yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jwa0042:
I'm getting pretty major lag and a homescreen re-draw the majority of the times i return to the homescreen from an app. Also, the app drawer has to reload for about 10 seconds if i try to open that after the re-draw

I'm on the M3 release, but it was doing the same thing on the earlier April nightly i was on (can't remember which exactly). Any ideas what's going on?
[Samsung Galaxy Nexus] tiny4579:
Known android 4.2.2 issue.
[Samsung Galaxy Nexus] klobkelosh:
I had decent luck adding "ro.HOME_APP_ADJ=1" to the end of /system/build.prop. I know I'm gonna get flamed here...people claim it doesn't work but I found it to nearly eliminate launcher redraws. CM seems to have fixed it after the m3 release.
[Samsung Galaxy Nexus] Nick_Gl:
I had to reinstall my gapps on the latest nightly anyone else have that problem? They just disappeared on me.
[Samsung Galaxy Nexus] jwa0042:
I remember seeing a setting at one point in the past called "lock home in memory" or something. I looked for it and couldnt find it, but i enabled ZRAM at 18% (i think it was off by default) and i checked the "purge assets" box and rebooted. Homescreen re-draws seem to be fixed, but there's still some lag with he animation. Overall a definite improvement though, as far as i can tell.
[Samsung Galaxy Nexus] thechainrule:
X2

also cant get gTalk back for some reason.
[Samsung Galaxy Nexus] mikeblock:
Also, in netflix, video stops, not the phone or sound it just sticks on one still frame but everything else works normally. Also lost gapps this morning after a crash and reboot involving netflix. None if this until nightly 21.
[Samsung Galaxy Nexus] mouf32:
Everything work well with the 4.18 dirty flash...
[Samsung Galaxy Nexus] MordeKyle:
On the 4/24 Nighty. No problems to report. This rom runs great.
[Samsung Galaxy Nexus] friguy3:
So after looking, seems as though the GPS issue is a 4.2.2 issue? Anyone actually found a good way to get a lock. Mine takes for ever and then is sometimes off. My friend on his S3 went back to stock and his GPS now locks fast again.
[Samsung Galaxy Nexus] omniatic:
No problem here...first lock on boot takes about 20 seconds. After that, most are 5-8 seconds. Same on all the nightlies that I've seen.
[Samsung Galaxy Nexus] klobkelosh:
No problem here. I had first lock in 6 seconds
[Samsung Galaxy Nexus] johnhimm:
Mine has always locked in under 10 secs. Maybe its where you are located.
[Samsung Galaxy Nexus] friguy3:
Ugh, thanks. No Im in NJ and used to get great quick locks. Even after I get a lock. If I turn off GPS, and then turn it back on, it doesnt get the super quick lock.
[Samsung Galaxy Nexus] friguy3:
So just if anyone else is having issueswith GPS...i found this...

http://xdaforums.com/showthread.php?t=1789543

flashed the file and ran the apk and whow! uber fast locks now :)
[Samsung Galaxy Nexus] Wishka233:
I have had several people tell me that after I send a text message, a second message is sent that says Command not supported followed by my current battery level (Ex. "Command not supported *Battery remaining: 84%")

Any ideas what this could be? Running 4/8 nightly using the stock messenger.
[Samsung Galaxy Nexus] klobkelosh:
Fyi, that is a gpsconf edit. If you are into gpsconf tweaks, you should read this: http://rootzwiki.com/index.php?/topic/28989-The-End-All-Be-All-Guide-to-Your-GPS#entry1086327.

Take away lesson, gpsconf tweaks can help if the person who tweaks knows what they are doing. Frankly, I've found most tweaks to be suspect and a few that really f things up. Stock, on the other hand, has always worked for me.
[Samsung Galaxy Nexus] wastedlife:
The syntax for that gpsconf file is very wrong. I am genuinely surprised that it even works:

NTP_SERVER=server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org
XTRA_SERVER_1=0.north-america.pool.ntp.org
XTRA_SERVER_2=1.north-america.pool.ntp.org
XTRA_SERVER_3=2.north-america.pool.ntp.org
XTRA_SERVER_4=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_5=http://xtra2.gpsonextra.net/xtra.bin
ACCURACY_THRES=80
SUPL_PORT=7276
SUPL_HOST=supl.google.com

Tweaks By Mitch Edwards
Mitch0115

Agreed that messing with gpsconf can mess things up if you aren't careful, but the stock for CM 10.1 is missing any NTP server data, which may cause issues if your clock is not 100% in sync (tower clocks can be off sometimes):

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276

With stock I used to have slow GPS lock, but it is better after making a slightly modified version with the NTP servers and intermediate position settings added. This seems to help me out:

NTP_SERVER=0.us.pool.ntp.org
NTP_SERVER=1.us.pool.ntp.org
NTP_SERVER=2.us.pool.ntp.org
NTP_SERVER=3.us.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=1
ACCURACY_THRES=5000
SUPL_PORT=7276
SUPL_HOST=supl.google.com

I have attached a version that can be flashed in TWRP or CWM.
[Samsung Galaxy Nexus] JPBeard21:
You may have an app running in the background that is listening/receiving SMS commands. Some antivirus/location/tracking apps do this as well as "Spyware" apps. You may want a clean install and pay attention to how any of those sort of apps are configured. Those are the only things I can think of.
[Samsung Galaxy Nexus] Wishka233:
Thanks. I have uninstalled SeekDroid for now and will see if the problem pops up again.
[Samsung Galaxy Nexus] Ammontj:
I am racking my brain, trying to figure out why I can't send MMS on the past several nightlies. I noticed that something had been changed on the most recent nightly, but I still can't send MMS.

Any ideas. I appreciate any help. (I use the stock messaging app)

Swyped on my CM10.1 Verizon GNex via Tapatalk 2
[Samsung Galaxy Nexus] flytechguy:
Did you try a davlik and standard cache wipe?
[Samsung Galaxy Nexus] underwaterjr:
For those of you having trouble I have to assume you've been "dirty" flashing for a few nightlys now. Almost, but not all of the bugs reported on here I have never experienced. Everybody goes about wiping and updating a little bit different. I have been compiling my own builds for about six months now but they are stock cm so no different than the nightly builds, and I always do the same thing when updating to a fresh build. My version of a dirty flash is reboot to recovery and format cache, dalvik, and system. Leave data alone so you don't have to set everything back up again. While doing it this way I've never had problems with gps, sms, or most of the other things listed on here. If your really having problems then I would say a clean flash is in order. By that I mean factory reset along with formatting those other ares. Then let the market restore your apps. I will use titanium back up to load any apps not done by the market and only restore data to a handful of market apps, the rest get a fresh start. A little more work maybe but I'm a lot happier with a bug free device.
[Samsung Galaxy Nexus] friguy3:
Thanks! Seems to be working great. It was so bad before it wasnt even usable. Id be driving down the highway and it would have me driving of to the side of the highway. I flashed the other zip and its all back. If I have more issues Ill flash your zip. Thanks!
[Samsung Galaxy Nexus] marcusva79:
This is what I use to get GPS working good.

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

Works really great on any ROM and carrier.
[Samsung Galaxy Nexus] klobkelosh:
Hey I recognize that zip :)

Those files were pulled from the official vzw ota. The same ones should be in the cm repository, but you never know. The conf file is optimized for vzw.
[Samsung Galaxy Nexus] marcusva79:
Oh klobe. I am just trying to help out. Some just told me to use this so I thought I'd post it again haha.
[Samsung Galaxy Nexus] klobkelosh:
All cool. Like I said, you never know. For a long time cm had the wrong ones in there. For all I know they still do. Flashing official binaries from the ota never hurts. Peace.
[Samsung Galaxy Nexus] underwaterjr:
Ever since the implementation of the hex code picker for the led light I can't set any custom values for individual apps like messaging or gmail. Anybody else?

