yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mckennal:
Thx for the links, I'll go do some reading and see if I can figure out how to capture the logcat just prior to a reboot.

If I get annoyed enough with the reboots I may try it. I certainly had no problems any time on stock before going to CM, so would have to be a very unlucky coincidence to be a hw problem I think.

Thx

Luke
[Samsung Galaxy Nexus] AgentSmith:
Just talking from personal experience. And yes I could do frequent factory resets to keep Android snappy if that is what you want to say but I'm pretty sure that more recent phone models with 2-3 GB of RAM and much faster processors don't show the same degradation in user noticeable performance between resets. In the end it's user experience that counts, not theory.
[Samsung Galaxy Nexus] soder:
Strange question, but what nightly version since 4.4.4 do most of you guys recommend? As I said before, I was on 0624 and 0622 and went back to 0622. But I still find the phone kind of laggy, all over the place.

Don't know if it's since I switched to ART (yeah, yeah, I know that ART isn't "supported" in CM11 yet), or if I'm at bad builds.

/Söder
[Samsung Galaxy Nexus] sq3htu:
Since saturday I'm running 0621 nightly on my GNex. So far so good. Dirty flashed (cache & dalvik wipe) from M7 Snapshot.
[Samsung Galaxy Nexus] soder:
And it's 4.4.4?

/Söder
[Samsung Galaxy Nexus] sq3htu:
All builds since 0619 are 4.4.4 based. I've also changed kernel to Dirty-V URSR from 0615.
[Samsung Galaxy Nexus] soder:
OK, thanks.

What version is the most stable do you say? As I said, since I just switched to ART the phone is strange. =) That, or the version of CM11 I use.

Has anyone tried 0625, and can say it's better then the two prior?

/Söder
[Samsung Galaxy Nexus] sq3htu:
I didn't try newer builds after 0621, it's running fine for me so I stay with it.
[Samsung Galaxy Nexus] soder:
OK. Well I switched to 0621, and for me it's still extremely slow. =( Guess it has to do with the switch to ART. No one else that made the switched and noticed something like this?

EDIT: Might not be as slow as the other versions. Will try this and see...

/Söder
[Samsung Galaxy Nexus] allblackt:
I'm on M7, switched to ART a few days ago and noticed that it's slower and less responsive than Dalvik. Applications were slower to start, switching between applications was laggy and waking the phone by pressing the power button was sometimes not working immediately, I had to press a few times in order for the phone to respond. Switched back to Dalvik and all these problems are not present anymore.
[Samsung Galaxy Nexus] soder:
Hmm, OK, interesting. Is it possible that ART on CM is generally not as good as on "stock" android? I've heard others saying it's "incredible fast" and stuff like that?

Or should we wipe or something like that to see the glory?

/Söder
[Samsung Galaxy Nexus] allblackt:
I tested ART before, on a nightly, a few months ago and it was snappier than Dalvik. I'm waiting for more information about this as well, probably a stable version of ART.
[Samsung Galaxy Nexus] soder:
Is there no way to use theme but not change everything that's changes with styles? Like only the layout of the navigation buttons, but not color and stuff?
[Samsung Galaxy Nexus] AgentSmith:
What are the experiences here with recent nightlies?
[Samsung Galaxy Nexus] DomieMic65:
I am on 0623 with no obvious problems, except some lags now and then! Nothing very annoying...

I won't go to another nightly though, I will wait for the next stable and if everything is going well I will stick with it for quite a long time!
[Samsung Galaxy Nexus] acloh0411:
i am using Gapps-kk-20131208. Any thing to do with Gapps or Greenify?
[Samsung Galaxy Nexus] pablomoreno:
I can declare to all my unconditional love!
[Samsung Galaxy Nexus] pianistaPL:
Are you using latest Nightlies or M7? If Nightlies, you have to install 4.4.4 gapps, for example Banks gapps http://xdaforums.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
[Samsung Galaxy Nexus] a3361035:
Wanting actual proof has nothing to do with theory. All your feelings could be simple placebo or caused by something totally unrelated. We need reproducible use cases with logs.

