yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] blueberry.sky:
FAQ suggestion

FAQ suggestion, something along the lines of

Screen seems stretched or distorted.

The actual pixels in the Fire's LCD are not perfectly square, that causes some distortion. It is particularly noticeable with round icons & when the screen rotates.

This issue also effects the stock amazon OS as well as all custom roms. It is not yet known if this will be fixable. See this thread for more information.
[Fire Original Android Development] EncryptedCurse:
Fantastic work, [MENTION=5749760]ggow[/MENTION]. This works buttery smooth on a $35 tablet.
[Fire Original Android Development] nujak:
First off, [MENTION=5749760]ggow[/MENTION] Thanks for the ROM and continued development. You rock!

Just some FYI on my installs in case any of the information is useful:

1.) 12/02 ROM Clean Install with 12/03 Nano Gapps, no app compatibility issues

2.) 12/11 ROM Dirty Install from using FlashFire (ROM only), app compatibility issues

3.) 12/11 Clean Install with 12/03 Nano Gapps, app compatibility issues

Gapps on 12/02 ROM were fully updated to Play Store 6.0.5 and Play Services 8.4.89 and no compatibility issues. [Used this build from 12/03/15 to 12/13/15]

Dirty "Upgrade" to 12/11 ROM experienced a few "Play Services" errors during initial setup (most likely due to the Google Sign-in as the errors stopped once I skipped it). Play Store opened fine, but the UI was different then the current UI and the banner wouldn't load. Shazam and United app shown as not compatible. After a restart, the Play Store UI was the current one and the banner displayed/worked properly, but apps still not compatible.

Clean Install to 12/11 ROM using same 12/03 Gapps had no "Play Services" errors, but the same UI issues until restart. Shazam and United incompatible before and after restart.

In all cases, Settings>Apps reported Play Store 6.0.5 and Play Services 8.4.89

App issues are no biggie for me, I'll just sideload whatever doesn't download (mostly just trying out "incompatible" apps from posts to see if I had the same issues). Thanks again for all your hard work [MENTION=5749760]ggow[/MENTION].
[Fire Original Android Development] TheHunterOfShadows:
That would help, but when i see someone ask a question that was answered a few posts above, its sad.

But this isn't 'broken' the fire isn't an official Google android device. Its a fire os device, so its no surprise many apps show not compatible.

I agree that reading every post is not gonna happen, but can people read the last two or three pages? Is that too much to ask for something given to you for free?
[Fire Original Android Development] ldeveraux:
Rather than that, it's suggested to use the search function.
[Fire Original Android Development] Webern:
As you can see from pretty much every thread in every forum on this site, it would appear to be too much to ask, hence my suggestion.
[Fire Original Android Development] TheHunterOfShadows:
Lmao, fair enough, you win :)
[Fire Original Android Development] DB126:
By all means start a FAQ thread on your own, spend countless hours maintaining it and then face withering criticism from thoughtless posters when it is somehow imperfect in their expert judgement. Oh wait, someone else should be doing that. Silly me.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 16 Dec 2015

- Change log on Post #2
[Fire Original Android Development] Webern:
If that was aimed at me then I'm confused; I'm not criticising anything, just suggesting something which may reduce the number of posts asking the same questions.
[Fire Original Android Development] csolanol:
We have been playing with SurfaceFlinger and panel orientation settings but couldn't fix screen off animation completely. When we fixed it we broke camera and apps rotation lol.

Awesome work Joel!
[Fire Original Android Development] :
Just flashed this baby and it's awesome! [MENTION=5749760]ggow[/MENTION] - you rock! Really made this cheap tablet into a premium device!
[Fire Original Android Development] DB126:
Fair enough - perhaps I misinterpreted your tone (and maybe a bit jaded from being on the other side of the fence).
[Fire Original Android Development] Sulinjr:
[MENTION=5749760]ggow[/MENTION] We'll have to start referring to you as "Master ggow", bout to drop the pain onto this tablet! Darth Amazon can't even handle. Haha
[Fire Original Android Development] mojoehand:
I thought I'd test USB OTG with the 11 Dec build. A USB 3 flash drive works. A USB mouse works. A USB keyboard is detected, but I get no characters when I type.
[Fire Original Android Development] kramalot:
For those who want apps more than me, as far as I can see with today's ROM + today's open gapps everything that was unobtainable from play store is now fine!

[MENTION=5749760]ggow[/MENTION] = genius! Best ROM ever and a really usable Amazon Fire now worth x times more than we paid for it.

