yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] vtec_:
Had this issue a few weeks back and it went on for a few days, the solution was ridiculously simple. Just 'hit' your phone with some force on the power button side to loosen it up. Sounds too simple but a quick Google shows the solution works for most...
[Nexus 5 Original Android Development] ssauger:
Email

Will there be the normal email apk back in 12.1 official or we have to use the service apk to get exchange working in gmail. I am on [MENTION=4152171]myfluxi[/MENTION] unofficial CAF 12.1 and the mail is missing since first build.

Thanks in advance
[Nexus 5 Original Android Development] AndrasLOHF:
So how does CM work in regards to devices. If myfluxi's Nexus 5 is unfixable do we lose support; have a new maintainer assigned; have to have someone volunteer to do it; CM will push builds anyways; etc???
[Nexus 5 Original Android Development] happiness4u:
I just hope not. But base on [MENTION=4152171]myfluxi[/MENTION]'s post, it can be the "grand finale". Maybe for the hammerheadcaf variant, as he is the only one pushing caf kernel commits for our devices. I still see him working on it until now, I'm following his work on github, and he's really working hard tho his phone is broken. If only myfluxi was near, I would repair and replace his power button for free, as I have the tools to do so. :)
[Nexus 5 Original Android Development] AndrasLOHF:
I hope not either. Actually I just jumped to CM almost 2 months ago as the two teams that I usually run on my phone have been very dormant(compared to past history) as far as official public builds go since Lollipop dropped. I thought to myself..."It's CM they're sure to push consistent updates to a Nexus device." I prefer running something from bigger teams in hopes on not losing support.
[Nexus 5 Original Android Development] happiness4u:
[MENTION=5052420]AndrasLOHF[/MENTION], I'm also keeping an eye to this new caf build. If this can keep up with myfluxi's build, I might consider this rom. But if not, I will probably stay with myfluxi's caf build, or revert back to a stable 5.1 stock rom in the future. :)
[Nexus 5 Original Android Development] AndrasLOHF:
Have you flashed the latest myfluxi 12.1 CAF release? If you have can you tell me if song skipping with volume buttons when screen off is working? I reverted back to 12.0 as too many times I blasted my ear drums by long pressing the volume up to skip tracks and due to my forgetfulness blasting the phone up to full volume. :eek::eek::eek:
[Nexus 5 Original Android Development] happiness4u:
Sorry man, I'm on official CM12 04-14 as we speak. The last time I was on 12.1 caf, was 04-08, I guess, I can't really remember. I haven't really have the time to test the build thoroughly as it prompts to many fc's before. :)
[Nexus 5 Original Android Development] qitt:
It doesn't work for me on 13-Apr myfluxi CAF...
[Nexus 5 Original Android Development] ssauger:
Its working for me, had to dis/enable it in button Settings.

sent from Nexus5
[Nexus 5 Original Android Development] AndrasLOHF:
Do you have Ambient Display turned on?
[Nexus 5 Original Android Development] archish:
So what will be your next new phone? (Nexus 2015 whenever that is?) I will jump ship :P
[Nexus 5 Original Android Development] ssauger:
You're right, it's only working when Ambient Display turned off, maybe [MENTION=4152171]myfluxi[/MENTION] can look at it since he worked a lot on it. Hope his N5 is fine again.
[Nexus 5 Original Android Development] myfluxi:
Would you (or the original reporter) please put this in a usable report. Exact usecase, steps to reproduce etc. This is the only way I can pass this to the framework people.

Regarding "stabilty", the CAF builds are now every bit as "stable" or "instable" as AOSP.
[Nexus 5 Original Android Development] ssauger:
Start a musicplayer and play any music. I use Power AMP.

