yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Thanks for the feedback. Swap priorities determine write precedence with higher (more positive) numbered spaces being used first. So, the swap file you created in the cache partition won't be used until zram is effectively full. If priorities are identical the spaces get consumed roughly equally.

Swappiness is more difficult to explain but generally determines how aggressively information is migrated from memory to swap. Due to limited resources (cpu, memory) Fire 7 devices lag badly when free swap is exhausted. You can keep an eye on available swap space using the free DiskInfo app. Once swap shows full it's time to reboot.

---------- Post added at 01:18 AM ---------- Previous post was at 01:05 AM ----------

Go for the swap tweak; it should serve you well. Rebooting every night will also help, especially if frequently connecting to different/new wifi networks. Keep location services disabled whenever possible, preferably just before entering sleep so device doesn't bog down on wake trying to acquire new location data. Keep it simple by swiping away unneeded apps before firing up resource intensive video services. Happy device, happy user. :)
[Fire Original Android Development] DragonFire1024:
Try to limit the number of WiFi logins in one spot. If it's constantly bouncing between two signals, that's wasted energy.
[Fire Original Android Development] DB126:
I too have started omitting GApps on secondary devices with limited resources. Play Services demands a sizable chunk of active (non-cached) memory which can be a burden on gizmos with less than 2GB of RAM. As most of these are special purpose devices I simply sideload the needed apps and call it a day. Makes a big difference in responsiveness.
[Fire Original Android Development] ajislav:
Thanks, worked like a charm!
[Fire Original Android Development] ajislav:
Delete
[Fire Original Android Development] coopmaster:
Can we confirm that Magisk doesn't work with this ROM or just in general the amazon fire like this? every time I try this i get boot loops until i uninstall it.
[Fire Original Android Development] DragonFire1024:
Have you unlocked your bootloader yet?
[Fire Original Android Development] DB126:
Short of a sucessful hardware mod Magisk will not work on this device as the bootloader remains locked. Even if it did there would be no significant advantage over current root manager solutions given the Android 5.x base.
[Fire Original Android Development] Ace42:
Plus, most of the apps that care about safety net would run terribly on the Fire (Fortnite, Pokemon GO, FGO, Android Pay, etc). I can't see anyone using banking apps on this tablet, and some have a minimum API higher than Lolli.

Xposed + SuperSU is sufficient.
[Fire Original Android Development] Rortiz2:
LOL fortnite? ?? This device has a 1GB of RAM and fortnite requires 4!

By the way there are applications to hide the root.
[Fire Original Android Development] t3chwizard:
PUBGM > Fortnite how dare you speak the F word. Anyways lol this tablet doesn't even load up Brawl Stars so heavier games would probably cause it to burst into flames.
[Fire Original Android Development] Neffy27:
[MENTION=5488402]Davey126[/MENTION] , I just did via FF Pro, full wipe, re-flashed latest Lineage (without gapps). There's still Google components that come by default. Is this right?

