yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
All contemporary Amazon devices are locked down. The HD 10 can be rooted by clever individuals but there is no custom ROM support at present. If you want something for the kids consider a carrier branded pre-paid Moto phone from Walmart which will run circles around a Fire 7 or HD 8. Just pull the SIM and don't activate. Makes a great WiFi only gizmo with full access to the Play Store. If hooked on tables consider a used Nexus 7 or a 2nd or 3rd gen Fire which can be unlocked and support custom ROMs.

To speed up your existing gizmos reload/sideload the latest version of FireOS via the stock recovery menu to give them a fresh start. You can also downgrade to FireOS 5.4 and partially debloat. Several threads in the general section outline the process. Good luck.
[Fire Original Android Development] DragonFire1024:
I assume you meant the HD 8 can be rooted by clever individuals? You don't need to be clever to run a one click root app :P
[Fire Original Android Development] t3chwizard:
I use Titanium Backup Pro to freeze apps whenever I have to. It has worked without failure for me. Maybe give that a try? The pro version is reasonably priced too.
[Fire Original Android Development] DB126:
While Titanium is a good product there are a number of well regarded free apps that can disable/freeze and enable/unfreeze installed apps. I mentioned one in a previous post on this topic but there are many others. Of course, hiding is another option although that won't stop background activity and the associated resource consumption.
[Fire Original Android Development] t3chwizard:
Yea, but I swear by titanium lolol. It has saved me on so many occasions and is now a must have for restoring apps and backing up as well. If those free alternatives work though, then by all means feel free to use them.
[Fire Original Android Development] drotheb:
Hey guys, I am trying to get my Fire HD on 5.1.1 running Lineage to work with GPS Tether over bluetooth(tethered to my phone) and I am having no luck. The Wifi/Hotspot tether options work, but when connected and both devices saying they are sharing location, I can not get a GPS fix on the tablet(Using OsmAnd or Mapfactor nav apps)

I read lots of threads of people not having issues with Bluetooth GPS tether so I'm wondering if it may have something to do with the rom? Mock locations are enabled, gps services are enabled, but no luck. Any one have any ideas?

Thanks!
[Fire Original Android Development] DB126:
This thread targets 5th/7th gen Fire 7 devices vs 4th gen Fire HD. You may have better luck posting your question in this thread.

On a personal note I didn't have much success with this app when last tested on CM 12.1 in late 2016. Symptoms were similar to yours. I did prototype a USB GPS receiver which worked fine. I believe there is a Bluetooth varient of this device which would be a better fit for your intended use. Good luck.
[Fire Original Android Development] drotheb:
I believe it is a kindle fir 7, 5th gen? At least it is according to the results I get from googling the first 4 of the serial number G0K0.

Any ways, thanks for the feedback. I wonder how the folks saying it worked for them got it. Maybe they were just on the stock fire rom?
[Fire Original Android Development] sd_shadow:
Serial 5th gen should be A000

---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------

See Fire Index: Which Amazon (Kindle) Fire Do I have?
[Fire Original Android Development] drotheb:
Or any number of the 100 other SNs for a 5th gen work also, including mine. Unless all the references I am finding are wrong.

https://iristech.co/how-to-find-your-kindle-model/