When Ambient Display is enabled, you can't switch to next or previous track when the display is off using volume button long press. Long press volume up when display off increase volume constantly. Is ambient display disabled, volume button can switch tracks if display is off. I restored my old CM12 CAF nandroid (cm-12-20150408-NIGHTLY-hammerheadcaf.zip ) and there i was able to use volume button to skip tracks, no matter if ambient display is enabled or disabled. So it think its a issue from CM12.1 or any change after the nightly from my nandroid CM12.
[Nexus 5 Original Android Development] djsubtronic:
I was able to reproduce this on PlayerPro, so looks like the player is not relevant.
[Nexus 5 Original Android Development] myfluxi:
Thanks. It's just our button hackery conflicting because parts of it haven't been migrated to 12.1. With all these open issues, I don't see how I could enforce a priority. If you depend on it, stick with 12.0.
[Nexus 5 Original Android Development] ssauger:
The Volume thing is no problem for me. I got an other issue i can't reproduce. Since i am on CM12.1 CAF, it was a clean flash and i wiped all, i got 2 times the problem that my phone didn't come on right. I pressed powerbutton, then display was on but i could'nt do anything. Had to wait till display turns off, but i was not able to unlock it. So i pressed the powerbutton as long till the phon reboots. One time it happens, the android is updating prozess was on the next boot. As it happens the second time it reboots normal. Is this a known thing?
[Nexus 5 Original Android Development] myfluxi:
This is the the dreaded mdss error but it only helps with the exact build date. I'm getting really tired to rephrase this again and again and again. Plus logs. Sometimes I really ask myself why I bother if nobody listens, it's so frustrating and disillusioning.
[Nexus 5 Original Android Development] Sly_67:
Same thing happen to me. I notice that device was extremely hot both times. I'm not sure that those things are related.
[Nexus 5 Original Android Development] ssauger:
How can i help if it happens again, what do you need also to the build date, logcat?
[Nexus 5 Original Android Development] simplicio11:
Yep.
[Nexus 5 Original Android Development] mrmidnight:
For some reason, last two days, I am unable to flash hammerheadcaf, this is a clean flash attempt, coming from Cataclysm rom. I'm on the latest TWRP.

The error states an error in executing updater binary

EDIT

I'm getting the same issue when attempting to flash over the AOSP build of CM.

Thank you
[Nexus 5 Original Android Development] AndrasLOHF:
...but are you using CAF TWRP?
[Nexus 5 Original Android Development] Sly_67:
You must have TWRP for CAF. Last official version is :)

http://dl.twrp.me/hammerheadcaf/

It's new device :)))
[Nexus 5 Original Android Development] AndrasLOHF:
Anyone else notice stronger cell signal on 12.1? On 12.0 with the 5.0.2 or 5.1 radio I get a day of mostly yellow and some red cell signal. On 12.1 with 5.1 radio my day is mostly green and some yellow signal. I've flashed back and forth between the two enough to notice the consistency of the difference. Using T-Mobile.
[Nexus 5 Original Android Development] mrmidnight:
Yep that is the issue, thanks!
[Nexus 5 Original Android Development] kogone:
same issue here. running 12.1 20150405

caf is so great. won't go back! thanks for all the work flux!
[Nexus 5 Original Android Development] d1n0x:
[MENTION=4152171]myfluxi[/MENTION] I want to take this moment to appreciate the hard work you put in for us and hammerhead.

Hope you get your device issue settled ASAP so we can continue to enjoy your awesome creations.

Been using your unofficial CAF versions for quite some time now and haven't looked back since! I flashed a few other ROMs here and there, but always end up restoring the CAF nandroid :D
[Nexus 5 Original Android Development] happiness4u:
I've tried mylfuxi's cm12.1-caf. But my HDR option for GoogleCamera was missing. Anybody with the same issue? Maybe it's my Gapps, I'm using the original PA Gapps 5.1. But on CM12, HDR was there, using PA Gapps 5.0. I also tried on the new cm12.1-caf-optimize that was surfacing on the development thread, same issue arise. :( But that new caf build was fast and very responsive imo. :)
[Nexus 5 Original Android Development] AndrasLOHF:
[MENTION=5451017]happiness4u[/MENTION]