I decided to do this due to the increased responsiveness and longer battery life when I uninstalled Google play services via TiBu. Though now, TiBu can't detect my Pro key license.
[Fire Original Android Development] DB126:
I have not looked at [MENTION=5749760]ggow[/MENTION]'s Lineage 12.1 build sans GApps. Could be some Google components are baked in. Nexus is an alternative if you want to go GAappsless. Of course, most licensed content is not available w/o the play store unless the developer offers a separate licensing file that you can download/sideload.
[Fire Original Android Development] ggow:
There could be some google stuff included in lineage like google analytics maybe, but just to confirm I don't add any myself.
[Fire Original Android Development] DragonFire1024:
I suspect if you remove all the gapps, including the hardcore ones, as lowest as you can get is the play store apks. On my xt907 I prefer the stock rom to the custom ones and I'm just about at that level. It takes a lot of tinkering to get there. I found a few handy flash zips that help with gapps removal I've been using for a while on my eldest devices. I'll upload them when I get back inside.
[Fire Original Android Development] DragonFire1024:
Correct me if I am wrong...I really don't know. The 8.9 Amazon Jem has TWRP, but is it actually unlocked or does it get TWRP in the same fashion as the 7? Well either way, someone got Magisk to boot on the 8.9 and it's awesome. Here is the link to the thread. I have no idea how this was done except he says something about the "magic number" getting screwed up when Amazon boot.imgs are patched or altered. Using his method here, I confirm it works. https://xdaforums.com/kindle-fire-hd/8-9-inch-help/magisk-poc-boot-img-3-19-18-los-14-1-t3770638
[Fire Original Android Development] DragonFire1024:
Ok the remove_gapps_1.1.zip is hardcore. This will wipe just about everything google from a device. I found it to be a headache to put back together so I ended up flashing stock and starting over. The gapps-remover.zip is a lot less harsh and I use this one the most. Simply flash them in flash fire.
[Fire Original Android Development] DB126:
Back in the day (2012-2013) there were a few approaches to exploiting vulnerabilities on 2nd gen Fire HDs (Jem/Tate). My gizmos are fully unlocked leveraging the native root manager in CM/LOS. TWRP 2.8.x.x is onboard. Personally I could care less which root manager is in play as long as it doesn't get in my way.
[Fire Original Android Development] DragonFire1024:
I guess I am wondering if something like the above can be used on our present day devices. The unfortunate thing is, Everytime you edit the boot.img on the Jem, you have to repatch it. Do we know if the same issue persists today with unpacking and repacking the imgs?
[Fire Original Android Development] DB126:
Sorry - I don't mess around at this level any longer. If a device can't be natively unlocked or otherwise prove useful it doesn't make it into my portfolio. I'm banging this out on a stock 8th gen HD 8 with a sideload app portfolio. Works fine, perfectly stable. I do have a few older 2nd, 3rd and 5th gen devices that were easily rooted. Might root this pup at some point. Value add needs to exceed time investment. Not there yet.
[Fire Original Android Development] reliant_turbo:
Ggow,

Any chance of you creating a newer android version of these ROMs (lineage/aosp) with kernels once the bootloader hack is released? Or for the hd8 2018 since its already available? I love the current versions even though they are lollipop. Thanks for the work you have done. Its great.

Brian
[Fire Original Android Development] Andrewmail83:
Bootloader hack is released? Someone finally made it? :)
[Fire Original Android Development] DragonFire1024:
Could have saved yourself a paragraph. So if anyone else is interested, the methods I linked to earlier work perfectly at patching the boot.img for the 8.9 jem. If the same technique can be applied to boot.imgs of recent tablets, then we have a way patch it any way we want, especially the kernel command line. I really do think its worth a look by someone who knows more about this than I do.
[Fire Original Android Development] DB126:
Let's move this out of the Lineage thread. You'll likly get more traction in one of the unlock/unbrick/stop-drop-and-roll threads where like minded individuals converge.
[Fire Original Android Development] nintendobuster420:
The best I could run on my Fire was a couple of N64 games including Mario 64, Zelda ocarina of time, mario kart 64 and goldeneye. I bet this thing could run PS1 games as well as PS1 dosent require that much specs to emulate
[Fire Original Android Development] Pix12:
Could there be a chance of porting newer Lineage versions since there's a new unlock for the tablet?
[Fire Original Android Development] Rortiz2:
Can I flash this ROM on my rooted Fire 7 7th gen?

FlashFire
[Fire Original Android Development] kozyy:
No
[Fire Original Android Development] kozyy:
[MENTION=5749760]ggow[/MENTION] is that quote^ still accurate or would the unlock method used possibly have changed something?
[Fire Original Android Development] ggow:
The quote is still accurate.
[Fire Original Android Development] Rortiz2:
Possibilities to compile the ROM for the 7th gen?
[Fire Original Android Development] Pix12:
Can the unlock give newer Lineage OS versions on the 5th Gen?
[Fire Original Android Development] thoughtlesskyle:
Theoretically if somebody builds the rom yes. The reason we couldn't move passed lollipop was because we couldn't flash a boot.img because it signature checked on start up so we couldn't boot anything that wasn't signed by them. Now that we have the bootloader compromised it should be possible
[Fire Original Android Development] DragonFire1024:
Still only able to flash stock, unmodified boot.imgs. part of the problem is the above mentioned. The rest is because there are no tools which properly unpack and repack the boot.img without messing up the magic, which causes the kernel to not boot.

