yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] JohnKuczek:
MMS Issues

Is anyone else having issues sending and receiving MMS? I realized on 2014-01-15 or 16 that I could do neither.
[Samsung Galaxy Nexus] NCguy:
Wonder specifically what "works more reliably" means? Isn't superuser installed by default? Why wouldn't CM switch unless its something to do with open licensing?
[Samsung Galaxy Nexus] un4givn85:
did the 1/21 build bork anyone elses phone, its on and works when it wants to, but is very unresponsive and takes about 15 presses of the power button to wake it up, edit, turns out it is on with the first press, just no screen output, if i long press after the first time, it vibrates giving the power menu, tho i cant select anything
[Samsung Galaxy Nexus] TurboD:
I haven't used Pete's, but the nightlies have been extremely stable for me.
[Samsung Galaxy Nexus] NookMonkey:
I agree.
[Samsung Galaxy Nexus] rdtshaw:
I had goo manager prompt me for a rom update and direct me to the Cm9 nightly. I downloaded it and hit the are you sure and started flashing. Just as I hit go, I realized it... doh! I just dirty flashed the previous cm10 nightly and Jame bond kernel and all has been well. Was waiting during the boot wondering if I was going to spend a couple hours wiping, restoring apps and resetting up... lol... make sure to read the goo manager notifications and download link, its crossing its cm9 and 10 wires right now.

Cheers!

Also, the cm10 nightlies have been GREAT on my vzn gnex. Battery life has been pretty decent too. I'm looking forward to cm10 on my xoom, nightles are supposed to start soon.
[Samsung Galaxy Nexus] phydo:
Honestly I've wiped data hundreds of times by now probably on devices. I can reinstall and set up most apps from booting up within maybe 30 minutes. You get quick about it. The one thing I like is you start to weed out unneeded apps.
[Samsung Galaxy Nexus] rdtshaw:
I was being mostly facetious. :) a complete wipe and restore takes me about an hour: restoring a ti backup, going through all the system settings, re-pairing my headset, the headset on my helmet(motorcycle, not special needs), bluetrip audio adaptor in my truck, BT headphones, setting up multiple email accounts, changing all the notification settings, setting preferences in my corp calendars and email accounts, manually reloading some of my I.T. mgmt apps that don't like to be restored in TI Backup, resetting up VPNs, etc. That is all before I start thinking, "now is a great time to try that other kernel and get rid of old apps and clean up my sdcard and double check my backups to box, oh and clean out the old backups on box... maybe I should switch those to Google drive, or use both...". :)
[Samsung Galaxy Nexus] wad3g:
I've made some wallpapers for various ROMs and haven't posted them in hardly any of the actual ROM threads.

So I figured I'd post them in here, for the people who actually use the ROM. lol

Anyway, hope hope you enjoy.

Information about these wallpapers are in this thread: http://goo.gl/x2Akl

CyanogenMod: 3 Versions
[Samsung Galaxy Nexus] DoctorSasquatch:
Pretty sweet wallpaper.

Any chance of making a pure black one with the circle and "Cyanogenmod"?
[Samsung Galaxy Nexus] DarrellRaines:
The same smartass that has been since the ROM was released. That page is for both. You can't fault someone else for your or even my failure to pay attention to what we were downloading.
[Samsung Galaxy Nexus] eiddor:
+1 - Like those daily free Amazon apps that I install every day but never play.
[Samsung Galaxy Nexus] cmajpwc:
I have the 9/3 nightly and was wondering two things if they are fixed in the current nightly:

1) my WiFi connection is abysmal at best compared to when I was on ICS, and I was wondering if it was any better in the current nightly? Some of the comments I have seen from ROM Manager say it's been fixed but I just would like to know before I go installing it.

2) The MyVerizon issue I had earlier has been resolved: sort of. When I install it as a system app, it works fine for a little bit, but maybe an hour or so later when trying to get in it says the ogin process has stopped and I have to reinstall it, then it works again for another hour. Is there any way to fix this? Is there some process I'm skipping that is allowing the VerizonSSO.apk to be either overwritten or uninstalled every so often?

