yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johnhimm:
I tried it myself this morning and i agree so I flashed back to 10.1.3. When on 10.2, manually switching between 4g/3g i timed 40 seconds, on 10.1.3 it took 6 seconds. I don't see any updated features in 10.2 to justify this laggy performance.
[Samsung Galaxy Nexus] nycebo:
Can't disagree. Hand off times are terrible presently. However, I DO find that the performance of the OS on my SGN more than justifies keeping CM10.2 on the phone.
[Samsung Galaxy Nexus] KWKSLVR:
Hand off isn't going to improve until Verizon graces us with new radios.
[Samsung Galaxy Nexus] jlvlawrence:
I flashed an unofficial aokp 4.3 build yesterday and the hand-off is much better than the current cm nightlies.
[Samsung Galaxy Nexus] chazzdjr:
Hand off on Pure Toro ROM is far better than CM's. Error311 has been messing around with things to improve it. I don't know what he's done.
[Samsung Galaxy Nexus] johnhimm:
Which ROM did you flash?
[Samsung Galaxy Nexus] jlvlawrence:
Newest nightly from hillbilly hacker at androtransfer.com
[Samsung Galaxy Nexus] JeeperDon:
I'm not seeing any real reason to 'gotta have 4.3 now, big wow factor!' I just went back to 4.2.2, CM 10.1.3 RC2. I think I'll stay there until I quit hearing of CM4.3 issues. After a 10+ day breakage with 'no phone number in Status', then two days of 'wrong size, won't boot', I'm not sure the toro CM monitor is as efficient as the old CM toro days. I don't recall this sort of 'fix lag' in the CM10 to CM10.1 transition. I can wait.
[Samsung Galaxy Nexus] sandrewmorrison:
FYI for those that couldn't get recent nightlies to boot, tonight's works.
[Samsung Galaxy Nexus] johnhimm:
I agree totally, and 10.1.3 is running flawless with decent battery.
[Samsung Galaxy Nexus] nsnowdeal:
Did you flash the 9/9/13 over the 9/4/13 nightly?
[Samsung Galaxy Nexus] sandrewmorrison:
Yes, thru the CM updates tool in the settings.
[Samsung Galaxy Nexus] Sharpbarb:
I'm running 10.1.3 RC2.

I've had a problem with Chrome and Pandora. Basically, Chrome just randomly crashes pretty often. If I try to use Chrome while Pandora is playing, eventually Pandora will just shut down.

Is anyone else having a similar experience?

I understand there are some logging tools that can be used to help reporting to problem to the CM team. Can someone point me in that direction?
[Samsung Galaxy Nexus] ironfisted:
Have we fixed the data bug yet?
[Samsung Galaxy Nexus] hotrodwinston:
Sorta - data sometimes drops and toggle data on /off will fix, sometimes it takes an airplane mode toggle, sometimes it takes a reboot.

But it does work it does hold your number and prl and it does send/receive mms.
[Samsung Galaxy Nexus] zandroid:
You can use alogcat from the play store.

https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en

It will output a file you can post here or send to the CM team.
[Samsung Galaxy Nexus] past_pluto:
All 4.2.2 Roms crash out apps when using Pandora and a browser. There is a memory issue somewhere. The more stock a ROM is the better it is. MMuzzy is only ROM it hasn't got annoying on.
[Samsung Galaxy Nexus] zandroid:
I checked out the PURE Toro Rom after seeing your post. The other devs need to take a look at what error311 is doing with that Rom in regards to data hand off. I'm not sure what he did, but I have had no data hand off issues with that Rom. He states in the change logs that the hand off issues are fixed. When I leave my house I have 4G, then hit an area with very little service and it switches to 3G, then back to 4G at work. If I move about my building, it will switch between 4G and 3G.

