yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sruel3216:
I had a **** load of force closes dirty flashing 8-13. Did a clean flash and everything is good
[Samsung Galaxy Nexus] JPBeard21:
I finally got my data working by restoring my last nandroid. Let's see what happens going back to the 8-13 build.
[Samsung Galaxy Nexus] chikimonke:
Yup, I've almost thrown my phones a few times. Which launcher are you using? I was on Nova, and the lock ups happened constantly, switched over to Apex, and things have been better, but still happening here and there. I've run Fancy, ASKP and Golden, happened on all of them, even tried going back to an earlier build, still happened, and did a full wipe of my phone, still happened. I'm glad to see I'm not the only one having the issue.
[Samsung Galaxy Nexus] laureanop:
Two lock ups today on 08 13. Didn't happen before that

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] jonstrong:
As with the last few nightlies, I only wiped Cache and Dalvik cache, flashed the nightly, my favorite gapps (latest from Paranoid Android team), flashed Fancy kernel r38, and it's been perfect. No issues yet.

...beamed to your puny "planet" from my Nexus 10
[Samsung Galaxy Nexus] justen7723:
Official cm10.2 is out http://get.cm/?device=toro

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jonstrong:
Just got the in-app notification... About to try it...

...beamed to your puny "planet" from my Nexus 10
[Samsung Galaxy Nexus] chikimonke:
So based on this information by the PA team, I'm pretty certain this is a Google issue now.
[Samsung Galaxy Nexus] jonstrong:
Perhaps... Still doesn't explain why some have issues while others of us do not (no issues here). Possible, I guess, that jss is less stable under certain conditions which only some of us encounter.

...beamed to your puny "planet" from my Nexus 10
[Samsung Galaxy Nexus] chikimonke:
I imagine it has to do with the exact setup of your phone. The lock ups happened constantly with the latest Nova launcher, but now only 3 or so times a day using Apex launcher, for me that is.
[Samsung Galaxy Nexus] laureanop:
I didn't have any issues till yesterday. Another issue popped up today that never happened in my phone: status bar clock frozen at 149 am

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] baling:
New gapps package from goo.im is out for 4.3 builds includes new plays store and all updated gapps here is the link for everyone just in case http://goo.im/gapps/gapps-jb-20130813-signed.zip
[Samsung Galaxy Nexus] Rahshaka:
Anyone know what nightly was the last built from JWR66V?
[Samsung Galaxy Nexus] infinit22:
What cherry picks are in this that are not in the official cm10.2?
[Samsung Galaxy Nexus] chikimonke:
My guess is everything listed here. http://fitsnugly.euroskank.com/?rom=cm10&device=toro
[Samsung Galaxy Nexus] jlvlawrence:
Is anybody having issues changing text messaging ring tones. I can't seem to get them to stick.
[Samsung Galaxy Nexus] aggrophobik:
No issues here.

Sent from my Nexus 7
[Samsung Galaxy Nexus] jlvlawrence:
Clean flash of yesterday's build fixed it!
[Samsung Galaxy Nexus] mongonexus:
alright wise guys, who stole my LTE icons in the 8-18 build,,lol,lol thanx guys ,,steve
[Samsung Galaxy Nexus] SirBindy:
Didn't even notice till now... thanks a lot!

Also, I got a whole lot of Exchange service FC's on 8/18's build. They seem to have stopped, but i got like 4 in a row at first.

I don't even use exchange.
[Samsung Galaxy Nexus] blackhand1001:
What google apps package are you using. I remember some of them causing that. I recommend downloading the official 8-13 ones.

http://goo.im/gapps/gapps-jb-20130813-signed.zip
[Samsung Galaxy Nexus] Kaptinkrunk:
I've been using the believe gapps

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
I had the same issue and went back to 8/17. As soon as I booted I got a bunch of FC's in a row for Email. Then got a few for Exchange.