I've had no issues on any builds. I also use the last official PA Gapps.
[Nexus 5 Original Android Development] happiness4u:
You have the HDR function? I already clean flashed twice, still HDR was not there. :( I already reverted back to 12.0 atm.
[Nexus 5 Original Android Development] el_smurfo:
Must be gapps. I used one called gapps-L-3-17-15.zip...I think it was from Banks/Euroskank and my HDR+ works fine. Here's the latest

http://fitsnugly.euroskank.com/?rom=banks&device=gapps

EDIT: Just noticed the description "fixes swiping in AOSP keyboard for cyanogenmod"...Damn that has been bugging me...guess I'm trying 4-15 too.
[Nexus 5 Original Android Development] AndrasLOHF:
Yes. One of the first things I do when setting up after a flash is turn HRD+ on.
[Nexus 5 Original Android Development] Sly_67:
I have same HDR+ problem. Flashed Banks newest gapps, and everything is OK now. And swipe on AOSP keyboard is working too.

I'm on 4.13. CM 12.1 unofficial myfluxi CAF + Banks gapps-L-4-15-15.

Nexus 5 CM 12.1 CAF
[Nexus 5 Original Android Development] el_smurfo:
Good to hear about the keyboard. Do you need to flash gapps each time to keep the keyboard swiping working with a dirty flash?
[Nexus 5 Original Android Development] Sly_67:
I don't think so!

Nexus 5 CM 12.1 CAF
[Nexus 5 Original Android Development] *child:
CM12 CAF is so awesome. It's much smoother and I don't get home screen redraws like I do with non-CAF builds. I can't wait to try CM12.1 CAF.
[Nexus 5 Original Android Development] myfluxi:
cm-12.1-20150415-UNOFFICIAL-hammerheadcaf.zip
[Nexus 5 Original Android Development] ilaf0106:
Hey for people with low sound issues, have you guys tried the nexus volume boost on Google play? I have it and it works just fine no problem?
[Nexus 5 Original Android Development] jawz101:
I don't know why but my phone feels normal on the CAF builds. I don't know why but it does.

It's the best adjective I can think of.

I don't even have a compulsion for 3rd party kernels or extra snake oil. Thanks for this.
[Nexus 5 Original Android Development] VQ30DE:
I am having same problem on myfluxi's 12.1 4-13 CAF build. Clean flashed over 5.1 stock, used banks minimal gapps. In morning while plugged in alarm goes off once and then system hangs. Has happened exactly the same two days in a row but I don't know if the Clock problem is just coincidence. Touch screen is almost entirely unresponsive; have to reboot. I can try to get a logcat tomorrow if that will help.
[Nexus 5 Original Android Development] caliban2:
Try again with today's version.

I also had lockups and reboots with 4-13 edition. Full wipe last night made it even worse. ^^ (was running a dirty flash from cm12-caf before).

Stuff like opening gmail and skype made it reboot, sometimes sys became unresponsive.

Today's nightly (dirty flash) -> none of the above happened so far in the last hour. Too early to be sure, but give it a try. At least everything "feels" better, snappier.

[MENTION=4152171]myfluxi[/MENTION]: Of course I deleted the logs from 4-13 when I saw you uploaded a new build.

But: just rebooted and had a look at last_kmsg. Look the very end, it's best visible there - any idea what I'm looking at? The logs after the crashes showed the same corrupted text. It starts right at boot and goes throughout the log.
[Nexus 5 Original Android Development] el_smurfo:
Glad you folks posted. I also am having extreme slowdowns several times a day, usually upon unlocking. A hard reboot is the only fix. Yesterday, I took it out of my pocket to a System UI crash message and had to reboot as well. Installed a logcat capture program, but so far 4-15 is running very well...perhaps snappier than 4-13 (new governor mode? New Play Services that I updated today?).
[Nexus 5 Original Android Development] VQ30DE:
Thanks, will try 4/15. Looking at the end of your log, I do see "mdss" there which is the problem myfluxi referred to but I don't know what it is.
[Nexus 5 Original Android Development] caliban2:
Yeah, I know about mdss. (Doesn't it go back to cm11?)

Currently I'm more worried about this stuff: ^^
[Nexus 5 Original Android Development] d1n0x:
Nothing of that sort happening here on 4/13, it's been running great for 2 days straight, no hiccups, no hangs, no reboots :good:
[Nexus 5 Original Android Development] happiness4u:
Finally, I manage to make HDR+ to work on 12.1. Just let the phone sit for a while to load all the drivers. :D Being impatient won't really help. LOL
[Nexus 5 Original Android Development] caliban2:
Yeah, I don't know what happened on 4-13, the build from 15th is running perfectly on my phone. Despite the corrupted log file (found some info this could be caused by multiple debug-instances and means nothing) and the IRQs not being attached to CPU anymore it's fast, smooth, stable, etc so far.
[Nexus 5 Original Android Development] happiness4u:
CM12.1 Caution: Accidentally activated the flashlight on quicksettings, It takes about a minute, then the LED flash stopped working and it's scorching hot! The toggle is also deactivated automatically. This never happen to me at CM12 with flashlight turned on for a couple of minutes. Tried to reactivate the flashlight again, but it immediately and automatically turn the toggle off as I press it. I tried to use the camera, and I got FC's. Fixed by a reboot. A very manageable issue tho. This is just a reminder.
[Nexus 5 Original Android Development] californicated:
Why don't you post a log?
[Nexus 5 Original Android Development] happiness4u:
Why would I? As I've mention, I already rebooted my device and if I take a log after the reboot wherein the LED started working again together with the camera, therefore the issue won't be included in the logcat anymore. I don't want to risk my device to reproduce the issue again. I already thought that my LED was broken due to that intense heat from the LED. You could try if you want, then make a logcat. :D
[Nexus 5 Original Android Development] californicated:
To support development? I'm currently on stock and can't flash as I'm waiting for important calls, otherwise I'd be glad to help. ;)
[Nexus 5 Original Android Development] happiness4u:
If the devs read it here, they may already address the issue. Some devs, just need a clear explanation on how to reproduce the issue. I'm planning to shift back to CM12 some time, as that scenario with the LED heat scared me big time. As for me, I don't want to risk it, I might end up with a camera-less phone if I do. :)
[Nexus 5 Original Android Development] simplicio11:
I'm on cm12.1 15-4 and I don't have this issue. :good:
[Nexus 5 Original Android Development] ssauger:
I thought this is a problem started with android 5, i remember i had this also once on cm12 when i used the flashlight over a longer time. There was nothing hot, but i had to reboot to get flashlight working again.

