yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] psi78:
Hmm. So did you wipe all partitions (wipe Dalvik/art cache, cache, system, data, internal storage), or better even format data partition with twrp before flashing the rom with twrp?

And also do a reboot into recovery/twrp after formatting the partitions / before you install the rom image with twrp. That way it always worked for me.

Not sure about installing the rom by adb. You'd probably have to do a reboot into recovery at some point to clear stale mounts if you get mount errors.

This guy had a similar issue btw: https://xdaforums.com/t/rom-testing-suez-lineage-16-0-13-apr-2022.4232785/post-86724039
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Hey, as long as its working, but, the instructions say if your on the latest fire os to downgrade then proceed.

You may however want to run a virus and malware scan on that tablet and on pc or wherever you used kingo.

How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more

Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.

www.xda-developers.com
[Fire HD 8 and HD 10 Original Android Development] ggow:
Not possible to upgrade OpenGL without updated blobs kernel drivers etc from amazon/mediatek.

Vulkan drivers are not provided either. ANGLE abstraction would require blob/ROM support which there is none provided.

Graphics glitches are something I'm looking at.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Don't know if this may be of any help, there's an opengl es 3.X conformity test suite availabe for building, and instructions regarding that:

OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions

Source code is here i think: https://github.com/KhronosGroup/VK-GL-CTS/releases/tag/opengl-es-cts-3.2.8.0

Or is it of any use to turn on System tracing in developer options to get more info?
[Fire HD 8 and HD 10 Original Android Development] psi78:
Brave Browser worked for me when playing YouTube Videos.
[Fire HD 8 and HD 10 Original Android Development] Klaus R:
Videos getting zoomed in with fennec/Firefox, zattoo (german TV). Running 0413,no magisk, no gapps
[Fire HD 8 and HD 10 Original Android Development] psi78:
Just read that Imagination Tech released an early open source vulkan driver, they use Acer Chromebook R13 with mt8173 and PowerVR GX6250 as a development base.

See this post: https://lists.freedesktop.org/archives/mesa-dev/2022-March/225699.html

on https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15243 it says "The driver is only currently capable of rendering the Sascha Willems triangle example on a GX6250 and a lot of functions are either only partially implemented or not implemented at all. However, we hope to fill out this missing functionality over the next few months before moving on to passing all the conformance tests."

Also kernel sources and firmware for the PowerVR driver linked there, for kernel 5.16 though.

I don't know much about kernel/driver building, but maybe in the future this could be a base for updating drivers for suez/mediatek/powervr devices too?

Edit: Since archlinux apparently supports Acer chromebook R13 and a tablet pc mode, now i'm wondering if it would be possible in any way to get that running on suez🤔😆

See https://archlinuxarm.org/platforms/armv8/mediatek/acer-chromebook-r13

and

Tablet PC - ArchWiki

wiki.archlinux.org

But ok, that's something else entirely

Edit: archlinux kernel sources are here, maybe also of interest in fixing errors for suez

GitHub - archlinux/linux: Arch Linux kernel sources, with patches (Mirror)

Arch Linux kernel sources, with patches (Mirror). Contribute to archlinux/linux development by creating an account on GitHub.

github.com
[Fire HD 8 and HD 10 Original Android Development] psi78:
Xiaomi Mi Pad 3/ cappu sources are on the web btw too. 3.x kernel. Latest MIUI 9/Android 7 Rom for Mi Pad 3 supports Open GL ES 3.2 for PowerVR GX 6250 and has similar chipset to suez: MT8176 with big.little cpu's A53 and A72:

GitHub - MiCode/Xiaomi_Kernel_OpenSource at cappu-n-oss

Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.

github.com
[Fire HD 8 and HD 10 Original Android Development] psi78:
Regarding the benchmarks i get errors like in the attached image of matlog

about those FrameEvent errors there's also a post here:

FrameEvents: updateAcquireFence: Did not find frame

I recently started seeing this message in Android Studio’s Logcat while running my app, and I’m not sure what is causing it or how to resolve it. Googling has failed me. E/FrameEvents: updateAcquir...

stackoverflow.com