I'm using the PA gapps (pa_gapps-full-4.3-20130805a-signed.zip). I have the latest 8/13 gapps, but haven't had any issues with the PA gapps.
[Samsung Galaxy Nexus] jlvlawrence:
I had the same force closes. They stopped and I haven't had any issues since then.
[Samsung Galaxy Nexus] SirBindy:
Same Email/Exchange FCs on 8/19. Will try different gapps and report back.

EDIT: Nope, same issues with official gapps from goo.im
[Samsung Galaxy Nexus] bigbear6708:
Sorry my noobness. Since fits does the cherry picks... does that mean those added features are not in official nighties yet? Also.. How does this ROM run in comparison to official 10.2??
[Samsung Galaxy Nexus] kuronosan:
Do they know what the deal is with the focal green border glitch and the spastic data drops yet?
[Samsung Galaxy Nexus] SirBindy:
The OP says "If cherry picks disappear, it's because they were merged, abandoned or conflict with the current source or other cherry picks."

So.. yes. The cherry picked features added in this are not in the official nightlies. There would be no point in doing this if they were identical.
[Samsung Galaxy Nexus] bigbear6708:
I thought cm usually leaves features out of stable builds and throws the kitchen sink at the nightlies...
[Samsung Galaxy Nexus] jonstrong:
I've had the FC's with exchange and email...but it seems that it only starts up when I try to turn on bluetooth -- then it all goes nuts. Various parts of BT fail, BT turns off, restarts itself, then exchange and email start flipping out. It seems to get into a loop of FC's and restarts, and one time tonight the phone rebooted after this went on for a few minutes. As long as I leave BT off, this doesn't seem to happen. All started with the 8/18 build -- and I seem to have the exact same condition whether I try jellybro or "official" CM10.2 nightlies....
[Samsung Galaxy Nexus] fitsnugly:
CMAccount? Yesplz.
[Samsung Galaxy Nexus] JPBeard21:
As always, huge thanks for staying on top of the most recent CM commits and the special blend of cherry picks. That combination keeps me running these builds.

Although I shouldn't report this as a bug since I am guilty of dirty flashing, when pressing the back key to exit an app, instead of closing, it brings to the recent apps list. Another press on the back key returns to the app I was trying to close. I usually wipe system before flashing but was distracted and skipped that step this build (8-20). I will try again and see if this continues, just wondering if anyone else has noticed this behavior.
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
I haven't had issues with Bluetooth or Navigation keys, but I was having a lot of email and exchange force closes and random freezes. This morning I clean flashed the 820 build and the 813 gapps from rootz and its been running like a champ all day. I'm afraid that might be a recurring issue, as I saw it happen when 4.3 first dropped, but I hope not.

gnex|s7pro|dinc
[Samsung Galaxy Nexus] JPBeard21:
Just wanted to post that my issue was created by not wiping the system partition. After wiping the system position and reflashing with 8-13 gapps, haven't had any issues yet.
[Samsung Galaxy Nexus] Blanko6:
Your not planning on adding transparency or nav size setting in the future are you ?

Thanks
[Samsung Galaxy Nexus] T-Keith:
Transparency? Yes please.
[Samsung Galaxy Nexus] modernbummer:
Highly doubtful unless CM actually implements it. Fits only cherry picks from CM sources.
[Samsung Galaxy Nexus] bigbear6708:
Is there anything different about these builds re: battery life. It seems to be better than "official" cm build
[Samsung Galaxy Nexus] greyhd:
On 082313 the option to boot into recovery is gone.
[Samsung Galaxy Nexus] parkson:
Have you tried enabling Advanced Reboot within developer options?
[Samsung Galaxy Nexus] greyhd:
Now I feel really dumb. Thank you for this. I guess I was use to it being checked automatically.
[Samsung Galaxy Nexus] bigbear6708:
Do the latest nightlies here have the MMS issue that the official builds are facing??
[Samsung Galaxy Nexus] greyhd:
Yes, 824 has the mms issue
[Samsung Galaxy Nexus] wund3rground:
I'm on 8/23 and I can't send MMS, so I'm guessing so... I haven't flashed 8/24 yet...
[Samsung Galaxy Nexus] oubeichen:
could you please add this patch?http://review.cyanogenmod.org/#/c/47134/5