No, CM doesn't touch libart.

Not really. Rip it out manually.

Those aren't ART-compatible afaik due to odex files. Use 20140606.

http://wiki.cyanogenmod.org/w/Gapps

Personally i prefer PA-Gapps due to PA-Gapps-Remover but those are moving targets with their weekly updates, which might introduce new bugs.

So fixed "CM Gapps" are generally recommended.

There's no source for L Preview. So that's pretty pointless and not really a port.

CM will merge L when there's actually something to merge.

Gapps don't really correspond to Android point releases and update themselves.

Don't use Banks as those aren't really compatible with maguro:

http://xdaforums.com/google-nexus-5...imal-gapps-t2012857/post52543072#post52543072
[Samsung Galaxy Nexus] AgentSmith:
Every theory needs verifiable proof so when you're talking about the latter you are asking for the former. With daily life user devices it's the experience that counts and experience is difficult to catch in numbers or theories. Everyone's experience is valid to that person. That is true for all of us and you are no exception.
[Samsung Galaxy Nexus] mckennal:
I noticed something I thought was strange with my "reboots" - the uptime is not interrupted by these "reboots". Perhaps I could describe my reboots and someone more knowledgeable might be able to help. I am sometimes using the phone, sometimes not, and the phone will appear to reboot - all of a sudden the CyanogenMod startup animation will come on, but the phone returns to the lockscreen quicker than a full shutdown/reboot of the phone.

I have read fair portions of this thread, but not all. I saw mention of the "System UI" crashes, but ignored most of it because I went straight to M7 and thought this issue was fixed. Is what I'm experiencing a "System UI" crash? If so, are there any known fixes or known apps that may cause it?

Apologies if it's already covered in this thread somewhere, I did a search but couldn't see anything.

Thx

Luke
[Samsung Galaxy Nexus] aswinrulez:
I'm getting green lines appearing at the side of the screenwhere the video is cropped or ends in my mxplayer after updating to latest nightly
[Samsung Galaxy Nexus] Sdobron:
This is why I keep finding myself going back to Omnirom... Faster, lighter and more stable for me.
[Samsung Galaxy Nexus] a3361035:
That's not how the scientific method works.

Missing logcat/kmsg.

Missing any proof.

Omni uses an old CM device tree and is without a maintainer and near dropping support for maguro completely. [1]

[1] Andrew Dodd aka Entropy512 in https://plus.google.com/107222470150379447280/posts/iKrDTGYYfb6

In other news:

Google Play Services 5.0.xx causes wakelocks in CM (prolly in any custom rom). Fix merged on Jun 29:

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

Usually Google takes weeks to complete the rollout of an update (which can be uninstalled again), so M8 will likely arrive before you get 5.0.xx, if you don't sideload.

Edit:

Some possible temp fix:

http://xdaforums.com/showpost.php?p=53767086&postcount=6535
[Samsung Galaxy Nexus] xergio24:
I know this is OT and I also know I have no proof but... are you Sheldon Cooper or something? xD

BTW: thanks for the "news"... I am experiencing wakelocks with the new Google Play Services... so now I'm searching for 5.0.82 to see if they fixed the wakelock in that version (I'm using 5.0.77 now).

EDIT:

5.0.81 here - Android Police (safe)

5.0.82 here - "android zone" (not sure if 100% safe)

EDIT 2: BEWARE, this apks are for 480dpi phones, and Maguro is 320dpi... so they may not work well.
[Samsung Galaxy Nexus] AgentSmith:
You are seriously denying that theories need proof? You do know the world isn't flat do you...?
[Samsung Galaxy Nexus] CYoung234:
I also find myself using Omni quite a bit these days. I am not sure what type of proof you are looking for that it is faster, but my phone consistently benches faster on AnTuTu with Omni than running CM11, around 1000 points faster in fact. Running the same kernel on both (franco R396 - the fixed version). At 1536MHz and Interactive, I get around 13500 on Omni and around 12500 on CM11. I will try to post some screenshots of this or will run a different benchmark if you prefer.
[Samsung Galaxy Nexus] Sdobron:
Sorry man but you're trolling. The proof that Omni being lighter than CM is that it doesn't have theme manager and other CM 'features'
[Samsung Galaxy Nexus] a3361035:
The gerrit review talks explicitly about 5.0.81 causing it.

