yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AgentSmith:
My phone is completely screwed up since M6. I even missed an alarm in the morning causing me to be late at work. Not complaining but how long before they fix the latest milestone? I don't want to go back to nightlies as I thought I'd be safe from problems like these. I simply don't have the time anymore to fiddle around with ROMs often. :)

Things like this make me wonder if I ever use custom ROMs again. I know how much effort people put in them. It's just that in the end phones have to be usable in the real world and I thought that milestones would use that as a starting point. Either I'm mistaken or someone clearly screwed up. ;)
[Samsung Galaxy Nexus] CYoung234:
Hmm... When you try a nandroid, TWRP tells you in advance how much data you are backing up. I have about 170 apps on my phone, and the data for a typical nandroid is only a bit larger than 1GB. The whole nandroid is in the 2GB range, and takes maybe 10 minutes to make, so not a big deal.

On another note, have you tried clearing cache and resetting data on the specific apps that are getting messed up when you change versions?
[Samsung Galaxy Nexus] soder:
Welcome to the club. My advice.

1. Get Titanium Backups of your userapps, and some of the system apps that you trust can be restored with TB.

2. Wipe that f-ing phone, flash M5, gapps and all other stuff you want. Maybe even a zip for TB.

3. Boot up, fix some settings, do not log in to Google. Reboot.

4. Restore apps with TB, then login in to Google.

5. From now on, wait also with the M-releases. =)

/Söder

---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------

When I went back to M5 from M6, there wasn't just "apps" that was f-ed up, it was a lot of system settings that was gone and stuff like that. never mind. I'm back at M5 now, with a wiped phone, restored most of my user apps with TB, and might be good until the next f-up. =)

/Söder
[Samsung Galaxy Nexus] NCguy:
I know that you can't always follow every post. In the case of M6 there were several posts here that were predicting, prior to its release, an all but certain disaster with M6 due to the state of the profile code. It was enough warning for me to stay clear until actual usage reports emerged.
[Samsung Galaxy Nexus] RcrdBrt:
I confirm that from 09 may nightly the bug appears to be finally fixed. Flashing 09 over M5 adds the phone perceptible smoothness and speed when multitasking

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Kustaa:
I think you're making a lot of drama lol. Me? I'm on 04/10 nightly and it works perfect. And yeah, it's safe to wait for anyone comment before flashing somethinh new...but hey! Someone has to do it. Besides, we're flashing phones! With custom sh#t! And if you wanna new radical features, well...things like this can happen. They'll sort it up at some point.
[Samsung Galaxy Nexus] cidefix:
I switched from m6 to 11-20140510 nightly two hours ago and the UI just crashed again pulling down the notifications... Not fixed. :(

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] AgentSmith:
The reason I started using milestone builds was that I wouldn't have to follow this topic too closely. Apparently I was wrong. ;) I'm flashing nothing until a proper fix is released. Can't be bothered to invest time in all sorts of workarounds so I'll put up with the bugs for now. I'm sure it won't be too long.
[Samsung Galaxy Nexus] RcrdBrt:
I'm on 10 may nightly right now and I don't have any issue I had with previous nightly. It's really strange.

I dirty flashed over M5 and I had no app problems at all. Sounds like something really weird for me if someone is having problems even with today's nightly.

Would you mind wipe data and then flash 10 may nightly again?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] revanmj:
I don't see anything related to the Theme Engine memory usage and crashes in the changelog so my guess is that after some time you are going to have issues with this nightly ;)
[Samsung Galaxy Nexus] NCguy:
I won't even flash a google OTA without checking the comments. Guess I don't trust anyone.
[Samsung Galaxy Nexus] pepifness:
Sometimes my phone freezes for about 5 to 10 seconds in some applications with the version from 8,9 and 10052014 . I made clean install and full wipe from stock JB 4.3

Sent from my Galaxy Nexus using Xparent BlueTapatalk 2
[Samsung Galaxy Nexus] RcrdBrt:
Still running flawless

There were some dalvik and framework changes.

Maybe the problem is theme manager code that broke something else. In fact I decided to abandon the M5 for this reason. And it seems I was right

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] agritux:
Just continue using. It starting to freeze and crash after (much) notification comes.
[Samsung Galaxy Nexus] luckana:
The latest nightly still has the ui bugs, reverting to m5 back again dirty over the nightly ****ed up my device :D the home button was not working, i couldnt recieve phone calls and many more.. Had to fully wipe and now started with a clean m5 build.. I dont think of flashing anything now unless its 100% ui bug free proved
[Samsung Galaxy Nexus] KreNtal:
Can't play .wav anymore on latest nigthly, do you? O.o
[Samsung Galaxy Nexus] CYoung234:
Well, I wiped and installed the 5/10 nightly, and so far (23 hours) it has run flawlessly. Process stats say SystemUI is behaving itself, and so far the max has been 69Mb of RAM used. Don't worry, I have an M5 Nandroid to go back to if needed.

