yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Likely not ... although hardware limitations will impact quality of play. CM is rooted by design; the on/off toggle under 'developer options' simply exposes it. It's likely Pokemon Go recognizes this underlying capability and blocks play.

The faux Play Store app incompatibility issue is a common annoyance with custom ROMs (thanks, Google). Best option is to sideload from another trusted source which seems to be what you did.
[Fire Original Android Development] hasexxl1988:
I've done everything according to the instructions, after the tablet started, the picture was black. The device could however be switched off, after the turn on, now only the fire logo is in an endless loop

Is there a solution to fix this error?
[Fire Original Android Development] DB126:
You will need to reload FireOS (same version that you had before) and try again. See below for general guidance on restoring FireOS via the stock recovery menu.

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294/page26
[Fire Original Android Development] yochananmarqos:
Yes. I'm not sure what you've experienced otherwise, but Wi-Fi should always stay on unless Keep Wi-Fi on during sleep is disabled.
[Fire Original Android Development] DB126:
This device tends to power down the WiFi radio during extended periods of inactivity (sleep) irrespective of ROM settings. Might be a 'feature' buried in the kernel.
[Fire Original Android Development] jaladhjin:
well the feature doesn't work on the Nexus rom for this device.. that's why I'm curious..

even if enabled it doesn't work.. so the next few times you turn your device on.. right when it comes on take a look at your Wi-Fi icon ;)
[Fire Original Android Development] yochananmarqos:
I've never had it drop WiFi.

I've never tried the Nexus ROM. I bought it earlier this year and immediately flashed CM on it via TWRP. I never once booted into FireOS 5.0.1.
[Fire Original Android Development] DB126:
Yep - seen it on CM as well. Doesn't bother me as that my preference.
[Fire Original Android Development] jaladhjin:
well the main reason it bothers me is it seems like Wakelock Detector is showing apps like Kik wasting a ton of my battery.. I assume attempting to connect to the internet..

In addition to whatever else I suspect trying to stay up to date & push notifications while the screen is off..
[Fire Original Android Development] DB126:
Install Greenify (optionally Xposed framework) to address/fix potential screen off drainers with minimal/no side-effects.

Have you tried disabling WiFi before sleeping to verify your suspicions regarding Kik? Most apps are pretty smart about connectivity.
[Fire Original Android Development] bgtbbum:
Hi there, I finally rooted and installed Cyanogenmod on my Kindle Fire 7 today. I decide to install some themes on theme engine. When I apply one of the themes I downloaded; suddenly my Kindle is stuck in a loop where the default wallpaper flashes, then the screen goes blank, then the default wallpaper pops up again. I have no control to go to the home screen, back, or see processes. I think I accidentally bricked my device because of a theme.

Any way to fix this bug or at least get it out of looping?
[Fire Original Android Development] DB126:
I have heard of tailspins trying to utilize the CM theme engine on this device an others. Unfortunately, I am not familiar with a resolution other than reloading FireOS via the stock recovery menu. If your are not in a hurry I would wait a day or two for other responses to roll in before sideloading FireOS.
[Fire Original Android Development] ytsejam1138:
Boot into recovery

Use the file manager

Go to Data/system

Delete Theme folder

Reboot
[Fire Original Android Development] bgtbbum:
How do I boot into recovery though? I booted into the sideload adb screen and tried to do the

adb reboot recovery

command on my PC to no avail.
[Fire Original Android Development] ytsejam1138:
Try turning off the phone and then turn it on by pressing power and volume + at the same time.
[Fire Original Android Development] bgtbbum:
Just tried that two times on my Kindle Fire 7 and it still doesn't boot into recovery.
[Fire Original Android Development] ytsejam1138:
Sorry, I should have said volume - and power. There is also no file manager, but you should be able to factory reset from the stock recovery and then reboot.
[Fire Original Android Development] DB126:
You can't. Previous poster was giving generic advise that does not apply to this device. Reload FireOS and start again as previously advised.
[Fire Original Android Development] bgtbbum:
I did do a factory reset on my Kindle Fire and it went back to stock Cyanogenmod (not FireOS) and it's working just fine now.
[Fire Original Android Development] DB126:
Interesting...not what I would expected but a good outcome. Thanks for sharing!
[Fire Original Android Development] sd_shadow:
factory reset just wipes user data and settings
[Fire Original Android Development] Flowah123:
I'm pretty confused: if I'm on stock FireOS, don't I need to wipe /system partition too before flashing the custom ROM? ò.ò

