yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] billyrich:
You can build MindTheGapps for Android 13 (T) yourself, see here.

Edit:

from linageos wiki: https://androidfilehost.com/?w=files&flid=322935

(MindTheGapps-13.0.0-arm-20221025_095826.zip)
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
You can use mind the gapps or whatever. I see that opengapps discontinued for Android 12 and 13
[Fire HD 8 and HD 10 Original Android Development] billyrich:
@Kaijones23, could you update the local_manifests repo with the manifest for los-20.0?

Thanks
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Beyond Bluetooth and Codecs, rom is quite nice, I can disable animations and set to 0.5 x.

For first release you did good job kaijones, I also saw you removed a lot of telemetry entries from kernel, so big cheers to you.

Good rom.

Edit: If you guys like gapps, you can use same use on official, https://androidfilehost.com/?fid=14871746926876840647 I use on other unofficial and all good.

We are arm.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Im not using local mainfest anymore. please use https://github.com/mt8163/android , its already integrated there.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
LiteGapps "lite" was used.

It's done! Looks like the obb files are in place this time...Nice ROM!
[Fire HD 8 and HD 10 Original Android Development] jumstec:
bluetooth does not work...

Whenever I try to connect with any enthusiasm... But it stops at "bluetooch is turned on".

In other words, it won't start.

Then the wired earphones won't work either, so I have no choice but to use the built-in speaker.

As you can see, it is probably a problem with the startup process.

Is this a problem only with this device?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Im looking into that issue

FYI : please please post logcat of the issues to make this job easier.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I was able to get the Gapps to get installed, I used MindtheGappsPackage . i bypassed the error message.
[Fire HD 8 and HD 10 Original Android Development] desidude2000:
BiTGApps worked for me as well. Download link from GitHub below.

https://github.com/BiTGApps/BiTGApps-Release/releases/download/v1.8/BiTGApps-arm-13.0.0-v1.8_signed.zip

Thanks so much for this ROM. My 5 year old son much appreciates you (as do I). Cheers.
[Fire HD 8 and HD 10 Original Android Development] desidude2000:
Thanks for the second update. I installed the update after wiping system and cache. Works just fine. UI Graphics are indeed a bit more responsive.

Keep up the good work. Thanks again
[Fire HD 8 and HD 10 Original Android Development] tsukeyomi:
Hello @Kaijones23 , amazing work! I’m incredibly grateful for this.

If I install this, is there a way to easily update to your newer builds (OTA) or will I need to clean flash every time?

I wish you best of luck with putting out polished builds!
[Fire HD 8 and HD 10 Original Android Development] nabiladeeb:
Thank you so much @Kaijones23 , just flashed it. Will report any issues. Really appreciate the hard work :D
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
You can dirty flash every time if I release an update. But if you're coming from like lineage 19.0 or older you would need to clean flash
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Extracted META-INF/com/google/android/update-binary, commented out the following lines, and added it back to the zip again.

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
[Fire HD 8 and HD 10 Original Android Development] dwreck420:
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
[Fire HD 8 and HD 10 Original Android Development] lilgman:
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://xdaforums.com/t/rom-unlocked-karnak-lineage-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!
[Fire HD 8 and HD 10 Original Android Development] SalsaBeard:
I've been looking around quite a bit and I'm turning up a pretty empty hand here. With LOS20.0 I'm noticing that my tablets won't stay asleep after the screen times out if the lock is set to none. If I manually sleep the display or have any lock option set when it times out, then the display will stay asleep. Otherwise it wakes up about 5 seconds after sleeping. I'm using these as wall control panels, so I'd really like to avoid the lock if possible, but I also don't just want to leave them on indefinitely if they aren't manually put to sleep.

Anyone else run into this and/or have any thoughts?

And a second item, I too ran into the issue where MindTheGApps won't install. I'll probably try the BiTGApps option mentioned above if I end up needing paid apps, but right now I've found that F-Droid works perfectly (if you only need access to free apps). It can be installed either as an APK directly from the OS or as a system resource. You can simply download the zip file from their site, reboot into recovery, and install it. Once the app is installed, you do need to allow it access to WiFi as I've noted it won't prompt for access, and it won't connect to the internet until you do. I've also read that it is only able to automatically update apps if it is installed as a system resource (zip file).

