yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Nice. I dont use gapps so thats even better. Trying to live a google-less life is strange at first, but then makes sense in the long term.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
I was listening the Android Faithful podcast where they had a news segment about people who have android 14 facing bootloop problems, though they were using pixel phones.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I had no bootloop problems
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
Things can vary widely from device to device... and at least we modders have TWRP :p
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
I'm having an issue installing an application

It fails with the follwing message (in adb):

failed to install <appname>.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

Is this an issue with the ROM? This is the only app that's giving me this issue; and it worked fine on the armeabi-v7a Galaxy Tab 4
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
What App are you trying to install?
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
Can I tell you via PM?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
sure
[Fire HD 8 and HD 10 Original Android Development] timpster:
I have never yet rooted android, how do I setup magisk? I understand how to reboot into the twrp system, but not a clue what I need to do.
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
[ROM][unlocked][karnak] Lineage-20.0 [3 January 2023]

Disclaimer /* * This ROM will eat your cat * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features...

xdaforums.com
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Other than the microphone, headphone jack and memory issues, Android 13 is excellent, im eagerly anticipating Android 14.
[Fire HD 8 and HD 10 Original Android Development] timpster:
O.K. so to explain the process, I still had lineageOS file downloaded on my SD card. I could not extract the whole folder, which is actually helpful, because the included Files program allows viewing the contents.

I selected the boot.img file and extracted only that file. I then had magisk apk file from github installed and open, and had magisk patch that boot.img file.

Then, I rebooted into TWRP, and clicked install, and could not find the file.

Turns out I need to click the button for "image file" so it is visible.

Then I "installed" that patched magisk boot img file.

I reboot to lineageOS and open magisk again. It says it needs something else and reboots the device. It appears to be stuck at the bootscreen so I left it alone for at least ten minutes and held the power button until device is off.

Then reboot.

So, I can say for certain that modifying swapiness does nothing, and having pandora open, then switching to Fennec (firefox with about:config) very quickly caused pandora to close.

The only way I see to fix this is a larger swap region. Is there a simple way to increase or re-create a larger area? Has a scenario for music streaming / local media playback and browsing the web been tested?

I have been using termux to check free -m for basically the whole time I've had this system installed. I found it confusing why swap isn't used more.

With more closer testing, programs (pandora, but could be anything, even a browser tab) will close when physical memory is full, with swap only being used by somewhere around 250 - 270. So it has maybe 350 MB of swap that could be used, but is not. Once the 1390 MB of regular memory is absolutely full, something is engaging (akin to an out of memory software program) and some task quickly gets closed.

I looked for some values in /proc/sys/vm but changing (echo value > path) hasn't solved the oom behavior. What process could be responsible for checking free memory, and not at all considering available swap memory as well? If whatever that is, would also consider the other 300-400 MB swap space, and then allow it to be used, performance may be slow, or sluggish, but more programs, browser tabs etc could be used at once and switched between.

It would also reduce unnecessary network use, locally and server-side, from tabs losing memory space.

I am looking forward to the next release, and hope the swap space can be used more effectively.

Setting proc sys vm swappiness to 0 does not cause any noticable differences, so something is managing memory in a way I don't understand.
[Fire HD 8 and HD 10 Original Android Development] timpster:
Here's a quick and easy test. Open Fennec (which has about:config, firefox removed it from the main program for android and iOS) and just scroll down ten days of posts on

http://reddit.com/r/linux

Just keep scrolling until you are nearly 10 days back in post date using the default sort method.

Then, watch the whole browser reload spontaniously. This is because swap is not being included in program memory use for user-started programs. Swappiness set to 200 does nothing at all to change the amount of swap memory used by programs, although it does get rid of the constant pauses that occur every three to four seconds after a while. Those pauses last about five or more seconds and can make it very slow to scroll and read an article. Swappiness at 200 helps with this, but does not at all allow programs to utilize swap space.

Addition: I have learned that Android doesn't use swap at all, and that this model of device doesn't by default support it. It isn't supported because as I worried, it would wear out the nand flash memory way sooner than need be.

Instead, it has its own memory manager. To modify its settings:

echo #,#,#,#,#,# > /sys/module/lowmemorykiller/parameters/minfree

I can't remember what each number represent, but you must echo all values.

My setup:

echo 96,99,120,140,144,52800 > /sys/module/lowmemorykiller/parameters/minfree

Seems to work O.K. but I lost this browser tab (had already clicked save) and an EQ program in the background.

I arbitrarily picked the 300s for all values, as it is recommended for the values to be of increasing order, and I don't remember the exact values. At one point, I actually had:

Firewall (60 MB)

Pandora (averages 32 MB)

Fennec, with an incredible three tabs open AND none of which ever reloaded when switching

Termux, and superSU to enter su on the comnand line and fiddle with these settings.

Once I loaded a forth tab in fennec, the music stopped.

So try values, starting with 364, and slowly increase, up to 640 I think was the highest value with is 256 kilobytes of memory.

Tweak Android Low Memory Killer (LMK) to Your Needs - DroidViews

In Android (and Linux) philosophy, free RAM is wasted RAM. The Operating System will try to utilize all the amount of RAM available to it to increase its throughput. By design, Android tends to keep activities in RAM after the user exits them. This way it can speed up opening them again if...

www.droidviews.com
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
@Kaijones23 being mindful that you are a busy person, could you give a timeline for the A14 build?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Refrain from asking for ETAs, please. I'm not entirely sure, but it might be against XDA rules, and honestly, it can be quite annoying. I personally know Kai, and he's constantly working on Android 14. However, it's going to need some time before it's ready for a stable release.​
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Duly noted. My apologies @Kaijones23
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
It is being worked on and it is somewhat close to being done I have been invited to test it and there are not many major issues
[Fire HD 8 and HD 10 Original Android Development] Dismal.:
Android 14 will be based on AOSP and not lineage os :)
[Fire HD 8 and HD 10 Original Android Development] OptimalGrammar:
The download link appears to be broken, could somebody reupload please?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
the link is not broken
[Fire HD 8 and HD 10 Original Android Development] TheNox88:
Sorry for Disturbing but i have the same problem. Looks like Github is down because "No Found" or "404" but its only this.
[Fire HD 8 and HD 10 Original Android Development] somolinoff:
My experience is the same.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
The llink is updated. so try again
[Fire HD 8 and HD 10 Original Android Development] somolinoff:
Thank you very much.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Happy Thanksgiving.

Now that i think about it, the speakers are so low on LOS20 when compared to LOS16, which then brings me to this question; Does the AudioFX app actual do any meaningful sound improvement? On/Off whilst using options sound the same and is at the same decibal level when using a decibal meter. Tried speakers, earphones, external speakers, still low. I was tempted to stay on LOS16 due to the low speakers, but a annoyingly the wifi keeps disconnecting so i came back to LOS20.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
One more thing, is amonet v3 a one-time flash or will i have to flash every time i change roms?
[Fire HD 8 and HD 10 Original Android Development] Qynklee:
I only use one times when unlock Bootloader and install TWRP
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
echo "TZ, Preloader or LK are too new, RPMB downgrade necessary (or brick option used)"

Since we downgraded them in order to push our changes, running custom rom, we don't want them updated, cause probably it won't work anymore. You can find more infos inside the file called fireos-step.sh, what will upgrade those components is of course an Amazon update of the stock firmware. From my understanding, all those components in the right versions, allow us to complete the boot chain. Also your comment reminded me that in some cases a permanent "jailbreak" is not possible, and those are semi-tethered exploits that need to be runned everytime, I think we had something similar to it in the past in other devices, and we still have it in another device.

Anyway a better interpretation similar to our situation you can find here: https://dragon863.github.io/blog/echoroot.html This puts the processor into bootrom mode, allowing us to push a payload to the memory that loads a patched preloader that doesn’t verify that the little kernel is signed with the correct keys. However, this means it is a tethered exploit, as we are required to push the patched preloader by USB.

So in the end I think we are untethered thanks to the microloader, in our case, probably the echodot is a different story.
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
One time, then TWRP will take care of it (remember NOT to flash images from Android itself!)
[Fire HD 8 and HD 10 Original Android Development] Rypha:
Yeah, I realized later that the issue still persisted...

My memory is foggy as it's been a while since I messed around with this tablet and have since given it to my mom but uuh, you have to downgrade to Lineage 17 or even 16 to not have to deal with this issue anymore.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
LOS 17 working well for you? I attempted it but it was laggy. LOS 16 really tempting but that wifi issue stopping me from making a jump.
[Fire HD 8 and HD 10 Original Android Development] Rypha:
Ah, I checked and it was LOS 16 and yeah, the wifi issue is annoying for my mom but she knows how to turn the wifi off and on again to temporarily fix it now.

And while I can't remember why I didn't stick with LOS 17 the performance was probably why.

I might look for better ROMs for this tablet and if I find something better I'll try to let you know.
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
I flashed this and I got a bootloop! I am reinstalling LOS 16

(I'm rebooting back into LOS 16 now)
[Fire HD 8 and HD 10 Original Android Development] ITasteTerrible:
I'm trying to go back to stock and i'm having trouble finding the fire os 6 for fire tablet 8 karnak. I was able to get it back to stock about 1 month ago but I don't remember which os download worked and it has recently started to boot loop. I'm also willing to install another ROM as long as it pretty stable as I plan to give the tablet to a family member. I was able to reinstall lineage os 20 but its pretty laggy.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I never encountered a boot loop, you probably could need to wipe user data before flashing, and you could have provided logs
[Fire HD 8 and HD 10 Original Android Development] JimmyK87:
I was stuck in a boot loop using the older amonet V2, trying flashing the latest version first then LOS20
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
I wiped everything but Internal Storage, and I couldn't get a log either...
[Fire HD 8 and HD 10 Original Android Development] timpster:
I want to add at the top of this post, a pdf that talks about tuning ext4 on flash media, and settings to modify:

http://csl.skku.edu/papers/fce12b.pdf

So, there are some reasons to tune the settings. Another option is to use noop, or no scheduler, but I like contiguous file allocation, on any storage type.

Hey, I went plundering into the /sys/fs/ext4 and also the /sys/block/mmcblk0

mmcblk1/

Then do ls command.

In termux, a commandline program, if you type in

cd /sys/block/

and then press the two arrows (left right arrow on far left) this is the TAB key, and will autocomplete available options, without having to change directory, then list, ls. It makes it much faster to navigate available directories and available settings.

There is also /proc/sys/fs but those options seem to be not as performance impacting, so if you want to change file syshem settings, /sys/block/mmc (tab key) is a great place to start.

This is part of the reason I rooted the device, to test performance. It is my understanding that all of these settings should be temporary unless written to

/etc/sysctl.conf

I turned off in iosxhed:

low_latency.

This should be temporary, but when I shutdown and rebooted, the lineageOS animation just stays on the screen. I am currently backing up some data in case a wipe is the best way forward but I want to know what is the issue.

I have waited over half an hour and the animation still continues.

How can I show the text output during boot? I hold the power button to power off, so I'm guessing dmesg won't be useful.

Is there any wipe option to keep the currently installed software but clear the settings of whatever is misconfigured?
[Fire HD 8 and HD 10 Original Android Development] traman124:
Do a reflash of LOS. Wipe system inside TWRP first - you'll need to reboot but apps and files will stay
[Fire HD 8 and HD 10 Original Android Development] vendo232:
tried this version and it does not support exfat ( larger files than 4GB ) , SD cards are formated to FAT32. Is there a way to add exFAT?
[Fire HD 8 and HD 10 Original Android Development] timpster:
Edit: I cleared some space on internal by copying downloaded podcasts back to desktop hard disk. This freed up over one gigabyte for over 3 GB free. I did an advanced wipe/ repair function on data partition. That fixed it.
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
Just press backup and you might see a data partition to back up, just back that up and erase all data in the wipe,
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
you would need to do adb logcat to see what’s is going on in the logs.
[Fire HD 8 and HD 10 Original Android Development] timpster:
Yep, I couldn't use the repair function in advanced wipe settings as I was low on space, so I backed up some podcast downloads, and had just barely enough to do the repair operation. All apps still installed and I am able to keep downloaded podcasts on the internal storage. I usually use my sdcard, until it is full, so it may be time to back it up too.
[Fire HD 8 and HD 10 Original Android Development] timpster:
Do you usually view and backup sd card contents on your own pc? If so, I suggest trying F2FS, which is flash-friendly fliesystem, or, EXT2 or ext3 without journaling. Journaling keeps track of write operations, and which do not complete. This adds to the writes on flash storage.

To view a ext 2,3,4 or f2fs format media, you will need Linux. Windows now has Linux as an easy download in the Microsoft store. This will allow you to boot Linux as easy as opening Firefox.

Then, you'd passthrough the usb connection to the Linux virtual system, which I hope is easy to do. If not, download virtualbox, and download Ubuntu. Then, open the .iso file from ubuntu as the startup disk. Then, connect the tablet to your pc once Ubuntu has booted.

In virtualbox, click devices in the menubar, usb, and whatever the tablet connection is called. This will take away access from Windows, and send it to the Linux system. Then you can read any file system you want.

So, ext4 looks to be supported, judging by the /sys/fs/ext4 directory. I have no idea about f2fs, or any others.
[Fire HD 8 and HD 10 Original Android Development] nandpgtwsl:
Thanks @Kaijones23 for your work this ROM. I tried LOS20 for a month but found it to be very buggy and the sound so low. It crashed multiple times for some reasons. So, I reverted it back to stock. On the way back, I only got the Amazon logo, i.e., it no longer booted to twrp. I had to use "Another way to fix a brick" instructions (https://xdaforums.com/t/fire-hd-8-2018-only-unbrick-downgrade-unlock-root.3894256/) to do it. However, I used a 7.3.2.19 bin package instead of the one from the link. Then I manually debloated the Fire packages/OS updates/ads via adb; I guess it'd have been easier using the Fire Toolbox. All's well now for an old device. If the next ROM is less buggy, I'll have another go at it.
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
You could try more stable LineageOS 16.0, but I found YouTube to not work, LineageOS 15.1 had a unnecessary app "Lawnchair", but if you use Lawnchair, it's fine.

I personally now use LineageOS 14.1
[Fire HD 8 and HD 10 Original Android Development] mirek54:
I have a Fire HD 8 (2018) and have been using Lineage-16.0 https://xdaforums.com/t/rom-unlocked-karnak-lineage-16-0-04-june-2020.3981685/ for 2 years now. I would like to try this ROM. I have installed it from TWRP (wiped system, data and cache). Installation has gone without any error, but the device will not start. It shows the bare Amazon logo all the time. I have tried to install this 3 more times, but without success.

I'm back in Lineage-16.0, but what am I doing wrong?

I would like to get this working.
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
Update to amonet v3
[Fire HD 8 and HD 10 Original Android Development] mirek54:
Thanks for that, it does the trick
[Fire HD 8 and HD 10 Original Android Development] mirek54:
Location not working for me on this lineage.

Even though my location is on and I have given all the permission. The google maps app is not able to detect my location.

Is there any way to solve this?
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
I'm not sure if this device has GPS in the first place
[Fire HD 8 and HD 10 Original Android Development] mirek54:
That's understandable. But location could work over wifi i.e to use weather widget.
[Fire HD 8 and HD 10 Original Android Development] nandpgtwsl:
Thanks, that's good to know about LOS16 and 14. It's interesting that videos either on the app or in the browsers crashed my device LOS20. I was going to flash it to LOS16 when I lost twrp, so I flashed it back to stock.
[Fire HD 8 and HD 10 Original Android Development] Joester101:
The rom works fine but I can't get gapps or magisk to work, flashing either seems to do nothing.
[Fire HD 8 and HD 10 Original Android Development] Joester101:
lite gapps works nvm
[Fire HD 8 and HD 10 Original Android Development] mirek54:
Do you know when you will release android 14 Lineage?
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
He won't if you ask
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
This old device is getting more support from Kaijones23 than my much pricier Lenovo tablet. Now if only I could revive my old Motorola Xoom.

Has anyone attempted to use Termux on 20.0? I'm having trouble keeping the app active, but I'm not sure if it's due to the hardware, or if downgrading to an earlier version (like. 14.1) would solve the issue.
[Fire HD 8 and HD 10 Original Android Development] Kovaelin:
Are you using gapps? I noticed Google Play Services has increased their resource hunger in the past several months. L20 runs fine without it. I also managed to get performance back by using swap with Apps2SD.

I feel like people are forgetting that 1400MB of RAM is no small amount. We're all just becoming desensitized by people that abuse our machines and don't optimize anything anymore.

Heck, I still remember when Windows Phone was running apps with a third of the memory requirements for identical apps on Android and iOS.
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
Just downgrade to LineageOS 14.1, 15.1, or 16.0, all of them are stable, except LineageOS 14.1 camera freezing when you take a photo, or LineageOS 16.0 YouTube keeps crashing, or even LineageOS 15.1 with no bugs, but has a bloat app "Lawnchair"
[Fire HD 8 and HD 10 Original Android Development] eriklion:
is there a need to have selinux permissive and signed with a public key?

Also the 3.4 version of twrp isnt reading adb keys properly and mtp isnt working and USB mass storage option is missing too (3.3 crashes when you try and give the sdcard back to twrp)
[Fire HD 8 and HD 10 Original Android Development] Uusername:
will this work on a Amazon Fire HD 8 (2018) KFKAWI?
[Fire HD 8 and HD 10 Original Android Development] Fred's Androids:
Just follow this guide here
[Fire HD 8 and HD 10 Original Android Development] mirek54:
I accidentally got location to work. I have installed app Today Weather. You only need to start this once to find the location. Now the google maps app works correctly and other apps also find the location.

It is not necessary to have Today Weather active, it is enough just to start it once.
[Fire HD 8 and HD 10 Original Android Development] tsukeyomi:
Thanks for the clarification.

I’m seeing a couple of “almost done” in the posts above, so I wonder: is the interface currently too sluggish to use or is it working fine? Especially compared to the ugly stock rom.

I would try it myself but I still have to unlock my tablet with the shorting method. I’d rather flash this rom when it’s good to go for daily usage and without hiccups (which I’m sure it eventually will be) but I am unsure what’s the state now.