Those are really the only two qualms I have with the rom so far so I really don't wanna go and flash a new one without knowing those answers, because you know what they say, if it isn't broke, don't fix it (yeah, kind of hypocritical considering I flashed CM10 anyways haha)
[Samsung Galaxy Nexus] thefatalepic:
I went from 9/3 to 9/7 but I can't comment on #1 since I never really had any WiFi issues.

However, regarding #2 I was having MyVerizon issues before but because of the LogIn app. Try: uninstalling both apps. Install the Verizon LogIn app from this apk VZ LogIn. Now install MyVerizon apk (from market if you can). Now make sure you are NOT on WiFi for the first time you open MyVerizon. It will ask you to log in and now you can re-enable WiFi and it should work normally from now on.

Note: Just do regular installs if you can, don't install them as system apps.
[Samsung Galaxy Nexus] 911junkie:
I'm getting reboots. I thought it was kernel but still getting them on different kernels. Can't make sense of it either. Will be up for 24 hrs one day and can't get much more than 4 hrs uptime the next day. ??
[Samsung Galaxy Nexus] mike216:
Fix permissions in recovery. I bet this fixes your reboots. It did for me
[Samsung Galaxy Nexus] budwizer:
Actually that is not accurate. I can swipe from my camera just fine in the top portion where the active camera image is displayed. If I'm not mistaken this depends on which Gapps you are using. I'm using Formula's gapps from 8/31.
[Samsung Galaxy Nexus] thefatalepic:
Well, it is accurate.

The thing is, CM10 has it's own camera/gallery I believe, with custom options and settings that they have added. If you are using Formula's gapps that includes the camera/gallery, you are just flashing over the one included in CyanogenMod.

So, it is broken, but there is the workaround that you used, which is replacing the CyanogenMod camera/gallery with the stock one. Hopefully they fix it soon :D
[Samsung Galaxy Nexus] stillthisguy:
The swipe issue occurred when they added pinch to zoom into the ROM, which was on the 09/08 nightly. They decided that pinch to zoom isn't really needed and that it can break the swipe, so.... on the 09/10 nightly they removed pinch to zoom. I tested swipe on 09/08 and was only able to swipe from the right of the camera area and now on 09/10 can swipe from anywhere. Remember, anyone can see what changes are being made here - http://cm10log.appspot.com/?device=toro

Revert "Camera: Add pinch to zoom"

If well, pinch to zoom is really awesome and that stuff

camera already has zoom control on the right side and it's better to have

AOSP implementation slide to gallery on the entire screen that just on the

buttons. This may also break swipe to gallery on LDPI devices

(and even MDPI ?), in wich case buttons area is really small.
[Samsung Galaxy Nexus] thefatalepic:
Odd, I use bbqdroid to view the changelog and it looks like there are differences between what it says there and the site you posted. I wonder why that is. I was viewing CM10 for 'toro' and there are slight differences as to what they are changing in each nightly.
[Samsung Galaxy Nexus] budwizer:
I hope it is fixed soon as well. I really would like the enhanced camera however the Google+/Picasa sync I need more and thus keep having to revert to one that works with that functionality.
[Samsung Galaxy Nexus] stillthisguy:
I used to got to bbqdroid as well, until someone pointed out changes that happened that were not listed at bbqdroid. Since then, I have always went to http://cm10log.appspot.com/?device=toro to get updates, as it always has all the changes that are being made, and for some reason bbqdroid doesn't.
[Samsung Galaxy Nexus] gkastrinos:
Ah ha. Didn't realize that. I was wondering why I didn't have the extra options I had originally with these nightlies.

Now I know, it's because I switched to Formula's gapps to get Picasa sync to work.

I suppose I'll watch the log like a hawk, waiting for the camera fix to be merged, then I'll remove the camera.apk from Formula's package before I flash.