because I have a wifi/3g switch problem,maybe it is about the signal in my country.

thanks
[Samsung Galaxy Nexus] blackhand1001:
I think the MMS issue is also related to the carrier text missing in the notification drawer and data toggle.
[Samsung Galaxy Nexus] ironfisted:
I am having issue of 3g not working going from 4g to 3g and WiFi to 3g. Verizon here
[Samsung Galaxy Nexus] bama17:
Yep
[Samsung Galaxy Nexus] atlp99:
I agree, and I think the issues with carrier text and MMS are also related to the data drop issue.
[Samsung Galaxy Nexus] mongonexus:
8-25 up guys,,steve:good:
[Samsung Galaxy Nexus] cms5423:
Do MMS and the network identification work on 8/25?
[Samsung Galaxy Nexus] mongonexus:
at this point it looks like the answer is negative,:crying:
[Samsung Galaxy Nexus] JPBeard21:
Anyone have a link to the 8-18 build? Looking for the latest build without the MMS issues. Thanks
[Samsung Galaxy Nexus] sruel3216:
Same lol
[Samsung Galaxy Nexus] JPBeard21:
I found a working link over on rootzwiki.
[Samsung Galaxy Nexus] aggrophobik:
I too am seeing issues swapping back to WiFi w/out doing it manually, not to mention MMS bug. Not really a deal breaker, but here's to hoping it's addressed soon.
[Samsung Galaxy Nexus] cms5423:
Anyone try the new build (20130829.1829)? And if so, does MMS actually work now? **Crosses fingers**
[Samsung Galaxy Nexus] mongonexus:
yes at least for me this build has working mms, and verizon is back on the lockscreen, thankyou all for fixing and sharing,,,steve
[Samsung Galaxy Nexus] aggrophobik:
Same here, MMS working well, as well as handoffs. Thnx a bunch.
[Samsung Galaxy Nexus] kuronosan:
Not working for me
[Samsung Galaxy Nexus] blackhand1001:
Adding

wifi.supplicant_scan_interval=30

To my build.prop fixed my WiFi issues for me. My nexus 7 has has this line so I added it to my galaxy nexus and it seemed to work. I think the default is 15 but 30 seemed like the best compromise between battery and how fast it auto connects. It doesn't seem to actually mean the number of seconds. I think in 4.3 they no longer let the driver decide this behavior and someone left this line out of the build.prop so it never auto scanned.

Edit: Nevermind, the issue seems to have come back after deep sleep
[Samsung Galaxy Nexus] z0mghii:
MMS not working for me on 30th nightly
[Samsung Galaxy Nexus] tattedupboy:
One issue I've had on several Android 4.3 ROMs lately is that my screen timeout settings never seem to stick, and neither do my ringer volume settings. My personal screen timeout preference is 2 minutes and my ringer volume preference is turned all the way up, but they always seem to set themselves to 15 seconds and vibrate (respectively), and having to readjust them gets annoying as hell. Is anyone else experiencing this? How can I stop it?
[Samsung Galaxy Nexus] Chopes:
Anyone have a direct link to the chronic kernel? One I tried boot looped me lol.

Not sure what version and all that

Update: has anyone been having problems with the voice+ stopping working after moving around and passing through a poor connection area? Until a reboot which then starts it again until it decides to die.

Is this a particular process that is dying that I can just restart instead of doing a full reboot?
[Samsung Galaxy Nexus] tattedupboy:
I don't really know what I did, but I finally succeeded in getting my screen timeout settings to stick. However, I'm still having the issue of my ringer volume settings not sticking. Specifically, I'll turn my ringer volume all the way up, but whenever I get a notification, it sets itself back to vibrate. How can I get my ringer volume preferences to stick? Since I use a bluetooth headset I don't miss any calls, but nevertheless, the fact that the ringer volume control seems to have a mind of its own is quite annoying!
[Samsung Galaxy Nexus] wund3rground:
Has this been addressed yet?

