yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] revolt1:
How do you get rid of the flicker using Google maps navigation

I tried the disable hardware
[Verizon Samsung Galaxy S III] mastamoon:
Try the nightly I posted earlier. Resolved my graphical issues.
[Verizon Samsung Galaxy S III] revolt1:
So that one you posted took care of the flicker while using navigation
[Verizon Samsung Galaxy S III] Restola:
Anyone have a link to m2?

Oops nvm its in the cm updater.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
I don't recall having flickers with navigation per se. But there was a bug that was fixed by the commit I cherry picked that fixed graphical glitches so I bet it clears it up.

I was having major issues playing videos and other moving glitches that are gone. Give it a try.
[Verizon Samsung Galaxy S III] fix-this!:
not to sound redundant here but the wifi bugs im having appear to not only effect cm builds but also aokp & the eclipse rom. i guess my router just doesn't like aosp. reflashed m2 and i still cannot get it to work. :p
[Verizon Samsung Galaxy S III] mastamoon:
You probably tried this but have you set your region code in wifi options? I remember that causing issues when they first rolled that setting out.
[Verizon Samsung Galaxy S III] fix-this!:
yup tried that, i odin back to stock, changed my security, changed my ssid, toggled on & off wifi hotpsot. nothing works after a device reboot. i just don't get why this only effects a few and not everyone. my point being all ics roms work fine for me and so does jellywiz which is jb. :crying:
[Verizon Samsung Galaxy S III] mariod505:
Bug Tracker being looked at?

Are the CM developers actually looking at the bug tracker OP mentioned? The number of issues is only really going up - nothing is getting resolved. That either means it isn't being used, or development has slowed (I'm guessing the former).

I was looking to the bugtracker to gauge if I should flash, but looking at the last few comments, I see the current version is probably worse than the one I have.

What are the "M Snapshot" releases on the get.cm website? Is the latest 10/11 one stable/tested?
[Verizon Samsung Galaxy S III] fix-this!:
im not sure whats being looked into. i reported the wifi bug i have two weeks ago. but since cm is multi-device im sure they get overwhelmed with bugs.
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried changing the name of your device? I've heard of some routers not liking the long device names our phones have. Under developer options, host name. I believe that's the name our phones are identified as in a network.

Unless this is what you meant when you said you changed the ssid?
[Verizon Samsung Galaxy S III] fix-this!:
the ssid is under my router settings. no i haven't tried changing the device name, im gonna give aosp a break for awhile until this gets sorted out but thanks.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah give the host name thing a try next time.
[Verizon Samsung Galaxy S III] revolt1:
Yeah I know about that And that's fixed but not the flicker on navigation

Not a deal breaker but annoying
[Verizon Samsung Galaxy S III] jackpot08:
My battery life is god awful. Should I stay on m2 or go to a nightly for better battery
[Verizon Samsung Galaxy S III] pschatz12:
What do you mean by God awful? Hours lasted and screen time?
[Verizon Samsung Galaxy S III] njbuzz:
I've been consistently getting around 5 hours screen on with WiFi and about 2 hours with just network data with almost all the nightlys
[Verizon Samsung Galaxy S III] pschatz12:
I believe that is considered pretty good battery life with ASOP ROM's running JB considering there is not a Verizon JB TW release for the s3...I could be wrong though
[Verizon Samsung Galaxy S III] njbuzz:
Seems about normal. Gets me through the day just fine.
[Verizon Samsung Galaxy S III] Nightwind Hawk:
Does that imply a TW rom would usually get better battery life than ASOP? Or the ASOP rom would get better once we have the material needed from a JB TW ROM?
[Verizon Samsung Galaxy S III] pschatz12:
I have been told that TW ROM's generally get better battery life then AOSP... I have tried both and found that TW has better battery life... Something like Scotts clean rom was getting people damn near 2 days on normal use... I have only been flashing ROM's for a couple months and and AOSP just a couple weeks so I'm not an expert by any means
[Verizon Samsung Galaxy S III] MG386:
usually an AOSP rom with all the current drivers (kernel source) will be better on battery vs. a touchwiz/sence/blur etc. think of it this way, all android phones run AOSP, but most have a manufacturers skin, or user interface UI over the top. so most phones are running both systems integrated together. If it only had to run pure AOSP, there would be battery savings there.

Our problem with CM10 right now, is there is no kernel source available yet, because it hasn't been released. I would suspect that after official JB releases for D2VZW and the kernel source is released for JB, then the CM team should be able to refine and really polish up CM10.