Thanks!
[Samsung Galaxy Nexus] klobkelosh:
Running fine here. No such problem for me.
[Samsung Galaxy Nexus] peterlemonjello:
Works fine on the 1/16 build on my VZW GNex.
[Samsung Galaxy Nexus] thehiggins:
Since flashing to CM11 I haven't been able to connect to 3g. 4g works just fine. Both worked in previous versions of CM. I've been flashing every CM11 nightly for weeks with the hope that it will get sorted out, but I'm starting to suspect that it isn't a CM bug. Has anyone else ever seen this issue? If it isn't a CM thing, is it a KitKat problem? Or is it a configuration/activation problem with my device?

Things I have tried in my attempts to resolve the problem:

Verified that I'm using the latest radio version

Toggled 4g on/off

Toggled mobile data on/off

Toggled airplane mode on/off

Removed and reinserted SIM card

Used *228 to reprogram phone and update PRL

Used *#*#4636#*#* to verify that the phone is set to GSM/CDMA auto (PRL)

Did another clean reflash of CM11

Sorry if this is the wrong place to post this, but since the only thing that has changed is CM10.2 -> CM11, I'm not sure what else it could be.

Edit: On further research, it is possible that TWRP 2.6.3.0 may be the cause. Updating to 2.6.3.2 and will do another clean flash of CM11
[Samsung Galaxy Nexus] Royal2000H:
I'm on the 1/18 nigtly, running Dalvik, not ART and getting random reboots. Anyone getting it too? Is there any way to figure out what's causing them? I assume logcat won't help much but open to ideas.
[Samsung Galaxy Nexus] tattedupboy:
The only way I'm ever able to get 3G to work is to switch to it in he settings and then reboot.
[Samsung Galaxy Nexus] klobkelosh:
My 3G and 4G work as expected, and the phone bounces between several times a day. I suspect the 4g tile is still broken.
[Samsung Galaxy Nexus] ca.reaper:
Have the unresponsive screen issue as well. Seems to come and go. Had it for the past few nightlies.
[Samsung Galaxy Nexus] Juice3250:
Installing Supersu from the play store absolutely won't cause conflicts and won't hurt. I too installed it and I'm not having any issues. The Supersu will pop up with notifications asking for root permissions now instead of what comes with the ROM.

Update: It's not needed. In fact, whenever I reboot from recovery it asks me to fix root permissions. So, I'm going to uninstall supersu.

I was having problems with Softkeyz working, and thought it might be attributed to root permissions which is why I downloaded it. To try and update the binaries.
[Samsung Galaxy Nexus] SynbiosVyse:
1/18 and beyond is currently broken. Do not flash 1/18.

From the CM forums (netboy):
[Samsung Galaxy Nexus] klobkelosh:
Thank you for this info. I installed a log cat to keep an eye out, but I'm not seeing these symptoms on last night's nightly. Granted, I'm in a strong 4g area, but I'll keep my eyes open. Maybe we can identify what system components were altered and "roll back" to the 1/17 files with a flashable zip until cm managed to revert the changes. Anyone know?
[Samsung Galaxy Nexus] SynbiosVyse:
Actually I think it might be fixed in 1/22, but my phone is still going back to 3G, which it wasn't doing before 1/18.

I'm not seeing the huge battery drain by cell standby now like I was noticing on 1/18 though.
[Samsung Galaxy Nexus] peterlemonjello:
This explains a lot of my 4g to 3g problems. I can confirm it exists in the 11/21 nightly.
[Samsung Galaxy Nexus] Skyh:
Yep, did the same exact thing to mine.

FYI, I just flashed 1/23 and am still having the issue where the phone becomes completely unresponsive shortly after starting up.
[Samsung Galaxy Nexus] un4givn85:
I went to the m2 release until i hear that things are better on this front

hopefully an RC is in the near future
[Samsung Galaxy Nexus] SynbiosVyse:
I flashed 1/23 and had the phone "sleeping" problem.

