yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DragonFire1024:
It's some checking feature that takes place just before downloading an app or updating one. I'm pretty sure but could be wrong it has to do with play protect. My guess is it is checking the device to see if it's certified rooted etc. Also to check app compatibility status etc etc etc. In my experience first install takes the longest time. Turn off auto updates and then reboot usually that fixes it. That usually happens for longer periods when the play store or services try and update at the same time as apps. It just freezes everything. Usually if you stop all apps from Auto installing/updating then stop all the apps from updating on the update page itself, and stop play services from updating, then pick one, it all generally catches up in a minute or less. Best to update play services first so if needed the play store can update.
[Fire Original Android Development] ggow:
New Build is Up

Dated 18 April 2019

- Fix sdcard write permissions

- Fix screen off animation for odd hwrotation

- Add support for amazon fire 7th gen

- Merged common kernel for ford and austin (android_amazon_kernel_mt8127-common)
[Fire Original Android Development] Reynald0:
I installed Busybox module Osmosis into Magisk, if I type Busybox, It output segmentation fault

I removed Osmosis Busybox module, and is working fine with default 1.22.1, I think is probably a problem of the Magisk Module.

Switched to another solution for now.
[Fire Original Android Development] Reynald0:
Fixed, it was the lineage-su.
[Fire Original Android Development] DragonFire1024:
How did you remove or disable lineage su?
[Fire Original Android Development] Reynald0:
DragonFire1024:

With your instructions in some post above, plus this addonsu-remove-14.1-arm-signed.zip,

basically was happening to me that for every reboot stucked on Amazon, and needed to reflash Magisk
[Fire Original Android Development] DragonFire1024:
So editing the script worked then?
[Fire Original Android Development] eric93se:
Thank you ggow for your hard work!!!!! This is awesome!

Just to add to the supersu conversation, before I flashed the latest rom (unlocked bootloader, twrp, ford 5.1.2 :D ) I flashed "update-unSU-signed.zip" in twrp. I wanted to use Magisk.
[Fire Original Android Development] ldeveraux:
I'm sure this is a foolish Q, but what's the differentiation between FORD and AUSTIN ? Does FORD=2015 model and AUSTIN=2017 model?
[Fire Original Android Development] ms372591:
I believe

Ford it the 5th Gen

Austin is the 7th Gen
[Fire Original Android Development] riverstyxxx:
I hate to say this but I have three of these tablets and it doesn't run well on any of them anymore, too slow. Apps take forever to open, etc.
[Fire Original Android Development] Pix12:
How far away are we from getting higher Lineage versions?
[Fire Original Android Development] ldeveraux:
No ETA on XDA:good:
[Fire Original Android Development] Rortiz2:
MT8127, 1GB RAM .. What else do you want from these tablets?
[Fire Original Android Development] riverstyxxx:
With all this work, I just don't see the point if the hardware can't support it.
[Fire Original Android Development] DragonFire1024:
In these cases, at least the HD 10, it looks like a lot of hardware is in place, just sitting on the sideline. I'll admit gps isn't looking likely, however mediatek does have a pretty sophisticated agps protocol. There's plenty of that in the source, and that's mostly related to software (Google has their own implementation of it). I also see multi window in the config, and a lot of other things like their mircast protocol which on these tablets, is singing with the crickets. The HD 8 has been the only one to ever be setup for it for quite some time now. There's a lot more to these things than applications. Hell I didn't even know there was a boot room mode until several months ago. We are only now just able to scratch through the surface. There are a lot of smart and dedicated devs and volunteers here and if anyone can get it done it's them...and us. I know it's hard to be patient when so close...I'm an example of the worst kind of impatience. But good things come to those who wait...or do ;)

Edit. I got out my xt907 razr. That phone is nearly 10 years old and I'll tell you, if it weren't so small, I'd use it as much as my tablet. Why? It out performs almost every device I have had since I got it. Sometimes you get a good device like that and it lasts forever. These tablets have proven to be no exception. My Ford is still a badass. But as long as you don't expect it to cook you dinner, then it's still one of the best 7in tablets old or new.
[Fire Original Android Development] riverstyxxx:
Speaking of which, is there any reason the HD 6 and 7 hasn't seen any updates in the past four years?

