yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Unjustified Dev:
Here's a way to fix the sound error without configuring hrtimer to select snd_timer

https://github.com/TeamRegular/andr...mmit/9a30462318030189948947febd31b98e51cbedff

Trapz didn't compile and seems to be specific to amazon build
[Fire Original Android Development] sam tyler:
Bluetooth is working! many thanks.
[Fire Original Android Development] switchy85:
So, I don't think I saw this mentioned in the thread yet, but is anyone else not able to adjust the screen brightness? It seems to always be at max and when I move the brightness slider nothing happens.
[Fire Original Android Development] Deuces:
Netflix took a long time to start the first time, but works fine now.

When pressing the power button for screen-off, you can see the screen rotate to portrait before shutting off.

Some of my videos (mp4s, avis, mkvs) do not play. Most work fine, but on the broken ones: screen stays black and I can hear audio. Screen gets freezy / slow, hard to use buttons.

thanks for the hard work, this rom is running waaay better than stock all of a sudden.
[Fire Original Android Development] James.Harking:
I would just like to thank ggow for all of your hard work. You have turned what is a cheap limited tablet in to a very capable device.

I would just like to ask anyone who has experience of using a case that supposedly turns off the screen when closed and on when opened? I recently purchased one from eBay. As I have only ever run CyanogenMod I have no idea if the screen not switching on and off is due to the case itself being faulty or CyanogenMod not supporting this functionality? Can anyone comment? Is there a setting in the OS that needs to be enabled? Many thanks and best regards.
[Fire Original Android Development] DB126:
Fully agree with [MENTION=5749760]ggow[/MENTION] sentiments. CM 12.1 is an ideal rom for this device, especially when used in a secondary role (I prefer Nexus on my daily driver).

Note the 2015 Fire lacks the hardware sensor necessary to respond to magnetic trips which is the mechanism used by most (all?) cases. If you want auto-off capability take a peek at Gravity Screen which uses various sensors to turn off the screen. Unfortunately, 2015 Fires also lacks a proximity sensor which will limit functionality.
[Fire Original Android Development] stslimited84:
Just got my fire delivered and it came with 5.1.1! :D

I saw in the early pages of this thread this rom has to be fast booted for it to load. Is that still the case or has it been worked out to where normal shut down/start up procedures work? I'm setting this up for a friend with no technical knowledge. Just trying to provide an improved experience over the stock fire.
[Fire Original Android Development] mageus:
This ROM has been great except for one major issue - the brightness bug.

The brightness will go to its lowest setting and stay there. The Settings menu won't fix it. Brightness Level won't fix it. Only a reboot fixes it. Problem is, it has happened up to 3 times in an hour.

- Does anyone have another suggestion to fix the problem?

- Is this a problem with all ROMs? (e.g. AOSP or Slim)
[Fire Original Android Development] DB126:
Unlike earlier versions FireOS 5.1.1 offers no significant advantages over 5.1.2 from a rooting or device management perspective. You can not boot a custom recovery (eg: twrp) so all flashing must be done via Flashfire. You will want to keep WiFi off (or airplane mode engaged) until rooted and updates blocked as you will immediately get pushed to 5.3.1 which can neither be rooted nor rolled back. Also do NOT register the device with Amazon when prompted as that triggers OTA updates and complicates rooting. Your friend can always register later if you opt to retain FireOS.

---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------

This problem is most frequently triggered by a low memory situation such as extended game play, HD video or multiple background apps. It has been observed on CM and Nexus; not sure about the others. There is no solution at present other than monitoring/reducing memory load.
[Fire Original Android Development] stslimited84:
Thanks to all who worked on this
[Fire Original Android Development] mageus:
So, having Tasker, Rocket Player, TabletTalk, and Maps open (along with a background changer) may be straining this cheap little machine that wasn't designed to do all that at once? Who'd have thought?!

I'll try to remove everything not needed, and turn off all notifications.

- Would AOSP decrease memory usage compared to Slim or CM? (I know you mention Nexus above)
[Fire Original Android Development] atroph:
FWIW I use lux dash that takes a light sample with the camera when you turn the device on. From there is adjusts the brightness of the screen according to how you have your profile setup within the app. Works great for me. You can have it sample at different rates however it may affect your battery life.

