yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Vlasp:
Once the camera is fixed, I will go to CM12.1 ASAP, I just use my Fire as a backup camera if my phone runs out of battery (basically all the time), so that is a major issue for me. I also play Clash of Clans a lot, and when I used the first untethered build, it shut down every 5 minutes. Stock OS is fine for me, but when CM becomes as stable as stock, I will go to CM for the goodies.:D
[Fire Original Android Development] ggow:
- Thanks for this [MENTION=4375260]diegocr[/MENTION]

- The commit causes bootloop on CM12.1

- Looking into it now.
[Fire Original Android Development] diegocr:
rm form vendor folder and build it, slim create them.
[Fire Original Android Development] ggow:
Yeah, I needed to update my PRODUCT_PACKAGES.
[Fire Original Android Development] diegocr:
:good: we are trying to fix camera and full screen video
[Fire Original Android Development] ggow:
New Build is Up

- Dated 2015-12-01

- Change log on Post #2
[Fire Original Android Development] sandman512:
Ok, so trying to update to the latest version. Installed drivers, no problem. Used the SU TOOL, device was recognized, click #5, device went into FASTBOOT MODE and just hung there. Any advice?

Thanks!
[Fire Original Android Development] Darkside1984:
Is it necessary to format the device before update installation?

Enviado desde mi KFFOWI mediante Tapatalk
[Fire Original Android Development] ggow:
- No, just flash the ROM, SuperSU.zip and then reboot :)
[Fire Original Android Development] ggow:
Did you flash SuperSU after flashing the ROM?
[Fire Original Android Development] spicypixel:
Good stuff, just waiting on confirmation HW accelerated video works - only really use the tablet for plex at the moment so fairly important.
[Fire Original Android Development] thechosenone43:
Same for me ? stuck in fastboot mode on the Fire. Tried to copy and paste the "fastboot boot image TWRP 2.8.0.7 but the answer in the window was.. Cannot find the Image!!? I have it in the same folder like the cmd.exe! Please help. Thanks
[Fire Original Android Development] k4y0z:
The Image is called "TWRP_Fire_2.8.7.0.img"
[Fire Original Android Development] EgotisticalElf:
FlashFire 0.30 has some issues with opengapps and cm due to default chmod's on files. It was fixed in the 0.31 release.
[Fire Original Android Development] m00head:
Here are the links to the MicroSD cards recommended by Amazon, linked to from within the FireOS Storage settings if you choose to buy a MicroSD card:

Amazon US: http://www.amazon.com/SanDisk-micro-Memory-All-New-Tablets/dp/B013TMNKAW

Amazon UK: http://www.amazon.co.uk/SanDisk-microSD-Memory-All-New-tablets/dp/B013TMNUCA

Insert and Manage a MicroSD Card
[Fire Original Android Development] Y314K:
Before any ROM is made. We would need a working FlashFire for them. Right now we need logs of FlashFire on ROOTED HD6, HD8 & HD10 tablets.

more info here: http://xdaforums.com/hd8-hd10/help/custom-rom-cm-hd-8-t3354757
[Fire Original Android Development] Sulinjr:
Interesting, the card I have is of high quality so I would be surprised if that were the case. I'll have to buy another recommended card and test that as a possible variable.

I'd have to agree, I'm all for hard data testing for different variables compared to a control test. I believe [MENTION=5749760]ggow[/MENTION] is aware of the issue and looking for a possible solution. As he had me test his latest release for any changes. If he is unable to find a solution to the disappearing app icons on the home screen, you very well may be right about the SD Cards being the source of the problem. I'll buy another SD card and test them against each other.
[Fire Original Android Development] GioXmen321:
error, cant install this package on top of incompatible data How do I fix this?

