yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] EtoileLabrie:
Feature request:

Can I request [MENTION=5749760]ggow[/MENTION] if possible to add volume + and - in the left and right side of nav bar (screen bottom). I saw this a while ago at my local store in a 'chinese' no-name tablet - Seems good idea. Also in nougat this feature is in Buttons menu. I do understand that lollipop will be newest android for this Fire tablet but this feature would be useful especially for people with bad hardware buttons.

Thanks for the great work
[Fire Original Android Development] DB126:
Lineage is a packaged ROM with similar functionality on various devices. IMO it would be inappropriate to add custom UI/UX features even if the developer was interested. There are Xposed modules that could perform the suggested customizations; not sure they will play nice with Lineage is it already offers limited navbar customizations.
[Fire Original Android Development] melvinaury:
You there is a jernel module for the rom. You can install them and the a kernel manager on that way yiu can create zram that is a specific amout od memory used ro compress information it help and is much faster than what you ask for.
[Fire Original Android Development] Xrx53:
Sd card

Hi. Im using the custom rom lineage released sep 2017 for anazon fire 7" 5th gen. i Cant set default storage to sd there is no option. Cant unmount/mount sd there is no option. Cannot register to amazon account and get access to books. Cannot install google play services from play store. Are these bugs or am i doing sth wrong?
[Fire Original Android Development] DB126:
Most Lollipop (Android 5.1) based ROMs do not allow setting external storage as the default destination. This is best accomplished using an app that support symbolic linking. App2SD and Link2SD are two examples. Both are available in the Play Store.

A similar comment applies to mount/unmounts. Some custom ROMs add this functionality; Lineage is not one of them.

Google Play Services should be installed concurrent with the ROM as noted in the OP. Adding it later won't work with Lineage. You'll need to use FlashFire to (in this order): 1) wipe the system partition; 2) reinstall Lineage; 3) install a suitable GApps package. Suggest 5.1/arm/nano which can be obtained from here. Do not install a package bigger than mini as there is insufficient space in the system partition.

Once these issues are addressed you can install a limited version of the Amazon store and Kindle app which should give you access to your reading library. Note you will not be able to take advantage of some native community features such as free books, book sharing, etc. These are Amazon restrictions, not bugs in Lineage. You need to return to FireOS if you want the full pallet of Kindle features.
[Fire Original Android Development] jeanett:
Hello, someone knows how you can add and show device name in the kindle fire 7 5gen Lineage-12.1 ROM

[IMG="See picture below"]https://image.ibb.co/eR5fy6/kindle_fire_home.jpg[/IMG]
[Fire Original Android Development] DB126:
This can be accomplished from Amazon's web portal. Logon to your account and look for section titled "Manage your content and devices". There's an edit button to rename the device.
[Fire Original Android Development] jeanett:
there is some way to do it in the ROM of Lineage-12.1 ROM since amazon does not detect the kindle fire because it no longer has the original software fortunately since I did not like the original I really like Lineage-12.1 ROM

note: the previous photo is not of my table is of internet only as reference
[Fire Original Android Development] DB126:
- where are you seeing this in Lineage-12.1? In an Amazon app?

- amazon maintains a device history that is unrelated to whether FireOS is currently in use; you should be able to find your device there and change the name which will appear in FireOS (if being used) and some Amazon branded apps (eg: Kindle reading app)
[Fire Original Android Development] Xrx53:
SD card

majority of the issues have been solved. the missing google apps can be installed directly from .apk file. the sd card unmount issue still remains though, none of the two apps link2sd root and app2sd root give an option of dismount although default location has been set. amazon account requires amazon os5.4.4 instead of 5.1.1 as the stock base system but that is frought with complications.
[Fire Original Android Development] DB126:
Some Google apps will not function properly unless the framework is flashed concurrent with Lineage. May or may not apply to the apps you installed.

Google apps installed (sideloaded) via a ".apk file" reside in the data partition reducing the amount of space for personal apps/data. Those same apps will be installed in the system partition if flashed.

I would not expect App2SD/Link2SD or similar apps to add a discount option; not their function.

