yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] BeeWall:
If fire Nexus gets updated, could patches be taken from that and ported to cm? Maybe taken straight from AOSP? I'm kind of a noob, so sorry if the answers should be obvious on why not.
[Fire Original Android Development] jaladhjin:
I really must have just not rebooted then because I did everything else I knew how to do all that & it was all chaos for me & I was beside myself with **** **** **** I don't want to restore to FireOS again & basically start all over..

It's all good now.. all great.. all beautiful.. thanks all for chiming in.

.

[MENTION=5749760]ggow[/MENTION] I'd like think I was pretty clear in my rant but I want to say it again.. I wasn't flaming you man.. wasn't intended to call the rom some broke pile of trash or anything of the sort it was my personal ignorance & I'm grateful for your releases.. your time.. your trouble..

So to you specifically thanks again :)
[Fire Original Android Development] ggow:
No worries, good to hear it's working :)
[Fire Original Android Development] DB126:
With some restrictions anything is possible with sufficient time and talent. Time is the resource in greatest demand as the qualifications of the development community for this device are well proven. Best left in their capable hands. Lots of CM 12.1 instances in the wild...many that have no viable path to Android 6+. I suspect a best practice will emerge that will keep those devices relevant/secure for the foreseeable future.
[Fire Original Android Development] Marsu42:
Did the LineageOS devs actually state that they won't do Android 5.x, or is it just that they only released 6/7 with the first batch after switching from CM?

Simple /me is new to Android, and I'm wondering how necessary it is to have the latest sec patches anyway. Not only b/c lotsa devices in circulation never get any updates at all anymore. But how grave is the danger for example to catch some drive-by download with an updated web browser that then roots your device behind your back? This isn't like Windows, is it?

I understand Amazon and the like want to have their OS patched to prevent rooting, but from a mere user perspective I really wonder if this CM build isn't "good enough" as long as people will keep using the Fire7.
[Fire Original Android Development] BeeWall:
I believe they said it is MM/N only.

I'm personally fine with this version right now, but it's good to be on the safe side. While there is a small chance, if it does happen to you, then it doesn't matter what the chances against it were, it happened anyway. Plus, as I said, it's a good idea to stay up to date.
[Fire Original Android Development] ggow:
Agreed, FireOS only gets patched when they want to prevent bootloader unlocking and rooting.

Amazon have a history of not keeping as up to date as some other manufacturers do.

This version of CM-12.1 is much more secure then FireOS 5.x will ever be.

Also much of the newer security updates from google are more gearing towards Android 6.x and 7.x .
[Fire Original Android Development] BeeWall:
Probably part of why lineage is 6.x and 7.x only, as well as lack of time for development of older versions. Patches could be backported, but I imagine it would be hard. It's kind of funny to hear anything positive about OEMs staying updated ☺ Though I agree they are better than Amazon. And when they do update, it's a really bad idea to take that update, because it's probably going to ruin root for a while.
[Fire Original Android Development] Marsu42:
... and that's saying something. Esp. all the non-Amazon devices dumped onto customers during the recent cyber week by Amazon were Android 4.4 or maybe 5.0, with the latest updates from a couple of years ago.

Are there stats on what Android non-specifically targeted remote or local (script exploit, drive by download) exploits actually did happen in the wild, i.e. how dangerous running Android is vs. Windows in usual Internet or Office usage?

There comes a time in a man's life if you've watched one too many security updates like from libobscure-1.23.15-9.ubuntu-3 to libobscure-1.23.15-9.ubuntu-4 and start wondering about the actual attack surface if your aren't working for a government, key industry or terrorist org.