nvm fixed it!
[Fire Original Android Development] XmanORE:
Ok...downloaded and installed CM12 and gapps from these links today. CM12 appears to have installed fine but gapps didn't. I'm stuck on a functioning install of CM12 but with no apps and I can't figure out how to get them installed. I don't have a flash app any more (used flashfire when it was running Fire OS but that's gone) and can't figure out where to get any apps.

Sorry to be stupid, I'm stuck here.
[Fire Original Android Development] GhostRider86:
Adb sideload Gapps,

Or install flashfire as apk (root is built in this CM12 ROM under devolper options)
[Fire Original Android Development] platypoid:
Check out the thread for Root Junky Supertool - you can install Flashfire with that but make sure you only use Flashfire version .31 . Then you can install the pico or nano gapps - he has them on his site also along with the Supertool .

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire Original Android Development] XmanORE:
I'll take a look at that. Can't seem to get the tablet back online with ADB now, Windows drives seem to have bonked. Dang.
[Fire Original Android Development] sd_shadow:
https://download.chainfire.eu/956/FlashFire/FlashFire-v0.31-20160405175326.apk
[Fire Original Android Development] platypoid:
Did you turn Android debugging back on after you loaded up CM ? Also you can enable root in CM developers options where you turn Android debugging on .
[Fire Original Android Development] williamvito:
even though it wasn't successful in the latest build, thank you [MENTION=5749760]ggow[/MENTION] for attempting to fix the app/sd card issue, hoping you fix the issue and appreciate the effort.
[Fire Original Android Development] error28:
Because it's broken?

I just flashed 20160412 from stock 5.1.1 with FlashFire and was quite surprised to discover that root is not working at all after enabling "Apps and ADB" in developer options. I cannot su from an adb shell and root checker apps complain that the device isn't rooted.

If there's some way to get this working, I'd love to know about it, but in the meantime it looks like I'm going to have to use SuperSU.
[Fire Original Android Development] sd_shadow:
you need to reboot after enabling Apps and ADB
[Fire Original Android Development] error28:
OK, you were right, I'm an idiot today :)
[Fire Original Android Development] sd_shadow:
no worries, it's an easy step to miss
[Fire Original Android Development] Sulinjr:
Dude if I had a dime for each time I've done something like that. Haha You just learn to start double checking yourself and you'll come across your error sooner or later.
[Fire Original Android Development] ggow:
Bitbucket account updated with latest changes.
[Fire Original Android Development] m00head:
This one, right?

https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/branch/cm-12.1
[Fire Original Android Development] ggow:
Yes
[Fire Original Android Development] ggow:
New Build is Up

- Dated 20 April 2016

- Updated CM Code
[Fire Original Android Development] ggow:
FlashFire 0.32 is out
[Fire Original Android Development] riverstyxxx:
Question: If I do an upgrade over a previous CM, will I have to go through setup again? Or will all of my apps and wallpaper still be the same?
[Fire Original Android Development] theechap:
As long as the only wipes you do involve the cache and dalvik cache, you should be fine. I've had a Flashfire flash go bad though and I had to reinstall Fire OS and start all the way over. Lesson learned: only update a CM build when you really need to (unless yours is older and has TWRP).
[Fire Original Android Development] sridharpg:
Recovery and gapps issue

Right now I face 2 issues. I tried installing gapps via FlashFire but it gets stuck at "Gathering device & rom information" and never gets installed. So I tried installing TWRP recovery. Now I am not able to boot to recovery at all. It gets stuck at Amazon logo.

Any idea how to resolve these two issues?

Edit: GApps issue is fixed after installing FlashFire 32(latest as of now).
[Fire Original Android Development] RoroTiti:
Faulty battery indicator

Hello !!!

I installed CM on my tablet received before yesterday and it works perfectly. So, thank you very much for this intense and perfect work !!!

BUT I have concerns about the battery level. The tablet discharge abnormally slow (1% every 10-15 minutes in heavy use). Therefore, it abruptly turns off about 30-40% of battery level because the real battery level is likely to 0%.

Where does the problem come from ? Would I flashed CM with a too low level of battery? I tried to recalibrate the battery but it did not work.

Thank you in advance for your answers !!!

---------- Post added at 03:58 PM ---------- Previous post was at 03:44 PM ----------

Which was the version of your stock firmware ?
[Fire Original Android Development] DB126:
Unlikely this is a ROM issue. I believe battery level is calculated by the kernel and simply passed to the ROM for display. Possible you have a defective cell in the battery pack. I also use CM 12.1 on this device and have not noted the behavior you describe. However, discharge is not linear with the final 25% depleting considerably faster than the first 25%. I have observed this on two 2015 Fires running different ROMs (CM 12.1 and Fire Nexus). For completeness both have v5.0.1 bootloader and associated kernel.
[Fire Original Android Development] m00head:
It is possible to temporarily boot into TWRP, but only if the bootloader from FireOS 5.0.1 is still intact.

If your device can boot into CM 12.1 you may want to try flashing a stock recovery img using Flashfire, but it must match the exact version of FireOS you were on before you installed CM 12.1:
[Fire Original Android Development] Hungerfordf1:
Fire os 5.1.2