I also set my screen to turn off after 1 min if I forget to shut it off prior to closing the flap on my case.
[Fire Original Android Development] DB126:
Out-of-the-box Fire Nexus (AOSP clone) has a slightly lighter footprint vs CM 12.1 but the difference isn't significant. Can't speak to Slim or the other roms for this device as I didn't work with them long enough.
[Fire Original Android Development] Munns86:
Not that this ROM is heavy by any means but I was wondering if anyone had any luck using any of those CM debloater scripts? I've used them in the past and i'm tempt on this device to shed any spare weight I can. Not being a dev I wasn't sure of the possibly of thing breaking.

Here is an example : http://xdaforums.com/xperia-t-v/general/script-cm-12-12-1-debloater-script-t3076142
[Fire Original Android Development] DB126:
Meh - extra busywork with no significant benefit. Snag a backup of your current config if you go for it.
[Fire Original Android Development] morganfreeman:
I was lucky enough to grab a 5.1.4 Fire 7 (5th gen/KFFOWI) from Amazon on PrimeDay for $33. I quickly realized the FireOS limitations so I downgraded, rooted and installed CM12.1 (12.1-20160710-UNOFFICIAL-ford). Thanks to all those that made this possible. It's really a nice little full featured tablet now.

Because I was running low on internal storage from big apps/data, I threw in a 128GB microSD card , but I can't seem to figure out how to take advantage of this extra space. I tried moving the apps to the SD card but that doesn't really seem to free up the internal space. I also spent the better part of the day partitioning the card into FAT32 and ext2 and trying to get Link2SD to work. Unfortunately, I haven't figured it out after combing the forums for answers.

Has anyone found a way to free up the internal storage by offloading apps to the SD card either with Link2SD or formatting as internal storage on KFFOWI/CM12.1? Would love to hear comments as this really is the last step for a perfect, affordable device/OS. Thanks!
[Fire Original Android Development] Kramar111:
http://xdaforums.com/showpost.php?p=67788798&postcount=3
[Fire Original Android Development] MisterSteve:
Set up an Ext4 partition for Link2SD.
[Fire Original Android Development] DB126:
Fair enough. Not sure this offers a 'significant advantage' for most but worth noting as the situation warrants.

---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------

Footnotes:

- two partitions are mandatory with Link2SD, one of which must be Ext4

- larger SD cards (128GB in particular) have been problematic for some; try a smaller card or partitions and work up

- see Link2SD FAQ for additional tips: http://www.link2sd.info/
[Fire Original Android Development] MisterSteve:
I've used 2 Samsung EVO 128 gb micro sds and they worked fine for me. I also used a SansDisk128 gb, which worked fine until it crapped out on me. If you go with the same specs as the card Amazon promotes, should have no issues. The issue may be lower spec cards. This is just my experience for what it is worth.
[Fire Original Android Development] jdougal11:
I just purchased a Fire 5th Gen, it came with 5.1.1 installed. Got it rooted and used FlashFire to wipe then install latest CM from 1st post and GAPS. Device is not stuck in a boot loop for 20 mins. What should I do? How can I repair the device?
[Fire Original Android Development] DB126:
Best path is to reload (adb sideload) FireOS 5.1.1 via stock recovery menu. Don't try to go lower; device will brick. Files and instructions can be found in the forum index:

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485

Tips for a smoother experience next time around:

- don't register device with Amazon on initial FireOS boot

- keep WiFi off until ready to root (an OTA update will spoil your day)

- replace Kinguser with SuperSU after rooting (see SuperTool)

- be sure to use FlashFire 0.52 or above; some earlier builds are flakey

- make sure wipes are properly positioned (above rom flash)

- consider flashing GAaps separately after CM successfully boots
[Fire Original Android Development] jdougal11:
Thanks for the help. I got it reloaded, however I used 5.1.2 because I read about bricking by going with 5.1.1. I wanted to be on the safe side. I've got 5.1.2 rooted, Flashfire installed, however it won't load. It appears the super tool I used was using .50, so I'm going to find .52 and go from there hopefully.

Thanks again

---------- Post added at 01:46 PM ---------- Previous post was at 01:24 PM ----------

Bootloop again. I don't know what the deal here is. -_-
[Fire Original Android Development] jratt:
Which gapps are you using? I believe you can only use Gapps micro or smaller, not sure what is going on just throwing it out there.
[Fire Original Android Development] jdougal11:
open_gapps-arm-5.1-pico-20151120
[Fire Original Android Development] webman2k:
Screen resolution fix?

