yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] revanmj:
[ROM] [NIGHTLY] [4.4] CyanogenMod 11 KVT49L for Samsung Galaxy Nexus [GSM]

We know they are trying to fix it. The problem is, it's not resolved for now and yet they still put it in the M compilation, which was supposed to be more stable than nightlies so people could use as a daily driver. And new theme engine so far causes so much lags and restarts of the system.ui process that it can't be used as a daily driver.
[Samsung Galaxy Nexus] xergio24:
Where did you get that the new theme engine is included on M6?

I have just dirty-install M6 over M5 and I'm not seeing it anywhere.

-BTW, everything seems fine for now-
[Samsung Galaxy Nexus] revanmj:
First from people that flashed it and then from CM official blog.

It was already said before - use it for at least 12 hours and then say if it's fine or not. Memory leaks caused by the new theme engine usually don't reveal themselves earlier.
[Samsung Galaxy Nexus] sq3htu:
Installed 30 mins ago ;) Will see what's gonna happen during the day ;)

I'm also running custom kernel - DirtyV.
[Samsung Galaxy Nexus] dehein:
I don't run Franco Kernel anymore. somehow it killed some programs for me and i had to reinstall them. so bwfore testing a custom Kernel on this build, just test the build

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Darklife1337:
installed now the m6 le'ts see..
[Samsung Galaxy Nexus] agritux:
With some CM 11 themes, some texts not shown. This bug known as nightly bug. Maybe we can say it isnt a bug. Because old themes and new theme manager isnt compatible. It is present in M6 now. So we can say new theme manager merged for M6 build. I hope there is no notification drawer and lockscreen bug.
[Samsung Galaxy Nexus] bomba6:
Would like to know if:

1. Phone still freezes when you pull down the notification bar?

2. If not, if a user is not using any other theme (but the default one), would he/she be affected by the new theme manager bugs?

Thanks!
[Samsung Galaxy Nexus] pedmond:
Thank you for that info. A quick question - are there any UI restarts?
[Samsung Galaxy Nexus] agritux:
I dont have until now. Flashed it this morning. Only used about 3-4 hours.
[Samsung Galaxy Nexus] qwertzboy:
I have ui reboot's when i pull down the status bar. Not always but since i flashed m6 this morning i got this bug 3 times. This sucks.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] pedmond:
That is sad... I guess I'll stick with S5 for a while.
[Samsung Galaxy Nexus] agritux:
Clean install?

Flashed over M5?

Flashed over nightly?
[Samsung Galaxy Nexus] Sdobron:
Bugs happen with default theme. The freezes with notification bar are intermittent... Once every couple hours at most. It's a daily driver still...
[Samsung Galaxy Nexus] AgentSmith:
Same problem with the M6 snapshot. Several freezes in the last half hour. Too bad I flashed before I came to read here. Is there an easy fix without dirty flashing a complete M5?
[Samsung Galaxy Nexus] qwertzboy:
Flashed over m5. Wiped cache and dalvik.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] soder:
What's the biggest changes from M5 to M6?

/Söder
[Samsung Galaxy Nexus] drunkenmastera:
i flashed it cleanly and no issues so far.
[Samsung Galaxy Nexus] pedmond:
That's good news - thanks. I'll try that.
[Samsung Galaxy Nexus] nickdc986:
Same here.
[Samsung Galaxy Nexus] aosp:
VanirAOSP awaits ?
[Samsung Galaxy Nexus] xergio24:
You were totally right... I'm still not seeing the new theme manager but I started to have problems with the ROM so... I guess I'm going back to M5.
[Samsung Galaxy Nexus] rootyourdroid:
I finally upgraded from the 01/2014 version. I need to update my kernel, can anyone suggest the newest kernel that will work well with this? My battery life has been horrible lately as well as signal strength.
[Samsung Galaxy Nexus] revanmj:
That's because they merged only theme engine so far (backend in other words). New UI for managing themes should land in nightlies next week (they said it in the blog post about M6).
[Samsung Galaxy Nexus] NCguy:
I'm sure glad this thread exists. I'd be on M6 right now and have wasted a day going there and back. Thanks to all.
[Samsung Galaxy Nexus] Atento:
Best ROM ever since CM merged this borked theme manager.
[Samsung Galaxy Nexus] kukky:
so...you don't have system.ui crashing with m5....it it?
[Samsung Galaxy Nexus] Darklife1337:
dirty flashed m5 to m6 7h ago at the moment no problems.
[Samsung Galaxy Nexus] rootyourdroid:
What is best kernel to flash over this for best battery life? Or am I better off using what is already cooked into the rom?
[Samsung Galaxy Nexus] pianistaPL:
Franco kernel is good for battery.

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] rootyourdroid:
Thanks, I think that's what I have now but I will have to check if there is an update.

