yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
I did a dirty flash from the previous version, with pico gapps, to the July 5th version without wiping anything and I had zero issues.

I then made a backup, I always make backups of known good setup's, wiped system, dalvik, and cache. Installed July 5th rom, reboot back into recovery and attempted to flash pico gapps which failed like others have said. I then attempted to flash BiTGApps (BiTGApps-arm64-9.0.0-R45_signed) and it flashed no issues.

I am guessing we are still having the issue with 2 of the cores being pegged at 100%? Is there anything specific you would like tested?

Edit -

I forgot to install Magisk so I downloaded the newest apk version from the official github, renamed it to .zip and flashed it via recovery. I didn't not perform any kind of wipe and instead attempted to reboot the system. This resulted in a boot loop. Rebooting back into recovery and perform a dalvik cache wipe only and that resolved my bootloop issue. This resulted in the app not being installed after flashing via recovery, after installing manually The app is reporting that Magisk IS NOT installed. Reboot back into recovery, flash the .zip again this time wiping cache and dalvik after the flash resulted in another bootloop. Back to recovery one last time to wipe cache and dalvik again, fixed bootloop but the Magisk app still reports Magisk isn't installed. It was at this point that I remembered the newest version of TWRP for some reason has issues installing Magisk. Downgrading my twrp version, flashing Magisk, then flashing back to the newest TWRP worked fine.

So to sum up -

- Dirty Wipe from previous version with pico gapps installs fine with no errors due to size

- Fresh Install (wiped system, data, cache, dalvik) July 5th rom then attempting to flash pico gapps results in error due to not enough free space

- Fresh Install (wiped system, data, cache, dalvik) July 5th rom then flashing BiTGApps (BiTGApps-arm64-9.0.0-R45_signed) works fine with no errors due to size.

- Flashing Magisk via recovery with newest recovery image (twrp_suez_3.6.1-9.2) results in Magisk not actually being installed (it reports no errors when flashing in recovery). Have to flash twrp_suez_3.6.1-9.0 in order for Magisk to be properly installed. (checked root with root check and Magisk superuser is working fine)

- Initial testing (htop via terminal) still shows at least 2 cores pegged at 100% usage with them sometimes dropping but then going back to 100%
[Fire HD 8 and HD 10 Original Android Development] gRooster:
For the heck of it, I tried resizing the /system (expanding) and /userdata (shrinking by same amount) partitions and it seems to have worked for me. My tablet is a 32GB version, so I figured i had some room in /userdata to spare, but I only added a few hundred MB (was not sure what size would be optimal).

Before changes TWRP showed /system size as 1557MB with 216MB free, and now shows 1936MB with 595MB free. (parted binary showed 1693MB before and 2097MB after). Also using TWRP backup and restore options I was able to do this without losing any data (I was able to boot right back into LOS as it was previously). My partition table has /cache, /userdata, /boot, and /recovery after /system, so I was not sure I could do it without messing with the boot and recovery partitions (which is a little scarier if I ran into trouble) but I did not have to touch them. I just deleted /system, /cache, and /userdata, then recreated /system at new size, recreated /cache using same size but moving to new position following /system, and then created /userdata using remaining sectors between /cache and /boot.

I used the info from here to attempt this.

I used a size of 4096000 sectors (was going for 2000 MB x 2048) for /system thinking it would give me approx 307MB extra space.

Note: I did a full backup in TWRP before starting, as well as another backup of just /system, /cache, and /data, but only needed the second. I also renamed /data/media/ (to mediabak) so that TWRP would include internal storage in the backups and of course renamed it back after restoring from backup.

I also printed out the partition table with sector start and end points before starting so I could use them as reference and to have original values to revert to if I ever need to.

In any case, just figured I would share this in case anyone else wants to try and do the same.

Edit: correction, deleted /userdata not /recovery

