yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] ggow:
- I'm going to do some work today on the ROM

- Bearing in mind this device does not have an ambient light sensor

- I'll disable the auto brightness features and that should enable the manual brightness to work

- I'll also be looking into video issues
[Fire Original Android Development] ggow:
- will take a look into it, maybe today if I have time
[Fire Original Android Development] bl4cKz4cK:
First of all, great work on that ROM, running super smooth and I'm really loving it so far!

There are only a few issues I've noticed so far:

- The Twitch App doesn't seem to work properly (becomes unresponsive/hangs, video doesn't play), which I guess has to do with the partially working OMX?

- When I use the device in landscape and turn it off, it rotates the UI to portait, but in a very weird and stretched way. When I turn it on again, everything looks normal. Not really a big thing, just thought I'd mention it as there might be a bigger issue behind it. (Tested on a freshly wiped/flashed device)

Edit: Just saw this issue mentioned over in the SlimLP thread: "Orientation artifact while turning screen off"

- As some others have already mentioned, there seems to be an issue with the Gapps in the opening post, using open_gapps-arm-5.1-pico-20151120.zip however worked for me just fine.

Keep up the great work!
[Fire Original Android Development] kramalot:
FYI I don't seem to have any problem controlling brightness, even the notification drawer slider works and all the live display settings seem OK.
[Fire Original Android Development] ggow:
- I'm not seeing any issue with controlling the brightness of the screen

- What issue are you seeing [MENTION=2211888]jbombs16[/MENTION]?
[Fire Original Android Development] jbombs16:
I am unable to adjust brightness. I enabled/disabled the various related display settings with no changes. I also installed xposed + gravity box and enabled the brightness settings in GB. Nothing.
[Fire Original Android Development] ggow:
- Could you try a fresh install?

- I have checked over how the ROM is configured and can see nothing might that might case this.

- I have tried with Live Display set to all the different selects and when adjusting using the brightness slider it seems to work fine.
[Fire Original Android Development] jbombs16:
I'll try later. I note that this was freshly installed yesterday and the brightness never worked.

Could gapps be the issue? I installed 12/3 Pico
[Fire Original Android Development] switchy85:
[MENTION=5749760]ggow[/MENTION] and [MENTION=2211888]jbombs16[/MENTION]

For the brightness issue it seems like something needs to be done to "shock" it into working. When I enabled the brightness settings in gravity box I could then adjust the brightness, even after disabling the gravity box setting again. Others have said that they set the screen to max brightness then enabled (or disabled then re-enabled) live display to make it work again.
[Fire Original Android Development] ggow:
- I never use GravityBox on Cyanogen Roms so can't comment about that

- I'm about to factory reset and try again.
[Fire Original Android Development] ggow:
- Could be but I'd be surprised if that were the issue.

- Maybe you could wipe system, install just the ROM and SuperSU and test that to start?
[Fire Original Android Development] case-sensitive:
First, thanks for your great work!

Question: I noticed that there is an on-going process called "Mobile Data". I tried to freeze it using titanium but the tablet keeps complaining; I assuming there are other pieces that need to be frozen but I don't what they are. *When* you get a chance and *if* it is possible, would you consider consider removing all the apk related to this (which as I understand is for phone calls and hence not needed for the Fire).

THANKS!

---------- Post added at 11:14 AM ---------- Previous post was at 11:12 AM ----------

The developer of gravitybox explicitly says that GB is not compatible with CM (more generally, any ROM that's not close to aosp): http://repo.xposed.info/module/com.ceco.lollipop.gravitybox
[Fire Original Android Development] alcuin:
Fyi no problems with brightness setting here, using stock + pico 12/3, no xposed, no gb.

---------- Post added at 10:58 AM ---------- Previous post was at 10:25 AM ----------

On an unrelated note, I just tried something weird; I changed the usb connection mode from mtp to charging only. Now I don't seem to be able to change it back; I go to settings, storage, then the dot menu in corner and select usb computer connection, and it just says "usb is now disconnected". Anyone else already tried usb mode switching?
[Fire Original Android Development] switchy85:
While it's true he said that, everything is working perfectly at this point (other than normal issues with this rom on this device). I only enabled and disabled the brightness feature and it fixed the issue there. And I use very few tweaks from GB, so most things are turned off.
[Fire Original Android Development] ggow:
- Just tried this out my new build and works a treat :good:

- Much faster boot time :)
[Fire Original Android Development] jgore43:
Brightness works fine here now .
[Fire Original Android Development] ggow:
- I just did a complete wipe of all partitions