I tried looking an answer in the thread, but unsuccesfully. Hope my question isn't redundant.
[Fire Original Android Development] yochananmarqos:
Yes, you need to wipe system, data, cache & dalvik when flashing a new ROM.
[Fire Original Android Development] DB126:
Answer can be found in OP (1st post in thread). Should always refer to OP before flashing any ROM.
[Fire Original Android Development] ytsejam1138:
My navigation buttons don't rotate when in landscape mode. Is there a setting to change this?
[Fire Original Android Development] yochananmarqos:
Mine do.
[Fire Original Android Development] DB126:
Yeah, that's weird. Assuming native CM 12.1 with no tweaks. Not something you can change in settings AFAIK. If problem persists through a reboot and orientation lock/unlock you might consider reflashing CM in case something went awry the first time around.
[Fire Original Android Development] ytsejam1138:
Figured it out. I had changed the DPI to 180. Setting it back to 160 fixed the problem.
[Fire Original Android Development] cybermcm:
Question about storage: I've a 64 GB sdcard and want to move apps there. If I use the settings feature, the app seems to be moved but after a reboot the app is gone. There was a discussion on this thread about this issue.

I tried link2sd (free version) but it doesn't seem to work (it says successful but after reboot the app is gone). My SDcard has only one partition, not really sure if 2nd partition is really necessary. Do I need the paid version. Is the 2nd partition really necessary?
[Fire Original Android Development] DB126:
Yes - 2nd partition is necessary. Read the FAQ: http://www.link2sd.info/faq
[Fire Original Android Development] cybermcm:
I read the FAQ and I think that I'm understanding this better now. But another question remains: Without creating the 2nd partition Link2sd does the same thing as the internal settings section. I'm getting the same result, app get's moved according to the app but after a reboot the app is gone.

Is this function broken in the Android Fire build?
[Fire Original Android Development] DB126:
Not at all. Lollipop's 'move to SD' function has always been a dicey affair and depends heavily on developers designating their apps as relocatable. Happens on various device types although some ROMs attempt to override app settings to deal with the shortcomings. Link2SD uses native symbolic links which is the most reliable relocation mechanism (aside from adoptable storage) as the change is transparent to the app and normal OS functions.
[Fire Original Android Development] cybermcm:
So basically the function works but my apps (games for my kids) are not allowing it to be moved and get broken?
[Fire Original Android Development] DB126:
Likely. Developers must take extra steps to designate an application as relocatable prior to Android 6 (Lollipop is 5.x). Most don't. Symbolic links fix that.
[Fire Original Android Development] llamasking:
How to silence?
[Fire Original Android Development] DB126:
How to silence what? Keyboard, notifications, youtube, spouse ...
[Fire Original Android Development] Sulinjr:
Davey,

could you direct me to a tool or guide for make a 2nd partition on my 64gb micro SD card? I haven't had much luck with my stock os tools and I haven't had any luck with the Google Play store partition tools either. I've been trying to find a way to make more space on my Amazon Fire by redirecting the all apps to SD card. I value your opinion and would greatly appreciate your advice on this.

Thanks!

-Jake
[Fire Original Android Development] cybermcm:
I had the same challenge a few days ago. I used Aparted (free) and Link2SD (free) from Play Store. Please be aware that you will loose all data on your SD card if you decide to change the partitions.

Both tools need root access. My SD card now has a small fat32 and a larger ext4 partition. If I remember correctly for the ext4 partition you have to choose ext2 first to design (size) your partition and then format it with ext4.

