yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
I use this rom/device daily and have not experienced this problem. On occasion the device will refuse to connect to any Wifi network after waking necessitating a reboot to correct (also a problem on other Amazon Fire devices including 2nd gen HD & 3rd gen HDX). I have also seen WiFi misbehave under heavy sustained load (eg: high resolution streaming from a distant AP) suggesting a temporary thermal issue with the SOC.

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

First issue can be fixed using Link2SD (or a similar app) that supports symbolic linking. See product FAQ for background: http://www.link2sd.info/faq

Lollipop (AOSP) does not natively support persistent unmount options although some ROMs offer this either as a storage option or notification. As observed CM does not appear to have either.
[Fire Original Android Development] KhuynhThanh:
Can u build ANDROID N for amazon fire 5th gen? Plz?
[Fire Original Android Development] sd_shadow:
no, there will be no M nor N

bootloader is locked, kernel doesn't support those Android versions
[Fire Original Android Development] Vlasp:
There could possibly be Android M or N for the devices that are able to boot unsigned images through the bootloader (Devices that did not have 5.1.x before they rooted) but that would require them to boot the kernel from recovery every time they shut down\restarted the device.
[Fire Original Android Development] DB126:
Small community; requires a dev willing to make investment.
[Fire Original Android Development] ggow:
- My laptop will be back from RMA this week, so should be up and running by the end of next week

- New build of CM-12.1 should follow shortly after that.
[Fire Original Android Development] cheezweasel:
I know this information is buried in this crazy long thread. I read many pages and some of the information seems contradictory to me. I am getting my Fire tablet tomorrow morning in the mail. Straight out of the box, what do i need to do? Install flashfire .27? Do I need SuperSU? I thought i read a post that says I don't, but the instructions say i do. I tried searching the thread for these answers, but, again, so many results and some that conflict with each other. The way i understand it:

1) Open the box and turn on the Fire (Is this when I smash the developer button for a while? - or is that for people who already have a version installed?)

2) Install Flashfire - which version?

3) Maybe install SuperSU?

4) Copy CM12 and GApps to phone storage

5) Use Flashfire to flash CM12 and GApps

6) And I guess SD Cards are giving people problems?

is that close?

Any help is appreciated
[Fire Original Android Development] marrco:
1: ok, but don't turn on wifi, and first check your version. If you're lucky and have 5.0x go back to post one

2: latest

3: no need

4: yes, use minimal gapps or add a gapps-config.txt setup file

5: ok

6: a fast ssd (class 10 - u1 or better) should be fine. But i'd suggest to install it later.
[Fire Original Android Development] KhuynhThanh:
Can u add "multi window" for this rom?
[Fire Original Android Development] cheezweasel:
Thanks for the reply! I have, obviously, never done this before, so I want ot make sure I get this right (although im not too worried about bricking a 50 dollar tablet - I bought it specifically so I could try this)

So far so good. Turn on the tablet, do NOT turn on Wifi, check the version. If its 5.0.x, then proceed with the instructions.

OK, install latest version of flashfire. How do I do this with no wifi? Or can i turn the wifi back on if i check the option to disable OTA updates?

Got it, no need to install SuperSU

I have downloaded PICO. All I want is GooglePlay store. I am using this thing only to stream Pandora/Netflix/web video via Chromecast/bluetooth. This should work, right?

Easy enough, follow the instrcutions to flash the two zips I have. (CM12 and Gapps Pico)

When you say "install", do you mean there is something extra i have to do to get Sd card to work? Or do you mean "install" in the sense that i just put the formatted card in the reader and let android pick it up on its own?

Thanks again, I really appreciate it. This kind of thing doesnt make me nervous or anything, I just want to make sure I get the steps right before I do it so I have an idea once I start instead of having to constantly check boards and videos during the process.
[Fire Original Android Development] Doggy77:
Attach it using the USB cable. Download it from chainfire directly.

The installation (insertion)= of the SD-Card is optional and not needed.

If you want to use "App2SD" (native from Android) there may be flaws by disappearing Apps. (See thread). If you just want to store files (MP3, PDF,...) on the SD just insert it. But the tablet also works well without SD-Card.