Not sure I understand comment regarding Amazon OS level. You will need to install Amazon Underground (a legitimate Amazon app) to access proprietary Kindle/Prime content while using a custom ROM.
[Fire Original Android Development] t3chwizard:
Do you have a picture of this?
[Fire Original Android Development] t3chwizard:
[MENTION=5749760]ggow[/MENTION] would you mind posting a link to your repos for this ROM, I am working with someone else to make a back ported security patched 5.1.1 ROM for my LG E980 and don't want to have to do all the security patches from scratch if possible.
[Fire Original Android Development] ggow:
The ROM is just a folder of files on my PC. The problem with much of the ROM stuff I do is I don't have time to manage online repos. I track changes across the whole lineage tree within a local git repository. ie I haven't got a .repo folder in the root from where I originally synced lineage.

It sounds like a mess and some people will surely want to have a go at me for it, but working this way is speedy for me because I don't have very much free time to play with this stuff.
[Fire Original Android Development] DB126:
I can empathize having worked many IT projects. Some clients demand (truly need) highly disciplined source code management which sometimes accounted for nearly half the billable hours on an active project taking in all related activities. There is obviously a balance between available resource and the quagmire. If you and the bus have a premature meeting historical archives on XDA and elsewhere will continue to endure for our discretionary gizmo's. We are not talking critical infrastructure here. Seems like what you have been doing has been working reasonably well over the 3+ years I have been exposed to your work.
[Fire Original Android Development] t3chwizard:
Could you upload that to Google drive or something then? Or a zip file on AFH?
[Fire Original Android Development] melvinaury:
Can someone confirm if Nitro Nation game work on your tablet. After the last game update I can't play the game. I already uninstall and install again, but continue with the problem. The developer indicate that it should work..
[Fire Original Android Development] steve8x8:
I'm running the same (Sep 28) rom, and have some working *m*zon services.

I have sideloaded:

- Amazon Music_6.5.3.apk

- Amazon Shopping_10.9.0.100.apk

- Amazon Kindle_4.2.0.101.apk

The first two worked right out of the box (I had to "login" into my A account, of course). To get Kindle working, I had to start logging in with (it seems) a random password, then wait for an email containing a one-time password, then finish the login.

I was able to download my purchased music, and a number of books from my shelf, and browse my wish lists in the shop.

Now don't ask me where I got those apks - probably from TiBackups of rooted fireOS devices...

I like to run Music in the background - now if Davey could explain how to accomplish this with a strict "don't keep activities" policy... (thanks)
[Fire Original Android Development] DB126:
- Amazon apps can be downloaded from the Play Store or APKMirror

- background playback works fine with "don't keep activities" policy active
[Fire Original Android Development] yochananmarqos:
Just as an FYI, Amazon asked APK Mirror not to host their apps anymore. They haven't been there for quite some time now.
[Fire Original Android Development] DB126:
Some still are although versions may be dated. Best to grab from Play Store if available. Kindle and Music are there and current as are a couple different shopping apps depending on display size. In the past I found the tablet app to be lacking but Amazon may have fixed that in more recent builds.
[Fire Original Android Development] SanctusSua:
I have installed Lineage a few months ago on my Fire. The "About tablet" screen shows it as "12.1-20170802-UNOFFICIAL-ford". It's working (mostly) great, but for some reason my own app (which works on other devices) cannot wake up the device with a "wakelock". Is this somehow blocked? This build has a really low power consumption, so could it be possible that wakelocks (which CAN be used to greatly increase battery consumption) were disabled/blocked?
[Fire Original Android Development] t3chwizard:
[MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] DB126:
I doubt any overt actions were taken by the Lineage team to block app wakelocks. More likely you are running into a kernel obstacle. Suggest backing up your device and installing Fire Nexus which is pure AOSP. If your app behaves the same way it is probably device/kernel related. Not much can be done about that.
[Fire Original Android Development] SwitzXXL:
I replaced the stock root with SuperSU root but if I flash Lineage over, SuperSU is deleted and build-in root automatically exists?
[Fire Original Android Development] DB126:
Yes, assuming a system wipe is performed prior to updating Lineage. Include SuperSU zip in update or install SuperSU from Play Store after updating LOS.
[Fire Original Android Development] SanctusSua:
You were right, switching to AOSP fixed the problem. Curious, but at least it's resolved :)
[Fire Original Android Development] Dakotalee24:
Just because amazon restricts it doesn't mean that ggow couldn't take that source code and reverse engineer it a little bit to get it to work with this older tablet. Im not a programmer so I dont know specifics but I dont think amazon can put in to many restrictions to force a version of android to only run on certain hardware.
[Fire Original Android Development] DragonFire1024:
He probably could get it to work, but he already working on these two. It's not easy doing this especially on these Amazon tablets. Samsung does the same thing with their phones and devices. They just don't pretend it's their own operating system and don't butcher Android as much.
[Fire Original Android Development] DB126:
Highly impractical given bootloader (thus custom Amazon kernel) is locked with Android 5.1 era binaries. A maintenance nightmare even if possible.