Now, while I know its probably a kernal problem and thus not something that you can fix, is there anything (some work around/kludge) that might overcome the problem of the sdcard becoming unmounted or invalid or whatever when a USB device is removed? Am I the only one suffering with this? At the moment every time I remove a USB drive I have to remove and reinsert the SD card before SD card apps come back.
[Fire Original Android Development] k4y0z:
Is it an ExFAT SD-Card? If so, could you test if that also happens with a FAT SD-Card?
[Fire Original Android Development] kramalot:
No, its just a FAT32 card. Don't have a bigger one. And the same thing happens on my other L device and my KK 4.4.2 device, hence my assumption that its a kernel/Google hatred of SD card problem. Just hoping a fiddle might be possible.

Btw, re: my last assertion about play store, I was wrong. Apps are still incompatible. I swear when I first booted the problem apps were OK, 30 mins later - not OK. Weird. And before anyone jumps on me shouting "apkmirror" I'm not checking because I want to install anything, I'm just testing for completeness sake.
[Fire Original Android Development] monza1412:
Enjoying the latest release, bug free in all my applications, awesome job. Thank you
[Fire Original Android Development] manywelps:
If you told the GPU or whatever's handling the framebuffer that the physical screen size was different, and let it correct, I would think you would be able to force it to correct.

(Mind you I don't know how Android's graphics system works specifically)
[Fire Original Android Development] BoulderGeek:
Woo, hoo!

Dirty flash of 12/16 over 12/11 and everything seems to work great!

Thanks so much for your efforts, ggow!
[Fire Original Android Development] mmurphmsu:
I dirty flashed latest build over 12/11, flashed the gapps I had, then SuperSU and when I rebooted, my tablet looked like I had not installed any apps. Nova launcher wasn't installed and none of my apps were in my app drawer. I have most of my apps on my SD card to free up space. Any idea why that would have happened?
[Fire Original Android Development] hammer-is:
I also did the upgrade from 12/11 to 12/16 as a dirty flash yesterday, but did not loose anything. I'm using stock launcher but I don't see why that should matter. I only flashed the CM file. I'm using opengapps (micro) and there is no need to reflash that. The gapps gets backed up and restored automatically using a script installed by opengapps package. I'm also using the "built-in" root that can be enabled under "developer options" as I don't see the advantage of installing SuperSU.
[Fire Original Android Development] fmc000:
Upgraded this morning from Dec 10 AM release to 16 Dec, dirty flash, along with OpenGapps Pico and SuperSU 2.46 . All OK with Nova Launcher in use.
[Fire Original Android Development] mys7:
dirty flash with FlashFire... smooth as silk

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

just for information, maybe you did because you wanted to do, but reflashing gapps is not needed nor SuperSU is needed anymore :)
[Fire Original Android Development] mastakila:
Thanks again ggow amazing work!

One issue...

I did a clean installation (wiped all system partitions) of 12/16 ROM and noticed that backlight brightness adjustment doesn't work. Is it just me or has anyone else experienced it? I'm sure this worked before...

EDIT:

OK, it looks like I need to flash the ROM again, I will try it when I get back home.
[Fire Original Android Development] ggow:
Fix for screen off animation

[MENTION=2511007]csolanol[/MENTION], [MENTION=4375260]diegocr[/MENTION] and [MENTION=369083]cbolumar[/MENTION]

- I have uploaded the fix to cyanogen's gerrit here:

- http://review.cyanogenmod.org/#/c/124798/2
[Fire Original Android Development] csolanol:
Ty very much!!!
[Fire Original Android Development] fmc000:
Reflashing gapps is needed if you want to update them to a newer version and I bought SuperSU pro years ago so I keep flashing it.
[Fire Original Android Development] monza1412:
Quick question, what DPI settings are you using? I saw 160 as default, but I'm trying to find something less blurry
[Fire Original Android Development] mmurphmsu:
I wonder if my issue was because I used the app in the Play Store Link2SD to move my apps to my SD card? That's the only thing I can think of. I dirty flash ROM's on my OnePlus One all the time and that don't happen.
[Fire Original Android Development] cbolumar:
Thank's . :good:
[Fire Original Android Development] :
Using 200 and it looks good to me.
[Fire Original Android Development] bigpapa007:
hello, i got a question and i'd appreciate if someone can answer it please.