For me, keeping an up to date web browser and scripting engines is important, but everything else hit me by my own stupidity running programs from non-trustworthy sources outside a sandbox. With Android and the play store (not that I applaud manufacturer's control over software), the reasons for sec updates seem to be to prevent reading other users' data in a multi-user device or installing software on locked company/school devices.
[Fire Original Android Development] Firefly1337:
Just wanted to say thank you for this amazing ROM. [MENTION=5749760]ggow[/MENTION]

I received my brand new Fire yesterday. Imagine my surprise when I checked the software version, it was running 5.0.1 from 2015. I quickly booted TWRP and installed this ROM.

I live in Germany and bought the 8 GB version without ads (it's a gift for my mom), maybe someone else will be as lucky as I am :)
[Fire Original Android Development] andPS2:
any way to get fire emblem running?

playstore says device not compatible

sideloading from apkmirror i cant press the install button only cancel

should run on android 4.4 and higher

p.s. ok it was either the missing "play games" apk or the twilight app with night mode

(can't touch install when that is running only cancel)

working now!
[Fire Original Android Development] ggow:
Announcement

As many of you know, the CM-12.1 branch will not be supported in the new LineageOS fork. And many of the new Google security patches are difficult and fiddly to back-port as they are now geared towards Marshmallow and Nougat. So as a result there will be no further updates to this rom.

Instead my focus will now be Fire Nexus ROM for this device.

Also looking at possible ways to get later android versions on the device. Will let you know if there is any progress later.

Thanks for all the support :good:
[Fire Original Android Development] :
Thread closed per OP request.
[Fire Original Android Development] nirogu325:
You mean what people call here a dirty flash that involves cleaning both Cache and Dalvik Cache, then flashing the build on top of the older one. That way, the user doesn't lose anything. It is advised not to do that if you want to avoid possible stability issues. Also people who do dirty flashing are advised not to report issues in development threads such as this one. Clean flashing involves losing everything (except internal storage data) by formatting /system, /data, both caches and then flashing the ROM.
[Fire Original Android Development] JasonJJM:
Thanks, that clears everything it up. I will do the clean flash, since its best for stability. Just wondering, but what kind of stuff is stored in the internal storage data (must be something important if its never erased..)
[Fire Original Android Development] nirogu325:
Well, it's not erased if you don't select to format Internal Storage. That's optional for a clean flash.
[Fire Original Android Development] JasonJJM:
Okay that makes sense, but what kind of stuff is typically stored there, it must be non-os related files otherwise a clean flash would demand internal storage also be deleted?
[Fire Original Android Development] sd_shadow:
downloads, pictures...
[Fire Original Android Development] kylemaguire:
When you format a 32+ GB through FireOS's SD card settings, it does format it as exFat.
[Fire Original Android Development] JasonJJM:
Okay, cool, thanks :)
[Fire Original Android Development] Stormbringer!:
I tried one of the 5.0 from the site listed on page one and it said "incompatible rom" which gapps are people using that actually work? is anyone using the gapps from the site listed?
[Fire Original Android Development] case-sensitive:
I f wiped cache/data/sytem, flashed the Dec 4 built + root + pico gapp, wipe cache again, and then reboot. The reboot was successful, but everytime I fire up the brower I got the error message "Unfortunately, Browser has stopped". I reflashed the whole thing a couple more times and I still got the same error message (I even tried another side-loaded browser). Any suggestions on how to fix this?
[Fire Original Android Development] switchy85:
You need 5.1 gapps.
[Fire Original Android Development] Stormbringer!:
Sigh... yes, I know.....

I tried all of the 5.1's located on http://opengapps.org/ from the first page and I get the google store crashing... someone else suggested I try an earlier version, I tried 5.0 from the same site, and that didnt work.

Are you guys using gapps from another download?
[Fire Original Android Development] Deuces:
5.1 pico should do the trick. might want to try wiping /system /cache and /dalvik-cache in recovery and installing the 3 zips again (cm rom, pico gapps, supersu)
[Fire Original Android Development] Webern:
I used:

open_gapps-arm-5.1-nano-20151203.zip

Works fine. Had a brand new fire 7. Booted into twrp, did factory reset, flashed cm, supersu, gapps. Everything works (except Google Play Games - need to spend a few minutes fiddling with that). It's more stable than my stock nexus 10. Everything I used I got from locations suggested in the first post on this thread.
[Fire Original Android Development] kramalot:
Had the same problem with the 1204 build of CM + the 1204 gapps pico. Got it working OK with an earlier gapps pico build (one from Nov on rootjunkies site, but I assume it would be fine with any gapps pico build prior to 1204). This has been discussed in the fire q&a thread http://xdaforums.com/amazon-fire/help/cm12-1-20151204-problem-t3263531
[Fire Original Android Development] duanim:
Last update I did the dirty flash using flash fire apk from chainfire,even I did a backup was safe for me no problems so far.

Flash the CM update,the slim mini or nano gapps and super su at the same time.
[Fire Original Android Development] Stormbringer!:
Sweet! Thanks for all the info, I got it working somehow (hey, I had a lot of beers by this time!). So I went to try working on the other one that I got on black Friday so I can figure out what did it. Of course I ran into a different problem that I cant seem to find much info on. the fastboot gives me an error, I used the same file/command on the previous one that works and this one throws up:

C:\Temp>fastboot boot TWRP_Fire_2.8.7.0.img

downloading 'boot.img'...

OKAY [ 0.303s]

booting...

FAILED (remote: unknown command)

finished. total time: 0.318s
[Fire Original Android Development] switchy85:
I assume you let that tablet go through the update process and it now has 5.1.1 on it, which breaks fastboot. One of mine did that, too. I'm just lucky that one has a dead pixel so I'm returning it.
[Fire Original Android Development] sd_shadow:
If on 5.1.1, at this time,

cannot root

cannot boot custom recovery

cannot downgrade

once a the update.zip is captured, maybe a new twrp can be built
[Fire Original Android Development] Deuces:
did you try kingroot?
[Fire Original Android Development] jayjr1105:
Hey guys, so I have the error after skipping SIM card step too... How do I get back into TWRP. I have the November based recovery from rootjunky's site. Just not quite sure how to get back into TWRP. I can get into stock recovery and into fastboot mode. I'm just not sure how to get TWRP from fastboot.

Edit: Nevermind, just tried the boot TWRP script. I was using the supertool.
[Fire Original Android Development] Vlasp:
Can someone test Clash of Clans on this ROM and reply with feedback? When I was on this ROM when it first came out, my device would shut down randomly while I was playing. Thanks!
[Fire Original Android Development] spicypixel:
Well I'm really glad I decided to switch to this ROM before the latest OTA, that'd be a disappointment.
[Fire Original Android Development] thechosenone43:
True ? I didn't buy it [MENTION=1654362]the black[/MENTION] Friday but i safed myself the pain I. T.A. with the latest OTA from Amazon ???
[Fire Original Android Development] eigen:
Making great progress! Thanks for your work. I can't wait to get CM running on this.
[Fire Original Android Development] acmurdah:
I have a few mp4's on my sdcard that worked fine on stock, but they won't play on CM12. I hear the audio but no video tried stock media player, VLC, and MX. Something that needs to be done or workarounds to get videos to work?
[Fire Original Android Development] 4t701:
settings --> developer options --> check "disable HW overlays" --> check "Use AwesomePlayer" (deprecated)

that's what fixed my video issues. Pretty sure after each reboot you have to go in and recheck "Disable HW Overlays" though :/

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

Does anybody know how to change default install location for apps and downloads on cm 12.1 (latest 12/04 build)?
[Fire Original Android Development] k4y0z:
I just wanted to post a quick update on the status of kexec:

I finally got a new Kernel to boot (paritally) :):):)