Edit: never mind I recompiled and it works fine.
[Samsung Galaxy Nexus] AuroEdge:
I'm using the latest nightly and am unable to select led colors for apps like you had said
[Samsung Galaxy Nexus] underwaterjr:
Huh, maybe I wasn't crazy then. I just resynced earlier tonight and rebuilt and it works fine now. I'm sure it will be fixed in the next nightly.
[Samsung Galaxy Nexus] automaddux:
curious, I know I can upgrade from a previous build without a full wipe but what if I was downgrading?
[Samsung Galaxy Nexus] nowetdio:
Should be fine. Just wipe system/cache/dalvik.
[Samsung Galaxy Nexus] automaddux:
Cool. I've always wondered should you wipe before or after? Or both? I guess if you are using the bathroom concept then you should wipe after but I never really knew in regards to wiping things off your phone...
[Samsung Galaxy Nexus] TRU3L3GEND:
Noticed my phone started dragging lately so did a full wipe after updating via cm updater for a few months. Its now just as fast as it was when I got it however its turned off three times now and required a battery pull. Wondering if its just the nightly I'm on, anyone with problems on the 4/27 build? The battery was plenty full, it happened once playing Real Racing after a few min and the rest it was sleeping. Any ideas?
[Samsung Galaxy Nexus] TEK112:
Sounds like a voltage issue. If you are uncomfortable upping the voltage of the low end clock speed you can up the frequency of the minimum clock by one notch. Alternatively you can flash a different kernel.
[Samsung Galaxy Nexus] jim_stem:
Anyone have any ideas why there are two nightlys of different sizes were posted to the getcm for today (4/30)?

Also, why has the lock screen clock widget gone small again? I kinda liked the huge clock.
[Samsung Galaxy Nexus] norm12:
I'm on m3 and have the smaller widget as well----to expand it makes the lockscreen sliders disappear and I don't care for it. I'm sure there's a fix or a toggle I'm missing though, just play around
[Samsung Galaxy Nexus] johnhimm:
the large lock screen was an error
[Samsung Galaxy Nexus] PARick:
The OP mentions a Google add on, but I do not see a download link or mention elsewhere. It seems like a way to restore without TBU? Can someone point me in the direction of the download? Thanks!
[Samsung Galaxy Nexus] TRU3L3GEND:
Thanks I'll try that out and see what happens. The problem was on the stock kernel, guess ill go back to franco's

The Google add on is on the OP, its called GAPPS which is at the very bottom. I'm not quite sure what else your asking, the gapps are just the google apks that arent included in the build because of licensing. I'm not sure whats included as of today since many have just been moved to market downloads.
[Samsung Galaxy Nexus] jmk4412:
Could someone post the stock gallery apk ,lost mine and I wanted to keep both the cm and stock.thank you in advance.
[Samsung Galaxy Nexus] PARick:
Thanks for your reply. I was referring to this:

INSTRUCTIONS:

- First time flashing CM 10 to your Galaxy Nexus (or coming from another ROM)?

1. Do a Nandroid backup!

2. FULL WIPE (Data, cache, and dalvik cache)

3. Install the ROM

4. Optionally install the Google Addon

I guess if it is GAPPS, why not just call them GAPPS:D

Thanks!
[Samsung Galaxy Nexus] mentaculus:
I've been having major battery drain issues with the last several nightlies...when I check the battery stats, I see that "Android OS" is keeping my phone awake for hours at a time. Seems like an issue with the kernel?
[Samsung Galaxy Nexus] rcdeck:
I second this, although strangely I have been installing lean kernel
[Samsung Galaxy Nexus] TRU3L3GEND:
Went to open data usage this morning and noticed the graph disappeared and haven't been able to get it to come back. Anyone else have this happen? I even flashed an update via cm updater and its the same.
[Samsung Galaxy Nexus] gpzbc:
Weird. Mine is fine on the 5/2 nightly.
[Samsung Galaxy Nexus] Lunarskye23:
These recent nightlies seem to get worse. My battery also sucks even with WiFi. Bluetooth is temperamental. Yesterday I was having issues with MMS texts. I'd have to keep sending them. Some message threads had to be deleted just to avoid it crashing over and over. My GPS doesn't lock at all today. The only positive thing I can say is the home screen seems to be more snappy and I don't get crashes, but at what cost. I'm not sure why things have decreased but I hope it can be fixed soon. Thanks.
[Samsung Galaxy Nexus] JBAeroEngineer:
is there a CM GPS thread somewhere? I haven't had working GPS in over a month. It never acquires in maps/nav/etc
[Samsung Galaxy Nexus] johnhimm:
on toro? I think you may have a bad hardware.
[Samsung Galaxy Nexus] omniatic:
Try GPS Status from the market. It might help fix it up for you.