The Rom itself is ok. He's using an AOSP base and cherry picking features, which is fine. However, it is missing a few features I would like to have; specifically pop up text message notification and lock screen options are limited.
[Samsung Galaxy Nexus] swyecso:
Whether it be a new radio, error311, or whatever I hope something fixes it soon. I just spent all night reverting back to 10.1.3. My solution to the data problems was just to disable LTE but hey I'm paying for that and not this ROM so I had to make a business decision and revert.

BTW 3g is a lot slower than I remember nowadays but maybe that's just me
[Samsung Galaxy Nexus] tattedupboy:
Is CM account login available on the night lies yet?
[Samsung Galaxy Nexus] ExodusC:
If this is true, someone should really be asking him what changes he's made, and then get someone to push them to the CM10.2 toro codebase.

From what I gather, broken data hand off is the only deal-breaker for most on the current nightlies. I'm suffering through it, and it's good to know someone has (supposedly) found a working solution.
[Samsung Galaxy Nexus] mouf32:
My biggest was the MMS and after the 9.6 build that wouldn't even boot I reverted back to stock for a bit...
[Samsung Galaxy Nexus] ExodusC:
MMS has been fixed for roughly a week now on the official nightlies, thankfully.

The only huge issue that remains seems to be data handoff.
[Samsung Galaxy Nexus] ssmcd:
Is A2DP BT not connecting a known issue with the last few nightlies?
[Samsung Galaxy Nexus] danman7:
Not that I've noticed. I'm running the 9/11 nightly and had no problem connecting/streaming to bluetooth headphones and my car last night. I received track information on the car display as well (Thank you 4.3 for bringing back AVRPC!)
[Samsung Galaxy Nexus] mouf32:
Good luck to everyone on their CM10 GNex adventures... I went and picked up the G2 on lunch yesterday. Hopefully CM10 comes to it sooner then later.

FYI I have a pogo dock that has been modified for the VZW Gnex if anyone wants it.
[Samsung Galaxy Nexus] johnhimm:
Car dock?
[Samsung Galaxy Nexus] mouf32:
No the pogo desktop dock with 3.5mm audio out.
[Samsung Galaxy Nexus] MattyBoy4444:
The latest nightly, 2013-09-13, may have a fix. It seems better, but will know more with time. The fix I am talking about is listed as "CdmaLte: Fix 3G reported as unknown on certain devices..."

github.com/CyanogenMod/android_frameworks_opt_telephony/commit/f2c1ee61135815f84642ea7663c45e4ebeb9fd0f
[Samsung Galaxy Nexus] kfan12:
Just recently after a clean flash to CM 10.1.2 from 10.1.0, installed the latest Gapps for 4.2.2 and installed a GPS fix I've been getting a SIM removed error which would need a reboot to cure. Is this ROM related or is my SIM card going bad?
[Samsung Galaxy Nexus] KWKSLVR:
I get that error from time to time and have to reinsert the SIM. I assume it's the SIM card itself, I've just never bothered to have it replaced.
[Samsung Galaxy Nexus] swyecso:
I was looking at that and hoping it would help out. Any final word?
[Samsung Galaxy Nexus] ssmcd:
Hmm I was able to connect to my car initially, both telephone and A2DP. But it won't reconnect on its own. And when I manually reconnect, it only connects to the phone and I can't play audio. I am also on the 9/11 build.
[Samsung Galaxy Nexus] MattyBoy4444:
Nope. Didn't seem to help!
[Samsung Galaxy Nexus] swyecso:
Dang one day we'll be saved. I'll probably be getting the Nexus 5 when it comes out anyway though.
[Samsung Galaxy Nexus] jeff b:
Just went out to my car. First time i have ever seen track info from this phone!

-----

