yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] nirogu325:
So far while setting it up, Settings crashed just once opening Home but hasn't crashed again. Sadly, automatic LiveDisplay does not work here as well (didn't work in the past October CM build I had), you have to manually toggle it. I just finished setting everything up. The rest is working like a stable build so far. Will let you know if something happens down the line.

What I did:

- Clean flashed thru TWRP

- Flashed the kernel modules, micro OpenGApps, Xposed & V4A

- Cleared journaling from /data & /cache

- Turned off KSM and set up the I/O Sched and governor with Kernel Adiutor

- Slimmed up the ROM and the GApps (current TWRP unable to run AROMA)
[Fire Original Android Development] tonibm19:
I did the

Fresh installation from FireOS or other ROM FlashFire >= 0.57 coming from CM12.1

During the flashing, there were errors of couldn't unmount system, resource busy and things like that.

Now my tablet is stuck on the amazon logo. ;(
[Fire Original Android Development] tobyxx:
I guess i had the same error about two weeks ago while going from cm to RR. If you can access stock recovery you need to sideload the original fireos version your tab was running before you installed a costum Rom. There is a tuturial here on xda, can't look for the link right now.
[Fire Original Android Development] DB126:
Couple thoughts:

- inability of LiveDisplay to switch automatically is common to most CM/LOS 12.1 builds, especially on devices that lack a physical GPS or do not utilize Google Location Services in 'High Accuracy' mode; seems the function uses location vs the clock to to determine on/off times

- custom kernel modules are not demonstrated to work with this ROM although there is absolutely no reason to believe there will be any conflicts
[Fire Original Android Development] ggow:
I'll look into this before next update
[Fire Original Android Development] DB126:
Another hour of configuration/use did not surface any gremlins. I am always surprised how snappy this device can be under the right conditions given modest specs. Hardware definately likes the deadline scheduler augmented with a 5 sec write delay. Tweaking animation scales under developer options also has a nice effect. Lineage hummed through all that and more without glitching.

Other notes: WiFi connects/disconnects reliably. ROM sleeps as it should with minimal idle drain. Rotation fast and reliable. Bluetooth uneventful.

This weekend I will push a little harder on various apps that sometimes upset the applecart. Given experiences to date not expecting any issues.
[Fire Original Android Development] ggow:
LiveDisplay, as I have come to understand requires modification to the kernel. So will be a no-go unless we find a vulnerability to exploit.
[Fire Original Android Development] nirogu325:
Gotcha. Minor stuff but do you remember that old image distortion whenever you turned off the screen? It's been a long while since I had a ROM with that and it's rearing its head again sometimes here.
[Fire Original Android Development] DB126:
Even with a kernel mod auto behavior may still be erratic without the benefit of full location services if numerous user reports are accurate. Apparently goes beyond simply obtaining sunset/rise info for current location as most phones secure the proper time/zone via network.
[Fire Original Android Development] ggow:
Yes, I remember that screen issue, will be fixed in the next release.
[Fire Original Android Development] nirogu325:
I forgot to tell you that it looks like the SDcard fix is not implemented. Several apps gave me trouble, including Titanium Backup (for write purposes) until I applied the SDcard Fix. I have all my backups in my microSD card.
[Fire Original Android Development] jeanett:
Hello thanks for your help, your advice was very useful, finally get everything installed and correctly, sorry so many questions, it was my first time with an android device, now I am happy and enjoying everything thanks to you.

again thanks and kisses from Venezuela
[Fire Original Android Development] xantiux:
Yet another update! Awesome!

Thank you ggow!
[Fire Original Android Development] t3chwizard:
[MENTION=5749760]ggow[/MENTION] just to be clear I am not asking for an ETA but in the next build will the blueborne exploit be patched (if possible)?
[Fire Original Android Development] ggow:
Yes it will

Already started patching the ROM.

Just taking time because it's busy with our little person needs 99% of my time :cool:
[Fire Original Android Development] steve8x8:
So there's 1 percent of non-quality time left :/ Take your time, and enjoy being with the little one, they grow up so fast :eek:
[Fire Original Android Development] t3chwizard:
Congrats if you had your child recently, or even congrats if it happened in the past!! Some day I hope to start a family.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 28 September 2017

- Ported relevant September Security Patches

- Includes all bluebourne patches
[Fire Original Android Development] idaknowit:
Thanks ggow, I had forgotten all about this tablet until now. Now if only I could get Directv Now to work, apparently it is not compatible with this tablet.
[Fire Original Android Development] ggow:
Download from apkmirror and try sideloading it.
[Fire Original Android Development] Pottkopp:
first of all thanks a lot ggow for all the effort you put into this rom. It works absolutely great.

There's just one downside for me. If you try to open files with the documentsUI the external SD won't be shown. If you try to hide/show the external SD it just hides/shows the internal storage (see screenshots). Is there any workaround for this? As some apps can't get permission to write to SD because of that...

thanks in advance

cheers

Pottkopp
[Fire Original Android Development] NeuromancerInc:
I would guess it's SafetyNet related. I have the same problem with Netflix. It's unfortunate as it can't be fixed with the current situation regarding the locked bootloader.
[Fire Original Android Development] steve8x8:
Absolutely great. If the Fire in question was mine I wouldn't hesitate to clean-upgrade immediately - but I've already given it to a close relative... What about dirty flashing (over 0912), with the corresponding nano gapps as before?
[Fire Original Android Development] ms372591:
I just used Flashfire and flashed the update and wiped davlik. I don't see any need to reload the g-apps.
[Fire Original Android Development] t3chwizard:
What do you mean when you say "not compatible"? If that means you cannot find it on the play store when on this device there are other methods around that.

Take a look here, I use an app called apkpure to get region locked apps

https://apkpure.com/p/com.att.tv
[Fire Original Android Development] idaknowit:
I tried DTVNow from apkmirror & sideloaded but it still doesn't work. While it opens up and you can see the guide, etc., when video should come up, it says to check on their site to see if this device is compatible with it. I've also tried hiding root, but no luck. Interesting however that Netflix does work.

---------- Post added at 11:55 AM ---------- Previous post was at 11:35 AM ----------

I also tried the one from apkpure, I don't think it's an issue of region lock, since I am in the USA.

The actual message I see is this:

"Find out if your devices are compatible, search Devices in the Help Center (Ref.#1005)"

On the DTVNow site, it mentions as being compatible with: Amazon Fire TV Edition Smart TV, Amazon Fire TV media player, Amazon Fire TV Stick, Android phones 4.4 and higher, and Android tablets 4.4 and higher.

So I'm at a loss here; maybe there is a thread elsewhere on this site with more information, if someone finds it, please post.
[Fire Original Android Development] t3chwizard:
Hmmm, maybe an Xposed module to spoof your device ID, model and such forth would do the trick? I use Xposed on this ROM and it works pretty well (I haven't tried spoofing the device ID and stuff though). It might work even better if you could spoof it to one of the known supported devices.
[Fire Original Android Development] xenokc:
Thanks for the update with Sept security patches.

FireOS6 based on Nougat has been announced. Is it possible those of us able to apply LOS will be able to get Android7 version of LOS at some point?
[Fire Original Android Development] DragonFire1024:
Don't hold your breath. I'll bet Amazon will limit their version of Nougat to newer, specifically 2017 models of their tablets. This would explain why they suddenly came out with all these new 7th generation models and the new HD 10.
[Fire Original Android Development] but-888-:
Hi,i Tried this Rom twice, but it seems i am Missing Something, gapps are not installed (yes i flashed them) and i am unable to install any apk (unknown Ressources is activate). Now on Nexus Rom and ITS Working,but would Like to try LOS.

THANKS vor any idea
[Fire Original Android Development] t3chwizard:
I wish there was something we could do to get them to allow us to unlock the bootloader. I would even pay $20-$50 just to unlock it if I had that option.

---------- Post added at 11:23 PM ---------- Previous post was at 11:22 PM ----------

You need to flash gapps preferably the nano (pico might work too but I used nano) gapps from OpenGapps
[Fire Original Android Development] DragonFire1024:
That's what I did to unlock the bootloader on my Motorola Droid Razr M, XT907. There is a company called 'Sunshine' that has the codes to unlock the bootloader a on that device. I guess we have to wait for either a big root, or a disgruntled employee formerly of Amazon to leak the codes.
[Fire Original Android Development] DB126:
Motorola's bootloader were designed to be unlocked with carrier agreement. Hence the databases of unlock codes tied to IMEI/MEID that were eventually leaked. In contrast Amazon has never offered the ability to unlock device bootloaders. Doubtful lists of unlock codes exist - or even a code generator.
[Fire Original Android Development] steve8x8:
Re Nougat on Fire (pun intended): *if* the Fire 7 (at least 7th gen) gets a newer kernel - that one would be signed in a way the existing old bootloader would accept? So it would be possible to flash the newer kernel (only), or would we have to get all the preloader/tee/littlekernel cruft - which would probably be even more hardened?

I'm definitely not holding my breath - with all its limitations, Lollipop serves this device very well, in particular when it comes in a LOS flavour ;)
[Fire Original Android Development] DB126:
Amazon would almost certainly include all the "cruft" to the level possible in an OTA update. That said, I see little/no chance FireOS 6 will come to this device. There is zero financial incentive for Amazon but tons of headaches. Most likely will appear (and be played up) in 8th gen devices when released.
[Fire Original Android Development] EtoileLabrie:
I have enabled "Root Access" > Apps and ADB. Despite this when I use

adb devices
List of devices attached
G0K0H2345522209T	device

shows me the device. But adb root says

adbd cannot run as root in production builds

any suggestions what I am doing wrong. I am at lineageOS 2.Aug.2017
[Fire Original Android Development] mrmazak:
"adb root" only works on "debug" or "eng" builds this is a "user" build.

Use "su" and then grant permission in the pop up on device.
[Fire Original Android Development] glockman4519:
Very nice update. All flashed through Flashfire just as expected and without any issues. One issue that seems to be a Google Playstore issue, is that Google Calendar will not install. All other Google apps that I tried to install from the PlayStore installed and is working as it should. Thank you for sharing.
[Fire Original Android Development] DB126:
Google Calendar and Games are often problematic when install from the Play Store on custom ROMs. A simple solution is to download from a 'trusted' site and sideload. Recommend APKMirror for downloads.

https://www.apkmirror.com/apk/google-inc/calendar/
[Fire Original Android Development] Gwheet:
ROM source code

Thanks for great ROM!

Is source code of this ROM available or it's closed?
[Fire Original Android Development] ggow:
It is just a folder on my pc, so not available online.
[Fire Original Android Development] DocRobbe:
By installing the Xposed module "Bright Lockscreen" this problem disappeared at my tablet. Perhaps you should try this...
[Fire Original Android Development] DragonFire1024:
Still haven't had this issue. Though I think I'm going to try the lineage ROM [MENTION=5749760]ggow[/MENTION] made.
[Fire Original Android Development] DB126:
Interesting. I have had this module installed for more than a year in conjunction with several ROMs by [MENTION=5749760]ggow[/MENTION]. I have not experienced the brightness issue during that time which I attributed to careful memory management. But perhaps the module played a role.
[Fire Original Android Development] DragonFire1024:
I just discovered this module myself but recently. Prior to,I still can't say I ever had the issue. Weird. Nonetheless great little module.
[Fire Original Android Development] t3chwizard:
I'm confused, this is the thread for the Lineage ROM is it not?
[Fire Original Android Development] eric93se:
how do we turn off the keyboard click sounds?
[Fire Original Android Development] t3chwizard:
Hold the comma on the keyboard and/or find the settings option in Language and Input for whatever keyboard you are using. For example I use AOSP keyboard for English so for me it is in the settings menu and then in "Preferences" turn off the "Sound on keypress option".

NOTE: The screenshot is from my Nexus 6, but the options should still be the same for AOSP keyboard and such.
[Fire Original Android Development] s.i.t.h.l.o.r.d:
After some time, I gave it another shot and this time, I did save my daughter's status manually and not through Titanium Backup. After switching to LOS 12.1 28092017, I re-installed HorseWorld 3D - Premium through the Play Store and restored her progress manually into the app's data directory. Et voila, it worked out nicely. I could start the game and it shows me her savegame with all the progress she has made so far. :good:
[Fire Original Android Development] DB126:
The discussion is relevant as it surrounds an issue that impacts all custom ROMs to different degrees.

---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------

Note there are related switches under settings->sounds->other sounds.
[Fire Original Android Development] t3chwizard:
No, I mean I was confused because he is posting in the Lineage thread saying he was going to install the ROM and I thought he already was using it but never mind
[Fire Original Android Development] eric93se:
Turning off the keyboard click sound does not work, tried toggling it, no change.
[Fire Original Android Development] DB126:
The two settings referenced above control all keyboard sounds on every Android device that I own. If still no joy try downloading/installing the Google keyboard from the Play Store.
[Fire Original Android Development] mrmazak:
Are you talking about the click sound or the heptic vibration. They are different settings.
[Fire Original Android Development] DB126:
Can't be the latter as Fire 5th-7th gen devices have lack the hardware for haptic feedback (ie: no vibration).
[Fire Original Android Development] mrmazak:
My mistake,I thought it did. But you right it does not
[Fire Original Android Development] huangj268:
Can not replay voice via externel USB Sound Card

My external card is Midiman m-track 2X2. No voice replayed when I connect it to the Fire.
[Fire Original Android Development] monsieur goonie:
installed failed from CM12.1 but ok from stock rom

Tried to flashfire it from CM, got a bricked tablet, reinstalled it from stock, now it works swell.
[Fire Original Android Development] DB126:
Likely wipe action (required for switch to LinOS) was mispositioned in FlashFire operations sequence.
[Fire Original Android Development] melvinaury:
I try the module, but continue with the same oblem...
[Fire Original Android Development] AwlsomeAlex:
Is the Fire 7 (7th Generation) Supported?
[Fire Original Android Development] DB126:
No - device is locked down (no root).
[Fire Original Android Development] GofreeSing:
Awesome!!! I am giving my fire a new smoke ;)

---------- Post added at 05:53 AM ---------- Previous post was at 05:41 AM ----------

"ROM OS Version: 5.1.x Lollipop"

So which gapps version do we need? ARM 5.1 too or 7.1 nano?

UPDATE: ARM 5.1
[Fire Original Android Development] SwitzXXL:
Hi Dave, I'm currently have SuperSU installed and root is working. But the app now has been updated to SuperSU 2.8.2 and so I shouldn't use it anymore.

How to change from SuperSU to stock root? Just enable root in settings and deinstall SuperSU? Or should I leave the working SuperSU as long as I don't update the binary from SuperSU 2.8.2?
[Fire Original Android Development] GofreeSing:
The built-in camera crash with video shooting. And the thumbnail cannot be clicked to show the picture if shot with still camera, but it can be clicked with panorama. The camera button is a bit far off to the bottom.

UPDATE: Tried Open Camera, it's working fine with the click on the thumbnail to go to the full image, but still the video capture will cause a crash.

With this error, we cannot use video chat through Messenger or Skype.
[Fire Original Android Development] ggow:
I'll look into before the next build.
[Fire Original Android Development] GofreeSing:
FlashFire crashed too though enabled with the root App & ADB.

UPDATE: The latest FlashFire 0.73 will work with Super SU 2.65 (not the latest 2.82)
[Fire Original Android Development] AwlsomeAlex:
Exploits exist for everything. Nothings truly locked down. ;)

