yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] klingklang76:
Running 06/13 with old cm gapps, faultless so far. My gf's running same nightly with new gapps, no issues either, but new gapps come with a lot more bloatware as far as I'm concerned.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] polar775:
been absolutely flawless for me so far along with franco kernel
[Samsung Galaxy Nexus] a3361035:
This doesn't make sense. A different filesystem will not lead to random process errors, or rather only when it causes file corruption.

You basically [1] just need a kernel that supports f2fs (and comes with a ramdisk for f2fs fstab) - that means not CM stock kernel, and modify the ROMs updater-script to mount/format the system partition as f2fs. [2]

Tho this wouldn't be a perfect conversion as some things need actual patches in the ROM. [3]

But all is WiP anyway - even the filesystem itself.

[1] Obviously you still need the same preparations as for other ROMs, i.e. f2fs-enabled recovery and formatting as f2fs before

[2] Along the lines of: http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53312320#post53312320 or look at already converted f2fs ROMs

[3] http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53285950#post53285950

CM devs don't care about bugs in nightlies:

https://plus.google.com/+CyanogenMod/posts/7MwcZd9bPwa

Only CM stock kernel is supported by CM devs:

https://plus.google.com/+SteveKondik/posts/S1c2HQJPhJU

Seems like 4.4.3 broke wi-fi in a few custom kernels, too:

http://xdaforums.com/showthread.php?p=53411614#post53411614
[Samsung Galaxy Nexus] soder:
http://xdaforums.com/galaxy-nexus/development/ref-galaxy-nexus-gt-i9250-baseband-t1405345

/Söder
[Samsung Galaxy Nexus] xergio24:
I'm having a strange bug with N 06-11... I can't install any apk (outside the play store).

When I open xxxxx.apk it loads, the screen with permissions shows at it should but I can't touch the "next" / "install" button!

The "cancel" button works fine, but the other is like my screen is not responding in that area =/

Anyone else with the same problem? I have already tried wiping caché and dalvik but it was useless.

(see how the "cancel" button goes grey when I touch it? well, the other stays the same when I touch it)

(0611 nightly, stock kernel, PA minimal gapps)
[Samsung Galaxy Nexus] luckana:
someone else having a little lag when going back from the app drawer to the home screen on the latest nightly ? :D
[Samsung Galaxy Nexus] ->---:
On the last 4.4.2 version (6.6.?) there seems to be a memory leak problem. The device is significant slowing down after a while of uptime. Is that solved on the 4.4.3 versions? Which of the new nightlies is the most stable one?

Gesendet von meinem Xperia Z1 mit Tapatalk
[Samsung Galaxy Nexus] knuspertante:
I'm on the same settings as you! I have the same issue -.- it's really irritating

