yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] aForcefulThrust:
Just install google keyboard then go to input settings. you can disable the sound on google keyboard.
[Fire Original Android Development] ggow:
It's on my list
[Fire Original Android Development] ggow:
- Think I've fixed all the video issues

- Camera and Videocam is now working too (HDR isn't working but not a big on this device)

- I'll get a new version out for testing

- [MENTION=2511007]csolanol[/MENTION] and [MENTION=4375260]diegocr[/MENTION] will push changes to my bitbucket shortly
[Fire Original Android Development] highend01:
Damn, happened to me as well :/ How big are the chances that we'll be able to install your rom on such a device (in the future)?
[Fire Original Android Development] ggow:
- My guess is the recovery exploit has been patched by Amazon so no TWRP means no custom ROM

- Safestrap may be possible but I didn't finish looking into that
[Fire Original Android Development] highend01:
Oh no... :/
[Fire Original Android Development] ggow:
New Build is Up

- Dated 10 Dec 2015

- Change log is Post #2

- I would appreciate if I could get some feedback on Apps/Games to do with Video etc

- I tested Netflix and Youtube and seemed good.

- I'll update the table in the OP once I have enough feedback

- Feedback on the Built in Root Access would also be appreciated as I haven't tested it because I have SuperSU installed.

- Enjoy!

EDIT: I've pushed all changes to my bitbucket repo
[Fire Original Android Development] k4y0z:
You are right, that isn't an option, I just described the possibility for an already flashed system.

I was going to suggest the change in the Settings app as well, this seems like the safer route, thanks.
[Fire Original Android Development] sam tyler:
Another update?! I just put on 9/12/15!! :) I will try to put on latest update tomorrow or at the weekend (busy at work) the only problem I had with the 9th Dec update that the tablet would not detect my new sdcard, tried to format it via windows didn't work(even it said it did) in the end I got my old trusty THL W200S phone and I formated there. but keep the updates coming.
[Fire Original Android Development] ggow:
- exfat should now work - it was broken on the 9th-Dec build because init.d wasn't initialised
[Fire Original Android Development] azcom:
Plex is working great now with the 2015-12-10 update. No more need to keep turning off HW overlay each reboot. Great to see the camera/video recording finally working too.

This is the update I've been patiently waiting for. Great work [MENTION=5749760]ggow[/MENTION]! I owe you a debt of gratitude for all your continuing hard work on this ROM. I'm sure there are still little bugs or improvements that can be looked at but for me all the major stuff is now working as you would expect it to. Keep up the good work!
[Fire Original Android Development] ggow:
Hi [MENTION=7104332]k4y0z[/MENTION],

- I just tried a build using the new update-kindle-full_ford-37.5.4.1 and it didn't boot

- I believe the symbol version has changed and so the new kernel isn't loading the existing selinux permissive module

- Would you mind building a new module against the new kernel?
[Fire Original Android Development] k4y0z:
If it uses a different zImage, that is entirely possible.

I had the pointer for selinux hardcoded in the module.

I will try to make it find the pointer dynamically, so it will also work on future updates.

Could you upload the new boot.img or point me to it?
[Fire Original Android Development] sam tyler:
I knew I should have waited for the next update! thanks for replying.
[Fire Original Android Development] ggow:
- Your right the zImage is different

- I have attached the new boot.img on this post

- Thanks :)
[Fire Original Android Development] kramalot:
You are Da Man (and I live in Scotland so that's not a phrase I use very often)
[Fire Original Android Development] archerymodz:
Built in root does not work for me, wiped system, cache and dalvik then installed system and gapps and wiped cache/dalvik again.
[Fire Original Android Development] ggow:
Will take a look
[Fire Original Android Development] csolanol:
It is in the same status as cm. No Bluetooth and no battery stats. Still working on it.
[Fire Original Android Development] diegocr:
You can flash any boot.img but with locked boot loader only boots signed imgs.

Slimlp is like this cm build, BT don't works and have signal network icon.

Are using [MENTION=5749760]ggow[/MENTION] device info [emoji106]
[Fire Original Android Development] ggow:
- I now have a solution for booting Cyanogen standalone :D

- I'll update the OP and upload the new ROM
[Fire Original Android Development] ggow:
New Build is Up

- Dated 2015-11-16

- No more tethered boot :)

- Change log will be on Post #2
[Fire Original Android Development] zach61797:
Awesome how did this work? I thought bootloader would

Don't allow it
[Fire Original Android Development] ggow:
- Turns out Cyanogenmod works a little different to SlimLP

