yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] gRooster:
The last two updates that I installed (the one from 03/16 and then 04/06) failed with error 7. It fails when trying to create "/cache/recovery/". Manually creating the directory in TWRP fixes it and allows it to update, but why is it it unable to create that directory itself? Is there something I can do to fix that?
[Fire HD 8 and HD 10 Original Android Development] Klenz39:
Thank you so much for the guide. It took me a while to try it. First time using magisk and terminal in android tablet. After much google and youtube, i managed to install all and including zygisk enabled. But it still didnt work properly. To make sure it is not a fluke, i did clean installation of the ROM and install magisk all over again but same problem occur.

I dont really think i need spoofing device for this app. It run with previous ROM, lineage 12.1 and 14.1 (without working video though). Has it happened before for an app that run in older ROM but need spoofing in newer ROM?
[Fire HD 8 and HD 10 Original Android Development] ggow:
Might need to just wipe /cache from TWRP.
[Fire HD 8 and HD 10 Original Android Development] ggow:
There is a definitely a problem here. Unity.Webview seems to be crashing due to reading from the audio HAL. Really not sure what's going on at the moment.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
I think I tried that when I had trouble with the 03/16 update and it did not help, but I cannot say for sure. In any case I will give it try next time if it happens again. Thank you.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
That would explain why blue iris freezes after a while. In HTML mode @ 720p full screen ill get pipeline error or video will freeze. In JavaScript mode, all works except going above 1080p. JavaScript however has a delay in live video playback but that is normal in blue iris which is why HTML5 is preferred.

When was the last time the device tree was updated?
[Fire HD 8 and HD 10 Original Android Development] ggow:
I don't think that explains the problem you have with blue iris. You will need to send logs so we can see what's happening.

Unity.WebView is an inherent component used internally by Unity applications for webview support. Is blue iris a Unity app?

The device repos are constantly been updated.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
To make sure i get the log right, reboot, replicate the issue by running blue iris till pipeline error, pull log, post?
[Fire HD 8 and HD 10 Original Android Development] ggow:
Yes, replicate the issue then use adb logcat and then post the log.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Just got a notification about the April 2022 update. Looks like I'm going to have to dust off the gal and get her a new outfit. Been meaning to tinker with it again anyways. This is still my favorite tablet next to my nexus 10. They just don't make them like they used to.
[Fire HD 8 and HD 10 Original Android Development] Tomatenjoghurt:
Just installed and was buffed at how good the performance was. Then I installed Magisk hide Props and noticed a huge performance loss. Is it possible that Magisk Hide Props has a negative impact on performance?
[Fire HD 8 and HD 10 Original Android Development] :
In what way did you lose performance? Did you notice general sluggishness eg. slow video playback or did you perform benchmarks?
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Did you enable zygisk and change signature to a tab 7?
[Fire HD 8 and HD 10 Original Android Development] Tomatenjoghurt:
Yep. Passing safetynet successfully! :)

Just felt sluggier after the installation. Sometimes apps, actions in launcher or in Firefox felt sluggy but somehow it feels better now after using it again for a while. Don't know. Will report if I come across it again. Just wanted to know if this could theoretically happen.

Otherwise great ROM, really gives life back to this beautiful old Tablet! :)

Some Minor things I came across: Gmail App crashed when opening but a reinstall seemed to have fixed that.

Firefox crashes occasionally when opening links in external apps and when the Firefox App moves to the background. But no big deal :)

Writing this from the tab right now! :D
[Fire HD 8 and HD 10 Original Android Development] german_psycho:
Dear @ggow. Thank you soooo much for this ROM.

Really gives my old Fire HD 10 a new life. At the current state - at least for me - it is useable as a daily driver.

The last few quirks will be sorted out over time, I am sure.

Thanks for the great work!
[Fire HD 8 and HD 10 Original Android Development] ggow:
Try just rebooting, I have proved this with a passmark benchmark tool. If you boot up and find it laggy, a quick run of the 2D Solid Vectors test scores between 3000 - 5000 Vectors/Sec

But if I reboot (usually on the first go after been laggy) that score goes up to the usual level of 11000+ Vectors/Sec