Is it possible we'll one day be greeted by one as we were for a small period of time for the 5th Generation Fires?

Or is this something completely unrelated with the bootloader being like COMPLETELY locked down?
[Fire Original Android Development] DB126:
Sure...

Bootloader on 5th gen Fires was never compromised (unlocked). Amazon neglected to disable a simple fastboot command that permits a custom recovery to be booted via tether vs being installed on the device. It is easy to secure root from a custom recovery which is why many/most OEMs disable this capability. The 5th gen Fire represented a turning point for Amazon from a HW sourcing perspective. While clearly a clumsy mistake it's easy to understand how neutering the 'fastboot boot' command escaped attention on initial release. As we all know the gaff was quickly addressed and is not likely to reappear.
[Fire Original Android Development] Munns86:
Had root then lost it. Anyone else having this issue? Did a clean flash of 9/12 build from Fire Nexus. Enabled root through dev options and all worked fine. Out of no where all my apps don't recognize root. I've tried turning off root and then back on and rebooting. Still nothing. I was thinking of updating to 9/28 but I root to flash it via flashfire.

Any suggestions?
[Fire Original Android Development] DB126:
You didn't mention rebooting which is sometimes required when re-enabling root in CM/Lineage. It that doesn't work you could try rooting with SuperSU (available in Play Store) but that rarely works IME. In the end you may have to reload FireOS via stock recovery and start over.