- I ended up modifying netd service to force selinux to permissive

- [MENTION=4375260]diegocr[/MENTION], the solution I have can be integrated into the build process

- Tomorrow morning I'll finalise it and update my bitbucket with the change.
[Fire Original Android Development] zach61797:
Can this work on hdx devices that can't be unlocked??
[Fire Original Android Development] ggow:
- This isn't the place to ask about the Kindle HDX and this is not required for those devices, please ask for help in the HDX forums

- There may be solution waiting for you there :)
[Fire Original Android Development] zach61797:
Awesome thanks if so both my devices will be on cm 12 thanks alot
[Fire Original Android Development] Vlasp:
Nice! Testing right now as soon as my device finished backing up.
[Fire Original Android Development] :
I love you dude

I love you dude
[Fire Original Android Development] Khyinn:
Oh yeah, so now, we have a custom recovery (not flashable but it's not a real problem) and a working standalone ROM. Great ! I love you man !
[Fire Original Android Development] Harry44:
I dirty flashed the newest build, flashed su, and then gapps. No issues as far as I can see yet.

Time to buy 5 or 6 more of these for around the house and gifts now haha.
[Fire Original Android Development] BadPotato:
Thanks for this man!

Just in case anyone is wondering how to get rid of the horrible orange bars when battery saver is enabled, you can disable it using gravity box (LP) and go to . . . Power Tweaks - Disable battery saver indication.
[Fire Original Android Development] a1yet:
where can i get su

to flash

found one im going to try

.
[Fire Original Android Development] qtotter:
hi ggow,

great job! i just installed the rom, and it looks good.

i have noticed two things. the first thing is does this rom support SDXC? if i put my 128gb sd card (transcend), fire doesn't recognize it at all. i didn't have issues with 16gb cards...

secondly, when i connected fire to pc, i chose charge only option on fire. now, there is no way back to MTP or PTP... i got this "usb is now disconnected" message when i clicked "usb computer connection" in the storage setting. i cannot even enable debug option, either.

thanks for your good work.

qt
[Fire Original Android Development] a1yet:
with gapps i could only get the "NANO" version to install

Full and stock gives error then erases
[Fire Original Android Development] Tobb555:
How long does it take to boot into CM? I just flashed 11/16 and its been flashing the Cid boot screen for 10 mins now.
[Fire Original Android Development] Vlasp:
You have to flash the SU.zip for it to boot. Search it up, it is the one by chainfire.
[Fire Original Android Development] Tobb555:
Thanks. I must have missed that step. Booting now.
[Fire Original Android Development] archerymodz:
If you need a test mule I can test for you before releasing.
[Fire Original Android Development] ggow:
Thanks, will let you know when I have new root version to test

Found the cause: Will fix and send you link
[Fire Original Android Development] chetta:
Do I need to factory reset if I'm upgrading from the 12/4 build?
[Fire Original Android Development] ggow:
- Wipe cache and Dalvik should be enough
[Fire Original Android Development] chetta:
Thanks for quick reply and great ROM.

Just to be certain - 12/4 , gapps, and SuperSu already installed.

Just flash new build and wipe cache and Dalvik?

Reflash either gapps and/or SuperSu?
[Fire Original Android Development] ggow:
- Yes, flash the ROM

- If you didn't run the script in supersu to survive ota updates then you also need to flash supersu again

- Then wipe cache and dalvik and then reboot.
[Fire Original Android Development] chetta:
Thanks!
[Fire Original Android Development] ilfred019845:
Video playback work good on hulu, YouTube, and newmoviesdotnet.

Tested camera and photos and videos work.

Thanks a bunch now I can flash my kids and nephews x-mas presents with a ROM that is much much better.[emoji106] [emoji106] [emoji106]
[Fire Original Android Development] fmc000:
My daughter will have CM12.1 for Christmas :D Kudos to ggov and to all the devs working on this.
[Fire Original Android Development] ilfred019845:
I know the feeling. I was also waiting on camera fix. Now i know that my kids will love their presents. A positive is that it will boot without SuperSu so now i don't have to worry about them messing it up.:D
[Fire Original Android Development] highend01:
With the 5.1.1 rom update from Amazon, is it dangerous to see if it still boots via fastboot boot TWRP_Fire_2.8.7.0.img? Or is it better to don't try that at all?
[Fire Original Android Development] archerymodz:
Amazon blocked all fastboot commands with the 5.1.1 update.
[Fire Original Android Development] k4y0z:
I just updated the kernel-module it now finds the pointer dynamically.

EDIT:

removed debug-output.
[Fire Original Android Development] highend01:
Ok, thanks for that information
[Fire Original Android Development] kramalot:
Ditto here. I know I've said I don't care about the camera but I need to get CM onto my wife's Fire and explaining why "the camera isn't working yet" is more than I can face!
[Fire Original Android Development] ggow:
- Thanks for this :)
[Fire Original Android Development] ggow:
- Just got Built-In root working