Not sent from a PC......or a red delicious.....but from a robot with a human appearance.
[Samsung Galaxy Nexus] General Crespin:
Does anyone know if the base Sync system in the 2013 Fords supports AVRPC?
[Samsung Galaxy Nexus] kmcrane:
My carrier label is just caricatures.. No longer says Verizon Wireless on pull down or the quick tiles. Just a bunch of symbols.
[Samsung Galaxy Nexus] nitsua98:
I had that happen to me on the 9/14 unofficial aokp build by Marc Landis.
[Samsung Galaxy Nexus] z0mghii:
Getting that also haha
[Samsung Galaxy Nexus] lonnyrs:
This may have been covered, and if so, my apologies.. But I'm not getting the "Navigation" with the Gapps in the op. I've tried another version, and still nothing. What am I missing here?
[Samsung Galaxy Nexus] pitchdarkice:
The carrier label is fixed in the 20130915 build
[Samsung Galaxy Nexus] hotrodwinston:
Navigation has been merged into maps now
[Samsung Galaxy Nexus] chazzdjr:
So what's the verdict? Did the 14th nightlie resolve the radio issues?
[Samsung Galaxy Nexus] hotrodwinston:
Reports said no luck - will be testing 9-15 tomorrow as I work in a sprint only area and have to pass thru a no signal area to get to work and always lose data on 10.2 both going to work and coming home.
[Samsung Galaxy Nexus] pitchdarkice:
I still have the slow radio issue on the 20130915 build. Pretty much have to reboot my phone to get back my data connection.
[Samsung Galaxy Nexus] johnhimm:
I can also confirm that the 3g/4g transfer has not been fixed on 9/14 or 9/15.
[Samsung Galaxy Nexus] atrophis:
It appears the toro build for 9/16 failed today, along with multiple other devices. Guess we won't get another build until tomorrow. Ahh, the joys of running nighties. :D
[Samsung Galaxy Nexus] hotrodwinston:
That's fine - 915 runs great - I'll most likely wait till something changes with data or new features before flashing another release.
[Samsung Galaxy Nexus] NeoandGeo:
Trying out the 9/17 build. What is needed to get native tethering to work?
[Samsung Galaxy Nexus] MattyBoy4444:
My 3G/4G Data Drops seems to have been resolved by changing my build.prop to include

ro.telephony.default_cdma_sub=0

http://xdaforums.com/showthread.php?p=44394564

It was merged into Google code a while ago, but never into Cyanogenmod.

https://android.googlesource.com/de...^1..c3ef7ffe27e64eb3942fe103eaabff9cea529539/

We should make sure others experience the same thing. If so, how do we get this merged into CM?
[Samsung Galaxy Nexus] jaredsleboeuf:
I have no idea what changed in the recent nightlies, but as of 9/17, I'm able to send/receive MMS, SMS, etc. on 3G/4G without problems. I hope it isn't just a fluke. As for data drops, transfer problems, I'm going to try to stay on 3G for a while in the hopes that doing so mitigates the issue. /crosses fingers
[Samsung Galaxy Nexus] johnhimm:
If you read the rest of that forum link people say that it did not fix data drops.
[Samsung Galaxy Nexus] MattyBoy4444:
I think there are a few issues going on. Data Drops at end of Phone calls was supposedly fixed in some other change that did get merged into CM. I don't experience this issue. The build.prop fix seemed to correct the 3G/4G Handoff. I used the wrong wording before. At least this is my experience. I am running CM 10.2 nightly from 9/14.
[Samsung Galaxy Nexus] anotherdroid:
yes, that is what i should have said. all our phones are the same and all our problems are unique...
[Samsung Galaxy Nexus] atc3030:
anyone having issues with the device just randomly waking up. or like i hit the sleep button, it turns off the screen but the screen turns right back on. cant get it to stay off. at the end of the day I have like 3 hours of screen on time. anything? nightly 9/04 and 9/06 both did this. tried running with franco kernels 246 and 248 and same problems. Tried clean flashes and stock kernel as well. Tried to run a log cat but it wont do it while logged into it through adb.