Three weeks of nightly builds, now on Tiny's, and never took more than 20 seconds to lock, even from cold start. Most times, it locks in 5 seconds or less.
[Samsung Galaxy Nexus] klobkelosh:
There are several threads on the q&a section, but what's the problems specifically? Have you checked to ensure all good settings are turned on? Check Google app location permissions as well as all app permissions. Is the unit still activated with Verizon? If not, you would not be receiving agps data and acquisition of a position would take 15 or so minutes on a cold start. Try gps status, clear agps data and download new agps data. Then go outside and try to acquire. Are you flashing any gpsconf tweaks or using faster gps?
[Samsung Galaxy Nexus] wastedlife:
On page 284 I posted the GPS.CONF settings that work for me and should work anywhere in the US. I also posted a flashable .zip file in case you don't want to mess around with conf files.
[Samsung Galaxy Nexus] klobkelosh:
You shouldn't need any modifications to gpsconf for gps to function correctly.
[Samsung Galaxy Nexus] landstander:
Looks like the toro build hasn't completed yet, but CM 10.1.0-RC1 has been announced. :)
[Samsung Galaxy Nexus] johnhimm:
Looks like it will hit tonight as long as the build server keeps chugging.
[Samsung Galaxy Nexus] JBAeroEngineer:
let me try gps status app.

permissions/activation are fine. even did a fresh install.
[Samsung Galaxy Nexus] JBAeroEngineer:
Still no luck, see attached.
[Samsung Galaxy Nexus] allcity187:
Rc1 is ready for Toro, http://get.cm/?type=RC
[Samsung Galaxy Nexus] norm12:
Downloaded it, just wondering if anyone else has flashed it yet.

Sent by Logo the Turtle
[Samsung Galaxy Nexus] jmk4412:
Flashed rc1 an hour ago, so far so good. No issues here.GPS locks fast no data issues :D
[Samsung Galaxy Nexus] klobkelosh:
Ok, so I see your gps is in fact receiving some signal (see the strength bars for individual satellites). Are you indoors? If so, go outside. Also, there's no age on your agps data suggesting you don't have any. Have you tried downloading agps data in the gps status app tools menu?
[Samsung Galaxy Nexus] Lunarskye23:
The GPS on this ROM has been terrible for awhile. I don't give Google apps permission to use my location because when I go to areas that only have 3g coverage it crushes my battery and that's even having the seido 3800. I watch other people cold start GPS and they are up and running in no time. Reasonable time is a minute or two. I remember when my phone would lock right away in Google maps...now it takes forever. GPS status app works OK...but I shouldn't have to use 3rd party apps in a custom ROM.
[Samsung Galaxy Nexus] klobkelosh:
I disagree. Gps has been prefect on cm10.1 since the cm team incorporated the correct drivers a month ago or so. Fast locks. Always. Even after a new ROM flash. The difference, I allow all location permissions. I go in and out of 4g/3g all the time and gps had no effect on my battery. But I agree you should not ever have to use gps status just to get a location lock. I never use that app unless I am troubleshooting.
[Samsung Galaxy Nexus] b4u2:
What Kernel is the best for enabling fast charge?
[Samsung Galaxy Nexus] wtr_dhd:
Try franco r376.
[Samsung Galaxy Nexus] b4u2:
Do I have to buy his app in order to make changes?
[Samsung Galaxy Nexus] wtr_dhd:
You can always use something like Trickster Mod, it's a free app.
[Samsung Galaxy Nexus] b4u2:
I might have to. I just tried latest LeanKernel and it's not really working. Keeps resetting phone.
[Samsung Galaxy Nexus] jlvlawrence:
AK kernel has been great for my phone.
[Samsung Galaxy Nexus] JonBsbB:
Ok so i just used the CM updater to go from CM10 to CM10.1 RC1 and now i can't get my google account connected. and also there is no camera. Any ideas
[Samsung Galaxy Nexus] rcdeck:
The latest lean kernel works well for me. no reboots
[Samsung Galaxy Nexus] johnhimm:
Probably a good idea to do a clean install on RC1. I did and all is working well.
[Samsung Galaxy Nexus] Nick_Gl:
Anyone know where the slider shortcut icons are stored? I want to edit the color of them to match cm color. Also what hex code does cm use for the blue?
[Samsung Galaxy Nexus] wolfman87:
Are the new builds (eg. cm-10.1-20130509) based on RC1, or or they continued from older versions?
[Samsung Galaxy Nexus] b4u2:
I downloaded Franko and the trickster app. Now I just need to understand all these settings to get peak performance from phone and battery.

