yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] MERLev:
So, update about my random shutdowns

Last line in my logcat was

D/AMZ-hwcomposer( 135): [DPY] UEventThread::threadLoop recv change@/devices/virtual/thermal/thermal_zone7

Honestly, I don't know meaning of this, but I thought that it might be somewhat connected with tempreture sensor - thermal_zone7. So, today I leftmy tab running CIV2 revolution on debug, while monitoring temprature values every second using

shell cat sys/devices/virtual/thermal/thermal_zone7/temp

and storing it to file.

last entries :

44953
44961
44969
44969
44969
44974
44976
44976
44975
44984
44990
45003

This may be fully a coincidence, but last value i got was 45003, and it was the first value >=45000, so, may it be that device was turned off due to overheat based on this sensor's temprature value?
[Fire Original Android Development] julianpaul:
^^ just curious, what's your ambient room temperature?
[Fire Original Android Development] blueberry.sky:
Has anyone tried skype or similar video chat? I've read it has issues under Fire OS.
[Fire Original Android Development] shiz0id:
So I just dirty flashed the latest build and its stuck on the Cyanogen Boot screen, should I just wipe /system and /data and try again using a clean device?
[Fire Original Android Development] sandman512:
I assume that I can dirty flash the latest version?
[Fire Original Android Development] Pyrb:
Did you reflash SuperSU too? I had the same issue until I reflashed SuperSU.
[Fire Original Android Development] shiz0id:
I just wiped everything and reflashed everything, everything works fine now
[Fire Original Android Development] Orbiting234:
Really great work so far! Although things like YouTube and YouTube Gaming work great, I can't get the video in the Twitch app to work with this. :( I'll get some audio playing but the rest of the device is almost at a hard freeze while doing that (video portion of screen is blank and everything else is completely unresponsive, have to hit the power button to get out). Outside of that it is super stable!
[Fire Original Android Development] mreckhof:
OMX solution

For the OMX issue, copy the libMtkOmx* libs over to /system/etc. I took mine from here just to test and seems fine.

Github/luckasfb/vendor_wiko_s8073-1/tree/master/proprietary/lib

Prob best to get them from the original ROM I suspect.

Didn't test a lot. One google play movie that was hanging badly is smooth now and a couple games.
[Fire Original Android Development] blueberry.sky:
Could you try taking a picture? See if it still fails to work. I see OMX can be involved in image capture (camera) and display.
[Fire Original Android Development] mreckhof:
Doesn't appear to be, however may just be more libs I didn't move.
[Fire Original Android Development] BlueFlame4:
I've seen the camera behaviour on other devices (preview works, taking picture freezes) and it was often related to KSM being enabled. Did you enable KSM in the kernel?

PS: I neither own the device nor do I have time to investigate but you might give this a try.
[Fire Original Android Development] csolanol:
We are stuck on stock kernel and boot image due to locked bootloader.

Enviado desde mi Nexus 5 mediante Tapatalk
[Fire Original Android Development] BlueFlame4:
I see. Perhaps it can be disabled at runtime though.
[Fire Original Android Development] sandman512:
Quick question, if flash the latest version, will I loose my current set up? Thanks.

PS: Happy Thanksgiving to all!
[Fire Original Android Development] ggow:
- No you won't lose your current setup

- Remember to flash SuperSU.zip after flashing the new ROM
[Fire Original Android Development] sandman512:
I got into recovery, installed latest Cm file and SU at the same time, rebooting now.

Thanks.
[Fire Original Android Development] MAGICMAN516:
Just ordered mine for $34.99. Can't wait to give it a go.
[Fire Original Android Development] theechap:
Pardon my ignorance but isn't that the situation we're in now? And yet we have CM12.1. So wouldn't it be possible to create a CM13 version once Amazon upgrades to FireOS 6 and someone hacks it? Isn't that what happened for CM12.1?
[Fire Original Android Development] DB126:
Yes. Doesn't require a 'hack' as FireOS is based on Android which open source. Amazon is required to make the code available (which they do). Often developers can proceeded with custom roms even without the source once root has been secured along with a method for updating the system partition (eg: TWRP or FlashFire). That said, it is unlikely FireOS v6 will be available anytime soon; if/when it does materialize no guarantee it will be rootable and/or available for 5th Gen devices.
[Fire Original Android Development] AwlsomeAlex:
FlashFire Workaround