Will this work on fire os 5.1.2 with flashfire. Thanks.
[Fire Original Android Development] m00head:
Yes, this CM 12.1 ROM will work with the Amazon Fire 7" 2015 tablet if you currently have FireOS 5.1.2 installed. Make sure it is exactly 5.1.2 though and not 5.1.2.1. You will need to root the device first, so I suggest you start with Rootjunky's SuperTool:

Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more

You may also want to consider an alternative ROM for this device, such as one of these:

[ROM][AOSP] Fire Nexus ROM - LMY49J [20 Apr 2016]

[ROM] SlimLP 5.1.1 for Amazon Fire 2015 (Ford)

[ROM] Resurrection-Remix-LP-v5.5.9 Amazón Fire 2015 (Ford) (17-12-2015)
[Fire Original Android Development] Jstame:
Here's the link to restore stock recovery.

http://xdaforums.com/amazon-fire/help/restore-stock-recovery-amazon-fire-7-t3351480
[Fire Original Android Development] tuanbo91:
thanks, this is exactly what I need
[Fire Original Android Development] RoroTiti:
Any solutions ?

I have received today a new model of this tablet (I have returned the previous for defect :)). But with my new, the problem persist ... Any solution ?

EDIT: The new model is with 5.1.2 bootloader, as the previous

EDIT2: I have also tried SLimLP and the Nexus ROM on the 2 tablets and the problem is the same.
[Fire Original Android Development] DB126:
Is what it is. There is nothing you can do to tune reported battery status. Learn the shut off point and adjust usage accordingly. For reference I get 5-6 hours of screen on time (modest brightness) on this device regardless of ROM. I do optimize FireOS by killing a number of background services. Nexus and CM start out clean.

It's possible a power glitch was introduced in 5.1.2 (stock kernel is updated with stock ROM) but haven't seen this mentioned elsewhere. If so Amazon will likely fix it in a future build.

I am surprised you were able to cycle through two ROMs and two full discharge cycles on two devices in <24 hrs. ?
[Fire Original Android Development] sridharpg:
Thanks, I restored the tab to stock recovery, now everything look good :good:
[Fire Original Android Development] RoroTiti:
Yes, I was be able to do this because I hadn't only 24H but 72H. I have received my first tablet the 19, as I said yesterday. Also, I live in France and I can be delivered by Amazon in the afternoon if I order the morning :D !!! To speed up the handling, I played at big games, with maximum brightness and Wi-Fi and Bluetooth on.

Actually, I test the first discharge of my new tablet. I will come give you news in the evening !!! :)