Kind regards,

Doggy77
[Fire Original Android Development] DB126:
Reasonable responses provided end game is not a custom ROM. Recommend FlashFire 0.32 (for now) as later versions remain experimental. Avoid versions below 0.31.

If CM 12.1 (or another custom ROM) is the end game:

- historically FlashFire and Kingroot do not play nice together; so you'll probably need to revert to SuperSU after rooting. Which rereading the guidance is not mentioned anywhere. Use the SuperTool. Which also leads to complications if your device arrives with any version of FireOS > 5.1.2. In which case you''ll want to consult this thread.

- as noted by [MENTION=5722672]Doggy77[/MENTION] forget the SD card for now. Once you have a stable config you can decide if/how you want to store apps and data. Recommend Link2SD over other solutions which tend to have side effects (eg: disappearing icons).

- keep reading to gain a better understanding of what you are getting into and how to navigate choppy seas you will invariably encounter on the journey. An excellent resource is the index page located here.
[Fire Original Android Development] yochananmarqos:
If you have 5.0x, then look at the first post, you don't need Flashfire.
[Fire Original Android Development] cheezweasel:
[MENTION=5124760]yochananmarqos[/MENTION], [MENTION=5488402]Davey126[/MENTION], [MENTION=5722672]Doggy77[/MENTION], [MENTION=6000946]marrco[/MENTION]

Thank you everyone so far for your help. This really is a great community.

So, thanks to PrimeNow, I was able to order my Fire last night around midnight. It came this morning at 8AM. I have it sitting on my coffee table right now charging up.

I checked the version and it is 5.0.1. That means I guess ill be using the TWRP method from post#1, which I read is preferred anyway. So no need for FlashFire I guess.

Anything I should be aware of that could make life a bit easier? It seems pretty straight forward from the videos and instructions.
[Fire Original Android Development] marrco:
Ok, you've been lucky. Now you just need to boot twrp. Then backup your partitions and install CM. You can install you sd card now.

you can use supertool to boor from twrp recovery or better you can learn how to do that in a command prompt.

1) install adb and drivers. Open a command prompt in that folder

2) connect the fire via usb to your pc

2) turn on adb debugging (in developer options, you need to tap setting/about/build number 7 times)

3) type adb devices. It should list your device.

4) type adb reboot bootloader and your fire will reboot in bootloader mode

5) type fastboot boot TWRP_Fire_2.8.7.0.img

6) wait a minute, twrp boot is slow.

Just for *first* CM install i suggest to wipe system and data. than install CM+pico gapps, then wipe cache and dalvik and reboot.

To enable root after you install CM you have to enable developer options again.

supertool can be downloaded from http://www.rootjunky.com/amazon-fire-5th-gen-supertool/ and you can just unzip it and use the drivers and files from it. Your goal is just to boot TWRP and then completely remove the fire os and install CM. There is almost no risk bricking the fire if you have (and keep) bootloader version 5.01.
[Fire Original Android Development] cheezweasel:
Why do you suggest this? Im not second guessing you - Im really interested in learning.
[Fire Original Android Development] marrco:
That's what i learned a few years ago. When switching to a different rom always clean start doing a complete system and data wipe. I don't know if that still holds true today or if it ever was. But that never failed on me. And with Amazon Fire we want to be extra sure not to leave any service running that can update bootloader.

You can do that because you're booting from TWRP so you should be safe from bricking your device if flashing fails. I forgot one last suggestion: it's always better to have your device at least 50% charged before flashing it.

And if you have a few dollars to spare buy a USB OTG (i bough one for 0.15 usd, shipping included) so you can even use a usb drive with TWRP and a cheap cover to protect it (a decent fake leather folding cover can cost less than 4 usd). Than you have a fully featured 7" tablet running android for less than fiftyfive bucks.
[Fire Original Android Development] marrco:
Thanks for the excellent guide. It should be added to the first post.

I'd say there's no need to flash SuperSU. ROOT is already included in CM 12.1 just get again to developer options and enable it. But i know some people prefer to use SuperSU.
[Fire Original Android Development] ginbo27:
after installation there were not any google app. i try to install manually goggle play store and services but doesn't work. any one have same problem?
[Fire Original Android Development] ajislav:
Did you flash gapps?