Dirty flashed back to 1/15 and having lots of 4G to 3G handoff issues, I think residual from the 1/18+ fiasco. Your best bet might be a clean install of 1/17 or earlier right now.
[Samsung Galaxy Nexus] dm47:
have you seen any issues with M2? I just did a clean install today and so far I've had wifi drop once and one poweroff out of nowhere. Might be a fluke... will report back
[Samsung Galaxy Nexus] klobkelosh:
Hopefully this fixes a bunch of our toro issues: https://github.com/cyanogenmod/andr...mmit/cd9386902c2921ab4736a92846522529802c2d34
[Samsung Galaxy Nexus] un4givn85:
havent had any issues so far, knock on wood.

i will report if i do
[Samsung Galaxy Nexus] dm47:
haven't had any more wifi drops or hard resets so I think that's fine. However, an issue I've been having for over a week now is that the phone doesn't recognize it's being charged until 15+ seconds after I plug it in. Additionally, in the battery stats I see "0s on battery", even though it's been on battery all day. Do I need to wipe battery stats or something?
[Samsung Galaxy Nexus] un4givn85:
Thats what I would do.
[Samsung Galaxy Nexus] klobkelosh:
I'm happy to report, after extensive testing, that reverting to the version of bionic (libc.so) from the 1/17/13 nightly does seem to fix the network connection. I've tested the fix on a clean build of the official cm nightly from yesterday and LTE works properly. I'm now testing upgrading my working 1/17 nandroid with cyandelta - fingers crossed.

Please help me test. Flashable zip for the bionic rollback patch is at toro-downgrade-bionic-to-1.17.13.zip - 332.05 KB
[Samsung Galaxy Nexus] David 617:
Will this work for Vanir also? I switched to omni b/c I was having these exact issues.
[Samsung Galaxy Nexus] klobkelosh:
It may, if vanir is based on cyanogenmod. Give it a try. If it doesn't work, you can really revert by reflashing your ROM.
[Samsung Galaxy Nexus] David 617:
Thank you! This works perfectly! No more 4g/3g issues for me ;)

Bootloop on ART though, not sure if its related to this. People have been saying ART is unstable on vanir lately.
[Samsung Galaxy Nexus] klobkelosh:
Yeah, I've heard that about ART on vanir. You might pluck libart.so from something more stable and see if it helps at all.
[Samsung Galaxy Nexus] David 617:
how would i do that? just using a file manager?
[Samsung Galaxy Nexus] klobkelosh:
I'll pm you. Sorry for the ot folks
[Samsung Galaxy Nexus] Badger51:
Toro Woes

Thanks, I'll give it a try.....battery has been killing me the last few days...is this related to the above fix?
[Samsung Galaxy Nexus] klobkelosh:
Not sure. Could be if your data is cutting in and out that it is draining battery.
[Samsung Galaxy Nexus] ulnevrwalkalone:
Fixed my 4g issues, Thanks!

Is this being/ has this been added to the CM nightlies?
[Samsung Galaxy Nexus] Big ZD:
It has been provided to the maintainers of the toro and toroplus.
[Samsung Galaxy Nexus] klobkelosh:
I'm told that the CM maintainer for toro - [MENTION=554863]beki[/MENTION]t (Brint Kreibel) - is aware of the problem. The zip is hacky rollback, I'm sure the CM team would prefer to identify the particular bionic commits resulted in the problems. It might be a while.

:good:
[Samsung Galaxy Nexus] Badger51:
Update

It's early but the phone does seem more responsive...will report on battery life later today...

Perhaps, it's unrelated, but prior to applying the fix, I had difficulty getting Play Store Updates to download...they would stall and download and/or installation would never complete.

After the fix, the updates downloaded without difficulty...

I'll keep you posted on any other observations...

I assume that I should refrain from any further downloads of nightlies?