- I had to modify system_extras_su binary source to bypass the ro.debuggable property enforcement.

- Will upload new version a bit later
[Fire Original Android Development] k4y0z:
Was just about to do the same ;)

EDIT:

Now when I looked at the source I see it couldn't have been working with "eng" either since it was still on ro.debuggable=0.

Then I remembered I had overlayed /default.prop (with mount -o bind), which is why it worked for me.
[Fire Original Android Development] inscythe:
The rooted stock ROM also can't do HDR with Google camera app. The hardware might just simply doesn't support it.
[Fire Original Android Development] fmc000:
A possible bug: I don't seem to be able to modify the phone lockscreen shortcut with something useful (sorry if it was already brought up but I'm on tapatalk atm) .
[Fire Original Android Development] k4y0z:
[MENTION=5749760]ggow[/MENTION]

For the next update could you please add /system/etc/install-recovery-2.sh with the same content as /system/bin/install-recovery.sh

That way init.d-support doesn't break when SuperSU is installed (it overwrites /system/bin/install-recovery.sh, but executes /system/etc/install-recovery-2.sh).
[Fire Original Android Development] spicypixel:
Is the rom available to download today the one with built in root/privacy guard?

Just asking since the post in the thread announcing it was Today, 03:47 PM and the latest update on the second post was before that
[Fire Original Android Development] ggow:
- Yeah, sure no problem :)
[Fire Original Android Development] ggow:
- I might get a few more fixes in then release it for tomorrow instead.
[Fire Original Android Development] spicypixel:
That's fair, not that upgrading is a burden just wondered.

Gonna go check it out now and see what's working.
[Fire Original Android Development] ggow:
- I have a build locally which I have it working in

- I haven't uploaded it yet

- I'm going to try out the binaries and boot.img from Amazon's latest FireOS

- And look into a couple of other small bits

- Then I'll do another release when I'm done

:)
[Fire Original Android Development] hard_where:
Thanks! This explains why my exFAT micro sd cards are not being detected in the 12-10 build.
[Fire Original Android Development] ggow:
- Agree with you, looking at the specs I would say it doesn't support it too.
[Fire Original Android Development] ggow:
As expected, the new module works

Thanks :)
[Fire Original Android Development] ggow:
- Got done sooner than I thought

- Uploading a new update now
[Fire Original Android Development] kramalot:
Couple of minor oddities as I install it on my wife's fire. Initially Google Keep would not install, said it was incompatible but after a couple of reboots it worked although the widget was not there until after another reboot.