Which version?

Try it again with pico or nano..
[Fire Original Android Development] ginbo27:
-yes

-i try with nano but nothing.

-how can i do for flash it now after cm is installed?

---------- Post added at 09:06 AM ---------- Previous post was at 08:46 AM ----------

how can i do for install it again? i try with flashfire just installing gapps but my sistem was rebooted and now i have to install all apps again
[Fire Original Android Development] Cameron W.:
i love this rom but i've ran into a problem. i connected a usb drive with my otg cable and downloaded a file to it and now when i connect the usb and then unconnect it several apps icons go grey and i can't use them untill i reboot or reconnect the usb. not sure why this is happening. any one know?
[Fire Original Android Development] kramalot:
Are the affected apps ones that you have moved to SD card? I've always suffered the problem when unmounting any otg storage (that all apps moved to SD become unavailable). I can also restore them by removing and reinserting the SD Card.
[Fire Original Android Development] chuckconnors:
This ROM is awesome on the Fire tablet. Unfortunately I'm having a problem with getting voice-to-text/voice typing working. I do not see the microphone on the keyboard and it seems stripped from the settings.

I flashed the nano gapps package. Was the voice typing feature stripped to save on size? Is there a way to download an apk or something that will enable this? Can/should I flash a different gapps to enable voice typing? The tablet is used by my daughter who is too young to spell most things correctly but is successful in using the voice typing function. Any help is most appreciated.
[Fire Original Android Development] m00head:
You need the 'Google voice typing' option under 'Settings->Language & input->Keyboards & input methods'.

To get that particular option to appear, try installing the Google app:

https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox

If that doesn't work, then try installing the Google Keyboard app:

https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
[Fire Original Android Development] Cameron W.:
yes, the apps are mounted to the sd card. Nothing you can really do to fix it. Thanks though, at least now i know why.
[Fire Original Android Development] kramalot:
I'M NOT ALONE! Whenever I've mentioned this in the past it's seemed as though nobody else suffered from it.

It seems that when I unmount otg the system thinks that sd card is also unmounted (this also happens on my kitkat Hudl 2 as well).

As you say, we just have to live with it.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 28 May 2016

- May 2016 AOSP Security Patch Level

- Fixed bug: No way back from USB Charge Only Mode
[Fire Original Android Development] ldeveraux:
this is super speedy, what a difference a month makes!
[Fire Original Android Development] Weicheng_Gao:
If you were in USB Charge Only Mode, try the following command in terminal in Fire.

setprop persist.sys.usb.config ptp

It works on version 20160420.

I thought it is my own problem until today.
[Fire Original Android Development] DB126:
Running this rom for 6 months including incremental updates; never experienced a speed degradation that wasn't of my own doing.
[Fire Original Android Development] ldeveraux:
Yeah, but you have an opinion on everything, which is why I didn't see your comment initially. and back to it...
[Fire Original Android Development] DB126:
I see. Fact remains as stated; core rom is fast and stable. Sorry your experience wasn't as favorable.
[Fire Original Android Development] :
Is there also a recovery image available for this version? I'm asking because I see on download cyanogenmod org that there are two columns - one for downloading the build, and another for downloading a recovery image for the same version.
[Fire Original Android Development] DB126:
Recovery images are not applicable to this device as the bootloader remains locked and stock recovery does not support .img sideloads.
[Fire Original Android Development] inscythe:
Thanks for the update!

However, I had the screen rotate bug back again when setting it to sleep. Is it just me or anyone else having the same problem?
[Fire Original Android Development] ggow:
I'll take a look. Maybe my repo got messed up. If so it will be put right in the next release.
[Fire Original Android Development] DB126:
Can you elaborate? Looked back through your previous posts but didn't immediately find the issue. Sorry if I overlooked the obvious ...
[Fire Original Android Development] inscythe:
Thanks!

I wasn't referring to any of my previous post. This old bug is supposedly fixed months ago, but it is now back (at least in my case). Probably related to [MENTION=5749760]ggow[/MENTION] having to set up a new repo in his new computer.