I mean, FlashFire was created to bypass both the Bootloader and the Kernel (Current Method for 5.1.1) I was just wondering if a project was started.
[Fire Original Android Development] sd_shadow:
no, neither the bootloader nor kernel are bypassed to boot cm12.1 on ford
[Fire Original Android Development] AwlsomeAlex:
GApps didn't flash with CM 12.1!!! Halp!

I Installed CM 12.1 Successfully (But FlashFire Warned me of Problems) but GApps wasn't flashed along with CM 12.1. Any Idea on how to install it or flash it without having to do the whole process again? :confused:
[Fire Original Android Development] DB126:
Not really. All roms for the 2015 Fire are dependent on the stock kernel which can not be modified.

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

- pick a different GAaps package (read through thread for choices)

- pick a different ROM as GAaps flash issues seem more prevalent with CM - especially when using FlashFire and recent Open GAaps builds.
[Fire Original Android Development] atayal:
can i use flashfire to upgrade from slimrom 2.3?
[Fire Original Android Development] marrco:
i received a new fire today (5.1.1). Activated ADB, rooted and installed cm-12.1-20160229-UNOFFICIAL-ford and open_gapps-arm-5.1-pico-20160310 without any issue.

Instructions on the first page are wrong for this specific version, when installing open_gapps-arm-5.1-pico-20160310 you have to leave default enabled system writable (i don't remember the exact option name).
[Fire Original Android Development] ajislav:
Got 2 Fires the other day, both with 5.0.1. Guess I am lucky. Running smooth with latest 20160229 and opengapps nano installed using TWRP. Thank you ggow!
[Fire Original Android Development] AwlsomeAlex:
I actually Installed FlashFire on the CM 12.1 Modified Fire Tablet and Reflashed GApps and kept that System Write Enabled, it took me about 2 minutes (When it failed it took 15 seconds) and Wiped Dalvik/Cache Partitions. It gave me problems with connecting to the servers at first, but I did another wipe and it fixed the problem. I didn't even think you could install FlashFire on CM 12.1 :victory: Makes it easier to upgrade!

---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------

I Don't see why not. :) Try looking at RootJunkys guide to do it. (On YouTube or www.rootjunkysdl.com)
[Fire Original Android Development] atsiz77:
I have installed for testing CM, and installed as Gapps ARM 5.1 Micro. However, Google Aps are not at all appear, I need something to activate so that they appear to me?
[Fire Original Android Development] booogermonkey:
Just wanted to say thanks to the dev for this. everything installed well using open GApps 5.1 nano using flashfire. Beer coming your way on payday[emoji6]
[Fire Original Android Development] atayal:
SuperSu is not updating

https://imgur.com/hvLRoby

SuperSu isn't updating for me, any fix? (I used flashfire to update)
[Fire Original Android Development] wulfie66:
you don't need supersu, root is built into this rom, just enable developer options and enable root from there ;)
[Fire Original Android Development] DB126:
Some find SuperSU preferable as a root manager. It can be reliably flashed it via TWRP (@atayal's devices). No doubt a remedy could be found for FlashFire but why climb the mountain when you can walk the valley.
[Fire Original Android Development] booogermonkey:
If ya got twrp I don't see why you couldn't flash su. I like it better too. Never used flashfire until now, but if I had a custom recovery I'd try it. Not telling you to tho lol but we got root and that's what counts[emoji110]
[Fire Original Android Development] atayal:
Downloading app bugs!

I don't know what the problem is, but the play store keeps failing to install apps. Error codes that I have gotten: 963, 924.

I have cleared data and resolved the problem for the first app i download, but the second app i try to install fails... any fixes?
[Fire Original Android Development] DB126:
Don't quote OP when posting a question (2nd request)
[Fire Original Android Development] atayal:
sorry, i am new to xda, i dont know which one does which. Please forgive me
[Fire Original Android Development] yochananmarqos:
What Gapps package did you flash?
[Fire Original Android Development] ipdev:
Try ejecting / unmount sd card. As stupid as is sounds, I got passed a lot of play store download / installing errors that way. (Something about available mounted storage.) Obviously you need room on your internal storage, but it seems you can move it to sd, once you remount your sd card, without a problem. (Most of the time. ?)
[Fire Original Android Development] ldeveraux:
It's extremely irresponsible to suggest that a user not install a root manager. Any dev ever will tell you to install one, so rogue apps can't take control of your system without permission. ALWAYS install a root manager!

EDIT: Unless you meant that because SuperSU is baked into this ROM, you don't need to install it additionally. Is it baked into this ROM?
[Fire Original Android Development] ggow:
New Build is Up

- Dated 11 March 2016

- Change log on Post #2

- Updated CM Code

- 01 March 2016 AOSP Security Patch Level

- Updated FlashFire Flashing instructions on OP
[Fire Original Android Development] wulfie66:
new builds are always nice :D

OP needs instructions on updating via TWRP as well ;)
[Fire Original Android Development] drkbg:
Which Open GApps are working?

Maybe it's a goo idea to put that on OP...
[Fire Original Android Development] ggow:
I'm still using open_gapps-arm-5.1-nano-20151219.zip on this ROM, it's old but it works. I tried later ones but they didn't work correctly.

As for the OP, I have lost track of what I have tried. If someone offers up a later package name that works I'll add it.
[Fire Original Android Development] marrco:
Issue with gapps was not mounting for write system. Just follow the updated instructions in the first post. You can use opengapps. Today build is fine. I just update my tablet with FF so if you follow exactly the instructions you should be fine.

I'm using cm-12.1-20160311-UNOFFICIAL-ford and open_gapps-arm-5.1-pico-20160311
[Fire Original Android Development] DB126:
CM manages root access via the integrated Privacy Manager in the absence of a 3rd party tool like SuperSU. Do your homework before spouting off.
[Fire Original Android Development] ldeveraux:
I don't think warning someone of the risks was "spouting off". That's why I edited my comment. Sorry I offended you?
[Fire Original Android Development] DB126:
Success with newer versions remains inconsistent. I have not experienced difficulty with the latest builds (March 2016) installed via TWRP or FlashFire (options set as noted). Others struggle with FlashFire but it's not entirely clear how much is due to user error. Seen many posts indicating instructions were followed precisely only to be followed up with a revelation. That said, I do feel something has changed with newer builds that causes difficulty with FlashFire.

I would not change your guidance as older builds will quickly auto-update to the most recent versions via background process.
[Fire Original Android Development] drkbg:
Are this the right settings? because I am not getting google play icon in the menu with these...

[IMG="ff"]http://s11.postimg.org/wnxt0bdtf/Screenshot_2016_03_11_14_31_03.png[/IMG]

Also is this warning a problem?
[Fire Original Android Development] DB126:
This is no risk with CM and your edit demonstrated lack of knowledge in the subject matter. Your post suggested that I and another poster were "extremely irresponsible". So yea - I took offense.
[Fire Original Android Development] ldeveraux:
I said that not having a way to manage root access is irresponsible. Again, I didn't know what CM already has for this, which is why I made my edit. If I was wrong, then I was wrong. I'm not calling you out personally, so you can knock off the butthurt. :good:
[Fire Original Android Development] DB126:
Whatever. Standby comment about doing homework. Moving on...
[Fire Original Android Development] ldeveraux:
So on I move.

This isn't necessarily a Fire CM12 question, but what does the privacy manager entail? I don't think I've ever flashed CM without also SuperSU, what's the difference? Why wouldn't SuperSU be baked in, does Chainfire have to bless it or something?
[Fire Original Android Development] DB126:
Privacy Manager oversees both root access and app permissions. Sort of a hybrid between SuperSU and App Ops with some level of automation. It's baked into the rom and enabled by default. Believe it was developed by cyanogenmod (not sure) and seems to be a signature feature of CM. I prefer SuperSU - but that's a personal choice.
[Fire Original Android Development] booogermonkey:
I think a lot of us do, and like I said earlier if I could install a custom recovery bet that I would try (for better or worse) to flash SuperSU. Cm root manager is working well tho, and I'm not about to complain about it.
[Fire Original Android Development] drkbg:
Figured the problem myself. Those are the right settings + files need to be on the internal storage. For some reason FlashFire doesn't mount SD card when started from CM. (It worked when started from stock ROM)
[Fire Original Android Development] sandman512:
Quick question, would someone mind uploading the latest Flashfire as I cannot download at work. Thanks.
[Fire Original Android Development] AwlsomeAlex:
Error 963 on Google Play Store with SDHC

When I use a 8GB Fujifilm MicroSDHC (Class 4) applications that I want to install keep giving me the 963 Error. I tried clearing the data and cache from Google Play Store and wiped Dalvik/Cache Parititions, but the only solution was to remove the SD Card. Im using the current version of CM 12.1 and the March 11th build of GApps Pico.
[Fire Original Android Development] qtotter:
If you're tired of laggy Fire, try Trimmer from the Play Store. This app speeds it up drastically.

https://play.google.com/store/apps/details?id=com.fifthelement.trimmer
[Fire Original Android Development] DB126:
Lost track of who said what to whom. Know that SuperSU can be installed via FlashFire. Some have problems getting it to initialize; most have no problem.

---------- Post added at 06:06 AM ---------- Previous post was at 05:58 AM ----------

https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx

---------- Post added at 06:13 AM ---------- Previous post was at 06:06 AM ----------

The presence of a mounted SD card is known to trigger this error with Lollipop based ROMs and newer versions of Play Services/Store. If possible try a different card, preferably faster as class 4 is pretty slow by today's standards (although I don't feel that in itself is causing the problem).
[Fire Original Android Development] KLit75:
Anyone tried Deep Darkness theme with this rom? It's a little heavy so thought I'd inquire before purchasing. Thanks
[Fire Original Android Development] yochananmarqos:
Any CM theme should work. Try it out and hit the Refund button if you don't like it.
[Fire Original Android Development] KLit75:
Not this one. Killed my system UI and I couldn't do anything at all. The upside is I just booted to safe mode and was able to change the theme back. Not that it matters now but Deep Darkness is actually free so I didn't need to seek a refund. I've heard really good things but also recall some people having issues with it on other devices.
[Fire Original Android Development] AwlsomeAlex:
Okay, thanks. I might have a Samsung Class 10 32GB lying around somewhere.
[Fire Original Android Development] M.Ray:
I had this problem too. Last good working gapps are 2016 01 20, I used the nano package:

https://github.com/opengapps/arm/releases/download/20160120/open_gapps-arm-5.1-nano-20160120.zip

It's playstore version 6.05. Anything newer, e.g. playstore 6.1.12 from later releases, produces the 963 error at certain apps.
[Fire Original Android Development] AwlsomeAlex:
Thanks, been getting a new one lately, Error 505. Stupid pain in the rear end GApps. :good:

But the temp fix is removing an SD, hopefully this will work better. (I'm getting one for myself today, and have been modifying my friends, because everyone has one thanks to this, and i'm the only one who knows to do it. :rolleyes: But maybe an update script will arise to enable OTA for this Unofficial build, but who knows. :confused:
[Fire Original Android Development] M.Ray:
For Error 505 (google calendar and goolge games) you just need to install an older apk from apkmirror (take one from december 2015) and update them (also see FAQ).
[Fire Original Android Development] AwlsomeAlex:
An older Play games or Store?
[Fire Original Android Development] Dread This Day:
Updating to latest build has left me with a brick, as it erased the stock recovery. Updated with Flashfire as normal, then got cyanogenmod logo boot loop. With only fast boot and no adb side load, it is now a paper weight.
[Fire Original Android Development] KLit75:
games. I just tried this one &it installed fine

http://www.apkmirror.com/apk/google-inc/google-play-games/google-play-games-3-5-17-release/google-play-games-android-tv-3-5-17-2463965-836-android-apk-download/
[Fire Original Android Development] yochananmarqos:
Flashing any ROM does not modify recovery. I believe you can restore the stock Amazon ROM via fastboot. There is a guide somewhere around here.
[Fire Original Android Development] sd_shadow:
fastboot only works with 5.0.1 or 5.0.0

---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------

there are several threads about that too
[Fire Original Android Development] Dread This Day:
No, you cannot. Only through ADB through recovery. Fastboot, unfortunately, offers no fix. If you read through some other threads, mainly the custom recovery threads, this appears to be a common issue with CM. The difference with mine, though, is that I was simply dirty flashing the newest build, there should have been no issue, but there was. Only fix is a replacement, as of yet.
[Fire Original Android Development] DB126:
[MENTION=5124760]yochananmarqos[/MENTION] - Installing/updating CM via FlashFire can disable access to the recovery partition with no known remedy. This seems most prevalent with versions of FF below v0.26. System restoration is not possible via fastboot due to restrictions imposed by Amazon.

[MENTION=384587]"Dread This Day"[/MENTION] - what version of FlashFire? Any wipes involved and if so where were they positioned (eg: above/below rom operation)?

---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------

Play games. Don't think it needs to be an older version. Just sideload the latest from apkmirror or another trusted source.
[Fire Original Android Development] Dread This Day:
[MENTION=5749760]ggow[/MENTION] [MENTION=4267571]sd_shadow[/MENTION] any ideas why this would happen on a plain old dirty flash? I fid use the newest Flashfire. There was no wipe action at all, so it isn't as if I flashed it and then wiped it, I do remember Flashfire saying something about not being able to unmount /system.
[Fire Original Android Development] sd_shadow:
also were files (rom/gapps..) on internal storage or external SD card?
[Fire Original Android Development] booogermonkey:
Well, good news is its a LOT cheaper than bricking a phone[emoji23]
[Fire Original Android Development] case-sensitive:
power menu?

First, thanks for putting this ROM together! I've been running it since Dec and it's been great.

I just updated to the March 11 built. Everything works great, except possibly for one small item: When I long-press the power button I got the "power off/reboot/airplane mode" menu, and then when I click reboot, all I have is "Reboot Your tablet will be reboot". I *think* in an early version of the rom, under reboot I have to option to reboot/reboot into bootloader/reboot into recovery. Is it possible to bring this to the current ROM? (and apologies if I mix up your ROM with others).

MANY THANKS!
[Fire Original Android Development] Doggy77:
If you go to the "developer options" (to get this menu go to "Settings => About tablet" and multitap on "Build number". After the Developer mode is unlocked go back to settings), you may find the "Advanced reboot".

Best regards,

Markus "Doggy77" Seifert
[Fire Original Android Development] forenmoderator:
I wasn't able to update from the 2016-02-03 build either. So I tried it your way and.... it worked!

Started FlashFire, first step wipe all data, second step flash Nexus Rom, third step wipe all data, fourth step Flash new unofficial CM build, fifth step Flash opengapps and last but not least wipe again. No Problems anymore. I am just hoping, that I don't have to "update" like this with the new builds.

Ah, and a big thank you to ggow for all your work. I am really impressed!!!:good:
[Fire Original Android Development] Dread This Day:
I'd tread lightly using Flashfire for CM. See above posts, it just bricked mine. Especially if you bought it more than 30 days ago. I strongly suggest flashing the hard way, if you're on 5.0.1 that is, use fast boot to boot CWM or TWRP. If you're on 5.1.1, like I was, be careful because as stated above Flashfire and CM are known to erase the stock recovery, which means if your flash doesn't take, you've got a paperweight with NO WAY yet to fix it. When I get my replacement, if it comes with 5.1.1, I will not flash this ROM again until that gets figured out.
[Fire Original Android Development] marrco:
I have 5.1.1 and used FF 0.27 without issues last week first to install and then to update, using latest pico opengapps. So there's something different in what we did. Do you have and external sd card? Did you install xposed? How did you root it first?

btw, there's a new FlashFire v0.28 version:

Changelogs - FlashFire

- N preview compatibility (requires SuperSU v2.70)

- Properly copy selinux contexts

- Updated embedded SuperSU version to v2.70﻿
[Fire Original Android Development] abacabie:
Mine also bricked on 5.1.1 when flashing CM 12.1 from stock Amazon (rooted) with flashfire, its happened to a few others as well so be careful, just because you had one successful flash doesn't mean you wont hit issues another time , i would advise cation if you're stuck with 5.1.1 as once you loose recovery there is no way to recover.

I was able to get my tablet replaced as we have a 12 month warranty in UK and immediately flashed CM 12.1 back , its a brilliant build and expertly put together by a very talented person.
[Fire Original Android Development] sd_shadow:
When you send it back to Amazon, did it have the cm boot logo, or just amazon?
[Fire Original Android Development] Dread This Day:
Mine has the CM logo, but I drained the battery. Lol. I really don't think they care, they didn't say they were going to inspect it or anything. I was just told that as soon as they received the "broken" one they'd two-day ship my replacement. I'm confident it won't be an issue. As far as I know, there's no way with it being bricked, to get rid of that boit logo anyway.

And to be clear for others discussing it, I had an external SD in, but the file to be flashed was from internal, I was on the build before the newest, dirty flashing to the newest. Flashfire gave an error about not being able to unmount /system because it didn't exist, rebooted, and stuck at the CM logo. Yes, Flashfire works, but for how many times? I had had issues with it already, and had to side load the FireOS, and reflash CM 12.1, then al l was good again, until this.