Google calendar will not install so far, not a big problem I prefer the stock (she won't "its different")

The Weather Channel says its incompatible with device.

Camera works thanks!

Other than that all looks great as usual.
[Fire Original Android Development] ggow:
- For Google Calendar install an old version from apkmirror then update from playstore
[Fire Original Android Development] alcuin:
Video works great here, using diceplayer in default mode. Great job, thanks!
[Fire Original Android Development] ggow:
New Build is Up

- Dated 2015-12-10 - PM Build

- Change log on Post #2
[Fire Original Android Development] kramalot:
Thanks for that.
[Fire Original Android Development] fmc000:
Also with MX player in hw mode with custom codec.

---------- Post added at 07:55 PM ---------- Previous post was at 07:49 PM ----------

Just curious, what are the binaries included in the build? Some proprietary pieces of firmware or non GPL drivers?
[Fire Original Android Development] 4t701:
should I be using an usb 2.0 or 3.0 or are both versions supported?
[Fire Original Android Development] ggow:
- See no reason why both should't work except where power requirements may be too high to support a particular device
[Fire Original Android Development] archerymodz:
Usb 3.0 supports usb 2.0 and usb 3.1 supports 3.0 and 2.0
[Fire Original Android Development] 4t701:
Guess I might as well go with a 3.1 cable then if it's backwards compatible with 3.0 and 2.0.
[Fire Original Android Development] archerymodz:
Usb3.1 was just introduced. So unless you have just recently built your own computer it won't have 3.1
[Fire Original Android Development] hard_where:
exFAT not detected with 12-10pm build. I do have superSU installed.
[Fire Original Android Development] spicypixel:
Having a plex chromecast session in the notification bar still breaks everything, minor issue but annoying if you wanna reply to another notification and instinctively drag it down to tap it. On the upside nuplayer works and plex playback works without a hitch.
[Fire Original Android Development] 4t701:
I am just wanting an OTG cable to possibly use an usb mouse/keyboard/etc. on my Fire. An OTG USB 3.0 would be my best bet then?
[Fire Original Android Development] l.m.prowse:
Play movies still doesn't work :( still gives the "playback not supported on this device" message when attempting to play anything :(
[Fire Original Android Development] switchy85:
Tested out video in a bunch of video apps on the latest 12/10 pm build. Vlc w/ full acceleration, Netflix, hulu, amazon video, and comedy central app all work perfectly. The adult swim app gets laggy, but it was never the best even on my Nexus 5. Mx player is kind of weird, though. I can manually select HW or HW+ and it works on compatible videos (not avi/divx), but it always defaults to SW decoding on each video even though I have it set up to use HW+ first. I can definitely live with this, though.

I was even having more WiFi issues on the 12/09 build that seem to be resolvedpon this one, so good job on that!

This rom is now waaay more usable and makes this tablet a joy. :) Thanks, guys!
[Fire Original Android Development] ilfred019845:
I believe USB 3.0 otg id different than a 2.0 otg.

Just Checked and they are. Male ends are Different and the 3.0 won't plug into a 2.0 socket.
[Fire Original Android Development] k4y0z:
It seems like SuperSU still breaks init.d,

For now you could either install without SuperSU and use the built-in ROOT (Activate under Developer Settings).

Or if you have adb installed, issue the following commands:

adb shell su -c "mount -o remount,rw /system"
adb shell su -c "chmod 755 /system/etc/install-recovery-2.sh"
adb reboot

[MENTION=5749760]ggow[/MENTION]:

It seems /system/etc/install-recovery-2.sh doesn't have the correct permissions set, once the file is made executable it works
[Fire Original Android Development] archerymodz:
I'm sorry I misunderstood
[Fire Original Android Development] ggow:
- Ok, I'll fix this up for the next release
[Fire Original Android Development] alcuin:
Same here, using 12/10 pm. I see the SlimLP rom seems to have this fixed, I will do some searching to see if I can find out what the difference is; thx.
[Fire Original Android Development] ilfred019845:
[MENTION=5749760]ggow[/MENTION] and [MENTION=2511007]csolanol[/MENTION]

I was just looking through my logcat and found this.

I/PowerManagerService( 499): Going to sleep due to power button (uid 1000)...

I/PowerManagerService( 499): Sleeping (uid 1000)...

I/[MALI][Gralloc]( 134): usage: 0xf02, format: 1 stride: 608 vertical_stride: 1024 size: 2490368

I/MaliEGL ( 499): [Mali]window_type=1, is_framebuffer=0, errnum = 0

I/MaliEGL ( 499): [Mali]surface->num_buffers=4, surface->num_frames=3, win_min_undequeued=1

I/MaliEGL ( 499): [Mali]max_allowed_dequeued_buffers=3

I/[MALI][Gralloc]( 134): usage: 0xf02, format: 1 stride: 1024 vertical_stride: 600 size: 2457600

I/[MALI][Gralloc]( 134): usage: 0x333, format: 1 stride: 1024 vertical_stride: 600 size: 2457600

E/[EGL-ERROR]( 134): egl_image* _egl_create_image_ANDROID_native_buffer(egl_display*, egl_context*, EGLClientBuffer, EGLint*, void*):593: CHUN try create image with crop 0,0,0,0

E/ ( 134): CHUN map external image rgb 1024 x 600

E/[EGL-ERROR]( 499): egl_image* _egl_create_image_ANDROID_native_buffer(egl_display*, egl_context*, EGLClientBuffer, EGLint*, void*):593: CHUN try create image with crop 0,0,0,0

E/ ( 499): CHUN map external image rgb 1024 x 600

If you notice on the first MALI Call it has a stride of 608 and a vertical stride of 1024.

And if you look at the second and third MALI calls stride is 1024 and vertical stride of 600.

After that there are four errors with creating the image.

Thought this might be helpful with trying to figure out the artifacts (image rotation/distortion) when locking the screen.
[Fire Original Android Development] tonyf7:
5.1.1