Don't think google will "fix" it as it's not their problem. CM has disabled SystemUpdateService, so new SystemUpdateService$Receiver goes amok.

Those apks are the wrong ones. -038 is for 480 DPI devices, maguro is 320 DPI, so needs -036. [1]

A possible workaround if you really want Play Services 5.0.xx for M7 or older nightlies might be:

http://xdaforums.com/showpost.php?p=53767086&postcount=6535

[1] http://xdaforums.com/showthread.php?p=51813198

There aren't any good benchmarks for Android to measure actual responsiveness. Even measuring raw power is hard and it's certainly not AnTuTu, which still can be easily fooled. (sic Anandtech or [0])

Anyway strange that the results are different as those should be very much kernel dependent. I guess CM's performance profiles [1] combined with your overclocking will trigger thermald sooner, thus lowering your clockspeeds to not overheat. Or some bug in the custom kernel. Got logs? (logcat/kmsg)

How did you even find that OC value? Are you sure your device can sustain those max clockrates for longer periods, i.e. actual gaming not benchmarking, without overheating?

P.S. Neither custom kernels [2] nor overclocking [3] is recommended.

[0] Asinine things like disabling fsync because you cares about lost writes as long as it's faster or the recent mpok ram "optimizations": http://xdaforums.com/showpost.php?p=53251528&postcount=10062

[1] http://review.cyanogenmod.org/#/c/64254/

[2] https://plus.google.com/+SteveKondik/posts/S1c2HQJPhJU

[3] not in CM stock kernel for a reason; along the lines of: http://review.cyanogenmod.org/#/c/35504/

Picking some random feature from some ROM and proclaiming it's bloat is not how this works. Omni has its own features not in CM.

The actual reason Omni doesn't have a theme manager is lack of time - nothing else. [1]

In fact - tho somewhat dated - Omni devs doubt it being more responsive than CM. [2]

KitKat did get procstats, at least provide those for both ROMs. [3]

Also you claimed more than it just being lighter and didn't even try to provide any form of justification now.

[1] http://xdaforums.com/showpost.php?p=48546993&postcount=2

[2] http://xdaforums.com/showpost.php?p=49902995&postcount=10

[3] http://android-developers.blogspot.com/2014/01/process-stats-understanding-how-your.html
[Samsung Galaxy Nexus] Sdobron:
Your referenced posts aren't even fact. They're developer opinions.
[Samsung Galaxy Nexus] xergio24:
Well... I was using 5.0.77 at first and I also had the SystemUpdateService wakelock... and I'm also having it with 5.0.82, so I will try with that workaround! =)

