yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Casti9l:
Cast Screen

Hi,

I have a problem with 22 nov version, cast screen interrupt immediately. It's normal with this version ?

Thanks !
[Fire Original Android Development] nirogu325:
Looks that way. Nexus ROM also cannot cast the screen/audio through Chromecast. I have a feeling we'll have to wait for the December update.
[Fire Original Android Development] jerz4lunch:
Installing SuperSU

Hello.

I am wondering how I should go about installing SuperSU and namely the SU executable. I forgot to install it when I flashed the tablet with FlashFire version 0.53.

I have a feeling that all I need to do is install it with a zip file containing it (using FlashFire), but I want to make sure, since I've already hard-bricked the first tablet that I attempted to root (doing this on a second one, obviously).

Oh, and by the way, the tablet is running a fresh install of the latest version of CyanogenMod along with Open GApps, per using this guide.

I appreciate any help on this matter.

PS: As I am new to this forum, should I have posted this on SuperSU's '[SUPPORT] Update failures' thread?
[Fire Original Android Development] GhostRider86:
Root is build in this ROM, see developer options, enable it, reboot. If you want to use SuperSU just install thru Play Store afterwards
[Fire Original Android Development] jerz4lunch:
Thanks for the quick reply.

I did do that, but I kept getting an error when trying to update the SU executable with the app. I used 'Normal Mode' if that makes any difference. Also, pressing reboot in the app doesn't seem to do anything. It almost looks as if my SU executable is non-existent at this point, as the app doesn't let me assume root privileges before attempting an update.
[Fire Original Android Development] leotakacs:
I tried this but my Fire just hung on the black FlashFire screen with the red FlashFire bar on top. FireOS 5.3.1.0/5.3.1 ROOTED (Using, well, this guide lol)

I'm currently restoring the 5.3.1 firmware to try again. Is there anything I can try to make sure it works this time?
[Fire Original Android Development] jerz4lunch:
Thanks. I didn't initially realize that I needed to enable it through developer options.
[Fire Original Android Development] hooks024:
I found that if you enable apps and adb root in developer options then supersu won't update. I set it for just apps, and it updated. Hope this helps.
[Fire Original Android Development] McguyverZero:
Hello all, first of all thank you for this amazing ROM of 12.1 for the Fire. I like many others I'm sure got my fire on black friday and hated the default so wanted a more android like UI.

The problem I'm currently running into and I apologise if it has been answered before; I have a 32GB SD card in the device and since I mainly got this to play games away from my phone I need to put the games onto my SD card as the internal storage is too small. MOST games/apps copy over fine, they range from sizes 10-445MB but there are a select few apps that refuse to move and throw me back the error "Couldn't move app. Not enough storage" but the apps in question are smaller than some of the others I've copies (This particular one is 168MB) Any ideas on getting around this?

Thanks in advance!
[Fire Original Android Development] GhostRider86:
Use Link2SD
[Fire Original Android Development] McguyverZero:
tried using this and it's still not working with the error: "pkg:/data/app/com.ravensburgerdigital.labyrinth.humble-1/base.apk Failure [INSTALL_FAILED_CONTAINER_ERROR]"

Is this because it's a game I installed from an APK gotten from the Humble bundle app thing? Other games from the same bundle have copied just fine.
[Fire Original Android Development] platypoid:
Did you make sure you put Wipe to the top of the Flashfire list ?
[Fire Original Android Development] DB126:
Can't answer your specific question (re: Humble bundle) but will advise Link2SD works best when the SD card is partitioned per FAQ which allows the use of symbolic links to relocated apps. A technical discussion is beyond the scope of this post; just know that symbolic linking allows virtually any app to be relocated. Link2SD handles the gory linking details; you just need to get the SD card format right. Post back if you need help creating a ext4 partition.

http://www.link2sd.info/faq
[Fire Original Android Development] ldeveraux:
There's a complex procedure involving formatting the sd in a certain way before using Link2SD. You need to figure that out before it will work properly
[Fire Original Android Development] Signor Rossi:
Why not use the build in feature?

Worked fine e.g. on Heartstone (~ 700 MB)
[Fire Original Android Development] McguyverZero:
Thank you both for all this information, done the second partition as EXT4 and it's linked and working perfectly thank you both so very much!
[Fire Original Android Development] DB126:
Long story short: the integrated app migration utility (Apps2SD¹) in most Lollipop based ROMs only works if app meets certain criteria *and* the developer has tagged the app as 'relocatable'. Symbolic linking works for almost any app and is completely transparent to the OS.