http://review.cyanogenmod.org/#/c/48873/
[Samsung Galaxy Nexus] Chopes:
I've had similar issues
[Samsung Galaxy Nexus] mongonexus:
new build up guys and gals, happy holiday to all ,, thankyou rick,,steve
[Samsung Galaxy Nexus] wund3rground:
Mobile data is still farked...
[Samsung Galaxy Nexus] tattedupboy:
I believe I've finally figured out what was causing my ringer volume to drop on its own. I had a profile scheduler installed that would automatically decrease the ringer volume during certain set times, such as while I was in church. As soon as I uninstalled the profile scheduler, this issue stopped. I guess until the developer fixes this, I'll have to remember to turn the ringer on and off manually.
[Samsung Galaxy Nexus] Azrith:
Anyone else try the 9/4 build? I'm noticing a crash on the AOSP keyboard when I try to swipe, normal typing seem to works fine. Not sure if it's the 9/4 build OR my dirty flash methods. :laugh:
[Samsung Galaxy Nexus] blackhand1001:
What google apps package did you install. Also try wiping data on the aosp keyboard app.
[Samsung Galaxy Nexus] Azrith:
I didn't reflash gapps as I've not been wiping system - that has been working for me the last few dirty flashes. Clearing data didn't work either. Maybe a format of system and reflash rom/gapps?
[Samsung Galaxy Nexus] wund3rground:
Is data still wonky on the latest build?
[Samsung Galaxy Nexus] parkson:
Data is wonky on all 4.3 roms.
[Samsung Galaxy Nexus] dmsaia:
No issues

Been running this rom now since the initial build. Dirty flash a new nightly once every 5 days or so with a cache/dalvik wipe. Using Mpokang kernel I am getting pretty good battery life, even though my battery is starting to take a poop. I personally haven't had any data issues whatsoever, gps is almost instantaneous, no wifi issues, no force closes, nothing. It's getting to the point where I want something to go wrong just so I have a reason to flash a new rom.
[Samsung Galaxy Nexus] z0mghii:
9/6/2013 build not booting for me, going back to 9/4
[Samsung Galaxy Nexus] aggrophobik:
Weird, reading a lot of these. Booted fine for me.
[Samsung Galaxy Nexus] T-Keith:
U guess there is a problem on the 9/6 build for all phones, dont flash.
[Samsung Galaxy Nexus] Azrith:
You don't use Bluetooth in a car I assume? This ROM is plagued by the ugly CM bug with Bluetooth where it starts to get reboot happy once you mess with Bluetooth audio in a car head unit. Other than that - it's pretty sweet, I agree.
[Samsung Galaxy Nexus] jlvlawrence:
I haven't had any Bluetooth issues with my Sony head unit in my GTO.
[Samsung Galaxy Nexus] cujo6801:
You just wanted us to know you had a GTO..... Lol

sent from the DOG pound
[Samsung Galaxy Nexus] Azrith:
Odd. I noticed in other threads it tends to be Nissan's (all types) and Mazda's (all types) that seem to be quoted most often. Maybe it's certain head unit types... *shrug* It definitely worked fine pre 8/17 or there about so something CM changed around that time has broken all builds since for my BT at least.
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
NFC

I've recently discovered the amazingness of NFC tags + CM profiles, but I'm annoyed with having to wake and unlock to change profiles. I know there are zips out there that disable/change the nfc.apk, but I don't want to flash the wrong one.

Does anyone have a link/zip that will allow NFC with the screen off or while locked?