http://www.ubergizmo.com/2014/11/android-5-0-lollipop-seems-to-have-flashlight-bug/

http://www.ibtimes.co.uk/installed-...-4-smartphone-look-out-flashlight-bug-1475313
[Nexus 5 Original Android Development] happiness4u:
Good for you.

I did not experience that in official CM12. LED flash really heat up when used for a while, both on my Nexus 5 and G2. But this cm12.1 glitch, It doesn't take 2 minutes to generate heat on the LED, then the lights are out. If it's there before on stock 5.0, maybe it needed a rework on the rom. :)
[Nexus 5 Original Android Development] gjobjo:
update

Hi, is update appl configured for CAF Rom update? I installed this Rom today
[Nexus 5 Original Android Development] dr.eXntriK:
Hey,

Awesome work on the CAF. I'll be honest, I have been looking u CAF for a while now and I've gotta say that i am not able to find the advantages of CAF over the normal edition. Can you please kindly explain them to me?
[Nexus 5 Original Android Development] djsubtronic:
Hey guys. I just found out that Heads Up notifications (a major annoyance for most users as I've gathered) can be disabled globally by simply making a change to one of the records in Settings.db (using a SQLite editor). I remember the original feature being developed was abandoned due to too much work, but this seems like a simple setting that can be added which changes the flag.

What would be the best way to bring this to a developer's attention? It would be nice to have this setting back. If I knew how to tinker with Android source on Github I would attempt this myself but I don't have the skills.
[Nexus 5 Original Android Development] :
Lol is anyone even using my unofficial builds?
[Nexus 5 Original Android Development] qitt:
Yes, I'm using...
[Nexus 5 Original Android Development] :
Do you notice any difference?
[Nexus 5 Original Android Development] qitt:
Hard to say... Anyway all works fine for me and I thank you for your work. But I used your builds two days only. Need to test it more.
[Nexus 5 Original Android Development] wintrxtrem:
I just ran torch for 5 minutes, catlog running, but the led stayed on the entire time.. 4/15 CAF 12.1

My lock screen toggle does not work though. No matter which position I always have to unlock with my PIN.
[Nexus 5 Original Android Development] el_smurfo:
Poked around General and Development and couldn't find them. Even stalked your profile and don't see anything related. Maybe that's why no one is using? I'd give it a try if you direct me to the changelog and link. Your gapps are still consistently the best for me.
[Nexus 5 Original Android Development] jerunk:
I've been running them since you first released them, with your latest gapps.

Performance is excellent, battery life is standard.

The only issues for me still are Bluetooth Share crashing when my car tries to read my SMS messages, and the camera being unable to connect which I may have sorted at this point.

I really appreciate your builds!
[Nexus 5 Original Android Development] qitt:
Here's the link.
[Nexus 5 Original Android Development] VQ30DE:
I am still having freezes that require hard reboot on myfluxi's 4-15 build. Would love to try Banks' CAF builds if someone can post a link.
[Nexus 5 Original Android Development] :
Let me know how it goes.

http://xdaforums.com/google-nexus-5...12-nexus-5-t3057931/post60021215#post60021215

Thanks. I really didn't change any features or even touch the kernel source. Bluetooth works fine for me. Maybe a CM specific bug?

---------- Post added at 11:45 AM ---------- Previous post was at 11:45 AM ----------

http://xdaforums.com/google-nexus-5...12-nexus-5-t3057931/post60021215#post60021215
[Nexus 5 Original Android Development] jonesy.chris:
That mean your phone was fixed?
[Nexus 5 Original Android Development] el_smurfo:
You don't need a phone to build CM...It does likely mean it is untested when first posted, though this is the most stable build yet for me.
[Nexus 5 Original Android Development] VQ30DE:
Thanks. Just installed along with your 4/16 Gapps and running smoothly so far. Will report back with my experience.
[Nexus 5 Original Android Development] mmo.xda:
Tomorrow will be the day, I hope

http://www.cyanogenmod.org/blog/microsoft-and-cm12-1-nightlies

Regards

Enviado desde mi Nexus 5 CAF mediante Tapatalk
[Nexus 5 Original Android Development] jfim88:
Where i can find these gapss?
[Nexus 5 Original Android Development] :
CyanogenMod member ciwrl just announced that the next nightly queue will be 12.1 based! You can find his post in the comment section of the latest blog on the official CM page. So keep on refreshing your Jenkins page guys! :)
[Nexus 5 Original Android Development] VQ30DE:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 5 Original Android Development] happiness4u:
Jenkins have already loaded the 12.1 nightly at this very moment I post this, but only for some devices. Luckily hammerheadcaf was included to be one of the first to recieve 12.1. cmxlog has also been updated with 12.1 branch. Finally. :D