Edit: sorry - reread your post and saw the (obvious!) reference to rebooting.
[Fire Original Android Development] Munns86:
I was worried about that. I didn't mention but I did try installing SuperSU 2.79 and it just kept failing to install the binaries.
[Fire Original Android Development] Wagner.B:
Jeah.. got the same problem...

SU2.65 should work.. but can I just flash it via flashfire?..

Why is the Built in Root not usable?

Questions over Questions...
[Fire Original Android Development] DB126:
Installing SuperSU disrupts (replaces binaries for) the integrated root solution. Reinstalling Lineage is the only way to restore "built in" root. FlashFire requires root; you'll need to reload FireOS via stock recovery and start over.

This convoluted restoration path is necessitated by the locked bootloader and crippled fastboot environment that does not allow use of a custom recovery. Amazon's stock recovery only supports reloading FireOS.

Loss of root following the installation (or update) of SuperSU on CM/Lineage 12.1 is a common problem as evidenced by the flood of similar complaints in the SuperSU forums. I have personally experienced this on a different Amazon device running CM 12.1. Using the integrated root solution solved the problem.
[Fire Original Android Development] t3chwizard:
Will next build have the recently discovered WPA2 ("KRACK") vulnerabilities patched as well?
[Fire Original Android Development] theechap:
[MENTION=5749760]ggow[/MENTION], thanks for keeping the updates coming for our Fires! I stopped updating at the end of last year and thought that was the end of the line for us.