And about DPI... you are right! I have the "wrong" version... but it seems that it is working fine without counting that wakelock problem that seems to happen to everyone, not only CM users (that's why I said that Google should fix it).

Anyway... thanks!
[Samsung Galaxy Nexus] a3361035:
This is not the Nexus 5 thread and your problem is Nexus 5 specific.

Anyway it got fixed:

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

===

New features incoming:

Make settings searchable:

https://plus.google.com/+CyanogenMod/posts/ZHQ2z3Xs3aL

Merged on Jul 1:

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

Add left and right virtual buttons while typing (to move the cursor):

https://plus.google.com/+RomanBirg/posts/MKmB2EmkQXo

Not merged yet:

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

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

Somewhat late:

PhotoPhase Live Wallpaper:

https://github.com/CyanogenMod/android_packages_wallpapers_PhotoPhase/blob/cm-11.0/README.md

Merged on Jun 23:

http://review.cyanogenmod.org/#/c/65828/
[Samsung Galaxy Nexus] aswinrulez:
Sorry about that. I was wondering where my post went in the nexus 5 thread :D
[Samsung Galaxy Nexus] CYoung234:
A couple of things. First, without some way of measuring actual responsiveness, I guess all of this is just conjecture. If there really is no test that provides some real measure of responsiveness, then we are wasting each others time. I do not know why Omni measures better than CM11 with AnTuTu running the same franco kernel at the same settings; it just does. Subjectively, it feels faster in terms of UI responsiveness. As one example, when I open recent apps and kill all of them, the response is faster in Omni.

Second, the settings I quoted are not daily driver settings. I only use them for benchmarking. I keep clock speeds stock for normal use. Omni measures faster at stock clock speeds as well. I do not use my phone for gaming, so I could not comment on sustained use. I do not experience reboots at that clock rate while testing. In terms of providing logcats / kmsgs, I could provide them, but it is more time consuming to set the phone up to generate them for both environments than it is worth. Not sure what, if any payback from doing this would be.

Finally, please do not think that my post is intended to bash CM11 in any way. I like CM11 and have used it extensively. I will likely continue to use it in the future, especially if support for OMNI dries up, as it appears it may.
[Samsung Galaxy Nexus] KreNtal:
Installed today's nightly with Google Play Services' (5.0.XX) fix but phone still doesn't go deep sleep :( Any tip?

EDIT: After some reboots it went deep sleep yuppie
[Samsung Galaxy Nexus] Kustaa:
Any report about today's nightly? How is searchable settings working?
[Samsung Galaxy Nexus] x3m.zone:
I have just tryed both ROM's (CM and Omni), with own defaults settings and kernels (no OC or something else), and i also confirm that Omni is faster in terms of UI responsiveness (ex: switching betwen apps and scrolling).

I will try to make a 1:1 comparation video.

PS: all respect to CM and Omni guys for the great job!
[Samsung Galaxy Nexus] KreNtal:
Today's nightly is working really well for me, I don't see any bug at all. Search in settings is working really really well too, I think it's useful sometimes. Thanks CM
[Samsung Galaxy Nexus] a3361035:
Change of schedule for M8:

https://groups.google.com/forum/#!topic/cyanogenmod-dev/8oi0enuYGfk

Don't update to any new nightlies beyond 0701 if you want to switch to M8.
[Samsung Galaxy Nexus] RevengeFNF:
Im using the nightly from 21 of June with Google Services 5.0.82. I don't have any Deep Sleep problem.

The problem of the deep sleep persists on today nightly? Just trying to know if its better to stay with the nightly im at the moment of if i can safely update.
[Samsung Galaxy Nexus] a3361035:
CM Roadmap

More: http://www.cyanogenmod.org/blog/the-l-is-for-later
[Samsung Galaxy Nexus] Darklife1337:
sorry guys for the stupid question, maybe someone already had that problem and i missed the post but:

at the moment i'm using the 06/13 N, yesterday after the google play services autoupdate (5.0.84) i started to have problems with the deep sleep, in 9 hours my phone just had just 1.32minutes of deep sleep and for the rest still active, is a bug services/rom so i have to update to a new nightly or is just a google bug?

after a better search found that a3361035 post and i think is my problem

"Google Play Services 5.0.xx causes wakelocks in CM (prolly in any custom rom). Fix merged on Jun 29:

http://review.cyanogenmod.org/#/c/66894/"

so time to test the 06/29 build ;)
[Samsung Galaxy Nexus] Haik0:
Proximity sensor problem

Is there any chance Cyenogenmod team can fix the proximity sensor driver for this device ??

It's a very "popular" problem, a lot of ppl are having the problem with screen going off during the call and never coming back on (till the devices is restarted), most of the time it will just restart after a while being in a screen off stat .