Note: While I do not expect to have any issues I have not yet tried to flash the latest LOS release yet (nor anything else for that matter), so I cannot say for sure that resizing the partitions will not cause any issue there.
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
I have inserted a screenshot of htop showing cpu% of a few processes over 100%, doing a shutdown and turn on seems to get rid of the cpu pegged at 100% issue and the few processes that were showing over 100% cpu are not anymore.

Its been a while since I have done any kind of in-depth diag of a Linux system, but am I seeing correctly that in the first attached image it says my uptime is 1 hr 19 minutes but the top 2 system_server processes and the system/bin/surfaceflinger process show WAY MORE then 1 hr 19 minutes of run time?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
@ggow A different (and more reasonable) approach to gain some space in /system is to exclude extraneous fonts from the /system partition. Alternatively, you can also exclude unnecessary apps with RemovePackages.​
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Ran into some weirdness today with the resizing partitions stuff. Decided to flash (dirty) the latest LOS release and that went OK, but checked size in TWRP and it now shows the size as 1589MB, which is different from both before and after sizes that I got yesterday. Checked with parted binary and although it shows same size as yesterday (after resizing) it now shows the fs-type as ext2 instead of ext4. However TWRP and mount and other tools show it as ext4, so not sure what is up with that. Tried a clean install as well with the same results. Anyway, restored my backup and reflashed (dirty) the LOS update (same results) and aside from the above, everything seems OK.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
thats the problem I had when I tried I don't remember what the issue was I think amonet might be fiddling with the gpt definition
[Fire HD 8 and HD 10 Original Android Development] Shack70:
I'm having issues with Magisk. It won't install again, we had a similar problem with an older build.
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
I am going to assume you are on twrp_suez_3.6.1-9.2 and are attempting to flash using the .zip file via recovery. If so first you need to downgrade to twrp_suez_3.6.1-9.0, flash the .zip file via recovery, boot into the system and make sure that magisk is installed and root works properly, then you can reboot back into recovery and flash back to twrp_suez_3.6.1-9.2.

I had the same issue and I documented how I resolved it (what i told you to do) in my previous post from yesterday
[Fire HD 8 and HD 10 Original Android Development] Shack70:
Thank you, I must have missed your post. Appreciate the help!
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
In twrp, click install, click your LOS then click add more zips then click gapps then slide to flash.
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
I am using the tablet as a “daily driver” for

Music streaming while at work and I am using my phone’s hotspot for a wireless connection. I am having an issue where when the tablet goes to sleep it drops the connection to my hotspot. I know this because Spotify stops playing music and I have to reconnect to my hotspot when I unlock the tablet. I checked the wifi sleep policy in terminal by typing “settings list global” (in an elevated terminal) and it shows wifi_sleep_policy=2 which is the correct selection for having wifi not turn off when the screen goes to sleep. Is anyone else having this issue? I will check later when I get home to be 100% sure it isn’t just something weird with my hotspot.

Edit -

Ok so it may very well be my phones hotspot that is causing the issue because it just dropped connection without the tablet going to sleep, but I am still going to check with my home internet just to be sure
[Fire HD 8 and HD 10 Original Android Development] dasbooter:
Is this "THE" ROM to install now?

I'm still on lineage 12.1 unofficial Suez.

Whenever I pick up this tablet I say to myself this is a nice convenient device but quickly that goes away BC now I can't install most of the apps I need.

Hoping for intact Netflix, Bluetooth audio, video in general. Could maybe give up camera.

Can jump through hoops if need be. Had the original Google phone which ran out of system space but I could repartition the memory using black rose to keep it going.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
widevine L1 still isn't working so netflix is limited to 720p

hardware acceleration is still a bit dodgy

there are performance issues yet

its wip

tbh suez is pretty dead ggow is the only one working on it
[Fire HD 8 and HD 10 Original Android Development] Nosepull:
Depemding on your needs still a solid tablet with this ROM, IMHO.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
didn't say it wasn't but he specified he was going to be using audio/and video which both still have some issues I use mine to monitor my wyze cameras and for unified remote
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
agree, I use mine for Blue Iris therefore 12.1 works best for me, Gapps pico, Magisk and SafetyNet pass, no issues whatsoever.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Someone else mentioned that the 12.1 release was the best. Perhaps you are onto something.