Another question - are their radio updates I need to install for Gnex? I'm coming from thunderbolt where we had radios, wondering if that has something to do with weaker signal?

Also, I just looked at my battery stats and for some reason its showing like 80% bluetooth usage, even though I don't even use bluetooth. I just made sure it was disabled which it already was, so kind of confused on that too.
[Samsung Galaxy Nexus] xergio24:
Ohh I see... thanks for clearing that up!

So you are saying that M6 clean install works well? Can you confirm it after 12+ hours of use?

Anyone else reporting the same?

Thats right, no crashes on M5.
[Samsung Galaxy Nexus] drunkenmastera:
well i flashed it since 7am. It's currently 2:30 here so far it has work fine. I was using the new launcher btw, inspire if that got to do with anything.

I'll report more tomorrow.
[Samsung Galaxy Nexus] catalin.v:
Is ART stable now? Haven't used for two months, because the GPS stopped working for me on ART. I know that it caused a bootloop in a previous nightly. Is is usable now?
[Samsung Galaxy Nexus] KreNtal:
I didn't know about all these problems with new theme engine. After flashing m6 this morning I noticed strange reboots after using chrome and even strange systemui loop restart so now I know that's related to the new theme engine. Really sad for all these problems, i'm switching back to m5 that works like a charm.
[Samsung Galaxy Nexus] gsfores:
same problem here, on m6 dirty install systemui restarts.
[Samsung Galaxy Nexus] NCguy:
Well, M6.5 could be out in 2 weeks according to the new strategy. Let's hope they get it stabilized.

BTW, do you have to install consecutive M builds to avoid a clean wipe?
[Samsung Galaxy Nexus] KreNtal:
I don't really understand these M builds 'cause they're more buggy than nightlies -.- before M11 I used to flash every single nigthly without problems... But now, don't know if is my GN or cyanogenmod but things are going worse and worse.
[Samsung Galaxy Nexus] Nelson George:
little buggy...

i installed m6 last night. everything seems right. but i had a strange reboot once. i am always using extended desktop. but sometimes it is not working. it makes me to swipe so many times for navigation.

another strange problem is after installing this rom i installed pa gapps. it removes cm launcher, browser, msg etc...

i had a bad habbit. i am not the fan of google now / launcher.

so i always remove those apps from system and replace with apex or nova. its working fine in slimkat build 4.

but in cm if i remove google now launcher or cm launcher or google search.........it ends with blurry wallpaper. strange is't ?

because of this i flashed this rom again and again to find-out.

but after all i like this rom a little. i will use this one untill next slim release.

one reboot cannot change my mind.:good:

but you guys did a grate job by bring the kk to gnx.
[Samsung Galaxy Nexus] Darklife1337:
so after 24h with the M6 don't had crashes/freezes etc
[Samsung Galaxy Nexus] gsfores:
Clean installed latest nightly 06.05 works good without the systemui fc;)
[Samsung Galaxy Nexus] bomba6:
Dirty / clean install?

I hear opposed opinions here, and can't decide whether to update or not.

Can I go from a nightly to M6 and back to a nightly, without clean install?
[Samsung Galaxy Nexus] Darklife1337:
[MENTION=2350486]bomba6[/MENTION]