:(
[Samsung Galaxy Nexus] xergio24:
Dirty flash 06-15 and still the same problem...

Tried with a physical mouse connected through USB OTG and it's not working either. :(
[Samsung Galaxy Nexus] pedmond:
This may be silly, but you enabled installing third party apps from settings -> security, right?
[Samsung Galaxy Nexus] KreNtal:
Wait, what? Banned? I thought that the dev abandoned it...
[Samsung Galaxy Nexus] Kustaa:
well yeah, I mean the kernel is 'banned' and they closed the kernel threads.
[Samsung Galaxy Nexus] xergio24:
haha yes it's enabled... if it weren't enabled I wouldn't even get to the installation page 'cause a message would pop-up saying that I should unlock installation from unknown sources.

EDIT: problem solved! =D

Doing a simple search on google lead me to other people with the same problem but with different devices and versions of CM.

So the problem is not CM, it is caused by some apps... in my case "Echo Notification Lockscreen".

This is kind of Off Topic but it may help someone else! so... for the record, this is a lists of apps that may cause the same effect (according to what I read in other pages):

*Screen filter

*EyeProtector (Night Mode)

*Lux

*Twilight

*Echo Notification Lockscreen
[Samsung Galaxy Nexus] KreNtal:
Anyone know what's that second option?

It's under performance>memory managment
[Samsung Galaxy Nexus] LiquidXed:
Bug?¿? While talking to somebody if somebody calls in "call waiting" it won't let me tell the other person hold on I got another call. I gotta hang up on the person thats callin to beable to talk to the first person again.

cm-11-20140614-NIGHTLY-maguro.zip

Stock kernel and no mods

Anybody else?
[Samsung Galaxy Nexus] vizzze:
same here on cm-11-20140615-NIGHTLY-maguro.zip
[Samsung Galaxy Nexus] soder:
Can someone please tell me how it all is with the app Mirror and the function called Cast Screen in android?

I've had the app Mirror installed on my Gnex, and I've used it, and it worked. I've then kept the app during different updates of CM11.

I always thought that the "Cast Screen" function in CM11 was because of this app, but I've also read that there is some kind of this function built in to android or CM11 also?

When I a few days ago wanted to use Mirror again it crashed, and I today wanted to uninstall the app. I removed tha apk's, both updates in /data/ and also the system version, and I rebooted.

Still there is the function "Cast Screen" in my quick settings menu, so I guess there is some kind of function for this in CM11 or android.

Can someone please tell me if I'm correct, and also if there's something to do if I want Mirrors to work...

Thanks.

/Söder
[Samsung Galaxy Nexus] rtimoff:
They screw up dialer, ayayay

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] CYoung234:
SIM Card Removed Error

I am seeing this problem with a maguro i9250 running the latest cm11 from a fresh install after a full wipe with stock kernel, etc. Here is a screenshot as well as a logcat. I posted the same problem in the Carbon forum, as I see it with the later Carbon ROMs as well. I know that the 6/12 Carbon ROM worked fine, and OMNI does not seem to be seeing this either. So, I believe it is a problem in the cm11 codebase.

UPDATE: I just tried the 6-18 OMNI ROM, and it has the same problem. Reverting back to something pre-6/12, which runs fine.
[Samsung Galaxy Nexus] pirigu:
here is download it from here:good:

https://www.dropbox.com/s/hl23lwajy6...-v10_1080p.zip
[Samsung Galaxy Nexus] xergio24:
I have been running CM11 Nightly 20140615 for several days and I don't have this issue.

Are you sure your SIM card is not "broken"? maybe it is bad and you need to change it.
[Samsung Galaxy Nexus] CYoung234:
Anything I run that is pre 6/12 or so runs just fine, so it is difficult to conclude that it is hardware. I am running the 6/5 FML OMNI variant right now, and it is rock solid. It has to be some recent change to the code.
[Samsung Galaxy Nexus] nchall:
Anyone know why Google Wallet Tap to Pay doesn't work on CM 11 M7?
[Samsung Galaxy Nexus] dirtyreturn:
I'm at a loss here, maybe someone could help me out. I've been flashing nightlies keeping that up to date. Today I went to connect to my pc and it would not connect( display as a filesystem). Yesterday it was working fine. I tried rebooting and reflashing dirty. Am I left with a clean flash?
[Samsung Galaxy Nexus] agritux:
is the usb debugging enabled in developer settings?
[Samsung Galaxy Nexus] a3361035:
Google dropped support for Galaxy Nexus.

http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post52538096#post52538096

USB debugging has nothing to do with MTP/PTP access. It's for adb.

MTP/PTP options are under Settings -> Storage -> 3-dots: USB computer connection.

Anyway no good error description, no logcat and using nightlies and not M-releases, so your loss.

In other news:

Android 4.4.4 is out:

http://www.androidpolice.com/2014/0...-factory-imagesbinaries-up-for-nexus-devices/

Seems to only fix the openssl ccs issue (CVE-2014-0224) which CM already fixed in M7 and nightlies after June 6:

https://plus.google.com/+CyanogenMod/posts/JLjacfrwrHU
[Samsung Galaxy Nexus] agritux:
Really? Try it yourself. Disable USB debugging and connect your phone to your computer.
[Samsung Galaxy Nexus] gcsuri:
I'm on 20140613 nightly. I have a problem with call-waiting. When I'm in conversation and have an incoming call, the existing conversation is hanging up...

anybody can confirm?
[Samsung Galaxy Nexus] hanschke:
thats that I dont want cause of my data loosing :( what is about factory reset. what will I lose?
[Samsung Galaxy Nexus] Sincerinhoo:
Use any kind of backup app. This is your only solution i guess. With factory reset you will also lose everything
[Samsung Galaxy Nexus] hanschke:
But as you know Titanium Backup will safe on intern memory and if i do a reset it will removed or not?

13 gb download with wlan is a bad idea :(
[Samsung Galaxy Nexus] Sincerinhoo:
Hmm no that's not really an option. But now you mention it all my images etc, where still on there when i wiped it. Maybe it was thanks to google backup or it just did not got deleted. Maybe someone else here can confirm that? I can't really remember :p
[Samsung Galaxy Nexus] hanschke:
if factory reset will not delete my data it will be ok.
[Samsung Galaxy Nexus] :
Factory reset in Recovery doesn't wipe your data stored on the internal memory like photos, music and anything else you've stored there. What's lost is only the apps, your settings, accounts and so on.
[Samsung Galaxy Nexus] hanschke:
does it is the same if i use the option for android like recovery?
[Samsung Galaxy Nexus] :
not sure I understand you. Resetting from Settings while booted into Android wipes all your photos/music etc. Resetting from Recovery, like TWRP or CWM, doesn't wipe photos/music.
[Samsung Galaxy Nexus] Sincerinhoo:
Anyone??
[Samsung Galaxy Nexus] :
Do you have Superuser or SuperSU?
[Samsung Galaxy Nexus] Sincerinhoo:
SuperSU and updated the binaries like requested. But shouldnt it be just fine disabling the SuperUser from 10.2 as well?
[Samsung Galaxy Nexus] :
Superuser is a bit buggy still. I am able to disable SuperSU. Try using the Full Unroot option then.
[Samsung Galaxy Nexus] hanschke:
i have now done a reset and flash cm and gapps again but same problem:(:eek:
[Samsung Galaxy Nexus] Sincerinhoo:
Mwah that's not really an option it's not that I need it that bad atm. Guess I have to wait for an update then. What I see is when I disable the cm superuser and switch of developers tools the cm superuser turns on again. That's the bug why it's not working for me now I guess
[Samsung Galaxy Nexus] matteventu:
Try to re-flash the nightly and then wipe cache and/or dalvik cache.
[Samsung Galaxy Nexus] h1ghland3r:
Guys,

I'm with CM 10.1.2 and franco r384. Can I do a dirty flash to CM 10.2?
[Samsung Galaxy Nexus] saeed14i:
Not recommend
[Samsung Galaxy Nexus] h1ghland3r:
You don't recommend because the dirty flash or because the kernel?
[Samsung Galaxy Nexus] Krayvon:
!

is it me or is GNexus and cm10.2 the best thing ever happened to XDA? :p

I truly prefer this better than my htc one s and my N4. LG Nexus can suck it!
[Samsung Galaxy Nexus] saeed14i:
Because of the dirty flash. Kernel will be overwritten once the new rom is flashed but it is never recommended to dirty flash between different android versions (in this case from 4.2 to 4.3)
[Samsung Galaxy Nexus] scorpeeon:
New nightly says about itself that it's 4.4.4 already :)
[Samsung Galaxy Nexus] mundavincicode:
can i know, how to update rom, using cyandelta or download 200mb rom, i now using cyandelta but have some problem, the problem is cannot update the latest rom 4.4.4, its say my rom its to old. but i have on nightly 20140619 someone help me please.
[Samsung Galaxy Nexus] Conte Mascetti:
Usually cyandelta takes a while to release delta file, at least a hour. And I heard OTA cm updater not always works. IMO I prefer download ZIP from CM repo, here's today nightly http://download.cyanogenmod.com/get/jenkins/73101/cm-11-20140620-NIGHTLY-maguro.zip
[Samsung Galaxy Nexus] LiquidXed:
same here...
[Samsung Galaxy Nexus] a3361035:
11.0-InstallerXNPQ25S

New Installer build out for maguro:

11.0-InstallerXNPQ25S based on M7. [0]

Flashable zip:

http://mirrors.reflected.net/pub/get.cm/fota/1120

But best install with CyanogenMod Installer [1] or check for OTA if you are already on the Installer channel. (official delta updates for installer builds)

To cross into or out of the Installer build release channel will require you to wipe your data (due to the different key signing). [2]

Installer builds are signed with real private keys, not insecure AOSP ones. [3] So besides official Omni builds to my knowledge one of the few custom roms which don't compromise android's security fundamentals like the rest. [4][5]

[0] Differences to M7: http://pastebin.com/kDt5tMSM

[1] http://beta.download.cyanogenmod.org/install

[2] 'So what are the release streams?' paragraph in http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items

[3] last paragraph in http://www.cyanogenmod.org/blog/cyanogenmod-account

[4] http://wiki.rootzwiki.com/Signing#Shared_Keys

[5] Dianne Hackborn in https://android-review.googlesource.com/#/c/22694/

In other news, new CM weekly report out:

http://www.cyanogenmod.org/blog/last-week-in-cm-jun-19-2014

Maguro is among those devices, which got towelroot (CVE-2014-3153) patched around June 6 and it's already in M7. [1]

New features mentioned don't look that interesting, so combined with the unstableness, flashing nightlies instead of Installer/M builds remains a mystery.

[1]https://github.com/CyanogenMod/andr...mmit/8504e79dc829ba78b75cbae8414236f12d4f82cb
[Samsung Galaxy Nexus] Kustaa:
me too
[Samsung Galaxy Nexus] mundavincicode:
thanks for that information. thank you very much :)
[Samsung Galaxy Nexus] mckennal:
I had been using CM 10.2.1 (stable release) for a while, but found it was unstable (phone crashed during phone calls, occasional random hang needing battery pulled). I then upgraded to the recent kitkat M7 (including factory reset/wipe data) and have found it to be more unstable: E.g. Screen wouldn't turn on after receiving a facebook message (led was flashing as I'd configured it to flash on fb notifications) required battery pull, crashed while listening to music via bluetooth again requiring a battery pull - about 1 hard crash per day so far. I'm loving the speed of kitkat and lower resources the system consumes, so keen to keep trying with kitkat, but obviously would rather it be more stable.

Can someone point me to directions on where to find the log files needed to file bug reports?

Anyone have suggestions for a more rock solid kitkat experience? (any other ROMs worth trying?)

Thanks

Luke
[Samsung Galaxy Nexus] AgentSmith:
This sounds as if a certain app is causing problems. I would uninstall most, see if that solves the problem and then reinstall one by one until you find the app causing the problems. Are you using Xposed with a certain plugin? ART is also known to cause problems with certain apps.

The only problem I have with Kitkat (M7) is the fact that this great phone is starting to show its older specs after all these years. The lack of RAM is becoming more and more obvious e.g. recurring page reloads in Chrome after briefly switching to another app even when all other apps have been closed. I still hope for the 3.4 kernel to actually start working. For now I'm truly happy with this ROM though. At least we're not behind with our Nexus devices!
[Samsung Galaxy Nexus] mckennal:
No, I'm not using Xposed or ART.

If it keeps crashing I may try removing apps, but was hoping someone could tell me where the crash logs were in case it gives me some hints at the app causing the problem.

Thanks

Luke
[Samsung Galaxy Nexus] a3361035:
Do a real clean install, i.e. wipe /system, too. For example some old init.d scripts - having an addon.d script to backup itself during ROM install - might cause your symptoms.

Alternatively delete /system/addon.d, so there're no backup scripts.

As for reporting bugs:

http://wiki.cyanogenmod.org/w/Jira#Create_a_new_issue

Bugreports without logcats are pretty pointless and for kernel crashes you should also include last_kmesg - to be found under /proc/last_kmsg right after the reboot.

In other news:

Android Police featured the new Heads Up floating notifications:

http://www.androidpolice.com/2014/0...n-aosp-enables-them-in-latest-cm11-nightlies/
[Samsung Galaxy Nexus] soder:
About ART vs Dalvik, if I switch to ART and reboot, and later want to run Dalvik again (for Xposed) can I switch back then, without any problems?

Or do I need to wipe or something like that?

/Söder
[Samsung Galaxy Nexus] pianistaPL:
Just switch.
[Samsung Galaxy Nexus] DomieMic65:
Hey guys is the 0623 OK?

I am on 0613 with no (obvious) bugs and I am considering the newest
[Samsung Galaxy Nexus] klingklang76:
Running 0623 for some minutes only, can't really tell about stability, but heads up is definitely very cool :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] agritux:
What does "org.cyanogenmod.launcher.home (CM home)" do? it is just 43kb.
[Samsung Galaxy Nexus] a3361035:
Nightlies are never recommended:

https://plus.google.com/+CyanogenMod/posts/7MwcZd9bPwa

Not much yet, but will be an extendable homescreen:

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

In other news:

Cut-off for M8 release is July 3rd. [1] Don't update nightlies further if you want to switch to M8.

Expect a release a week later. So M8 is a week behind the planned schedule. [2]

There's no real schedule for Installer builds, ideally it shouldn't take that much time after an M-release, but there were no Installer builds based on M4-6.

[1] https://twitter.com/CyanogenMod/status/480249821115072512

[2] Last post in https://groups.google.com/forum/#!topic/cyanogenmod-dev/GIRIkbVxDb0

Blacklist for Heads Up is on the way:

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

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

http://review.cyanogenmod.org/#/c/66379/
[Samsung Galaxy Nexus] ariful2907:
I'm doing a test on the battery for my galaxy nexus with CM 11 (21/06/2014) with franco kernel. If you want follow or comment please follow this link:

https://docs.google.com/spreadsheets/d/1pG19wd7HqfNDFQJUhtGfvIoj-GixHT8sJpViK0ZWysA/edit?usp=sharing

I hope it is useful to someone.

p.s it is in Italian but there is no difficulty in understanding
[Samsung Galaxy Nexus] klingklang76:
It's there in 0623 already. Thanks a lot for the... heads up on next M8 :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] soder:
I just flashed 0623 over 0622, and it seems like the clock widget is gone. Both the normal widget and the lock screen widget, and the settings for it.

EDIT: It was gone, but then came back, on a reboot or just in a while...

/Söder
[Samsung Galaxy Nexus] a3361035:
It's clearly not as it isn't merged yet. You are prolly confusing Do Not Disturb with the Blacklist:

Do Not Disturb: no Heads Up while you are using listed apps

Blacklist: listed apps won't show Heads Up regardless of the app running﻿
[Samsung Galaxy Nexus] soder:
I'm having huge problems with 0624. 0623 was OK, but I hope I can go back to 0622 without any problems. I have to learn to not be a crack flasher.

EDIT: I say it again. 0622 is pretty "fast" and "stable". 0623 and 0624 is not. Worked going back to 0622 for me.

/Söder
[Samsung Galaxy Nexus] m.is.for.michael:
From one addict to another: define "huge problems" please?

sent from my brain using telepathy
[Samsung Galaxy Nexus] soder:
Well hard to explain, but, all kind of problems. And generally a slower system. Apps taking long time to open.

/Söder
[Samsung Galaxy Nexus] acloh0411:
why i got many FC after switch to ART?:(
[Samsung Galaxy Nexus] mckennal:
Unfortunately I am still having the occasional reboot with M7 and can't work out how to get a logcat from just before the phone rebooted, and I also don't have a /proc/last_kmsg (only /proc/kmsg).

On the positive side, the battery usage is excellent - far better than any previous stock or CM release I've tried, and it is also definitely faster - which is why I want to stick with it.

Luke
[Samsung Galaxy Nexus] n1kolaa:
CyanogenMOD dont support ART.
[Samsung Galaxy Nexus] pianistaPL:
Yes, it doesn't support but ART works without problems, this has to be problem from user, not ROM.

---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------

Which Gapps do you use?
[Samsung Galaxy Nexus] Darklife1337:
confirm the soder's problems, 06/23 and 24, tried with a dirty then with a clean flash slow system with many fc, i'm back to the 06/13 build and waiting for M8 ;)
[Samsung Galaxy Nexus] klingklang76:
As new versions go by, I have this feeling that cm11 is gradually offering more features than our device can easily handle. Only time and new milestone builds will tell, but it may have come the time when new updates can't result in a faster system no more...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] DomieMic65:
That's my feeling too...

Στάλθηκε από το Galaxy Nexus μου χρησιμοποιώντας Tapatalk
[Samsung Galaxy Nexus] AgentSmith:
+1

This device's 1 GB of RAM is starting to show. Maybe/hopefully the kernel 3.4 project will give us the necessary optimization. I love to extend my phone's work life as much as possible which is why I won't replace it for at least another year. If it doesn't die on my before then of course. But 4 years seems a reasonable time after which I allow myself a nice hardware upgrade. ;)
[Samsung Galaxy Nexus] Atento:
What I don't understand is that KK was supposed to be lighter than JB and it's not true at all. The promise of running KK on 512mb devices is impossible to be realized.
[Samsung Galaxy Nexus] a3361035:
You should really learn how to use adb and logcat:

http://wiki.cyanogenmod.org/w/Doc:_adb_intro

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

Tho there's an app for logcat, but that adds another abstraction layer:

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

last_kmsg will only be there after an reboot, it's the old kmsg. not a good sign when this doesn't get created.

If you go back to a clean stock install, do those problems persist? Could be faulty hw.

ART is officially considered experimental for 4.4:

http://source.android.com/devices/tech/dalvik/art.html

For that reason CM does not even accept bug reports when ART is used:

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

How about you provide some proof:

http://android-developers.blogspot.com/2014/01/process-stats-understanding-how-your.html

Otherwise it's likely more the usual old installs with zillion apps are slower than new, clean installs with few apps.

Again where's the proof. Moto G even has the same.

KitKat's Project Svelte made Android better when dealing with tight memory constraints, not worse:

http://android-developers.blogspot.com/2013/10/android-44-kitkat-and-updated-developer.html
[Samsung Galaxy Nexus] pianistaPL:
I wrote it actually, i don't know why you didn't quote my full post. Anyways even if CM doesn't support, it doesn't mean that ART doesn't work. ART works perfectly for me since i have installed KitKat on GNex (from november).
[Samsung Galaxy Nexus] a3361035:
Still missing the point.

Google themselves consider ART in KitKat experimental. Don't infer that no fc does mean it works perfectly.

Or take a look at AOSP master and how heavily ART is still under development:

https://android-review.googlesource.com/#/q/status:merged+project:platform/art

ART in the L-release will be very different than the one in KitKat.
[Samsung Galaxy Nexus] pianistaPL:
I understand you ;)
[Samsung Galaxy Nexus] soder:
When do we start to see themes with the new navigation buttons from the next L version of android? =)

/Söder
[Samsung Galaxy Nexus] KreNtal:
This theme was submitted before the google i/o, don't know how he made it https://play.google.com/store/apps/details?id=com.carlosavignano.objects.orange. However we're going off topic here.