Any ways, back to the GPS bluetooth tether! Any one else try using a bluetooth GPS tether app using Lineage?
[Fire Original Android Development] DB126:
While waiting for a response you may want to reach out to the developer (see previously linked thread). He/she has been responsive in the past and often has suggestions when things aren't working as they should.
[Fire Original Android Development] drotheb:
Okay great, I'll do that, thanks.
[Fire Original Android Development] riverstyxxx:
SuperSU isnt compatible, I've clean installed onto two tablets and it says "Su Binary Occupied". I've enabled root in developer options, and rebooted. Nothing helps. Otherwise, great job. I like how animated wallpapers are working as opposed to fire nexus. Looking forward to future updates as needed.
[Fire Original Android Development] rwbonesy:
SuperSU has issues in general lately as was discussed earlier in this thread. For now just use the Lineage's root feature + privacy guard i guess?
[Fire Original Android Development] DB126:
Well known issue with the latest SuperSU builds on numerous device types; Android 5.1 ROMs are particularly vulnerable. To remedy a full device wipe and fallback to SuperSu v2.79 is required; the latter will immediately attempt to update to 2.82 which still has the problem. Rather than dip your head into boiling oil just use Lineage's native root manager accessible under developer options. Works a treat.
[Fire Original Android Development] riverstyxxx:
I've uninstalled and took your advice, everything's functional with their root manager. Only problem is the # logo is still there in the upper-right corner on both tablets, no matter what. On the other side, this rom is working very nicely; I'm glad to have live wallpapers back and the icons are big.
[Fire Original Android Development] DB126:
There are ways to ditch the persistent root icon (#) via Xposed Framework if truly bothersome. Note it only appears if an app has actively requested root permissions; sometimes that's good to know. If you want further control over icon size consider the well regarded Nova launcher which plays nice on this device/rom. Easy to install/uninstall with no lasting side-effects.
[Fire Original Android Development] dctan:
Before I install lineage 12.1. Can someone tell me the miracast able to use after installing lineage 12.1? the previous CM 12.1 was not able to do so.....
[Fire Original Android Development] DB126:
Unlikely (at least reliably) due to hardware and/or kernel restrictions. Casting in general is problematic on these devices.
[Fire Original Android Development] ggow:
Miracast should work fine.
[Fire Original Android Development] DB126:
Stand corrected...forgot this ROM uses older Amazon kernel/"blobs" that seem to have better (albeit imperfect) Miracast compatibility.
[Fire Original Android Development] dctan:
Thanks for the reply, will try it out today, feedback later.......
[Fire Original Android Development] Dishe:
I actually have a handful of old phones including of those Walmart Moto E4's before they made them difficult to unlock. We we go on trips they use them as cameras and with a freedompop SIM card they can stay connected to the rest of the family. But at home, tablets serve a different purpose- I have 2 daughters close in age that read together, play games together, watch videos together, etc. Phones are too isolating, I found the kindle fires were a compromise between a phone and a laptop. Now I'm mostly just trying to salvage the hardware I have left over, but if I need to move on, so be it.

Funny, I used to have a 2nd gen Fire 7HD (Tate?), and it was pretty great running Cyanogen if I recall correctly, before I fried the USB port and corrupted the memory in the process. Maybe I should pick another one of those up on ebay. I totally forgot about those, thanks!

This is worth a shot at least. But curious- if I can downgrade to 5.4, is the issue that I need to go back earlier to get twrp/custom roms etc?
[Fire Original Android Development] DB126:
Tate and Thor (3rd gen HDX) are fully unlockabke and have a decent custom ROM selection. My Tate remains on CM11 and still sees occational use. I am penning this on a 7" HDX running Lineage 14.1. Great device that only now is feeling a bit long in the tooth. In my portfillo of gizmos Tate and Perry remain my daily drivers. I love stuff that just works.

Downgrading below FireOS 5.3.2.1 will trigger an efuse that permanently bricks the device. There is no advantage dropping below 5.4.0.0; a safe landing space for those who wish to debloat. I'd advise against it in your case unless willing to invest substantial time turning knobs and dials. An iPad or Windows based slate may be your best choice as those platforms will grow with your daughters needs/interests until ready for their own devices. Good luck.

---------- Post added at 01:11 PM ---------- Previous post was at 12:44 PM ----------

I may have missed out on the latest developments - last I knew 5th-8th gen HD 8 devices running any FireOS build can not be rooted short of breaking out a soldering iron. Please provide a link if mistaken. Thanks!
[Fire Original Android Development] DragonFire1024:
You are correct. Hard mod root the current HD 8. May even be able to go as low as the 2016 model. https://xdaforums.com/hd8-hd10/orig-development/root-hardmod-root-amazon-fire-hd-8-7th-t3851617

Until I can get a few more puzzle pieces together, or I find another surprise, we've got a bunch of half working theories at best for root. I may have found something last night that needs investigation.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 18 December 2018

- ASB December 2018 patches (sec. string 2018-11-05)

- Fix of 'adb root' bug (see LineageOS announcements)

- Addl. fix of CVE-2018-9531, CVE-2018-9536 and CVE-2018-9537 from November ASB, which are flagged Android 9 only, but also apply

- Backport of CVE-2017-15835 (skipped in November ASB)
[Fire Original Android Development] EtoileLabrie:
I am really enjoying clean Lineage in the fire. Before I order a USB-OTG cable can I ask the users if OTG works or not? thanks
[Fire Original Android Development] DB126:
It does provided expectations are kept in line with device/interface capabilities. Anything with a high draw (eg: spinning platter) or high I/O probably won't work well if at all.
[Fire Original Android Development] EtoileLabrie:
Thanks. I always use a 'powered HDD enclosure' for all my SSD/HDDs - too tired of them crashing while connecting to a raspi...
[Fire Original Android Development] DB126:
Yep - keep in mind power source must be external or self-contained. Max throughput will be limited by device/interface capabilities and may behave erratically on sustained transfers. Suspect you are not planning to use the drive in that fashion; just wanted to put out the caveats based on personal experience.
[Fire Original Android Development] uklz:
Hi!

I have purchased a used Fire 7 (2015) with CyanogenMod 12.1-20160311-UNOFFICIAL-ford already installed.

Can I simply use the instructions listed under 'Fresh installation from FireOS or other ROM FlashFire >= 0.58' to install this ROM instead?

Thank you!
[Fire Original Android Development] melvinaury:
Yes you can, but need to change year to like 2016 to use flashfire. I recommend a full wipe
[Fire Original Android Development] yochananmarqos:
Might as well try booting TWRP first just in case the original Amazon ROM was old enough. No reason to use Flashfire if you don't have to.
[Fire Original Android Development] melvinaury:
I really forgot to as if you're tablet had TWRP recovery.
[Fire Original Android Development] melvinaury:
I just install new version, with a full wipe from the 1 year old ROM. What I see is that Titanium backup, Candy Crush and google notifications are blocked on lock screen. I check thru the menus and both apps had access to lock screen notifications. How I unblock an app to be able to show notifications on lock screen
[Fire Original Android Development] melvinaury:
Forgot to add a screenshot, with notification for Candy Crush bocked
[Fire Original Android Development] melvinaury:
The Notifications are allowed on lock screen
[Fire Original Android Development] DB126:
TWRP can be booted if your device is an early build with bootloader 5.0.0/5.0.1. Otherwise, you'll need to use FlashFire which is has become rather problematic and is no longer supported (developer retired). Read the thread for details. You might just be better staying on CM 12.1.

---------- Post added at 02:08 PM ---------- Previous post was at 01:50 PM ----------

Odd given the full wipe (unless you restored apps/data from prior build). Try clearing app data on one of the 'offenders' from the settings menu.
[Fire Original Android Development] melvinaury:
I restore all my apps with TIBU, I test wiping the date of one of the apps and reply back.
[Fire Original Android Development] yochananmarqos:
It's better to restore data separately after you open the app once, otherwise you may run into weird things like that.
[Fire Original Android Development] edgarperez:
GAPP Crashes

I have installed the ROM in my Kindle Fire (model: KFFOWI) but when trying to install the gapps (open_gapps-arm64-5.1-stock-20181222) it gives the following error:

# Begin Open GApps Install Log

------------------------------------------------------------------

------------------------------------------------------------------

# End Open GApps Install Log

INSTALLATION FAILURE: This Open GApps package cannot be installed on this

device's architecture. Please download the correct version for your device.

# Begin User's gapps-config

# End User's gapps-config

I am installing a 5.1.1 gapp version so I dont quite get why the version is not the right one.

o
[Fire Original Android Development] nirogu325:
You're installing the wrong version. Choose ARM, not ARM64. This is a 32-bit device, not a 64-bit one. Also, you'd do yourself a big favor choosing a smaller package like Pico and go from there. Starting with a huge one will only bog down your device's performance severely down the line.
[Fire Original Android Development] grr8:
Hi, can I flash Lineage over FireOS 5.3.6.4? My Fire upgraded itself after connect to wifi by mistake. Originaly it was on 5.1.1. Stupidity.

Thank you
[Fire Original Android Development] DB126:
Nope - you are permently stuck with FireOS unless: 1) a root solution is found for FireOS > 5.3.2; and 2) custom ROM support is extended to newer builds.
[Fire Original Android Development] Herox:
Upgraded my rom as instructed and now it's bricked. That sucks.
[Fire Original Android Development] platypoid:
Can you boot into recovery ?