[¹] Android Apps2SD - not to be confused with the clever but unfortunately named Play Store app by the same name.
[Fire Original Android Development] leotakacs:
Yup, I did. However it worked the second try after I

1) Made sure Auto-Mount was checked for both CM12 and gAPPS zip files

2) Added Cache to the wipe list
[Fire Original Android Development] melvinaury:
Hi, I install the ROM and it's working perfect. I just notice two things one if you go to settings, about tablet the model name are KFFOWI and second I'm almost out of storage and I buy a 16GB SD card, but when I insert the card I don't had the option to link the card to the internal storage. On my other tablet when I insert the sdcard it ask how you want to use card, as part of internal storage or as an external storage.
[Fire Original Android Development] Doggy77:
The model name IS in fact KFFOWI: Kindle Fire ford wifi. Ford is the codename for this tablet from the kindle fire series. And it is the Wifi only model. (and no, there is no other model at the moment, so this addition is a bit useless. But we never know what may come from Amazon and Amazon chose this naming scheme).

The linking to the internal storage is not possible wih this rom (this function was added with Android 6, which we do not have here). And also no, there is no possibility to get a higher Android version. This is valid as long as Amazon does got give away a possibility to unlock the bootloader and therefore change the underlying linux kernel version.

I am using the SD card with a EXT4 partition and "link2SD"-App. This is the best option in my opinion for dealing with short memory issues.

Greets,

Doggy
[Fire Original Android Development] melvinaury:
Thanks for the information in fact my other tablet are running version 6.0.1...
[Fire Original Android Development] DB126:
- model name (KFFOWI) is correct for this device

- your "other tablet" is likely running a higher version of Android (Marshmallow or Nuagat) or a different rom that supports 'adoptable storage'

- you will need to use a tool like Link2SD that utilizes symbolic links to migrate apps to the SD card with CM 12.1 or any other custom ROM for this device
[Fire Original Android Development] yochananmarqos:
That's because KFFOWI is the model. Adopted storage is a Marshmallow feature.
[Fire Original Android Development] geoffobat:
Hello all, thank you for this amazing ROM.

I have one quick question.

I downgraded from 5.1.3 to 5.1.2 in order to root as per this guide.

Now I have installed CM 12.1, I'm wondering what version I need to flash back to in order to revert to original stock ROM.

The latest update says that CM 12.1 has been updated to FireOs 5.3.1 - does that mean that FireOs is still on the device somewhere in the background, and it was updated to 5.3.1 behind the scenes by flashing CM?

To flash back to stock, should I use 5.1.2, or 5.3.1? I don't want to try and flash 5.1.2 if I'm now on 5.3.1 in case I brick the device.

Thanks in advance!

Geoff
[Fire Original Android Development] DB126:
re: "does that mean that FireOs is still on the device somewhere in the background"?

Yes and no - but the details are unimportant. To restore FireOS sideload the same (or higher) version of FireOS that was on the the device just prior to flashing a custom ROM. Never attempt to sideload a lower version unless explicitly advised to do so by an experienced XDA contributor.

All FireOS restorations should take place via the stock recovery menu. Never attempt to flash FireOS using a 3rd party tool like FlashFire or TWRP.
[Fire Original Android Development] geoffobat:
OK great that's what I thought.

So what's the significance of this in the changelog?

- Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img

Does that mean the boot image is from 5.3.2 but it's still OK to flash back to my original 5.1.2? And is there any way to tell what my stock version was before updating?

Cheers

Geoff
[Fire Original Android Development] TheLoonyRebel:
Is anyone having issues with Skype on the November 22nd build? My girlfriend logged in and once she gets to the screen with her user names it kicks her out and won't let her back in.
[Fire Original Android Development] sandman512:
Quick question, I'm running the latest build and my device seems a little sluggish. Any advice? Thanks
[Fire Original Android Development] DB126:
References bootloader/kernel components which are primarily of interest to developers and disturbed techies with a few loose screws... (I resemble that characterization).

Safe to restore whatever version of FireOS was last on your device. If unsure go for the most recent rootable version, currently 5.3.1. Never attempt a rollback to an earlier version of FireOS unless advised by an experienced XDA contributor or reputable thread. Outcome could be a brick.

