yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Chillmann:
It worked :good:
[Fire Original Android Development] ggow:
New Build is Up

- Dated 10 August 2016

- August 2016 AOSP Security Patch Level

- Fix audio lag issue in games - thanks [MENTION=3317625]$ideWinder[/MENTION]
[Fire Original Android Development] toidimaet:
Thanks for your work on all of the custom roms you have created for a number of fire devices , it is very much appreciated.

The only problem I have is sticking to a single one and kick the old rom junkie habit.
[Fire Original Android Development] prazola:
July and august release bugged wifi on my fire. The device connect to my network, but after a bunch of seconds of downloading, every network operation just freeze, but wifi is stil connected. I disconnect and reconnect to the network and, again, I start downloading, then it stops. :(

EDIT:

my net is served by a ddwrt router, and runs of channel 5 (40mhz width) 2.4GHz wireless-N only. If I switch to wireless-g only, freezes disappear. Maybe it's related to the binary used, because I've never encountered this problem before.

EDIT 2:

problem persists with wireless-n 20MHz on channel 1. So it's wifi-n related.
[Fire Original Android Development] EncryptedCurse:
I popped in a 64GB SanDisk microSD card the other day and moved a few apps to it (in the Settings menu, of course).

After a reboot, however, they were completely gone, both from the launcher and under Apps > On SD Card.

I'm browsing through the card's contents with a file manager and I can see an Android/data folder, containing blank folders for a handful of apps (which don't even seem to be related to the ones I moved).

I think it's safe to say that they're gone, but is there somewhere I went wrong or could it be an issue with the ROM?
[Fire Original Android Development] toidimaet:
I've always found that moving apps to SD flaky at best using any roms built in tools, that is why I use foldermount.

It has served me well in shifting large games etc to SD with virtually no issues.

http://xdaforums.com/showthread.php?t=2192122

---------- Post added at 02:57 AM ---------- Previous post was at 02:53 AM ----------

Been using this and nexus rom for weeks on 2.5ghzN and never had any of the issues you have. May be it is a config setting on your router that could be causing the issue?
[Fire Original Android Development] prazola:
I use this cm since the first build and never faced this problem. Nothing has changed in my router config and every other device works.

When I flash a new version I always wipe system, dalvik and cache, but I could try to do a backup and test with a clean install.
[Fire Original Android Development] toidimaet:
This makes it rather strange. Maybe a kernel update in last couple of builds, or some sort of kernel level patch has caused the problem for you. It could also be a read/write issue causing it as well. Just thinking out loud here.
[Fire Original Android Development] ggow:
- There seems to be no problem here on my fire on various networks b,g and n.

- June build marked a change in the binaries used, is that when WiFi started playing up?

- If so try flashing the May build and let me know if that works. <<Link to May Release>>
[Fire Original Android Development] prazola:
I'll test it in a couple of hours. ty
[Fire Original Android Development] DB126:
My go-to app is Link2SD. I believe FolderMount and L2SD both leverage symbolic links which enhances reliability. L2SD does require a dedicated ext4 partition on the SD card which is a PiTA for some. I keep a 32GB card permanently mounted with an 8GB ext4 partition for large apps. Works great. Note performance lags internal storage due to HW interface (read) and SD card (write) limitations. Manifests as a slight hesitation during launch and extended update times but is otherwise imperceptible.
[Fire Original Android Development] prazola:
May build is fine with my wireless network, so it could be a binary problem, but I don't get why new builds can work for like 5MB and then they freeze. I put here my detailed wireless config:

[IMG="ddwrt settings"]http://116.imagebam.com/download/f5qtmKlnmiGt06fNvhRMgQ/49944/499433942/ddwrt.PNG[/IMG]

Yesterday i checkd dmesg and when the problem appears there's a lot of: tx_thread entries about nicTxReleaseResource. I don't know if its mtk related or not, I've never seen anything like this before.

EDIT: after 130MB the problem is back again on may build :(

I'm going for a clean install :((
[Fire Original Android Development] toidimaet:
All true, the only advantage foldermount has, is it allows windows users to access the micro sd directly due to the fat file system. Not an issue for me as I will always fire up Arch or Mint if I want any real work doing. You could still enter the symlinks manually, but that would really only be of interest to a very small amount of people, such as anyone who is perhaps thinking of building/cooking their own custom rom.
[Fire Original Android Development] el_charlie:
So, can I use gapps-config.txt with FlashFire?? I've done it before with TWRP on a S3 mini and worked great. IDK if it works with FlashFire, that's not exactly a recovery.

Cheers!
[Fire Original Android Development] DB126:
Yes, you can (others have - apparently with no ill effects).
[Fire Original Android Development] prazola:
WiFi Problem Update:

switching from channel five to six solved the problem (at least in the last two hour), but...why? I'm confused.

Edit:

I'm lucky...freezed again.
[Fire Original Android Development] toidimaet:
I've been playing around with flashfire and found that it can pretty much do everything that twrp, or any other custom recovery can do. It's a bit like flashify on steroids.

Gotta love flashing from the front end, there is no more remembering different button combos for different devices to boot into recovery. Flashing roms doesn't need to be like playing streetfighter any more :)

---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------

Shot in the dark, but did you update your router firmware recently? If so, it might help to explain the problems you are having.
[Fire Original Android Development] prazola:
Yes, I update it monthly, is there an open bug related to this problem?
[Fire Original Android Development] GhostRider86:
Not relevant, you tried the may build with no issues, so not related to the router firmware
[Fire Original Android Development] prazola:
When I reinstalled that build, after some hour I faced the same problem, but it's started with upgrading from may to june build one month ago.
[Fire Original Android Development] DB126:
Have you gone for a 'clean' install which includes a full wipe of all partitions including internal storage? To pull this off you'd need to put the CM zip (and any related flashable files) on the SD card or OTG device which introduces some risk IMO (not everyone agrees with the risk statement). A less risky, but also less comprehensive approach, involve a reload of FireOS from the stock recovery menu which would also update the bootloader/kernel.

If the problem persists you may have a bad device/soc that coincidentally manifested with the may/june build. Heat would be an obvious culprit which may be isolated to wifi components. To my knowledge there are no radio specific temperature sensors on this device. Keep in mind there are dozens (if not hundreds) of individuals using this rom, some of whom are probably using wifi 'n' networks. If the problem was widespread additional reports likely would have surfaced by now.
[Fire Original Android Development] prazola:
Yes, I did the full wipe many times. I could try to restore the original fire ROM to see if wifi works, otherwise I'm still under warranty...but I want a flashable device back :(
[Fire Original Android Development] toidimaet:
Perhaps ggow or someone else who is knowledgeable regarding the logs you posted may be able to find a solution.
[Fire Original Android Development] ggow:
From I'm guessing you are using TWRP to flash the new ROM?

From the logs you posted, it looks like there is a mismatch between the kernel and userspace API. More specifically the kernel isn't expecting that particular ioctl command.

I'll take a look to see if I can spot anything that may have caused this.
[Fire Original Android Development] prazola:
Yes, I always use TWRP.
[Fire Original Android Development] corax2.05:
I can confirm the wifi bug!

I flashed the june build for the first time on 3 fire tabs.

On 2 of the 3 tabs I see the wifi problem. The third I can check this evening.

The wifi connection doesn'f crash! It only seems like this, but the connection gets extremly slow.

Sometimes it works for y long time fine. Sometimes it happens after some minutes.

Sometimes it seems it get back to normal after a (long) while.

A second bug found in august build.

The Camera crashes if you try to capture a video. It say's "no connection to camera".

Photos are fine.
[Fire Original Android Development] HA4ever:
I can confirm the camcorder bug. However, my WiFi works fine
[Fire Original Android Development] corax2.05:
The wifi on my third device seems to work fine. I synced a big owncloud folder for 2 of 3h. There where no noticeable problems with wifi.

The main difference between the other 2 devices is, it's orange. ;)

Ok.. serious... the orange one was delivered with FireOS 5.1.1.

The others with 5.1.3. Maybe there's a different hardware inside?
[Fire Original Android Development] DB126:
None of my (3) 5th gen Fires are experiencing WiFi issues. All arrived with FireOS 5.0.1 which was immediately overwritten by various roms. All retain the 5.0.1 bootloader and kernel. FireOS was never booted on two of the three. So yea, maybe there are subtle differences on higher level variants.
[Fire Original Android Development] atroph:
What type of encryption are you using?

Also are you using any wds, wifi client, repeater and such?
[Fire Original Android Development] DB126:
WPA2 AES per-shared key (pretty standard). No wds. I have a few repeaters around the house but most connections are to the primary AP. More importantly, WiFi consistently works while travelling whether it be an airport, hotel, cafe or a random ice rink serviced by some home brewed network.
[Fire Original Android Development] corax2.05:
Is it possible to get some hardware information?

I tried some hardware info apps and I looked at the dmesg output, but I cannot see anything about the Wi-Fi hardware.
[Fire Original Android Development] dschroeter:
Loving this rom and confirming the video recording bug, 8/10 build. Is this bug present on the 8/12 AOSP rom, also by ggow? And a noob question: when does an unofficial rom graduate to CM nightlies (to update from the OS)? I'm surprised such a cheap device with such a stable rom isn't there already.
[Fire Original Android Development] DB126:
Also confirming video glitch with stock app and Open Camera. Don't know about Nexus (aka AOSP) rom; haven't seen any related posts in that thread.
[Fire Original Android Development] ldeveraux:
I don't think CM does nightlies for 12.1 anymore with 13 in activity. So the dev updates personally ~ monthly.
[Fire Original Android Development] jratt:
Are there cm-13 nighties for this tablet if so where?
[Fire Original Android Development] sd_shadow:
No
[Fire Original Android Development] ldeveraux:
Did you read the comment you quoted?
[Fire Original Android Development] jratt:
Yes the following makes no sense.

"13 in activity"

"So the dev updates personally ~ monthly"

Did you read what I quoted?
[Fire Original Android Development] sd_shadow:
The bootloader prevents newer android versions (Android 6+ / CM13) from booting
[Fire Original Android Development] dschroeter:
Just an update: I tried the AOSP rom and the camcorder bug is present there as well. Anyone tried video on the slimrom version?
[Fire Original Android Development] SeanAche:
I did a stupid. I assumed that dirty flashing a recent build over an older CM 12.1 install would keep things intact, and I didn't flash SuperSU. Thus, I lost root.

The system was a 5.1.x base, 5.1.1, most likely (I don't remember). I can get it to fastboot, but I can't get it to do anything with anything I attempt to sideload, and attempting to install SuperSU or even KingRoot (blergh) fails. I can't pass anything to the neutered bootloader- it just won't do anything that I would expect.

Can anyone help me with this? Thanks!
[Fire Original Android Development] GhostRider86:
Are you still on cm? Root is build in. available in developer options.

Are you in FireOS? Sideload FireOS in correct version,reroot
[Fire Original Android Development] SeanAche:
I am on cm12.1 (August build) w/ GApps micro. I tried to access su via adb and developer options, but /system/xbin/su is 755. Since I don't have root, and a locked bootloader, I've got the feeling I'm somewhat hosed :silly:

Thanks for your help!
[Fire Original Android Development] DB126:
If (integrated) root will not enable in developer options you will need to reload FireOS via stock recovery (recommend 5.1.2 since you don't recall exact 5.1.x variant) and redo the boot/root/flashfire procedure.
[Fire Original Android Development] ggow:
Integrated root should work

You must reboot for it to take effect
[Fire Original Android Development] SeanAche:
I disabled/re-enabled root and gave it a reboot. I was prepping to sideload 5.1.2, but something told me to try it once more before flattening- root is back! Thanks, everyone!
[Fire Original Android Development] nahtnam:
A bunch of apps are "not compatible". :( That sucks. Anyone know how to work around that?
[Fire Original Android Development] GhostRider86:
Download from apkmirror for example.

I wonder if changing the name in the properties file to nexus or something will help as well?
[Fire Original Android Development] nahtnam:
Yeah, thats what Im doing right now, but installing apks is pretty annoying. Would be great to be able to use the play store instead.
[Fire Original Android Development] alberthdev:
Screen pinning seems to not work. I'm able to enable screen pinning and set an app to pin, but it doesn't look like the pinning is active. If I press the home button, or exit the app manually, I can navigate elsewhere, despite it supposedly being enabled.

Steps taken:

Open Settings, go into Security options, go into Screen Pinning options, enable it, and exit Settings app.

Find an app to pin, hit the Overview button on the screen, swiped up to see the pin button, and tapped it.

App zooms in, but no notification about Screen Pinning appears, nothing happens at this point. Press Home button to exit the app.

Is this a bug, or am I doing something wrong? Thanks in advance!
[Fire Original Android Development] martinml:
I found that all the apps that are "not compatible" with the Fire were because they ask for some phone-related permissions (for example, accessing SMS or making calls), which obviously we don't have. APKPure fixes this, and if you use their app it's not so annoying :)
[Fire Original Android Development] keithalaws:
It made sense to me:

• earlier post asked about migrating from unofficial to official status with nightly builds

• post you quoted says that core CM activity now focused on version 13 so probably no interest in making official nightlies for a device stuck with version 12.1 so in this case the dev is personally producing updates approximately monthly

What's hard to understand about that?
[Fire Original Android Development] jratt:
Sorry that I was born before "PHONE TALK"

I read it as

"13 in activity" = the person who brought this rom to fire tablet 7 was working on cm13 release, and also official cm12 was no longer in development.

"So the dev updates personally ~ monthly" = he releases a nightly cm13 build for this tablet monthly.
[Fire Original Android Development] DB126:
For the record:

- no CM13 for this device (locked bootloader; can't update kernel)

- dev posts an updated version every month or so as time permits

- above is not a "nightly"
[Fire Original Android Development] ldeveraux:
THERE IS NO DEVELOPMENT OF A CM13 ROM FOR THIS DEVICE.

Do I need to make it clearer, or have you gotten it by now?
[Fire Original Android Development] harling:
Hi, I still have a brightness issue - slider not working at all. I installed the Brightness Level app, also this app doesnˋt change the brightness of my Fire just a little bit. I couldnˋt find anything else in this thread, maybe someone has an idea how to get brightness working?

Iˋm little bit confused about various options of Day/Night/Auto - what is recommended to choose to make the slider working?

THX, Christian
[Fire Original Android Development] jratt:
I understood that 3 pages back when sd_shadow made it clear.

as for my other replies they where answers to the people attacking me as to why I didn't understand a cryptic answer.

Now stop with the BS
[Fire Original Android Development] DB126:
Perhaps the best response is none at all ... ????
[Fire Original Android Development] Munns86:
I have this issue as well. Normally after a reboot the brightness will work for sometime but it sounds like it's a memory issue and as soon as the brightness service (not sure if the right word) gets pushed out of ram it won't work again until I reboot again.
[Fire Original Android Development] Copro:
Installed on a brand new Fire that I had to downgrade from stock 5.1.3 to 5.1.2 to be able to root and install. I was missing the notice from the older CM threads that root is required in the first post. Although that became pretty obvious when FlashFire 0.52 demanded root access in one of the first steps.
[Fire Original Android Development] ogpog:
This is interesting, I have one app that I really would like on this device. I sideloaded it onto FireOS but it wouldn't run (well, it would - but only to say the device isn't compatible and then exit!) I'd hoped putting CM on it would make it work but it didn't.

I'd assumed that was that. But then I see these posts and now I am interested in how I might get it to work. How do I change the name in the properties file? And what is APKPure? I searched it and it just seems to be another download site.
[Fire Original Android Development] DB126:
APKPure hosts a number of 'cracked' apps (along with legit copies of free apps) which obviously deprives developers of legitimate revenue.

Changing build.prop properties will typically not fix an app that starts then immediately exits as it usually reflects a deeper incompatibility.
[Fire Original Android Development] ggow:
Which apps are showing as not compatible?
[Fire Original Android Development] nahtnam:
Google Inbox and GroupMe for starters.
[Fire Original Android Development] fmc000:
For inbox: get the apk from apkmirror.com and install it. It works just fine.
[Fire Original Android Development] nahtnam:
That is what I've done, and it is working fine. Since it's working fine, there is no reason the play store should block it.
[Fire Original Android Development] jratt:
Like others have said get it from apkmirror, I usually try to get the older version then upgrade it through play store.
[Fire Original Android Development] nahtnam:
See my post above.
[Fire Original Android Development] Dunard:
I have a question. How come I can't find apkmirror apk? :)
[Fire Original Android Development] fmc000:
apkmirror is a website, not an app.
[Fire Original Android Development] DB126:
Understand this is a long standing issue that is hardware and (custom) ROM independent although Amazon devices and Google properties seem to be more susceptible for whatever reason. Games and social media apps are also disproportionately impacted. Resolution resides with Google and obviously they have no desire to fix it. You can try various build.prop hacks but they generally introduce more headaches that offset any benefits. Sideloading from a trusted source is usually the best option.
[Fire Original Android Development] yochananmarqos:
Not yet, anyway. They're testing the app internally, no word on when it's coming. Until then, check out APKUpdater found here on XDA. It uses APK Mirror as one of it's sources.
[Fire Original Android Development] ogpog:
The app that I can't get to work on a CM or RR KFFOWI is Tesco Groceries UK. It shows up on Google play as "Your device is not compatible with this version". I can sideload the apk obtained from apkmirror or copied from another device where it is installed and working but as soon as I start it, it exits.
[Fire Original Android Development] DB126:
So it would seem the app is not compatible with this device. Contact the app developer if you are seeking resolution. Not a rom issue.
[Fire Original Android Development] DugRus:
Stuck at boot screen

I tried flashing CM 12.1 to my 5th Gen Amazon Fire (5.1.1) but I followed the instructions to upgrade using the steps below, instead of a fresh install.

Upgrading from FlashFire 0.50

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik and Cache.

- Press the big FLASH button.

Now tablet only boots to the fire load screen and stays there. When connecting the tablet to my Mac, it says No Android Device Found when plugged in to the computer when tablet is at Amazon system recovery.

What's my next step to fix this?
[Fire Original Android Development] GhostRider86:
Sideload FireOS 5.1.1, reroot and install cm with FlashFire
[Fire Original Android Development] DB126:
Actions as shown should not have yielded outcome even with a fresh install. Possible culprits:

- older version of FlashFire (<0.32)

- wiped system partition after flashing rom

- did not replace Kinguser with SuperSU prior to flashing CM

If you can still access stock recovery reload FireOS 5.1.1 to recover your device. Otherwise contact Amazon for a courtesy exchange if still under warranty.
[Fire Original Android Development] DugRus:
Next step?

That's where I'm getting stuck. Having issues sideloading with my Mac. Can't find a tutorial

---------- Post added at 03:16 PM ---------- Previous post was at 03:06 PM ----------

how do I access stock recovery?
[Fire Original Android Development] DB126:
http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Watch the video.
[Fire Original Android Development] rahul200023:
USB OTG Keyboard

Hi i flashed this rom in January, and have been very happy with it, I am planning on getting a micro usb keyboard case, and am wondering if it will work with this.

i cant post the link, because this is my first post, but the produc is called iRULU 7" PU Leather Micro USB Keyboard Case With Buttons Stand Cover for Tablet (Black) on amazon

the product says that the device should support usb otg, which it does, but i also read that this won't work with an Kindle's. However when i look in the comment section, someone people claim to say it works with the kindle. so will it work with this rom, bc ik this tab supports usb otg, i have used a mouse, and flash drive on it before
[Fire Original Android Development] legacymjr:
I have a different brand same thing works fine.
[Fire Original Android Development] rahul200023:
Sweet thx for letting me know, to clarify, you are using a micro usb keyboard case right, cause if it does i am going to buy it:):):)
[Fire Original Android Development] DB126:
Not ROM related; should be posted here:

http://xdaforums.com/amazon-fire/accessories

Given specs of both devices it should work but there are no guarantees.
[Fire Original Android Development] darkwind56139:
Hi, just went through the whole process of downgrading and rooting. I was on 5.1.3 and went to 5.1.2 Decided to install the nexus fire ROM. It's working good but now I want to try the cm ROM for comparison . what would be the easiest way to do this? Can I install cm directly from nexus using flashfire or do I have to recover to 5.1.2 again and repeat the process.
[Fire Original Android Development] GhostRider86:
If you have root access I would try the direct way with FlashFire to install CM and gapps.