thanks again
[Samsung Galaxy Nexus] klobkelosh:
cool! I wasn't aware of play store problems from the bionic update, just data and ART issues. Thanks for finding this. As far as nightlies, you can definitely keep flashing nightlies as long as you flash the bionic rollback afterwards.
[Samsung Galaxy Nexus] wavedashdoc:
Is this issue only for the gsm variant? I have had better radio results since the recent change with a clean flash of the 1/25/14 on toro.
[Samsung Galaxy Nexus] klobkelosh:
It was definitely broken on the 25th and 26th nightly builds
[Samsung Galaxy Nexus] jrk190:
So what's the current best ROM/zip to flash? I'm looking to switch back to Cyanogenmod, but I need my data!
[Samsung Galaxy Nexus] klobkelosh:
Flash the most recent nightly, gapps, and the rollback zip and your data will work perfectly. If you don't want to rollback, flash the 1/17 nightly or the m2 release.
[Samsung Galaxy Nexus] NCguy:
hate to sound totally ignorant but what is the rollback.zip? A link would be helpful, I just can't find it when I search.
[Samsung Galaxy Nexus] jrk190:
That's what I've done, just need to flash the rollback. I'm just looking for better battery life...

---------- Post added at 12:14 AM ---------- Previous post was at 12:03 AM ----------

Just noticed the sleep of death. Does the rollback fix that?
[Samsung Galaxy Nexus] klobkelosh:
Yeah, xda search... anyway

precisely one page back:

---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------

The sleep of death is a kernel thing IMO. If you're using stock cm kernel, you might try a custom one (askp, tiny, fancy are all on xda toro our maguro forums). That would help your battery life too, but not by much. This is toro, battery life not our thing.
[Samsung Galaxy Nexus] jrk190:
I just used touch control and i'm not having it anymore. CM11's looking good!
[Samsung Galaxy Nexus] Mr_GreenJeans:
Clean installed 1-27 nightly + rollback zip. Still having trouble with delay in mobile data connection coming off Wi-Fi and between towers. (Same trouble I've experienced with every kk Rom) Unable to stream music or play ingress while driving. Shows connected in status bar but data does not work unless airplane mode or data is toggled.
[Samsung Galaxy Nexus] jrk190:
Ingress while driving... That's an interesting concept. I know you can play it on Glass.... That'd be fun.
[Samsung Galaxy Nexus] jlvlawrence:
You should look for a better phone if your looking for better battery life.
[Samsung Galaxy Nexus] jrk190:
My current income of $700 a month won't allow that. And that's after an 18 hour shift. But alas, the battery life is still better than my old Motorola Bionic. I'm holding off for the X Dev edition or the next thing from HTC. Both have been good to me in the past, I won't revisit Samsung simply because no ROM flashing. I need an unlocked boot loader and hackability!
[Samsung Galaxy Nexus] drumst1x:
I'll cross-post this in both threads, but i've been running fitsnuggly's CM builds lately, which are nightlies with a few cherry picks, and i've had the same issuue everyone else has been having with sleep of death and rare 4g and crappy 3g.... I'm currently on the 2014-01-20 (Jan 20th) nightly and I just flahsed this rollback. IMMEDIATELY upon rebooting i went right into 4G and have had great service since (only about 10 mins, but coming from what i had, it's impressive). Great job, and thanks so much for providing this. Even tho it's only a "hack" the results are great for me. Hopefully CM team can figure out what really went wrong and truly fix it, then we can stop with the rollback hack.

Since you seem to understand what went wrong and what needed to be done to rollback, can you explain what libc.so is, and why it's related to Bionic? Is that referring ot the Droid Bionic phone, or some piece of CM known as "bionic"? Curious to know more details, even though i'm already back up 'n running.

Thanks so much.
[Samsung Galaxy Nexus] Big ZD:
Yes yes, we know, we know...newer phones have better battery. Thanks for the astute observation. Had this not been stated, I think we all would have been stuck in gnex land. SMH