The ones I've seen aren't confirmed working on CM10.2...
[Samsung Galaxy Nexus] ironfisted:
Any change in handoff data issues in 9/30 build
[Samsung Galaxy Nexus] ironfisted:
Not coming off of airplane mode. That still doesn't work
[Samsung Galaxy Nexus] blackhand1001:
Data is pretty much broken in 9/30. Same with WiFi. They work some of the time but then the phone process crashes and everything gets screwed up. WiFi after a while ends up saying null instead of connected and doesn't get fixed until a reboot. Even worse is that it takes mobile data with it, so even if your mobile data hadn't crashed it stops working.
[Samsung Galaxy Nexus] T-Keith:
Is data working better on the 10/1 build?
[Samsung Galaxy Nexus] kuronosan:
Data is working for me but as of 10/5 the led won't turn off.
[Samsung Galaxy Nexus] t1.8matt:
Would it be a reasonable idea to start a thread in the general section as to which VZW roms have working data handoffs, or is it just a waste of time and space?
[Samsung Galaxy Nexus] t1.8matt:
Seen Maguro CM11 builds are up, any chance you'll build for Toro again?
[Samsung Galaxy Nexus] modernbummer:
First CM11 build for toro up: http://fitsnugly.euroskank.com/?rom=cm11&device=toro
[Samsung Galaxy Nexus] tattedupboy:
Great! Couple of questions though. Can we expect the same bugs (black boxes, freezes, reboots, and graphical glitches) that are present in all the other kitkat ROMs for toro? Also, which gapps package should we use with this?
[Samsung Galaxy Nexus] jlvlawrence:
I'm sure it has the glitches as well. You could probably use paranoid android gapps or any variety of the 4.4 gapps packages that are out there.
[Samsung Galaxy Nexus] fcisco13:
Running for about 2 hours, no reboots, no freezes, glitches here and there. Great rom as always by fits.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
I've never been so excited to flash a rom.

Post 619 from this thread: http://xdaforums.com/showthread.php?t=2071021&page=62 leads me to believe the glitching should be over soon. That's the thread where devs are working on fixing the reboots and webview/rotation issues, in case anyone else is interested in reading up on the progress.

I personally don't even care about the screen issues. As long as this stops random reboots it's daily driver ready for me...
[Samsung Galaxy Nexus] modernbummer:
New build up with this commit included: chromium: gpu: Refactor GpuMemoryBuffer framework for multi-process support

http://fitsnugly.euroskank.com/?rom=cm11&device=toro
[Samsung Galaxy Nexus] ironfisted:
What does that mean?
[Samsung Galaxy Nexus] justen7723:
It means no more black boxes in stock browser or Google now searches.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] modernbummer:
Fixes black boxes in stock browser, google search, etc. LTE doesn't appear to be working, however.
[Samsung Galaxy Nexus] spearman792:
Can anyone else confirm this?

I was holding off on flashing a 4.4 build until the graphical issues were fixed, but if LTE is broken, then I think I can wait a few more days :P
[Samsung Galaxy Nexus] DevVorteX:
lte works just fine for me DC area. Also can confirm that black boxes are gone. There's still those little streaks in the screen when rotating or doing the screen off animation thingy, but I can finally read my email without scrolling up and down 30 times :)
[Samsung Galaxy Nexus] t1.8matt:
Sweet. That was the only thing that was bugging me was not being able to read my gmail. Can't wait to flash this new build.
[Samsung Galaxy Nexus] gardobus:
scroll

zoom

scroll

zoom

scroll

scroll

read a few lines

repeat

So glad that they figured out a workaround!
[Samsung Galaxy Nexus] t1.8matt:
I can't play back videos recorded with the camera app. Is this a known issue on KK?
[Samsung Galaxy Nexus] Sheetzie03:
A lot of these 4.4 ROMs I would think that lte wasn't working. But it wasn't the case. After the initial boot, I reboot once(,before any setup), lte then Pops up after the reboot, and then go thru the setup. So I do this now with every 4.4 ROM and lte has not been a problem.

Hope this helps your issue.

♦ToroNex-KK'd
[Samsung Galaxy Nexus] modernbummer:
I dirty flashed, so maybe that was the issue.
[Samsung Galaxy Nexus] blackhand1001:
Ugh, chromium webview is awful. Why didn't google just update the old webview to the latest version of webkit. The strock browser and all apps that use webview suck now.
[Samsung Galaxy Nexus] jlvlawrence:
I dirty flashed and LTE is working for me.