I have no clue what most of these settings due and I don't have time to study this so guess I'm just going back to CM kernel.
[Samsung Galaxy Nexus] JonBsbB:
Worked great. Thanks
[Samsung Galaxy Nexus] wolfman87:
Might need to reinstall gapps?
[Samsung Galaxy Nexus] JonBsbB:
Yea had to do that as well. Thnaks all for help
[Samsung Galaxy Nexus] nitsua98:
OK idk what CyanogenMod did with the rc1 but it's a lot faster than the other builds.
[Samsung Galaxy Nexus] tiny4579:
Nightlies are nightlies. They run nightly. The rc1 is just a progress point in the development process.
[Samsung Galaxy Nexus] johnhimm:
and they got the gamma right
[Samsung Galaxy Nexus] ExodusC:
Whew, I'm getting absolutely terrible battery life on RC1. Is that just me, or is there a known issue here?
[Samsung Galaxy Nexus] Sharpbarb:
Just updated RC1...

I use swiftkey. For some reason, my phone keeps reverting to the stock keyboard. I select Swiftkey as the keyboard of choice, and it changes to Swiftkey, but after the keyboard pops in and out a few times, the stock keyboard comes back. Very weird.
[Samsung Galaxy Nexus] johnhimm:
Must be you, on toro here and getting same battery life as stock for the most part.
[Samsung Galaxy Nexus] ExodusC:
This battery might just be shot, I'm losing percentage in 2% increments in incredibly short periods of time just idling.

I might just spend $25 and get the extended battery.
[Samsung Galaxy Nexus] Meticode:
No, but I do recommend buying Franco.Kernel Updater. It's one of the few kernel apps worth buying.
[Samsung Galaxy Nexus] stbxxl:
+1
[Samsung Galaxy Nexus] tshelby73:
Working great so far came from other ROM and this seems very fast. Even 3g seems faster but may just be Verizon today.
[Samsung Galaxy Nexus] JBAeroEngineer:
i was outside. i left it open for 20 minutes and it acquired. will check it again today for speed. thanks
[Samsung Galaxy Nexus] klobkelosh:
20 minutes is about what it would take to acquire cold start ephemeris data without agps. Do you have a problem with your data connection?
[Samsung Galaxy Nexus] Lunarskye23:
I agree. My brightness is on auto and all I've done this morning is look at a few pages online. My 4g is moderate but even still. 10 percent in 13 minutes. Not even doing stuff the whole time. Its almost a percent a minute and I have the seido 3800 so it shouldn't do that. Another 2 percent drained as I'm posting this. I'm on Francos kernel. What's going on?
[Samsung Galaxy Nexus] Lunarskye23:
This is what I'm running and my signal which sometimes does greatly effect my battery.
[Samsung Galaxy Nexus] dx1881:
RC2 is out:)
[Samsung Galaxy Nexus] Sharpbarb:
I've been using RC2 for 5 minutes now and I haven't noticed a huge improvement in battery life.