If you had adb debugging enabled and plug it into your computer and do adb devices ( if you have adb installed) and it shows the serial number you should be able to get it back to life by side loading original amazon rom .

I did an update and thought it was a goner but was able to mess around and bring it back to life and then root and install Cyanogenmod again - was a lot of messing around but worked and as many people have advised -- if you have something installed and working don't try to update it because there are bugs - unless you have a very early version with TWRP installed then updates or different roms are possible.
[Fire Original Android Development] grr8:
Damn,

I was so full of hope as I fastbooted twrp with "ok" at end.

I guess there is no way of removing Amazon bloatware and lockscreen ads.?

Thank you for reply.
[Fire Original Android Development] DB126:
So it basically ignored the command: fastboot boot <twrp.img>? Interesting as earlier FireOS builds rejected the boot parameter with an error. Same outcome, just a different response.

You can rollback to FireOS 5.4 and remove bloatware via script. Also possible to clobber lockscreen ads, install a different secondary launcher and perform some other high wire tricks. There are several threads elsewhere in the forum that describe techniques and trials. Plan on reading, effort and patience.

Oh yeah, essential Google services and the Play Store can also be sideloaded, no downgrade necessary.
[Fire Original Android Development] Herox:
Nope, no recovery. I don't know why but since I initially rooted it's had none recovery. I could never get twrp on it. Honestly it's old anyway. I was going to give it to my 3 year old to get him into using things like it without breaking it. Is what it is.
[Fire Original Android Development] platypoid:
adb acknowledgement is not the same as recovery and twrp is not needed to do adb side loads . Question again is when you plug it into a computer is there any acknowledgement of the device ? I don't know the exact process I used - it is described somewhere on the forums here on how to possibly bring it back. I will try to look up my old post to refresh my memory of exactly what I did to fix mine when I thought I bricked it.

