yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] norweeg:
Thanks! I was able to flash successfully with flashfire 0.31 once I found an apk. Unfortunately encryption still makes the external SD card read-only :(
[Fire Original Android Development] Signor Rossi:
External SD is read only also without encryption.

Search the app store for a sd card fix

Gesendet von meinem OnePlus One
[Fire Original Android Development] kramalot:
Anyone know if, somewhere in the last few updates, something has changed in the permissions of last_kmsg?

I use a little app called Bootlog Uptime which used to make a copy of it after a crash and I've just noticed that it is now failing. I also can no longer copy it manually using fx though I can using cm file manager. Fx gets permission denied.
[Fire Original Android Development] norweeg:
SD card in mine is read/write before encryption and read-only after
[Fire Original Android Development] berto648:
Tried a lot of different browser but man does lightning browser load quick. Thank you for the hint. Appreciate it! Works great on the Touchpad as well.
[Fire Original Android Development] berto648:
Been installing games. So far pretty nice. But on kingdom hearts unchained x, just released, i get really annoying lag. Almost as if the GPU can't handle loading all of the map. Almost playable. Tested on other devices I own, even on the ancient touchpad and the game runs smooth. Is our device just not able to run this game? Not really an issue as its just a free android game. But curious. I mean its already surpassed my expectations but wonder why this game is so close to running.
[Fire Original Android Development] DB126:
5th gen Fires lack a GPU. The CPU combined with reasonably fast internal bus/memory and low-res screen handles many graphical tasks surprisingly well. Really depends on combined workload and size of dataset. If most/all doesn't fit into memory performance is going to suffer.

---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------

Not a problem for most. If you need a 'fix' on recent CM 12.1 builds something else is wrong.

---------- Post added at 02:46 PM ---------- Previous post was at 02:35 PM ----------

This makes sense from a security perspective as protection can not be assured on removable devices unless they too are encrypted. Windows users know the failure scenario well as EFS protected files are silently decrypted when copied to a non-NTFS device/partition (most flash drives). It would be nice if you were given the option while acknowledging the potential exposures. Marshmallow takes a different approach: when you 'adopt' storage is becomes unusable off-device. I believe encryption is maintained on the removable device but have no MM builds to test on at the moment.
[Fire Original Android Development] Signor Rossi:
I might be wrong, but this is normal since Google changed how external SD Cards are being handled. I guess it's like this since KitKat.

Gesendet von meinem OnePlus One
[Fire Original Android Development] DB126:
Typically not needed with custom ROMs as devs have set permissions to allow write access. Are you finding this is not the case with CM 12.1? If so it doesn't mirror my experience - but I have many have inadvertently done something enable SD card writes without knowing it.
[Fire Original Android Development] booogermonkey:
I haven't had any issues on either one of mine running this rom[emoji15]
[Fire Original Android Development] kramalot:
I've needed sdfix on every version of 12.1 so far and often wondered why sdcard was not rw by default and prior to the version I'm using now (1 back from latest) have occasionally needed to rerun it after write access vanished. Now I worry that I'm doing something wrong son where along the line ?
[Fire Original Android Development] booogermonkey:
So long as the end result gives you rw to sd, it's all good I guess
[Fire Original Android Development] Signor Rossi:
I had to fix SD every time I flashed a new Version of this rom here.

Titanium Backup wasn't able to write to the external SD without the fix

Gesendet von meinem OnePlus One
[Fire Original Android Development] berto648:
[MENTION=5488402]Davey126[/MENTION] thank you for the reply. Real shame. I guess its just too much to load at one time. If I let it sit for a while the fire seems to load up the environment and I get normal play for a bit. But the minute you enter a new section of the map the tab just skips about 15 frames. Time to uninstall.
[Fire Original Android Development] DB126:
Doubt it's ROM related. Try a few different cards (if you have access) and make sure the format is correct. On one (and only one) occasion CM 12.1 could not see a fresh FAT32 card when first inserted. CM knew the card was there but couldn't see contents. I allowed CM to initialize (Settings->Storage) at all was well. Reported VFAT after formatting which is a variation of the original FAT. See below.

Interesting read -> http://stackoverflow.com/questions/...ifference-between-vfat-and-fat32-file-systems
[Fire Original Android Development] riverstyxxx:
The first tablet I installed this to is running so good that I decided to buy a second one for a backup (Or if there's any new builds that need testing). Great job and thanks for all the help, everybody's really awesome here.
[Fire Original Android Development] nyln:
This worked flawlessly, however I needed to use Flashfire 0.24, as 0.27 crashed.

This is the link I used:

http://flashfireapk.com/FlashFire-Download.html

---------- Post added at 01:28 AM ---------- Previous post was at 01:27 AM ----------

I only wish this was working with the HD 8/10 models, it would be so great on them.
[Fire Original Android Development] GartimusPrime:
I have now put either AOSP or CM on 10 of these devices. It really makes these a halfway decent device. Thank you to all involved to make this happen. My only thing is, like a few others, I am unable to write to my external SD card as of late.
[Fire Original Android Development] kramalot:
Well, current card is a Sandisk Ultra and apart from needing sdfix once to make it writable, which seems to have stuck with this ROM, all is well so I guess I'm content to leave well enough alone at least for the time being.
[Fire Original Android Development] DB126:
Both Nexus (AOSP) and CM? Happen spontaneously or after flashing an update? Both ROMs are supported by the same dev and received recent security updates. Wonder if there is a common thread. It's simply a permissions issue; possibly getting reset somewhere.
[Fire Original Android Development] Signor Rossi:
FlashFire 0.31 is out [emoji41] crash at loading is fixed in there

Gesendet von meinem OnePlus One
[Fire Original Android Development] ggow:
Think I have found what's going on with not been able to write to sdcard. In the next release I'll have something in place to try.
[Fire Original Android Development] Sulinjr:
Hey guys I recently updated to the latest build of CM12 by ggow, I moved some apps to the SD card via the built-in android movable app to SD function. The apps work fine but I do notice they disappear from my home screen every so often. Not sure if this has been reported or not. If anyone has a temporary fix please let me know! Thanks!
[Fire Original Android Development] DB126:
This symptom has been reported. Dev is working on a SD accessibility issue that might address this issue. Hang tight!
[Fire Original Android Development] Sulinjr:
Is there a temporary fix that you know of? Something I could implement in the mean time? Such as a 3rd party app from the Play Store to lock the icons in place?
[Fire Original Android Development] DB126:
Try SDFix or Link2SD. I have no experience with the former but has been recommend by several as a quick/easy 'fix' to various SD woes. Despite the title it apparently works on Lollipop ROMs. Link2SD is a more robust solution which I have used and like. I wrote a small blurb about it here; collaborated by a CM user here and elsewhere within this thread.
[Fire Original Android Development] kramalot:
On the occasions when I've had icons for apps on the card disappear a soft reboot fixed it.
[Fire Original Android Development] Sulinjr:
Oh really? I haven't had the same luck but I've been doing a full reboot, I will try your method.

Yes I have SDFix and while that does fix the SD Card writing issues, I still do notice my icons disappear from the home screen. Its seems to be affecting only the icons of apps that have been transfered to the SD. Either way it sounds like these issues are related and will be fixed in the upcoming update. Thank you for being so thoroughly helpful.
[Fire Original Android Development] kramalot:
Can't imagine it makes any difference, I only use soft reboot because its marginally faster.
[Fire Original Android Development] Sulinjr:
Yeah I gave it a shot and the icons didn't come back. I'll just keep the apps off the SD until an update corrects the issue. It sounded like he had figured out the problem so after he compiles his code I'm sure it will resolve the SD issues.
[Fire Original Android Development] matthieuarcher:
Bootloop

Hi people!

I installed recently the CM ROM by following all the steps and I succeeded quite easily thanks to the tutorial. Yesterday I played with LuckyPatcher and I used the odexify system app. It rebooted my FIRE after some seconds and now I'm sucked in a boot loop. I tired to go in the amazon recovery and do the factory reset but CM is still in bootloop. I had the Fire OS 5.1.1 and the recovery cannot allow me to flash a zip file. I cannot enter into the CM and use FlashFire to re-install CM or my backup of the FireOS I did when I rooted the tablet.

Is there any trick for the 5.1.1 version?
[Fire Original Android Development] ggow:
New Build is Up

- Dated 11 April 2016

- Fix sdcard write access?

- Could someone test and report back any impact on the ability to write to sdcard?
[Fire Original Android Development] Sulinjr:
I'll test it now.

[MENTION=5749760]ggow[/MENTION] Update: The issues appear to be resolved but I'm still running tests to see if the app icons are continuing to disappear from the home screen after being moved to the SD card.
[Fire Original Android Development] kramalot:
Looking good here so far, yet more thanks [MENTION=5749760]ggow[/MENTION] ?
[Fire Original Android Development] ipdev:
cm-12.1-20160411-UNOFFICIAL-ford

Seems to be working for me.
[Fire Original Android Development] Sulinjr:
[MENTION=5749760]ggow[/MENTION] Final Update: I've spent the better part of today testing all of this and I've concluded the following...

-SD writting issues appear to be resolved.

-App icons continue to still disappear from home screen after moving them to SD with built-in moveable App to SD functionality.

Hope this helps with further testing, feel free to contact me if you need additional information.
[Fire Original Android Development] jboxer:
This thread is very long so please forgive me if this question has been asked before. I am currently using the Jan 4th CM12 version and want to update to the latest release. Is there a simple way to update without having to factory reset? Can I just flash the new release over the current one and what is the best tool to use to do this? My Fire still has the ability to boot into twrp recovery and has Flashfire installed.
[Fire Original Android Development] sd_shadow:
just install new version in twrp, no wipes required

or follow upgrade with FlashFire instructions in post #1
[Fire Original Android Development] mbholm:
So, I have seen Davey say to keep FlashFire defaults, but first post still says to uncheck all options (rw and automount)? Which is it? I also would like to update cm, but fearful of updating cm without twrp.
[Fire Original Android Development] Sulinjr:
Rootjunky has some tutorial videos on YouTube involving flashing with FlashFire. However Davey is well respected and thorough, its a pretty safe bet to follow his instructions.
[Fire Original Android Development] jboxer:
Thanks. When I get home I'll charge it up and update it.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 12 April 2016

- Fix disappearing icons for apps moved to sdcard?

- [MENTION=7112146]Sullinjr[/MENTION] could you test and report back whether the issue is resolved?
[Fire Original Android Development] sandman512:
Would someone mind linking the latest version of FF that will work. Thanks!

PS: I was reading through the latest posts, but just want to be sure that I get the right one.

Thanks!
[Fire Original Android Development] m00head:
Latest confirmed version of Flashfire that works with this ROM is v0.31:

https://plus.google.com/+Chainfire/posts/8WB78xvY2oM
[Fire Original Android Development] ldeveraux:
uncheck is the safest with less chance to brick
[Fire Original Android Development] mbholm:
I have seen several mention issues with wifi stability. I just moved one of my sons from FireOS and he noticed the first day. Is a different wifi driver used by the custom roms?
[Fire Original Android Development] Tibidee:
After flashing the new version I've moved some apps to the SD card and rebooted the device - All apps are still on my homescreen and started without a problem! Great! Many thanks! :good:

Edit: Sorry... A few reboots later most of the icons were gone again. :(
[Fire Original Android Development] mattcb:
When I tried flashing this and the gapps my 5.1.2 tablet was on blank screen after saying "Beginning flash" or something like that (I know it warned about this but it was a very long time.). I force rebooted and then I lost my root. Was the blank screen supposed to happen? How can I keep my root?
[Fire Original Android Development] sd_shadow:
tried what?
[Fire Original Android Development] mattcb:
I tried flashing this ROM. I've edited my original post too.
[Fire Original Android Development] sd_shadow:
how?
[Fire Original Android Development] DB126:
No evidence one way or the other except for personal experiences which vary all over the map. In the absence of hard data or a dev supported explaination/recommendation I will stick with the FF developers defaults as one would think there is good reason for setting them that way. Keep it simple.
[Fire Original Android Development] mattcb:
Well, I rooted using the supertool (which involved KingRoot) (just search fire 7 2015 supertool and click the XDA link if you would like to find it). I then simply followed the instructions in this post. The only possible theories I have come up with is a root issue (KingRoot is garbage in my opinion and it always was temporary for some reason), nothing being compatible with Fire OS 5.1.2, or using FlashFire 0.31 (although that shouldn't be an issue).
[Fire Original Android Development] sd_shadow:
so your issue is with super tool, ask in the Super tool thread
[Fire Original Android Development] mattcb:
Ok thank you.
[Fire Original Android Development] EgotisticalElf:
I installed 0412 over 0406 using flashfire 0.31 without selecting opengapps and all the googleapps disappeared. I attempted to rectify by re-flashing the rom and gapps together and the apps have reappeared, but i am no longer able to add a google account to the device. I have tried several options including wiping system and reflashing the 0406 build back onto the device with no luck.

Any ideas ?
[Fire Original Android Development] GhostRider86:
Did the Flash of CM run? Ist is starting? Root is disabled by default. Go to developer options and the root access, change to app for example...

---------- Post added at 04:45 AM ---------- Previous post was at 04:43 AM ----------

Use other package. Gapps, Open Capps...
[Fire Original Android Development] EgotisticalElf:
I used opengapps, both the one i put on the tablet initially and a new one i got today. nano size.

---------- Post added at 11:01 PM ---------- Previous post was at 10:50 PM ----------

I just put on the micro edition and same problem.
[Fire Original Android Development] Sulinjr:
[MENTION=5749760]ggow[/MENTION] Testing Now...
[Fire Original Android Development] ipdev:
Had to reboot after restart (Wi-Fi connection issues. Said I was connected but, I wasn't)

Still have all my settings & gapps work fine.

First time updating.

Normally I restore back to fire os 5.1.1 & start fresh.
[Fire Original Android Development] jboxer:
Root is built into CM12. Why are you flashing supersu?
[Fire Original Android Development] ipdev:
I run the supersu beta on all my devices.

(Seems to work better than most supplied su.)
[Fire Original Android Development] Sulinjr:
[MENTION=5749760]ggow[/MENTION] I've finished testing. I experimented with a few variables, via fresh install with and without Xposed components. Also with with and without apps that could affect the file structure such as Clean Master.

It first seemed there was some correlation between app cleaner programs such as Clean Master; I would clean the system, reboot then see the app icons that had been moved onto the SD. However after another fresh install it appeared to happen again regardless. It would seem however, to take a couple of reboots for the symptoms to show up but this could just be completely random.

Xposed modules didn't appear to have any sort of impact.

The app drawer would take a few mins to load up upon reboot (Granted, there were 60+ apps installed onto SD) Apon receiving the appropriate permissions from SuperSU they would eventually load correctly (in the app drawer, not icons on home screen).

Interestingly enough though, during reboots I noticed sometimes that some of the apps that had been moved onto the SD would not disappear while others would. This appeared to happen at random with random app icons. This did not happen before so you may be getting close to a solution with that last CM12 build. Ultimately, I've found after many reboots the movable app to SD icons still eventually disappear with all given scenarios.

I'm calling it a night but I will test out a few more things in the morning and report if I find anything of interest. Excellent work on this [MENTION=5749760]ggow[/MENTION] I'm sure I speak for more than myself when I say we appreciate your time and effort on this.

Update: On another note, I've noticed a widget error, "Couldn't add widget" appearing up top in the app changer menu. I'm unsure if this is due to some sort of installed widget or setting. Is this appearing for anyone else?

Picture below...
[Fire Original Android Development] sesquipedalianman:
Open Gapps? Sideloading?

Putting Cyanogenmod on my device worked perfectly! But I can't get open Gapps to load with the process you outlined. It just seems to hang halfway through. I've been trying to sideload open gapps through adb, but with the fastboot adb load it doesn't seem to work. Do you have any guidance on:

1) how do I sideload after loading Cyanogenmod or is there a better way to get open gapps on it?

2) what is the best way to "start from scratch" after I loaded cyanogenmod?
[Fire Original Android Development] jboxer:
Are you using the pico version? There is very little room left for gapps after installing CM12.
[Fire Original Android Development] DB126:
So where does it say "sideload" GAaps? Use FlashFire 0.31 (version matters) with pico or nano build. This will only install the framework and key components. Other Google properties can then be added via the Playstore.
[Fire Original Android Development] sesquipedalianman:
I tried to sideload through rebooting into the recovery options once I turned on developer options in CM and it has an "install via adb" or some similar option in its menu choices, along with recover & reboot (my tablet isn't with me at this time so I don't have the exact words). I interpreted this to meaning I could use fastboot to add software via adb, but neither my version of adb on my linux machine or my windows one detected the device when it was connected this way.

I'm guessing that I was incorrect in assuming that a 16GB device meant that the system partition was large enough to support a different gapps. I'll give it a shot tonight & confirm that this is all my stupidity.
[Fire Original Android Development] GhostRider86:
We know what sideloading is, but it is but described in the tutorial on page 1, cause it is not necessary...

If you have trouble with open gapps, use Capps, search this thread, I guess something around page 232
[Fire Original Android Development] prisoner1969:
I had the same issue that apps moved to sd card would vanish. Turned out it was a bad SD card. If no one else is having the issue then it's probably your card. I replaced my SD card with another one and have had no issues since then. I googled the problem and it's a common problem on all phones/tablets if the sd card is bad.
[Fire Original Android Development] DB126:
Agreed. A 'bad' card can be one that works perfectly well in other devices and/or for other tasks but does not have the characteristics for this particular use. I have had no problems with this card. Not promoting the brand/card but you can look at specs to get an idea of what works.
[Fire Original Android Development] Tibidee:
I have issues and I'm using a Sandisk Ultra 32GB class 10 card. :crying:
[Fire Original Android Development] DB126:
While that's a nice card speed isn't everything. I have seen numerous class 6 SD cards outpace class 10s on nonsequential I/O. Not saying that is the problem with vanishing icons, just a possibility.
[Fire Original Android Development] sesquipedalianman:
Changing to the pico gapps still did not work, but when I changed to Flashfire .31 it worked great. The tools from rootjunkysdl.com include a previous version of flashfire (.30).

16GB 2015 Fire

was running the eminently awful FireOS 5.1.1

now happily on Cyanogenmod.

Now to find a good source to sideload Instagram...

Thanks very much for the help
[Fire Original Android Development] booogermonkey:
Really? I like the slim build. I'm just lazy and want my features baked in so prefer the cm edit: just read again. Fire os, duh. Yeah fire os sux[emoji12]
[Fire Original Android Development] sd_shadow:
http://www.apkmirror.com/?s=Instagram&post_type=app_release
[Fire Original Android Development] ipdev:
[MENTION=5749760]ggow[/MENTION]

From comments in a few other threads, just wondering if you are working on a 10 / 8 " fire cm build?

Willing to try 8" version if you are. ?
[Fire Original Android Development] ggow:
- Feature will be in the next version
[Fire Original Android Development] danweb66:
FIX for streaming video

so I just wanted to post a solution for anyone having problems with youtube or streaming apps not playing in fullscreen from the web or other embedded streaming sites. if you go to settings and go to display and in rotation set it from 270 to 180 it will work perfect. only reason I came across this is because i loaded this on my stepdads fire 7 and he was having problems with his exfinity go app playing videos. but once i changed these settings it worked flawless.
[Fire Original Android Development] diegocr:
On SlimLP have working bluetooth

[MENTION=5749760]ggow[/MENTION] see my github

rm lib/hw/*.default.so
[Fire Original Android Development] k4y0z:
Build-Environment

Hi [MENTION=535343]all[/MENTION],

Great work so far!

I'm trying to build cm-ford from the sources, however I always get the following Error, when trying brunch:

make: *** No rule to make target '/mnt/mnt/cyanogen/out/target/product/ford/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by '/mnt/mnt/cyanogen/out/target/product/ford/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.

How do I setup the build-environment correctly?

I have repo synced the cm-12.1 source, added [MENTION=5749760]ggow[/MENTION] s device-tree and extracted the proprietary libs from FireOS.

Please help.

k4y0z
[Fire Original Android Development] Harry44:
Thank for for this. Now pretty much everything "major issue" has been sorted out for this device.
[Fire Original Android Development] Awesomeslayerg:
I just want the video playback to be fixed and if possible camera too and that should be enough