UPDATE (5/12/2014): Well, I spoke too fast. SystemUI still showed 69Mb maximum memory, but I ran the fill free RAM program this morning, which worked okay. While I was navigating back to Developer Options to check the memory stats, the phone rebooted and went into the SystemUI FC loop. It is actually sort of fun, because if you are fat enough, you can still get your phone to reboot into recovery in between these messages... :) At any rate, I reverted back to M5 for now...
[Samsung Galaxy Nexus] Nelson George:
Nice Rom to try ...!

i am now using 20140509. i am very happy with that. it is far more better than m6. and i got no problems with theme chooser.

and also i like the new theme chooser engine. but i think it needs some more work.

sometimes it crashes, when i selected particular option,

but i dont care about that.

great job guys...:good:
[Samsung Galaxy Nexus] PrimeDirective:
There's a LOT of other custom ROMs out there bro. You should give some a shot since you don't know what you're missing
[Samsung Galaxy Nexus] RevengeFNF:
http://review.cyanogenmod.org/#/c/63867/

Something related?
[Samsung Galaxy Nexus] revanmj:
To the issues some people were having with SystemUI crash on opening notification tray. But nothing about high memory usage here.
[Samsung Galaxy Nexus] dirtyreturn:
I flashed the may 10th build after a data/dalvik/cache wipe and restored my apps that I use. Things work fine here at least for the time being. I had been dirty flashing and up until the beginning of may I think all things were working that way. I have noticed that Google apps are already in the ROM without flashing a separate gapps package. (((??)))
[Samsung Galaxy Nexus] NCguy:
Wonder if becoming qualified with the one plus one they now have permission to include them?
[Samsung Galaxy Nexus] m.is.for.michael:
You're probably just seeing the results of the addon.d backup scripts.

sent from my brain using telepathy
[Samsung Galaxy Nexus] m.is.for.michael:
Latest nightly seems to have fixed the notification shade bug

sent from my brain using telepathy
[Samsung Galaxy Nexus] sq3htu:
What's your uptime with this nightly? ;)
[Samsung Galaxy Nexus] dirtyreturn:
Do you flash clean? If not, have you had any 'problems'?
[Samsung Galaxy Nexus] agritux:
Yes it is fixed now! i confirm that. i am on carbonrom latest nightly and it has this commit too. i dont have any fc or freeze today.
[Samsung Galaxy Nexus] m.is.for.michael:
9.5 hours or so so far.

Flashed dirty over 12 th. No major problems. It is a bit laggy and the keyboard swipe is a bit hit and miss, but I think that's indicative of low RAM. Will try freezing some apps.

sent from my brain using telepathy
[Samsung Galaxy Nexus] m.is.for.michael:
OK so after about 12 or 13 hours I started getting them again when pulling down the shade, but a reboot fixed it (temporarily, I presume). I guess there's some sort of memory leak involved in addition to the npe which was squashed.

sent from my brain using telepathy
[Samsung Galaxy Nexus] Conte Mascetti:
Here http://review.cyanogenmod.org/#/c/63806/

From GNexus
[Samsung Galaxy Nexus] djMesias:
Thanks! I'll try it in my own compilation.
[Samsung Galaxy Nexus] onnaj:
Mine is also slowing down after 24 hours usage and random freezes :( Hope the devs tackle the problems soon. It is better though then with the m6 snapshot

Verstuurd vanaf mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Conte Mascetti:
So... did you try this in your own compiled cyanogenmod? Does it solve anything? I think I'm going to try your rom :o

Does it support italian language?
[Samsung Galaxy Nexus] djMesias:
For now, all issues are gone. But sorry, I'm compiling this ROM in English & Spanish only.

Enviado desde mi Nexus 5 mediante Tapatalk
[Samsung Galaxy Nexus] Conte Mascetti:
Toooo bad ?

From GNexus
[Samsung Galaxy Nexus] CYoung234:
Tethering ERROR on 5/13 NIGHTLY

In the 5/13 NIGHTLY, with a clean install, tethering fails with an error screen. Here is a screen shot as well as a log. Oh, this is running Franco r396 kernel. Tethering works fine in the same config with SNAPSHOT M5.
[Samsung Galaxy Nexus] n1kolaa:
That kernel is not supported,so report on kernel theard plz use stock cm for reporting bugs/errors :)
[Samsung Galaxy Nexus] CYoung234:
So this is a kernel issue? I don't believe so, but I will reload with the stock kernel to test this. I appreciate your position, though...
[Samsung Galaxy Nexus] n1kolaa:
from first post:

Reporting Bugs

You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
[Samsung Galaxy Nexus] CYoung234:
Thanks, but I already indicated I would be doing this.
[Samsung Galaxy Nexus] kompressorgpl:
Hello! After the last 3 nithlys, the mx player, the apk dosent "see" the videos on the "sdcard". Nor the music apk...
[Samsung Galaxy Nexus] EDNYLaw:
This is a nightly issue. I was using the nightly with Franco kernel and tethering failed. I went back to M4 with the same kernel, Franco 396, and tethering worked just fine.
[Samsung Galaxy Nexus] Conte Mascetti:
Hopefully crash for sliding down notification is finally solved! Take a look here http://review.cyanogenmod.org/#/c/64114/

From GNexus
[Samsung Galaxy Nexus] revanmj:
So, this fixes lags, high memory usage and SystemUI crashes?
[Samsung Galaxy Nexus] CYoung234:
Agreed. I went back to a nandroid of M5, uninstalled franco r396. Tethering worked. Re-installed franco r396 and tethering is now working. So, I believe it is an issue with more recent nightlies.
[Samsung Galaxy Nexus] Stamgastje:
So far, the nightly of May 17th is running very smoothly here. :)
[Samsung Galaxy Nexus] revanmj:
I'll wait few more days for confirmation. Don't want to do a full wipe for nothing :)
[Samsung Galaxy Nexus] m.is.for.michael:
Same for me.

I dirty flashed the 17th and running fine so far.

sent from my brain using telepathy
[Samsung Galaxy Nexus] basf:
+1
[Samsung Galaxy Nexus] cujo6801:
By that time something else will be broken.... Lol

Sorry I couldn't help myself.:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] revanmj:
I know, but I doubt it will be such a big issue like the ones with new Theme Engine. I personally haven't encountered so serius bug that would take so long to get fixed (and that would land in a stable channel) since I begun using CM (version 7.1 I think).
[Samsung Galaxy Nexus] RevengeFNF:
Last version finally working fine.
[Samsung Galaxy Nexus] pianistaPL:
Wow, new nightly is so damn fast with SmittyV kernel... Of course this is only after hour of using but it seems really good. I removed Theme Manager because i don't need it so i shouldn't have any problems. Let's see...

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] NCguy:
Got to wonder if they will start the two-week M version this month? If they have it stable now might not be a bad time to start.
[Samsung Galaxy Nexus] m.is.for.michael:
17th nightly running smoothly still after more than 18 hours. No freezes or reboots.

sent from my brain using telepathy
[Samsung Galaxy Nexus] TrainRekS:
No data connection.

I first installed M6 with a full wipe and lost my data connection. Everything works except mobile data. I then tried the latest nightly build May 17th. and the same thing occurs. I flashed back to 10.2.1 and my data connection came back. I am using ATT Has anyone else had this issue?
[Samsung Galaxy Nexus] kompressorgpl:
How did you did that?
[Samsung Galaxy Nexus] pianistaPL:
You mean theme manager? I deleted it via Root Explorer.
[Samsung Galaxy Nexus] 0s1ride:
After 23hrs of usage on the 17th nightly, no more notification-related crashes, nor system ui memory leaks.

It still uses more ram than M5, though (I didn't use to have so many launcher reloads), but it's definitely a step in the right direction.
[Samsung Galaxy Nexus] AgentSmith:
I simply disabled Themes provider in apps. Seems to have the same effect. :)
[Samsung Galaxy Nexus] kompressorgpl:
Hello! Just tried that now and dosent work...
[Samsung Galaxy Nexus] Sdobron:
The memory leak is in systemui not themes provider. This won't do it
[Samsung Galaxy Nexus] Droiderat:
Am using cm-11-20140517-NIGHTLY-maguro (w/DirtyV) and it works well. No crashes or freezes (2+ days).

Am on Dalvik. When I first installed it, I tried ART (which is what I prefer), and I immediately got repeated "systemui.apk has stopped." Had to do a full wipe and reinstall.

Is anyone successfully using cm-11-20140517-NIGHTLY-maguro (or later) and ART? If yes, I will Nandroid and try again.
[Samsung Galaxy Nexus] catalin.v:
The same happened to me. You can manually switch to Dalvik by pulling libdvm.so via adb and pushing it back after you edit it, so you won't need to reflash.