Joking aside, lets all install windows Vista!

I think I saw someone on another thread asking questions about trying to get 12.1 updated.. do people even do that? Spend time bringing an old release up to standard? I have 4 of these tablets and have 3 spares for a car project of mine, so I am on the lookout for a slim distro that works with my app without any fuss.

I'm up for testing whatever since I have some spares.
[Fire HD 8 and HD 10 Original Android Development] terry98:
I have managed to install this rom with gapps after a couple of hours tinkering and even with no L1 support and other stuff I prefer this over stock FireOs, thanks for the great work.
[Fire HD 8 and HD 10 Original Android Development] azrel:
Is there a walkthrough for installing this rom?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Hi there,

1) You will need to find a suitable root method for the tablet.

so far there is the MTK-SU package, if that works for you, great!

A) https://xdaforums.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/

If that doesn't work for you *It didn't for me, you will need to use the other root method here.

B) https://github.com/3ch01c/3ch01c.gi...-to-setup-amazon-fire-hd10.md#root-the-tablet

I have used the B one and it works great.

2) The rest of the guides available will show you how to install TWRP and then a rom. Unfortunately I can't locate the guide on the how to install after you have gotten root.

At this point I don't know if there is a super comprehensive guide available... you just kind of have to piece meal it together and make it work.

The general jist of it is.

Root tablet, Install TWRP, then sideload or sd card load a rom. The TEMP root is just that temp, once you have temp root you can do the rest of the steps. Don't assume that when you get root it sticks around . I had an issue where after the option B above I restarted the tablet and I was not able to run the exploit again, so you have to factory reset the amazon tablet and try rooting again with option B.

Hope that helps and gives you some ideas on the process. Perhaps someone else can contribute to help you out.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
Unlock bootloader, install twrp

flash rom

flash magisk and gapps if desired
[Fire HD 8 and HD 10 Original Android Development] Shack70:
https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/ is a good guide/ process for getting everything setup to install the rom. Make sure you read it thoroughly before jumping into actually doing it. It requires a PC and Linux. For Linux you can you can use a portable version of Linux off a USB thumb drive.
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Just picked up one of these devices through a deal at woot... Some notes:

(1) I had to open it up and do the "short CLK to ground" thing to get twrp and the tweaked bootloader on there. As far as I can tell none of the software-only root methods work with the latest stock firmware.

(2) After getting twrp on there, the system partition was too small to fit either this lineage16 ROM or the older lineage14 ROM with their accompanying pico opengapps package. I ended up sideloading a parted binary and editing the partition table by hand to get a larger system partition.

(3) If you manually enlarge your system partition like that, after you flash the ROM you need to use the Resize function (under Wipe/Repair) to resize the newly flashed system partition so it takes up the full size of your larger system partition, rather than the smaller size in the image. After the resize you need to either reboot or go in the Mount tab and mount and unmount the newly resized system partition so the recovery recognizes it's been resized properly.

(4) Once all this is done...

(a) I had a *lot* of wifi connectivity problems with the lineage16 ROM. Anyone have any suggestions on what I could try tweaking, either tablet side or router side? I actually tried cloning the lineage16 source code to mess around with but some of the externals in it seem to be broken at the moment...

(b) With the lineage14 ROM wifi is 100% solid but the Gmail app can't see Gmail accounts I have configured into the system... Even though they're actually being synced and I'm getting notifications when there's new Email in them... I can't actually VIEW those Emails...
[Fire HD 8 and HD 10 Original Android Development] ken2802:
I have a fire HD 8 from 2020. Will this Rom work?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
The thread title explicitly says suez, which is the codename of the Amazon Fire HD10 2017, so no, it won't work with your device.​
[Fire HD 8 and HD 10 Original Android Development] ken2802:
Can you link to one which Will work with it
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
None of them will work, because you have to unlock the tablet and in your case, that's not even possible (since there is no unlock method for the 2020 version).​
[Fire HD 8 and HD 10 Original Android Development] puffdank:
Pretty sure I picked up a nice lot of them from the same sale on Woot!, for some reason they priced the Blue/Black 64gb ones at $45, but if you selected the Red 64gb variant the price dropped to only $20. I got 10 of them for family and friends. Mine seem to all have FireOS 5.6.9.0 and after a few failed attempts using the available soft-root methods, I was able to get this one to work.