With the paid version of Link2SD you can move all your app data to your SD card, with the free version only parts of it (e.g. game data folder remains on your device with the free edition).
[Fire Original Android Development] DB126:
I use MiniTool Partition Wizard (Windows) because it is convenient and works. If you prefer Android try Apps2SD which attempts to provide card/partition management capabilities via 3rd party tools. Results are variable and highly dependent on device type, installed rom and other hardware and storage device characteristics. Your best option is to prepare the SD card on different host and then leave it permanently in your device, especially if apps are 'moved' (preferably linked) to the SD card. I use an inexpensive OTG adapter and/or multi-headed flash drive (example) for removable storage as needed and ignore the SD slot.

As an aside, the external storage interface is considerably slower than internal storage on this device regardless of card type/rating. Keep that in mind when deciding what to relocate. You can improve performance by fiddling with cache sizes but internal storage will always be notably faster (at least on 5th gen devices).
[Fire Original Android Development] Svalfio:
Is there a way to set the original Fire's 171 PPI on cm12.1? In the settings I found 160 and 180, among others, but not that one ( and if this a stupid question I am very very sorry )
[Fire Original Android Development] DB126:
Good question. Use one of the many DPI/PPI changers in Play Store. Can also be done by editing build.prop directly (not recommended). Note CM is not optimized for 171; you'll probably find fonts look a bit fuzzy. To my knowledge here is no decisive information on the native (hardware) panel resolution; Amazon simply reports what they have chosen for FireOS.
[Fire Original Android Development] Svalfio:
Thank you for your answer! The fact is that, on 160dpi, I find the name of the apps on the home to be a bit, how can I say it, "pixelly" and shrunk, while as i recall on fireOS the font was displayed better there. I'll try looking on the play store, thank you very much for your advise!

Now that I think about it, is there a way to make the navigation buttons disappear in the apps or watching a video?
[Fire Original Android Development] SeanAche:
I just wanted to thank ggow and all developers involved with these fiddly little entry-level devices. This has enabled me to bring a multimedia experience to my extended family who could not otherwise employ face to face communication over the miles, and this build will soon be enabling a recently-now-great grandmother enjoy the latest additions to her family.
[Fire Original Android Development] DB126:
Pixels on the 5th gen panel are asymmetrical (eg: circles have a slightly oval appearance). As a result characters and some graphics will always appear slightly fuzzy regardless of size or DPI setting. FireOS fonts may have accommodated this characteristic; you are not the first to say they look better.

Most roms, including Fire CM 12.1, support Android's Immersive mode (aka Expanded Desktop) which can hide certain screen elements like the navigation and status bars. Look under Display and Lights in the settings menu for global options. Some apps involve Immersive mode automatically or you can trigger it via gestures and/or key combos depending on launcher. Note: when the Navigation bar/buttons are hidden you can bring them back by swiping up from the bottom of the screen.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 21 October 2016

- October 2016 AOSP Security Patch Level

- Fix x265 video playback - Thanks [MENTION=4144960]jeromeof[/MENTION]
[Fire Original Android Development] DB126:
Updated via FlashFire v0.53. No wipes, no gaaps, accepted all defaults. Didn't even bother to backup. 10 min later back in business. Tomorrow I'm going to drive 5 mph over the posted limit. Liv'in on the edge, baby!

Edit #1: x265 playback works fine.

Edit #2: LiveDisplay also working properly; in previous two builds actions associated with 'automatic' were reversed.
[Fire Original Android Development] tonibm19:
New update working fine here.

Followed OP instructions and all fine as always.
[Fire Original Android Development] HA4ever:
Thank you for the great work. However, the video recording bug still exists
[Fire Original Android Development] marrco:
installed via TWRP on my fire with Opengapps pico 5.1. Everything works fine. Thanks for the great build
[Fire Original Android Development] el_charlie:
Thanks for this.

Used gapps stock with a gapps-config file. Everything is great (140MB free on /system).

Funny thing: On your Fire-Nexus ROM, Instagram wasn't compatible on the play store. Now, on CM12.1 it is. Weird, huh?

Cheers!
[Fire Original Android Development] ggow:
That is strange, about Instagram compatibility.

Has to be something ROM dependant. Cheers for the feedback
[Fire Original Android Development] nujak:
Did a dirty install using latest FlashFire and Nano GAPPS. Everything installed fine, but play store wouldn't launch and it said I was missing Google Play Services. Downloaded both from APKmirror and installed. Everything is now working flawlessly and I didn't lose anything from the previous installation.