---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------

Not to mention nearly a dozen other custom ROMs on a variety of Amazon platforms and likely other projects that are not so visible. IRL anyone?
[Fire Original Android Development] Dakotalee24:
For us users with a unlocked bootloader that never upgraded to the locked version, we still have the possibility of nougat on this device. However ggow seems to be the only dev still interested in developing for this tablet. So its kinda solely up to him if its worth the challenge. We could theoretically still run the new nougat fire OS 6 on top of our old bootloader couldnt we?

---------- Post added at 11:20 AM ---------- Previous post was at 11:18 AM ----------

I really wish google would make it a thing that forbid companies and carriers from locking bootloaders. I purchased the hardware. Let me run whatever I want on my device and dont give me a warranty if thats what it comes to.
[Fire Original Android Development] DB126:
Bootloader remains locked. Assuming your device is rocking a 5.0.x generation bootloader it simply has a vulnerability that permits a custom recovery (eg: TWRP) to be booted. Nothing more.

While some would like that it makes little sense from a business perspective. Amazon and others would have little incentive to produce affordable gizmos if third parties could easily unlock and repurpose the device. Not to mention the security implications. As evidence look at the market for unlockable devices in general and tablets in particular. Not a lot out there. There's a reason for that.
[Fire Original Android Development] ggow:
The source code I will not post, it's massive and very specific to the Amazon Fire. I have stripped out every project that is not required for compilation due to the Amazon binaries providing what we need. I have made mods/optimisations across the rest of the sources targeting mediatek specific stuff. Therefore the sources will be not usable for your qualcomm powered phone.
[Fire Original Android Development] DragonFire1024:
Does the same apply to the 8.9 HD? I've recently discovered them and have fallen in love. It has TWRP and a custom ROM. The 8.9s have Ice Cream Sandwich 4.0, but I run 6.0 now. Really amazing tablets.
[Fire Original Android Development] duckwizzle:
So I've been using OPs (now deprecated) unofficial CM 12.1 ROM for over a year now. Other than security patches, am I missing anything major by not using this? Performance wise, is this ROM better ?
[Fire Original Android Development] DB126:
There are a few incremental refinements but no major new functionality. That said I would consider updating as there is no need to wipe personal data and apps.

---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------

I know nothing of HD 8.9 mods. I am quite familiar with the HDX line; bootloader can be unlocked on 3rd gen devices (but not 4th gen).
[Fire Original Android Development] ceanth:
Hi guys, I made a switch from the AOSP ROM to this ROM and I really like it.

I have also installed the L-Speed app but does anybody have any recommendations on setting up this app to work best with the free tablet?

---------- Post added at 09:42 PM ---------- Previous post was at 09:36 PM ----------

Fire tablet
[Fire Original Android Development] DB126:
Most tweaks are usage dependent, especially on a low RAM device with a modest CPU. I have turned several knobs that align with my own interests but many would be detrimental in other scenarios (eg: gaming). A few universal tweaks worth considering are "improved scrolling" and reducing all animation scales to 0.75x or 0.50x.
[Fire Original Android Development] ceanth:
Cool, I will play about with it.