- Installed the ROM and brightness control is working fine

- Let me know what you find.
[Fire Original Android Development] jgore43:
Just installed an auto brightness app and used it to set the brightness lower . Then uninstalled it . Now the cm mod slider works fine.
[Fire Original Android Development] ilfred019845:
If i am not mistaken after you freeze the apk you need to reboot to get the system to optimize for the lack of that apk.
[Fire Original Android Development] kramalot:
[MENTION=5749760]ggow[/MENTION] fwiw regarding brightness: I'm running a fairly clean system, no installs beyond basic Google apps + Firefox, Nova. MXplayer and the GSam bat mon. Default theme and daydream off. Maybe this is down to interactions.
[Fire Original Android Development] ggow:
- Yes I think so too - I did a clean install several times and couldn't get the brightness control to fail so seems good to me

- Although I can't seem to get any open gapps version to work correctly

- Getting the dreaded - "Unfortunately, Google Play services has stopped message" repeatedly
[Fire Original Android Development] case-sensitive:
Thanks. I did reboot (more than once) and I kept getting the error message saying that "Unfortunately mobile data has stopped" (something like that). The only way to stop that is to go back to titanium backup and unfreeze the apk (a lot harder than it might sounds since I have to switch apps in between pop-up error messages). I'm pretty sure the root cause (ha!) is that there is more than one "mobile data" app but I couldn't identify all of them.

*If* the developer could find the time to remove this it would be most wonderful (not to mention saving some space in /system). If not, no problem. THANKS!
[Fire Original Android Development] ilfred019845:
When i get off work this evening i'll take look to see what needs to be removed to take care of the issue.
[Fire Original Android Development] spicypixel:
The only show stopping bug left for me is that when actively using plex with my chromecast (which provides controls in the notification) the tablet will go black when I try to open the notification drawer, but the backlight is still on - screen is definitely not off just displaying black. Tried rebooting and clean flashing and nothing seems to prevent it happening.
[Fire Original Android Development] ggow:
- The next version will remove all the Telephony/LTE/SIM related stuff
[Fire Original Android Development] ilfred019845:
Cool Thanks.
[Fire Original Android Development] kramalot:
OK, if it helps I just did a wipe all but internal storage and installed CM of 1202 with gapps of 1205 and got the same problem so likely it's a change in gapps from Dec 4th onwards that's the root of the problem since the Dec 2 build of CM was fine with gapps of 1202 and if I recall correctly so was CM 1203 with gapps 1203.
[Fire Original Android Development] shadowsiul:
I think i may have found a way to fix the "Unfortunately, Google Play services has stopped message".

It doesn't makes sense but using the same install instructions. Try installing GAPPS first then the rom followed by the SuperUser. I tried it a few time wiping the device every time and it works for me anyways.

Anyone willing to test this also?

Also it possible to get a section in one of the posts with quickfix [MENTION=5749760]ggow[/MENTION]?
[Fire Original Android Development] MAGICMAN516:
I just installed it and everything is fine. I did install the mini gapps. The issue I'm having is once I connect to the internet and try google play store I get "unfortunately google play services have stopped." and I can't get into the store or any google apps.
[Fire Original Android Development] bl4cKz4cK:
Am I the only person who can only use bluetooth as primary user on the tablet? I'm currently using it with two users and for some reason I can't turn on bluetooth if I'm not logged in as "owner" (basically the default user)

Is that a thing?

Search for these gapps (open_gapps-arm-5.1-pico-20151120.zip) in this thread and flash them. There is a link somewhere.
[Fire Original Android Development] ilfred019845:
Just verified I have the same issue. Tried with regular user and restricted user and Bluetooth just keeps cycling itself on and off. Also if the owner profile has Bluetooth off and you try to turn on with a different user and switch back to owner it is turned on.

---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------