Don't know what the cause is yet, but it's on the list.
[Fire HD 8 and HD 10 Original Android Development] Tomatenjoghurt:
Awesome, thank you!
[Fire HD 8 and HD 10 Original Android Development] Klaus R:
Can confirm 0406 gives fennec sdcard access. Great, next updates are downloadable directely 🙂
[Fire HD 8 and HD 10 Original Android Development] dooderooni:
I'm on the latest build and find it excellent apart from some YouTube videos resizing. New Pipe doesn't seem to have the same issue.

The only consistent issue I've found is that a dirty flash always fails when creating the backup directory and I have to do a format and clean flash to update. It's not really an issue, but if anyone has any tips on dirty flashing it'd be nice to know.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Thanks for your great work again ggow!

Just a small report (used your updated twrp 3.6.1-9.0 and clean install of ROM Version 20220406 and open_gapps-arm64-9.0-pico-20220215, no magisk)

Testep apps like Brave Browser, Feedly and Prime (playstore versions) and Netflix and Disney+ (latest apkmirror.com bundle versions) which all worked fine.

Regarding the Bluetooth headphones it seems dependent on the headphones:

The Bluetooth headphones of my girlfriend - Soundcore Life Q30 - work fine.

My Motorola Verveloop+ Bluetooth headphones lead to the afore mentioned crashing loop of bluetooth again (fitting to their name 😆).

When i look into developer options under the Network/Bluetooth section, the Soundcore headphones are using AAC Codec, which seems fine. The Verveloop Headphones are using the Qualcomm Aptx HD-Audio Codec.

So maybe the crashing loop of these Bluetooth headphones has to do something with the aptx library?

It's minor to me as i use those headphones rarely anyway but maybe it's a hint for some errors🤔
[Fire HD 8 and HD 10 Original Android Development] ggow:
Cool, will take a look at the headphones issue. I might remove the aptx library so you can check it on the next update.
[Fire HD 8 and HD 10 Original Android Development] digbys:
when playing hevc videos over smb with vlc, after about 20-30min the video freezes and vlc can no longer play videos - just a black screen. have to do a reboot to play videos again. no sure if its related to the weird zoomed in 1080p videos in vanced.
[Fire HD 8 and HD 10 Original Android Development] ggow:
Will add this one to the list
[Fire HD 8 and HD 10 Original Android Development] Shack70:
I can confirm, having same issue.
[Fire HD 8 and HD 10 Original Android Development] computerworm:
Hi everyone, I have an Amazon Fire HD 10 2017, and I flashed the Lineage OS 16 20220406 image onto my device using TWRP after rooting and unlocking. But when I try to boot it, it shows the Amazon logo for a second, then goes to a screen with a blue downward curve with a blue-outlined circle traveling repeatedly to the left. It stays on this screen indefinitely until I hold the power button for several seconds to shut the tablet off. It appears that the device is soft-bricked. But I'm not sure how to fix it.

I unlocked it using this guide: https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-79169422 and I know that there are some form of unbricking instructions in that guide, but I'm not sure if they will work because they were designed for replacing/restoring the stock firmware, and I'm no longer on stock. Can someone please point me in the right direction?

EDIT: I was able to return to TWRP by holding the power and volume down buttons for several seconds, so I guess I'll try flashing the image again and see what happens, and if it still doesn't work, maybe I should try an previous build of Lineage 16?

FINAL UPDATE: I looked at the flashing directions again, and I realized that I had skipped the step where you wipe system data with TWRP before flashing. So I wiped system data, then tried flashing Lineage 16 20220406 for the second time, and it worked! :D
[Fire HD 8 and HD 10 Original Android Development] Shack70:
Just let it run. The first time Lineage (the blue downward curve) loads it takes a long time.
[Fire HD 8 and HD 10 Original Android Development] computerworm:
Thank you for your reply. :) I had expected that maybe it would take time, so the first time I booted I let it run for over an hour with no result, and then I tried rebooting again and again. In the end, I got the issue sorted - see my update above. :)
[Fire HD 8 and HD 10 Original Android Development] mhump711:
Connecting to a hidden SSID did not work. I even tried setting a static IP, that didn't work either. The SSID in question will prioritize 5Ghz then try 2.4Ghz. So I'm curios if I tried a 2.4Ghz only if it would work. I try testing this tomorrow. Otherwise, everything is very functional.