https://xdaforums.com/fire-hd

I have an hd 7 and it's pretty good, but lacks a custom rom worth using because nobody has updated it.
[Fire Original Android Development] Rortiz2:
You have not understood me .. I mean that this tablet has a very bad hardware and can not go faster. Always, there will be a moment that will go slow.

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------

https://github.com/ggow/android_device_amazon_thor

There's a Lineage 15.1 branch but I don't know if anyone is working on it..
[Fire Original Android Development] DB126:
Both correct.

---------- Post added at 12:59 AM ---------- Previous post was at 12:46 AM ----------

Device is fine for certain highly focused workflows such as streaming, news feeds, lite browsing, etc. Multi-tasking quickly overwhelms its limited resources. Leveraging a static swap file can help with wake lag with the proper config. That said, most contemporary 'entry level' phones easily run circles around this aging slug.
[Fire Original Android Development] Oco:
Thanks, update works fine + gapps pico + magisk. Just allow me to say that your nexus fire seems snappier :)
[Fire Original Android Development] DragonFire1024:
I am pretty sure only the 7, 8 and 10 receive updates. Good question though.
[Fire Original Android Development] fmc000:
Yeah, I miss updates for fire nexus too.
[Fire Original Android Development] mrmazak:
In the developers options menu, there is an option to update cynogen mod recovery with system updates. I assume this is a bad idea to run this option??

Can this menu be removed from the build tree?
[Fire Original Android Development] ggow:
I'll look into it.
[Fire Original Android Development] ggow:
New Build is Up

22 April 2019

- Rebased kernel with full history

- Upstreamed kernel to 3.10.108
[Fire Original Android Development] WangGang:
Dumb question. Can new build be dirty flashed?
[Fire Original Android Development] mrmazak:
very nice.
[Fire Original Android Development] ggow:
Yes, dirty flash is fine.
[Fire Original Android Development] mrmazak:
the new build is not in the folder linked in OP.

It is one level up.
[Fire Original Android Development] ggow:
Thanks for letting me know, I'll move it later

Edit: Done.
[Fire Original Android Development] WangGang:
Don't know if its just me but dirty flashing is causing bootloop. Had to clean flash.
[Fire Original Android Development] ggow:
That's strange dirty flashed 2 devices here and all was good.
[Fire Original Android Development] tonibm19:
Yay! Thanks for kernel upstream! :)

Now if we got a newer android version (I don't know if it's even possible, though)
[Fire Original Android Development] WangGang:
Maybe because I installed xposed?
[Fire Original Android Development] ggow:
Yes, that would do it.
[Fire Original Android Development] llamasking:
As of the latest version (20190422 / 22 APR 2019), Magisk Modules are working!

Tested on Magisk 18.1 or whatever the latest Stable is.

Last test was on the 18 December 2018 release, on which modules caused soft brick (did not boot) and the same issue happened if Magisk 19 was installed at all.
[Fire Original Android Development] WangGang:
No issues whatsoever? Wooot!
[Fire Original Android Development] RockwellB1:
I love that you guys are keeping this budget device alive, had one I couldn't do anything with because I rooted it in the past. Something went wrong and everything quit working correctly, couldn't even use apkpure or anything to get apps. Bought a cheap one off eBay with a broken screen, swapped the guts, and all is well again. And the work being done here gives it new life.

I just wish the same could be said of my other old tablet, a Tegra Note 7. According to benchmarks it's still twice as fast as a 2018 Fire HD 8, and has those great speakers and stuff, just zero support. nVidia really screwed people with that thing by not giving it at least the marshmallow update like they originally promised.

Ah well, thanks again guys. Keep the little purple ford chugging along!
[Fire Original Android Development] llamasking:
I did actually run into ONE issue after writing that.

On Magisk 19.0 (speaking of which, that works now. On the previous test, it caused the same soft brick as modules), I ran into an issue with the module called "SafetyPatcher", where it ran into the same issue as you would have on the 18 December 2018 release. Probably error on my part. I didn't read the instructions.

This is almost definitely an isolated incident, though. I've used modules on both 18 and 19 with no issues whatsoever. I can not get Safetynet to pass, though. Basic integrity works but CTS always trips.