Does anyone know how to force apps to install internally instead of the sd card? All of the apps on my sd card get wiped on reboot unless I remember to "move them to the tablet" beforhand. Or is there a fix for that issue that I don't know about?
[Fire Original Android Development] DB126:
You need a tool that supports symbolic linking to make full use of external (physical SD card) storage on Android 5.x based ROMs. App2SD and Link2SD are two examples. Either will give you full control over installation location. Apps located on the SD card will survive a reboot.
[Fire Original Android Development] t3chwizard:
I can confirm this works, as I use App2SD (found it to be better than Link2SD) and I have had no issues.
[Fire Original Android Development] steve8x8:
I've read the original paper by the Dutch guys who discovered KRACK, but it still isn't clear to me whether the vulnerability was only introduced with Android 6 (M) and would not exist in 5.1 (L).

I must assume though that LOS (even 12.1) uses a more modern software base, i.e. its wpa implementation would be affected. [MENTION=5749760]ggow[/MENTION]?
[Fire Original Android Development] steve8x8:
There seems to be a problem with AFH, is it PEBKAC on my side?
[Fire Original Android Development] DB126:
All good here. Such 'failings' are often regional and tend to clear up after a few hours.
[Fire Original Android Development] steve8x8:
Thanks Davey, so there's still hope (although I haven't seen a good response for a few days now). Will again when the IP has been renewed.