The new kernel will load, but then crashes, seemingly because the cpu-cores aren't reset properly, will have to look into that.

I will try to implement hardboot, this should hopefully prevent issues like this.

I wasn't yet able to get atags exported to /proc/atags.

Since they are required for bootup my solution for now is to boot a custom kernel (once) with atags_proc enabled using fastboot,

and than just copy them to a file for later use. I will try to find a way to get them exported using a module.

(atags contain device dependent information like MAC-adresses and serial-number so we can't just include them)

If that doesn't work, I suppose we could just use a recovery with a custom kernel (with atags_proc) and copy the atags during installation.

So long story short, I am confident we will soon be able to bypass the locked Bootloader and run a custom Kernel. :D

We will still need to use "fastboot boot" during installation, so this ISN'T a bootloader-unlock and WON'T help those unlucky ones that got an updated bootloader without "boot" support.
[Fire Original Android Development] case-sensitive:
gapps stop working after a while

[Edit: I fixed this by (1) doing a factory reset (2) uninstall the "Playpermissionfix" module in xposed. In retrospect I probably could skip (1) and do (2) only.

Play store is still a bit wonky but it mostly work (and youtube works 100%). YMMV.]

I flashed the 12-04 built with the 20151120 pico gapps, and I was able to download apps from playstore. But after a couple of reboots (initiated by me and not because of any problem) the playstore AND youtube stops working.

I have a couple of older devices running various versions of lollipop, and playstore+youtube etc all stopped working for at least a couple of weeks. The trigger seems to be v.6 of the playstore --- when I use titanium backup to restore an older version of the playstore on these devices the playstore works for a minute or two until it updates itself. On the Amazon Fire I could not even install the older version of the playstore so I couldn't test this.

Am I the only one having this problem, and any advice on how to fix this? Thanks!
[Fire Original Android Development] acmurdah:
Thanks videos working again, I have same question about default install location and downloads
[Fire Original Android Development] jgore43:
I've been trying to build this rom for a couple days now, mainly for personal use/learning purposes. I've been able to get it to build with brunch ford, and boot to the loading animation, but it stays there and will not continue past that stage. Was there anything special anyone has done to get his rom to boot? Im new to the process of compiling cm-mod without the devicetree - etc in the source. Thanks for any help..
[Fire Original Android Development] Unjustified Dev:
Did you pick the netd change to make selinux permissive? You could be getting denials on boot causing segfaults?
[Fire Original Android Development] 4t701:
remember you gotta recheck "Disable HW Overlays" on each reboot.
[Fire Original Android Development] fmc000:
Some posts in the last few days are confusing me. People are saying that after the latest factory update you shouldn't be able to boot a custom kernel because of some bootloader changes. I received my fire last week and as soon as I booted it kept updating itself. But after that I still was able to boot a custom kernel and replace the default launcher with one of my choice (Nova, BTW). What am I missing?
[Fire Original Android Development] csolanol:
New update arrived 2 days ago. That's the reason.
[Fire Original Android Development] jgore43:
I grabbed the files for that change from bitbucket and overwrote them in my local source. Still no luck
[Fire Original Android Development] spicypixel:
Anyone had the screen go black and effectively turn off if you pull down the notification shade? I was chromecasting a plex video and nothing I did to open the drawer worked, it just flashed up and the screen goes black. Power button turns it on but I can't open it without just making it go black again.
[Fire Original Android Development] hithisisme:
Flashed with TWRP and now cannot get past "SIM card missing" after I click skip it says "Unfortunately, Google Play services has stopped.". I cannot get past this. I have used ARM 5.1 Gapps pico. I have tried to flash stocks gapps but it isn't working.

EDIT: I have gotten past this with turning off wifi before it asks for a sim card but whenever I use google play it says "Unfortunately, Google Play services has stopped." Can I flash new gapps or am I stuck without them?

Double Edit: I have re-flashed everything, but whenever I use google apps it says "Unfortunately, Google Play services has stopped.". Guess no gapps for me. :(
[Fire Original Android Development] ldeveraux:
I can't figure out how to just flash the ROM in Cyanogen recovery. Shouldn't there be a drill down option for it? Or is there an ADB command?
[Fire Original Android Development] acmurdah:
I had same problem and reflashed everything using gapps from rootjunky site here and worked fine http://rootjunkysdl.com/?device=Amazon Fire 5th gen&folder=CM12
[Fire Original Android Development] kramalot:
Out of interest which days gapps build were you using, I and a few others had the problem with gapps of 20151204? Be nice to know if the problem persists beyond that.
[Fire Original Android Development] joll200x:
I had the same problem with GApps and the Google Play services crashing. I was using Nano GApps from 5th December 2015 but found the copy that RootJunky has on his site to work fine. Found that to get past the 'missing SIM card' error disabling WiFi / not setting up a WiFi network works too.
[Fire Original Android Development] imonandroid:
I had the same issue, I ended up restoring a backup but based on the feedback here it sounds like an issue with the latest gapps. I'm going to try with rootjunkys gapps tomorrow night when I'm back home. Will also try with the latest gapps to see if it's been fixed with something even newer.
[Fire Original Android Development] kramalot:
Will an older gapps install over a newer? If not what needs wiping to get rid of it, presumably system? I'd like to try installing the 1202 build of CM with today's gapps to see if its gapps or CM. I know CM and gapps of 1202 were OK together and, if my memory serves, so were those of 1203.
[Fire Original Android Development] BXM500:
I can confirm, that 04/12/2015 ROM works fine with Open Gapps 3/12/2015.

Any newer Gapps and I got force close.
[Fire Original Android Development] mercurio.:
Hi,

I have noticed two bugs:

For me when switching on the tablet after some longer sleep time (I guess when it is in some deep-sleep status) the display only shows some wired lines (looks like the graphic chipset is not up or something like that) after putting it to sleep (tap on power button) and waking it up again it works right.

One other bug is that when putting it to sleep a rotated and wrongly scaled screen-dump is used for the screen off transition... I suppose that's some easy to solve bug...
[Fire Original Android Development] Nooblet:
How long does first boot take? I dirty flashed it goes through optimizing apps and then just hangs on the cm boot logo. Rom flashed, supersu flashed, and gapps flashed, still no boot.
[Fire Original Android Development] ggow:
- Did you try a factory reset in TWRP?
[Fire Original Android Development] Nooblet:
I wiped system, dalvik, and cache in TWRP, rebooted to CM Recovery as Sideload does not function in TWRP.

---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------

I wiped system, dalvik, and cache in TWRP, rebooted to CM Recovery as Sideload does not function in TWRP.
[Fire Original Android Development] ggow:
- Did you wipe /data?

- You must do this.
[Fire Original Android Development] k4y0z:
[MENTION=5749760]ggow[/MENTION]

I just hacked up this little kernel module, which will set selinux to permissive once loaded.

It can be placed in a location where the original kernel/ramfs will load it, like "/system/lib/modules/vcodec_kernel_driver.ko" (which is loaded by /init.mt8127.rc).

This should remove the need for SuperSU and the netd hijack, and also speed up the boot-process.

Since selinux is set to permissive much earlier during boot, this should allow us to enable init-scripts and such.
[Fire Original Android Development] kramalot:
Ah, useful to know. BTW Do you know where the the 3/12 gapps can be downloaded because I've lost mine, should be in my prev_vers folder but I suspect a gremlin ate it (or I deleted by mistake, but how likely is that...)
[Fire Original Android Development] ggow:
- Thanks for this, will test this out for the next release :)
[Fire Original Android Development] sd_shadow:
Not what you asked for...but the

open_gapps-arm-5.1-pico-20151120.zip can be found on rootjunky
[Fire Original Android Development] csolanol:
Awesome. Will test too. Ty!
[Fire Original Android Development] k4y0z:
BTW, I just tested out init.d support, to enable (requires selinux_permissive.ko):

- move /system/bin/install-recovery.sh to /system/bin/install-recovery-orig.sh

- create new file /system/bin/install-recovery.sh:

#!/system/bin/sh

/system/bin/sysinit

/system/bin/install-recovery-orig.sh

- chmod 755 /system/bin/install-recovery.sh

EDIT:

SuperSU overwrites the file during installation, so additionally create a symlink to survive SuperSU install:

ln -s /system/bin/install-recovery_original.sh /system/etc/install-recovery-2.sh

Then we can put init-scripts to /system/etc/init.d/ which will be loaded at startup (like the exfat-fix for example):

/system/etc/init.d/99exfat-support:

#!/system/bin/sh
/system/bin/mount.exfat /dev/block/mmcblk1p1 /mnt/media_rw/sdcard1/
/system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/sdcard1 /storage/sdcard1&

- chmod 755 /system/etc/init.d/99exfat-support
[Fire Original Android Development] kramalot:
Thanks for that, but I already have that one.
[Fire Original Android Development] nirogu325:
I personally use this one without any issues.
[Fire Original Android Development] BXM500:
You can get all previous versions from their GitHub.

https://github.com/opengapps/arm/releases

"open_gapps-arm-5.1-pico-20151203.zip" in that case.
[Fire Original Android Development] kramalot:
Many thanks. I poked around there a few days ago, dunno how I missed it!

---------- Post added at 01:11 AM ---------- Previous post was at 01:11 AM ----------

Cheers.
[Fire Original Android Development] GloriousDJ:
Thanks so much for all the hard work you have done. I was wondering why after I moved every app to sd card that I could, it still has the same amount of storage used internally? This is a clean install and I went to settings > apps > (clicked on each app) > move to sd card.
[Fire Original Android Development] demig0d01:
Is anybody having issues with this thing randomly shutting down while playing games and watching vids? Not sure if its the rom or my device

edit: just saw vlaps post, coc was what i was playing also but it also shuts down with other games
[Fire Original Android Development] jbombs16:
How do we fix the brightness issue?