What gives? Why hasn't this incremental update to software been able to triple my battery life? Is there something wrong with my phone?

/s
[Samsung Galaxy Nexus] tshelby73:
Lol
[Samsung Galaxy Nexus] ashclepdia:
I bet you forgot to reset battery stats...

:D :D :D
[Samsung Galaxy Nexus] nitsua98:
So... CM Updater decided it would be funny to delete my Download folder -.-
[Samsung Galaxy Nexus] klobkelosh:
Yeah, I think something is wrong with cm updater in rc2. Keep getting a java toast spam, logcat showed it was cm updater, when I tried to launch the updater from settings it crashed. Odd.
[Samsung Galaxy Nexus] laureanop:
Does anybody happen to know why rc1 and rc2 were released so close to each other ? I've run both and I can't see any differences whatsoever

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Ammontj:
Curious about the same thing

Swyped from my CM10.1/Franco Verizon GNex, using TapaTalk 2
[Samsung Galaxy Nexus] johnhimm:
Because Google I/o is here with a new Android version. 10.1 stable is days away
[Samsung Galaxy Nexus] AuroEdge:
The RCs now are supposed to be final bug fixes. So, not every device will get the same number of RC releases
[Samsung Galaxy Nexus] laureanop:
Makes sense. We're talking 4.3 right ?

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Meticode:
I'll give a review on battery life tomorrow (at least 3G the whole day). I tend not to run 4G because it drains the battery faster and when I'm web browsing 3G is personally sufficient for me.

I can tell you this. On a wifi network the battery life is absolutely awesome on RC2+franco.kernal running the BeastlyBattery Power Mode. I was at home all day on the wifi. Unplugged it at 9AM, at 12AM (15 hours later) with moderate to heavy use I was still at 55%. While the screen is a major culprit of battery use, the radios for 3G and 4G seem to take up 2x to 3x the batter the screen does. I get poor reception in my area (1 to 2 bars usually).
[Samsung Galaxy Nexus] JonBsbB:
anyone else having an issue with the time on battery info not being correct? I been unplugged for bout 14 hours and it says I been in plugged 10 hrs 37min. after I did a reboot it went to 9hrs 13min. if it makes a difference I am on rc2 with Tony kernel 4.0.1 old wifi.

UPDATE: Ok so i wiped battery stats and shut down phone and fully charged over night. and all seems normal now.
[Samsung Galaxy Nexus] Lunarskye23:
Battery life seems to of picked up on the May 10th nightly. The previous build from the 2nd was terrible even with WiFi....so hopefully it stays solid from here on out. Based on DC area.
[Samsung Galaxy Nexus] JonBsbB:
RC2 + Tiny Kernel seems to be great "for me" on battery life. im a light to moderate user. and a wifi junky.
[Samsung Galaxy Nexus] b4u2:
I'm on 5/10/13 and when I installed it from CM updater it changed my kernel (didn't realize till later that it did this) However if I run anything other than performance mode (Trickster) the phone lags horribly. Any suggestions?

Battery life seems normal for me btw. I am an extremely heavy user (kingdoms at war junkie). I have a Qcell 3500 extended battery. On 3g I got roughly 4 hours 30 mins before it shut off. Seems ok but keeps me tied to a charger a lot.
[Samsung Galaxy Nexus] n2imagination:
Just curious guys but what are you using to wipe battery stats? I used to use recovery but have switched to twrp and I have never found an option to wipe battery stats in there. I used battery calibration from the store for a while but started feeling lately that that one isnt working as well as a recovery based option.
[Samsung Galaxy Nexus] ExodusC:
I'm quite certain those who recommended it were joking.

Google, CyanogenMod and others have all acknowledged that wiping battery stats does absolutely nothing in terms of your battery and is on no way linked to your battery's charge memory or anything of the sort.
[Samsung Galaxy Nexus] JonBsbB:
I use rom tool box to wipe stats.