Here is the post I made when I thought I bricked it and what I did to get it back

https://xdaforums.com/showpost.php?p=74879345&postcount=400
[Fire Original Android Development] Herox:
It sticks to the Amazon logo. I did as the tutorial said, added the newest to ZIP OTP, wipe dal and cache. It came up with mount errors and then when it rebooted it stuck at an amazon logo. During install it showed Samsung logo twice though. So all it will do is get an amazon logo. Holding Volup+power does nothing for it.
[Fire Original Android Development] platypoid:
I had to restore original Amazon . I think I did that via a tool that does it - if you read my post again you will see I was stuck on the screen like you were. I don't remember where that tool was to restore original amazon - I think same place you get supertool.

Look for Firmware Downgrade to Fire 5. 1. 2 Supertool - I think that is the one but double check
[Fire Original Android Development] Herox:
But do I need recovery mode? Because I can't use it if so.

---------- Post added at 02:50 PM ---------- Previous post was at 02:16 PM ----------

Yea it just says waiting for device. I cant get the kindle into any kind of download mode so, no dice.
[Fire Original Android Development] platypoid:
Watch this

https://www.youtube.com/watch?v=RQLoH-ahjy4
[Fire Original Android Development] Herox:
See, he puts it in recovery mode. My Kindle has a bricked recovery. No matter what I tried it wouldn't flash recovery. I can't do this sadly. She's borked. It's okay.
[Fire Original Android Development] platypoid:
Do you have adb installed on your computer ?

open cmd on your computer

type in

adb devices

if your fire shows up and shows a serial number

then type

adb reboot recovery