On the Amazon 8.9, they were able to make edits to the boot.img or patch it with magisk, then repack it and run a few commands in Linux to patch the magic back and use the img for magisk. I was also able to make my edits to the img then patch it through Linux too. I have not yet been able to apply this to the modern tablets.
[Fire Original Android Development] Pix12:
Magisk did work on the 2015 Fire 7 if that could help? Also I think the modded TWRP in the unlock actually patches the boot but I'm not quite sure.
[Fire Original Android Development] DragonFire1024:
If it does, I'd like to know how. It would be great to flash a boot.img with just root.
[Fire Original Android Development] Pix12:
Here's a link to what I think is the boot patching code that the TWRP uses, but i don't think you can do it with just root, as it seems to be a bootloader unlock.
[Fire Original Android Development] DragonFire1024:
I just need to look at the scripts. The patch work done after magisk on the 8.9 was all done through a Linux terminal. If we can finally properly edit and patch the boot.img, we can use flash fire to flash it.
[Fire Original Android Development] k4y0z:
Once you have the exploit installed, you could theoretically also flash prepatched boot-images with Flashfire.

My github includes a python-script that patches the image for you.

The patching is device-specific though.
[Fire Original Android Development] DragonFire1024:
I'll look at it. What would I need to do to port that script to the HD 10? Just want to edit the cmdline and default.prop and test a theory.
[Fire Original Android Development] k4y0z:
As previously said, it's not as easy as changing a script. Someone will have to write an exploit for the HD 10 bootloader (LK).

Which will be more difficult because it forces a 64-bit kernel.
[Fire Original Android Development] k4y0z:
FYI: there is unlock now also for the 7th gen in addition to the 5th gen: https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire Original Android Development] thoughtlesskyle:
So this bypasses needing the stock boot.img correct?

Also [MENTION=5749760]ggow[/MENTION] are you still developing for this device?
[Fire Original Android Development] DragonFire1024:
I'm not talking about that. I'm talking about editing the boot.img without screwing it up. I know why it gets screwed up, you see the error in various tools. If it can be done on the 8.9, it has the potential to work on the 10, or others.

That being said, I need to look at the bootloaders and lk because I recall seeing at least 3 or 4 serial numbers in one of those that when googled, came back as Lenovo hardware. I'm on the hunt for DA authentication files for SP flash tool (.auth) in hopes one will work. It's not likely, but if anyone comes across some, let me know. There are quite a few Lenovo .auth files around, but it's a matter of finding legit sites that host them that aren't polluted with click bait.
[Fire Original Android Development] k4y0z:
Yes, that is correct.
[Fire Original Android Development] Pix12:
How hard would it be to port Lineage 16 to the Fire because I kind of want to try now.
[Fire Original Android Development] Rortiz2:
For 7th gen or 5th gen?
[Fire Original Android Development] Pix12:
​

5th
[Fire Original Android Development] Rortiz2:
It can't be ported, it need to be compiled.

I can assure you that it is a lot of work. But I do not know what exactly should be done to compile LineageOS 16..
[Fire Original Android Development] mateo121212:
so now the 7th gen is bootloader unlocked i went through some trials. if i remove the boot.img from instalation it boots on the 7thgen. the only thing i can confirm working now is screen,sound,touch,wifi the screen is 180 from where it should be and the touch is 90 off from the screen.
[Fire Original Android Development] Pix12:
Could you send the rom?
[Fire Original Android Development] mateo121212:
It is not even close to running. If you dont know how to edit the updater script yourself as per my description, then even messing around with this rom is not for you right now. It is not capable of even getting around setup without alot of guess work.
[Fire Original Android Development] Neffy27:
No offense guys, this thread is for this ROM (ggow Lineage) and this device ($35 Fire). I'm subscribed to this thread for related updates.
[Fire Original Android Development] k4y0z:
[MENTION=6568249]mateo121212[/MENTION] is talking about this ROM working on the 7th gen. It seems only display isn't set up correctly.