There is no way to directly query bootloader/kernel version or the version of FireOS that was last installed on the device.
[Fire Original Android Development] steve8x8:
There may be, at least for the bootloader. (The kernel gets overwritten by boot.img of the custom ROM - which for Nov 22 CM-12.1 and Nov 24 Nexus is the one of stock 5.3.2.0, no cigar.)

But there's images/preloader{,_prod}.img.

The preloader_prod.img file (used for "secure", i.o.w. the majority of our devices, while preloader.img is being used for some (exotic? pre-prod) boards) gets flashed to /dev/block/platform/mtk-msdc.0/mmcblk0boot0 - why don't they use /dev/block/platform/mtk-msdc.0/by-name/something like anywhere else??? - I should have a look into /proc/mtd now, but ... the device is at home ...

Re exotic boards: What does /proc/idme/board_id "typically" contain? (& is there more info in /proc/idme we might make use of?) Have they ever been sold to the public?

Edit: I went ahead and piped the preloader images available through "strings -8 | grep 201.....-......" (looking for a build timestamp), resulting in this list:

fireOS-5.1.1/images/preloader_prod.img: 20150923-180133
fireOS-5.1.1/images/preloader.img: 20151202-052945
fireOS-5.1.2/images/preloader_prod.img: 20160120-094719
fireOS-5.1.4/images/preloader_prod.img: 20160217-183554
fireOS-5.1.2/images/preloader.img: 20160227-021828
fireOS-5.1.4/images/preloader.img: 20160506-045524
fireOS-5.3.1.0/images/preloader_prod.img: 20160603-023745
fireOS-5.3.2.0/images/preloader_prod.img: 20160603-023745
fireOS-5.3.1.0/images/preloader.img: 20160624-191357
fireOS-5.3.2.1/images/preloader_prod.img: 20161102-031807
fireOS-5.3.2.0/images/preloader.img: 20161104-214024
fireOS-5.3.2.1/images/preloader.img: 20161201-113631

(5.0.1 values are available too now. I'll add them later.)

Note that 5.3.1.0 and 5.3.2.0 (secure device) cannot be distinguished by this method, and it doesn't provide a means to identify possible downgrade paths (which would include LK and perhaps more).

Now we've got to identify the partition the preloader is written to (in /dev/block/platform/*/by-name/) read /dev/block/mmcblk0boot0, and provide a small shell script that can be run from the sdcard (as root, of course) mapping the build stamp to the fireOS version it belonged to...
[Fire Original Android Development] ggow:
[MENTION=7104332]k4y0z[/MENTION]

1. EDIT: I'll have a look at exFAT requirements

2. Maybe we could build this as a module: https://github.com/dorimanx/exfat-nofuse
[Fire Original Android Development] archerymodz:
Thanks ggow for the steady updates/fixes. Have you considered becoming an official maintainer for cm on this device?
[Fire Original Android Development] ggow:
- Yes I'm looking at the requirements for this at the moment

- I'll speak to the guys there next week and figure out what needs to be done
[Fire Original Android Development] Webern:
A couple of quirks:

1) I can't figure out the location settings. It seems to show where I am but doesn't track me when i move (by train or on foot). And when I press the location button in google maps it keeps asking me to improve location accuracy, and I keep saying yes. Perhaps it's just slow. It's not doing the big radius of uncertainty around me that it would if there wasn't a gps lock. It's hard to find a lot of detail on this tablet between when you search for `amazon fire 7 2015" you get a millions hits for the HD/HDX etc, so i'm not even sure that it's got a gps!

2) Am I alone in having trouble with Google Play Games? If you install the free Zen Pinball game, for example, it'll try and install it, taking you to the play store, but it repeatedly fails with error -505 (Can't install app. "Google play games" can't be installed. Try again, and if the problem continues, get help troublesheeting).
[Fire Original Android Development] pjsockett:
I haven't tried it, but others have said it's only an issue with the play store version and if you try to install from apkmirror it works
[Fire Original Android Development] ilfred019845:
1) I can't figure out the location settings. It seems to show where I am but doesn't track me when i move (by train or on foot). And when I press the location button in google maps it keeps asking me to improve location accuracy, and I keep saying yes. Perhaps it's just slow. It's not doing the big radius of uncertainty around me that it would if there wasn't a gps lock. It's hard to find a lot of detail on this tablet between when you search for `amazon fire 7 2015" you get a millions hits for the HD/HDX etc, so i'm not even sure that it's got a gps!