and see if that does it
[Fire Original Android Development] DB126:
Let's put this to rest. No recovery = game over if stuck on boot logo. Stock recovery was borked by some early FlashFire builds (prior to 0.32) which poster likely used 3+ years ago. Rather unfortunate.
[Fire Original Android Development] Herox:
That would be it. I figured that was the answer. It's fine the thing is 3 years old and slow as dirt. But it was a nice gesture to try and help.
[Fire Original Android Development] DragonFire1024:
You would be surprised what swap memory will do to speed up lower end, older devices. Apps2sd allows you to create a swap file or partition on external storage. It dramatically improves performance. I have one on most of the devices I use.
[Fire Original Android Development] DB126:
Absolutely! I typically place swap files in the underutilized cache partition. Depending on workload and device setting swappiness between 20 and 60 usually works best. Tweaking dirty ratios can lead to further refinements on some devices but are largely ineffective on low end Fires (won't go into detail here). The major point is swap helps (dramatically) on devices with <2GB of of RAM and can. Both ZRAM and a traditional swap file.
[Fire Original Android Development] chris-89:
Can you explain in detail please how you set up the swap file in the cache partition and maybe also the other tweaks you did?

The would be nice :), because my Tab is sooo slow :(
[Fire Original Android Development] DB126:
Quick overview:

- device must be rooted

- install Apps2SD app (from Play Store)

- launch and select 'Swap Manager'

- use slider to set swappiness to 25

- tap '+' icon in upper right corner

- key in 200 MB for size

- leave priority at '0'

- select 'cache' from folder list

- tap 'ok' to create swap file

- use small slider to enable newly created swap file

- tap 3-dot (overflow) icon in upper right corner

- change swap priority for the existing ZRAM swap file to '1'

Let's see where that takes you. There are a few other relatively simple tweaks that make a significant difference; topic for another day.

Keep in mind this device will never be a race horse or multi-tasking monster; it is a low end tablet with minimal resources. Keep it simple, swipe away unused apps, reboot when things get sluggish (usually due to exhusted cache space).
[Fire Original Android Development] ajislav:
No root on TWRP capable ford

Hi, I have two tablets both running the november lineage build:

1) 5.0.1, i.e. TWRP capable, has problems with root (root was lost during a previous Nexus rom install), Lineage ROM was installed using Flashfire - this is my test tablet where I always have an easy way back

2) 5.1, no root problems, Lineage ROM was installed using Flashfire - this is the tablet where I want to avoid going back to FireOS.

Any suggestions how to fix the root problem on the first tablet? Surely there must be a simple way, if I can TWRP.

Regards ajislav
[Fire Original Android Development] DB126:
From TWRP wipe system, dalvik and cache partitions. Leave data partition alone. Reinstall Lineage, your prefered GAaps package and (optionally) SuperSU 2.82 SR5.
[Fire Original Android Development] chris-89:
Thanks a lot :good: i set it up like this.

Lets see how it is with this setup.

I'm looking forward to the other tweaks :)
[Fire Original Android Development] ldeveraux:
Hey Davey,

I setup Apps2SD on a new install of Nexus, should it work the same as Lineage? Whenever I boot the device it says:

"2nd partition was not mounted some apps might not be detected. A soft reboot is required to mount."

then:

"You can fix this issue by recreating mount script with "I've su.d support on my device / I use Magisk interface" mount method"

We can't have Magisk, so I have the latest SuperSU build. Any clue what to do?
[Fire Original Android Development] DB126:
Hi [MENTION=1360535]ldeveraux[/MENTION],

No immediate worries regarding that message. It pertains to moving apps from internal storage to a specially formatted partition on the SD card which we aren't doing here (although you certainly can use that feature if running short on internal storage!). You can usually eliminate the boot message by selecting the option that you quoted above - even when using SuperSU. Or simply ignore it while testing the swap tweaks. If neither works to your satisfaction there are other workarounds.

As an aside ...

If expanding swap seems to help but you still experience lags waking from sleep there's a fix for that. Basically involves toggling off Google Sync for 1-2 min which reduces the activity spike when waking a 5th gen Fire that has Play Services installed. I'll write something up if there is sufficient community interest.
[Fire Original Android Development] ldeveraux:
After a refresh to stock Nexus, and applying the swap, this thing isn't laggy in the least. I also removed a bunch of larger sized apps, specifically Gapps that I wouldn't really need on this tablet. So for now it's going swimmingly. I'll let you know when I can play more with it if I run into problems.

Regarding the message, I went in and just mounted the links as it asked and I think it fixed it? No clue really. How do you know if the swap is using the cache or the zram? In the Swap Manager, I have both zram0 and the cache active, with the cache priority=0 and zram priority=1. Is that right?
[Fire Original Android Development] Neffy27:
Well, don't stop there [MENTION=5488402]Davey126[/MENTION]. Want all the tweaks!

This device is my movies/music player when I travel for work, lots of travel.