dirty.

anyway M to nightly need a clean install ;)
[Samsung Galaxy Nexus] nickdc986:
I'm on M6 since yesterday...it works really good, no freezes or reboots, did a full wipe. I'm with dirtyv 5/3 too.
[Samsung Galaxy Nexus] rrusso:
M6 working good....dirty flash from m5
[Samsung Galaxy Nexus] Sdobron:
M to nightly is fine - nightly to M may not be OK depending on the changes.
[Samsung Galaxy Nexus] NCguy:
what about M to M? Can you skip one or more?
[Samsung Galaxy Nexus] hdoraemonk:
M6 crash and reboot, flashed over 11/4 nightly :D
[Samsung Galaxy Nexus] Sdobron:
Should be fine. Only reason why nightly to M is not OK is because if you're on the latest nightly before an M build is released you revert to some code that is actually older than your nightly and that can cause issues.
[Samsung Galaxy Nexus] agritux:
i think flashing nightly over M build is ok. But flashing M build over nighlty is wrong.
[Samsung Galaxy Nexus] sq3htu:
Same here.

I've installed M6 over the M5 two days ago replacing CM kernel with DirtyV (build from 2-4-2014). After ca. 12hrs got first issue when listening to music with Deezer.

After swiping down status bar I tried to tap on "next song" button - UI got freeze, no restart after that.

Yesterday I had 2 crashes of systemui process. Changed DirtyV kernel to newer version (build from 5th may). All looked to be fine with this config till today morning. Phone rebooted while surfing the net with Dolphin browser.

At this moment I've flashed M6 once again leaving CM kernel under the hood.
[Samsung Galaxy Nexus] 0s1ride:
M6 caused lots of system UI reset for me, and reverting to M5 brought the weirdest issues, like home button no longer working.
[Samsung Galaxy Nexus] luckana:
That's why you shouldn't upgrade to M6. It's that simple, stay on M5 and you won't have problems :D
[Samsung Galaxy Nexus] soder:
But it's very strange that we no longer can "trust" even the M-releases. =(

I stopped using the nightlies because of all the problems, and told my self to only flash every month. Now, not even that is "secure"...

/Söder
[Samsung Galaxy Nexus] Darklife1337:
depends after 48h i don't had a single crash,notification lag etc ;)
[Samsung Galaxy Nexus] NCguy:
Did you flash over M5?
[Samsung Galaxy Nexus] Darklife1337:
[MENTION=2716223]NCguy[/MENTION]

yes ;)
[Samsung Galaxy Nexus] Sdobron:
Interested to try but I went to Omnirom the other day out of frustration and am enjoying it much more than buggy CM11 (although Omnirom still has some quirks of its own)
[Samsung Galaxy Nexus] n1kolaa:
first time i try non cyanogen rom/stock,today i flash paranoid 4.3 beta 3 and must say its far beter then cyanogen rom it lot ways,first music playback,then speed(those are my core things) and also got no system ui fc or reboots :)
[Samsung Galaxy Nexus] tjizzle:
I'm on may 5th nightly and for some reason my screen randomly turns on without touching it. This is after a clean flash. Is anyone else experiencing it?

EDIT:

Never mind, it's a faulty charger port. For some reason the phone thinks a charge has been plugged in and then unplugged. I guess it's time for an upgrade.
[Samsung Galaxy Nexus] m.is.for.michael:
On the latest (7 may) build, I have a weird beeping during phone calls. Dirty flashed over 4 may build.

sent from my brain using telepathy
[Samsung Galaxy Nexus] imam.krismanto:
Me too..
[Samsung Galaxy Nexus] agritux:
It is fixed in 8 may nightly. I am using.
[Samsung Galaxy Nexus] Kustaa:
I'm a little confused...if it's ok going from M to nightly, but not from nightly to M, then going from a nigthly to an older nightly shouldn't be risky too?
[Samsung Galaxy Nexus] 0s1ride:
Can you share with us your 24hrs System UI process stats?