2) Am I alone in having trouble with Google Play Games? If you install the free Zen Pinball game, for example, it'll try and install it, taking you to the play store, but it repeatedly fails with error -505 (Can't install app. "Google play games" can't be installed. Try again, and if the problem continues, get help troublesheeting).[/QUOTE]

This device does not contain GPS hardware.

Try installing "Google Now". i had some issues with the play store and some apps and after installing it everything started working.
[Fire Original Android Development] ggow:
- The tablet has no GPS

- And yes install an old version from apkmirror then update to the latest from play store
[Fire Original Android Development] spicypixel:
Anyone noticing the brightness being static regardless of settings?
[Fire Original Android Development] ilfred019845:
Go to settings > Display and Lights > Live Display > Display Mode and set it to Automatic and that should allow you to adjust brightness.
[Fire Original Android Development] xm41907:
As the others have said, it has no GPS capabilities. Yesterday I played with GPS tethering apps and had minor success. I could link my phone to the Fire, and Google Maps would show my correct location, but It wouldn't navigate with it. The same was true with Waze. This is true with stock, CM, and SlimLP so it must be inherent to the device or something with the apps. I'm looking for a solution so I can use it for navigation.
[Fire Original Android Development] k4y0z:
OK, so I have been looking into exfat myself.

As it turns out all necessary tools are already in the rom, there should be no need for an extra kernel-module.

mounting an exfat storage by hand using mount.exfat works as expected. It is however not mounted automatically.

It seems this is caused by the following line in /fstab.mt8127 which explicitly uses "vfat":

/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto,noemulatedsd

I believe if configured with "fuse-exfat" or "exfat" (maybe something like "auto" would work as well) exfat storage should be mounted automatically although I'm not sure that this won't break vfat-support.

Since as far as I understand this is all done in the initramfs (which we can't modify currently) this begs the question:

Did exfat ever work on stock?!
[Fire Original Android Development] swicago:
Quick question. In order to update a current install of CM12.1 to the latest revision, I just flash over it right? I don't have to do any wipes?

Thanks
[Fire Original Android Development] spicypixel:
Didn't work :(
[Fire Original Android Development] ggow:
- I never used the stock rom so perhaps someone else can chime in whether or not exfat works in stock or not.

- If it does then I'm sure we'll find a way to make it work here
[Fire Original Android Development] ggow:
- No wipe required

- Just flash the rom and SuperSU

- Then reboot
[Fire Original Android Development] swicago:
Thanks, that's what I thought....just wanted to be sure, since some of my other custom rom devices tend to require partial wipe in order to upgrade
[Fire Original Android Development] ilfred019845:
Which version are you on?

I am on 20151204 and it works.

I even set display mode back to none and it still works.
[Fire Original Android Development] swicago:
I know exFAT does not work on STOCK fireTV, so I would assume it will not work on STock Fire Tablet, since they are based on same FireOS
[Fire Original Android Development] k4y0z:
Doing something like this during bootup, should get it working:

/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&
[Fire Original Android Development] sam tyler:
Just installed latest update, otg works. es file manager and cm file manager both detect my flash drives. only the ROMs video player won't play my external drive. on mx player I can only use hw and not hw+. I note from some posts to look in developer options and look at hw overlays and Awesome player.great update. many thanks.
[Fire Original Android Development] steve8x8:
I'm in doubt this would perfectly fit in here (rather than one of the numerous bootloader analysis or unbrick threads). Dear demigods. please feel free to move it.

Here's my first take at a script to find which has been the last FireOS version installed on the Ford tablet (by retrieving the build date from the preloader partition):

iam=`whoami 2>&1 | tr -dc '[0-9]'`
if [ $iam -ne 0 ]
then
echo must be root
exit 1
fi
bld=`strings -n 12 /dev/block/mmcblk0boot0 | grep 201.....-......`
echo build stamp: $bld
case $bld in
20150730-164940)
echo fireOS 5.0.1 secure
;;
20150923-180133)
echo fireOS 5.1.1 secure
;;
20150930-051243)
echo fireOS-5.0.1 unsecure
;;
20151202-052945)
echo fireOS-5.1.1 unsecure
;;
20160120-094719)
echo fireOS-5.1.2 secure
;;
20160217-183554)
echo fireOS-5.1.4 secure
;;
20160227-021828)
echo fireOS-5.1.2 unsecure
;;
20160506-045524)
echo fireOS-5.1.4 unsecure
;;
20160603-023745)
echo fireOS-5.3.1.0 or fireOS-5.3.2.0 secure
;;
20160624-191357)
echo fireOS-5.3.1.0 unsecure
;;
20161102-031807)
echo fireOS-5.3.2.1 secure
;;
20161104-214024)
echo fireOS-5.3.2.0 unsecure
;;
20161201-113631)
echo fireOS-5.3.2.1 unsecure
;;
*)
echo unknown build date, please report your fireOS version
;;
esac