https://f-droid.org/en/docs/Get_F-Droid/
[Fire HD 8 and HD 10 Original Android Development] Quinoa_:
Can I ask you to explain it in detail?

I also get flickering on Netflix, YouTube, and MX player

Is there a way to solve it?
[Fire HD 8 and HD 10 Original Android Development] pioneersohpioneers:
I've got this same issue. Disney+, ESPN, & YoutubeTV all throw an error when trying to playback video.

Otherwise, this ROM has been great.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
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.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
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.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
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.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
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.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
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.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
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.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
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

I suspect this comes down to some sort of kernel configuration difference that leads to crda not being included in these LineageOS builds, but I couldn't even begin to guess at where exactly the difference would be.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
I haven't built a whole ROM in about a decade, but I do know a thing or two about kernels. I've found that our kernel does have CONFIG_CFG80211_CRDA_SUPPORT enabled.

$ zcat config.gz | fgrep 80211
CONFIG_CFG80211=y
CONFIG_NL80211_TESTMODE=y
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_INTERNAL_REGDB=y
CONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not set
# CONFIG_MAC80211 is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0

However, it also has CONFIG_CFG80211_INTERNAL_REGDB enabled, which I suspect it shouldn't. I notice the karnak defconfigs in the various versions of the kernel repo don't enable it. It doesn't seem to have the 4.19 kernel we have here, but I think this is still relevant.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
Aha. From the kernel docs on crda:

I don't think that's my issue, though: CONFIG_CFG80211_INTERNAL_REGDB isn't set for me, and I'm not on a 4.19 kernel. See below:

[root ~] # adb shell zcat /proc/config.gz | grep 80211
CONFIG_CFG80211=y
CONFIG_NL80211_TESTMODE=y
CONFIG_CFG80211_DEVELOPER_WARNINGS=y
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
# CONFIG_CFG80211_DEFAULT_PS is not set
CONFIG_CFG80211_DEBUGFS=y
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
CONFIG_CFG80211_WEXT=y
# CONFIG_LIB80211 is not set
# CONFIG_MAC80211 is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
[root ~] # adb shell uname -r
4.9.117-g63c08df92fdb

--

I also believe that the current kernel source is here - it's not archived and has a Lineage 20 branch. I'm also not noticing CONFIG_CFG80211_INTERNAL_REGDB being set in the configs here either, though.

--

Upon further investigation it would appear that the 4.9 kernel source does already have an existent-ish internal database so even if CONFIG_CFG80211_INTERNAL_REGDB were to be set both you and I should be able to get regdb updates (GB and US are both in there).
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Ah heh, I was half asleep and checked the kernel on my phone rather than my tablet. 😅

Although that now has me thinking that we've got this backwards. Maybe CONFIG_CFG80211_INTERNAL_REGDB should be set, despite what it says.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
It would seem that building a new kernel is a surprisingly involved process. I even need to build my own copy of a cross-compiling toolchain. I've thrown a new regulatory database into a local copy of the 4.9 kernel linked in the OP and enabled CONFIG_CFG80211_INTERNAL_REGDB in the karnak defconfig, and will let you know if I ever get it to boot.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
I cross-compile kernels all the time, so it wouldn't normally be a problem, but 4.9 is so old that you need an ancient GCC to build it. The oldest I could easily get my hands on was 8.5 and that was still a train wreck. I could still do it if I really had to, but I wasn't prepared to put that much effort in just now. The upstream linux-4.9.y branch has all the fixes for modern compilers but rebasing was a non-starter due to our kernel being a distant fork.

I hope your effort goes well.
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
Hey there this was working great until I got bricked and unbricked and when I tried to install and then reboot it rebooted back to recovery
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
We'll be needing some more details. What exactly did you do to end up bricked? How did you try to reinstall after the brick?
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
Quick question @Kaijones23: what toolchain and personal settings have you been using to compile kernels for this ROM? I'm getting some very weird "cannot find header" issues that I suspect are configuration differences between what I have and what you used.