Hey All,

Huge thanks for the devs. Picked this up for $25 shipped on Amazon Prime Day (with the audible trial $10 credit applied), and immediately rooted and flashed this rom. It's been super stable - no crashes whatsoever. Bravo on creating a super cheap full android tablet!

I've been thinking about the non-square pixel issue, which bugs me every once and a while. Has anyone tried using one of the resolution changers?

NOMone Resolution Changer

That's just one I saw... there are others on the store. Basically they're just adjusting the resolution and DPI settings in build prop:

wm size 1024x600

That's the default, which, since the pixels are non square, causes a stretched appearance.

So, what if we just artificially stretched the width(or height if thinking portrait)?

wm size 1080x600

Shouldn't this effectively scale the resolution to appear as if it's rendering on square pixels? I don't have access to my tablet to test right now - just was wondering if anyone had tried something like this before.

Edit: Never mind. Just realised that's not how it works. We would need to find a way to make the vertical DPI different than the horizontal DPI.
[Fire Original Android Development] GhostRider86:
Do you change the order in FlashFire so wipe is the first, then flashing CM then GApps?
[Fire Original Android Development] jdougal11:
Yes, thank you. I believe the issue was with the CM file. I redownloaded and reloaded it after another go around. Everything went as expected after that. Thanks everyone!
[Fire Original Android Development] DB126:
Strange. Thoughts:

- You would have been fine with 5.1.1 provided that was the previous version on your device. Your new base version is 5.1.2; any precious version is no irrelevant (and dangerous)

- Recheck recommendations (best practices) in my prior post

- Verify full wipe (system, data, dalvik, cache) task remains the at the top of the FlashFire operations sequence just before hitting the Flash button

- Do not include GAaps, SuperSU or anything else on the initial flash attempt

- Leave all FlashFire options at their default values

Also (briefly) describe your bootloop symptoms. Folks tend to use this term loosely. I have seen full lockups described as a 'bootloop'.
[Fire Original Android Development] GhostRider86:
Problem solved, see #3205. His download was corrupt.
[Fire Original Android Development] toidimaet:
I've been using FolderMount by madmick (an xda developer). It costs £1.40 ($2) but it has been fantastic and simple to use with every device I have put it on.
[Fire Original Android Development] yochananmarqos:
FYI, I was only able to mount a Seagate 1 TB external drive via a powered OTG cable formatted (by default) to exFAT using StickMount.

Note: StickMount requires the proper binaries placed in internal storage for exFAT & NTFS support. More info can be found on the Play Store description.

---------- Post added at 06:26 AM ---------- Previous post was at 06:17 AM ----------

I'm curious if you ever tried Link2SD. It looks like both apps do the same thing. I haven't tried either yet.
[Fire Original Android Development] toidimaet:
Yochananmarqos, I did use linked in the past, but it's been so long I can't remember much about it.

I went with FM as it was the first app that supported the change in the directory structure back in Android 4.something.

PS. FM doesn't require partitioning or ext4, allowing you to easily work with the contents on a pc as well.
[Fire Original Android Development] duckwizzle:
Backups?

Hey everyone - I got my Fire yesterday. It was on 5.1.3, I downgraded it to 5.1.2, rooted it, installed FlashFire and am now running this CM 12.1 ROM with no issues. But from what I understand, since I did not unlock my bootloader - I probably still have the stock amazon recovery, right? How do I perform a backup or a restore, if needed? It's been years since I have not used TWRP on an unlocked device, and even longer since I've used Clockworkmod recovery. But like I said, I don't have any problems - but I'd like at least one back up in case something bad happens. I am just a little confused on how backups/restores will work for this device
[Fire Original Android Development] mattgyver:
You can use FlashFire to make backups. I made one, and restored it to my son's fire tablet, just to see if it works, and it works well enough.
[Fire Original Android Development] DB126:
Fully support [MENTION=4441541]op3n[/MENTION]src recommendation (FlashFire) or you can use a well recognized backup app like Titanium. Or create a native nandroid using adb (Google for details). Regardless of tool be aware that you will not be able to directly recover if CM or any other rom won't boot. You'll need to reload FireOS via stock recovery, root, reinstall FlashFire and then restore your backups. Here FlashFire holds an advantage over other tools. You may also want to consider a separate backup of just your data partition as that is where most personal/irreplaceable content is retained. Apps can always be reinstalled; pictures of your kids can not.
[Fire Original Android Development] duckwizzle:
That's exactly what I was curious about. This tablet won't have any irreplaceable data - it's main purpose will be browsing the internet/reading books stored in the cloud - so I am not concerned with data backups... I just didn't want to be helpless if one day CM didn't boot. So if that does happen, I just need to flash FireOS 5.1.2, root, install FlashFire and then I can install CM or restore a backup. Thank you!
[Fire Original Android Development] toidimaet:
Duckwizzle that's about the gist of it yes. The default recovery allows for factory reset of any Rom as well. Which can come in real handy if you get stuck in a bootloop.
[Fire Original Android Development] NeightC:
GApps Install

