yashsingh1/xdaforums huggingface dataset:
[ONE General] whitebait:
Also with regards to BT, cm12 had stopped letting me skip tracks fwd and back using physical buttons on my BT head unit.

Skip worked once today on 12.1 and then failed to work after that. Weirdly, it'll still let me fast forward and rewind tracks and if the screen's awake when I press the buttons it lights up my capacitive buttons, so the signal's being received...

That's with shuttle+ and the default cm12 music player. Anyone else having the same issue?
[ONE General] dmbkiwi:
Just one reboot for me. Glad it's not just me. Has this been reported?
[ONE General] jtl5770:
alarm from power off staate working for anyone?

Hi, after I saw on last nights nightly those bunch of RTC and alarm fixes, I was hoping that maybe those could make automatic wake up work from power off (not! quick boot) for an alarm that is about to go off...

But it doesn't work for me - does it for anyone? I have unmodded cm-12.1-20150518 with original kernel and gapps from CM.

I did give my test alarm enough time in the future so it has time to boot up (over 5 minutes), but I only got the "missed alarm" notification afer I finally bootet up again manually. The alarm has been set with the stock cm clock app.

Any ideas or feedback?
[ONE General] novren:
In case screen is not responsive enough to flash it via flashify, could you or anyone make a zip from this to add it to the flashing queue of twrp?
[ONE General] fards:
If the screen is that unresponsive then it would be better to use fast boot.
[ONE General] fards:
I'm not really understanding the mechanics behind this.

Are you saying you want the phone completely powered off but still able to wake itself on an alarm?

How would it know or be able to monitor an alarm off its completely off?
[ONE General] tiny4579:
That could be but there were changes in the kernel side to how wakelocks are functioning. They may be the cause of the reboot and force close issues.

I've had system fc once today and play services crash a few times. I'm allowing keep awake and wakeup in privacy guard for play services now to see if this still happens. If it does, my money is on the kernel changes.
[ONE General] jtl5770:
It's actually an advertised feature of the one+ one. You will find on google people who at least had it working on the stock cm11s or similar, but also people having problems.

Actually if you scan the commit messages for the last nightly, it is even mentioned, and also something along the line that now they somehow don't need the "boot two minutes early so we are ready when the alarm should happen" thing anymore (didn't really understand why, but then I only briefly skipped the messages last night).

For the concrete mechanics - I can't tell how it is done on the opo, but usually you can write a wakeup time into nvram or so and the RTC (that still runs) will boot the device when it's time... maybe done similar here.
[ONE General] Renosh:
This actually used to be a feature of dumb phones (Nokia's, Old Samsung's on Symbian etc) back in the day. They would switch themselves on in response to an alarm just in case you turned it off, and sound the alarm. Never seen it on an android phone, or more correct to say it's never worked for me while on android.
[ONE General] doalittledanse:
This may be a dumb question, but is it supposed to work without quick boot? I would think that it's required.
[ONE General] tiny4579:
For anyone who's had issues with A2DP, I'm compling a build that reverts a possible culprit of the A2DP issues.

This is the change I'm reverting. I have no a2dp issues but this should be fine even if you're having issues as our sampling rate is locked to 44.1kHz per the audio_policy.conf.
[ONE General] tiny4579:
I haven't used this feature, but that's my understanding.
[ONE General] tiny4579:
Try this one guys if you have A2DP issues such as audio speeding up.

https://www.androidfilehost.com/?fid=23991606952606813

It's got the new firmware in it.
[ONE General] rallysquirrel:
Exchange Services battery hog

running 20150515 nightly. I've noticed that in the last 2 weeks of nightlys with Exchange Services fetching email every 15 min, the phone is using much more battery life than it ever has. Exchange Services are using 35% or more of my battery, whereas before Screen would be my biggest memory hog and is now only at 2% with 49min of screen time.

Anyone else using Exchange notice the same thing?

EDIT: Deleted Exchange account, rebooted phone, and added account. Now working fine.
[ONE General] AbootCanada:
My wifis been dropping during sleep mode since the may 17th update anyone else getting this problem?
[ONE General] tiny4579:
No, but apparently it is an issue:

http://review.cyanogenmod.org/#/c/98678/

And that commit also has some comments on what might fix it.

Reverting these fixes it for titan:

https://github.com/CyanogenMod/andr...mmit/0a94e057e526afbee2d993d021025b177aa8c1ef

https://github.com/CyanogenMod/andr...mmit/93e03711c504c75fb2447bc837dd0cd174d335e2