You'd know pretty quickly if you had the issue. For one, if you reboot from the Magisk flash window, you won't get past the Amazon logo. Then, if you reboot by holding the power button, your boot animation would be rotated 90 degrees.

You can use MM from twrp to fix it.
[Fire Original Android Development] Jik Sey:
Thanks to everyone involved in working on this. Working great for me.
[Fire Original Android Development] Reynald0:
Just a heads up about one thing I noticed, at first I dirty flashed new build over old, but seen WiFi not working, then I did a clean flash as I wanted try to go without gapps on this device too; the MAC WiFi is changed, so if like me you have setup rules in your router about it, you may have to update them, not sure if this is a effect of the new kernel or someone else can confirm.

Thank you.

I think is a feature that is enabled by default in newer kernels, if possible, add a switch to turn it off.

Thank you
[Fire Original Android Development] Reynald0:
As for now, I reverted to previous build, from what I understood, there is a option to compile the kernel with that config to off, I use the MAC WiFi filtering not only for the "modest attempt" to improve my security, I know can be easy bypassed, but also it is useful for me with PiHole defining names for devices, in the case of MAC Randomization, I will be forced to have a android-xxxxxxx device of which monitor the DNS requests, hope there will be a switch inside developer options inside new build, to enable it, but not be the default.
[Fire Original Android Development] ggow:
I am going to replace the austin and ford device trees on my github.

There will be a device/amazon/mt8127-common which both austin and ford will draw on.

Then there will be other device specific trees for each variant.

Again this will help maintenance going forward.
[Fire Original Android Development] Jik Sey:
Is the random mac address default on more up to date kernals? Is it possible to configure this option to on or off? Thanks
[Fire Original Android Development] ggow:
I'll take a look.
[Fire Original Android Development] Stettin:
For some reason I cannot flash open gapps. I picked 5.1 nano - open_gapps-arm64-5.1-nano-20190426.zip and get an error saying wrong architectures. Any idea what I'm doing wrong? I'm using TWRP to flash the zip.
[Fire Original Android Development] mixmaxmux:
Hi,

I use the arm nano gapps.

For me the arm64 are not the correct gapps for the fire 7 tablet.

Max
[Fire Original Android Development] Stettin:
Thanks, that worked. For some reason I thought it was arm64.
[Fire Original Android Development] Stettin:
Can someone tell me what combination of SuperSU and Titanium Backup will work on the latest build? I keep getting "unable to acquire root privileges - This attempt was made using the "/system/bin/.ext/.su" I've tried an older SuperSU 2.46 which worked with Titanium Backup on the stock ROM. I also have an APK of the older version of Titanium Backup 7.3.0-376, and that doesn't work either. According to this link it might have something to do with systemless root:

https://android.stackexchange.com/questions/166848/titanium-backup-unable-to-obtain-root-permission

I have a few things backed up with Titanium I'd like to restore, like a key for SuperSU pro that I got from Amazon that is not downloadable anymore.
[Fire Original Android Development] Reynald0:
Update: Privacy Browser is now v3.0
[Fire Original Android Development] WangGang:
AFAIK Lollipop doesn't support systemless root. Did you do the namespace separation thing?
[Fire Original Android Development] Stettin:
I did try unchecking that and rebooting, and I still get the error. I did some searching and it looks like Titanium Backup is assuming the SU binary is in system/bin/.ext/.su but it really is not. I downloaded a root checker app and installed a new version of busybox and they all detect root just fine. I saw a workaround to try and copy from system/xbin to system/bin, however I'm not seeing the SU binary in system/xbin. Any idea where the binary is for a default SuperSU install? I haven't done much ROM hacking for a while now, so I'm a bit rusty. I poked around with ES File Explorer and can't find it.

https://forums.androidcentral.com/incredible-rooting-roms-hacks/20081-having-trouble-superuser-permissions-titanium-backup.html

