yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Possible device lacks adequate hardware resources but you mentioned some games work with FireOS so something else is likely getting in the way.

---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------

Device lacks an ambient light sensor so should stay at whatever Ievel you set until changed. Ironically I ran into a similar problem last night where screen remained at lowest brightness level regardless of where I moved the stock slider. First time that has happened. A reboot fixed it. Bears watching.
[Fire Original Android Development] mainstang:
So I have hunted around the forum and this thread. Tried the SD card fix app in the play store but it says I already have correct permissions. How do I move a file from internal storage to external SD?
[Fire Original Android Development] Sulinjr:
I recommend flashing Closed and installing XinternalSD. This will allow you to migrate the bigger data files for applications in the Android OBB folders.
[Fire Original Android Development] ldeveraux:
Or link2sd works fine on this Rom
[Fire Original Android Development] mainstang:
I don't mind having the apps on the internal memory. I really like being able to download Roms, gapps and a couple of apks to the external.
[Fire Original Android Development] oae08:
Hey guys, I've recently got the Amazon Fire (5th Generation) Tablet and it has the Fire OS 5.1.4 installed on it. Will i be able to use this rom and can anyone point me to the procedure because im getting confused with what stock os i should be on in able to install a custom rom.

Thank you.
[Fire Original Android Development] mainstang:
You will need to downgrade your fire OS to 5.1.2 via ADB. The link to the instructions is in the index section.
[Fire Original Android Development] oae08:
Hey, thanks for your help. I was actually reading the index and it led me to this video in order to downgrade my 5.1.4 to 5.1.2. However on the video itself, there is a warning note that says do not downgrade or the device will brick. That is why im a little confused on how should i do it.
[Fire Original Android Development] mainstang:
That's the one I used. I went from 5.1.3 to 5.1.2. I think the warning is maybe for the known brick that will happen when trying to go to 5.1.1 from anything higher. You may wait on someone else to confirm/contest my thoughts as I'm still relatively new to rooting the fire.
[Fire Original Android Development] oae08:
ok will do it right now to downgrade to 5.1.2. After that i only install flashfire and then this rom? or is there something i have to do before?
[Fire Original Android Development] mainstang:
After that I used the super tool in the index to get root and immediately block ota updates. Use the same tool to install flashfire. Then follow your rom of choice's flashing instructions.
[Fire Original Android Development] DB126:
If you are looking to migrate applications (vs just files) recommend using LinkSD or another tool that leverages symbolic links. Really the most comprehensive and reliable method for application migration.
[Fire Original Android Development] oae08:
All worked great. Thanks for your help. Any idea how updates are released here? I mean how frequently is the rom updated. Thanks again
[Fire Original Android Development] ldeveraux:
Whenever op gets a chance. Maybe monthly.
[Fire Original Android Development] Munns86:
It seems like they are at least monthly. It looks like they wait for the monthly security patches (July's just came out) and then roll all their fixes and features into those updates.
[Fire Original Android Development] DB126:
"They" is one individual who generously shares his time and talents with this community. [MENTION=5749760]ggow[/MENTION] supports multiple custom roms on several different devices and likely has a day job and family too.

The previous poster had it right: "Whenever op gets a chance". Don't look for updates on a schedule keyed off the release of security patches.
[Fire Original Android Development] Munns86:
I wasn't implying anything. I was just pointing out the pattern (why I used the words seems and likely) that I noticed from the previous updates for this ROM.
[Fire Original Android Development] monza1412:
Does anyone have Wi-Fi problems with the latest release? Like disconnecting randomly after a couple of minutes?
[Fire Original Android Development] Henil Shah:
I think it is kind of a battery saving feature. If i dont use the Wi-FI for a couple of minutes it does disconnect. However it doesnt disconnect randomly without any reason or while im using it. Happened to me on both me and my moms kindle
[Fire Original Android Development] monza1412:
Thanks for the answer, In my case I lose internet connection but the wifi is still active, and in proper range. I get the exclamation sign till I reconnect to the router. Its kind of weird as it never happened before with earlier releases, and with my other devices I don't have any trouble.
[Fire Original Android Development] mangelkool:
Brick after reboot

I rooted my fire 5.1.2 and after flash fire procedure, reboot and brick in amazon logo.

I unbrick it and try another ROM and happened the same thing.

Does anybody know something to help me? Thanks in advance
[Fire Original Android Development] DB126:
Please don't cross post. Responded to earlier post: http://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/post67649536
[Fire Original Android Development] razlack:
This has been happening to me for a while on both CM12 and FireNexus roms for quite some time. Usually happens when I have my bluetooth headphones connected. Well, it feels that way as I only notice it when streaming videos.

I have not been able to fix it or find a work around :(
[Fire Original Android Development] oae08:
I have the same problem. At first i thought i may be something with my wifi but after trying other devices it seems only my amazon tablet with cm12 has this problem.
[Fire Original Android Development] monza1412:
Are you in the latest release (14 jun)? Did it happen with earlier releases as well?
[Fire Original Android Development] DB126:
This problem seems to hit some and not others. I have not experienced it on the latest build or its immediate predecessors. Occasional wifi disconnects and loss of internet connectivity do occur but no more frequently than on my other Amazon devices from several generations running various roms. In contrast my mobile, laptop and various wireless gadgets rarely loose connectivity. Appears to be an Amazon thing.
[Fire Original Android Development] mainstang:
Exactly this. I had no issues until I tried using Bluetooth headphones and wifi at the same time. I thought I was going crazy lol.
[Fire Original Android Development] EncryptedCurse:
As a tip, you can go into Display & lights > LiveDisplay > Color calibration and turn down the green to 95% or so in order to remove the greenish tint of the screen.
[Fire Original Android Development] Root????????????????:
Is the $50 Fire tablet x86_64

X86

or what

The question is for g-apps
[Fire Original Android Development] Doggy77:
Use "arm", version "5.1" and "pico" or "nano".
[Fire Original Android Development] oae08:
i dont know as this is my first build that i have tried. hope it will be fixed in the next update.
[Fire Original Android Development] ggow:
[MENTION=5488402]Davey126[/MENTION] for awareness

- I have tested exFat on this ROM and it seems to work with no problems here.

- Formatted 32gb microsd card in windows

- Installed CM-12.1 + SuperSU 2.65 stable (I always use SuperSU)

- Put the card into the Fire Tablet

- Reboot and Voila.

I haven't got a 64gb or 128gb to test
[Fire Original Android Development] ggow:
New Build is Up

- Dated 10 July 2016

- July 2016 AOSP Security Patch Level

- Re-tested exFAT with 32GB Sandisk microsd card and seems to work fine.
[Fire Original Android Development] DB126:
Interesting. Results do not mirror my findings in a similar test (here) so likely some nuance in card characteristics or format laid down as you obviously removed the app suite variable going with a fresh CM install. Good news is the Fire build of CM 12.1 can support exFAT (yea!) but there may be some dependencies/incompatibilities that have not been fully identified.

I will try to duplicate your findings with a clean install of the latest build in a day or two. I have a several 32gb cards to choose from and various tools for formatting. See what shakes out.
[Fire Original Android Development] Munns86:
I see the op mentions flashfire .50 and I just wanted want to make sure I don't break anything when I do this upgrade. Is it OK if I use the version off the play store ? It's been updated to .51
[Fire Original Android Development] Az Biker:
Please remember to show respect to all XDA users... JUNIOR members who need to learn XDA etiquette is to be expected, SENIOER members responding with disrespect or condescension is not.

Rather than wasting a post with sarcasm and berating another user, make a constructive suggestion that helps the user learn, and maybe next time they'll figure it out on their own.

If posting a helpful response is too difficult, don't respond at all. Lack of respect will not be tolerated.
[Fire Original Android Development] ipdev:
Just flashed lp-fire-nexus-rom-ford-20160615 yesterday with ff .51, didn't seem to have any trouble.

(Flashed from fireos 5.1.1)

- Note: FlashFire 0.51 was a mid-release. The next version might be out sometime this week.

http://xdaforums.com/showthread.php?p=67641073
[Fire Original Android Development] DB126:
Yes - that's fine.

---------- Post added at 02:27 PM ---------- Previous post was at 02:10 PM ----------

I assume this common sense reminder is in response to a caustic post that has since been deleted. I would hope that exchange was an exception as I have generally found the discourse in the Amazon Fire forums to be both respectful and (hopefully) helpful to new members.
[Fire Original Android Development] DB126:
- finally found time to run a few tests

- inserted the same 32gb card from previous test (still had exFat format from Win 10)

- recognized card but wouldn't read it; rebooted; same behavior

- flashed B20160710 via FF 0.51 with a trailing cache/dalvik wipe; no issues

- reinserted card after second boot; recognized but could not read

- rebooted with card in device; card recognized and readable - YEA!

- attempted to duplicate findings by ejecting/reinserting without rebooting

- card recognizable and readable on every subsequent attempt - GRR!

Thoughts

: Likely there was nothing fundamentally wrong with the prior CM 12.1 build wrt reading exFAT formatted cards. I do not have an immediate explanation of why my test card would not initially read and then suddenly became accessible. Nor can I explain why others are having problems with exFat cards other then the size of the card itself which is often 128gb for those who have reported troubles. As noted in my June 20th post difficulty accessing exFat formatted devices is not uncommon with post CM 11 builds across a variety of devices but apparently it is not a licensing issue with this particular build.

Bit of a head scratcher that will likely get sorted as others report their experiences (successes/failures).
[Fire Original Android Development] frankvalve:
kindle fire 5.1 brick

hi, I wonder if anyone knows how to fix the problem the brig after installing the CM12 only stays CM12 logo and does not enter recovery mode , only in fastboot mode , there aguna way to fix it ?. Thank you
[Fire Original Android Development] GhostRider86:
Hi. Recover with Amazon Tool, root again and install CM once again
[Fire Original Android Development] frankvalve:
Kindle fire 5.1 brick

Where I get amazon tools?
[Fire Original Android Development] DB126:
Perhaps I am misunderstanding OPs situation but this would appear to be an unfortunate 'no-boot'/inaccessible-recovery' scenario that at present has no solution. Such outcomes were more common with early rom and FlashFire (<0.32) builds but have since been resolved. Contents of the recovery partition are likely intact just inaccessible by any means. Suspect a preloader corruption that may someday be fixable. If the device is still under warranty an exchange is your best option.
[Fire Original Android Development] whitesymphonia:
My 128gb microsd (exfat) doesn't show up using the Nexus rom. It's a sandisk, from Microcenter, so not worried about it being a fake. I haven't found anything that says there's support for 128gb microsds. Can anyone point me in the right direction?
[Fire Original Android Development] empathyislost:
Can someone please confirm if this build of CM 12.1 has SD card app storage built in? As in, I can format my SD card from Settings > Storage & USB and then I will be able to move big apps over to the SD card natively (without using any complicated partition / 3rd party apps)?

Thank you!
[Fire Original Android Development] Munns86:
Yes this build does support native app moving to the SD card.
[Fire Original Android Development] empathyislost:
awww yeah.jpg

Thanks!
[Fire Original Android Development] Claghorn:
Can someone tell this poor feeble minded user exactly what that means?

I can find a boot.img file in the cm .zip file. Is that what I tell it to boot? If not, what is the modified_boot.img file referred to in this thread, and where do I find it? What exact command do I give it?

fastboot boot boot.img

Is that the one?

P.S. I got my new prime day fire running CM following all the instructions, so I'm golden till I have to reboot :).
[Fire Original Android Development] sd_shadow:
old directions, has nothing to do with current builds
[Fire Original Android Development] DB126:
Only a limited suite of apps can be moved using native functionality.
[Fire Original Android Development] Norapapa:
I will insall supersu. Can I flash supersu Zip with flash fire, with flash Zip/ota? Works the newest Version of supersu?
[Fire Original Android Development] antiwesley:
Wanted to let everyone know that I was able to use the methodology to get my Prime Day Fire to CM 12.1 :)

I had to dig a bit to find a root solution, and using SuperTools, I was able to root after a few tries.

Flashfire 0.50 wouldn't run, but an update to 0.51 worked just fine, and it loaded and worked the first try.

Using a Samsung 128GB card, and it recognizes and uses it as external storage just hunky dory as well.

My only question/concern is when and if will we see an update to CM 13? I know it's probably a far way off, but there doesn't seem to be an

update option for CM proper. (and yes, I know it's unsupported, so we are dependent on the kindness of strangers to get a newer version...)

So has anyone tried CM 13 on it yet?
[Fire Original Android Development] GhostRider86:
Good to hear.

CM13 will not running, cause the stock kernel is used. More technical explanation from others ?
[Fire Original Android Development] DB126:
Yes to all.

---------- Post added at 02:20 PM ---------- Previous post was at 02:13 PM ----------

exFat support seems to be inconsistent on this device regardless of custom rom (in contrast to FireOS). Larger cards appear to be more problematic. See following post for a bit more detail.

http://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416/post67718114
[Fire Original Android Development] corax2.05:
Hi,

Yesterday I tried to install this ROM. All seems to be fine, but after reboot the tab stuck on Amazon logo.

I reanimated it by sideloading the stock ROM.

The tab ist on fireOS 5.1.1.

I rooted with supertool (kingroot) and installed via supertool flashfire 0.50.

I put the CM ROM and gapps on external sd card, checked md5sums and followed the steps in #1.

After reboot it stuck on Amazon logo.

Any idea what's going wrong?

Edit:

My second try worked very well!

The only thing I changed, I used the actual flashfire 0.51.

Something strange... on first try, the flashfire 0.50 installed by supertool seems to work. On second try the app crashed and I had to install 0.51.

Anyway...

A big thanks to the devs for this really fine and smooth working CM ROM!
[Fire Original Android Development] core_x:
Is it necessary to wipe internal storage? If not I could put the cm files on my internal storage and flash it from there right?
[Fire Original Android Development] DB126:
No need to wipe internal storage (silly recommendation in the absence of other issues). To the contrary, I recommend placing roms and any other zips targeted for flashing on internal storage, not a SD card or OTG device. One less thing to go wrong during the sensitive flash process.
[Fire Original Android Development] nickhaven:
Has anyone noticed that the development option for mock location isn't wanting to stay on?
[Fire Original Android Development] RVD26:
Does anyone have step-by-step instructions (or preferably a video) on how to install CM 12 on the Fire?

I have Fire OS 5.1.4, so I know I have to use FlashFire.

But how do I install FlashFire?

Do I need to install SU?
[Fire Original Android Development] ldeveraux:
I've not done it this way, but you need to downgrade, root, then install flashfire from the play store. Not sure if you can downgrade (like I said, been rooted since the beginning), but search the threads for what to do with your OS version
[Fire Original Android Development] DB126:
http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Original Android Development] jratt:
which gapps Platform, Android, and Variant do i choose? i have the 16gb version.
[Fire Original Android Development] DB126:
Arm, 5.1, mini or smaller. Anything not included in the selected package can be obtained from the Play Store.
[Fire Original Android Development] Doggy77:
The steps I described worked for me for at least 5 tablets I flashed so far. My intention doing it like this is, to have a surely clean memory after the flash. This is alos my preference when upgrading any ROM (regardless which devices), I never chose the "dirty" way, instead I prefer to restart from the beginning with a clean devices. Thus to ensure that all problems that may arise do not come from leftover aps or app settings.

Yes, it is some work to do, if you have to reinstall all the apps needed. But I am willing to go this way. It often results in a clean up of about 1/3rd of all apps because I do not need them any more. The backup of essential data and apps (pictures, contacts, WhatsApp, Threema, SoundProfile,...) is also done regularly, not only as preparation for flashing. My device(s) may crash or crush any time, I backed up the important things at least every month. (I see myself as a "IT service provider" for my wife and my kids, so I also back up their devices on this regular basis. This backup concept already avoided a lot of tearsat my beloved ones.)

I never experienced any SD-card related problems, therefore I never had any concerns for applying these steps. If you can't or don't want to use a SD card: you have to place the files needed on the intenal memory and leave "internal storage" unticked at wiping.

Greets,

Doggy77
[Fire Original Android Development] DB126:
Happy it works for you and also glad to see the other precautions (eg: regular backups) which is solid guidance regardless of install/upgrade preference. That said, wiping internal storage offers no real benefit but if it fits ones style there is no real harm other than the risks (small) and extra work outlined in my original post.
[Fire Original Android Development] core_x:
Does this rom include multi window feature?
[Fire Original Android Development] yochananmarqos:
It sounds like you're confusing the data partition with internal storage. Apps are installed in the data partition, so neglecting to wipe that is considered a dirty flash. A clean flash involves wiping data, system, cache & dalvik.

However, some apps save user data in internal storage, so I understand why you like to wipe it for a fresh start.
[Fire Original Android Development] GhostRider86:
cm12 does not have multi window feature, so no
[Fire Original Android Development] DevilsClaw1991:
So I did everything as explained above and the following error showed up: "cant install this package on top of incompatible data. please try another package or run a factory reset" Then the Tablet starts and optimizes system storage and applications. I tried it twice but it doesn't work. Any idea why?﻿
[Fire Original Android Development] GhostRider86:
Do you changed the order, so first wipe then flash?
[Fire Original Android Development] jratt:
This is great really makes this cheap tablet worth buying. Only things I dislike is the screen brightness doesn't go low enough, dpi should be set as 200 dpi to make everything fit this form factor, and orange status bars in power saving are ugly. Also wish I could boost audio volume a bit
[Fire Original Android Development] DevilsClaw1991:
I choosed Wipe first at least but the Flashes were before. How do I change the order?

I just started the Fire again and now nothing is on there. How do I reset it to factory settings?
[Fire Original Android Development] GhostRider86:
Ok so this is the issue. Click and hold and then drag and drop, so wipe must be the first as stated out in OP
[Fire Original Android Development] searchworlds:
Does anyone else have problem with brightness not working?

Is always at a fixed brightness , and the slider does nothing to change it .
[Fire Original Android Development] DevilsClaw1991:
Jezz.. So simple. Thanks for the answer.
[Fire Original Android Development] GhostRider86:
You are welcome
[Fire Original Android Development] DB126:
Reboot; should fix it. Others have noted a loss of brightness control after prolonged usage and/or game play with this rom and Fire Nexus. Likely a side effect of high memory utilization. From a user perspective not much can be done aside from tweaking kernel parameters which is not for the faint of heart.

---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------

- minimum panel brightness and maximum volume are kernel issues; nothing can be done via rom or xposed tweaks

- rom correctly uses native panel DPI by default; you are free to tweak it via integrated settings or external module (greater granularity)

- I suspect (can't confirm) some crafty xposed module will permit changing status bar colors when in power saving mode
[Fire Original Android Development] searchworlds:
Thank you very much, I couldn't find a similar problem searching in this forum, reboring solved it!

:)
[Fire Original Android Development] DevilsClaw1991:
Well now I have another problem. I wanted to reset the tablet to the factory settings and did and now when I start it the lock screen without adds appears. When I try to unlock it it shows the background without apps for 2 seconds and goes dark. I can only access the settings by swiping down the top bar but I can't use update? What can I do? Did I brick it?
[Fire Original Android Development] GhostRider86:
If you can access the settings, you did not brick it ☺

What do you want to do? Start from beginning, rest with Amazon tool to FireOS, flash Cm with FlashFire
[Fire Original Android Development] DevilsClaw1991:
Okay so should I connect it to the PC and use the Supertool by Rootjunky again? Could you give me an explanation for dummies on how to proceed from here since I can't do anything except accessing the settings. And I can't even use the Update feature. My goal is to firstly get it working again, then get root access and this time successfully installing CM 12.1

You'd be my hero if you can explain this in detail to me :victory:
[Fire Original Android Development] GhostRider86:
Yeah, firmware restore with rootjunkies supertool is possible, see https://youtu.be/RQLoH-ahjy4

So first restore original firmware (same version as originally installed), then root, and flash CM, see OP for instructions. How this helps.
[Fire Original Android Development] jratt:
You will also need to downgrade to fireos 5.1.2 to root
[Fire Original Android Development] GhostRider86:
If it is on higher version, yes, if not then not?

If it is on 5.1.1 or below, keep this