• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[DISCUSSION][ROM][5.1]CyanogenMod 12.1 for Bacon[OFFICIAL Nightlies]

Status
Not open for further replies.
Search This thread

fiorellona

Senior Member
Nov 11, 2014
64
24
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?

I had aasked the same thing in post #1589 - because in my tests it still doesn't work :(

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
 

hroo772

Senior Member
Jul 16, 2014
71
41
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
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.
 
  • Like
Reactions: fiorellona

flappjaxxx

Senior Member
Apr 8, 2009
3,844
11,431
Somewhere, FL
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:
 

hroo772

Senior Member
Jul 16, 2014
71
41
Seriously? So it works fine for you? Why this isn't the same to me and to @jtl5770 and many more? Does this feature work everytime to you? Or just when you upgraded TWRP?
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.
 
  • Like
Reactions: Lar5

hroo772

Senior Member
Jul 16, 2014
71
41
So it was the first time that you used this feature since you flashed cm12.1, right?
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.
 

runderekrun

Senior Member
Apr 28, 2009
975
152
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.
 

flappjaxxx

Senior Member
Apr 8, 2009
3,844
11,431
Somewhere, FL
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.

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
 

whitebait

Senior Member
Jul 23, 2012
142
23
London
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.
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?
 

flappjaxxx

Senior Member
Apr 8, 2009
3,844
11,431
Somewhere, FL
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?

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.
 
Last edited:

fiorellona

Senior Member
Nov 11, 2014
64
24
hroo772 said:
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.

Let me know tomorrow..
 
Last edited:

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,328
5,060
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.

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.
 

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,328
5,060
The Bluetooth worked great for me. Tested it on my lunch and the entire drive home(over an hour) with zero Bluetooth issues.
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.
 

runderekrun

Senior Member
Apr 28, 2009
975
152
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    CyanogenMod 12.1 (Android 5.1) Official Nightlies Discussion Thread

    CyanogenMod tries to build a new, fresh "nightly" version every 24 hours for each of the devices it supports, which includes the most up-to-date changes to the source code, provided from all over the Internet. Of course, the nightly builds may also contain newly-introduced bugs, but hey- if you feel adventurous, you can help make CyanogenMod better by trying these experimental builds and reporting back bugs to the developers.

    Source: wiki.cyanogenmod.org


    Changelog:
    http://cmxlog.com/12.1/bacon


    Download Links:
    1. CM12.1 ROM: http://download.cyanogenmod.org/?device=bacon

    2. Android 5.1 Gaaps:

    Flashing Instructions
    Comprehensive installation instructions for CM on the OnePlus One can be found on the CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_bacon

    Note: If you are flashing from CM11/CM12, you MUST flash 5.1-compatible gapps after flashing the ROM!

    1. Download the nightly and move it to your SD card.
    2. Download gaaps and move it to your SD card. [This step is optional.]
    3. Reboot into the custom recovery of your choice.4A. Flashing dirty from CM11/12: Wipe cache/dalvik cache.
    4B. Flashing clean: Full wipe.
    5. Flash cm-121-2015xxxx-NIGHTLY-bacon.zip.
    6. Flash gapps.zip. If flashing dirty from CM11/12, then you must reflash 5.1 compatible gapps (link above).
    7. Reboot

    For those having problems with apps crashing:
    1. If you didn't wipe cache / dalvik-ART from recovery when you flashed 12.1 over 12.0, go back and do that first.

    2. If you still have FCs, go to Settings » Apps, find the offending app and click Clear data.

    3. Still no go, time to do a factory reset.


    Rooting:
    This is a pre-rooted ROM, so there is no need to flash SuperSU!

    1. Enable Developer options by going to System » About tablet and clicking Build number rapidly 5-7 times.
    2. Under Developer options, click Root access and select Apps only, then Ok.

    That's it!


    Known Issues:
    (I will keep this updated)
    • Camera still splits the exposure when using the flash
    • You tell me
    25
    Starting from CM12.1 today's nightly, a new sound panel is included in power menu, whose source code has been written by me.
    To enable it, go to Settings - Buttons - Power menu and enable "sound panel".
    This sound panel is available for all devices supported by cm12.1.
    If you have problems, please let me know.

    http://review.cyanogenmod.org/#/c/100452/
    11
    post to androidfilehost, that seems like a great place for a rom.

    1. Too much work for a one-off.
    2. My DSL connection is currently rather flaky, so uploads probably wouldn't finish (thanks AT&T...)
    3. With all these things, there nowadays unfortunately are too many people asking for support, and I have neither time nor patience for that.

    I may upload it to my own webserver. I prefer to be in control... But that depends on my DSL connection staying up...

    Update: It should now be available via torrent:
    http://www.feise.com/~jfeise/Downloads/cm-12.1-20150521-UNOFFICIAL-bacon.zip.torrent
    md5: 2c8383584fd2ccc451969e9836fcd36d cm-12.1-20150521-UNOFFICIAL-bacon.zip
    10
    When will be ready CM13.0 for OnePlus One?
    Exactly some number of minutes after soon.
    10
    For the new CM 12.1 nightly (post 20150418), you have to use the official Cyanogen recovery for properly restore your current GApps. An alternative solution for now, a modified TWRP with current CM 12.1 kernel (f2fs support included): http://goo.gl/G2T5yY Please check http://review.cyanogenmod.org/#/c/95349/

    Too lazy to set up TWRP recovery build for now, please tell TWRP developer about this transparent lz4 compressed ext4 issue.