Does Lineage store the SU binary in a special location or hide it?
[Fire Original Android Development] WangGang:
Strange. I'm using SuperSU 2.79 SR5 and the binary is in system/bin/.ext/.su . Have you tried uninstalling and reflashing SuperSU? Or just switching to Magisk?
[Fire Original Android Development] ldeveraux:
If I have a handful of updates through the Play Store, I can set them all to update in series. Is there a reason that it hangs when the screen is off? I have set "Keep WiFi on During Sleep" set to Always, so there's no reason it shouldn't have service. But whenever the screen turns off, it will download the next update, but not install it, nor continue with the next update. I suppose it's not specific to this ROM, it's occurred with every ROM I've had on this device, dirty and clean flashed, SuperSU or Magisk. This happens with a newly installed ROM even before I restore anything via TB.:confused:
[Fire Original Android Development] DB126:
Kernel dumps into low power mode which effectively stops non-critical processes. Primary reason why this gizmo has outstanding standby endurance regardless of ROM.
[Fire Original Android Development] ldeveraux:
Yeesh! I'm guessing no way to disable that then?
[Fire Original Android Development] DB126:
Not without flucking around with the stock kernel. Not a great idea in the absence of a knowledgeable resource given its importance; efforts to date have been amateurish at best.
[Fire Original Android Development] Reynald0:
Will be me, but from when I decided to give a try to the AuroraStore, in place of the gapps-pico, the endurance seems much longer; nonetheless, about 80% of the apps I was using before where coming from F-Droid, I think I should have tried it before, because the result really satisfy me.
[Fire Original Android Development] DB126:
Yep - GApps can be a big fat pig if not properly constrained. I often go GAappless (eek!) on my secondary devices. That said, it takes a little more effort to maintain the app portfolio on those gizmos.
[Fire Original Android Development] Stettin:
Thanks for the tip on Magisk, that worked.

Hmm.. It appears I accidentally deleted my Titanium backup files when reinstalling it. Ugh! Stupid ES explorer offered to clear out unused files and I wasn't thinking when I said yes.
[Fire Original Android Development] Reynald0:
You can try MiXplorer if it fits more better your needs friend, or in alternative compile OI File Manager inside Android Studio, is really similar to the default File Manager. I don't think they do any cleaning of files, as unwanted consequences.