Sent from my Nexus 10
[Samsung Galaxy Nexus] ldp_frog:
Everything running great, but I feel like I am missing something. I don't see the developer options in the settings when I went to enable ART, and the phone/dialer app is also not identifying businesses that have numbers listed in Google Maps. These are the 2 biggest reasons I upgraded to 4.4 :( what am I missing??
[Samsung Galaxy Nexus] cujo6801:
Go to about phone and tap build number about 10 or 12 time...

You'll get what you need

sent from the DOG pound
[Samsung Galaxy Nexus] justen7723:
Go to about phone and click on build number about 7 times to enable developer options. ART will take a while to boot

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ldp_frog:
Hah thanks guys. Wasn't convinced I wasn't being trolled at first! Unfortunately, after I enabled ART and rebooted, I got a continuous "Unfortunately, Google Search has stopped". Had to go to settings from the quick settings and re-enable dalvik to make my phone functional. Anyone ever heard of this?
[Samsung Galaxy Nexus] justen7723:
What gapps did you use? The latest PA gapps working great with ART for me.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] mattyd3:
LTE

I was an idiot tinkering around and switched to cdma mode, now i cannot get LTE back. Dirty flashed the rom and PA gapps again in hopes of the LTE coming back to life no luck as of yet... Any work around short of doing a clean install again?

Thanks.
[Samsung Galaxy Nexus] DevVorteX:
ha ha, I did the same thing, then just dirty flashed another cm based 11 rom that has the overlay already fixed, switched it back, then re-flashed this one.

I think you can also do *#*#4636#*#*, then go to phone, and set the prefered network type to gsm/cdma (auto)

I don't know if that last way sticks after a reboot though, haven't really messed with it.
[Samsung Galaxy Nexus] mattyd3:
Awesome! That did work to kick it over to the LTE radio, had no clue about the *#*#4636#*#* until now... however, I can also confirm that it does not stick after a reboot. I think i'll just stick with this band-aid fix until the fix is merged.
[Samsung Galaxy Nexus] dyussen:
Google Now crashes when I try to add a widget to the home screen. Anyone else with this issue?

Clean install. Working perfect so far, besides this.
[Samsung Galaxy Nexus] justen7723:
No problems here, On 11/22. Won't get to 11/23 until after work.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Nandrew:
Love the new boot ani :)
[Samsung Galaxy Nexus] t1.8matt:
Hey guys, I still can't get video playback to work on anything I record on this rom. I've tried 2 different gapps, I've used Mpokang 1080 kernel, PA Kernel, flashed the latest build and still can't get it to work. Does anyone have gapps with KNOWN working video playback on videos recorded on 4.4, and is there any chance it could be the kernel? I don't understand why it isn't working.
[Samsung Galaxy Nexus] fcisco13:
My videos work fine, i just recorded some and played them back fine, using 11-23 build with pa gapps.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] xMoment:
I am also on 11-23 build with latest (11-19) pa gapps but can't play either newly recorded or previously recorded video when using the camera app (swipe to the left when camera/video recorder is loaded). However they played fine using the Photos app. I no longer have a "gallery" app, I noticed
[Samsung Galaxy Nexus] t1.8matt:
Yep, its a gallery issue. I'm on 11/23 build and it doesnt work through gallery but does through the photos app like you said.
[Samsung Galaxy Nexus] fcisco13:
I have a gallery app and they play, they also play when on camera and i swipe left to access videos.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] t1.8matt:
OK, well it doesn't work for me. I don't know what else to tell you.
[Samsung Galaxy Nexus] fcisco13:
Only thing i can tell you is to try a fresh install, wipe, wipe, and flash.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] dyussen:
Wiped Google Now fixed it. Strange.

Been on it all day, this now seems quite stable.. At least enough I don't have to roll back to cm10.2.