So this might be an easy fix.
[Fire Original Android Development] thoughtlesskyle:
Then other than the Fire 10 stuff this is probably some awesome news for you
[Fire Original Android Development] ggow:
Yes I am. Just haven't had a lot of spare time recently. There will be updates for this ROM.
[Fire Original Android Development] Neffy27:
Is this sarcasm? This thread started for Amazon Fire (7") 5th Gen - 2015 KFFOWI | Ford. I won't bug anymore.
[Fire Original Android Development] thoughtlesskyle:
That the bootloader has been compromised and we can potentially go passed lollipop?
[Fire Original Android Development] mateo121212:
So i was bored. I got this rom running on the 7th gen.

Working

Camera

Touch and all that

Wifi

Bluetooth

Usb MTP and ADB

Sound

Brightness control

Not working

I dont know

I only made a few modifications to get it running. Take the attatched zip and use 7zip to merge its contents with the the 5th gen lineage zip. I commented out the boot.img install so make sure you start with the 5.6.3.0 boot.img installed allready
[Fire Original Android Development] DragonFire1024:
Wouldn't it be just my luck if this is all that needs to be done on the HD 10, is comment out the boot.img portion of the script. I'll kick myself. I'll experiment when I have time.
[Fire Original Android Development] mateo121212:
That's not all I did, look at the zip. Since its the same processor,I looked at a bunch of mtk porting guides. And figured out witch files needed to be changed. Since this Rom uses stock boot.img of the 5th gen I was able to comment out the boot.img and use the stock one on the 7th gen.

This Rom only flashes boot and system originally. Roms from or to other systems would be harder
[Fire Original Android Development] Pix12:
Thank you for the port!
[Fire Original Android Development] mateo121212:
Remember to do factory reset and possibly wipe system b4 install. If done correctly it should take a while on first boot.
[Fire Original Android Development] Rortiz2:
lol you've gone ahead I was also porting this rom for the 7th gen.

I just get it and I see your message.:D

---------- Post added at 08:48 PM ---------- Previous post was at 08:26 PM ----------

Hi all, here's the link for download LineageOs 12.1 for austin:

https://www.androidfilehost.com/?fid=1395089523397896035

Thanks to [MENTION=6568249]mateo121212[/MENTION] for port the rom and many thanks to [MENTION=5749760]ggow[/MENTION] for compiling the ROM and doing the hardest work.

For not doing offtopic I propose to create a theme for the rom for austin.
[Fire Original Android Development] Pix12:
I'm going to try to port a Lineage OS 14.1 rom from the Alcatel Telekom Puls which seems to have the same processor as the Fire 7 Ford.
[Fire Original Android Development] mateo121212:
Ive been trying since yesterday to do that myself. I end up with a black screen pretty much. Still trying.
[Fire Original Android Development] Rortiz2:
Ported and bootlop °_° KFAUWI austin
[Fire Original Android Development] DragonFire1024:
At least I'm not the only one having an issue with porting.
[Fire Original Android Development] AndroidSpaceMonkey:
Looking for some help, I have a 5th generation Fire 7" with cyanogenmod installed on it but looking to install Lineage OS on it.

What would be the process to do this?

Do I need to install FireOS back into it first or can I go straight from cyanogenmod to LineageOS and how?

When installing cyanogenmod I used FlashFire if that makes a difference at all
[Fire Original Android Development] steevesmatthews3:
Great content
[Fire Original Android Development] Rortiz2:
LOL use this method for install TWRP permamently:

https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire Original Android Development] amti366:
Hi guys,

I am facing a weird issues. I have two 5th gen fire 7 tablets that were both rooted with CynogenMod version: 12.1-20170802-UNOFFICIAL-ford. I decided to update them both to the latest LineageOS version: 12.1-20181218-UNOFFICIAL-ford

Everything went smoothly and I was able to upgrade both tablets using flashfire 0.58 like recommended (wipre data followed by lineage install followed by Gapps nano) using a 16gig micro sd card.

Now for the weird part, one of the two tablets seems to have lost root after upgrade. I am able to see SuperSU got installed in one and not the other (tablet that has lost root). I tried sideloading superSU but it is unable to update the binary using normal method. I used flashfire so do not have CWM or TWRP on these.

I am not sure how is it possible that using the same sd card with same setups on two tablets with same version resulted in one of them loosing root access. I would really appreciate if someone can help me solve this mystery. Although everything is good on both the tablets for now but i am afraid I will no longer be able to upgrade the tablet that has lost root.

Thanks,

Matt
[Fire Original Android Development] Pix12:
Don't worry. In developer settings, there's a root access setting, just set it to allow for apps and adb.
[Fire Original Android Development] Neffy27:
[MENTION=1056340]amti366[/MENTION]