After bricking my first fire, I ordered 2 more and got CM 12.1 loaded on them. I believe I chose the wrong architecture for GApps as it did not install when I flashed it. I attempted to use the SuperTool to install Google Play with no luck and I cannot get FlashFire to install properly. When installed using the supertool, Flashfire opens a 1/2 sec then immediately closes. How do I get the proper GApps loaded onto my device? Unfortunately this is my first time messing with android and I still have a lot to learn.
[Fire Original Android Development] DB126:
Use the first link to grab a more recent version of FlashFire (0.52+). The version installed by the SuperTool tends to exhibit the behavior you describe. Use the second to snag a suitable GAaps package. ARM/5.1/nano.

http://www.apkmirror.com/apk/chainfire/flashfire/

http://opengapps.org/

Edit: You'll need to enable the following in CM to permit sideloading FlashFire: settings -> security -> unknown sources
[Fire Original Android Development] NeightC:
I enabled unknown sources. I downloaded Flashfire and installed it which went well. I downloaded GAPPS ARM/5.1/nano. I clicked the + sign, Flash Zip, selected the file and clicked flash. It went through its process and rebooted. Still no google play. I tried it with the pico and nano for ARM and ARM64 with no luck. I am one step closer now though thank you.
[Fire Original Android Development] DB126:
Welcome. ARM64 is not correct for this device. Attempting to flash an architecturally incompatible package is just asking for trouble. Would you dump tea in the fuel tank if your car didn't start? Heck, looks a bit like petrol - what could it hurt?

Try ticking the auto mount option in FlashFire. If that doesn't work you may need to perform a full wipe and then reload CM + GAaps.
[Fire Original Android Development] jratt:
In FlashFire was wipe moved to the top, then rom os you want to flash, then Gapps at the bottom?
[Fire Original Android Development] NeightC:
Ok. In previous posts I explained that this is my first time with this. I only tried the ARM64 because while searching the forum for the solution, somebody had said that solution worked for them. I will try your suggestions as well. Thank you.

---Ticking the mount option worked using the GApps ARM/5.1/Micro. Thanks again. Sorry for any inconvenience.
[Fire Original Android Development] morganfreeman:
MIsterSteve, thanks for the heads up. ext4 format works fine (despite some chatter in other forums to the contrary) so I went ahead and purchased the Link2SD Plus license and was able to move some of the bigger apps and data (e.g. Microsoft Word, Excel, and PowerPoint). Link2SD recommends leaving Google apps alone so I didn't try moving those.

Unfortunately, one of the bigger apps I'm running is GNURoot and the rootfs (Fedora linux) seems to require being left in device memory. I can see the partitions mounted in the Linux environment but the SD-card ext4 partition is not writeable. I was thinking maybe I need three SD card partitions: one for general SD use (FAT32), one for Link2SD (ext4), and one specifically for GNURoot to mount in the Linux environment (ext4). I've read that GNURoot has some hurdles because of Android app permissions. Anyone have experience with a setup like this?
[Fire Original Android Development] DB126:
Thanks for the follow-up; glad to hear all is well. I recognize you are new to android modding; hence the rebuke. Objective is not to poke fun or embarrass; rather communicate a decisive message not experiment until you have a better appreciation of the potential consequences.
[Fire Original Android Development] EncryptedCurse:
Thankfully, I believe Open GApps will refuse to install if there is an architectural mismatch.
[Fire Original Android Development] jayrocka1200:
Gapps not showing up