I'm not sure what changed with this rom, but I've yet to run into app compatibility issues. Before this version, for example, my bank app wasn't compatible. Now it downloaded and installed no problem. Regardless, it's good to see this device stay up to date. Thanks for all the hard work [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] DB126:
Guessing the reinstall of Google Play components was the difference maker vs. new ROM build. It's a fickle issue that has befuddled many experienced users across a variety of device types and custom ROMs.

A handful of contributors will likely try the same thing as you with varying outcomes. FWIW I have experiences very few app compatibility issues with this ROM. Those that exist persist through the latest build. Of course this is simply a Play Store ruse. Grabbing the apk from another trusted source typically results in a successful installation assuming general hardware and Android version prerequisites are met.
[Fire Original Android Development] bvbull200:
I installed using FlashFire, coming from a fresh root, and it worked, but I lost the SU app, FlashFire, etc. I also installed the GAPPS zip from the OP (chose the stock 5.1 version) and none of those seem to be installed, either. I can't get anything to install using the PlayStore via the browser, either, so here I sit with a rooted tablet running a nice ROM that I can't do anything with. Any suggestions?

---------- Post added 25th October 2016 at 12:01 AM ---------- Previous post was 24th October 2016 at 11:47 PM ----------

My SU was deleted, too, and now I can't run apps that require root access.
[Fire Original Android Development] nujak:
I know root is built into the ROM , so you can turn it on in developer options and then restart the device for it to take effect. You can also install Google play services and Google play store from APK mirror.

To enable developer options in settings, go to Settings > About Tablet and tap the build number until it says you have enabled development settings.

Worst case scenario is just to do a clean install from twrp. Although the previous steps should get you setup.
[Fire Original Android Development] jboxer:
You did not lose root. Root is built into the ROM. You have to enable in the settings menu. It is off by default. After enabling it in the settings you reboot and you have root.
[Fire Original Android Development] SHRAPNEL189:
Edit: answered

---------- Post added at 01:48 PM ---------- Previous post was at 01:44 PM ----------

I also thought I lost root and enabling it in developer options wasn't working... I didn't realize I had to restart LOL
[Fire Original Android Development] bvbull200:
Thanks. I stumbled across something that worked late last night and I got SU back. I'm sure I had root access, but without SU, I didn't have the option to grant root access to apps like FlashFire.

At any rate, I do have another question. Is there a way to turn off the clicking sound when making a menu selection? I can't seem to find the option to do so. I all volumes turned completely down, but it still makes a clicking sound anytime I select an option in settings. It'd be great if I could make that go away.

Thanks to the OP for the ROM and to all those offering their assistance.
[Fire Original Android Development] jboxer:
I believe that is in the settings for the keyboard...
[Fire Original Android Development] bvbull200:
The keyboard setting only affect sounds when pressing keys on the keyboard itself. I'm referring to the sound made when the home button is pressed, when a menu item is selected from the settings screen, etc.
[Fire Original Android Development] jboxer:
Try going into settings for "Sound & Notifications" then go to "Other Sounds" and look for something like "Touch Sounds". Turn them off.
[Fire Original Android Development] FatalIll:
Okay Im a bit of a tard...

I just got a 5th Gen 7" Fire Tablet, straight out of the box, FireOS 5.1.3. I want to flash this CM12.1, but it says to use FlashFire 0.50 in the OP. My understanding, having never used FlashFire, is that it requires root (which I don't have, and can't do on 5.1.3). Any advice?
[Fire Original Android Development] bvbull200:
You will have to root in order to flash CM. In order to rook, you will have to downgrade to 5.1.2.

This is the thread that I used:

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire Original Android Development] FatalIll:
Perfect, worked like a charm. Thanks!
[Fire Original Android Development] mbholm:
Bluetooth in restricted profiles using CM?

Since most all my experience with android has been with this CM rom, I am wondering if I am running into an android issue or something with this rom.