Someone can correct me but my understanding is your only need one root. You either use the built in root that comes in this ROM (Privacy Guard) or SuperSU. If you flashed SuperSU, supposed to leave Privacy Guard disable in Dev options. Having both roots might have caused the issue. I had the exact issues you described, randomly lost root one day after it had been working for months but I had Privacy Guard enabled and RUNNING SuperSU.

I currently Privacy Guard disabled, with SuperSU flashed, 100% working root for a few months going now.

To your situation, maybe toggle Privacy Guard root to hopefully regain root, if unsuccessful, have to go back to stock and start over.
[Fire Original Android Development] amti366:
Thanks Pix12 that was very easy to fix. I have a bigger issue after installing Lineage-12.1-20181218 to the tablet. I followed the instructions and used flashfire 0.58 and did a wipe followed by Lineage followed by gapps. but the tablet seems to be stuck in bootloop. it only shows the Amazon logo and nothing else happens. I tried to keep it on for hours. did I just brick my tablet?

Thanks,

Matt
[Fire Original Android Development] DB126:
Common FlashFire failing on Fire tabs. Traditional solution involves reloading FireOS via stock recovery and starting over. Also no reason to use a backdated FF build. The speculation that older builds would reduce/eliminate boot hangs has long been disproven. Stick with 0.73 which contains fixes for other issues.

tl;dr - not bricked.
[Fire Original Android Development] amti366:
Hi Davey126 thanks again for your help with this issue. I saw the same in a old message here : https://xdaforums.com/amazon-fire/o...neage-12-1-t3639447/post75694066#post75694066

But I am not sure which version of FireOS should i revert back to? I am guessing reverting to a wrong version will definitely brick the device? And above a certain version I will loose the capability to root.

Thanks again.
[Fire Original Android Development] Pix12:
https://xdaforums.com/amazon-fire/development/identify-bootloader-version-t3424634
[Fire Original Android Development] amti366:
Thanks Pic12. looks like I messed up. Followed the steps to read the binary and came to the conclusion that I need FireOS 5.1.1 (I think it is 5.3.1)

After install I think I have a hard brick since I do not even see the Amazon logo anymore.
[Fire Original Android Development] ms372591:
If it's bricked you can try this thread.

https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire Original Android Development] amti366:
I came across this thread but it seems to be for soft brick mine does not even show me the amazon logo hence hard brick.
[Fire Original Android Development] ms372591:
I could be wrong but I thought that this method was for a hard brick from downgrading the firmware.
[Fire Original Android Development] amti366:
Ok let me post a question on that thread thanks for your help.
[Fire Original Android Development] DB126:
Looks like your all set thanks to [MENTION=7153704]Pix12[/MENTION] and members in the thread he/she linked. Glad you were able to resurrect your device.
[Fire Original Android Development] amti366:
Yes Davey126 it worked out pretty well. bricked and unbricked my sons tablet in one day and the joy the the little guys face was worth it.
[Fire Original Android Development] elgreko16:
Heyy Friend,

I've already unlock my 7th gen fire 7 but when I install your Los 12.1 version It keep stuck on Los boot animation. Any advices????
[Fire Original Android Development] Rortiz2:
Do you make wipes?

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] elgreko16:
Yesss, all wipes!!
[Fire Original Android Development] t3chwizard:
Is there a concrete guide for the Bootloader unlock for the Fire 7 (2015)? I am just confused reading various comments and replies.
[Fire Original Android Development] blueberry.sky:
Yes, here https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860/
[Fire Original Android Development] fmc000:
Hello,

any news on this?
[Fire Original Android Development] DragonFire1024:
Slowly figuring it out as I go along. This will take time.
[Fire Original Android Development] Rortiz2:
I have the lineage 14.1 sources downloaded and I'm going to "" try "" to compile.

But do not expect anything ..
[Fire Original Android Development] Insane PPC:
just happy some of your good people are working on an updated lineage. just did the first of 4 tablets with the unlock and installed lin. 12.1 and its working good. but i always love updates and hoping an unlocked tablet might help with the development (maybe custom kernals too?)
[Fire Original Android Development] Rortiz2:
Yes. But as I said before, do not expect much...

ggow already said that he kept working on this tablet and that he would compile other versions of android.
[Fire Original Android Development] Vovan2k:
How do you remove google search bar from home page, i cannot seem to find a way.

Man it was right there hold home screen till you see widgets and walpapers and settings on bottom then swipe up to show homescreen options, first option disable search bar.