In closing, thank you for your interest in my problem is very nice !!! :D
[Fire Original Android Development] DB126:
It's possible the aggressive use of HW components accelerated the non-linear voltage drops observed here. May just be a battery pack characteristic.
[Fire Original Android Development] RoroTiti:
Finally, I decided to flash CM with 100% battery after restoring the original ROM and the problem is solved !!! Thank you for your guidance, and for this great ROM without which I would never have bought this tablet !!! :D See you soon !!! :laugh::laugh::laugh:
[Fire Original Android Development] DB126:
FYI - updated 20160404 -> 20160420 via FlashFire 0.32 using NO wipes and leaving all FlashFire options at their default values (no silly checking/unchecking mount options trying to outguess the developer's defaults). ROM updated in <3 min from FF launch to resuming normal operations. Easy peasy.

While more caution/steps are obviously needed switching from another ROM updating CM 12.1 to the latest build typically is a non-event with the latest versions of FlashFire or TWRP. Making a backup of your current install is always good practice should something go horribly wrong; in this case I didn't bother. I sometimes switch parking spots without fastening my safety belt too. Living on the edge ....

Starting with v0.32 FlashFire has a 'new' (meaning largely untested) feature to backup/restore the existing recovery partition during the flash operation. This may offer some comfort to those worried about loosing access to recovery options should the flash go bad. However, recent builds of FF and/or CM seem to have addressed the problem where access to stock recovery was blocked following a borked CM install. I would be wary of trying the FF recovery preservation feature in this initial release as it may do more harm that good until all the kinks are worked out.
[Fire Original Android Development] Signor Rossi:
2 broken FlashFire version ensured me it's OK to do a full Backup prior to each flash of Os

Gesendet von meinem OnePlus One
[Fire Original Android Development] staber:
Install gapp

Hi,

install it without any problen. CM works perfectily.

The only probleme a get is that Gapp didn't install!!! And I can't run flashfire again it say 'root access could not be acquired, or you are not running SuperSU or (CM SU with SELinix set to permissive) Are you rooted'

I have activated root access in the developer menu and SElinux is set to permissive....

SuperSU did not want to settle...

any idea ?
[Fire Original Android Development] ipdev:
What version of fireOS did you start from?

Once or twice I had to re-root after rom install.

Starting from fire 5.1.1 I used / modified this method.

http://xdaforums.com/showthread.php?p=64344114
[Fire Original Android Development] jboxer:
Did you reboot tablet after enabling root access in developer options?
[Fire Original Android Development] staber:
5.1.2

Yes.

I manage to root with kingRoot. but same issue with SU or FlashFire
[Fire Original Android Development] loocool2:
OK, so I tried to create a second partition on my SD card using apps2sd and it is now undetectable after a reboot by the tablet and my computer, I tried flashing a new version of CM to diagnose the problem, but that does nothing.

Tried looking for similar problems by other people, but they didn't work or were not viable as I don't want to have to format my SD card. Base bootloader version: 5.0.1
[Fire Original Android Development] DB126:
You'll probably need to reformat the card. While most of my experience is with Link2SD it is probably extensible to similar utilities like Apps2SD. Had a couple occasions where a card couldn't be seen after fiddling with partitions from Android. Reformatting and repartitioning the entire card in Windows (via Mini tool Partition Wizard) solved the problem. Make sure both partitions are marked as 'primary'.
[Fire Original Android Development] loocool2:
But my computer can't even detect the card. So I can't format the card or do anything with it, other than hope it comes back to life.
[Fire Original Android Development] DB126:
Assuming your 'computer' is running Windows you'll need to use Disk Manager to access/format the card.

http://pcsupport.about.com/od/tipstricks/f/open-disk-management.htm
[Fire Original Android Development] Sulinjr:
I've had this problem. I was able to resolve it in part by formating completely using the built in Android reformat. Then use Windows to make the necessary partitions.

However I kept running into issues because I had a bigger 64GB Card. I ended up just going with flashing Xposed and using Xinternalsd. Now the bigger game files run directly off my external memory and I can use the native app to sd functionality of CM12 to move those over to external storage to save even more memory.

The only issue I've experienced with this is the app icons will sometimes disappear from the home screen after a reboot (only app icons of the apps I've moved to external storage) However I'm still in the process of testing this for [MENTION=5749760]ggow[/MENTION] to determine if this is an issue with CM12 or if it has something to do with the actual sd card's properties. I will test on another Amazon Fire recommended micro sd card and post my results.
[Fire Original Android Development] loocool2:
I used XInternalSD and OBBonSD to get the majority of my large games/files to my sd card, then realized that data could not be moved. That's where Apps2SD came in. Created a second partition, set it to primary, no swap, and reboot. Boom! No access to the SD card! However, thanks to [MENTION=5488402]Davey126[/MENTION], I found, recovered the files using ZAR, formatted the SD, and am in the process of recopying everything back in... because my file structure is messed up...
[Fire Original Android Development] Sulinjr:
Did you format the sd with windows to make like a 4-8gb partition to install apps onto and get it working? I think I may give it another shot because back when I did it there were other issues that are no longer present in the latest CM12 builds.
[Fire Original Android Development] drag0micr0:
I have just run into a similar issue where the root won't work but i did get gapps flashed but now my tablet wont even connect to my computer unless in the middle of a boot or if it is in fastboot. I tried kingo root but it didnt work. I was somehow able to get the built in root to work momentarily but now it doesnt work.

**UPDATE**

I was able to do a reset and now my computer connects to my kindle but ADB doesn't connect or even find my kindle. Yet again i can still go into fastboot and recovery but i'm stuck on cyanogenmod.
[Fire Original Android Development] Xplic1T:
Is there anyway to enable Tethering & Hotspot capability on this ? I use it for private networks and to host files otherwise ?