You can access it via developer options>process stats>menu>duration>1 day>show system.

For me, its maximum ram use was over 400MB when using M6, it's around 70 with M5.
[Samsung Galaxy Nexus] RcrdBrt:
nice catch! :good:
[Samsung Galaxy Nexus] dvirf:
For me the maximum is 90MB with the nightly of May 7th... and it's crashing all the time :(
[Samsung Galaxy Nexus] mmo.xda:
OK great!

Regards!

Gracias crack!

Enviado desde mi Nexus 7 con Tapatalk 4
[Samsung Galaxy Nexus] RevengeFNF:
Tried dirty flash and got stuck at CM Logo.

Did a full wipe and its working fine now.

Wow, no more lag when installing apps from Play Store :D
[Samsung Galaxy Nexus] c20h25n3o:
Hi guys,

Happy use of CM since the day I got my nexus here...

I have 2 little CM issues that are driving me crazy!

1) After each new 10.2 nightly I flash, the old (permanent) search keeps appearing. I have to flash GAPPS again for the old one to disappear and the new search bar to appear again (without the magnifying glass)

2) Some icons in a home screen folder keep disappearing...

Also Focal on the left and down has a really weird graphical issue. But I assume that's a Focal issue and not CM10.2's

Any suggestions?
[Samsung Galaxy Nexus] :
1. Try a clean flash with the latest nightly and gapps, and let us know if that happens again.

2. Is a bug in Trebuchet

Focal is still in alpha/beta stages
[Samsung Galaxy Nexus] mkl23:
So now I tried a clean flash but now I'm still not able to simulate a second screen. Anyone able to simulate?

Swyped with Tapatalk4 on my GNex :)
[Samsung Galaxy Nexus] c20h25n3o:
1) I was using a slightly older GAPPS. One from July.

I flashed the one in the OP now. If after the next nightly it appears again I'll try another clean flash.

2) Nice, good to know. Thanks!

And I know Focal is in beta, I was just curious if was the only one here :).
[Samsung Galaxy Nexus] shriom_manerker:
ram usage is way too high with the stock kernel after 50 hours of uptime,
[Samsung Galaxy Nexus] Mach3.2:
Nova launcher kept redrawing after about a day of usage.

I'm mainly using only chrome and tapatalk.

A reboot would fix it though, I'm going to look into what I can uninstall. Greenify helped a little at best.

Beamed from my Grouper
[Samsung Galaxy Nexus] yojlik:
Check the dalvik.vm.heapsize in your build.prop. It should be 256m but Google screwed up in 4.2 and made it too large causing things to not kick out of memory. This bug persists in 4.3 stock and was corrected in CM10.1 but it might not have made it to CM10.2. Verify that it is 256m and if it isn't change it to that and reboot and you should see the problem disappear.

The symptom you describe is exactly how it manifested on 4.2 before the fix.
[Samsung Galaxy Nexus] thebiffman:
I have seen many people wondering if you can dirty flash CM-10.2 over CM-10.1 and having problems etc. Here is a link to the cyanogenmod forum explaining a lot of that:

http://forum.cyanogenmod.com/topic/74526-how-do-i-update-cyanogenmod
[Samsung Galaxy Nexus] mmo.xda:
Android is not windows.

Unused ram is wasted ram.

Other possible issue is an application with a memory leak, but that is not your point.

Regards

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] shriom_manerker:
i use a lot of apps,but most of them are frozen, the ones that cause wakelocks

the heapsize is 256 in build.prop. so i guess its the kernel.. most weird thing that i noticed is that it happens only on JSS15J build, the stock isnt effected (at least when i was on stock )

so where exactly did i state that android is windows ? anyways, ive been using android since Galaxy S i9003/ i9003 days, so dont jump to conclusions next time, and this was when i had cleared all the recent apps, so this is just stupid,the services that are running arent using that that high amounts of ram usage !
[Samsung Galaxy Nexus] mkl23:
Can anyone test the simulation of a second screen? Developer options >> Simulate second screen. Is the little window showing a mirror of the screen or just black. Would be great if anyone could answer the question :)