I am unable to install LOS 16 though, due to the system partition sizing, and don't really have any experience with using Parted or any other command line partition methods. Would you please share even just a brief step series on how you were able to resize the system partition so that it would allow you to flash LOS 16, then use the "TWRP resize" option to make the necessary room to go back and flash GApps and Magisk?
[Fire HD 8 and HD 10 Original Android Development] Kate6:
I don't know that I'd recommend monkeying with the partitions if aren't reasonably comfortable with command line tools in general... And just to say again - I'm not actually running Lineage 16. WiFi was entirely too unstable for me with the July 5th Lineage 16 ROM... So I'm actually running Lineage 14 on mine for now.

But basically, what I did was -

Grabbed the parted binary from https://github.com/edk2-porting/parted-android

Booted into twrp, adb pushed the parted binary to /tmp, chmod a+x'ed it

"unit b" tells parted to display partition start/end/size down to the byte

remove the system, cache and data partitions... I wanna say they were partitions 12, 13 and 14? Something like that. Been a week or so since I did it. (Looks like it's actually 13, 14 and 15 now that I grabbed the actual tablet to make the screenshot I attached below...)

Recreate system, cache and data so that they have the same partition numbers they did previously but with their sizes adjusted... Basically this means figure out how much you wanna increase the size of "system" by and then add that same number to the end sector of system, to both the start and end sectors of the new cache and to the start sector of the new data partition... Keeping the start sector of system and the end sector of data the same as they were before the modification.

Make sure you rename your newly created partitions to system, cache and userdata to match their original names...

Basically, when you're done, you want the output of parted's "print" command to look exactly the same as at the start except for the "end" number of system, the "start" and "end" numbers of cache and the "start" number of data.

After that you need to get the kernel to register the new partition table... The simplest way to do that is probably just to reboot the recovery.

Now the system partition image that comes with the ROM is an image for a system partition of the original size... After flashing the image you want to use this to adjust the flashed filesystem to take up the full size of the partition. The Wipe -> Advanced Wipe -> (select System) Repair or Change Filesystem -> Resize File System option in the twrp UI appears to run resize2fs for you, if you'd prefer not to do it yourself from the adb shell.

Here's a screenshot showing the "end result"... This is what my suez' partition table currently looks like. Notice the size of my system partition is 3093299200... The original size of system was 1692925952.
[Fire HD 8 and HD 10 Original Android Development] puffdank:
Wow, thank you, very much APPRECIATED! :)
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Feel free to ask more questions... I realize I skimped on some of the very specific details... But don't blame me if you end up bricking your device.

Though I guess if you have 10 of em' and you only paid $20 for each, probably not that big a deal if you brick one?
[Fire HD 8 and HD 10 Original Android Development] psi78:
Did you have heat problems on this ROM and unstable Wifi? The tablet feels really hot on the back in that case. If so enable Power Saving/Extreme Power Saver mode, should cool it down more.
[Fire HD 8 and HD 10 Original Android Development] Kate6:
I can't say the tablet at any point felt physically hot to the touch, but I still went ahead and tested your theory. In addition to turning on Extreme Power Saver, I also left the tablet sitting on top of my air conditioner's exhaust vent for a nice long while, so that when I picked it up the chassis felt genuinely cool to the touch.

I also tried using a kernel tweaker app to underclock the CPU.

WiFi was still considerably less reliable in the July 5th build of the Lineage 16 ROM from this thread than in the Lineage 14 ROM I've been using. Which is this one, to be specific.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Mm alright. So it isn't the cpu thing.

Are you using 2.4 or 5 GHz Wlan?