It looks like I should try updating some of my kid's Fire7 devices. . .it has been a while, but they have been working. But now I am running into a need to be able to use Bluetooth devices for my kids (speakers, fitness tracker band). I have the Fire7 tablets running KidsPlace under restricted profiles. . .and it seems there isn't a way to setup bluetooth devices to connect to a restricted profile. Is this true in all version of 5.x Android or is it something with restricted profiles with this CM rom? The reason I have had to use restricted profiles is because I can't allow them the ability to create new user profiles and as long as you can login as a "normal user", you can create new profiles from the profile switching screen.

Anyone able to confirm if there is a way to enable Bluetooth in a restricted profile on any 5.x android device? Or disable the ability to create new user profiles?
[Fire Original Android Development] luk2009:
Updated vía flashfire mini gaaps, wipe cache and dalvik. Everything working perfect. Thanks

Enviado desde mi KFFOWI mediante Tapatalk
[Fire Original Android Development] Neffy27:
Flashed over July release build with FF v55 (default values), no issues.

Many thanks!
[Fire Original Android Development] yochananmarqos:
If you're updating from a previous version, there's no need to flash Gapps again.
[Fire Original Android Development] mbholm:
So, I did some research and found this post. . .which I wanted to try to limit creating new users and disabling the guest mode option. . .

http://www.theandroidsoul.com/how-to-disable-guest-multi-user-accounts-on-android-lollipop/

...unfortunately, it appears that I didn't do something right because now I have the CM boot logo. . .stuck. Is there a way to get back and restore the backup copies of the files I tweaked? A safe mode? I haven't had to repair anything previously.
[Fire Original Android Development] NorCal55:
Flashed the Wrong GApps

I have an Amazon Fire, 5th Gen, that was running stock OSFire 5.1.1.

I followed the directions to use FlashFire to install the ROM and GApps, but apparently flashed the wrong GApp. Instead of 5.1, I flashed 6.0

My tablet works great, except that I don't have the Google Play Store, which makes it not so great.

I tried using RootJunky's batch file to install Google Play, and although it installs, it throws an "Error retrieving information from server [RH-01]" and is unusable.

The log for the GApp install describes my error in my new ROM installation , ie. "This GApps package can only be installed on a 6.0.x ROM."

I did not do a backup of my tablet before I flashed the new ROM, but it was brand new and had no data to lose.

So, what do I do now? Any options would be appreciated.
[Fire Original Android Development] GhostRider86:
Flash correct Gapps with FlashFire, or start clean: sideload previous installed FireOS version, reroot, and flash CM and gapps as descriped in OP
[Fire Original Android Development] DB126:
Reload FireOS from stock recovery menu and start over.
[Fire Original Android Development] mbholm:
Figured that might be the case. Is there a way to confirm which FireOS version was installed? I think it was 5.1.1, but I just wanted to know if there is a way to confirm.
[Fire Original Android Development] DB126:
Nope. Go too low and device will brick w/no known recovery. If unsure stick with 5.3.1 (safest choice).
[Fire Original Android Development] NorCal55:
Thank you, I was able to fix it by side-loading v27 of FlashFire and reflashing the ROM along with the MINI version of GApps.

I do not remotely resemble a knowledgeable android person, but I did learn a few things if anyone else has to do this:

1. I loaded the FlashFire APK on the SD card and then side-loaded it using File Manager on the device. There was a bug in the FlashFire App that required me to manually set the tablet's date to a date before June 1, 2015. if you don't manually reset the date, the App opens and then quickly closes.

2. To allow FlashFire to work, you also have to enable "Developer Options" by going to Settings, and repeatedly clicking on the build number until Developer Options are enabled.

3. Then, you have to allow FlashFire root access by selecting that option (both ABD and Apps) in the Developer Options section.

4. The largest version of GApps that I was finally able to flash was the mini version. The stock version was too large. You must carefully choose the appropriate version of GApps for your ROM and device from the link of the first post of this thread. For the Fire 5th gen tablet, it is version 5.1 and for me the mini version.

I would like to thank everyone involved in this project. I am extremely happy with the result. :)
[Fire Original Android Development] mbholm:
So, it is okay to go high, but not low?
[Fire Original Android Development] GhostRider86:
Yeah