Hi all, I installed CM and everything went smoothly except Gapps did not install so luckily I made a recovery file in flashfire beforehand to get back to my rooted kindle. I started on 5.1.3 and downgraded to 5.1.2 beforehand with Rootjunky's super tool. I also tried to flash Slim Gapps coming from CM and had the same problem, everything was good but no Gapps. I am sitting here at my recovered state with root and ready to reflash. Any idea what the problem is ? also, when checking mount in flashfire (.52) am I supposed to uncheck the other option ? or should both boxes be checked. Thanks
[Fire Original Android Development] GhostRider86:
Which Gapps are you trying to install? Arm, 5.1,pico is working. Normally you can leave the FlashFire options as they are
[Fire Original Android Development] jayrocka1200:
I just reinstalled CM and left the boxes how they were in flash fire , I didn't check or uncheck anything. CM installed perfectly with pico gapps installing perfectly as well. This tablet is really really impressive and for 30 bucks off Amazon as a basically brand new refurb you cant beat it ! Thanks guys
[Fire Original Android Development] $ideWinder:
[MENTION=5749760]ggow[/MENTION] I can confirm that the audio lag issues in games like mekorama are solved by Renaming /system/etc/permissions/android.hardware.audio.low_latency.xml to /system/etc/permissions/android.hardware.audio.low_latency.xml.bak or removing the file and rebooting
[Fire Original Android Development] BobQuiTue:
OTG Ethernet working ?

Hi everyone,

I wondered if anyone tried USB OTG Ethernet adapter on this cm12.1 ROM ?

For my part, I tried an apple (don't shoot ;) !) USB/ethernet adapter, and also an old noname USB/ethernet adapter that I bought for my wii (ok, it's old but it still works ^_^ ).

None worked for my amazon fire with this cm12.1 ROM.

I saw that some people made USB OTG ethernet adapters work on their unmodded amazon fire, and I was wondering whether this ROM could have broken that, or if it's just me having no luck with my adapters ?

Thanks in advance for your kind experimentation reports :)

Cheers !
[Fire Original Android Development] el_charlie:
Good day everybody!

Why the Pico Gapps are the recommended?

/system is 1.2GB so it would be enough to install stock gapps and they even replace many AOSP apps (browser, camera, launcher and so on). Do they have a problem with FlashFire??

On a related note, can I use stock gapps and use gapps-config.txt to prevent insalling some apps??? Does that work with FlashFire or just TWRP??

Thanks in advance for your replies.
[Fire Original Android Development] GhostRider86:
As stated out in the OP, the free space is not enough.

"

- Flash Open Gapps - Use either micro, pico or nano<br />

- Do NOT use stock gapps as there is not enough space on the /system partition

"

Flash a small package and install the apps from play store which you really need
[Fire Original Android Development] el_charlie:
Yeah, I understand. But you can use gapps-config.txt to prevent flashing some of the apps, and you end up using like a mmini-stock package.

I mean this because the stock package replaces many AOSP apps and therefore you have a better experience. The smaller packages don't replace anything. You end up having 2 apps of the same sometimes.
[Fire Original Android Development] DB126:
- those who flash full/stock GAaps on this device report bad outcomes

- advanced users can leverage gapps-config to create a custom GAaps package

- the recommended (generally smaller) GAaps packages are appropriate for the vast majority of individuals modding this device
[Fire Original Android Development] Chillmann:
Now i get error 505 while trying to UPDATE (regular update, no apkmirror file) chrome Browser :eek:

Any solution?
[Fire Original Android Development] DB126:
- uninstall (retain data if given the option)

- reinstall latest build from apkmirror: http://www.apkmirror.com/apk/google-inc/chrome/
[Fire Original Android Development] jratt:
Google update for chrome was messed up yesterday maybe you are still being served old update. Try uninstalling chrome then reinstalling it

I was having same issue with my Samsung phone yesterday.
[Fire Original Android Development] atroph:
I seem to be having an issue with the AOSP keyboard that comes as default. The ROM prior to this update would never expand when turned to landscape. After updating it appears to never shrink when portrait. I installed Google keyboard from the store and all is well when rotating now. Is it just me with the stock AOSP keyboard issue?
[Fire Original Android Development] DB126:
No trouble with the stock keyboard (which is not AOSP) on this rom.
[Fire Original Android Development] su6ur6an:
Download link still leads to 2016-07-10 build, though 2016-08-10 build notes are posted