UPDATE: Just found out that the phone thinks it is charging. as in, like it was screen off, you plug it in, then the screen turns on. thats what is happening then once the screen is on it realizes its not charging and removes the charging icon. however, the screen will not turn off if left to sit.
[Samsung Galaxy Nexus] xVallex:
Having an issue installing Swift key 3. Settings force closes when I try to make Swift key the active keyboard.
[Samsung Galaxy Nexus] andino:
Anyone notice that the quick reply and call buttons in the notification banner have switched? I accidentally made a phone call today when trying to reply to a message. I'm on the 9/4 build.
[Samsung Galaxy Nexus] Quod:
I had that problem with one of winner's builds. Turn on swiftkey through Settings->Language&Input.
[Samsung Galaxy Nexus] swyecso:
My only guess is that because it opens the messaging app and opens the new message, the phone thinks that the message has been viewed thus it is cutting off the notification alert because it has technically been opened its still a new feature so I'm sure integration will get deeper and the issue will be fixed soon I personally don't like the popup messages I always liked that in android you can get to your notification whenever you are ready don't want something popping up while I'm playing a game or something but just using the quick reply in the notification window is perfect for me and the alert is not cut short
[Samsung Galaxy Nexus] gonzlobo:
You pop up message enthusiasts are closet iFanboys. Heh.
[Samsung Galaxy Nexus] blay76:
I lol'd.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Christopher3712:
Them's fighting words.

(I secretly agree) lol
[Samsung Galaxy Nexus] Christopher3712:
I've had the Face Unlock issue every few builds or so. I did a search and found the answer under XDA's XOOM forums. Here were the steps I took to fix it:

delete the 'pittpatt' folder located in /system/vendor/

turn off facelock

reboot into recovery

clear cache and dalvik cache

reflash gapps

fix permissions

power on device

set up facelock

I was able to regain my facelock function after doing so.
[Samsung Galaxy Nexus] blackhand1001:
I have a fix for the lagginess in builds from the past week and a half or so. The culprit is the surface flinger library. It is the android compositing system and some changes recently made to it are responsible for the significant lag in recent builds. Most noticeable spot is if you hit the home button if you have the notification drawer down. It becomes extremely laggy without this patch. Scrolling is also less smooth whenever multiple things on the screen are being drawn. This fixes all those issues.

Just flash this in cwm or whatever recovery you choose. Should work on all cm10 builds and cm10 based roms like paranoid android.

http://www.mediafire.com/?dbi25egli253q1b
[Samsung Galaxy Nexus] Christopher3712:
Nice, I'll give it a shot real quick!

***Edit***

There's a noticeable difference after flashing. MOAR BUTTERY!!!
[Samsung Galaxy Nexus] blackhand1001:
Glad to hear. Now I just gotta get this merged into the cm source. Mad at whoever messed up the code in the first place. Gotta set up gerrit and my build environment again and track down the exact change on gerrit that is the issue now.
[Samsung Galaxy Nexus] swyecso:
Thanks I found in another thread that reflashing gapps does the trick but now facelock doesn't come up with show widgets before unlock enabled so I'll try your method

Update: Nope still doesn't come up with show widgets before unlock enabled
[Samsung Galaxy Nexus] bikeboy:
Thought the 9/7 CM10 was a fast build compared to the other s this week, but after applying the fix from Christopher3712 this ROM is blazing & smooth. Thanks all, love this phone again.
[Samsung Galaxy Nexus] caffeineighted:
Is there any way to stop Android from doing that volume protection thing?

I'm trying to listen to Spotify in the car with an auxiliary cable and it keeps stopping songs when they hit loud parts.

I get the function, and appreciate it's usefulness with headphones, but I need to stop it with the aux cable lol

I'm fine turning it off completely.

Gnex | tapatalk2
[Samsung Galaxy Nexus] mark manning:
In the sounds settings uncheck "safe headset volume"
[Samsung Galaxy Nexus] cam30era:
Settings - Sound. Deselect safe headset volume.
[Samsung Galaxy Nexus] gkastrinos:
Yes. Franco's. He's got a JB milestone.