I'd rather not revert these drivers since they seem to decrease battery drain a bit when using bluetooth, or at least supposedly they do.
[ONE General] jay_d_:
For those with random reboots, do you have xposed installed? I uninstalled it (dirty flash of 5/18 nightly without installing xposed) and reboots are gone.
[ONE General] hroo772:
I previously posted my crashlog and I do not have xposed installed. It's been happening for the past week or so, I think it's tied to location wakelocks but I haven't looked in depth just yet.

EDIT: It's all related to google play services, even after wiping /system and installing fresh gaaps. The most recent version is quite crash heavy, even with the wakelocks allowed.

EDIT2: Going back to even older gaaps seems to have mostly solved the issue for now.
[ONE General] fmc000:
No nightly for today:

fatal: git fetch-pack: expected shallow list
error: Cannot fetch platform/prebuilts/qemu-kernel

error: Exited sync due to fetch errors
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 808, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 761, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python2.7/multiprocessing/pool.py", line 337, in _handle_tasks
for i, task in enumerate(taskseq):
File "/usr/lib/python2.7/multiprocessing/pool.py", line 259, in <genexpr>
self._taskqueue.put((((result._job, i, func, (x,), {})
File "/opt/jenkins/android/workspace/android/cm-12.1/.repo/repo/subcmds/forall.py", line 216, in <genexpr>
for cnt, p in enumerate(projects))
File "/opt/jenkins/android/workspace/android/cm-12.1/.repo/repo/subcmds/forall.py", line 157, in _SerializeProject
'lrev': project.GetRevisionId(),
File "/opt/jenkins/android/workspace/android/cm-12.1/.repo/repo/project.py", line 1190, in GetRevisionId
self.name))
ManifestInvalidRevisionError: revision refs/tags/android-5.1.1_r2 in platform/prebuilts/qemu-kernel not found

Build timed out (after 90 minutes). Marking the build as aborted.
Build was aborted
Archiving artifacts
Finished: ABORTED
[ONE General] 1337SereniTyx3:
So this is the 0518 build with TS fix & A2DP fix included?
[ONE General] shrubber83:
This could ne the fix for mobile Active radio bug?

http://review.cyanogenmod.org/#/c/98605/
[ONE General] Renosh:
[MENTION=3500210]tiny4579[/MENTION]

Do you know which commits are responsible for graphic issues in games like Clash of Clans, Boom Beach etc. where menu items within the game have glitches and content is obscured from being seen?

The issue started around/before 23rd of April
[ONE General] tiny4579:
More like what the 5/19 build would be.
[ONE General] tiny4579:
That sounds promising and it was included in my latest build.

No I don't sorry but that timeframe may help isolate this.

I think I heard it was due to the mdss commits around that time which makes sense.
[ONE General] tiny4579:
I know the sync took a while for me last night when I was building. Whatever caused that to be slow must have had an impact on this.
[ONE General] Whookid:
I have been getting random reboots today. (2 so far in a few hours...) and I do not have Xposed installed.

PS: I'm on 20150518
[ONE General] :
same here.

Don't use Xposed and 1 random reboot today (and other 1 yesterday). I'm on May 18 nightly.

Clean install of May 18 nightly and don't use Titanium to recover my apps settings and data.
[ONE General] Renosh:
https://github.com/CyanogenMod/andr...mmit/3a6a9902876bc56655f900468a18d9ed9a5b3b56

Is this the mdss commit you mentioned?
[ONE General] hammer-is:
Yup on 20150518 (running stock CM kernel and not using Xposed) I've got a few "process system not responding" and a random reboot so right now I've reverted to 20150517 (with some battery drain because it has the newer firmware and I'm using dt2w).

Hopefully the nightly tomorrow will be better :)
[ONE General] Enhanced:
Random reboots here as well. Waiting for that 0519 nightly to come.
[ONE General] Spannaa:
No random reboots here on [MENTION=3500210]tiny4579[/MENTION]'s unofficial 0519 build.

Very little unexpected battery drain so far either...
[ONE General] NullyOne:
With 05/18 nightly I had only one randon reboot.

No problems with touch, wifi, LTE and battery seems very good (after 8 hours using Facebook, Viber, Tapatalk, mails, sms is still 81%).
[ONE General] ch-vox:
one random reboot this afternoon while walking with my One in the pocket and one last night on my work desk, I was trying to wake it up, but instead it softly rebooted, without asking me PIN code.

