[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

Search This thread

Ok_Kaleidoscope5109

Senior Member
Dec 29, 2009
2,624
709
Same here. If it's under heavy use, it's hard to pass 3h SOT. I call bull**** to those 4 or 5 hours SOT. They probably don't even use the phone that much and set the brightness to the lowest.

Sent from my Nexus 4 using xda app-developers app

TBH SOT means nothing. I can achieve 6 hours SOT doing nothing, reading an e-book. Anandtech achieved 6 hours SOT on AOSP doing their wifi battery test. So what? Under 3G its significantly less.

We can't compare SOT unless we compare it with the same benchmark. For more information see my sig. I ran a test between CM kernel and Franco and I found little difference. Granted it was under constant CPU load because the battery benchmark wasn't perfect.
 

jphilippon

Senior Member
Apr 15, 2012
983
501
Same here. If it's under heavy use, it's hard to pass 3h SOT. I call bull**** to those 4 or 5 hours SOT. They probably don't even use the phone that much and set the brightness to the lowest.

Sent from my Nexus 4 using xda app-developers app

Auto brightness, only turned on WiFi 2 minutes before. Mostly browser, auto updating the Kings game, xda, social networks.. Not my definition of light usage. Could probably stretch this to 5.

sent from my Mako
 

Attachments

  • uploadfromtaptalk1370588520943.jpg
    uploadfromtaptalk1370588520943.jpg
    65.9 KB · Views: 817
  • uploadfromtaptalk1370588529652.jpg
    uploadfromtaptalk1370588529652.jpg
    49.4 KB · Views: 820

Planet X

Senior Member
May 10, 2008
1,471
504
Amersfoort
Auto brightness, only turned on WiFi 2 minutes before. Mostly browser, auto updating the Kings game, xda, social networks.. Not my definition of light usage. Could probably stretch this to 5.

sent from my Mako
You get the most screen on time when watching battery usage every few minutes :laugh:. When using my phone as a smartphone I can use it almost two days. But screen on time is mostley ~2 hours. That not bad at all for a smartphone these days.
 

saint_cow

Senior Member
Sep 25, 2011
820
94
It could just be my carrier playing up but on the latest nightly people are getting the same message from me multiple times. Flashed back to stock and it doesn't happen.

Sent from my Nexus 4 using xda app-developers app
 

azrash

Senior Member
Sep 18, 2010
1,221
669
Kuala Lumpur

stefabax73

Member
Oct 28, 2007
30
4
Background on lockscreen

Hello, using last nightly 20130607 I have an issue with lockscreen backgroud.
Using different image for lockscreen background not work, I choose a different image, but it show always the same of the home screen.
Anyone have found this?

Stefano
 

drewsky208

Senior Member
Dec 6, 2008
206
150
Hello, using last nightly 20130607 I have an issue with lockscreen backgroud.
Using different image for lockscreen background not work, I choose a different image, but it show always the same of the home screen.
Anyone have found this?

Stefano

Yes a commit yesterday appears to have broke that while fixing another issue. There is a commit going in tonight that will correct it: http://review.cyanogenmod.org/#/c/43919/

Just hang on until tomorrow's nightly :)
 

Ok_Kaleidoscope5109

Senior Member
Dec 29, 2009
2,624
709
Is the data usage bug still present? My phone used 773mb of data today when all I did was go to a meeting. I can understand the 100mb of so it claims I used on tethering because I pulled emails through VPN at the meeting at the customer, but the 300mb that Hangouts used overnight? I highly doubt it... same with the 170mb that Pulse used.
 

drewsky208

Senior Member
Dec 6, 2008
206
150
Is the data usage bug still present? My phone used 773mb of data today when all I did was go to a meeting. I can understand the 100mb of so it claims I used on tethering because I pulled emails through VPN at the meeting at the customer, but the 300mb that Hangouts used overnight? I highly doubt it... same with the 170mb that Pulse used.

That bug was fixed log ago.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 893
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.2 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.

    Instructions:

    First time flashing CyanogenMod 10.1 your device, or coming from another ROM?
    1. Download the zip(s).
    2. Optional: adb backup
    3. Fastboot oem unlock > fastboot flash recovery recovery.img.
    4. Perform a NANDroid backup of your current ROM.
    5. Wipe data & cache partitions of your device (required when coming from stock!).
    6. Flash CyanogenMod.
    7. Optional: Install the Google Apps addon package.
    Issues?

    Experience issues? As these are nightlies, bug reports are not accepted. You are relying on yourself and your peers in this thread for support!

    Download Links:

    CyanogenMod:
    Nightly:
    Download: link

    Google Apps addon:
    Use 4.2 gapps:
    Download: link


    GENERAL COMMENT AND REQUEST:

    We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"

    Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).

    We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.

    Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.


    The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
    54
    GENERAL COMMENT AND REQUEST:

    From now on, can we ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"

    Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).

    We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.

    Just clearing data etc may in fact cause us to never find the bug that caused the issue and makes for lazy users.
    53
    All,

    Please remember that Nightlies are experimental builds and even though we have been lucky thus far that Nexus builds have been fairly stable, we can, and many times do (remember the GPS issue last week), break things in Nightlies.

    4.2.2 just got merged this morning and the builds, even for Nexus devices, are not 100% functional yet. Give it a day or two for the device maintainers to work out the kinks and stabilise things.

    Please STOP flashing bootloaders, radios, kernels and random 4.2.2 builds and wait patiently for another 24 to 48 hours for things to be sorted out. It won't kill you to wait but it might kill your device if you rush things.
    48
    I'll get flamed for saying this, but the problem with CM is that they've become another OEM skin. The reason it takes so long for Samsung, HTC, Motorola, etc. to update phones to a new version of Android is because of all the customizations they do. Their customizations conflict with AOSP so they have to re-integrate them. Well CM is now in the same boat. it is so highly customized that new versions of Android break their code base.

    If anyone remembers when ICS came out, that was the best example of this. It took the CM team so long to port their customizations to ICS, that Jelly Bean ended up being released before CM 9 (ICS) was officially released. They did a better job with Jelly Bean, mostly because the changes to Android weren't as big.

    I love CM, and it is always my ROM of choice. But they've strayed so far from their original vision of bringing AOSP to the masses. They are now just another custom OEM skin that retains the AOSP look and feel. I appreciate everything they do and love the customizations, but unfortunately it makes it harder for them to keep phones up to date.

    /end rant

    Unfortunately you don't know what you are talking about. CM is not, and never will be "an OEM skin".

    Our 'customizations' have very little to do with how long it takes to merge a new version. There are many, many other factors that contribute, including ensuring it works well on the many, many devices we support.

    Yes, its not always an easy process to bring our features over - especially when Google completely re-architects parts of the system (like lock screen in 4.2) but then if you want AOSP, why don't you just install AOSP?

    Insulting the CM team is not going to make the 4.2.2 merge go any faster, in fact, it may just delay things, why should even I bother spending my personal time adding a feature to CM (like cLock or Quick reply etc.) when this is the type of response it gets?
    46
    Re: [ROM][Official][4.2.1] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

    General comment:

    There are probably a few things broken in the current nightlies similar to the quiet hours issue from yesterday. It will take us a few days to check everything and fix the parts of the merge that did not quite come out right.

    If you notice any old cm10.1 functionality that now no longer works quite the way it should (like the quiet hours issue) please post it here and I will look out for it.

    Please don't ask us to fix things that were broken before. We need to get this build to pre-merge state first.

    The rest of the month is focused on stability and bug fix in anticipation of the next M release.