Regards.
[Fire Original Android Development] WangGang:
No Problem man! Should probably switch to another file explorer though. Lot of good options. Someone said MiXplorer in thread and that's a pretty good one.
[Fire Original Android Development] llamasking:
I found that the camera works for taking photos but not for taking videos. This appears to have been posted a while back, but nothing seems to have came of it.
[Fire Original Android Development] llamasking:
I personally recommend Total Commander.
[Fire Original Android Development] Rortiz2:
For me works :/

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] llamasking:
What camera app are you using? On the stock app along with some other one, it doens't work.
[Fire Original Android Development] buletini:
The camera does not work for video.
[Fire Original Android Development] ggow:
I'll look into it for next release
[Fire Original Android Development] black.kahder:
OP Please update top post.
[Fire Original Android Development] Ataru Moroboshi:
It seems that encrypt tablet is not working. If i start encryption it go to endless boot animation of lineageos and i have to switch off the tablet. after it start but still unencrypted.
[Fire Original Android Development] nirogu325:
Thank goodness it doesn't work. You were lucky. In the past I enabled it once and it made the device perform a lot worse because its processor doesn't have hardware accelerated encryption support.
[Fire Original Android Development] Ataru Moroboshi:
My old amazon tablet was stolen 2 years ago including personal informations :(. this is why i want encrypt that, for me more important than performance. The robber was found by police but not the tablet and Prosecutor's office stopped the process against the robber.
[Fire Original Android Development] DB126:
Keep your valuable stuff in a secure container vs trying to trying to encrypt the entire device. The low end processor in these cheap Amazon tablets will yield a miserable experience. Encrypted cloud storage secured with MFA is another option.
[Fire Original Android Development] howzitnow:
Having trouble installing the rom, I don't do it often enough to be confident and I'd like someone to verify I'm following the steps correctly please.

current status (aside from the cracked screen lol)

5.0.1

twrp

fresh install of fire os following botched rom install

rooted/ota blocked/google playstore

What I did when first trying to install lineage

Booted into twrp,

clear cache, data & system on fire os

install lineage rom 12.1-20190422-UNOFFICIAL-ford (with verified md5) from sd card

install opengapps arm 5.1 nano

wipe cache/dalvik

tablet rebooted, wouldn't get past white amazon logo.

reloaded fire os via recovery/adb sideload

let it boot...it was fine

It was at this point I verified the md5s and they were good so I repeated all the steps I did previously. Same result as before, white amazon logo.

I reloaded fire os again and rooted with the intention of just leaving it, but, I'd really like to know where I went wrong and maybe try Lineage again

Am I forgetting something? Doing something wrong?
[Fire Original Android Development] mrmazak:
well. you must have missed the big notice that says this newest and all future builds are only for devices that have been unlocked.
[Fire Original Android Development] nirogu325:
You'd do well listening to Dave's two suggestions. Else this device will crawl like you've never seen (talking from experience) and have less battery life as well.
[Fire Original Android Development] howzitnow:
I did see that but I assumed that since I have twrp and the very old 5.0.1 that I was unlocked. Apparently it's more tricked than unlocked. Thanks for your reply.
[Fire Original Android Development] black.kahder:
ggow, thanks for updating the top post to remove the reference to only supporting ford/Gen5/2015-model.

Under the "Downloads" header, you still have the link as "Lineage-12.1 for Amazon Fire 7" 2015". May I suggest you remove the "2015" part of the text?

It would be nice if you had a "Known issues" header under which you could list the Magisk warning, and also add that the Camera app crashes on video capture.

I successfully installed this ROM on a new (purchased May 1 2019) austin/Gen7 Fire 7. Everything except the Camera video seems to be working. I will continue to test and post more feedback if I find something.

Your changelogs and other detailed information is very helpful for new educated devs/users like myself. Thank you.

---------- Post added at 01:42 ---------- Previous post was at 01:35 ----------

I think this is a reasonable mistake to make. The history of this device is complicated and the terminology being used by users and devs isn't terribly clear. I am an experienced dev but new to this device and I'm still learning the device history. I still don't fully understand the bootloader process very well yet because I have not yet seen a conceptual description anywhere.

In this case, I am guessing that old version of TWRP you have installed might be using an existing signed kernel from Amazon, or the old 5.0.1 bootloader doesn't verify signatures of the recovery part, or some other hackery. I'm not really sure.
[Fire Original Android Development] k4y0z:
The old 5.0.1 bootloader never allowed flashing TWRP. It allowed to fastboot boot unsigned boot/recovery-images however.

Though this was great to boot TWRP, this also meant a custom ROM would only work with a signed boot-image (or would have to be booted via fastboot i.e. being tethered).

With the unlock, unsigned images work for both recovery and boot, hence TWRP can be flashed and custom ROMs don't depend on the stock boot.img.

This is also the reason, why the current version of this ROM won't work without unlock, because it uses a custom kernel/boot-image.
[Fire Original Android Development] black.kahder:
I discovered that 5Ghz 802.11/wifi was not working. It would be nice to add this under a "Known issues" header on the OP. This appears to be known: https://xdaforums.com/showpost.php?p=79202917&postcount=3

Also, I had a problem where bluetooth appears to have crashed. I had a keyboard associated and then it stopped working after a few minutes. The bluetooth in Android turned off and wouldn't turn back on. I will have to try to crash it again later and capture logs.
[Fire Original Android Development] DB126:
You can flash any builds dated prior to 2019 if you don't care to unlock the bootloader. See first few posts in this thread for details & prerequisites for each build.
[Fire Original Android Development] corax2.05:
Dear [MENTION=5749760]ggow[/MENTION],

I have 3 tabs, running an early version of your build. All is fine. :)

Many thanks for your work!

I`ve read the bootloader is now open. Now it should be possible to bring this tab to a higher lineage version.

Do you have any plans to do this?
[Fire Original Android Development] ggow:
We can certainly go to higher android version. However there is no point unless we can have wifi, bluetooth etc all working. These devices are difficult to work with so first I want to make sure we can build these userspace items working first before moving up.
[Fire Original Android Development] DragonFire1024:
Check all the boxes on the HD 10. Add a few more because I think and I'm about 90% sure of it, we'll have full Miracast capabilities. There are a few kinks and some configs to go over, but it's already coming alive. [MENTION=5749760]ggow[/MENTION] have you seen the release on Google for the mt8127? It was released as part of the Android one project if I am not mistaken.
[Fire Original Android Development] Ztcc:
Check your PM!