Overclocked to 1536. No issues.
[Samsung Galaxy Nexus] Treken:
I don't get it. I haven't noticed any lag, but rather quite the opposite. Especially with CM's last build.
[Samsung Galaxy Nexus] hotrodwinston:
So if I'm reading all this right the build prop edits being discussed will be merged into cm10.2 as soon as they merge in the new 4.3_r3?
[Samsung Galaxy Nexus] MattyBoy4444:
Nope. It looks like 4.3 r3 will not include it. Does this change help anyone else?
[Samsung Galaxy Nexus] swyecso:
I'm going to freak if the fix was that easy lol. I'll try it out today hopefully if I can get on before I go to class I'll be able to let you know if it works as I have to go underground on the train and always get data drops by the time I get off.
[Samsung Galaxy Nexus] Azrith:
Did not seem to help for me on a different ROM in any noticeable way but I wasn't watching it like a hawk since it happens on my driving commute. I'll have to give it some more time. It still seemed to me that I stayed in "Grayland 3G" for way too long.
[Samsung Galaxy Nexus] NeoandGeo:
Quoting for new page. Is anyone else having native wireless tethering issues with this ROM? I can get it to start, but I can't get anything to connect to it.
[Samsung Galaxy Nexus] rmgibbs1861:
Build Prop

Does it matter where the edit is placed in the Build Prop?

Thanks,

Rick
[Samsung Galaxy Nexus] MattyBoy4444:
Nope
[Samsung Galaxy Nexus] swyecso:
A New Chapter

In case anyone didn't get the news

http://www.cyanogenmod.org/blog/a_new_chapter
[Samsung Galaxy Nexus] ExodusC:
I believe SMS & MMS have been fixed for well over a week now, maybe nearer to two weeks. That's regardless of if you have a working data connection for apps.
[Samsung Galaxy Nexus] jaredsleboeuf:
Yeah, I saw the SMS/MMS changes and I'm pretty sure they were made because that functionality was broken overall. I should have clarified that the issues I was having before were primarily related to sending/receiving SMS/MMS on 3G (usually after switching from 4G to 3G). I was never able to get a pic to send, or receive anything for that matter. Now, it seems to be better though.
[Samsung Galaxy Nexus] MattyBoy4444:
Fyi. Still broken in 9/18 and fix still works.
[Samsung Galaxy Nexus] NeoandGeo:
Was curious if the 10.1.2 stable release would clear up my tethering issues that I was having with the 9/17 nightly build, but the native tethering is still unable to work. I can connect to the created hotspot fine, but no data is transferred, nor do I get a Verizon hotspot subscription link. Is this a problem with the included kernel, or is there an adjustment that I have to make to the framework-res.apk to get native tethering to work?
[Samsung Galaxy Nexus] swyecso:
So you still haven't experienced any data drops?

Update:

Ok so I think I jumped the gun yesterday and made the simple yet critical mistake of not rebooting my phone after I changed the build.prop all seems to be working fine now
[Samsung Galaxy Nexus] hotrodwinston:
Applied fix last night on 9/15 (known broken )and rebooted - no data drop switching to extended network from dead zone - normally drops 90 percent of the time. Will check for pickup when I go back into vzw signal this afternoon - 100 percent drop there normally (shows 3g/4g but gray no connection )
[Samsung Galaxy Nexus] doalittledanse:
I'm kind of curious if the build.prop fix is so simple, why hasn't it been implemented yet?
[Samsung Galaxy Nexus] NeoandGeo:
Welcome to CyanogenMod development. :p It seems there are always really simple fixes that either never make it in, or make it in the build to be later messed up again for whatever reason. There could be a larger problem preventing it from being included, you never know.
[Samsung Galaxy Nexus] hotrodwinston:
It may not always work - testing is key
[Samsung Galaxy Nexus] Droid_JD:
I don't believe it works for me. I'm surprised there aren't more people discussing this.
[Samsung Galaxy Nexus] hotrodwinston:
With build prop edit my 4g connected when coming out of the dead zone without reboot or toggle for the first time since switching to 10.2 ! This was on known not working 9/15 will test tomorrow with 9/19.
[Samsung Galaxy Nexus] JeeperDon:
So what on an unaltered CM is not working at this point?