I'll be getting my tablet this saturday, so i want to know if once i get it i should let it update by itself before doing everything on here or should i NOT update it?
[Fire Original Android Development] jgore43:
I would not allow it to update, the latest update removes the functionality that allows us to use custom recoveries, like TWRP.
[Fire Original Android Development] dueltothedeath:
No.. Don't turn on WiFi. Skip all the steps, and turn adb on in developer settings. Any custom ROM is 10 times better then the fires stock OS.
[Fire Original Android Development] bigpapa007:
So there is no need for me to update anything at all before doing the steps on here? i just turn it on, not connect to wifi and just start flashing right away?
[Fire Original Android Development] ggow:
- In fact don't even boot fire os

- Get straight into fastboot and start flashing
[Fire Original Android Development] 30br:
That's what I did. I'm not real experienced, and after I wiped data I realized I didn't have my images on the tablet. I figured out to use ADB push to get them on the tablet. All was easy, even with the hiccup it onlt took about 20 minutes. Without the hiccup it's probably less than 10.
[Fire Original Android Development] pbailey212:
I haven't used limk2sd in a while, but there should be an option to recreate links, then you reboot and your apps should be back
[Fire Original Android Development] rogersa2k:
fastboot

Silly question, how do you do that? Power + ???

Thanks,

Aaron
[Fire Original Android Development] ggow:
Hold volume up and then power on
[Fire Original Android Development] mastakila:
FAQ suggestion

Question:

Why my brightness slider isn't working

Answer:

Try installing Brightness Level and use it to change brightness. After doing this brightness slider should work fine and you can remove Brightness Level.
[Fire Original Android Development] BoulderGeek:
Wow, 200DPI looks so much better!

My enthusiasm for this tablet just went way up, with the 12/16 version of CM12 and readjusting the DPI. Not nearly and funky and blurry. It was like a dirty window, before.

Launcher rotation seems to have stopped working when I went to 200DPI. Does anyone else auto-rotate in Google Now launcher @ 200DPI?

My brightness slider works, though. So, i have that going for me, which is nice.
[Fire Original Android Development] kpdeepu:
If we dont even boot fire os, how to enable USB debugging?
[Fire Original Android Development] ggow:
- When in fastboot - why do you need to worry about enabling USB debugging?

- You should have adb access through the fast booted recovery
[Fire Original Android Development] ggow:
- I have also noticed that on several devices, changing the DPI causes auto rotation to stop working

- Will look into that when I have time.
[Fire Original Android Development] kpdeepu:
Oh thank you, I was not aware. So does this mean I can enter fastboot mode on a new Fire tablet and can launch TWRP directly via ADB command?

Also one more question, sorry if I am dumb.. Without ever booting into fire OS, how can I transfer the flashable CM ROM zip to the device? thank you.
[Fire Original Android Development] mmurphmsu:
Thanks!! I have really looked into the app much but will now. I really appreciate it.
[Fire Original Android Development] ggow:
Follow the instructions on this thread to boot into recovery

- http://xdaforums.com/amazon-fire/orig-development/twrp-recovery-t3242548

- Once booted into recovery use the following to send files to the device:

adb push <filename> /sdcard/
[Fire Original Android Development] kpdeepu:
Thank you!!
[Fire Original Android Development] Pond-life:
as well as the adb way there is the options of sd card and usb otg. If nothing else an SD card is very useful for backups before switching roms.
[Fire Original Android Development] howzitnow:
Is there a way to verify if it's. 5.0.1 or 5.1.1 without booting first?
[Fire Original Android Development] k4y0z:
With the newest TWRP we can also use adb sideload.

If "fastboot boot" doesn't work it's probably 5.1.1
[Fire Original Android Development] randomblame:
can someone pull a freshly flashed cm12 system.img for me? got a neutered fastboot and an idea
[Fire Original Android Development] alcuin:
I don't think that is a bug. Google now launcher doesn't rotate on phonrs. I think at that high dpi, google now launcher thinks its a phone. I use adaptive rotation lock to force auto rotation.
[Fire Original Android Development] jbraney:
CM12, or CM12.1? It should make a difference...
[Fire Original Android Development] randomblame:
hehe 12.1 please
[Fire Original Android Development] jbraney:
Sorry, I don't have it, just thought it would be more helpful to you and by extension to us if it was clarified! :P
[Fire Original Android Development] randomblame:
thanks for your valuable contribution