And the build is broken. :D
[Nexus 5 Original Android Development] *child:
LOL
[Nexus 5 Original Android Development] mshook:
Future of CAF

With the imminent release of 12.1, what does it mean for us users on myfluxi's 12.1 hammerheadcaf builds? We'll be able to upgrade to official CYANOGEN hammerheadcaf builds?
[Nexus 5 Original Android Development] AndrasLOHF:
[emoji20] [emoji20] [emoji20]

Still happy to see the CAF builds will continue.
[Nexus 5 Original Android Development] d1n0x:
I guess so. I'll try to dirty flash as soon as the first nightly drops.
[Nexus 5 Original Android Development] mrbubba999:
Is there a flashable zip to update TWRP for CM12.1 CAF? I don't have access to a laptop at the moment

I did try updating on the cm12 CAF TWRP but it failed
[Nexus 5 Original Android Development] d1n0x:
You could download the .img from the website and flash it in regular TWRP. You just need to toggle between zip and img.
[Nexus 5 Original Android Development] happiness4u:
CM team burst our bubbles. Spoiled our hopes for 12.1. Hahaha!
[Nexus 5 Original Android Development] MaxNXS:
Have I missed something? 12.1 CAF builds are coming, right?
[Nexus 5 Original Android Development] d1n0x:
Yes, but the first nightly failed to build.
[Nexus 5 Original Android Development] jfim88:
Will be nightly today or tomorrow?
[Nexus 5 Original Android Development] mrbubba999:
I keep getting "error updating binary script" when I try and flash 12.1 over 12. I've updated the bootloader that was posted for 5.1 several pages back.