my 2c.
[Verizon Samsung Galaxy S III] fix-this!:
^ for me aosp has always been worse on battery than stock rooted. I agree with you and hope when we get our jb ota it helps some of the bugs.

Off topic but was there ever a cm9 build for us at all?
[Verizon Samsung Galaxy S III] rgrossie:
IIRC CM9 was skipped because the phone was unlocked just as JB was released.
[Verizon Samsung Galaxy S III] dobo84:
OK the visual artifact issues with the camera are starting to irritate me anybody know of a fix
[Verizon Samsung Galaxy S III] TechSavvy2:
Care to elaborate? I've followed every post since the beginning and haven't heard of this issue you speak of with the camera. My camera works perfectly. Its actually probably the only thing I can say is 100% stable on my phone ;)

How does one replicate your problem?
[Verizon Samsung Galaxy S III] imp3r10:
Seems the home button won't unlock the phone now.
[Verizon Samsung Galaxy S III] cgulliver:
I read the commit as being integrated into settings as an option to enable or disable. http://review.cyanogenmod.com/#/c/25160/
[Verizon Samsung Galaxy S III] i5aac:
try a reboot? mine does this once in a while, and a reboot fixes it.

also, regarding battery life: mine is approaching TW life. I was able to stream music for nearly 8 hours straight Friday at work, made it home and still had 42 percent left. This morning, with light use, I just rolled over 24hrs and have 15 percent left....good enough for a daily if you ask me!

FWIW, i am on M2, stock kernel, stock speeds. i have no reboots, no camera, bt, or NFC issues. two thumbs up.
[Verizon Samsung Galaxy S III] cgulliver:
Built an unofficial in case anyone is interested...

https://docs.google.com/open?id=0B3zAomccE23ZVmlzWTNfY1JDbmM

MD5: 0a225b4f27d2db9e0cb3060b85a8e1bd

Tested the basics as well.
[Verizon Samsung Galaxy S III] xsteven77x:
It would actually be nice to have because they would have all the drivers to make it perfect. And seeing as we won't be getting jb for months upon months, it might actually be worth our time ..
[Verizon Samsung Galaxy S III] alee:
Thanks... downloading now!

---------- Post added at 02:07 PM ---------- Previous post was at 01:58 PM ----------

Don't know if I agree with that. The biggest problem with Android is vendors and carriers sticking with previous generation releases. There are still brand new phones out there that are being released with ICS which I think is ridiculous. I think they made the right choice to focus on the future.

You have to hand that piece to Apple... enforced upgrades with no rollback is pretty cruel, but they get to amazing saturation of new releases. If it worked that way on Android, we'd have practically everyone running JB today.
[Verizon Samsung Galaxy S III] fix-this!:
i agree 100%. we need a stable ics aosp build. jb is nice but still has alot of issues. it won't get 100% until we get our ota which looks like won't happen until 2013.
[Verizon Samsung Galaxy S III] landale:
Everyone keeps talking about how the AOSP builds aren't as good as TW because of the fact we don't have JB drivers but didn't the Sprint JB update leak a couple weeks ago? I would have to imagine the hardware is pretty much the same between the two so if that was the case you'd think devs would have already merged in many of those drivers from the leak. I'm hardly an expert but it just doesn't seem like waiting for the OTA release of JB is going to resolve that much for us.

Thankfully I haven't really noticed many issues and coming from a Galaxy Nexus this still blows it away in performance and battery life so any improvement is just a bonus to me.
[Verizon Samsung Galaxy S III] Brian Gove:
Obviously it's not the same. If it was, basic things like the camera would function 100%. There's just enough difference to cause problems.
[Verizon Samsung Galaxy S III] Imatoasta:
I think they need the source though.

Edit: the calculator is getting a major upgrade it looks like. All it needs now is a unit converter and it'll be really good.
[Verizon Samsung Galaxy S III] d1ez3:
Can anyone comment on how the m2 build compares to current nightly. Are they equally stable?
[Verizon Samsung Galaxy S III] cvsolidx17:
Much appreciated. Dirty flashing over my M2 build right now, gonna see if there any hiccups
[Verizon Samsung Galaxy S III] wctaylor79:
Official build is up for today.. Hooray. looks like vzw only one that didn't fail the build
[Verizon Samsung Galaxy S III] cvsolidx17:
Dirty flash over M2 resulted in a DOB. Btw it seems that the DL link to the official 10/21 build is properly working now
[Verizon Samsung Galaxy S III] Imatoasta:
I know there were some kernel (battery drain) and graphical issues starting around 10/12 or 10/13 but I'm pretty sure the stability has stayed the same when compared to m2. I've been on the 10/11 build with lk for awhile (totally solid now that my town has 4g) since the new ones had the previously mentioned bugs but I'm curious about this new build and the new calculator and date/time short cuts.