Incomplete and untested yet. Will only run as root (e.g. from /sdcard).

If you get the "unknown" message, share your result and ROM version. If you think the output is inconsistent with your Fire's history, do the same.

Note that not all build dates will show up as it takes root to extract the info. Probably we'll only see 5.0.1, 5.1.1, 5.1.2 and 5.3.1 secure.

Edit: Running this on my old Fire (which I rooted a year ago) went fine, but I had forgotten in the meantime that I made some additions, including a newer version of Busybox which came with a bunch of symlinks.

With the new 5.3.1.0 device, I had to prefix most of the Unix commands in the script with "busybox" that wouldn't be available otherwise.

I'll commit the new version once I've ironed out all quirks. Sorry for the noise...
[Fire Original Android Development] melvinaury:
The ROM is working perfect, but the only problem is that I can't , install play games app. I continue receiving error code 505. I try all the solution, restart, clear data of play store, uninstalling all the updates of play store, clearing dalvik and cache partition... For the moment I will sideload the app..

Update:. I download from apk mirror and install successful, then go to play store and update to latest version without problem....
[Fire Original Android Development] DB126:
Known issue. Sideloading is the recommended solution for -505 errors.
[Fire Original Android Development] ipdev:
Post moved.

Wrong thread.
[Fire Original Android Development] kyledowling:
Use apkmirror to sideload it. Known issue
[Fire Original Android Development] fabu09:
I've been reading the later parts of this thread and still cant seem to solve my root issue. I'm new to this so bare with me guys, i did everything exactly and have cyangenmod running on my device and even enabled root access to apps and adb but when i use root checker it says "SORRY! Root access is not properly installed on this device". Based on what someone said earlier i tried just enabling to apps only and still nothing. I'm trying to update the binary with SuperSU but it always ends with a failed to install error.

I've tried turn off root and reboot and back on and reboot again and still i don't seem to have full root access on my device, i have no idea what i'm doing wrong and growing frustrated with it, would appreciate it if someone could assist me.

NOTE: even when i have root access to disabled, root checker give the same error instead of saying no root, not sure if that makes any difference
[Fire Original Android Development] zeusminos:
There is a post in this thread that talks about someone with similar issue. The root access has to be turn on. There is an option on settings -》developer menu that will allow you to do that
[Fire Original Android Development] fabu09:
Yes i am aware, and i have turned it on but it still doesn't seem like i have root access because root checker doesn't say i am rooted. Trying to root with kingroot and also run into a failed to root issue, i seriously don't know what else to do..
[Fire Original Android Development] zeusminos:
I am using the latest CM 12.1 image and root access is there. No additional changes are required
[Fire Original Android Development] fabu09:
Yea, I think i may have done something wrong or didn't do something when flashing, I followed this guide:

http://www.overclockers.com/forums/...od-12-1-Android-5-1-1-on-Amazon-Fire-7-Tablet

when flashing this rom. Hopefully someone else can help me out here
[Fire Original Android Development] hooks024:
Did you set just apps or apps and adb? I had the same problem, and found that only one of them will allow you to update the supersu binary, but I forget which one. It's been a while since I did it, so you'll have to forgive me for that.
[Fire Original Android Development] zeusminos:
Apps only is the right way
[Fire Original Android Development] fabu09:
I did try both, just apps only & apps and adb with reboots when i change options each time but non seem to work at all. Only one i didn't try is adb only, don't think that's it but i will try that anyways. I also got Super SU from the Playstore, am i wrong in using that version?
[Fire Original Android Development] zeusminos:
Once you set apps only. Update superSu (pay few bucks and support the community ). Once you have superSu may tell you that you need to update some binaries go ahead and say yes