Oh also tried turning it on on owner and switching user and it still cycles on and off.
[Fire Original Android Development] jgore43:
Finally was able to build this rom! Had to make the change in this file. Add the netd change to local manifest and remove the default one, works perfect. Thanks so much!
[Fire Original Android Development] jbombs16:
I did a fresh install. Brightness issue resolved. I installed the rom, SuperSU, then gapps in a single twrp session.
[Fire Original Android Development] Kavex:
I had issues with the gapps not loading but then I just used the supertool from rootjunkysdl and that version worked for me. If anyone are having issues then worth a try to get those files.
[Fire Original Android Development] saud__19:
I have the same issue with my zenfone 2, it is related to the latest builds of GAPPS. the only solution is to install the rom then GAPPS then install the rom again.

---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------

...
[Fire Original Android Development] ggow:
- I'll be adding an F.A.Q section to the 3rd post soon
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], when updating each version of the ROM, do I need to wipe anything? So, far I haven't and everthing seems to be ok(knock on wood). Thanks.

Sandman
[Fire Original Android Development] ggow:
- Most of the time it should be just flashing the ROM - dirty flash style

- I will let you know with each release if that changes

- Like for the next version we will need to wipe dalvik and cache because of the changes I am making to the framework
[Fire Original Android Development] sandman512:
Thank you sir, much appreciated!
[Fire Original Android Development] jamesking420:
Hi,

I'd just like to check I understand the process for installing this.

Connect to PC in bootloader/fastboot mode.

Boot in to a custom recovery (whilst connected to PC).

Do a factory reset.

copy across the ROM, superuser and gapps

Flash the rom, superuser and gapps from the recovery.

Boot to System and it will be CM12.1

Subsequent boots to system will also be CM12.1?

Or will I need to reboot via TWRP when I want to boot to CM12.1 again? This isn't clear from the threads, but I assume that the system flash is permanent, and only the recovery needs to be tethered each time?
[Fire Original Android Development] bullet25:
You are correct but you might want to copy the rom supersu and gapps to a microsd card incase you aren't able to in recovery mode. I know I can't the device isn't even detected by windows for me when booted into TWRP.
[Fire Original Android Development] jamesking420:
Thanks. I read somewhere that the recoveries cannot read external SD cards, but maybe that's been fixed now?

Cheers,

James
[Fire Original Android Development] ggow:
New Build is Up

- Dated 09 Dec 2015

- Change log on Post #2

- Wipe Dalvik and Cache after flashing

- Now will start looking into video stuff
[Fire Original Android Development] hammer-is:
Thanks! Great work!

Is SuperSU still required for root access? Or does "built-in" CM root (under developer options) work now?
[Fire Original Android Development] ggow:
- SuperSU is now optional

- All in the Change log on Post #2
[Fire Original Android Development] bullet25:
With SuperSU being optional now, does the build in CM Root SuperUser work fine?
[Fire Original Android Development] ggow:
- i have never used the built in root so I don't know

- Will you give it a test and see?
[Fire Original Android Development] bullet25:
Yeah, I'm at work right now so it wont be for like another 5 hours before I can, but I will when I get home.
[Fire Original Android Development] inscythe:
With the new method to update to FireOS 5.1.1 and keep TWRP access now, would you consider rebasing to the new kernel with the next update? There might be better compatibility...

http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
[Fire Original Android Development] bl4cKz4cK:
Sweet, gotta try that out. Have you made any changes regarding the "bluetooth not working with multiple users" issue?
[Fire Original Android Development] ggow:
- Yes it should be possible to use the binaries and new boot.img without touching our current bootloaders

- Is there a link available where I can download FireOS 5.1.1?

EDIT: Found it
[Fire Original Android Development] ggow:
- Not sure what's causing this atm, I haven't looked into it yet

- Looking into Video Stuff right now.
[Fire Original Android Development] fmc000:
No progress on having the camera working? It's the only thing that is preventing me to move to this ROM (the Fire is my daughter's Christmas present and she's going to throw it at me if she can't take pictures of everything :p ). BTW, anyone tried with other cameras, like Google's or CM cameranext?
[Fire Original Android Development] bl4cKz4cK:
The video issue is more important since it affects way more users in comparison to the multiuser Bluetooth thing, I perfectly understand that. Just wanted to make sure that you recognized it as an issue and eventually will look into it. My friend pointed out that the issue behaves a lot like before you guys got it working for the first time, it basically looks like the second user is having the same issue which the primary user used to have. Hopefully that'll help you troubleshooting this bug.