If yours is updated to the latest, can you try turning it to sleep and check whether the screen flips to landscape briefly before the screen turns off?
[Fire Original Android Development] danweb66:
In developers options ckick on disable hw overlays, and click on use awesome player. This will solve your video problems.
[Fire Original Android Development] thechosenone43:
I know mate.. Just don't remember exactly. Don't wanna be rude but you got any solution or advice?
[Fire Original Android Development] k4y0z:
Well it looked like you where missing the extension, hence you got the error " Cannot find the Image!".

Try using the full path to the file
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], Figured it out, for some strange reason, the TWRP file was missing off the SD card. As soon as I put it on, no issues. Thanks!
[Fire Original Android Development] thechosenone43:
Im gonna give it a try tomorrow. Let you know. Thanks for advice.

Any others suffering of this problem?
[Fire Original Android Development] k4y0z:
[MENTION=5749760]ggow[/MENTION] Where you able to successfully build the kernel from the sources?

I know we can't use it at the moment, but I'm not even able to build one without errors
[Fire Original Android Development] ggow:
- You're right the kernel source Amazon provided has build errors so by my reckoning can't be representative of the released binary.

- I haven't tried to resolve these at the moment because we would need to use tethered boot even if it worked.
[Fire Original Android Development] thechosenone43:
Same for me ? Odd but true. The TWRP file was not on the device anymore. After that I could boot in Recovery ?

Unfortunately I tried to dirty flash to upgrade but endet in Bootloop.

So i have to clean flash again. How is the experience for others with dirty flash?
[Fire Original Android Development] sandman512:
Chosen,

All I did was copy the TWRP file to the SD card and rebooted(via ADB), then dirty flashed. All good.
[Fire Original Android Development] thechosenone43:
... flashed the ROM, then Gapps then cleaned Cache and Dalvic and rebooted.. Endet Bootloop ?
[Fire Original Android Development] ggow:
- Updated feature table on OP
[Fire Original Android Development] AdamHayton:
Awesome ROM, didn't use the stock ROM at all. Some fonts look a little odd on this, however I guess it is down to the SD display?
[Fire Original Android Development] ggow:
- Yes the display resolution is very low for the size which is why everything looks a little pixelated.
[Fire Original Android Development] CharleySimmons:
I'm unable to get google launcher to work. It installs, but when selecting a launcher - it does not display as an option. Other launchers such as Nova, seem to work. Any suggestions?
[Fire Original Android Development] k4y0z:
I figured as much.

I was able to get rid of the compile-time errors, but am stuck at linking now:

LINK vmlinux
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 9 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
sound/built-in.o: In function `snd_pcm_post_start':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:891: undefined reference to `snd_timer_notify'
sound/built-in.o: In function `snd_pcm_post_resume':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:1199: undefined reference to `snd_timer_notify'
sound/built-in.o: In function `snd_pcm_post_stop':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:940: undefined reference to `snd_timer_notify'
sound/built-in.o: In function `snd_pcm_post_suspend':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:1092: undefined reference to `snd_timer_notify'
sound/built-in.o: In function `snd_pcm_post_pause':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:1035: undefined reference to `snd_timer_notify'
sound/built-in.o:/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_native.c:1043: more undefined references to `snd_timer_notify' follow
sound/built-in.o: In function `snd_pcm_period_elapsed':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_lib.c:1859: undefined reference to `snd_timer_interrupt'
sound/built-in.o: In function `snd_pcm_timer_init':
/mnt/mnt/cyanogen/kernel/amazon/ford/sound/core/pcm_timer.c:119: undefined reference to `snd_timer_new'
/mnt/mnt/cyanogen/kernel/amazon/ford/Makefile:807: recipe for target 'vmlinux' failed
make[2]: *** [vmlinux] Error 1
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/mnt/mnt/cyanogen/kernel/amazon/ford'
build/core/tasks/kernel.mk:233: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2

#### make failed to build some targets (14:56 (mm:ss)) ####

I was hoping we'd be able to build modules for the Amazon-kernel (maybe even kexec?!)
[Fire Original Android Development] ggow:
- You can build kernel modules without building the kernel