1) I know the data switch issue is one.

2) Titanium Backup root issue is another, since it's broken in CM's root auth tool, which is Koush's, and he's part of CM, and ZIPping in SuperSU fixes the problem.

Anything else?
[Samsung Galaxy Nexus] Azrith:
Interesting. This was never my problem. It was always dropping from LTE to 3G where the struggle to reconnect data happened.
[Samsung Galaxy Nexus] ExodusC:
I see lots of RIL-related commits in the changelog for the 9/20 nightly, whenever it comes.

Not sure if they're device specific and will solve our issues, but here's to hoping.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Titanium works fine
[Samsung Galaxy Nexus] JeeperDon:
Not actually. Google search it. You have to alter the folder location, which is not what I'm talking about, but odd anyway. But if you do nothing else after a fresh 10.2 install, restoring data to an app produces odd behavior afterwords, at least for every app I've tried. Some get the UID mismatch error, others just break the app. No matter what the problem, if you load the SuperSU zip on top of 10.2 before trying the TiBu restores, there are no errors.

The point is, using SuperSU fixes it, so it appears what is broken is Koush's imbedded Superuser. This has been mentioned a few times in this thread and in others. Like I said, Google search it.
[Samsung Galaxy Nexus] hotrodwinston:
I have that issue but it is unpredictable where what I tested is predictable and this fixed it
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Weird. Only issue I had was having to change the folder location. The UID mismatch has always shown up after a clean flash for me for as long as I can remember, but tapping ignore makes it go away until the next clean flash. I restore all user apps with data, as well as texts, calls, and WiFi access points with no issues.
[Samsung Galaxy Nexus] Badger51:
Battery Drain?

My battery has been taking a hit with the nightlies the last week or so...

My extended battery lasts 5 or 6 hours, even with minimal usage....

I have noticed that the screen shut down doesn't seem to kick in and I have to manually turn it off...

Currently back on 9/15 nightly....but not much change in battery performance.

Anyone else seeing battery problems?

thanks
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Yea, since December 15, 2011.
[Samsung Galaxy Nexus] JeeperDon:
Looks like 9/20 might not be too great. It's 18MB smaller than 9/19. The last time MBs were missing we had boot loops. Anyone want to have a go?
[Samsung Galaxy Nexus] chazzdjr:
Focal has been removed. That's probably the reason.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Focal only takes up 668KB on my phone.
[Samsung Galaxy Nexus] JeeperDon:
Focal.apk is 12.55MB. That leaves 6MB missing, maybe the same 6M as last week?
[Samsung Galaxy Nexus] ironfisted:
Data? Handoff? Better?
[Samsung Galaxy Nexus] johnhimm:
No, 3g/4g handoff still no go
[Samsung Galaxy Nexus] dcp:
Help please!!!!!!!!!

I was messing with my phone last night and now it doesn't work. I was dirty flashing the 09/17 nightly and when I reverted back to the stable 7/11 realease my phone does not want to go pass the bootloader screen. I took the battery out, put it back in, turned on the phone, and all it does is stay on the cyanogenmod logo screen.

How can I fix this issue? Please advise. Thanks in advance!
[Samsung Galaxy Nexus] nalanotae:
Did you restore a backup or did you flash, if you flashed was it a clean or dirty install? Twrp or cwm? Try going into recovery wiping dalvic,cache, factory reset and wipe system. Flash the version you want and make sure you are using the right gapps. If you used 4.3 gapps on the stable build wich is a 4.2.2 build then that could be an issue as well. The 4.2.2 gapps you want is http://goo.im/gapps/gapps-jb-20130813-signed.zip Always clean flash between android versions, if you dirty flashed a nightly( 4.3) on top of a stable (4.2.2) then that is why it would not boot up. When you went to revert back to stable if you dirty flashed stable over nightly then you would run into the same problem. Hope that helps

Sent from my Galaxy Nexus that has been flashed more times than a tourist at Marde Gras