Anyways, good luck on the video issue, really appreciate the time you're putting into all of this!

Keep it up!

Gesendet von meinem Nexus 5 mit Tapatalk
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], Just want to make sure I have it right, So flash, then wipe Davilk and cache, then reboot. Thanks.
[Fire Original Android Development] ggow:
Correct
[Fire Original Android Development] Vlasp:
[MENTION=5749760]ggow[/MENTION] are you looking into the camera issue? On SlimLP they fixed the camera. Also, does the camera work for Snapchat?
[Fire Original Android Development] fredm77:
No problem with FAT32 sd card.
[Fire Original Android Development] ggow:
Yes, looking into it as part of the video stuff
[Fire Original Android Development] alcuin:
google camera and stock camera work for me, pictures and video on both 2015-12-04 and 2015-12-09 roms. keep up the great work.
[Fire Original Android Development] k4y0z:
I believe for CM-root to work we must set "ro.debuggable=1" and "ro.secure=0", however i wasn't able to change them.

I guess they're set by the initramfs and can't be changed afterwards.
[Fire Original Android Development] kramalot:
Tried a couple of others, Open Camera and one other, forget which. Same problem, can't save image.

Oddly video saves audio which plays but image stream is unplayable though does exist as it shows a thumbnail, also, crashes MX.
[Fire Original Android Development] archerymodz:
Am I the only one who doesn't have root settings in developer options?
[Fire Original Android Development] ilfred019845:
I had the same results with several different cameras taking pictures.

Video works on mine and IIRC can play the videos by disabling HW overlays and using NuPlayer in Dev. Options.
[Fire Original Android Development] bullet25:
Can't seem to find CM's built in root option in developers options with newest build.
[Fire Original Android Development] k4y0z:
As I mentioned earlier, we probably have to set "ro.debuggable=1" and "ro.secure=0", otherewise, the root option won't even show up.

But I don't know if that's possible.
[Fire Original Android Development] sam tyler:
Installed latest update ( 9/12 ) just reinstalled my apps,all good so far.cheers.
[Fire Original Android Development] TheHunterOfShadows:
Real dumb question, but while in recovery any reason i can't, or shouldn't do a format in addition to the factory restore right before install CM?
[Fire Original Android Development] kramalot:
Great stuff! All looking good so far and no problem installing with the latest gapps. I still have no vid problems or problems with brightness. Would love to see the "unmount USB" problem go away but maybe impossible. Others care more about the camera than I do, things more or less pointless anyway.

Great work [MENTION=5749760]ggow[/MENTION] and assistants (bows in appreciation)
[Fire Original Android Development] alcuin:
Video is the only issue for me; I use Diceplayer; if I set playback mode to system default or stock player for a video type, it freezes when trying to do playback unless I turn off hw overlay in dev options. Software playback works fine. I guess this might be an omx issue too.
[Fire Original Android Development] kramalot:
I did a wipe of everthing to start with a clean system, all seems well. Didn't wipe cache/dalvic after install (forgot) but since no problems.
[Fire Original Android Development] TheHunterOfShadows:
Thanks!

Anyone get google play games to install? I get the 505 error from the store.
[Fire Original Android Development] csolanol:
Happens sometimes. Download the apk from apkmirror and install it.
[Fire Original Android Development] TheHunterOfShadows:
Great idea! I just tried it though, downloaded the apk, then went to install it, it started then said, app not installed.