Another question: I seem to run out of physical memory every now and then. Is it possible (and supported by this ROM) to add a swap partition on the external SD? I vaguely remember having such a feature in my CM11.0 phone some years ago...
[Fire Original Android Development] eric93se:
Wifi performance was poor on my tablet, great on all other devices. I keep my wifi power level as low as I can but up'd it to 10mw, still had poor performance on the tablet. I opened it up with a guitar pik and was able to tape off the cheap antenna and solder on a simple 1db antenna from an old router, works as it should now. The outter gold tab is the ground/shield.
[Fire Original Android Development] DB126:
The two most important tweaks I make to manage limited memory are: 1) kill activities after leaving (under developer options); and 2) disable KSM. The latter may seem counter-intuitive but the CPU demand far outstrips the memory savings and triggers lag that is worse than swapping. I do tweak some other virtual memory parameters using L Speed but not sure how much they really help.

You really don't want to put swap on an external SD. Write performance is a fraction of internal memory primarily throttled by the interface capabilities vs card characteristics. Suggest setting aside a 1/4 GB of zRAM on internal storage and leave it at that.

---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------

Some of the degradation you observed may be due to a sample defect. I have a handful of Amazon gizmos and have not noticed a significant difference in WiFi sensitivity vs other 'value' devices (phones, tablets, etc) with integrated, single band antennas.