Edit: I just tried todays build and the graphical glitches when switching between apps are still there.
[Verizon Samsung Galaxy S III] alee:
Worked fine for me. Pulling down official 10/21 now as well.
[Verizon Samsung Galaxy S III] alee:
10/21 official installed clean without issues. Will give it a good test tomorrow, but suspect the same handful of bugs to still be there.
[Verizon Samsung Galaxy S III] revolt1:
Newest version had a slight glitch when in settings then go into developement then press the the back button all the way back

But in invisablek no issues that's weird
[Verizon Samsung Galaxy S III] XooLoo:
Same here...
[Verizon Samsung Galaxy S III] revolt1:
Invisablek works perfect
[Verizon Samsung Galaxy S III] PerCompLLC:
Link please?
[Verizon Samsung Galaxy S III] landale:
So already a 10/22 nightly. I can't seem to find anything listed as changing. Maybe there was some sort of bug with the 10/21 build? I am using djn541's CM10 build from 10/21 with no issues though.
[Verizon Samsung Galaxy S III] DriveEuro:
cm-10-20121022-NIGHTLY-d2vzw.zip

German: Update translation (android_packages_apps_Settings)

That's all.
[Verizon Samsung Galaxy S III] loryndm:
Hey Everyone. I have been having constant radio issues with the stable build 10-20121011 M2 and every nightly since M1. I will have 4G and then it will die until a reboot. I have searched this thread to see if there was a a new radio included in M2 or if there was one i could side load but i have failed to locate the exact post or if any. Can someone tell me if these issues are not just on my device? I keep reading 4 and 5 star reviews of M2 but no one mentions the radio issues so im thinking its just my device and its getting really annoying!

thanks in advance!
[Verizon Samsung Galaxy S III] littleneutrino:
Have you tried Flashing any of the newer radios?

You can find a list of the radios as well as the downloads here

http://rootzwiki.com/topic/34053-officialmodems-verizon-sgs3-sch-i535-odin-or-recovery-flashable/
[Verizon Samsung Galaxy S III] loryndm:
I have not but thank you for the link. I was hoping it would be baked into one of the CM releases. Guess i was just a bit ignorant thinking since no one complained that it was just my device. Mucho Appreciato!
[Verizon Samsung Galaxy S III] alee:
Should definitely not count on radios baked into releases... CM will never include gapps or radios.
[Verizon Samsung Galaxy S III] beaups:
Never say never. Radio is included in the one x builds.
[Verizon Samsung Galaxy S III] alee:
Really? I thought copyrights prohibited bundling.
[Verizon Samsung Galaxy S III] loryndm:
I know about gaaps but was not 100% on the radios. Good to know going forward.
[Verizon Samsung Galaxy S III] grin0048:
Looks like a fix for the loud call volume is coming:

http://review.cyanogenmod.com/#/c/25249/
[Verizon Samsung Galaxy S III] Jay Evans:
WooHOOO Soon I hope :good:
[Verizon Samsung Galaxy S III] danstar:
In regards to the radios, I read in other rom posts, that the radios are all ICS based. Until verizon releases an official JB OTA, there will be issues with data drops and so forth unless one of the various devs come up with a solution.
[Verizon Samsung Galaxy S III] loryndm:
Anything is better than the stock radio that shipped.
[Verizon Samsung Galaxy S III] danstar:
this is true. not currently on CM10, but running eclipse with the he radio and it has been good.
[Verizon Samsung Galaxy S III] PureLife90:
I want to flash this rom I'll be coming from jelly bomb ...are there any special steps to do in order to flash this or can I just flash the latest nightly with gapps if I wipe everything and format system? I've seen a thread somewhere saying I need to go to m2 before I flash a nightly but I can't find it... so can somebody help me with steps? Ty :)
[Verizon Samsung Galaxy S III] Jay Evans:
That is all that's needed. Nothing special just flash like any other ROM. After that, just use the CMUpdate under Phone info to DL and flash any new Nightly.
[Verizon Samsung Galaxy S III] PureLife90:
So I can flash M2coming from a ICS ROM?
[Verizon Samsung Galaxy S III] Jay Evans:
Sure. Wipe data/Factory reset and flash. Don't forget to backup apps.
[Verizon Samsung Galaxy S III] BlackBytes:
Any word on GSM roaming? Does it work again?
[Verizon Samsung Galaxy S III] Marcismo55:
In addition to this i highly recommend wiping system (under mounts and storage) as well as dalvik cache.
[Verizon Samsung Galaxy S III] littleneutrino:
According to http://mobile.cm10log.appspot.com/?device=d2vzw looks like we are going to have a big update tonight/tomorrow.
[Verizon Samsung Galaxy S III] alee:
It's having some problems. Only the last 6 commits are new since yesterday evening. The rest are all captured in nightly 21 and 22.
[Verizon Samsung Galaxy S III] VinBertinelli:
Well its official, cm10 is dead. Started with no nightlies for two days, now the sites down. It was a good run boys. (Lol just kidding but what the hell is going on?)
[Verizon Samsung Galaxy S III] iXNyNe:
Most (if not all) of those changes were already built into 10/21 and 10/22 nightly builds that were already posted.