Will this ROM work if my Fire tablet is currently on OS 5.1.1?
[Fire Original Android Development] ilfred019845:
Nope Amazon disabled fast boot on 5.1.1 which means you cant boot TWRP.
[Fire Original Android Development] tonyf7:
Arrrg! I just got my Fire delivered a couple of days ago and I think it came with 5.1.1. Is there a way to downgrade back to whatever version was before 5.1.1?
[Fire Original Android Development] ilfred019845:
At the moment there isn't.

---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------

I would check to see if you have any dead pixels and request a replacement.

If you do get a replacement i would skip the setup so it doesn't connect to wifi and then check the version.

if it is 5.0.1 then install this rom.
[Fire Original Android Development] blueberry.sky:
Did you use your Fire at all after is arrived?
[Fire Original Android Development] tonyf7:
Great minds think alike! I was literally JUST working on that through Amazon chat. They can send me a replacement with one day shipping but it would be a refurbished unit. Or I could wait until December 27th until new units are in stock, which I definitely don't wanna wait for.

You think I should take a refurbished unit or should I just keep my brand new one and hope that someone will root 5.1.1?

---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------

Yes, I used it and connected to Wifi when setting it up. It's very possible that it pushed the update to 5.1.1 then.
[Fire Original Android Development] blueberry.sky:
The Fire does not ask permission to update. If you connect to wifi (without disabling OTA first) then it will update.
[Fire Original Android Development] tonyf7:
Well that's really ****ty on Amazon's part.
[Fire Original Android Development] ilfred019845:
I would try the refurb.

I opened mine up a few days ago and there isn't much in there that could go wrong.
[Fire Original Android Development] jayjr1105:
That's really sh***y of Amazon to kill fastboot. Sorry for those who already upgraded the fire OS :(

On a side note... is there a way to permanently install TWRP or do I have to use the script from a computer every time?

2nd question, Can I dirty flash 12-10? What about gapps? Can I just leave that be? I still have the pico 11-20 build installed.
[Fire Original Android Development] ilfred019845:
Bootloader is locked so you can't flash TWRP.

IIRC you have to do a clean install but i may be wrong. [MENTION=5749760]ggow[/MENTION] should be able to tell you for sure.

Also 1120 pico is what i have been using since i flashed CM 12.1 and have not run into any issues.
[Fire Original Android Development] RW2112:
Already answered, lol.
[Fire Original Android Development] jayjr1105:
Thanks. I'll hold tight on 12-4 for now. Camera is the last thing I'd use on a tablet anyway.
[Fire Original Android Development] kramalot:
You can flash over, wipe dalvic and cache. I think to you need to flaah supersu again as well. Slightly lost track of where we are on that, probably best be safe. As for gapps it seems OK now, I'm using the latest.
[Fire Original Android Development] GloriousDJ:
I don't want to sound impatient or unappreciative of all the hard work you have done fixing the bugs and updating so often. But have you had a chance to look at moving app's to the sd card and it still taking up internal storage? Honestly while I love ROM, but this was the main reason why I wanted to use CM so I could use a 32GB+ sd card and install lots of movies/audio-books/apps/whatever and not be so limited to the 8GB internal with all of amazon's app's unable to really use the sd card on stock. Thanks again for all your hard work on this.
[Fire Original Android Development] theophile2:
Why do you think this is a rom issue? On every recent device I've had, only some apps can be moved to sd card and even then, it's hit or miss as to how much is moved. You may have to use an app like Apps2SD to do the hyperlinking necessary to truly move entire apps over.
[Fire Original Android Development] tonyf7:
Are you saying that you move an app to the SD card but it still takes up space on the internal SD? If so, is that also happening when you put movies on the external SD?
[Fire Original Android Development] 4t701:
depending on the app yeah...for instance with the game Dead Trigger if I install that app it installs on internal as default. I can then go and move the app to sd card and it will move the .apk to external sd card. However alot of apps (mainly really large ones) have an .obb file as well which isn't moved to your external sd card. If you use xposed you can get a module called 'Obb2sd' which allows you to manually move the obb file over to external sd. I don't think this is a rom specific issue rather an Android issue.

---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------

use xposed module 'Obb2sd' or other similar app of your choice. This isn't a problem with CM it is a problem with all android devices.
[Fire Original Android Development] Ownster:
Installed the Rom on my fire, runs really well, only thing I am wondering about is the sleep animation it's the screen in landscape for some reason.