No need to justify your desire for better battery man, it's all good. I too seek/sought better battery life, and the jump from JB to KK has been awesome for me. The overall system drain has been reduced dramatically. Yes, the screen is the one constant battery consumer...but all other areas can be improved upon. I can't wait for CM to further refine this KK ROM...I am expecting even better results. Now if Verizon would offer up just one more set of radios....
[Samsung Galaxy Nexus] jrk190:
Sorry to go into that, haha. As for bionic, it's a part of CM's code, not the Droid Bionic. I'm honestly holding out to see if Verizon gets the Nexus (Bloated, and covered with a huge checkmark on the back).
[Samsung Galaxy Nexus] Big ZD:
No need to apologize. I was just saying you don't owe anyone an explanation. We all have our reasons for wanting the most out of an aging phone.
[Samsung Galaxy Nexus] ca.reaper:
I am running the 1/29 nightly since last night. I have an hour drive in to work and I go in and out of 4g, 3g and even lose signal for a bit normally. The 1/29 build seems to be rock solid so far and I have not had the data switching problem that I have had in previous builds. I think I may stick with this one until another stable release pops up. Battery life is awesome as well, I am at 74% with 7h 21m on the battery. And that's with being in a crappy cell area.
[Samsung Galaxy Nexus] wbmsp:
Did you dirty flash or completely wipe?
[Samsung Galaxy Nexus] ca.reaper:
I dirty flashed. Actually used the OTA in settings/about phone
[Samsung Galaxy Nexus] ulnevrwalkalone:
Just updated to 1/30 nightly and it was not picking up 4g, flashed the rollback.zip and it picked up 4g.
[Samsung Galaxy Nexus] ca.reaper:
Same here. I swore I would stay on 1/29 but my flashing addiction got the best of me. I did restore my 1/29 backup though and I am happy again.
[Samsung Galaxy Nexus] CaliTilt:
Is Google Navigation working on 1/29 and 1/30? I see that GPS is working but navigation will is stuck at the starting point. I have not done a clean install and will try that next.
[Samsung Galaxy Nexus] klobkelosh:
Working fine on 1/31
[Samsung Galaxy Nexus] klobkelosh:
Vanir team found the source of the bionic problem. http://vaniraosp.goo.im/#/c/9911/ . Anyone know how to get this reverted in source?
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
Bluetooth toggle via profile has been resolved in 10.2.1... Just in case anyone was wondering
[Samsung Galaxy Nexus] Big ZD:
Communicate it to the CM maintainers via G+
[Samsung Galaxy Nexus] klobkelosh:
I did. I sent it to bekit and something15525.
[Samsung Galaxy Nexus] klobkelosh:
Response from Bekit on g+ - "Thanks! I'll take a look at it and either do a similar revert, or get the code fixed up."
[Samsung Galaxy Nexus] .SoFLy.:
Super, thanks for catching this and making sure it's getting fixed, many people will be happy :)

Just confirming, If I flash your rollback with a nightly, that should also fix the issues?
[Samsung Galaxy Nexus] klobkelosh:
Correct!

Oh, and just saw this on cm forum :

[quote name='Big Z' timestamp='1391464094' post='442860']

Looks like it's going to be fixed in the next nightly! There's a bionic commit in the change log.
[Samsung Galaxy Nexus] Meticode:
A couple of questions regarding some issues tha have plagued me the last 4-5 builds?

1.) I get g.apps and Google Sound Search closing messages randomly? Everytime at start up. Anyway to fix this? I found that disabling the Sound Search app works for this? Any way to fix the actual problem?

2.) The phone will randomly totally lock up when I'm connected to LTE or 3G. It'll let me lock the phone and turn the screen off, but it won't let me turn the screen on and lock the phone. I have to pull battery. When I use Wifi this doesn't happen at all and the phone runs fine? Any ideas?

I've tried doing a full clean install wiping cache, dalvik, etc and reset, no luck.