yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] ppog:
I installed this, booted once and set up. I wanted to reboot to recovery to flash magisk, but when I enter the command from adb, it just hangs on the Amazon logo, and TWRP doesn't boot. Any help?

EDIT It does reboot to recovery from Lineage power menu
[Fire HD 8 and HD 10 Original Android Development] badboy21102000:
Why not make one for hd 8 2020.
[Fire HD 8 and HD 10 Original Android Development] AJS1986:
The newer models can't be rooted as yet so there's no way of flashing a new OS on them.
[Fire HD 8 and HD 10 Original Android Development] ARandomneko101:
Will this work with the fire hd 10 (2017) if not whats the latest lineage version that will
[Fire HD 8 and HD 10 Original Android Development] Qynklee:
I used this rom in some week and now I think it very well. Very smooth for kindle, app run very nice despite a low ram device. Battery not drain, google servce work with gapps pico newest and a bug in camera but I'm Ok because I dont use cam 😀 Very thanks Kai 🤩
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I also tried this ROM. Works fine. Bug in camera means about video? Yes, camera works okay but video, it works but very dark. Only this issue. Very nice job Kai.
[Fire HD 8 and HD 10 Original Android Development] Rvllmor:
twitch and youtube [vanced] livestreams doesn't work?
[Fire HD 8 and HD 10 Original Android Development] xeenon:
Hello,

Thank you for this ROM. I love it. But I am a little bit confused.

I want to install Netflix and Disney+ from the play store. But I can't find the apps. In the web version of play store, it says there are no compatible devices.

I downloaded the Netflix app from the official Netflix page. After installing the app stopped due incompatibility.