The thing is ART is that I didn't see a major performance boost, faced some annoying bugs after a while, I don't find it stable enough at the moment for daily use.
[Samsung Galaxy Nexus] Droiderat:
I assume that you mean pulling libart.so (so the system is forced to default to libdvm.so), and pushing it back after the system has switched back to Dalvik. Yes?

Or would it simply be possible to edit build.prop (from Recovery) to switch from ART to Dalvik?

I find ART snappier, and have been using it for months (most recently with cm-11-20140411-NIGHTLY-maguro ... where I stayed until the 5/17 nightly fixed the crash issues).
[Samsung Galaxy Nexus] RcrdBrt:
now that the systemUI seems to be fixed, I think there is a need for a fix also with the famous "screen-off music microlag".

listening to the music and switching off the screen reports an audio lag.

I think it has been there since cm11 (i remember with cm10 there was a commit that fixed it).

am I the only one still having this issue?
[Samsung Galaxy Nexus] nickdc986:
I'm with you.
[Samsung Galaxy Nexus] :
audio bug

Its very annoying when listening to music, yeah.

A fix would be nice
[Samsung Galaxy Nexus] gsfores:
yea this lag is totally annoying!:eek:
[Samsung Galaxy Nexus] onnaj:
I have a pretty big lag when going back to the home screen. Pretty annoying but it disappears after a reboot. I'm on the 18th nightly

Verstuurd vanaf mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] m.is.for.michael:
Hey, does anyone know if CM11 is meant to support MHL (ie micro USB -> HDMI) cables? I bought one off eBay but it doesn't seem to work and I'm not sure if that's because the cable's faulty or the ROM doesn't support it.

sent from my brain using telepathy
[Samsung Galaxy Nexus] Sdobron:
I don't remember having this issue on cm10. It was introduced with audio tunneling in Android 4.4 I believe... It seems this is a very low priority to fix as the issue only occurs on some older devices I believe.
[Samsung Galaxy Nexus] AgentSmith:
I use an MHL cable with this rom regularly. No problems whatsoever.
[Samsung Galaxy Nexus] daasguy:
No vib feedback with all vib options enabled

For some time i had the system error i wont let me do anything but restart fixed it.

but now for almost 2 nightlies i have no vibrate option there isnt any thing. no vib feed back. i remember there was an option in settings>device>more (missing vibrate options)

edit: went back to 15may nightly and installed update. now vibrate feedback is back to normal.

back to using stock kernel was using franco r395 and i guess its causing problems as nightly progresses.
[Samsung Galaxy Nexus] scorpeeon:
I have M6, it's usually OK but sometimes the phone gets absolutely unresponsive for about half a minute, then it goes back to normal. I understand this is the systemui bug mentioned here?

Anyway, today I experienced a more serious issue that didn't occur before (not just with this ROM, with any previous M-release): it started with a random reboot while the phone being idle (i just happened to notice, this also never happened before btw) then after booting the systemui began to crash in a never-ending cycle, i think both the navbar and status bar were gone, it was really weird. After a long vol+/- and power button combo, I could reset it and turn it on, then it was back to normal, though my background picture got changed to the default CM one.

I don't think I can provide logcat since I had to forcefully restart the phone. Anyone experienced something like this?
[Samsung Galaxy Nexus] luckana:
-_- this has been discused one thousand times already
[Samsung Galaxy Nexus] michierusama:
And its fixed by now I think. On 017/05 nightly.
[Samsung Galaxy Nexus] catalin.v:
Sorry, I wasn't precise, this is the way to do it:
[Samsung Galaxy Nexus] xergio24:
I also use an MHL cable sometimes with no problems...

It's important however to mention that you should also plug the USB end, to the TV or any other source of "power"... it won't work without it (at least in my case).
[Samsung Galaxy Nexus] scorpeeon:
You mean both problems mentioned? The later seemed rather rare/interesting...

Thanks for confirming!
[Samsung Galaxy Nexus] michierusama:
The systemui issue is fixed.
[Samsung Galaxy Nexus] xergio24:
And what does that have to do with my comment? xD haha
[Samsung Galaxy Nexus] michierusama:
Omg lol wrong person sorry...

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

Systemui issue is fixed. Lol.
[Samsung Galaxy Nexus] Kustaa:
So...is it all back to normal? Or is there still some memory leaks?
[Samsung Galaxy Nexus] Darklife1337:
normal ;)
[Samsung Galaxy Nexus] Kustaa:
Ok, I flashed today's nightly, and there's no unlock sound...weird
[Samsung Galaxy Nexus] michierusama:
I am on 05/20 and I will stay there until M7 is launched. :)
[Samsung Galaxy Nexus] michierusama:
05/20 nightly with extended battery.

