pharpe said:

Would you mind sharing what you changed in the MindTheGapps package to to remove the arch check?

if [ $GAPPS_ARCH != $CPU_ARCH ]; then
  error "This package is built for $(nice_arch $GAPPS_ARCH) but your device is $(nice_arch $CPU_ARCH)! Aborting"
fi

Cdd100 said:

Yeah turns out it was using wifi but will find a way to share gps from my phone to use it as a nav system

have you seen the "bluetooth gps output" app? i used it with charting software on a laptop on a boat in the middle of the ocean once or twice lol

lilgman said:

Hi. I would love help to solve what I believe is a bootloop after I flash Lineage OS 20. I'm a newbie to android stuff, so probably some simple mistake. I've tried to follow this guide exactly, but all I get on reboot is the Amazon boot logo.

1. I successfully followed xyz`'s guide to brick, unlock, and root the device. https://forum.xda-developers.com/t/fire-hd-8-2018-only-unbrick-downgrade-unlock-root.3894256/

2. Boot to TWRP no problem
3. I wiped System, Data and Cache, but not Dalvik, Internal Storage or Storage
4. Pushed the Rom with ADB and installed it from TWRP. That finishes without errors
5. I did not flash Gapps
6. Reboot, but only get Amazon boot logo. Nothing happens even after 20 minutes.
7. I've tried reflashing and reinstalling the rom.
8. I re-downloaded rom and checked with sha256sum to make sure I didn't get a corrupted download. Still the same. I can revert back to FireOS 6300 with no problem, so I don't think it's a hardware failure.

I don't know how to troubleshoot on android, but am comfortable with cli in linux so should be able to follow directions. I'd appreciate any help you can offer.

Click to expand...

Just wanted to update that I got Lineage 20 working today after updating to TWRP version 34.0.0. I was not able to install MindTheGaps13 from post #15 in this guide because of the 64bit conflict. I was able to install BiTGApps linked here: https://forum.xda-developers.com/t/...age-20-0-3-january-2023.4533639/post-87911315

@pharpe's advice in the second paragraph of this post was crucial to get Play Store connected to the internet.

Thank you so much to everyone, especially @Kaijones23, for the great work and help!

Kaijones23 said:

I think it's because the CABC is controlling it via system properties.

# CABC on property:vendor.hwc.video_mode=1 write /sys/devices/platform/soc/soc:mtkfb@0/backlight_mode "mov" on property:vendor.hwc.video_mode=0 write /sys/devices/platform/soc/soc:mtkfb@0/backlight_mode "off"

pharpe said:

My main goal with this tablet is to watch streaming media (sports primarily). All the ROMs I've tried in the past did not work for streaming so this Fire went into a drawer. I was hoping that this latest version would work. I was able to install ESPN and Sling successfully. Both log in fine but whenever you try to watch anything you get an error.

Has anyone been able to get ESPN to work on this tablet with any ROM setup?

I've got this same issue. Disney+, ESPN, & YoutubeTV all throw an error when trying to playback video.

Otherwise, this ROM has been great.

JerseyChewi said:

I tried setting ro.boot.wificountrycode=GB in /system/build.prop, which looked promising from the logs, but ultimately didn't change anything.

<...>

I have been doing some investigation into this as well (I have similar symptoms to you: drops on 2.4GHz WiFi and no connection on 5GHz). Here are some of the things I have tried to no effect (I currently live in the US):
- Running iw reg set US (no output or effect in any log) and iw reg reload (which errors out with "Operation not supported on transport endpoint")
- Appending country=US to every copy of wpa_supplicant.conf that the shell could find in the filesystem (no effect)
- Editing the gsm.sim.operator.iso-country and gsm.operator.iso-country properties with setprop (no effect, altered properties did not persist past reboot)
- Thought about building a copy of crda, which according to Linux kernel docs is the proper way to set a regulatory domain (had no clue where to start with this, since Android doesn't seem to have any build tools and there's no framework in place in the crda source to build through the Android SDK. There's also a lot of infrastructure needed to get this to work that just won't translate to Android.)
I think the only solution is to ask the ROM dev (if he is not swamped with real-life responsibilities) to build crda and surrounding infrastructure into the ROM somehow or to put some sort of regulatory database into the kernel itself and control it with CONFIG_CFG80211_INTERNAL_REGDB.
Most information sourced from this set of docs and random Stack Overflow questions.

JerseyChewi said:

Thanks for looking into it. I've forgotten the details, but I think I got the impression that Android doesn't use CRDA. Could be totally wrong there though.

I guess that brings us right back to the question of what it does use. If it really is reading off SIM cards, there should be some sort of variable somewhere storing the SIM region that we can set manually, or the WiFi on my Android-x86 install (which also thinks it's a Pixel) should have no right to be working. Maybe I'll go ask the dev of the A-x86 distro what they did to set regulatory domains.

SergeantFury said:

I guess that brings us right back to the question of what it does use. If it really is reading off SIM cards, there should be some sort of variable somewhere storing the SIM region that we can set manually, or the WiFi on my Android-x86 install (which also thinks it's a Pixel) should have no right to be working. Maybe I'll go ask the dev of the A-x86 distro what they did to set regulatory domains.

I reckon it's more driver or firmware related. Obviously this works with LineageOS on other devices. You can see from my logcat that it tries to set the country to GB at least twice, once from me setting it manually, and once from telephony. It wouldn't be from the SIM card itself, as that wouldn't work when you're roaming. It just seems that those attempts to set it are ignored under the covers.

JerseyChewi said:

I reckon it's more driver or firmware related. Obviously this works with LineageOS on other devices. You can see from my logcat that it tries to set the country to GB at least twice, once from me setting it manually, and once from telephony. It wouldn't be from the SIM card itself, as that wouldn't work when you're roaming. It just seems that those attempts to set it are ignored under the covers.

Hmm. Does 5GHz work in FireOS? I think I'll flash back and check. The opinion of the other devs I mentioned was that it was a driver issue as well, but I doubt that Amazon would ship a 5GHz-capable chip that can't connect to 5GHz.

JerseyChewi said:

I flashed it as soon as I got it, so I don't really remember whether it worked in FireOS. I do remember having issues with this in LOS as far back as 11 though. Firmware can be part of the ROM too though, so that may be where we're missing something.

It seems perfectly happy on 5GHz WiFi in FireOS, both 6.3.1.2 and 7.3.2.7. It also would seem that at least in 6.3.1.2, crda is still used, and in the way that one would expect: somebody tells the kernel where the tablet is, and the kernel sends somebody to call crda. I can't check on FireOS 7, because as of now I don't think it's rootable.
FireOS 6.3.1.2 rooted with Magisk 25.2:

[root ~] # adb shell su -c dmesg | grep 80211
[  257.771534] <0> (0)[4:kworker/0:0][name:cfg80211&]cfg80211: Calling CRDA for country: US