:(

---------- Post added at 02:48 PM ---------- Previous post was at 02:41 PM ----------

My fault, I downloaded the wrong dpi. Did the correct one and it worked!
[Fire Original Android Development] swicago:
Last version I installed required SU, but I see new version doesn't require it. I already installed a lot of app. DO I still have to do factory wipe in order to install the latest version or can I just install over the current installation?
[Fire Original Android Development] hard_where:
Do we need to modify the init.d script to mount exFAT cards? My 64gb exFAT card is not being detected by default
[Fire Original Android Development] l.m.prowse:
Any news on the "playback not supported on this device" message in play movies?
[Fire Original Android Development] Hokie99:
With the 2015-12-09 release I can not install this app https://play.google.com/store/apps/details?id=com.logitech.harmonyhub Says it isn't compatible with the device. I have rolled back to 2015-12-04 and can install the app with no problem.

Is there anything I can check to see why this app will no longer install? I assume it is related to something tat was removed between the 04 and 09 releases.
[Fire Original Android Development] kylemaguire:
I don't think so at the moment. I had to go in and force Windows to format it to FAT32 to get the card to work.
[Fire Original Android Development] hard_where:
ExFAT support was listed in the 12-09 release notes so was curious if we have to modify a script to mount the card
[Fire Original Android Development] k4y0z:
System is overwritten during installation. A factory wipe shouldn't be necessary.

If you require root, you will have to install SuperSU again.

[MENTION=5749760]ggow[/MENTION]: it seems init.d support isnt actually activated, the install-recovery.sh looks like the default one.
[MENTION=2930353]hard_where[/MENTION]: check this post: http://xdaforums.com/showpost.php?p=64196430&postcount=455
[Fire Original Android Development] ggow:
- I'll take a look at what happened, why the correct file did not get copied.

EDIT: Just thought why - I'll do another release tomorrow with the fix
[Fire Original Android Development] 4t701:
can I flash the latest CM via FlashFire?
[Fire Original Android Development] k4y0z:
I just realized the exfat-fix causes logcat to be flooded with:

E/sdcard ( 255): [1] handle_fuse_requests: errno=19

replacing the content of /etc/init.d/99exfat-support with this fixes that:

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

that way the sdcard daemon is only started, when the mount was succsessfull
[Fire Original Android Development] Vlasp:
No. FlashFire is meant for OS modifications, and if the whole OS is gone, there is no FlashFire. Xposed and GApps work because they modify 1 folder.
[Fire Original Android Development] rotech72:
I was wondering the same thing about flashfire
[Fire Original Android Development] 4t701:
yeah, true. On hindsight that was kinda stupid for me to even consider doing that, lol.
[Fire Original Android Development] Vlasp:
It's fine, just glad to help.
[Fire Original Android Development] Sulinjr:
[MENTION=5749760]ggow[/MENTION] You sir are a BAMF. Excellent work! Haha
[Fire Original Android Development] sandman512:
@ ggow, just updated to the latest, maybe it's me, but this thing seems snappier.. Thanks. ?
[Fire Original Android Development] k4y0z:
Found a workaround:

First we need an init-script (99sudaemon):

#!/system/bin/sh

[ `getprop persist.sys.root_access` = 0 ] || /system/xbin/su --daemon

root access can now be controlled via persist.sys.root_access.

To enable the "root" option in developer settings change in /system/build.prop:

ro.build.type=eng
[Fire Original Android Development] Sulinjr:
Hey everyone I'm curious does L Speed work with this version of CM12? Also is L Speed compatible with Xposed or apps like Battery Doctor from the Play Store?
[Fire Original Android Development] TheHunterOfShadows:
I am really impressed with how much difference this makes. The tab was kind of junky before, with cm it's amazing how well it all works. Can't believe it was only $35.

Thought I would ask, (feeling like the needy kid), anyone get this to work with android auto? :D

I installed the app, but my car won't see it.
[Fire Original Android Development] Dr.TheMaster:
hi..I have a 5.1.1 tablet. I accidentally updated it when I first booted it up.. is there any way now to install this CM12.1? it sounds awesome from the comments that I have seen so far.. thanks in advance..
[Fire Original Android Development] aForcefulThrust:
Flashed the updated 12/09 CM and all is good. notice its a little snappier. Thanks!

Music player would not work before for me and now works.
[Fire Original Android Development] seine16:
Many thanks for this terrific job.

Could you please fix the keyboard sound ?
[Fire Original Android Development] sd_shadow:
not currently
[Fire Original Android Development] ggow:
- I won't set build type to eng

- I have done this in the past and seen behaviour like red highlights around certain windows etc

- Instead what I will do is add build type user-debug to the condition enabling built in root access.
[Fire Original Android Development] Dr.TheMaster:
thanks for the quick response.. hope you guys can have a hack for 5.1.1 :)