- I built one a while back for the Kindle HDX

- If I could remember the guide I followed I would post it

- But I remember there been plenty of guides and information available :)
[Fire Original Android Development] ggow:
- Not sure, I don't use Google Launcher as I like to use theming which CM's Trebuchet Launcher supports.
[Fire Original Android Development] AdamHayton:
Google launcher is working for me, I installed google now first if that is any help.
[Fire Original Android Development] CharleySimmons:
Flashed the mini gapps that contained Google Now Launcher, which seemed to resolve it. Now, google games won't install (error code 505). It's included in full and stock gapps, but those won't install due to space requirements.

---------- Post added at 04:18 PM ---------- Previous post was at 04:08 PM ----------

Seems to be an issue with the play store version of games.

I downloaded the apk from apkmirror and manually installed it - this worked without issue.
[Fire Original Android Development] mreckhof:
I see you have OTG still with ?.

It works fine. I'm typing this from a keyboard with mouse working via a hub to OTG adapter.

If you mknod a few SCSI drvices (I did /dev/sda b 8 0 and /dev/sda1 b 8 1), you can mount up a USB stick fine as well.
[Fire Original Android Development] ggow:
I can confirm it was an issue in my framework/base repo. Problem fixed will push another release at a suitable time.
[Fire Original Android Development] ggow:
FlashFire Support

- What's the general consensus on FlashFire Support?

- Would it make Flashing easier if I were to build open gapps nano into the ROM?
[Fire Original Android Development] GartimusPrime:
I have yet to have any trouble flashing anything in flash fire. Works great for me
[Fire Original Android Development] GhostRider86:
Flashfire works fine for me.

For sure it would be easier, one step saved. But we loose flexibility (someone do not want Google apps) and I guess licence could be an issue
[Fire Original Android Development] ggow:
- I was reading about this, as this is an unofficial build I should be free to include it

- I agree with you about the potential loss in flexibility, I am not sure if we would flash another build of gapps like pico over the top.

- not intending to do this unless it will really help with risk of bricking.
[Fire Original Android Development] DB126:
Yep - seeing it now. Thanks for follow-up.
[Fire Original Android Development] GhostRider86:
Ok, so what about two builds? One with apps and one without? How much effort in your repo? I'm not a friend of this, guess more faulty...

Flashing another apps over another wouldn't be the best thing to do☺
[Fire Original Android Development] ggow:
I don't really want to maintain two versions of the ROM, as I have many projects on the go now.

I suppose it depends really how clean a job the gapps installer script is at cleaning a previous installation of gapps.
[Fire Original Android Development] GhostRider86:
Yeah, that's what I guessed too. Let's hear some other opinions. I would leave it as it is, more flexible and less fault possibilities in building and cleaning
[Fire Original Android Development] ggow:
As I said, not something I am immediately going to do unless it helps with the risk of bricking the device. If all is good and it's working for the majority then it will be left as is :)
[Fire Original Android Development] ipdev:
Currently using FlashFire-v0.35-20160526190331-TEST-2. on everything.

(Just easier than booting into twrp. ?)

Only problems are with the 8 and 10 kindles.

As far as adding gapps, I don't think it's necessary.

Like others said, it's just one less step. (I normally install pico.)

(Complete wipe, install rom, install su, install opengapps, wipe cache and dalvik.)
[Fire Original Android Development] :
Ok, I see. Thank you for the information. Is there no other way to backup/restore the current state of a CyanogenMod OS running on the Amazon Fire?
[Fire Original Android Development] ldeveraux:
Please don't include it. It's a real bear with dirty flashes. It's really not a problem to add opengapps to my list if for some reason was doing a clean install. But no, I would never include it...
[Fire Original Android Development] Y314K:
I would say that leaving Gapps to the individual is best. I like to upgrade to the latest version when ever I want to flash a rom clean.

The FlashFire instrucrions in the OP seems to be good enough to stop most user errors. The folks that encounter the stubern Gapps problem will probably need to go back to stock & start a new anyway.

I would even say they should be left out of the Nexus build. But since it's part of stock I know why they are included.