Best regards
[Fire HD 8 and HD 10 Original Android Development] eris170:
Thanks for all the work on this! I flashed this to my hd8 a couple weeks ago. Not sure if I have the wrong Gapps or what (should be using Gapps 11 with 18.1-20211028-UNOFFICIAL-karnak, right?). Typing any text at all results in 3-4-many random characters being injected into the text field with each "key press". I disabled auto-correct and auto-fill and that seems to have fixed it. Also Brave and Firefox crash after a minute or so when playing back video on youtube. I have a logcat (https://pastebin.com/56cexaiP) which I tried to capture as far back as "normal" playback was happening. If someone could have a look and let me know if this is "normal"? I read something in this thread about codec issues but not sure it's related.
[Fire HD 8 and HD 10 Original Android Development] eris170:
Thanks again! Installed NewPipe (what a great app!) and set to WebM. Playing videos just fine now.

I'll check into a different keyboard if I run into more issues.
[Fire HD 8 and HD 10 Original Android Development] mikef1:
Thank-you for this android 11 ROM; for the most part, it works great!

While using it I discovered "Scoped Storage" is something new, and it's a pain.

Is there a way to disable it?

I tried a Magisk module: Scoped Storage Disabler but it doesn't seem to work right.

I also tried a few other methods, but no dice.

I'm trying to copy game files into the 'obb' directory.

Thank-you,

Mike F.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
I bought a few 2017 and 2018 Fire HD 8's during the pre-xmas sale. I was able to unlock and reflash the 7th gen (douglas) devices. pardon the pun, a flas. Unfortunately, I had to open up the case on the 8th gen's to get the karnak bootloader unlocked, but once I got that process worked out, I was able to load the 18.1 ROM onto them no problem.

But I was a nit surprised when some of my APKs failed to installed. I didn't realize all the 8th gen ROMs, at least those I could find, are only 32 bit. Especially since the ROMs I loaded on my 7th gen models were 64 bit, and the two have nearly identical hardware. Given that they both use the same 64bit CPU, and benchmark the same, I'm actually wondering if these 8th gen models are even worth the extra dollars.

I (now) realize Amazon shipped both models with a 32 bit version of Android, but beyond that, can someone tell me why there isn't a 64 ROM for karnak, like there is for douglas? And what the technical differences are between the douglas and karnak models? They're spec sheets appear identical, so I assume the changes are rather low level.

I apologize if this info I'm seeking is somewhere else, but after a couple hours on Google, I couldn't find any technical answers to these questions.If it does exist, just post a link please!

Here are the Amazon specs for both models. And as far as I can tell, the only difference between them is which version of Android they support:

Fire Tablet Specifications: Fire HD Models | Fire Tablets

Select the Fire tablet device you want to see. Fire HD 10 (2023, 13th Gen) Fire HD 10 (2023, 13th Gen) Fire Max 11 (2023, 13th Gen) Fire HD 8 (2022, 12...

developer.amazon.com

Fire Tablet Specifications: Fire HD Models | Fire Tablets

Select the Fire tablet device you want to see. Fire HD 10 (2023, 13th Gen) Fire HD 10 (2023, 13th Gen) Fire Max 11 (2023, 13th Gen) Fire HD 8 (2022, 12...

developer.amazon.com

Oh, and the 2018 models come in various colors.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
Removing duplicate submission.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
My first throught was the Android 11 ROM was built as a 32 bit ROM because the CPU didn't support the new features in Android 11 which require hardware support. Only I quickly realized all of the ROMs that have been posted for karnak are 32 bit.

If it's a question of BLOBS, the OS can be 64 bit, even if the drivers/blobs are 32 bit. It should just involve changing a few flags, and remapping a few pointers inside the build config. I'm tempted to try, but I have enough projects on my plate already. I bought these as cheap test devices, and for use as low power, network monitoring bots, IoT remote controls, etc. I ned to be careful I don't fall down the rabbit hole to far.

So I thought I'd post, and ask the question? It feels like an even bigger mystery to me given this work has already been done for the almost identical, and less popular, douglas variant. The douglas tablets also shipped with a 32 bit ABI.
[Fire HD 8 and HD 10 Original Android Development] FreakyyLike:
@Kaijones23 tried it as I remember on LOS14. But it resulted in Bootloops.

The Hardware between douglas and karnak is almost similar, but they run diffrent Fire OS. Douglas runs on FireOS 5 (5.1 Lolipop) and Karnak runs on FOS 7 (9 Pie).

I guess they removed from 5 to 6 everything Kernelside to not support 64bit at all for a reason?

I think its possible to run 64 OS on 32 BLOPS, but in this case it requires a lot of Kernel rewrite and trial/error.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
We actually booted 64 bit LineageOS 14.1 on karnak (using blobs from some Asus MT8163 tab). However, almost nothing worked.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
Cat anyone provide up-to-date instructions for compiling the 18.1 ROM forkarnak? I think there are steps I'm missing and/or something is missing from the GitHub repos. For example, I can't find the manifest with the linaro tool chain. But there are other issues. Like the mt8163/android_kernel_mediatek_mt8163_4.9 repo has no lineage-18.1 branch. So I'm not sure if it was never committed, it isn't needed, or it's identical to lineage-17.1.

It almost feels a like some of the changes weren't committed/pushed., or perhaps there is some other build process/script that I haven't found, or isn't on GitHub.

I've tried a number of different strategies, but at the moment I have the following device_manifest.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Device Tree -->
<project name="mt8163/android_device_amazon_karnak" path="device/amazon/karnak" remote="github" revision="lineage-18.1"/>

<!-- Kernel sources -->
<project name="mt8163/android_kernel_amazon_karnak_4.9" path="kernel/amazon/karnak" remote="github" revision="lineage-18.1"/>
<project name="mt8163/android_kernel_mediatek_mt8163_4.9" path="kernel/mediatek/mt8163/4.9" remote="github" revision="lineage-17.1"/>

<!-- Vendor trees -->
<project name="mt8163/android_vendor_amazon_karnak" path="vendor/amazon/karnak" remote="github" revision="lineage-18.1"/>
<project name="mt8163/android_vendor_amazon_mt8163" path="vendor/amazon/mt8163" remote="github" revision="lineage-18.1"/>
<project name="mt8163/android_vendor_raffy" path="vendor/raffy" remote="github" revision="lineage-18.1"/>
</manifest>

And I've recently tried pulling in the linaro tool chain with variations on this linaro_manifest.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Repositories -->
<!-- Linaro Repositories -->
<remote name="linaro-android" fetch="git://android-git.linaro.org/" />
<!-- Linaro Toolchains -->
<project name="prebuilts/gcc/linux-x86/aarch64/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu" path="prebuilts/linaro/linux-x86/aarch64/aarch64-linux-gnu" remote="linaro-android" revision="master" />
</manifest>

As for build commands, the simplified version would be:

mkdir -p $HOME/temp && mkdir -p $HOME/cache && mkdir -p $HOME/android/lineage
cd $HOME/android/lineage
git config --global user.name "Build Robot"
git config --global user.email "robot@lineageos.org"
git config --global color.ui false
repo init -u git://github.com/LineageOS/android.git -b lineage-18.1 -g default,-darwin
mkdir -p .repo/local_manifests/
cp $HOME/device_manifest.xml .repo/local_manifests/
cp $HOME/linearo_manifest.xml .repo/local_manifests/
repo sync --jobs=32
export USE_CCACHE=1
export CCACHE_COMPRESS=1
export CCACHE_DIR="$HOME/cache"
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
source build/envsetup.sh
rm -rf out/target/product/karnak/obj/KERNEL_OBJ/.version
rm -rf out/target/product/karnak/obj/KERNEL_OBJ/.config.old
lunch lineage_karnak-userdebug
cmka
[Fire HD 8 and HD 10 Original Android Development] mikef1:
I tried it, but doesn't work correctly on this rom.

Looks like forget about loading games that use a .obb file.

MikeF
[Fire HD 8 and HD 10 Original Android Development] rbronco21:
I've gone back and forth from your 14.1 and 16.0 ROMs with some success. What are the advantages and disadvantages of 18.1? My daughter currently uses it for kid games and some games stop or don't even load. I'd try this out in a second if it didn't mean facing the wrath of a 4yo.
[Fire HD 8 and HD 10 Original Android Development] minedog67:
when will lineage 19 be worked on
[Fire HD 8 and HD 10 Original Android Development] moritzm:
@Kaijones23

Thanks a lot for this ROM. I finally freed the kids tablet from FireOS and can now use a decent adblocker ;)

Just one think is a bit annoying:

Wifi is not working as expected. When my access point is using WPA2/WPA3 in mixed mode, the tablet will not connect to the wifi.

Just tried it with 17.1 and there wifi works fine with the same config. As the camera and some apps are not working on 17.1 I can't switch to 17.1.

Any chance that it can be fixed in 18.1?
[Fire HD 8 and HD 10 Original Android Development] kingladar:
I'm able to build the code just fine now. There were 3 typos in the kernel code that were keeping my early attempts from compiling. At least when I was using the v7.5 of the Linaro tool chain.

The only issue in which I was unsure how to fix, was the framerate. It was being calculated at 1520, when building one of the files, but the kernel config had CONFIG_FRAME_WARN=1500. Since warnings were treated as errors, the build was failing. I couldn't figure out how the 1520 value was being derived, so I simply increased the kernel config limit to 1520.

I'm playing around now, to see if I can build a ROM with support for the arm64-v8a ABI. I benchmarked the douglas with 15.1 and karnak with 18.1 and the douglas ROM was about 20% faster. I suspect that was in part because of the ABI.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
This is the error, in kd_sensorlist.c, in the function CAMERA_HW_Ioctl. Anybody know the best way to fix this?

./error.log:../../../../../../kernel/amazon/karnak/drivers/misc/mediatek/imgsensor/src/mt8163/.c: In function ‘CAMERA_HW_Ioctl’:
./error.log:../../../../../../kernel/amazon/karnak/drivers/misc/mediatek/imgsensor/src/mt8163/kd_sensorlist.c:3394:1: error: the frame size of 1520 bytes is larger than 1500 bytes [-Werror=frame-larger-than=]

I've been using this workaround:

sed -i 's/CONFIG_FRAME_WARN=1500/CONFIG_FRAME_WARN=1520/g' kernel/amazon/karnak/arch/arm64/configs/lineageos_karnak_defconfig
sed -i 's/CONFIG_FRAME_WARN,COMMON,,,1500,1500,1500,1500,1500,1500/CONFIG_FRAME_WARN,COMMON,,,1520,1520,1520,1520,1520,1520/g' kernel/amazon/karnak/scripts/kcrs/correct_config.csv

But that just increases the threshold. It doesn't set the frame rate to 1500. I'm not sure how important this is... older kernel builds for mt8163 used a frame rate of 1400.
[Fire HD 8 and HD 10 Original Android Development] digitalTARDIS:
I've been testing this ROM for about a week now. No major issues, Brave browser crashes every minute or so, same with a few other apps like Hyperion wallpaper picker, but I'm assuming that's the codecs?
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Really enjoying the ROM, but on this this version, and the Lineage 16 build, browser keeps crashing whenever trying to download something like gapps
[Fire HD 8 and HD 10 Original Android Development] flatherskevin:
Following up on this. Can't download anything from the Google play store as well. Always says there isn't enough storage when I have 10GB left on my direct device, and another 120GB as a mounted extended storage micro SD
[Fire HD 8 and HD 10 Original Android Development] yohoki3:
You can use X-Plore to install .obb files.

It's a little tricky, and gets blocked if you try to add a shortcut. Manually go here: /mnt/sdcard/android

You'll be in the internal android folder and have access to apps' data folders to place obb files.
[Fire HD 8 and HD 10 Original Android Development] enigma9o7:
I've been using this about a week and seems to be working fairly well, other than minor issues with video playback. In particular, with Kodi, I have to disable hardware rendering to be able to play back local H264 videos.

Any solution? This is the first version of Lineage I've tried on this device; would an older version work better?
[Fire HD 8 and HD 10 Original Android Development] lfom:
@enigma9o7 Try Lineage 16.0, unfortunately this version still has some issues with CODECs, while v16.0 works fine with just minor hiccups regarding WiFi.
[Fire HD 8 and HD 10 Original Android Development] 789mod:
Is camera work fine on this version??? 11 android ?
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
I reverted back to 15.1, which I found to be the most stable release so far. Do we have to/does it matter if we flash the finalize.zip file after flashing a new ROM, or did it only have to be run once to disable OTA? 18.1 was a little sluggish at first, but I might try to install it again later.

Maybe I shouldn't have messed with Magisk, because updating it also put me into a boot loop earlier. Would anyone happen to know how I can uninstall Magisk through TWRP recovery? Thank you.

UPDATE: I had to reflash the ROM to get out of the bootloop.
[Fire HD 8 and HD 10 Original Android Development] 789mod:
You most turn of your device and re flash twep
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
Took another stab at this one. Upon setup, I got Trust notifications for SELinux not enforcing and Encryption being disabled. Do these need to be addressed? I'm actually not sure if I had these on the previous builds before or if I just turned the notifications off and forgot about it. (Going back to 15.1 also gave me the same notifications.)

I also briefly had a warning saying that "Speech Services by Google" stopped working on the first startup, but it never came back after I dismissed it.

Overall, this one seems to be running quite well though. Thank you!
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
A couple new issues I noticed after a bit are that the screen becomes unresponsive/stays black after a while if it falls asleep while charging, and it doesn't seem to want to charge past 80%. I'm not sure if the latter was intentional to prevent encrypting, but I'm not brave enough to test that one myself.
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
After a few days of light use, it actually seems the battery is stuck reading 80%.

EDIT: After another couple days, it started going down again.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Could you explain what you have to did to compile the kernel successfully? Because I tried your guide and I keep getting problems building karnak because of the kernel.

Spoiler content hidden.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Hey kingladar, thanks, your kernel patches fixed the compilation, I probably did it in the strangest way possible to compile it:

Spoiler content hidden.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
You're right! I removed the bacon, but must have forgotten to remove it from the copy I had saved in my scripts repo. And the scri[pt I sent you was one of my early attempts, without all the patches, and changes to try and get a 64 ABI version working.

That said, I think it still builds the karnak ROMs, since the commands before it queue that device for compilation, but it's been awhile.

If the script is stable, and the ROMs work properly, submit it to this repo as PR: https://github.com/craptastic-droids/manifests

I can have my Jenkins server start rebuilding the ROMs every 1-2 weeks, and push them out. That should make it easier to stay "current"with what's coming out of the Android firehose. That's roughly 8,086 PSI of patchey goodness, that has, of course, been rebranded as "security updates."
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Sadly the rom doesn't boot.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
I was afraid of that. I took a quick look, and I think the head revisions all contain my 64 ABI changes, which I haven't managed to get working yet. If you can figure out why, please let me know! I also haven't been abnle to find any good guides on how to find out WHY it isn't booting, as rebooting into TWRP, and trying to get debug info like the various tutorails suggest, hasn't provided any info.

If you go back in the commit logs, and point your manifest at one of the initial commits for the each f the relevant repos, it should reverse the 64 bit chnages I made, switch you back to building a 32 bit ABI version.

I did get one a ROM to boot early on that way, but I didn't spend much time testing, and since I didn't realize what was ahread of me, I also didn't keep track of the exact commits, or tool chain I used to make it.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Thanks, I think easiest way is fork original and fix the kernel tree with your fixes, that should be back to building a 32 bit ABI as you said.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
Perhaps @Kaijones23 can shed some light on what his secret sauce might be?

And @Kaijones23 if you do see this, I recently noticed a bug. I wasn't able to get two karnaks talking with each other bluetooth. I think the issue was they were both trying to use the same bluetooth address. I haven't investigated any further, yet, but it looked like it was using a hard coded value.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Hey kingladar, I had no luck booting the 32bit one too with the kernel compiled with the patches you given me, so I taken the old kernel of kai and I putted it inside the new rom compiled and it booted. So the reason why it doesn't boot is the kernel. Maybe there is something else we don't know.

Anyway I am happy the same, now I will see how it behaves. :)

Spoiler content hidden.
[Fire HD 8 and HD 10 Original Android Development] kingladar:
For those who want one, Woot has 8th gen models on sale again. Although for me, it appears only the Yellow models with 32gb are available for $29.99, and not any of the 16gb models/other colors for $24.99.

Fire HD 8 Tablet (2018, 8th Gen) - $24.99 - Free shipping for Prime members

Fire HD 8 Tablet (2018, 8th Gen)

electronics.woot.com
[Fire HD 8 and HD 10 Original Android Development] Israelleite:
Can't get it to work. I flash the rom, but when I flash the gapps ( arm 11 mini ) it boot loops in bootanimation . Any hint ?

If I only flash the rom, it works fine .
[Fire HD 8 and HD 10 Original Android Development] Israelleite:
which rom are you using ?
[Fire HD 8 and HD 10 Original Android Development] Israelleite:
Can you guys please help me ? I really really want to put my fire 8th generation to work with gapps or minthegapps.
[Fire HD 8 and HD 10 Original Android Development] rbronco21:
Looks like I am currently on Lineage 16 and using OpenGApps ARM 9.0 micro. Of course, this is the most recent one. It seems like I had to try a couple of OpenGApps versions to get one to work, then update everything through Google Play.

These are the notes I took as I worked out the install procedure from all the posts:

Allow modifications (probably in TWRP?)

Go to wipe and wipe: system, data, cache

Go to install and flash ROM.zip and G-APPS with zip signature confirmation (md5s)

micro has gmail, calendars, and pixel launcher; pico is pretty empty and lots of google stuff won't work)

Reboot
[Fire HD 8 and HD 10 Original Android Development] kingladar:
Assuing you have an unlocked karnak tablet, use this ROM:

https://archive.org/download/fire_hd_8_and_10_replacement_roms_202201/KARNAK/lineage-18.1-karnak.zip

With this GApps:

https://archive.org/download/fire_hd_8_and_10_replacement_roms_202201/KARNAK/open-gapps-arm-11.0-pico.zip

Hashes

4c500b80325756a9333b9261519e783b1fb217e48c1577e61ab027587957c140 lineage-18.1-karnak.zip

9b55701a6e61fef383b3c0781d76e71a9e8668f1d6a51b24fd1ecaded32d6fdc open-gapps-arm-11.0-pico.zip
[Fire HD 8 and HD 10 Original Android Development] Voha888:
Good ROM, but Google Chrome keeps crashing. Lineage 17 have looped bootanimation on my Fire. Thats why, I will try Lineage 16
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Not sure about it, because I use it with microG, but for me I get this E: Reconcile failed: Package com.android.chrome requires unavailable shared library com.google.android.trichromelibrary; failing
[Fire HD 8 and HD 10 Original Android Development] Voha888:
I am using opengapps. You are right, the problem of Chrome crashes on Android 11 is actively discussed on the Russian-language forum. Many people solve this by rebooting the device, installing different versions of Webview, and trichrome - which you mentioned.

I've been on Lineage 14.1 for a long time, and haven't updated Chrome, so maybe the problem is not in the ROM
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Not sure, only problem I have with this rom is video codecs but no big problem. I use bromite with it and all works fine,

Spoiler content hidden.

On my build webview is this version, and it happens same.
[Fire HD 8 and HD 10 Original Android Development] Voha888:
Do wired headphones work on Your tablet on this ROM?
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
I never tried cause I only use bluetooth ones cause of the amplifier problem that has always been there.
[Fire HD 8 and HD 10 Original Android Development] JSquare:
Anyone has issues with the GApps Camera, I get a dark screen. Works fine with Open Camera, but when I try to use an app like Google Keep it defaults to the included GApps Camera app instead of Open Camera app.