Thank you for all the time you put in.

Edit: a sentence didn't make sense
[Fire HD 8 and HD 10 Original Android Development] ggow:
Moved this back to the todo list
[Fire HD 8 and HD 10 Original Android Development] gRooster:
That sounds like the same issue I am having. A temp fix (after it fails) is to go to Advanced > Terminal (in TWRP) and type "mkdir /cache/recovery/" and then back out to the main page and try again. That seems to work for me. However it is only temporary (i.e. I have to do that every time). Have not found any permanent fix for it as of yet.
[Fire HD 8 and HD 10 Original Android Development] Pikatch:
Can I update my Amazon binaries to the latest FireOS 5.7.0.0 and specify vendor security patches in the next build?
[Fire HD 8 and HD 10 Original Android Development] ggow:
ℹ️ New Build is Up

Dated: 12 April 2022

- [kernel] Up-streamed to 3.18.140

- [kernel] Enable per user storage quota

- [kernel] Optimized build flags for Cortex-a53

- [kernel] Boeffla Wakelock Blocker Driver v1.1.0

- [kernel] Enable some TCP congestion algorithms

- [kernel] Westwood Default TCP congestion algorithm

- [kernel] Sdcardfs v2.0

- [info] Remove aptX bluetooth libraries for now

- [info] Mount /system partition early-mount style

- [info] Add vendor security patch
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
Progress has been amazing recently, thanks @ggow.

I only have a sample size of one so far but I will shortly try and confirm by testing a second unit: after flashing the latest build 20220412 the shell itself has suddenly developed a strange glitch. Whether using adb shell from a PC or opening the built in terminal app itself it will stop responding after a single key press event. Killing the terminal or the adb shell process and re-initializing either will show the same result.

This was initially noticed immediately post-install after flashing MagiskPropsHide so I could change the fingerprint to pass SafetyNet (obviously in this case, Magisk is installed which I understand you don't support). After starting adb shell from the PC and getting the prompt on the Suez I could only type the "s" of "su". Exactly the same result in the built in terminal app on the device itself. Any key send will do it: open the terminal or adb shell and hit return twice for example: the first will work, the second won't. Odd!

Fortunately "adb shell su -c props" from the PC seems to escape the glitch and allows you to interact with it and successfully change the fingerprint.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Same problem here on clean install without Magisk.
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
The same Suez started exhibiting other issues immediately - to be clear none of these can necessarily be attributed to the ROM itself as specifically against @ggow's advice Magisk and OpenGapps for the google stuff is an absolute requirement for my clients and I can't/won't disable it.

Rolling back to the previous build 20220406 and keeping Magisk enabled complete with various modules and the fingerprint change via MagiskHideProps immediately resolved the various app crashes and restored a working shell.
[Fire HD 8 and HD 10 Original Android Development] Shadow Death:
Edit: Whoops wrong thread. Either way got my tablet back up and going and am now flashing this rom. lol
[Fire HD 8 and HD 10 Original Android Development] ggow:
I'll look at the adb issue next.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
It is not just adb, it seems to be an issue with any terminal emulator. e.g. built in terminal, an emulator from the play store, and the terminal in Termux. It seems to not be able to read any input beyond a single character.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I understand that, I'll look into it. I used adb for a broad statement. It's definitely resulted from the up-streaming of the kernel and shouldn't be too hard to track down.
[Fire HD 8 and HD 10 Original Android Development] Klenz39:
Thank you for the update, still looking forward if you managed to fixed the unity webview problem. I encountered a weird behavior when i reading from pdf. Normally the screen will turned black and locked the screen but somehow it turned off the whole device and i need to turn it on again.
[Fire HD 8 and HD 10 Original Android Development] ggow:
Which

Which app were you using to view the pdf?
[Fire HD 8 and HD 10 Original Android Development] ggow:
ℹ️ New Build is Up

Dated: 13 April 2022

- [fixed] Terminal input via apps and adb shell
[Fire HD 8 and HD 10 Original Android Development] Klenz39:
Microsoft 365 (Office) - Apps on Google Play

Microsoft 365 is a productivity app with Copilot, Word, Excel, Powerpoint & PDF.

play.google.com

Used this one. Office app from microsoft. It happened twice but i am trying to make sure it happened again. No luck until now
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
Ok reporting back with my findings. Testing on a second unit and upgrading it to build 20220413 has indeed fixed the kernel regression and shells now work correctly again. Thanks @ggow.

Now this bit isn't for @ggow because once again, he specifically does not support this configuration. But for those running recent builds on the Suez with Magisk + OpenGapps it's possible (probable?) that they're suffering from the same sudden faults that have started occurring in the last couple of days as I've had multiple users report to me. The most critical symptom is gmail becoming completely unusable (crash on opening) but I'm seeing general instability in several apps.

I presumed in my last post this was another artefact of the 20220412 instance but as I've now confirmed this behaviour on the *06, *12 and *13 builds I think that can be ruled out. The workaround for gmail specifically crashing (and probably the other unstable apps although I haven't tested that much, gmail was the only mission critical one in my environment) is to disable the MagiskPropsHide module.