http://changelog.bbqdroid.org/#d2vzw/cm10/next

BBQ log tends to be more accurate.

The cm updater (settings > about phone > cyanogenmod updates > tap on a build to see its change log) seems to be the most accurate and official documentation of changes from build to build.
[Verizon Samsung Galaxy S III] nohbdyshero:
I was just about to ask if it was down for anyone else......
[Verizon Samsung Galaxy S III] revolt1:
12/12/12 end of the world but early. lol

I'm just using invisablek cm nightlies
[Verizon Samsung Galaxy S III] iofthestorm:
Might have something to do with the amazon Web services outage today. A lot of sites are down because amazon screwed up, basically.
[Verizon Samsung Galaxy S III] zxsix:
Is it possible to create a shortcut on one of the launcher pages to go straight to the CM updater section, to reduce the amount of steps to get there?

Menu > System Settings > About Phone > CyanogenMod updates is 4 steps.
[Verizon Samsung Galaxy S III] wctaylor79:
Github is down due to the amazon outage. CM ties everything into that.. so.. we will see.. apprently amazon had control of a lot of sites i never thought they worked with.. oh well. only time. To much is down to not be fixed sooner than later..
[Verizon Samsung Galaxy S III] trbman:
i'm on 10/21 and just realized that there are no more emojis in the SMS app! This sucks. i came from 10/9 and they were there. Hopefully they come back soon. anyone know a work around to get some emojis back?

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] drdagreenphd:
Should be able to enable them in SMS settings. Then if you hit the menu button and choose insert emoji you will get the entire list of emojiis
[Verizon Samsung Galaxy S III] WhammyDroid:
fingers crossed. Hopefully someone commits this.
[Verizon Samsung Galaxy S III] Ty07allstar:
Hopefully because this is the reason I am not running CM10. Also does anybody know if HDMI out works on the latest nightlies?
[Verizon Samsung Galaxy S III] Brian Gove:
Interesting note, the Mayan's never took into account the leap years... so subtract all the leap year days since their time and we've already passed 12/12/2012. ;)

I don't believe there is one, unless tasker can do it... but then you have to take even more steps to find it on the market and download it... not to mention program it...:eek:
[Verizon Samsung Galaxy S III] jsb5388:
False, the Mayan calendar was so precise they didn't need to account for leap year.
[Verizon Samsung Galaxy S III] dvaderx:
in aokp low video vol recording bug fixed

speakerphone echo and call volume bugs not fixed. i believe this is using the cm fix. so ymmv with the next nightly
[Verizon Samsung Galaxy S III] Jay Evans:
Yes, it is possible if you're using Nova launcher.

---------- Post added at 07:46 PM ---------- Previous post was at 07:35 PM ----------

False. Mayans used three calendars. The "doomsday" calendar had nothing to do with the solar year.

And now back to our regularly scheduled program.
[Verizon Samsung Galaxy S III] cbunting:
Looks like it's a go, they are just waiting for the approval to patch it. I can't wait, just spent my last 15 minutes getting my ear blown out. Perfect for oldsters though.
[Verizon Samsung Galaxy S III] neyenlives:
There's this thing, called a volume button, use it, turn it down. I am not "old" and I really have enjoyed the "plenty loud enough" volume. It really sucks on Touchwiz when at max volume you still have to hold your finger in your other ear to hear with the slightest room noise.
[Verizon Samsung Galaxy S III] grin0048:
I find the volume to be uncomfortably loud even when set to min.
[Verizon Samsung Galaxy S III] WhammyDroid:
What's that sonnnyy?????? Speak louder!
[Verizon Samsung Galaxy S III] zxsix:
I have Nova Launcher Prime.

I looked through nova actions, widgets, shortcuts, and apps.

Don't see the CM updater listed there.