maybe next nightly will fix this little issue....
[ONE General] dark_on_5:
When are the new nightlies published? The page shows the time but not the timezone... :(
[ONE General] fiorellona:
Guys I saw some bug fixes on the changelog of 0518 for the alarm when opo is shutted down (that doesn't work since lollipop 5.0) uploaded from Steve, but the alarm does not yet work nor if the device is under charging nor if it does not. Could someone give me a feedback after a test?

I don't understand what Steve did...

Please let me know what outcomes from tour tests. Thanks
[ONE General] :
What commit exactly? I see like at least 5-6 things that has something to do with "alarm".
[ONE General] fiorellona:
These:

http://review.cyanogenmod.org/#/c/98673/

http://review.cyanogenmod.org/#/c/98672/

http://review.cyanogenmod.org/#/c/98671/

http://review.cyanogenmod.org/#/c/98662/
[ONE General] TorchaOne:
No reboots and maybe a little too high drain but I have problems with BT... it goes on and off couple of times and then stuck off. Only reboot helps. Ofc it might be the profiles, but I had same behavior with llama too. Well not biggie, good build overall...
[ONE General] jtl5770:
I had aasked the same thing in post #1589 - because in my tests it still doesn't work :(
[ONE General] razorloves:
it's UTC
[ONE General] fiorellona:
Yes, the same to me.. It's very strange! Could the problem to be linked to a different recovery installed?

Meanwhile I reported the bug on jira, here you can vote to fix that faster: https://jira.cyanogenmod.org/browse/BACON-3436
[ONE General] hroo772:
Using TWRP 2.8.6.1 and the 5/18 nightly, I actually had this feature occur this morning with my alarm. I have quickboot disabled and the phone was plugged into power all night. The phone was completely off all night and it woke itself up this morning right before the alarm went off, pretty wild stuff.
[ONE General] fiorellona:
Seriously? So it works fine for you? Why this isn't the same to me and to [MENTION=5188028]jtl5770[/MENTION] and many more? Does this feature work everytime to you? Or just when you upgraded TWRP?
[ONE General] flappjaxxx:
I can confirm mad random reboots on 5/18 nightly. Not complaining or asking for fixes just confirming so anyone else that may be having them won't be losing their minds. Dirty flash/upgrade. It's is to be expected on nightlies. I will just revert to 5/17 until worked out. :good:
[ONE General] hroo772:
I don't really think it was in effect for me before I upgraded TWRP. I'll know tomorrow morning for sure but there was never anything I did specifically to enable that feature. I only noticed it this morning when I looked at my battery stats and saw that the phone had been turned off all night and had only been on for a few minutes when I woke up. I do use the built in Cyanogenmod Clock app as my alarm manager if that makes any difference.
[ONE General] fiorellona:
So it was the first time that you used this feature since you flashed cm12.1, right?
[ONE General] hroo772:
I've been continually been using the Cyanogenmod alarm app the whole time, it's just the only time I noticed the phone being off all night but my alarm still going off at the correct time. I did also do a fresh flash of 5/18 with fresh gaaps last night, but I'd think those recent kernel changes were the reason that feature worked on it's own.
[ONE General] runderekrun:
I know others have commented about reboots on 5/18 but is you guys' cache having to be rebuilt every time? My phone has rebooted 4 times today and every time it does the "android is upgrading" on all my apps. Frustrating. Guess its back to 5/17 for now.
[ONE General] flappjaxxx:
Yes cache gets rebuilt etc. I just flashed the 5/17 kernel over 5/18 and so far so good. A lot of kernel changes in the 5/18 build
[ONE General] giaur:
No reboots for me. However, I noticed my phone to be not responding and I was forced to long press power button to hard reset. Then it started to optimize all apps instead of normal boot.
[ONE General] flappjaxxx:
Same here. I have had all of the above crashes, reboots and freezes etc. So far 5/17 kernel seems to be more stable
[ONE General] whitebait:
Exactly the same issue for me just now. It's only happened the once on 1805, but it's pretty frustrating. Anything in the next nightly likely to fix this or shall I dirty flash 1705 over it?
[ONE General] flappjaxxx:
Try flashing just the kernel from 5/17 and you should be good to go.

I just extracted just the boot.img from the zip and flashed it with flashify from the Play Store.
[ONE General] fiorellona:
Let me know tomorrow..
[ONE General] tiny4579:
That may resolve the issues if it's kernel related, but I also reverted the 5/18 kernel commits and added the updated WiFi driver.

I built two versions:

This is with the new touchscreen firmware.

https://www.androidfilehost.com/?fid=23991606952607294

This is with the older touchscreen firmware

https://www.androidfilehost.com/?fid=23991606952607293

I've only directly tested the first but the touchscreen firmware is the only difference between the two. I'd recommend the second one if you don't need the new firmware and want to use double tap to wake without the increased drain.
[ONE General] Enhanced:
Is this 0519 nightly never gonna come out?
[ONE General] tiny4579:
No it failed, there may be one tonight but I haven't seen one. I wouldn't be too excited about it as there are still some issues to resolve.
[ONE General] mhaner:
The Bluetooth worked great for me. Tested it on my lunch and the entire drive home(over an hour) with zero Bluetooth issues.
[ONE General] tiny4579:
How was it before? Did it have playback issues. One of the cm guys said this revert fixed the Bluetooth playback issues for him and I wanted to validate it to hopefully get it reverted and have these fast playback issues/audio speedups resolved.
[ONE General] runderekrun:
I have the Bluetooth audio sped up issue detailed here:

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-3275

I can test any kernel for you tomorrow. Currently on 5/17 nightly.
[ONE General] mhaner:
I had both the sped up/pitch issue and it would cut out every 15 or 20 seconds before. The issue had been present on pretty much every Lollipop ROM I had tried. I have had a couple of Random Reboots also. Mainly it seems like if the phone has been asleep for awhile then I go to wake it up, it will reboot.
[ONE General] giaur:
No new nightly again?
[ONE General] PlayersHeaders:
Bug Report

Hi, the energy saving mode dont work, it buggs very much
[ONE General] bommel_23:
Touchscreen issue still not fixed with 12.1

I switched from CM12 to CM12.1 Nightlies to get rid of the touchscreen issue but I still have probs with the touchscreen. Has anyone the same problems?
[ONE General] fmc000:
LOL, post of the YEAR! Please read the last few pages and then get back here if you need more details.
[ONE General] bommel_23:
Ok, so it will come within the next nightlies or I have to manually flash the posted boot.img images.
[ONE General] fiorellona:
So? Did the alarm work this morning?
[ONE General] jtl5770:
I would also be highly interested, given the fact that for me it doesn't work (neither on nor off charger)... But I also have an additional question - is it really possible that the recovery in use has any influence on this feature working?
[ONE General] franticjohny:
If someone manages to build unofficial please upload. I have a horrible RILJ wakelock and cannot go back to 12052015 because the device loops creating art cache.
[ONE General] dolphin77:
Hi. Appreciate that you build and share with all of us. Thank you.

Can you please advise why is your nightly build cm-12.1-20150519-UNOFFICIAL-bacon.zip (is ~ 265Mb) is 30Mb smaller then the official build cm-12.1-20150518-NIGHTLY-bacon.zip (is ~296 Mb)?
[ONE General] Spannaa:
[MENTION=3500210]tiny4579[/MENTION] built cm-12.1-20150519-UNOFFICIAL-bacon.zip and it's running fine here.

It's smaller than the nightlies because it doesn't contain all of the firmware - just system & boot.
[ONE General] fiorellona:
I don't think so.. However what do this mean http://review.cyanogenmod.org/98845?
[ONE General] tiny4579:
Try one of my boot.img files posted earlier.
[ONE General] benj!:
+1 it's running really well, actually. Battery life has been a huge improvement over previous nightlies
[ONE General] TorchaOne:
Huoh, since this 241 radio I have had lots of troubles connecting to wifi and mobile data, just leaving the wifi might cause the all data to stop, even if I go back to wifi just ! stays... and all this even if everybody is praising this new radio :) Anyway, I have had even more problem when moving, signal is close to poor all the time. Closing the screen seems to poison atm. Yeah, I did fresh when moving to new radio... maybe that was the fail. Am I alone?
[ONE General] giaur:
No such problem for me on latest official nightly.
[ONE General] TorchaOne:
All nighties since 241, well, I tried to wipe... complains that format access /firmware.... now booting to something... gee, going to be long evening. (back to older version of twrp and voila)
[ONE General] giaur:
I have no problems. Also no more random reboot problem, it happened for me inly one time. All stuff is pretty stable so far I'm waiting for next official build
[ONE General] NullyOne:
Same for me :)
[ONE General] hroo772:
Well my alarm went off just fine this morning but I'm not so sure about the phone turning itself off overnight. Looking at my battery stats the phone has been on all night, the thing that hinted to me about it last time was looking at the temperature readings which made it seem like the phone was off, as there was a huge gap in data overnight. Sorry to get you guys excited, I think it was real the other night but I'm not sure it happened overnight last night.