Additionally, I am unable to change the CPU Governor. My device is set to hotplug so I used kermal auditor app to change it to interactive the device reboots after a short time so not sure if changing CPU Governor is not possible with this device.
[Fire Original Android Development] DB126:
Stock kernel only supports a couple governors; interactive is not one of them despite being listed. Hotplug is a good choice for this device. If you want to go further there is kernel overlay package you can flash here. While knob turning is fun (qnd a great source of placebo pleasure) there is little measurable benefit to be gained given the humble hardware specs.
[Fire Original Android Development] DragonFire1024:
Not sure how well this build of Lineage takes to anything lower than .25x. in my experience a lot of ROMs don't like when you go to 0x. I've experienced pixilation and screen flashes when going to 0x in Fire tablets.
[Fire Original Android Development] DB126:
Would not recommend anything below 0.50x which is fairly aggressive on most devices. Hardware capabilities far out weigh ROM variations/tuning.
[Fire Original Android Development] Y314K:
When wanting to start from a fresh install from an old ROM using the latest FlashFire v73. Is there any reason not to include the "Internal Storage" (sd card) & Cache partition in the wipe ? Trying to start as fresh as possible. I keep everything I need on my external SD Card. So want to empty my non-external storage.
[Fire Original Android Development] DB126:
There are no dependencies on the contents of internal storage provided files to be installed (flashed) reside elsewhere.

Be aware FlashFire occasionally has difficulty reading from external storage which is likely device related. Worst case is you would need to reload FireOS from stock recovery and start over.
[Fire Original Android Development] Y314K:
Just to make sure I understood correctly. The two parts I mention can be wiped at will for a clean install. Nothing resides @ internal storage or cache that should mess things up.

Also my tablet was one of the lucky TWRP capable. But the drivers on my PC are not letting me see it to boot to TWRP since I flashed a few ROM's. How can I still check it is still TWRP capable when all the ROM's we install list FW at 5.1.1?
[Fire Original Android Development] DB126:
Flashed (custom) ROMs for this device do not impact bootloader capabilities. Bootloader remains at 5.0.x provided you didn't sideload a build of FireOS > 5.0.1 without taking appropriate steps to preserve the original bootloader. In short, device remains "TWRP capable" if you have only flashed custom ROMs.

You can safely wipe all partitions exposed by FlashFire with the caveats noted in my earlier post.
[Fire Original Android Development] Y314K:
So had a problem after I installed BusyBox Pro. I lost the built in Lineage Root. Couldn't get it back no matter what I tried. Which meant FlashFire would not work anymore. Luckily my tablet can do TWRP. And I was able to fix the driver probs I was having using the Kindle drivers exe. I was able to reinstall Lienage thru TWRP without having to reflash the Amazon FW. This time I included the latest SuperSU Pro .zip installer. This time BusyBox Pro didn't loose Root for me. XPosed is working fine too. The only part I haven't tested is SUHide. Might try it next time I reflash or update.

Thanks [MENTION=5749760]ggow[/MENTION] & [MENTION=5488402]Davey126[/MENTION].
[Fire Original Android Development] Y314K:
Forgot SUHide is for Android 6 and above. So won't be trying that.
[Fire Original Android Development] xenokc:
Great ROM. Hope to see update with Nov security patches.
[Fire Original Android Development] facted:
Also have the amazon logo boot loop. Can you point me in the right directino on sideloading original ROM?
[Fire Original Android Development] DB126:
See forum index for links: https://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Original Android Development] empathyislost:
by default there's no root on this ROM, correct? Super Mario Run and Snapchat have issues with Root even when attempting many different hide methods. I'd be happy with just Lineage and no root!
[Fire Original Android Development] DB126:
ROM has integrated root which is disabled by default (toggle lives under developer options). Many apps that are 'root sensitive' detect the su binary regardless of whether root is enabled.
[Fire Original Android Development] FredBloggs13:
My Fire is on OS5.6, can I still flash this ROM?
[Fire Original Android Development] steve8x8:
If you can root, and run FlashFire, yes.

Note that the sentence starts with an "if".