A few days ago I jumped the gun following someone else's advice to use MagiskPropsHide to change the device fingerprint to a Samsung Tab S7 and it worked so well I applied it to a whole bunch of Suezs. That has proven to be unwise and I've now disabled it again on all the effected devices so far. It did work great: for about 3 days. Now of course none of them pass SafetyNet but I couldn't care less about that.

Apologies @ggow for polluting your thread with Magisk/OpenGapps noise - nonsense like this is no doubt expressly why you don't support them. However unfortunately for a lot of us they're both hard requirements and so a certain amount of breakage and experimentation is the price we pay ¯\_(ツ)_/¯
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
After changing props to tab 7 and passing saftynet with magisk props hide, universal saftynet fix, and zygisk enabled, i have had no issue with gapps or google services. Gmail works properly as well and has worked without issue. Magisk installed without adding modules crashes gmail and google services. I do believe this to be a fingerprint issue. Remember, this is a fire tablet not supposed to have access to playstore apps.....
[Fire HD 8 and HD 10 Original Android Development] ggow:
ℹ️ New TWRP is Up

Version: 3.6.1-9.1

- [fixed] USB-OTG - needs testing

- [info] Last version is documented in the OP

- [request] Could someone report back whether USB-OTG is now working?
[Fire HD 8 and HD 10 Original Android Development] psi78:
Cool thing you implemented cortex-a53 optimization btw.

I'm wondering tho, why not full "big.LITTLE" cpu support for the mt8173 chipset with the flag ""cortex-a72.cortex-a53"?

But i guess since you use gcc 4.9 for the build, it isn't supported (as gcc 4.9 apparantly only supports the big.little flag "cortex-a57.cortex-a53").

Interesting there's a fix for a cortex a53 error in gcc 4.9.2 though: "As of GCC 4.9.2 a workaround for the ARM Cortex-A53 erratum 835769 has been added and can be enabled by giving the -mfix-cortex-a53-835769 option. Alternatively it can be enabled by default by configuring GCC with the --enable-fix-cortex-a53-835769 option." (https://gcc.gnu.org/gcc-4.9/changes.html)

PS: tested the new rom version without aptx, now my Motorola headphones work, using SBC codec🕺
[Fire HD 8 and HD 10 Original Android Development] gRooster:
The issue with flashing (dirty) the ROM appears to be an issue with BiTGApps. When flashing the ROM, BiTGApps appears to run it's own backup script that fails for whatever reason, and causes the install to fail and wipes out the "/cache/recovery/" directory entirely. Without BiTGApps installed it works normally. I am using Open GApps (pico) ATM and everything seems OK so far (including Magisk, HideProps, fingerprint change, etc)

Edit: update info. Open GApps (pico) is less stable than BiTGApps in the above environment, went back to BiTGApps.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I'm going to have rebuild this again. I just noticed USB is not working.

If you did flash the new version then:

- boot into lineage

- enable root

- copy the old recovery to your internal storage

- enter adb shell