also a bad file descriptor error of IMGSRV
[Fire HD 8 and HD 10 Original Android Development] ggow:
ℹ️ New Build is Up

06 May 2022

- [fixed] Voice assist MIC not working

- [fixed] USB-OTG Ethernet

- [fixed] TWRP: MTP access

- [fixed] TWRP: Fixed USB-OTG

- [info] Added android.hardware.opengles.aep.xml permissions
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Regarding the issue with dirty flashing with BiTGApps, for this latest update I just deleted the BiTGApps ota-survival scripts and then dirty flashed the new ROM and BiTGApps.

I.e.

In LOS, I deleted the 3 BiTGApps scripts. (backup.sh, bitgapps.sh, and restore.sh) in "/system/addon.d/"

Rebooted to recovery, and flashed both the ROM and BiTGApps and did not have any problems.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Great work again.

Tried the new build with bitgapps microg, that worked. For example netflix,disney, gwent (checks for playstore Installation and aep) possible to install and run.

Only thing that popped up is: new twrp Version 3.6.1-9.2 led to bootloop of LineageOS after installing magisk. Can someone else confirm this?

Installing magisk with the new Rom was possible again after reverting back to twrp 3.6.1-9.0, LineageOS boots normally again then.
[Fire HD 8 and HD 10 Original Android Development] :
Can also confirm it bootlooped after updating TWRP and then LOS.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I'll look into this.
[Fire HD 8 and HD 10 Original Android Development] ggow:
I have just updated

I just updated to lineage-16.0-20220506-UNOFFICIAL-suez from the previous build using thenew TWRP and it seem to work fine for me. I only flashed the ROM.

I previous had open_gapps-arm64-9.0-pico-20220215 installed which was preserved.
[Fire HD 8 and HD 10 Original Android Development] ggow:
If you previously had magisk and/or gapps installed you should just be able to dirty flash just the ROM and they should be preserved.
[Fire HD 8 and HD 10 Original Android Development] :
I think the problem might be Magisk’s survival script which immediately reinstalls itself after you flash any ROM update. I think the new TWRP doesn’t install it properly leading to a bootloop.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
I can confirm.

No problems until installing Magisk, then bootloop (does not get past Amazon logo before rebooting). To be clear, Magisk was not installed previously.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
This does not work with BiTGApps. Something with BiTGApps survival script causes a dirty flash to fail, and after failing the system will no longer boot (hangs forever on LOS boot screen).

Removing the survival scripts before flashing works, but it seems something from BiTGApps gets overwritten (and obviously not restored without the survival script), as once in LOS, all Google services keep crashing. Re-flashing BiTGApps fixes this.
[Fire HD 8 and HD 10 Original Android Development] ggow:
Yeah, BiTGApps looks broken. OpenGapps is working fine.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
If you install magisk you have to change the devices fingerprint and pass safety net before any of those apps will work
[Fire HD 8 and HD 10 Original Android Development] domce106:
I will post my experience as well. Most of them are somewhat repeats of previous bugs people have already mentioned. I mostly only watch videos/streams on my Fire, so these will the problems I will state.

Bad video performance after reboot. On first powerup 2D video performance is bad (checked by video performance and "PerformanceTest mobile" app benchmark scores). After reboot, it becomes normal (both video performance and benchmarks).

After another reboot it reverts back to being bad. This good-bad perfomance loop keeps repeating when doing reboots.

Video zoom. For me, the video zooms in only when going from lower to higher quality. Going back to lower quality reverts zoom to normal. It does not matter what resolution changes. 240p->360p works the same as 720p->1080p.

Also, it doesn't happen on every stream/video. It doesn't happen on NewPipe or youtube via Brave browser. It does happen for some generic streams via Brave browser, lrt.lt app (my country news tv) and F1 TV app. This is only as many as I have tried.

I guess I should try changing resolution from 4k to 1080p, but I can't find a stream like that.

Video stutter. 720p video works on every video I tried. 1080p stutters very badly on NewPipe. I then ran the same video as newpipe on youtube via Brave browser and it works perfectly fine on 1080p -- no stutter. I also downloaded the video via NewPipe and ran it from storage with VLC. It also had no stutter.

