yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Welcome to XDA (I think). Since you are relatively new let me offer a little guidance:

- best way to make a positive impression is to criticize a volunteer developer on one of your first posts

- the rom ("CM scene") you are questioning is very stable and does not need to be updated

- it is very stable because the developer selflessly invested countless volunteer hours bringing it to YOU

- volunteer developer also cranks out regular updates which are summarized in the change log

- we could get no updates or undocumented updates or broken updates that brick your device (ever used someone elses rom?)

- if you think you can do a better job have it it. Code is available for anyone to tweak. Don't forget to copiously document all changes

tl;dr - stop being a brat.
[Fire Original Android Development] fmc000:
:good::good::good:
[Fire Original Android Development] paarkhi:
Sir, Thanks for your kind updates (already thanked by pressing the thanks button, just wanted to express the feeling in words)
[Fire Original Android Development] tweekde:
Hi there and first of all thanks for your great work and taking care of the rom. :good:

Second, I got a small problem and I can't figure out the source.

Following behaviour:

#1

* fully charged tablet with first 2016 rom

* using it as main user, not caring about open apps

* battery drain in stand-by over night acceptable, survives even two nights

#2

* again, fully charged tablet

* changing to secondary user

* using it, carefully closing all apps afterwards

* switching back to default

* full battery drains in stand-by from nightly use until the morning

#3

* again, fully charged tablet

* changing to secondary user

* using it, carefully closing all apps afterwards

* rebooting

* sometimes the battery does not train like in case #1 sometimes it does like in case #2

I'm puzzled and would appreciate any clues, hints or even complete solutions. :D
[Fire Original Android Development] DB126:
To narrow possibilities try disabling wifi either in advanced settings (see 'KeepWi-Fi on during sleep'; choose appropriately) or manually turning it off when you retire. The wifi radio itself is not the problem (goes into low power mode when inactive) but severing external communications will often quiet chatty background apps/tasks. If that solves your problem you can leave it or dig deeper for the cultprit.

BTW - there are many other ways to ferret out this type of problem; suggested path is easy and doesn't require special apps/tools (at least initially).
[Fire Original Android Development] FireBill:
Can I flash Updated Rom over currently running CM-12.1 Using FlashFire?

I Used FlashFire to flash on Fire 5.1.1 and now there is a updated version of CM-12.1. Can I use FlashFire to flash over CM-12.1? I presume if so I would completely flash with full wipe, gapps and supersu as I did the first time.

Thanks,

FireBill
[Fire Original Android Development] ggow:
- From what I've been reading about other peoples experiences with FlashFire

- The best thing would be to:

- Flash ROM, Gapps and SuperSU over the top via FlashFire

- No need to wipe anything
[Fire Original Android Development] DB126:
Please search before posting -> http://xdaforums.com/showpost.php?p=64999089&postcount=1567
[Fire Original Android Development] ggow:
- On the audio issues

- Which games are showing the issue?
[Fire Original Android Development] nickhaven:
Don't judge me, this my daughter's tablet. Cooking mama and two dots.

Sometimes killing the app helps but most of the time it's just gargled audio.
[Fire Original Android Development] funkybrunk:
I think it might be an issue with CM12.1. I've noticed the issue with Shooty Skies and Horizon Chase, first on my LGG2 running CM12.1 (now running CM13, sound issue is gone), and on Ford. Interestingly, my old HP Touchpad running CM12.1 doesn't have the issue, but I believe the kernel used there is based on an outdated version.
[Fire Original Android Development] FireBill:
That's why I was going to update. Maybe I'll wait to see if this is fixed. I did 2 kindle fire's and 1 was for my daughter so the game audio was an issue for her.

---------- Post added at 09:37 PM ---------- Previous post was at 09:27 PM ----------