The only thing I have noticed more and more is that the phone seems to put itself into a deep sleep and I have to reboot the phone fully to get it back and working. In the context of these sleep alarms, I get the feeling that the phone is just turning itself off into that sleep state and I just didn't know how to get it back without the hard reboot. Last night before I went to sleep it was in that turned off state, and when I only held the power button for a few seconds, it actually turned itself on like it had just been in a hibernate mode. So I still have suspicions that the behavior still exists and works, but currently it's a little over-eager as to when it wants to turn itself off.
[ONE General] fiorellona:
That's very strange...
[ONE General] pijas82:
hi

cyandelta, no thanks, loooool , bugs, bugs , bugs bugs...........................
[ONE General] gondsman:
Guys, cyandelta produces the SAME ZIP you can download from the cyanogenmod website. It doesn't cause bugs per se. Delta downloads have been around for DECADES, they are perfectly fine (chances of them not working are the same as having a bad download for the nightly zip, actually less as there's less data to download). The only thing which can happen is that the nightly gets pulled by CM for whatever reason and it stays in the cyandelta servers, but that would be the same if you downloaded it during the time it was up on CM servers. For perfect safety you can check with the CM updater if there is an update (to make sure it's still up on CM side) and then download it with cyandelta.
[ONE General] critofur:
So if I have a One with touch screen problems, that is my best bet for now?

(I don't understand why Oneplus has not released a new "firmware fix" with the battery drain issue resolved, it's been DAYS since we found out about the problem!).
[ONE General] flappjaxxx:
I can confirm that 5/18 with 5/17 kernel has been running for me for over 24 hours without a single issue.

I've uploaded the boot.img

Download it here.

http://rootdev.org/boot.img

Flash it with flashify from the play store.

No more resets/reboots etc.

No more rebuilding of cache yada yada
[ONE General] giaur:
Not the same zip, delta and not full. I don't trust it
[ONE General] TorchaOne:
Fresh install and now I have those hands, need to force reboot and optimizing ongoing... what the ... is going on. Everything until this 241 and firmware stuff was working. Not anymoreee :crying:
[ONE General] NullyOne:
When I made a fresh install with wipe data/cache/system, I had long optimizing ongoing.

Wait for somebody who knows to have a better reply :)
[ONE General] TorchaOne:
Yeah, thats for sure... but 1 hour after fresh, phone was totally dead, had to longpress power to get reboot and went through optimizing... Hope it