Swyped with Tapatalk4 on my GNex :)
[Samsung Galaxy Nexus] olus:
i can confirm. just a black screen when i try to simulate screen via developer options!

i have dirty flashed from cm10.1 with the new gapps from goo.im. no problems so far! updated to the newest nightly hours ago.. all is running perfect. for now.. except the already known bugs (focal beta stadium, icons in folders dissappear sometimes,...)
[Samsung Galaxy Nexus] Mach3.2:
On to it!

Edit: heapsize is correct at 256m.

Beamed from my Grouper

---------- Post added at 07:26 PM ---------- Previous post was at 07:21 PM ----------

When you use up every single drop of it, it gets sluggish and apps redraw.

I just don't agree with that statement.

Beamed from my Grouper
[Samsung Galaxy Nexus] EnricoTFYKD:
Just a quick question: after flashing cm10.2 and gapps, I have tho stock dialer (without t9 prediction). Is it normal (maybe it hasn't been merged yet) or am I screwing up something?
[Samsung Galaxy Nexus] TheMan0790:
Under "Other Call Settings", make sure "Dial Pad Autocomplete" is checked....all this is in the "Phone" settings.
[Samsung Galaxy Nexus] EnricoTFYKD:
Thank you, found the setting.
[Samsung Galaxy Nexus] :
Indeed. Settings is taking ~80 MB, so you should have about a 100 MB free otherwise, which is a bit on the lower side. I'd advice you to stick with stock CM for a while after a clean flash, then check with Lean and Tiny kernels. I've had a fairly good experience with both.

If you have any games installed, Greenifying them is a good idea.
[Samsung Galaxy Nexus] matteventu:
That is related to Android 4.3, not to CM10.2 ;)
[Samsung Galaxy Nexus] 0s1ride:
For 1 day or 3hrs?

Anyway, I indeed noticed two things with M6: one is the System UI memory leak, another one is its crash when receiving a notification/open the notification shade. Dunno if they're related.
[Samsung Galaxy Nexus] NCguy:
Is CM11, at least thru M5, not vulnerable to the stock mm-qcamera-daemon battery drain bug? I haven't seen anyone report it and I'm wondering why? It's absolutely killing my stock nexus 5. I was planning on leaving that device stock for a while but this bug is absolutely debilitating and there are no good workarounds. Is M5 a workaround?
[Samsung Galaxy Nexus] soder:
Since the M6 release isn't very stable, I wonder how the nightlies are? Would I get a more "stable" phone if I flash a newer nightly over the M6?

/Söder
[Samsung Galaxy Nexus] RevengeFNF:
The Theme Chooser was merged in today Nightlys.