For me it was on 12.1 and the games were Lego Scooby-Doo Haunted Isle & Rocket Racer with garbled audio or continuous tone like motor boat (daughters tablet, please don't judge :)
[Fire Original Android Development] nickhaven:
Deleted
[Fire Original Android Development] heavy2803:
-Hi, xposed work un this ROM?

-Amazon Appstore/Underground work?

-Kindle app googleplay work?

-the ROM is booteable?

Thanks!!
[Fire Original Android Development] FredBloggs13:
My apologies if I caused any offense I didn't intend to.

I understand the hard work you put into the ROM and I really do appreciate it.

What I was trying to say was that I don't understand what you mean by "Updated CM code". Do you recommend I keep installing the latest version, or only when there is a new feature like the WiFi display, or can I just stick with the 2016-01-04 version which is working great for me?

Sorry!
[Fire Original Android Development] _AnAkIn_:
[MENTION=5749760]ggow[/MENTION]: as the ROM now seems pretty stable, is there any chance you could try to get official nightlies so we can benefit of the auto updater? :)
[Fire Original Android Development] paarkhi:
Yes to all your questions
[Fire Original Android Development] heavy2803:
Does have full acces to install apps on sd card?
[Fire Original Android Development] DB126:
-Yes to all

-Need to flash Xposed framework for Lollipop in addition to apk
[Fire Original Android Development] case-sensitive:
DPI change + CM calendar

First, a huge thanks to ggow for his excellent work! I've been running this rom since it first came out, and it's been most wonderful.

I prefer bigger fonts so I changed the DPI to 180. It works great, except for one small issue: In the "week" view of the CM calendar, under 160 DPI it shows the week view + a small monthly calendar in the lower left hand corner. I like that a lot. But under 180 DPI the montly calendar disappears. I installed the xposed module "App Settings" to change CM calendar's DPI back to 160 (while keeping the rom's DPI at 180), but to no avail --- see the enclosed screenshots.

Note that if you click the menu button in the upper left corner of the calendar app, under 160 DPI it has the "Hide Controls" option (which turns on/off the monthly calendar), but under 180 DPI this option is gone -- again see the screenshots.

I suspect that this is a CM issue, not specific to this ROM. In any case, is there any way to restore this monthly calendar while on week view, under 180 DPI? In case that matters, I run into this issue in the Jan 04, Jan 20 and Jan 26 built (and probably others).

THANKS!
[Fire Original Android Development] ggow:
- Ok, putting that behind us

- Updated CM code means I have sync'ed up the latest changes

- They make changes all the time which you can look at on their github - there are many projects within CM

- It's up to you, if you're happy with what you have then to stay on that version

- If you want the bleeding edge changes then update

- In the change logs on Post #2 I will will say if there are any major updates or security fixes included that I am aware of.
[Fire Original Android Development] ggow:
- The trouble is if I am successful in making it official then we may lose the ability to flash the ROM via FlashFire

- I'm guessing here, but I don't think the changes I made to accommodate FlashFire are going to be accepted as FlashFire is still beta and could cause a couple of the CM repository's to enter a state of flux as FlashFire evolves.
[Fire Original Android Development] ldeveraux:
Why do you people repeatedly reply in a list format when you're not listing anything? That's what commas are for, not hyphens!

-that being said

-things like this

-are comments

-not lists

/rant
[Fire Original Android Development] heavy2803:
Noob question; I can make a whole backup of my stock rom with TWRP or ROM MANAGER, then flash the zip with flash fire? I wanna install CM, in case I want back to stock with all my apps and config. Fire OS 5.1
[Fire Original Android Development] fmc000:
Nothing better to do? Woke up on the wrong side of the bed?
[Fire Original Android Development] nickhaven:
Yes you can with both, TWRP backup is best. Alternatively, there is a return to stock method.
[Fire Original Android Development] heavy2803:
I get this error; Usin flashfire on 5.1

can't install this package on top of incompatible data
[Fire Original Android Development] nickhaven:
I didn't seem to have an issue with flashfire on this ROM. Can you screenshot the options you chose and/or the error?
[Fire Original Android Development] Signor Rossi:
Make sure to tick automount

Gesendet von meinem OnePlus One
[Fire Original Android Development] heavy2803:
obviously rooted, i'm using microsd class 10, Fire OS 5.1.1.

im not an advanced user.

Error says; can't install this package on top of incompatible data
[Fire Original Android Development] nickhaven:
Try using this order and action list inside flashfire. It seems to work fine for me. https://drive.google.com/file/d/0Bxl6L9mLcWDJNWxWQ0VONEc0VEU/view?usp=sharing