OK so nevermind I got slim installed through flashfire no fastboot needed. for some reason cm12.1 does not work out with this method. So if anyone wants a custom rom with 5.1.1 this is how to do it.
[Fire Original Android Development] nujak:
Well, apparently I was too late! Unable to get 12/16 Gapps, so I Dirty flashed and clean flashed 12/16 ROM today using 12/17 Nano Gapps and 12/18 Nano Gapps, but same few apps are still showing "not compatible". Doesn't really effect the apps I use, but just thought I'd share my experience. Don't forget, if you have "not compatible with your device" just sideload from apkmirror.
[Fire Original Android Development] monza1412:
Thanks, after trying a few values I set it in 213ppi, icons/text seems sharper. Give it a try :thumbup:
[Fire Original Android Development] DavidNL:
I had xposed running on the last version of this rom...but can't get it going with this one. Reflashed it, even tried a newer version of xposed. has this happened to anyone else?
[Fire Original Android Development] pbailey212:
I just downloaded link2sd to confirm. It's "recreate mount scripts" you will want to do, to get your apps back
[Fire Original Android Development] mmurphmsu:
Thank you again, I really do appreciate it.
[Fire Original Android Development] DavidNL:
Solution found : uninstall then reinstall the xposed installer apk.
[Fire Original Android Development] ggow:
- Thanks :)

- Added
[Fire Original Android Development] ggow:
- Added - thanks
[Fire Original Android Development] :
How do you do that? I only see 160, 180, 200, etc as options in set dpi menu.
[Fire Original Android Development] stultus2:
I'm getting Trebuchet launcher crashing when screen rotates. Think it may be related to using the cLock widget.
[Fire Original Android Development] monza1412:
If you're rooted, go to the system folder and edit the build.prop file.

The ro.sf.lcd_density line to the desired value (let's say 173) save, reboot, and then select the DPI in the set dpi menu.
[Fire Original Android Development] Kaffeekranz:
Nice work, OP!

Is there a way to get more kernel config options, including overclocking?

Right now I get hard reboots a few seconds after switching to interactive governor for example.
[Fire Original Android Development] DB126:
Try Kernel Adiutor (spelled correctly!). Good tool if you know what you are doing; somewhat dangerous if you don't :)
[Fire Original Android Development] Kaffeekranz:
That is what I'm using, but the Fire doesn't seem to like interactive.
[Fire Original Android Development] DB126:
Yep - governors are SoC/firmware dependent. Every device I own has at least one cpu/gpu governor or scheduler that it doesn't like despite being listed in the drop down. Ashame interactive isn't supported. Guessing ondemand is the default?
[Fire Original Android Development] Larz2.2:
Any hope the USB>charge only bug will get fixed? Everything else about this rom is great!
[Fire Original Android Development] manywelps:
I think it's hotplug for slimlp. Would ondemand turn off unused cores?
[Fire Original Android Development] DB126:
Hotplug is not a bad choice (if it works) given the device characteristics. Lots of tools for monitoring cpu activity if you want to experiment. Governor optimization is highly device and load dependent. In most cases you are not going to see a huge difference but results are observable under the right conditions.
[Fire Original Android Development] duanim:
about youtube video the resolution set is 380 and i am using og youtube i has to do manual change to 1080p even set in settings to 1080, so there is a way to set the resolution to 1080p default in the device.

again this $35 device is amazing thanks ggow
[Fire Original Android Development] Pond-life:
Confused as to why you'd set it to 1080p when the screen can't display that.
[Fire Original Android Development] duanim:
in OG Youtube you can set manual the resolution to 1080p it looks good,but i dont know if the device support it,but i think the device in streaming video support high resolution
[Fire Original Android Development] Ownster:
Probably because downscaling makes it look better.

480p(640x480) stretched to 1024x600 doesn't look the greatest where as 720p it would look better.
[Fire Original Android Development] Pond-life:
The Fire only has a 1024 x 600 screen so you aren't going to magically see 1920 x 1080 just by running a 1080p video.
[Fire Original Android Development] KevOne:
Computer can't see External SD when plugged in via USB?

Hi guys,

Does anyone have this problem? I want to transfer files to my tablet but it only shows the internal storage and not the external storage. It showed both before when I was on the stock rooted rom. (I can always eject the micro sd card and transfer files through an sd card reader, but using the usb cable is more convenient :p) Other than that, this CM12 rom is perfect. Everything is smooth and the app store works perfectly.

p.s.,

Just to clarify, ES File Explorer can see all my files in the external sd card, and I can also listen to my music on it with Power Amp
[Fire Original Android Development] Pond-life:
Edit. Mine does that when I connect it as Camera PTP rather than Media Device MTP, don't suppose it's that? Don't switch it to charge only or it gets stuck iirc.

Can you adb push to the external sd? Or is that non functional too?

adb push filename.xxx /storage/sdcard1

or

adb push directoryname /storage/sdcard1

Not perfect solution but saves fiddling with sd card readers
[Fire Original Android Development] KevOne:
So I pushed a test.txt to my downloads folder by typing: "adb push test.txt /storage/sdcard1/downloads" and it looks like it successfully transferred it. It works, but I would hate to do that for 50+ files hehe

I also successfully pulled it by typing: "adb pull /storage/sdcard1/downloads/test.txt"
[Fire Original Android Development] Pond-life:
Put them in a folder and push the folder :D
[Fire Original Android Development] KevOne:
hehe that's also a good way to do it :laugh:

Thanks!

---------- Post added at 10:52 PM ---------- Previous post was at 10:41 PM ----------

Okay, I don't know why, but it finally recognized both internal storage and external storage after I restarted my computer :confused: maybe that adb push/pull did the trick. Anyway, thanks for your help! :good:
[Fire Original Android Development] paltieldav:
Adding CM to 5.1.1

Can we add CM to a rooted Fire with 5.1.1 on it?

Thanks
[Fire Original Android Development] Dr.TheMaster:
Not for now..

Kindly press thanks if I helped :)
[Fire Original Android Development] andPS2:
just got myself this device after the hdx mysteriously failed and who do i see here