stays alive for night so it wakes me up.. as the alarm do not work when powered off.
[ONE General] runderekrun:
Are you on 5/18 nightly? If so it is known to have rebooting problems. Either flash back to 5/17 or just flash 5/17 boot.img posted by flappjaxxx four posts up or so.

EDIT: Sorry didn't mean to quote both of you.
[ONE General] Longi94:
Dirty flashed 0518 over 0515, and now my device randomly soft restarts every now and then. Bummer... I hate factory resetting :(
[ONE General] runderekrun:
http://xdaforums.com/showpost.php?p=60857277&postcount=1671
[ONE General] tiny4579:
Look at my boot.img from a couple pages back.
[ONE General] TorchaOne:
Need to try that... hopefully at morning there is a new one waiting :)

Edit: 5/17 (or for me 17/5, heh) is stable enough. Even got rid of network connecting problems.
[ONE General] gondsman:
This is simply false. Cyandelta downloads a small "delta" file that contains the modifications between the two nightlies. It then uses this file and merges it with the old nightly to generate the new one. The file you flash in recovery is always the full zip, which is the same file you can download with the official updater. You can open it and compare the contents if you want.
[ONE General] rasobey:
I feel it's worth me admitting my mistake (I posted a few weeks ago about a nightly bootlooping on me.) to help others who fail to read.

My problem stemmed from not re-flashing the 5.1 GApps package after flashing a nightly, be it a cyandelta ZIP or full ZIP. Once I overcame my "durrr" moment I was all set to go.

tl;dr - read the OP.
[ONE General] usmave:
my alarm works nice when the phone was shut down. tested with the build in alarm on 18th nightly.

and it was completely shut down, only long-hold power button woke it up. no standby mode or stuff like this.