Note if it does fail you will most likely have to reroot.
[Fire Original Android Development] sd_shadow:
move wipe above install rom
[Fire Original Android Development] FireBill:
Deleted
[Fire Original Android Development] heavy2803:
Thanks works really fine.. good job, i got a new tablet now.
[Fire Original Android Development] Doggy77:
Move Wipe as first step (deag up, topmost position is after "unknown manufacturer"). Then flash ROM, then flash GAPPS, then tick "Everroot" and make sure to "inject SuperSu", so there is no need to flash the supersu.zip separately.

I have the files needed on an external SD-Card (external in the means of "not the internal partition named "sdcard" but rather the "sdcard1"): 2Gig is enough for ROM, GAPPS and my 2 APK's (FlashFire and FDroid). When wiping I am checking all boxes (including "internal" and "3rd party") to have a totally clean installation.

If your files don't reside on the external SD-card I would be careful by wiping "internal": maybe you wipe the memory and all ZIPs you want to flash are gone...

Best regards,

Doggy77
[Fire Original Android Development] madaone1:
Also noted it in my daughter's Sling Monkey
[Fire Original Android Development] nickhaven:
I believe this "in-game audio" issue has been attributed to cm 12.1 and not directly to this ROM itself.
[Fire Original Android Development] Jaytn:
I am not sure about this and don't even use CM calendar (Google FTW) BUT:

It may not be a bug but be caused by your DPI change. At some point it thinks you're on a phone and shows you a different layout. I think it was 180 at which point the Google Now Launcher for example won't let you turn to landscape mode anymore (that's why I didn't mess with it).

But you probably knew this already since you tried to change the DPI for the app itself - now I don't know to what extend this is handled by the app or the system and what could go wrong - need a dev for that.

Anyway I would like to point out that if you are only after text size you could just change the font size in the settings (it's 2 below the DPI setting) - you can even set it granular in % (for 180DPI that would be 180/160=112.5%)
[Fire Original Android Development] lebleu29:
Help

I'm running 5.1.1 and trying to use the Flashfire method. Running into problems. Flashfire keeps giving me this error after performing a wipe:

detected file system ext4 for /dev/block/mmcblk0p9 error

Any help would be greatly appreciated. :o
[Fire Original Android Development] nickhaven:
A few posts up and your question is answered. I included a screenshot with all the settings you need.
[Fire Original Android Development] heavy2803:
Google play music crash, any fix?
[Fire Original Android Development] DB126:
Works fine. Troubleshooting:

-uninstall/reinstall apk

-wipe caches (cache, dalvik)

-reflash gapps

-reflash CM
[Fire Original Android Development] nickhaven:
Also double check your gapps and make sure they are the correct version and right is for the gapps. Try opengapps
[Fire Original Android Development] heavy2803:
Yes, gmail, calendar and keep works fine, except play music, i flashed the right gapps. The rest of the system also works really fine. Nice ROM.
[Fire Original Android Development] nickhaven:
I used the micro gapps from opengapps and then downloaded the play music app and it seems to work fin for me.
[Fire Original Android Development] DB126:
Same experience as [MENTION=1807032]nickhaven[/MENTION] except with nano gapps. Look back through recent posts as several users have weighed in. Don't forget to wipe those caches.
[Fire Original Android Development] f1ux:
Has anyone gotten an xbox one controller to work via usb OTG?

I have an OTG adapter and the controller but it doesn't get detected when I plug it in.

Also, has anyone found crossy road has an audio bug?
[Fire Original Android Development] nickhaven:
Idk about the Xbox controllers but the Asus Nexus controller works great via Bluetooth.

Also the audio bug is not specific to this ROM, it is a cm12.1 issue. Don't think it can be fixed in this version.
[Fire Original Android Development] xChr11s:
I'm actually at build version from 2015-12-16. Can I just download the new version from 2016-01-26 ,place it on sd-card abd update it via zip in recovery ?

Does anyone knows if it changes something so that I can get a problem with Steamguard Mobile authenticator ?

Ty
[Fire Original Android Development] atayal:
is there an easy way to move from slim rom 2.3 to cm 12.1?? I have flash fire. (ps: i am a noob)
[Fire Original Android Development] saman0suke1:
Hi, what do I need to do before trying to install it with FlashFire? I'm running 5.11. Thanks.
[Fire Original Android Development] sd_shadow:
root

---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------

wipe system, 3rd party apps, caches, install rom, supersu, gapps
[Fire Original Android Development] atayal:
will it work? i heard there were some problems with it, or nah?
[Fire Original Android Development] sd_shadow:
should be fine, but no guarantees
[Fire Original Android Development] heavy2803:
What means?

2016-01-26

- Updated CM Code

2016-01-20

- Updated CM Code

2016-01-12

- Updated CM Code

No spesific bug fixes?
[Fire Original Android Development] topcaser:
It means that nothing has changed specifically by ggow, but the code was adapted to the cm mainline. You can have a look there if you are interested in the changes. Or do you want that ggow spends even more time to copy that information to this thread only that you can get this information quickly? I would suggest that every time, ggow posts 'Updated CM Code' that you get the information for him to support him. Is this a good deal?

Sent from my Galaxy S5
[Fire Original Android Development] DB126:
How about you try searching first: http://xdaforums.com/showthread.php?p=65020240
[Fire Original Android Development] saman0suke1:
This worked great, thanks!!
[Fire Original Android Development] :
Well it depends if your lucky enough to flash the current build from fireos 5.1.1 with no problems. In my case like some others, fireflash fails to flash the latest build of cm and doesn't really flash nothing sometimes even the device get stuck on bootloop. Workaround is flashing build from dec302015 then dirty flashing the current build. Well that's my workaround and for some also has worked. If you need the previous build pm me and I'll be glad to help

---------- Post added at 01:49 PM ---------- Previous post was at 01:38 PM ----------

Just received my replacement today [MENTION=4267571]sd_shadow[/MENTION] after fighting with amzon for like 4 days about them loosing my tablet in the service center. But anyway I'm screwed because its been shipped with fireos 5.1.1. Now I have no choice to use flashfire. And I don't want to $hit my pants if my device hits a softbrick again upon flashing cm latest build. Lol
[Fire Original Android Development] jason2o9:
I have tried to install CM12 via flashfire on my 5.11 amazon fire, upon boot up it gets stuck on the CM12 logo until i power it off. Have restarted it multiple times, have tried to get into recovery but it will just stay on the Amazon logo and go no fruther, does not even show text like in the videos of how to get into recovery mode. Not really sure where to go from here and could use some help getting back to either factory or fix the current issue. Thanks in advance.
[Fire Original Android Development] sd_shadow:
if device has 5.1.1 bootloader and

if you cannot boot to recovery and rom will not boot.

likely can't be fixed with the tools available

only option maybe return to Amazon for a one time free replacement
[Fire Original Android Development] jason2o9:
but will they take it back when they see the CM logo lol?
[Fire Original Android Development] sd_shadow:
yes it's fine, Amazon will just reflash and sell it as a refurbished

---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------

It may be time for me to add that to the FAQs
[Fire Original Android Development] DB126:
Be sure to note it's a one time courtesy exchange only valid during the warranty period.
[Fire Original Android Development] jason2o9:
awesome, will give them a call.
[Fire Original Android Development] DB126:
When you get your new device be sure to check in for the latest news before attempting to reinstall a custom rom. Good chance the order of operations in FlashFire may have been your undoing. Wipe needs to be first and include the default partitions (system, apps, dalvik). Not definitive by any means but is one of the majors.
[Fire Original Android Development] jason2o9:
actually i had seen that and made sure that was set right before doing the CM12 and still did this, hopefully I will get a device that has 5.0.1 on it instead of 5.1.1.
[Fire Original Android Development] :
hmm my replacement got here yesterday and came with fireos 5.1.1 already preinstallled. when you select wipe first then the others like rom/supersu/gapps. you will notice that wipe is the last to flash even though you choosed wipe first, and to be safe keep it like that and DONT drag wipe to the top. or your end up with a brick and noway to get out. i think thats what you did? i did it and had no recovery to flash back to stock.

lesson learned

---------- Post added at 05:41 PM ---------- Previous post was at 05:30 PM ----------

i just did some cool stuff to fire. opened my fire hd 3gen took out speakers,battery,chip and wifi antenna and did soldering and modding since i work for phones and putting them together. i did some test with cm12.1 and dam i got a full day on battery even though battery is not currently correct due to incorrect hardwarer. i also made my tablet to use two speakers instead of one. now is more louder than even. only thing im going to look is unlocking the bootloader but i have to wait 2 weeks intill my freaky friend comes to get this stright since he worked for amzon. also wifi antenna didnt not read well so ended up taking it off even though i had a powerful signal but idk i got to get more into it.

yeah it kinds of looks ugly with the holes i did for speakers lol but thats alright.

cm.12 rocks
[Fire Original Android Development] DB126:
Perhaps I am misreading your guidance or have a seriously flawed understanding of how FlashFire works. Wipe needs to be the FIRST option (top of list) not the last. If wipe is positioned last it will effectively erase everything that was just installed if it includes the system partition which is the default.
[Fire Original Android Development] :
i guess you misread what i tried to say. i said when you select wipe first then rom/supersu/gapps before you flash you will see wipe for last. cm/supersu/gapps/wipe.....

even though choosing wipe first wipe will preform last.

well dragging wipe to first will erase stock recovery and end up bricking.

wipe is the last thing that should happen after flashing roms. so again when you select wipe first then rom and gapps you will see that wipe is at the button of the list not the top if you drag the wipe from buttom to perform first thats when the brick happens.

why? i did that and yes it erases the system and stock recovery
[Fire Original Android Development] sd_shadow:
you need to drag wipe to top of list
[Fire Original Android Development] :
no sorry i did that and had a brick.

im flashing from rom to rom how im stating and i have no issues

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------

this is how it suppose to be and works.

open fireflash and select wipe then rom/supersu/.gapps

now it should look like this before flashing

rom/supersu/gapps/wipe

if you drag wipe to be first you actually are wiping everything from system to stock recovery
[Fire Original Android Development] DB126:
[MENTION=7216923](composer)[/MENTION] - No one can speak to the particulars of your situation that ultimately resulted in a bricked device. However, the guidance you are giving is incorrect for the vast majority of use cases and could well result in an unbootable device.

It is possible there are scenarios where placing wipe first is not advantageous. But you should not be advising others on the placement of wipe based on your experience with one device.

The recommendations I offer regarding wipe are not my own. They come from senior members of the XDA community whose opinion I have come to respect. I have used FlashFire a few times but only to update CM, not install a custom ROM over FireOS. Perhaps there is a difference.

There is no option under wipe that specifically targets the recovery partition. Yet somehow it is getting damaged by FlashFire - but not consistently.

Probably it is best to sit back and digest input from other members of the community to see what has worked and what fails (including your experience).

---------- Post added at 09:41 PM ---------- Previous post was at 09:31 PM ----------

While this may have happened to you it is not conclusive. Please don't draw conclusions based on one bad experience with one device. Your guidance runs contrary to that of most other contributors in this forum.
[Fire Original Android Development] :
My respect to all dev including [MENTION=4267571]sd_shadow[/MENTION]

I'm not saying senior are wrong about the fact that wipe being first won't brick.

I've had bricks all over my devices putting wipe has first after being the last to flash.

1 devices? No, couple of devices haved and that was doing testing. And I'm not telling nobody to do what I do I'm just giving out how I survive doing what I do with all my devices. Thank you very much. Nobody needs to follow my instructions and i don't really care either. All I know all my devices including fire hd seems to survive my workaround. Your absolutely right [MENTION=5488402]Davey126[/MENTION] I should haved kept my workaround tobmy self lol and not share it even though it can help someone in the future.

I love this ROM that's all that matters. But explain to be why wipe sets itself automatically to last if I tab on it first then ROM and gapps? But still works for me. Now since wipe was set to perform last by default and when I dragged it to the top then why half of my devices went to bricks? And it doesnt brick while I leave it the way it sets to default which is last? Idk but its weird
[Fire Original Android Development] lebleu29:
Not sure what I did, but after the flashfire process, my fire seems to be stuck with the blue Cyanogen logo. I've left it for an hour, but it doesn't go away. Logo is not frozen - it continues to run animations. Help please!
[Fire Original Android Development] sd_shadow:
5.0.1 or 5.1.1 bootloader?
[Fire Original Android Development] lebleu29:
5.1.1
[Fire Original Android Development] sd_shadow:
try to boot in to recovery