What else do I need?
[Nexus 5 Original Android Development] el_smurfo:
If you're trying to flash CAF, you need the CAF TWRP. I'm not sure which bootloader is required right now for 12-12.1, but the TWRP message should say?
[Nexus 5 Original Android Development] mrbubba999:
In using TWRP for CAF, as I'm already on CM12CAF. I just can't update to 12.1 I just get the update binary script error.

I've downloaded 2 versions of the 12.1, both same error
[Nexus 5 Original Android Development] :
Keep an eye on the Jenkins build queue :)
[Nexus 5 Original Android Development] jonesy.chris:
Somewhere along the way of dirty flashing (I assumed) my MMS and picture messages stopped receiving. I get a message that says "download" when i click on it they don't ever download. I tried hangouts and both google and CM's messaging app, none of them work.

I found an old thread on XDA that mentions verifying APN settings, using the APN settings from here (http://www.att.com/esupport/article.jsp?sid=KB424489&cv=820) did not resolve it for me. I even tried IPV4 and IPV4/IPV6 which was supposedly a fix on another XDA thread.

I have done a wipe and clean load (although I did re-import all my old SMS messages) and i'm still getting the error. Even tried the above APN's on my new load.

Any thoughts?
[Nexus 5 Original Android Development] mbellot:
Have you tried disabling WiFi?

Sometimes custom ROMs don't handle MMS properly when on WiFi since some carriers will download while on WiFi and some carriers will only download MMS when on cell data.
[Nexus 5 Original Android Development] mrbubba999:
It seems lollipop 5.1 comes with a new boot loader which is required to flash CM12.1, I thought I had flashed it, but it clearly didn't work.

Downloaded a separate zip and flashed, all working now.

I tried a dirty flash from 12 to 12.1 just to test it would flash.... not recommended :D
[Nexus 5 Original Android Development] el_smurfo:
You should be able to dirty flash by now. Did you flash 5.1 gapps? There was some sort of telephony bug, but deleting a file and reflashing seemed to fix it.
[Nexus 5 Original Android Development] AndrasLOHF:
Any version jumps on ROMs I always manually wipe system, dalvik, and cache before flashing and have never really had any issues(except when ROM maintainers explicitly state dirty flashing causes issues).
[Nexus 5 Original Android Development] AndrasLOHF:
I is very excite!
[Nexus 5 Original Android Development] el_smurfo:
CM said in their blog post it should be OK...I just seem to see a lot of folks flashing unofficials having some issues...
[Nexus 5 Original Android Development] AndrasLOHF:
Crossing fingers build doesn't fail again like last night.