Here someone already reported WLAN/packet loss problems with this suez LOS16 ROM on 5GHz WLAN:

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/page-11#post-86443363

I use 2.4 GHz WLAN (fritz!box Modem/german DSL) and it works fine for me.

https://www.speedtest.net/ showing stable 50Mbps downstream/10 Mbps upstream which is my DSL speed.

https://packetlosstest.com tests are reporting zero packet losses when i use suez with this LOS16 ROM.

So maybe 5GHz Wlan is bugged, @ggow what do you think?

@Kate6:

With Smartpack Kernel Manager you could also try out other settings for TCP but probably won't help much if it's a driver issue.

Or send a logcat/dmesg to ggow also.
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Tried with both 2.4 GHz and 5 GHz. And tried both on two separate routers... A Netgear R7000 and a Linksys WRT1200AC. Both running the August 03 2022 build of DDWRT. Similar instability problems with all combos.

I'm probably going to do that, but I'm thinking I want to set it up so it's just the ROM with no apps whatsoever (including no gapps) installed so the logcat will be as clean as possible. Should be able to get that done in the next few days.

... Or really, ggow's signature clearly says he won't answer questions over PM, so my plan was to post a logcat to this thread.
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Alright I sat down and captured a logcat...

This is just the lineage-16.0-20220705-UNOFFICIAL-suez.zip ROM installed. No gapps, no apps. The only things I tweaked was turning on developer mode for ADB access and gave it the passport to one of my 2.4 GHz access points (since you guys seem to say it's stable with 2.4 GHz for you)...

I let it make several attempts at connecting. At one point the list of SSID's it was seeing went blank so I toggled the wifi off and back on again, then let it try some more...

Edit: xda doesn't seem to want to let me attach the file to this post, so here it is as a gist...
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Sorry where do you see IPv6 related stuff? All I'm seeing is failed ANQP queries.

None of the MAC addresses on the failed ANQP queries appear to be in my router's ARP table though. My router's OUI prefix is C0:56:27 (Belkin) and the tablet's of course is cc:f7:35 (Amazon)...
[Fire HD 8 and HD 10 Original Android Development] Kate6:
Okay they appear to be the SSID's of neighbors' routers.

root@sidra:~# nmcli d wifi list
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
14:CC:20:D1:DC:AC TheJellyFox-2.4GHz Infra 6 195 Mbit/s 100 **** WPA2
C0:56:27:76:27:9A RoyCircles-2.4GHz Infra 9 130 Mbit/s 100 **** WPA2 WPA3 <---- My router
78:23:AE:85:AD:E3 Radish Infra 6 195 Mbit/s 92 **** WPA2
7A:23:AE:85:AD:E3 -- Infra 6 195 Mbit/s 90 **** WPA1 WPA2
0E:C0:3E:35:E8:09 -- Infra 11 130 Mbit/s 89 **** WPA2
AE:4C:A5:B6:EA:31 -- Infra 11 260 Mbit/s 87 **** WPA2 802.1X <--- failed ANQP query
AC:4C:A5:B5:EA:34 Sassypants House Infra 11 260 Mbit/s 85 **** WPA2 <---- failed ANQP query
AE:4C:A5:B6:EA:35 -- Infra 11 260 Mbit/s 85 **** WPA2 WPA3 <----- failed ANQP query
[Fire HD 8 and HD 10 Original Android Development] psi78:
yeah, right, my bad, thought at first glance those : separated numbers where ipv6 adresses. But like you found out, they were are mac addresses/BSSIDs of WLAn routers.

Well this ROM already had problems with hidden SSIDs in the past, but not sure if that's related to your problem.

But weird if other Wlan networks lead to such problems with potential out of memory error for the Wlan driver ("wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private commands, error msg: Out of memory")

Didn't see errors like that in my logcat yet🤔, but in Germany on the other hand other Wlan DSL routers are common, the fritz!box is widely used and some Telekom routers.

Well, i'd say go to the utmost and tell your neighbours to throw out their hardware pieces of crap😆