for example:

In file included from drivers/misc/mediatek/video/mt8163/dispsys/ddp_drv.h:17:0,
from drivers/misc/mediatek/video/mt8163/dispsys/ddp_gamma.c:21:
drivers/misc/mediatek/video/mt8163/dispsys/../videox/disp_drv_platform.h:29:21: fatal error: ddp_drv.h: No such file or directory
#include "ddp_drv.h"
^
compilation terminated.

My current toolchain, obtained from Google here:

$ aarch64-linux-android-gcc --version
real-aarch64-linux-android-gcc (GCC) 4.9.x 20150123 (prerelease)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

--

I switched to LineageOS's gcc 4.9 from here; the errors and --version outputs are just about the same. (Actually, if it's possible, it might be easier if you built the kernel and sent it to me to test. The only really important change is setting CONFIG_CFG80211_INTERNAL_REGDB=y in whatever defconfig you're using to configure the kernel.)
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
I got it working it took a few tries
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
Never mind, it worked. I switched to gcc 6.3.1 from here, manually edited a couple of Makefiles, et voilà, it builds. Works and all too. Bit slow on the boot, but I think that's a worthy price to pay for functional 5GHz WiFi.

[eternitydragon ~] $ adb shell iw reg get
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

Find attached proof that it works (please do not mind the German) and a TWRP-flashable, rooted, and already-Amoneted boot image containing my slightly modified kernel. (The kernel image itself is also here, in case you don't like root. I installed it via Android Image Kitchen, but there are other ways too.)

@JerseyChewi Thank you for the help in sleuthing out the problem, and I hope this can help you too.

--

This exact same kernel is confirmed to boot the updated-to-December-of-'22 Lineage 18.1 as well, if that happens to be your jam.

Speaking of confirmation, if there are any testers willing to help make sure that this works, please flash the attached boot image, confirm that you can connect to 5GHz networks, and let me know the output of iw reg get below. (Note that this will reveal your country of residence; feel free to skip this if you'd like.)
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Well done and thanks very much! I'll try this out soon.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
No luck here sadly. The kernel option is definitely enabled now, I can see it in /proc/config.gz. It didn't pick up the country automatically, so I set it as root in adb. iw list still seems as limited as before though and my AP doesn't show up. I even tried setting it to US, but it's no better.

karnak:/ # iw reg get
global
country GB: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 27), (0 ms), DFS
(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
(5925 - 6425 @ 160), (N/A, 24), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
This is quite strange. I tried setting my domain to GB to see if I could replicate your issue and not only did 5GHz stop working on GB, it stopped working entirely. I haven't been able to connect back to 5GHz since, no matter what domain I'm on. Maybe a backup and new installation is required? I think I first tested the new kernel on a fresh install.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Oh dear! Sorry about that. Maybe a fresh install is key as mine wasn't. I can't imagine why though.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
Your kernel image seems a bit odd as it's much bigger than the usual size and the abootimg tool cannot read it. I tried building my own, but wifi didn't work any better. I tried disabling CRDA, but that didn't make it any better or worse.
[Fire HD 8 and HD 10 Original Android Development] JerseyChewi:
I tried editing net/wireless/db.txt to match my phone, but copied the GB entries to 00. That didn't help either, despite those entries appearing with iw reg get.

What I've noticed is that iw reg get normally shows a config for each PHY, but in our case, it only shows the global config. I'm starting to think it's more of a driver issue again.
[Fire HD 8 and HD 10 Original Android Development] SergeantFury:
If you're referring to the boot image, I padded it out to the same 16MB that a raw cat of my boot partition was - in fact, that boot image is the boot image from my device with the kernel replaced. Maybe try Android Image Kitchen and make your own boot image?

Mine seems to have worked despite this. I'm really not sure what's going on anymore. I'll try a reinstall later.
[Fire HD 8 and HD 10 Original Android Development] nospamboz:
[Edit: Eventually found that managing Webview in Android 10 and higher is no longer as simple as a developer option, and needs Magisk modules like Webview Manager or Open Webview. (And doesn't always work.)]

Is there any way to update Webview on this ROM? I can install the Google Webview from the Play Store, but it does not seem to activate. The developer option for Webview seems stuck on version 108. The native browser and FOSS Browser on F-Droid both report as 108 on whatismybrowser.com.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Sure, it happens when you compile the rom.

https://review.lineageos.org/c/LineageOS/scripts/+/357375/1/build-webview/build-webview.sh

Our webviews have not the same signature as official builds, so we can't use an official build webview cause signed by LineageOS, as for the Magisk things I will stay away from them.

Here one updated webview for you my friend, not the last, but newer than that: https://murena.io/s/XLgALmEPFR3ppjy

p.s. Somewhere a guy posted also stock FireOS updated webview, those come handy for who has other devices locked like me has mustang locked lol, and don't want update for obvious reasons.
[Fire HD 8 and HD 10 Original Android Development] Rypha:
So I upgraded TWRP to 3.4 and was able to flash the gapps just fine.

The ROM is running pretty well and while I still get a a message that I should flash magisk from within the app Magisk 26.1 and the youtube revanced module work just fine.

I don't have any issues apart from the headphone jack not working.

I mean it detects that I plug or unplug my headphones and pauses any active videos, but it just won't output sound to my headphones and will still play through the speakers.

Is there anythin I could do to get it working or should I just switch ROMs until it's been fixed?
[Fire HD 8 and HD 10 Original Android Development] Rypha:
Looks like I just needed to update amonet to v 3.0.1

I was on v1 which was why some roms would never boot, and I'd have weird stuff happening like with the audio output with this one.
[Fire HD 8 and HD 10 Original Android Development] Vinz517:
I m trying to clean install this ROM but the device remains in loop on the AMZ logo. Some advice?
[Fire HD 8 and HD 10 Original Android Development] traman124:
@Kaijones23 sorry if I sound ignorant, but I need to know if there are any issues with this rom (I'm going to flash LOS for my grandma's old slow Fire HD8 (2018/karnak) and want to know if the issues with boot times and ui lag still exist. I'm using amonet 3.0.1 right now

(Edit: I installed it and am waiting for it to boot..... how lonh should it take???)
[Fire HD 8 and HD 10 Original Android Development] traman124:
My Tab8 is stuck on 1st boot and I can't get into TWRP. I flashed the latest build avail on your GitHub. What do I do? Should I redo the amonet / shorting step and reflash TWRP??
[Fire HD 8 and HD 10 Original Android Development] nowell29:
hi guys - has anybody figured out how to customize the launchers?
[Fire HD 8 and HD 10 Original Android Development] traman124:
Change it on the home screen OR go to system -> buttons -> taskbar if you want to disable them
[Fire HD 8 and HD 10 Original Android Development] nowell29:
I actually like this "taskbar" I just want to change the available shortcuts. I figured out the mystery. Thank you for replying. The editing of the "taskbar" can only be done in Trebuchet. I always use Nova, and Nova wasn't participating. So I switched to Trebuchet, changed what I wanted, and then switched back to Nova.
[Fire HD 8 and HD 10 Original Android Development] traman124:
Oh you used nova... I see.
[Fire HD 8 and HD 10 Original Android Development] nahid13:
Pls can you fix the mic in this rom
[Fire HD 8 and HD 10 Original Android Development] traman124:
I tried to patch it and even use an out of kernel driver. Don’t try - Android 11 is more stable and the mic works properly.
[Fire HD 8 and HD 10 Original Android Development] nahid13:
ok thanks
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
I want to build AOSP for this device myself however the files on the github arnt avalible https://github.com/mt8163.
[Fire HD 8 and HD 10 Original Android Development] MicroMod777:
Will this work on Amazon Fire Max 11 tablet?
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
Not it will not. That device is locked tight.