With stock kernel and Neph settings on whats possible to tweak.
[Samsung Galaxy Nexus] Darklife1337:
had the same problem with the 05/17 build, no sounds at all and many fc, flashed the 05/21 and now seems ok
[Samsung Galaxy Nexus] rtimoff:
Is there any recommendations for color settings?

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] -=W1S3=-:
IMHO 69 67 100

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] [sito_web]:
What colour are u talking about?
[Samsung Galaxy Nexus] rtimoff:
Thanks, and what about gamma correction?

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] -=W1S3=-:
Never touched it... LOL
[Samsung Galaxy Nexus] n1kolaa:
big thanks i was looking for this since i get manguro :)
[Samsung Galaxy Nexus] t3ej4y:
Is anyone experiencing a Google Play services log in error? I can access any other site on data except for play services, hangouts, g+ won't load, just came back to the gnex after a stint on the moto x and upgraded to m6, my signal bars are permanently orange as well (not connected to google services). Any solutions or suggestions?
[Samsung Galaxy Nexus] johnflorin:
M6 has some truly horrible issues, upgrade to the latest nightly and you'l be much, much better off.
[Samsung Galaxy Nexus] soder:
Would it work to install a new nightly today, and still go for M7 in about a week or two, without any of the "problems" that might happen when going from nightly to milestone?

How long before a milestone is new features stopped, and only bug fixes happens.. And, also, how come the bad theme engine was in M6?

/Söder
[Samsung Galaxy Nexus] winamp26:
hi guys

how to add icons in new theme engine?

is it support nova/awd or ... icons pack?
[Samsung Galaxy Nexus] rtimoff:
No, I don't think so. Icons must be included in theme. Or, this icon packs(for Nova, Apex...) must be reworked specially for new theme engine.

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] skyleth:
Really how do you achieve that? I have extended battery and my phone doesn't reach more than 3h of screen and not more than 12-14 hours in total before having to charge it. I have M6 and Dirty-RV with Nephilm's settings, although I think I have a bit more OC

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] TrainRekS:
Still no Data om ATT

I can not get data to work on cyanogenmod 11. I have tried the past two snapshots and all of the nightlies up until now. I do a full wipe every time I install. All of the other kitkat roms work fine when it comes to mobile data. Does anyone else have this problem or know of a solution?

I am on ATT
[Samsung Galaxy Nexus] michierusama:
I was sleeping the day before that and well the rest was like from 11 am to 7:30 pm using it normally. Chat music and some youtube.
[Samsung Galaxy Nexus] KreNtal:
Really? I have that screen time with stock battery. Maybe your battery is gone..
[Samsung Galaxy Nexus] luckana:
I am also starting to think that my battery is gone, i always have problems with battery life and it might be time for a new one :(
[Samsung Galaxy Nexus] skyleth:
The battery is almost new. The 1750mah one I know is gone, now it has around 1500mah or less probably, but the extended one is good, is almost new. I've never had such a good battery life. Not even at the beginning. Maybe I have too many accounts synchronized (3 Google, 2 exchange, 1 outlook, Facebook, Skype and probably something else I'm forgetting) and more than 150 apps, so maybe that's why, or is the only possible explanation I have

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] KreNtal:
I don't use to have sync always on, I switch it on only once a day.
[Samsung Galaxy Nexus] zackpack:
Could you be so kind to link the neph thread? i can't find it, ty
[Samsung Galaxy Nexus] skyleth:
http://xdaforums.com/galaxy-nexus/general/nephilims-custom-kernel-settings-thread-t2401653
[Samsung Galaxy Nexus] zackpack:
thanks, the problem now is to find a link for 05/20 nightly :confused:
[Samsung Galaxy Nexus] skyleth:
did you check here https://download.cyanogenmod.org/?device=maguro?

or go to the update section in your gnex and select to show all updates instead of new/stable

I have one question guys, i'm currently using TWRP, but I want to try CWM again. is it saving the nandroid backups still in that weird place or now you can find them in the "sdcard" folder?
[Samsung Galaxy Nexus] zackpack:
Obviously I've already tried before post my question. There is no 05/20 version.
[Samsung Galaxy Nexus] mundavincicode:
sorry if i ask something like this.

where can i find a changelog?

sorry again if i ask.
[Samsung Galaxy Nexus] onnaj:
Please please read the first and second post before asking such a question and polluting this topic.