If someone test it, tell if its working ok or if the system.ui errors are still there.
[Samsung Galaxy Nexus] agritux:
Yes! http://review.cyanogenmod.org/#/c/63221/
[Samsung Galaxy Nexus] thelegbra:
the theme chooser ui is just the frontend ui for the themeing system. it's just the fluffy ui, not the new framework that's built into the system. i don't think this fixes anything.
[Samsung Galaxy Nexus] zerand:
I totally agree! :(
[Samsung Galaxy Nexus] soder:
****, what I hate my GN right now. M6 has totally turned it from "ok" to "bad".

Crash during calls and stuff, reboots, systemui crashes....

Man....

/Söder
[Samsung Galaxy Nexus] CYoung234:
Well, go back to M5 until this gets fixed. Seems like the logical thing to do. I will just stay on M5 until this systemui issue gets resolved.
[Samsung Galaxy Nexus] soder:
I didn't know I was "allowed" to go back. I thought that would case problems just the what it is to go from a nightly to a M-release.

EDIT: Going back to M5 reset all my settings in android. =(

/Söder
[Samsung Galaxy Nexus] NCguy:
I would think you would need to wipe. How about a titanium?
[Samsung Galaxy Nexus] soder:
Well, even with a backup with titanium, it takes some hours to restore. Also not all apps are able to restore with TB, like twitters and some other that needs to sign in again, and Spotify resync music and stuff.

/Söder
[Samsung Galaxy Nexus] Atento:
What is the difficulty of charging ROM or just move back to the 'ok' release?

It's a bit obsessive trying to update every single nightly just because it's newer. Wait for the first feedback before flash. It's simple.
[Samsung Galaxy Nexus] soder:
I agree. That's why I stay at the M-relaease the last months. Something that turns out not being "safe".....

And now when I moved back to the "ok" release, most of my android settings disappeared and it's like my notification bar stopped working (shows nothing) and also the tiles view stopped.

Doing my TB now, and will wipe data and flash M5. Fun f-ing weekend. =)

/Söder
[Samsung Galaxy Nexus] revanmj:
Yeah, this is ironic - CM replaces "stable" channel with M releases and at the same time they put in them unstable and resources hungry new Theme Engine.
[Samsung Galaxy Nexus] onnaj:
I did a full wipe and installed m6. At first it was awesome and flew. Now a day later i can lots of freezes and the phone is laggy. Is it possible to revert to m5 without wiping everything again?

I didn't install the nightlies any more because they were unstable and specially waited for a stable snapshot, but it isn't :(

Without a doubt i really appreciate the work of the developers and theres always the risk of getting unstable release if choosing for other then stock roms

Verstuurd vanaf mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] xaifer:
Post deleted
[Samsung Galaxy Nexus] PrimeDirective:
Let's be honest here. This device is like ~2.5 years old. It's a REALLY safe bet that not a single one of the developers test the releases on it and probably haven't in at least a year.
[Samsung Galaxy Nexus] pedmond:
Well, they release a ROM for it, don't they?
[Samsung Galaxy Nexus] aosp:
And you could buy a 1+2 just for you
[Samsung Galaxy Nexus] pedmond:
Yes, I could. My meaning was CM is a serious company. If they release software (free or not) for a device, I'm sure they have appropriate QA procedures.

As for I could buy - this is certainly nobody's business.
[Samsung Galaxy Nexus] aosp:
It is business never personal.
[Samsung Galaxy Nexus] PrimeDirective:
A handful of paid developers.. Thoroughly testing 100+ devices instead of doing what they're paid to do. Yeaaaaa not so much.
[Samsung Galaxy Nexus] revanmj:
Then they shouldn't release M compilations if they can't properly test them. Those are supposed to be tested and stable, unlike nightlies.
[Samsung Galaxy Nexus] Conte Mascetti:
I'm with may 9th nighlty now, for me it's working flawlessly, and I think I'll keep it for a long time!

From GNexus
[Samsung Galaxy Nexus] KreNtal:
9th nightly is working like a charm even for me hell yeah.
[Samsung Galaxy Nexus] CYoung234:
Did you wipe anything or just dirty flash it and wipe cache and dalvik afterwards?

I normally would always have a nandroid backup to revert to. I make sure that SMS's and Whatsapp messages are backed up as well. If you get in the habit of making nandroids of your configurations, you will avoid all of the issues you and other people have mentioned.

Sort of an editorial comment, but I am not sure why so many people here seem to use TB and not do nandroids for their backups. I own TB but in truth do not use it much because I keep nandroid backups on my computer and transfer them to the phone when needed. I keep one or two on the phone usually. I also use Nova and have a backup there of my screen config. Even doing a full wipe and a fresh install is only about a 2-3 hour process.
[Samsung Galaxy Nexus] soder:
I have a lot of apps, and can't do nandroids of all my data. I have not time or space for it. Since it is the app data that's getting f-ed up between the different versions, I often without any other help then my TB's.

When I went back to M5 I didn't wipe anything, since I wanted everything as it was. =) Now I have wiped and restored a couple of times, and I'm still not finished. Great weekend. =)

/Söder