Why did Google turn this flag off in Lolipop and higher builds ?
[Fire Original Android Development] DB126:
You posted the same question in multiple threads associated with this device. Spamming the forums is a great way to get a non-response. Will pick this up is the thread you created in the "Q&A, Help & Troubleshooting" section.
[Fire Original Android Development] drag0micr0:
i was able to fix the root. I had to reset my tablet so the computer connection would work then i updated the adb drivers and such and used the supertool to root it with supersu and now the root is fully functional again as far as i can tell.
[Fire Original Android Development] elbastardo1:
Not sure if it's an issue, but since latest update facebook and messenger app take hours to install (literally hours). This didn't happened before. Haven't tried old facebook apps yet
[Fire Original Android Development] jboxer:
I have two Kindle Fires. One is CM12 and one is stock. Purchased around same time and both came with 5.0 on them. The stock Fire also takes a very, very long time for Facebook and Messenger to install. I don't this this issue is CM12 on this device only.
[Fire Original Android Development] drag0micr0:
Any app for me takes a long time to install unless I leave the screen on
[Fire Original Android Development] Xplic1T:
I've been having issues with the GAPPS portion. Using 5.1 PICO but it hangs up on FlashFire under obtaining rom information. Should I be using something else ?
[Fire Original Android Development] fastcar22:
how do i upgrade to latest version of CM 12 from TWRP? i installed CM 12 using TWRP earlier and i want to upgrade to latest version without loosing my apps, can someone help me on how to do this?
[Fire Original Android Development] sd_shadow:
same steps in post #1 except no factory reset
[Fire Original Android Development] s_k_u_ll:
I'm having the same issue! open gapps pico 5.1 can not be installed with flashfire 0.30, but it works with 0.31!

https://download.chainfire.eu/956/FlashFire/FlashFire-v0.31-20160405175326.apk
[Fire Original Android Development] Xplic1T:
Going to try flashing the next up ... will let you know.
[Fire Original Android Development] DB126:
Encourage going with the latest version of FlashFire (currently 0.32) as it contains incremental refinements that improve overall reliability. There are known issues with v0.30 and should be avoided.
[Fire Original Android Development] Handsome Jack:
Why not use Firefox browser? It has Ad-block.

Chrome doesn't have Ad-block.
[Fire Original Android Development] elbastardo1:
Is there a way to swap the external SD and the internal SD (swap sdcard0 and sdcard1)?

I tried the xposed module XinternalSD but all it did duplicate sdcard0 (internal) as sdcard1 and left my external sd card unmounted.

I know this to be possible since I have a phone (blu Life one X 2016) that internally does this. IMO I think it would be a great benefit for this tablet since it has such a limited storage.
[Fire Original Android Development] DB126:
Not sure about swapping. For more reliable SD card access and application migration try Apps2SD or Link2SD. I use the latter and have experienced no difficulties. Card format is important; be sure to follow instructions carefully. There's a fairly detailed post in the Nexus thread. Apps2SD also gets good reviews.
[Fire Original Android Development] jul_ass:
Good night! What should I choose in FlashFire on first time: fresh installation or upgraiding? My OS in 5.1.1. Thank you
[Fire Original Android Development] DB126:
[MENTION=7443715]jul_ass[/MENTION] Following video should help. Procedure is similar for CM12.1. Pay close attention to the order of operations; wipe needs to be on top.

https://m.youtube.com/watch?v=NaCBSuUuhRE
[Fire Original Android Development] Handsome Jack:
I have Fire OS 5.1.2

Do I have to root the device first before install FlashFire?
[Fire Original Android Development] DB126:
Yes. Use Kingroot. If your device arrived with a lower version of FireOS then upgraded to 5.1.2 you will need to reload 5.1.2 for Kingroot to work.
[Fire Original Android Development] Handsome Jack:
After rooted with Kingroot, should I replace KingUser with SuperSU?

Can you provide a link to the guide about rooting and replacing? I have searched everywhere.

Thank you.
[Fire Original Android Development] GhostRider86:
just Search for supertool, it does the steps automatically.supersu works better with flashfire
[Fire Original Android Development] bigpapa007:
Hi, i have a question, i have a 2015 build of the rom i used and installed TWRP back then when i first rooted and flashed the rom. Now i would like to update to the latest version but i would like to know if when i dirty flash with twrp if something will happen to the apps y have moved to the sd with Link2SD. can i just go ahead and dirty flash new version and there will be no problem with the moved apps? will it just stay the way it is right now? thanks :)
[Fire Original Android Development] madaone1:
*****

After you update via TWRP, you will get a mount script error from Link2SD. Recreate the mount script using the same format of the SD card you used originally in Link2SD for the second partition, then reboot.