- flash it with the following command

dd if=/sdcard/twrp_suez_3.6.1-9.0.img of=/dev/block/platform/soc/11230000.mmc/by-name/recovery_x
[Fire HD 8 and HD 10 Original Android Development] rG-:
@ggow let me buy you a beer man (bitcoin lightning, paypal or similar?) - thanks for the work!
[Fire HD 8 and HD 10 Original Android Development] KingLeaf:
Is it possible to add an battery idle mode (no charging while plugged in)?

Screenshot from AccA shows this isn't currently supported in the kernel, is it possible or is it a device limitation?
[Fire HD 8 and HD 10 Original Android Development] ggow:
It should be possible, looks like a good feature. I'll add it to the list.
[Fire HD 8 and HD 10 Original Android Development] ybroker:
Can not get Magisk installed. Please kindly provide more tips on what version Magisk is needed and how to install it. Thanks.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
I have used 24.1 and 24.3. To install, boot to recovery and flash the Magisk zip file (if you have the apk, but not zip, just rename the .apk to .zip)
[Fire HD 8 and HD 10 Original Android Development] ybroker:
I done that but got the device enter a bootloop. Thanks for the quick reply.
[Fire HD 8 and HD 10 Original Android Development] da_angelboy:
I'm actually encountering the same issue as well. I just tried to install Magisk and now i'm stuck in a bootloop. For now, I've uninstalled Magisk to get into Lineage
[Fire HD 8 and HD 10 Original Android Development] psi78:
I'm in for that too👍🏻🍻
[Fire HD 8 and HD 10 Original Android Development] ybroker:
flashed back to TWRP 3.6.1-9.0, now is good.
[Fire HD 8 and HD 10 Original Android Development] ybroker:
Is OTG USB for ethernet enabled by default? version 20220406 is working but not version 20220413 though. Thanks.
[Fire HD 8 and HD 10 Original Android Development] ggow:
It's likely an upstream kernel regression, will add it to the list.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
@ggow

Im unable to reproduce the pipeline error in the latest build 😍

Im kinda curious, is there a way to implement offline charging? As in when the tablet is off, can be charged while still off instead of it turning in to charge?
[Fire HD 8 and HD 10 Original Android Development] ggow:
I'll add the offline charging to the todo list
[Fire HD 8 and HD 10 Original Android Development] Pikatch:
It's a long-standing problem, but the network connection is unstable. After restarting and running the Google speed test, the download speed is 1.8 Mbps and the upload speed is 9.5 Mbps. Can you improve it?
[Fire HD 8 and HD 10 Original Android Development] Sesquipedality:
This is a really great ROM and a good way to make a Fire HD actually useful. Thanks.

When I install magisk, it complains about an "Abnormal State" and says an su binary not from Magisk has been detected. What is the right way to fix this, please?
[Fire HD 8 and HD 10 Original Android Development] psi78:
For anyone wanting to optimize the battery and idle runtime of suez, i did the following:

Activated energy saving mode and data saving mode, and deactivating location and synchronisation (i at least don't need these for a media tablet usage style).

Also installed the app naptime (needs permissions granted per adb, or root), with aggressive doze mode.

Now over a course of 12 hours not using the tablet in flight mode, the battery percentage just goes down like 0 or 1%. Apps like devcheck then showing a high percentage of the cpu being in deep sleep mode.

For on-screen usage, dark display theme and pitch black wallpaper app are also helpful to reduce battery consumption.

Also i noted, it isn't a good idea to deactivate too many system apps (which i deemed unnecessary - ha, those warnings seem there to be for a reason 😆), because the idle cpu usage went up high in some cases of deactivating system apps. So in the end i left them alone.

Performance of suez with this rom is way better than that of Fire HD 2019 with stock rom and Playstore btw.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Goto developer options and turn off root access there. Then flash magisk. The rom comes with su already added in development options, it needs to be turned off before magisk will install properly, magisk should remove su during install.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
I found when the cpu wont idle down, shut device off then back on corrects the issue. A simple reboot doesn't quit do the job. Mske sure its unplugged during the power reboot.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I don't want to play with this too much at the moment, the variety of routers makes this difficult to pin down.