Anyway,, the problem is with the proximity sensor driver, after disabling it,, the problem is going away, but by disabling the proximity sensor the light sensor is also being disabled so it's not the best solution, I thought maybe someone from Cyonegenmod can re-write that driver ?? !

p.s. this problem is persisting as on a stack ROM, as well as any build of the CM

Thanks
[Samsung Galaxy Nexus] loeb87:
Immersive Mode Bug

for if I have a problem with the immersive mode, when you turn the games Risco not to recall the navigation bar and the status bar with the swipe down!:(
[Samsung Galaxy Nexus] KreNtal:
I disabled it w/o disabling the light sensor as well.

How did you disable it?
[Samsung Galaxy Nexus] Haik0:
xposed

There is a Module for Xposed Framework called "Disable Proximity Sensor" also I tried to do it with "Hardware Disabler" (app from Play Store). There is a some sort of flashable Fix for this here in XDA forums, but I didn't try that, all though I've read that it's also disabling the light sensor.

Anyway,, would be so great if this could be fixed just by simpley having it working instead of disabling stuff.
[Samsung Galaxy Nexus] a3361035:
This is neither the place to report bugs, nor is that even a proper bugreport without a logcat:

http://wiki.cyanogenmod.org/w/Jira
[Samsung Galaxy Nexus] Haik0:
...

Go read the original post by abalam, where it stated, that: "CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 kitkat(KTU84P), which is designed to increase performance and reliability over stock Android for your device." >>> Well obviously when the your system is restarting after every phone call, that can not be called very much reliable, can it ?? ....

and then the original post continuous, by sating "What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here" >>>>

So, here I am discussing it here ! I am not submitting a bug report, cuz I am just trying to start a discussion about the well known issue with this devices, that's all !

So ! This is neither the place for you to ***** about things, nor you are being to useful to this Discussion and you are not even being funny for that matter.
[Samsung Galaxy Nexus] a3361035:
That's about nightlies and unofficial.

If you want official CM support use Jira like the official CM wiki says.

Also stop implying things like it's well known - when there isn't even one proper bug report - or some driver's fault without proof.

===

In other news:

Android Police featured the new searchable settings:

http://www.androidpolice.com/2014/0...s-search-feature-adds-it-to-latest-nightlies/
[Samsung Galaxy Nexus] KreNtal:
Probably you own, like me, a galaxy nexus c8 model (take a look underneath your phone battery for the model code and also make a search on Google), these models have a problem with motherboard and proximity sensor. Cyanogenmod is unable to replace your motherboard or your sensor, the only way I found to fix or at least reduce unexpected reboots is to flash this: http://xdaforums.com/showthread.php?t=2016338; it will disable ONLY the proximity sensor and it works for me. However before asking for non-sense stuff make a search on your own. Peace out.
[Samsung Galaxy Nexus] Haik0:
?

Will this solve the problem if I replace the proximity sensor only ?
[Samsung Galaxy Nexus] gsfores:
I had the same problem. Changing the motherboard solved it.... Like KreNtal said, c8 batch has problem with the proximity sensor.
[Samsung Galaxy Nexus] Haik0:
what to replace, Proximity sensor or entire motherboard?

My question is,, will I solve the problem JUST by replacing the Proximity sensor, or should I replace the entire motherboard ???

To replace just the sensor will cost a lot less then the entire motherboard, so If you are aware of the specifics of this problem pleas let me know, if I should order just the sensor of the complete motherboard ?!

Thanks
[Samsung Galaxy Nexus] gsfores:
I dont know. i replaced the motherboard without trying to replace only the sensor.

But the old sensor stayed inside so I guess its the motherboard problem.....
[Samsung Galaxy Nexus] NCguy:
I'm just seeing GT-I9250. No letter designators. Is it part of the SSN or S/N? BTW, I'm also not yet experiencing the problem. Just want to know if I'm a victim.
[Samsung Galaxy Nexus] KreNtal:
Yes, you have to check the 4th and 5th digits/letters of the serial number (S/N) and they stand for year and month of the phone's manifacturing C8 is august 2012
[Samsung Galaxy Nexus] a3361035:
Still missing a proper bug report and jumping to conclusions.

Merged on Jul 2, but not cherrypicked for M8:

https://github.com/CyanogenMod/android_frameworks_base/commits/stable/cm-11.0

Some fix for it merged on Jul 3:

http://review.cyanogenmod.org/67287/

Android Police featuring it:

http://www.androidpolice.com/2014/07/03/cyanogenmod-adds-leftright-cursor-keys-to-the-nav-bar/

===

Preview M8 compared to M7:

Branched on Jul 1, release expected Jul 7:

https://groups.google.com/forum/#!topic/cyanogenmod-dev/8oi0enuYGfk

So updating from nightlies till 0701 should be okay.

Trebuchet improvements mentioned for M7 actually merged

Trebuchet: Move settings to new slide-out panel

Trebuchet: Consolidate settings for home and drawer options

http://review.cyanogenmod.org/64118/

Android 4.4.3

Notable changes: Updated the Chromium based WebView to version 33

https://github.com/CyanogenMod/android/commit/22455b9031a02f1bfc3ee33102d9c85bf1f60f5e

Android 4.4.4

Notable changes: Nothing. CM already had the OpenSSL CCS exploit (CVE-2014-0224) fixed in M7

https://github.com/CyanogenMod/android/commit/476441b8a55a7fc13eed76d35132c58f01de6bbd

Add compass tile

http://review.cyanogenmod.org/64243/

Features from Last Week in CM: Jun-19-2014 (more details in link)

Trebuchet: Protected apps

http://review.cyanogenmod.org/65076

http://review.cyanogenmod.org/65317/

http://review.cyanogenmod.org/65318/

Trebuchet: GEL integration

http://www.androidpolice.com/2014/0...test-nightlies-just-like-google-now-launcher/

http://review.cyanogenmod.org/64793/

Heads-Up (floating notificatiions)

http://www.androidpolice.com/2014/0...n-aosp-enables-them-in-latest-cm11-nightlies/

http://review.cyanogenmod.org/64793

Settings Re-org

generic “Interface” category replaced by ‘Status Bar’, ‘Notification Drawer’ and ‘Gestures’

Expanded desktop under Display category

Lock screen items under ‘Lock screen’ category,

Navigation Bar layouts under ‘Buttons’.

https://github.com/CyanogenMod/android_packages_apps_Settings/commits/stable/cm-11.0

Blacklist for Heads Up

https://plus.google.com/+CyanogenMod/posts/W76rpyvdgCG

http://review.cyanogenmod.org/66380/

http://review.cyanogenmod.org/66379/

HeadsUp: Add heads up quicksettings tile

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

PhotoPhase Live Wallpaper

https://github.com/CyanogenMod/android_packages_wallpapers_PhotoPhase/blob/cm-11.0/README.md

http://review.cyanogenmod.org/65828/

Fix Google Play Services 5.0.xx wakelocks

http://review.cyanogenmod.org/66894/

Make settings searchable

https://plus.google.com/+CyanogenMod/posts/ZHQ2z3Xs3aL

http://www.androidpolice.com/2014/0...s-search-feature-adds-it-to-latest-nightlies/

http://review.cyanogenmod.org/66711/
[Samsung Galaxy Nexus] mckennal:
FYI for anyone on M7 or nightlies before the Google Play Services 5.0.xx wakelock fix that might be waiting for M8 before flashing a new build:

I started getting the SystemUpdateService wakelock issue that caused significant battery drain (no deep sleep) yesterday and used the workaround described here in the first post here:

http://xdaforums.com/showthread.php?p=53843098

From what I've read this workaround does not survive reboot.

Luke
[Samsung Galaxy Nexus] AgentSmith:
I recommend the 0701 nightly. It fixed the wakelock and it's the last nightly from which you can still hop over to M8 when it is released.