At the moment, the first prerequisite cannot be met though (last rootable version is 5.3.1, and there's no known rollback from 5.3.2.1 and later), thus the answer is no.

Whether 5.6 can be rolled back to 5.4.0.0 is yet unknown - there's no known download location. Probably not. They have been closing backdoors, and now they are sealing the windows.

BTW, there are dedicated threads for rooting Fire7's...
[Fire Original Android Development] Munns86:
I'm stuck in a similar situation. I also lost root but unlucky as I don't have TWRP so I'm not sure how to gain root back. Not sure if I should just start with a factory reset.
[Fire Original Android Development] Y314K:
From what I understand. If playing/toggling the developer options on and off & rebooting the phone doesn't work. Then your only method is to flash the same version of Amazon's FW you started with. And Re-Root from scratch using the Utility.

I think I tried a factory reset but it didn't bring root back. You can try it though. I think the recovery options on the newer FW can only flash official Amazon FW.
[Fire Original Android Development] Munns86:
Shoot! But thanks for the info.
[Fire Original Android Development] Y314K:
Wait to hear from [MENTION=1434990]dave12[/MENTION]6. He is more of an authority on this. But that is what I remember in my research & experience.
[Fire Original Android Development] DB126:
Unfortunately, [MENTION=1449438]Y314K[/MENTION] is spot on. Without the benefit of a custom recovery (eg: TWRP) the only remedy is to reinstall FireOS and start from scratch. Be cognizant of the FireOS build being sideloaded which must be equal to or greater than the version that was last on the device (but no higher than 5.3.1).
[Fire Original Android Development] TheLoonyRebel:
Couldn't one just use the TWRP we have right now (via using the fastboot method) and do either a dirty flash or at the least a new clean install of the current Lineage we have to get root again?
[Fire Original Android Development] DB126:
Keep in mind those who received (or allowed an OTA upgrade to) FireOS 5.1.1 or above can not boot a custom recovery. Guessing <5% of the members who participate in this forum have a device that is capable of booting TWRP.
[Fire Original Android Development] Munns86:
Thanks for the info! By any change on the device is there a way to find out which version I last had of FireOS?
[Fire Original Android Development] DB126:
Not easily. If uncertain go with FireOS 5.3.1 which is the highest version that can be rooted at present. This will minimize the risk of a brick while carrying no inherent disadvantages. Be sure to protect the device from an inadvertent OTA update by maintaining network isolation or other means. If a FireOS OTA is received/processed you will permanently loose the ability to reroot the device.
[Fire Original Android Development] TheLoonyRebel:
Very true. But for those like myself and you if we lose root somehow on Lineage the method I suggested should work with little to no issues.
[Fire Original Android Development] DB126:
Absolutely. Unfortunately, not applicable to the member who asked.
[Fire Original Android Development] vorcers:
I also had to deal with loosing root. Have you encrypted your fire?

When I encrypted the fire, the root was lost after the 2nd or 3rd reboot. I have three unencrypted fire's - two with stock root and one with SuperSU. All running fine.

Please note, that I am still using the old cm12.1 Version from 2016. But if you encrypted your fire, I would give it a shot and reset it completely. By reset, I mean a factory reset via the recovery.
[Fire Original Android Development] t3chwizard:
I wouldn't try to encrypt a device that doesn't let me install a custom recovery but that's just me
[Fire Original Android Development] nirogu325:
I do not suggest encryption on this tablet at all because the SoC doesn't support AES hardware acceleration. Do so at the cost of your device's performance/battery life. *Source: Google Search and personal experience.

I think you meant you cannot decrypt inside TWRP. We've never been able to install a custom recovery.
[Fire Original Android Development] DB126:
Fully concur...unless security trumps performance (in which case one has to ask if this is the right device to be holding such sensitive information).

... or those fortunate enough to be able to boot a custom recovery (ie: early 5th gen builds with 5.0.x bootloader which are few and far between).
[Fire Original Android Development] steve8x8:
Only if you still have access to it and root - the bootloader partition contains a timestamp of the form "8 digits - hyphen - 6 digits" which identifies (can be mapped to) the version of fireOS. Since bootloader files will not be overwritten by installing a custom ROM, this information is even available when you run LinOS or Nexus.

If you already lost root access, it's too late, obviously.

(My devices are marked with the fireOS version on the back... better safe than sorry.)