Streaming on other apps and on Brave seem to work fine at 1080p, but it might be a "fake" fine, because the video is always zoomed in.

Video crashes repeatedly. Streaming in Brave and F1 TV just crashes after about 10 minutes of watching. If I force stop the app, streaming comes back on, but crashes some time after. After a few crashes, even force stopping the app doesn't help and tablet needs a reboot.

Other than this, everything seems to be working amazingly. Thank you for chugging out updates!
[Fire HD 8 and HD 10 Original Android Development] lutz51:
Confirm, too. I'm not using GApps, just microG.

To leave bootloop:

- Entering twrp

- Installing twrp 3.6.1-9.0

- boot System

- Testing magisk (on my system it doesn't work properly)

- Reboot into twrp

- Install Magisk

- boot system

After that procedure, I've installed twrp 3.6.1-9.2 and everything seems still working
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Yeah, I will probably switch to OpenGapps. I had tried it and had some overheating issues, so I switched back to BiTGApps to see if it it made any difference, but the problem persists.
[Fire HD 8 and HD 10 Original Android Development] Xavras:
twrp 3.6.1-9.2 USB-OTG not working for me :( sorry - simple otg cable + 4GBUSB stick (ancient), formatted as FAT16. same setup worked just fine with twrp 3.2 (didn't reformat since). let me know pls if you need any further tests/data/logs
[Fire HD 8 and HD 10 Original Android Development] psi78:
For everyone having overheat or performance issues mind that what MarvinMod and ggow already mentioned in previous posts:

After a reboot of this rom cpu usage is high even when idle (maybe because of a kernel process).

You can check for yourself (with an app like DevCheck, Simple System Monitor, CPU Info, CPU stats) after a reboot, watch cpu usage and compare it to cpu usage after a power off/power on restart of LOS.

So after you've done all the installing don't do reboots anymore, use power on/off or flight mode

Edit: That was reproducable for me with a previous install and gapps at least.

Don't have a full install yet, just the latest version 20220506 of the Rom, previous twrp 3.6.1-9.0, magisk and fdroid, no gapps. Doesn't occur with this setup. Could someone test this with gapps or microg setup?

Edit2: OK, it's weird, played around with settings a bit, deactivating and activating energy saving mode and doing power on/off restarts and reboots in both modes, now i get the high idle CPU usage even after a power on ( and energy saving mode deactivated), and sometimes after a reboot CPU idle usage is alright. Looks similar to that what domce106 reported, just that i didn't play any Videos.
[Fire HD 8 and HD 10 Original Android Development] psi78:
I did some more testing: ROM 20220506, twrp 3.6.1-9.0, fdroid and CPU Info (no gapps, no magisk)

With this i could reproduce high idle cpu usage of CPU cores 2 and 3 and high idle cpu temperatures of 80 degrees Celsius and above. Sometimes when doing a cold boot, sometimes with a reboot. Sometimes after reboot the system was alright though and CPU cores 2 and 3 powered down and CPU temperature was like between 40 and 50 degrees Celsius.

I couldn't reproduce this in Power Saving mode (turn on in quick settings) though (yet?).

So @domce106 and @gRooster can you turn on Power Ssaving mode, do a cold boot or reboot and look with Devcheck (playstore) or cpu info (fdroid) if your cpu cores power down after like 30 secs after startup and your media playing performance is better?

@ggow not sure but could this have something to do with the gcc a53 tuning options? A test build without the optimizations maybe would be interesting
[Fire HD 8 and HD 10 Original Android Development] ggow:
Unfortunately, this issue has been present since day one of this rom.
[Fire HD 8 and HD 10 Original Android Development] domce106:
Did what you suggested. The same results for me as well. Cores 2 and 3 are in max usage. After turning on energy saver and restarting, the cores started working properly and temps went down.

Doing this did not have any noticable impact on video performance (as far as I can tell). The device does seem a bit snappier overall, though.

I am on ROM 20220506 with gapps installed, twrp 3.6.1-9.2, no magisk. Used CPU info from playstore for stat checking.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
There was an issue similar with the s5 a few years ago. The fix was to disable all but 1 core during boot then all cores brought online once fully booted. This was set by the developer for Los s5 at the time.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Thank you, enabling Power Saving then cold booting definitely seems to be helping with the system temps.
[Fire HD 8 and HD 10 Original Android Development] Klaus R:
Unauthorized shutdowns are really ennoying... If I remember right, that didn't happen before updating kernel to 3.18.140. Why not just use the version before? Noob question 😉
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Unauthorized shutdowns?

What is this you speak of?
[Fire HD 8 and HD 10 Original Android Development] Klaus R:
Almost posted this issue some weeks ago. After some minutes of non-use it is off. Have to press power and it boots up
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I've installed 20220506 okay with OpenGapps Pico and everything seems good, but I am getting the overheating/highCPU issue.

I've followed advise on power off/on rather than restart and I think this helps, but I'm confused by the suggestion on using 'Energy Saver Mode' - what is this? Do people mean "Extreme Power Saver" under 'Battery Saver and Performance'? I can't switch this on, everytime I try it says "The performance profile is currently unavailable" - why can't I switch that on? Is there evidence this helps with overheating/highCPU ?

I remember some years ago using apps to change the Governor & assorted other CPU management tweaks - is there something like this available for the FireHD10 running Lineage?
[Fire HD 8 and HD 10 Original Android Development] digbys:
i tried to downgrade twrp from the latest to the *0 version ((had issure with latest rom so i thought maybe it was the latest twrp that was causing the problem) and now twrp no longer boots - it just reboots the tablet back into android. tried doing a fastboot to reflash twrp but it gives an error about locked bootloader. tried to reset with the amonet scripts but it says its not suez device anymore but lineage instead. any idea how to reflash twrp back?
[Fire HD 8 and HD 10 Original Android Development] kmsi:
How did you flash the TWRP? You should have installed it via TWRP - flash image menu. Is your LOS still booting?

I had the similar trouble, and I had to reflash it using the unbrick method (by opening up device and following unbrick instructuons).

Those post might help:

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/page-75
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Slight aside question (because I can't find a good answer elsewhere), does the FireHD 10 (suez) with this Lineage 16.0 ROM, support Android Auto? I was hoping to use my FireHD10 as an in-car SatNav (linked by BT GPS) but Android Auto is not available to download from Google Play store. Any ideas?
[Fire HD 8 and HD 10 Original Android Development] psi78:
opengapps pico for Android 9 doesn't contain Android Auto (opengapps pico for Android 11 contains it, but isn't compatible with LOS16/android 9 of course)

So you'd need a gapps package which includes it (but bigger versions of opengapps won't install on suez probably, because of the small partition size of system partition) or just download it from apkmirror.com

Regarding the energy saving mode, that was probably a direct translation from german "Energiesparmodus" ;), but in english version of LOS it is " Power Saving" in quick settings, or settings/battery/battery saver and performance/extreme power saver

For kernel tweaking there exist apps like SmartPack-Kernel Manager(availabe on fdroid or direct apk download from github), on playstore: Franco Kernel Manager (Francisco Franco), EX Kernel manager(flar2)

all need root though
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Thank you for your excellent advice & suggestions.

One query though - the ROM is pre-rooted isn't it (System > Developer Options > Root Access) so presumably there's no need for Magisk if the only thing required is root access? (seemed to work okay when I installed SmartPack Kernel Manager)
[Fire HD 8 and HD 10 Original Android Development] psi78:
I don't have much experience with these versions of getting root access like supersu or su but there are tools like Root Checker to see if root works properly. I think the root version you mentioned may stem from k4y0z amonet scripts, there's a minisu.img inside that zip, or twrp which maybe contain it's own su version, but i'm not sure about that. Magisk at least reports removing a previous su version when you install it.

Other apps like naptime or matlog also for example will complain if they don't have root permissions (or permissions granted by adb), and they do complain without magisk giving them root access or setting permissions per adb.
[Fire HD 8 and HD 10 Original Android Development] ggow:
Hello, need logs to find out what's actually going on.
[Fire HD 8 and HD 10 Original Android Development] :
This doesn't seem to have broken anything but it didn't fix it either. I don't think this partition is related to whatever this issue could possibly be.
[Fire HD 8 and HD 10 Original Android Development] xjacksssss:
Sure! If you can tell me where I can grab the info I'll send it over!
[Fire HD 8 and HD 10 Original Android Development] ggow:
[Tutorial] How To Logcat

Here's how to use logcat: There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app: Here are two good examples are either: aLogcat or Catlog I prefer...

xdaforums.com
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
is it possible to do it on a virtual machine? or does it have to be a computer that has linux installed?
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
disregard this post, wrong topic
[Fire HD 8 and HD 10 Original Android Development] :
I've only had this issue when flashing it after having flashed newer versions. I do have one idea of what it could be though: the metadata partition is supposed to hold information about encryption, which I was trying to get working on LineaegOS 14.1 (which apparently is the version that switched to file based encryption). Do you know if it's safe to wipe it?
[Fire HD 8 and HD 10 Original Android Development] ggow:
firstly have you tried formatting /data in twrp?

Should be safe to wipe /metadata

We should also move this conversation to the q&a section because it's completely off-topic here
[Fire HD 8 and HD 10 Original Android Development] :
It worked!

Will keep that in mind next time!
[Fire HD 8 and HD 10 Original Android Development] ggow:
Cool, glad it worked
[Fire HD 8 and HD 10 Original Android Development] :
Unfortunately I tried and encryption doesn't work on LineageOS 12.1 either. So currently encryption isn't working on all three versions, and signature spoofing is only working on LineageOS 12.1. If signature spoofing and then hopefully encryption support is added to this version (cause you won't be updating the others), then I'll switch. Thanks so much for your work on this rom!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
So I've gotten some more information regarding the exploit which allows the use of SP flash tool without an authentication file, which is what in the original state this tablet needs an order for SP flash tool to function properly. Now from what I understand with this exploit we in theory can flash whatever we want to the device regardless of what the Amazon ecosystem or what they did to it says. With that being said couldn't we just retake the original boot partition on this device?
[Fire HD 8 and HD 10 Original Android Development] steve.on.xda:
I was able to get file system-based encryption working on LineageOS 12.1 but changes to the ROM were required to get it to work. More information on the steps required here: https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677/post83598879#post83598879
[Fire HD 8 and HD 10 Original Android Development] :
Oh nice. I'll look into that!
[Fire HD 8 and HD 10 Original Android Development] dasbooter:
Just chiming in with a thanks and to let the OP know we are still out there with our Suez
[Fire HD 8 and HD 10 Original Android Development] Sc4r3Crow:
Does this rom support signature spoofing?
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
its not currently useful enough to worrie about that

it boots but no hardware acceleration means its pure pain to use

wait for fixes
[Fire HD 8 and HD 10 Original Android Development] Sc4r3Crow:
Thanks for your reply (y)
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Been looking at a lot of the logs lately while screwing around with various things, that I won't discuss because it's off topic. But in doing so I have discovered a few things going on when attempting these experiments. and it might explain why some of the things don't work on these devices while flashing a custom ROM. And without being able to post logs right now I might be able to be safe to say it has to do with root in general. Something in the hardware composer that has to do with whatever Amazon put in there, essentially stops large portions of the device from either booting or operating properly. I only say this because the errors that happen are being logged or at least reported by an Amazon specific service. Most of the logs I read are while I am in a boot loop, I put it there on purpose in order to get these logs but wasn't looking for this specific thing. Anytime I try to use a rooting process that has nothing to do with the built-in root or magisk, which I think works because it is systemless, root is either denied or the device refuses to boot or even work properly whatsoever to a point where it will boot all the way. So although the device works while using the built-in root, that might be why some of the things aren't working properly, just because of root in general. I'll have to post the logs and you don't really notice it until you start seeing the pattern of it happening. So I don't think it has anything to do in some cases with hardware code missing as it does with something else going on that we don't know about or haven't found yet. That's just my take on it after running these couple of experiments. I'll give you more tomorrow when I can post some logs.