doing the good work again? its [MENTION=5749760]ggow[/MENTION] the master! ;)

thanks for another excellent rom!

one tech question: how was this possible to install cm when the bootloader is locked? (like

didnt we need specific bootloader partial then later full unlock on the hdx?)

how come here we could just fastboot boot recovery.image did amazon just forgot that on 5.0.1?
[Fire Original Android Development] ggow:
- Basically Amazon left CVE-2014-4325 open.

- This enables fastboot boot to work

- And plus FireOS 5 enabled lollipop type ROMs to boot
[Fire Original Android Development] exiva:
Is the audio corrupted and garbled for anyone else on Two Dots? Using the latest build.
[Fire Original Android Development] jdeandeck:
Sorry to jump in but im pretty sure you can adb push file/directory dest/directory.... Sorry didnt see already answered
[Fire Original Android Development] clapper66:
This tablet plus cm12.1 is awesome. I just did a geek bench 3 battery test and got 9 hours and 6 mims ;)
[Fire Original Android Development] Sulinjr:
Not bad for $35 Tablet.
[Fire Original Android Development] k4y0z:
[MENTION=5749760]ggow[/MENTION]

I've been looking into what prevents CM being installed through FlashFire.

I think the problem is the otasigcheck in the updater-script (lines 9-17).

I believe FlashFire doesn't completely wipe data.

Maybe you could add a check for the existence of a specific file and skip the signature verification if it is present.

Since FlashFire is currently the only way to install a custom ROM on 5.1.1, you would probably make many people happy ;)

EDIT:

just saw that the otasigcheck.sh does this:

grep -q "Command:.*\"--wipe\_data\"" /tmp/recovery.log
if [ $? -eq 0 ]; then
echo "Data will be wiped after install; skipping signature check..."
exit 0
fi

Maybe we can just create /tmp/recovery.log with:

Command: "--wipe_data"

EDIT2:

/tmp/recovery.log doesn't seem to work.
[Fire Original Android Development] gad42000:
Im currently on 5.0.0. Is it better to change it to 501 or 511 before installing cm 12 or it doesn't matter?
[Fire Original Android Development] fmc000:
If you let your device update to 5.1.1 you won't be able to install CM12.1 on it, so be careful.
[Fire Original Android Development] andPS2:
thanks Sir!

oopsie daisy that exploit was from 08/24/2014

and one year later when fire 2015 came out amazon forgot to check

well good for us ... ;)
[Fire Original Android Development] ggow:
- They patched it in FireOS 5.1.1 so be careful ;)
[Fire Original Android Development] ggow:
- I'll look into this ASAP

- There a couple of other problems I need to fix to enable block based update too so I'll look into these too

EDIT:

- Block Based Update now working

- Looking into the Signature checking now
[Fire Original Android Development] xChr11s:
Working realy good. Tablet seems running pretty good with it. Nice work !

But is there any way to allow the downloads from Amazon Video to be stored on SD Card ? There was an option on FireOS, but its not available in CM. Thank you
[Fire Original Android Development] nish108:
Recived my fire today, im eagerly waiting for flashfire to work with cm :)