Can you walk me through it in more detail?
[Verizon Samsung Galaxy S III] jackpot08:
Do you guys consider this bad battery life?
[Verizon Samsung Galaxy S III] VinBertinelli:
Very similar to mine, with all the android OS, media server, cell standby taking up the same percentage. If I had to guess you probably had about 2 hours of screen time
[Verizon Samsung Galaxy S III] ert342:
Mine's been pretty much the same, I'm new to this phone and coming from a Dinc but I don't think the battery is supposed to be this bad.
[Verizon Samsung Galaxy S III] VinBertinelli:
Sorry I didn't answer your question, I wouldn't call it good battery life or bad. I consider it right in the middle.
[Verizon Samsung Galaxy S III] Jay Evans:
Shortcuts>Activities > CMUpdater
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Having a problem with the play store. It recognizes my Google account, but when I try to check if I need to update any apps, it don't display any of my apps in the list. Also it's not recognizing my paid apps either.

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] TechSavvy2:
This.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I use a bluetooth so It don't bother me. Can you use a bluetooth or is that out of the question

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] zxsix:
Ah! There it is. Thanks!
[Verizon Samsung Galaxy S III] Jay Evans:
No problemo
[Verizon Samsung Galaxy S III] scriz:
Yeah..I would agree. I switched to CleanROM yesterday and got 28 hours with 15% left. I'd say 13 hours is right in the middle.
[Verizon Samsung Galaxy S III] jackpot08:
Wow that's a very compelling reason to switch to it. Why do you think AOSP battery life is so much worse?
[Verizon Samsung Galaxy S III] softwarestealer0:
I don't think it is. This Is on cm10
[Verizon Samsung Galaxy S III] Aarongauntt:
What kernel/build
[Verizon Samsung Galaxy S III] iofthestorm:
Mind showing the screen time? That's really the only stat that matters IMO. Judging from the percentages I'd say you hardly used your phone those two days lol. Honestly I was a lot happier with my Fascinate when I realized that battery life is way more dependent on how you use the phone rather than the ROM/kernel/voltages. At the end of the day the screen is by far the most intense power consuming component of the device and trying to optimize the ROM or kernel is not going to get you significant gains because they contribute relatively little to overall power consumption (in computer architecture it's called Amdahl's Law, same concept applies here). No matter what you do, at the end of the day you're probably going to get 4-5 hours of wake/screen on time, whether it's over a 10 hr, 24 hr, or 48 hr total period.

All that being said the stock OS seems to usually do better with idle power consumption than AOSP ROMs but meh, if it lasts most of a day it's good enough for me. Keep a charger near you for emergencies or something if it matters that much to you. The other important factor with regards to battery life is wakelocks that might be held by misbehaving apps but that's mostly the fault of bad configuration or something along those lines. You can diagnose those with BetterBatteryStats, I think it costs like a buck or something but it's completely worth it. You can also get the same information in a less pretty format by using adb but seriously, you have a $600 phone with a minimum $70 monthly plan, what's $1 for a well written app to visualize that data?
[Verizon Samsung Galaxy S III] TechSavvy2:
While I would usually agree with you completely......I'd say you've never owned a Thunderbolt, lol. Back in the day (a year ago) changing to cm7 and adding a kernel literally quadrupled the battery life, haha. But that's an extreme case.

On topic, my battery life is completely fine. I use my phone as much as I want and have screen brightness up all the way and still have 50% left at the end of the day. "Why not give more details on how to attain this?" one might say, and the response would be that it doesn't matter unless you do EXACTLY the same things as I do in EXACTLY the same locations. Otherwise, its a moot point. :)

---------- Post added at 11:59 PM ---------- Previous post was at 11:54 PM ----------

Lol, are you asking me if I can just use bluetooth all the time to compensate call volume? That seems a silly question.
[Verizon Samsung Galaxy S III] Jaegermeiste:
Seems average to me. Like others said above, it depends on your usage. ROM-wise, until Jelly Bean 4.2 we aren't likely to see any significant improvement in battery life in the nightlies.
[Verizon Samsung Galaxy S III] neyenlives:
not at all, not for someone who actually uses their device. I look for 10-12 hours out of mine, then it's time to swap batteries. I never go without.
[Verizon Samsung Galaxy S III] alee:
10-23 up... working ok. Volume fix was not merged last night so don't expect it to be there.
[Verizon Samsung Galaxy S III] codyvance:
Try calibrating gyro.. Never had issue but usually that helps
[Verizon Samsung Galaxy S III] tmar23:
Latest nightly working great so far. Signal seems better/stronger. No call issues yet, but I only had one call...

Camera seems to be working well, too.