yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] UberSuber:
So far on my phone it is at least as stable as RC1, which isn't saying much. RC1 had massive issues on my phone with powering off while I use Google Navigation. The "stable" release has done the same, although maybe not as much. Battery is roughly equal, meaning pretty good, but not awesome. Based on the change log, looks like there is not much difference between them. Actually I'm holding out for the 4.3 OTA to start up again, and then I'll probably flash jbeans again when the updated version drops. I loved 10.1.3. That was about as well as my phone has ever run, but it looks like the only stable way to 4.3 may be a Touchwiz ROM. I did a clean install of 10.2, but didn't flash back to stock first. I may try the ODIN back to stock first, I guess, since some say that helps some issues. Meh. Everyone else having big GPS problems and power resets (especially using GPS) on 10.2, or is it just me?
[Verizon Samsung Galaxy S III] rockingondrums:
The Odin wipe is exactly what I see quoted as a fix for GPS woes (get your lock in TW, then flash CM). I had GPS woes early on on my S3 but after several days/reboots they eventually went away. And now I have an N5 so *shrug*
[Verizon Samsung Galaxy S III] Jackdog89:
I have the same problem. Try turning the volume up during the call, then back down. This seems to work for me.
[Verizon Samsung Galaxy S III] Harb67:
Anyone know how to fix issues with google apps after flashing the newest ROM and gapps? I was on 10.1.3-rc2 and an older gapps for a while with zero issues, then I flashed 10.2.0 and the 8/20/13 gapps and now Hangouts, YouTube, Voice, and Play Music force close as soon as the phone boots and upon any subsequent attempts to open them, and Play Store won't download any updates, though it does see that various apps do have updates available. I've tried clearing cache, dalvik cache, and fixing permissions as well as clearing app data for Hangouts, Voice, Music, and Store but that didn't seem to help anything.

Any ideas?
[Verizon Samsung Galaxy S III] Hellven:
Maybe try uninstalling app updates, then re-download. That worked for me when Google search went crazy.
[Verizon Samsung Galaxy S III] titanshadow:
I had that happen and had a really hard time getting it to work. ONe device I had to uninstall updates from Play Store, Framework, and Play Services then reboot the phone and install. The other device I actually had to start over and redo everything. It was very frustrating.
[Verizon Samsung Galaxy S III] Aaron1017:
Anyone have working bluetooth calls/audio with their cars in 10.2 stable?
[Verizon Samsung Galaxy S III] aagvain:
working fine on ford sync
[Verizon Samsung Galaxy S III] fonixmunkee:
Working fine for Ford Sync here as well. I'm loving the updated Bluetooth stack in 4.3...music & calls work great with Ford Sync.
[Verizon Samsung Galaxy S III] tehloxely:
From reading the comments on the stable 10.2, I think I will wait for a better stable/nightly 10.2.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
10.2 works just fine here (i.e., stable).
[Verizon Samsung Galaxy S III] lostboy1952:
10.2 Bluetooth

Working with my Verizon SIII and my Accord. Both music and Phone.
[Verizon Samsung Galaxy S III] nickhex89:
Can anyone help with this issue...yes using stock kernel...having a major issue with all cm 10.2 builds this never happened before to me came out the blue. Shows my phone # as 000-000-5857 can't send MMS or SMS mobile network keeps going in and out constantly tried clean wiping and flashing different build(s) still does the same with all of them.
[Verizon Samsung Galaxy S III] diesburg:
Are you by chance using an s3 that's flashed from one carrier to another? And did you try a *228 activation to see if your programming gets reloaded ?

Since your phone lost the programming no matter how many roms you flash it won't come back unless it can grab it from the sim. Have to *228 or manually program some/all info with dfs or similar software.
[Verizon Samsung Galaxy S III] nickhex89:
Nope it is a d2vzw s3 and no I didn't... totally forgot bout the *228 haven't used that in years lol
[Verizon Samsung Galaxy S III] diesburg:
Ok. Since its all good vzw s3 on vzw, *228 should work fine. If not let me know.
[Verizon Samsung Galaxy S III] nickhex89:
And that's the thing it is programmed fine on any other ROM just not the cm 10.2 anymore
[Verizon Samsung Galaxy S III] diesburg:
Well just flashing a new eom SHOULDNT wipe your programming ever. Another setting to check out is Settings--> wireless and networks--> more. And somewhere in there is a serring where it says nv only and the other option is sim something. If its on nv only switch it to the other one. Reboot and see what that does.

Edit: the serring I mentioned is in mobile networks I think. I'm on stock so can't check for sure.
[Verizon Samsung Galaxy S III] nickhex89:
OK gotcha will re flash to cm10.2. Right now went back to stock rooted so will do that and then check back and let ya know
[Verizon Samsung Galaxy S III] diesburg:
Before u do all that did u try *228 or *228+ or *22800 activation on stock?
[Verizon Samsung Galaxy S III] nickhex89:
Yeah everything is fine on the stock no issues from the get go. Every single thing worked without flaw. Didn't even have to program. Number was normal as well as MMS n SMS and network connectivity.
[Verizon Samsung Galaxy S III] diesburg:
Ok now that you say that I'm pretty certain its that setting in cm I mentioned.
[Verizon Samsung Galaxy S III] diesburg:
From what information I gathered I'm glad I tried to help you. I learned simething that will probably help me later. My understanding is the vzw s3 takes all programmng for voice/text/2g/3g/lte from the sim card not the nv. But the sprint s3 only needs the embedded sim (yea sprint sucks that bad, I said it, embedded...lmao) for the lte but voice/text/2g/3g programming is from the nv not the sim. Which means I was probably wrong in helping you at first. I'm not sure if *228 works for programming coming from your sim and not the nv on at least newer lte phones. And if I'm wrong I would love for someone to correct me so I do understand this correctly and don't misinform everyone who reads this post...lol
[Verizon Samsung Galaxy S III] headcheese:
Official Cm11 nightlies! Sweet!
[Verizon Samsung Galaxy S III] situman:
Does the GPS and the regular camera work?
[Verizon Samsung Galaxy S III] airmaxx23:
They both work fine.
[Verizon Samsung Galaxy S III] annoyingduck:
My torch is working fine, both using a home button long press from the lockscreen and from the quick tile.

I can also confirm several lockscreen target issues. Apps not sticking, icons not able to be changed.

What's driving me nuts is the lte symbol that replaced the 4g symbol is always grey....:p
[Verizon Samsung Galaxy S III] sanjsrik:
Is there a fix for contacts not syncing? I had this issue with 4.2.x where if I created a contact on my device and said to sync with my google account, I would get a contact sync error message. I thought deleting and recreating my google account on my device would correct this until I created another contact on my device and said to sync with my google account and another sync error.
[Verizon Samsung Galaxy S III] pwrmedia:
Are you sure it's the contacts that aren't syncing, or the "people details?" giving you the error?

I've had no issue syncing any saved contacts, but the latter hasn't synced in both 4.2.x and 4.3.
[Verizon Samsung Galaxy S III] Chris Hansen:
I've had no problems with both contacts and people details, both synced this morning. I don't think I ever have for 4.1+.

I installed 8/15 this morning (dirty flash), and I can confirm that torch works now on the stock kernel.

An oddity was that it uninstalled Gmail. Seems like that was the only GApp that was uninstalled. Reinstalled just fine though. :good:
[Verizon Samsung Galaxy S III] Restola:
Removing Google account and adding it back fix the contact sync issue.
[Verizon Samsung Galaxy S III] ericsdeadinside:
Any progress on the touch sounds screwing up audio yet?
[Verizon Samsung Galaxy S III] annoyingduck:
What's the difference between contacts and people details?
[Verizon Samsung Galaxy S III] sanjsrik:
It's Contacts that is not syncing. I don't know about people. I just know, the minute I create a contact on my device and say to sync it to google, it gives me a sync error with the message, "Sync is currently experiencing problems. It will be back shortly."

Any help would be most appreciated. I haven't gotten contacts to sync for a while now.
[Verizon Samsung Galaxy S III] airmaxx23:
I'm able to change apps for the lock screen and change the icons as long as they are from the gallery and not system icons.
[Verizon Samsung Galaxy S III] annoyingduck:
I tried system icons...

Some apps are sticking, some aren't for me
[Verizon Samsung Galaxy S III] joshua5683:
Torch is now working in the 8/15 nightly :)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] dewhashish:
on 8/15 nighly, still cant find the option to shut off the light for the capacitive buttons, there was an advanced menu in CM10/CM10.1 for this
[Verizon Samsung Galaxy S III] WhammyDroid:
CM Devs,

This issue is still prevalent on the 8/15 nightly with a stock kernel.

https://jira.cyanogenmod.org/browse/CYAN-1355

I will update JIRA when I get home tonight.

Jeff
[Verizon Samsung Galaxy S III] ericsdeadinside:
Finally, I'm not the only one with this issue.
[Verizon Samsung Galaxy S III] thelangosta:
On the lockscreen? You have to touch the little floppy disk symbol in the upper right corner after you have them all set up and that will save them.
[Verizon Samsung Galaxy S III] :
I'm not having any issues with the slider icons including system apps.
[Verizon Samsung Galaxy S III] annoyingduck:
The issue I'm having is some apps aren't working correctly when launched from the lockscreen. ExDialer is an example.. Get errors and icon is gone on a reboot.
[Verizon Samsung Galaxy S III] droidfreak02:
I had the same problem too. Were when I flash cm or any 4.3 ROM I would lose signal and can't send MMS but I could always receive them. The only ROM that works is the eclipse rom. But I'm having problems with everything forcing close on me. I'm just going to go back to 4.2 till someone find a solution
[Verizon Samsung Galaxy S III] buschbarber:
I just updated with Nightly from 12/08. I lost several installed apps including ROM Manager, eCid, Rainy Days, but the biggest problem is that I receive a "No Connection" when I launch Play store. Gmail works fine. I cannot access Play store to reinstall lost apps.

I read some threads on this and checked the Time and Date. I toggled Airplane Mode on and off. I went into Manage Apps and cleared the cache for Play store. Still "No Connection" for Play store.
[Verizon Samsung Galaxy S III] Bright09:
Could someone post cm 11 boot animation thanks
[Verizon Samsung Galaxy S III] moparfreak426:
https://db.tt/e595uCiH
[Verizon Samsung Galaxy S III] bmeek:
It sounds like you just "updated" from cm10.2 to cm11 (from jelly beans to kitcat) using cmupdater?

I attempted this as an experiment, and decided to revert to a clean cm11 nandroid without trying too hard to make this dirty flash upgrade work...

That said, it was working well enough to make me suspect that things might have worked alright after flashing 4.4 gapps and clearing data on any apps with issues.

Since Trebuchet isn't in cm11 yet, I didn't bother. I'm back on the last cm10.2 nightly (12/06) as my daily driver, though I'll continue to play with the cm11 nightlies as the changelogs grow.
[Verizon Samsung Galaxy S III] Bright09:
Thank you didn't have this for my 4.4 ose
[Verizon Samsung Galaxy S III] moparfreak426:
Your welcome
[Verizon Samsung Galaxy S III] buschbarber:
The nightlie did not indicate it was for CM11. Almost every day, I see a silver ball icon, on the Notification Bar, indicating a new update is available. I click on it and it downloads. Then, I click on Update. Sometimes, I go to About Phone and see what new Updates are available.

I fixed the problem by downloading Mastamoons 08/20 ggapps and flashing it. Play store, ROM Manager, eCid, etc., now work. I think I had to reinstall one app. I don't remember which.

I am on CM 4.3.1.
[Verizon Samsung Galaxy S III] Bright09:
Its sweet but phone boots to fast to see it lol
[Verizon Samsung Galaxy S III] buschbarber:
OK! I am in error. The Nightlies clearly say CM11. I assume there are no more Nightlies for 10.2? Either stay there or move on to CM11. I found the Q+A section, so sorry for posting here.
[Verizon Samsung Galaxy S III] 996:
Sup guys!

I am having a problem with my GPS stuck on searching when ever I open up Google Maps or any other application involving GPS. When I toggle GPS on and off it quickly locks on... I was wondering why I have to keep doing this for it to lock. Is this a known issue?

I've had problems like this with other AOSP ROMS so yeah. Any suggestions or input would be greatly thanked!
[Verizon Samsung Galaxy S III] wolficus:
not sure... mine locks on pretty quick.

check the screws maybe?
[Verizon Samsung Galaxy S III] npro1464:
How does everything working on the latest CM 10.2 stable release? I had a "stable" release of CM a while ago but it was giving me random problems with making phone calls so I went back to a TW rom. I'd love to have vanilla on my phone again, but when my GPS or phone doesn't work, it makes me want to through my phone at the wall.
[Verizon Samsung Galaxy S III] vforaci:
I've been running it for about a week now with no issues.
[Verizon Samsung Galaxy S III] buschbarber:
I have been running 10.2 Stable since it first came out. There were a couple of Lockups and a couple of Reboots, but no problems for the last weekor more.
[Verizon Samsung Galaxy S III] xdstx:
Just clean flashed cm 10.2 Stable release and I've gotten 2 random reboots already, have I done something wrong? I'm on MF1, flashed 8/20 gapps and wiped dalvik cache/cache. Already did factory data reset and everything.

There are times where I find that the phone is also completely off when I check it, and the only way to get it back is to do a battery pull.
[Verizon Samsung Galaxy S III] phoenixus:
Hey guys,

Sorry for the newb question here. I'm currently running the M1 release, and my phone is prompting me that an update to the final release is available (via about phone > updates). Can one update in this method, almost like a normal OTA? Need to wipe cache/data?

In addition, I flashed the normal gapps as I didn't plan on doing any dirty flashing to the nightlies. If i update in the above way, do I need to flash those special gapps?
[Verizon Samsung Galaxy S III] sanjsrik:
Not a newb question at all. I "thought" I could do a dirty flash over the previous stable to a nightly. Bad idea. I had numerous issues. If in doubt, always do a clean flash by wiping everything, data, dalvik, cache.

You can and SHOULD be backing up using (either) TI Backup or something similar (whatever you choose is your preference) and restore all your applications from that once you boot in and have a stable base install.

Read the OP (original post) in this thread, lots of good advice there.

Good luck.
[Verizon Samsung Galaxy S III] phoenixus:
The built in updater worked fine :)

Made myself a backup, downloaded/installed, went ahead and wiped cache/dalvik. Seems good so far.
[Verizon Samsung Galaxy S III] vonrandy:
Depending on what I'm doing, I still get some random reboots too. Seems to have the most issues when I'm using google maps. I'll get 3 or 4 random reboots a day while using google maps on road trips. I wiped everything, reinstalled everything, cleared all the map data, nothing I do makes any difference. I think some people just have more problems than others, and some people are more tolerant than others.
[Verizon Samsung Galaxy S III] Shibby87:
My bad if this is off topic, I just flashed the latest 10.2 stable yesterday, been on TW since July and want to hold off on 11.0 til there's an RC or stable nightly. First time running AOSP on the GS3, reason being the CleanROM install I had was getting megga sluggish, and it doesn't look like there's going to be a stock rooted 4.3 ROM for awhile since the new OTA relocks the bootloader.. So do AOSP ROMs for the GS3 like CM and liquid accept OTAs from Verizon? Just wondering if I need to buy OTABlocker from the play store so I don't get screwed, thanks!
[Verizon Samsung Galaxy S III] funnyperson1:
No, you will only receive OTAs on TW ROMs, and even then most devs remove the app that checks for updates as part of the debloating (and even then the OTA won't flash correctly unless you're running the stock recovery).
[Verizon Samsung Galaxy S III] Shibby87:
So switching between network modes, LTE, 3G, WiFi etc.. Seems buggy, sometimes I have to reboot after leaving a WiFi hotspot to get LTE working.. Is this a known issue, should I be using a certain radio?
[Verizon Samsung Galaxy S III] phoenixus:
I've got a bug that's driving me crazy. I almost always use an aux cable in my car with Google music. Every time I disconnect the cable, the ringer on my phone does silent and I have to reboot to get it back. Sometimes the media volume goes silent too. Doesn't matter what I change the volume to, it doesn't even make the soundcheck noise when increasing or decreasing.

I seem to remember this happening on my bionic, so its either an aosp bug or a cm bug. Does anyone know a fix short of rebooting?
[Verizon Samsung Galaxy S III] Ok_Kaleidoscope5109:
So it sounds like reboots are normal? My gf sees 3-4 reboots a day despite a clean flash (we've done it twice now to verify), and it's driving her nuts. I may be a ROM flashaholic, but she does NOT want to put up with random reboots. I am running 10.2 stable on her phone btw.

I noticed 10.1 was pretty rock solid for her though, so should I go back to that?
[Verizon Samsung Galaxy S III] vforaci:
Reboots

I thought I'd update this thread.....

I had my first random reboot this morning. I was emailing/surfing when the screen went black and then it proceeded with a reboot. Uptime was about 16 days and I've never had a random reboot on CM10.1 rom.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I'm running the stable version of 10.2 on the MF1 baseband. I saw that Invisiblek posted the new ML1 baseband modem in another thread. Is it safe to flash the new baseband modem on 10.2?
[Verizon Samsung Galaxy S III] fonixmunkee:
I did two days ago. No problems, just make sure you follow his directions.
[Verizon Samsung Galaxy S III] darklavalizard:
The baseband is just the modem file right? It's not the entire firmware including the bootloader? Because I read the ML1 bootloader wasn't able to be unlocked like the old MF1?
[Verizon Samsung Galaxy S III] fonixmunkee:
That is correct, as far as how my small brain comprehends it, "firmware == full OS, baseband/modem file, etc...everything from the vendor." So when he says "baseband," he's referring to the modem file, which is the separate, flash-able ZIP he has linked in that original post: http://xdaforums.com/showthread.php?t=1788313. I just downloaded the baseband ZIP about 1/3 of the way through the post and flashed it: http://invisiblek.org/sch-i535/modems/d2vzw_ML1_modem.zip

Read the whole post and comprehend it...it took me a few reads before I understood what the differences were, and was comfortable with making the change. You must also make sure you are comfortable with your comprehension of the post before you do anything, otherwise you are just taking a gamble. Don't just arbitrarily flash something...I did that when I first got my S3 and was in the hurt locker for a few hours. It's fun to trick out your phone, but with great power comes great responsibility...read & understand! :good:

FAKE EDIT: FYI, that's not me being on a soapbox or scolding you! It's me giving you a heads-up, so you can avoid the pitfalls I just went through! :fingers-crossed:
[Verizon Samsung Galaxy S III] darklavalizard:
No problem, I'm coming from Samsung devices that are not boot loader locked in any shape or form, and where you normally flash modems and never ever do anything with flashing "firmware" or bootloaders, so I just wanted to make sure I had the S3 definition of "baseband" defined for myself.
[Verizon Samsung Galaxy S III] UberSuber:
Yeah, that is a problem with this ROM that has been mentioned several times. Mine has really bad GPS issues on 10.2 as well. It was suggested at one point that flashing back to stock and then back to 10.2 would help, but that made zero difference for me, and I haven't messed with it since then. Phone was perfect on 10.1.3. Using a Rugby pro and the GS3 side-by-side, the GS3 absolutely sucks on GPS on 10.2. Fortunately, the only thing I'm using it for lately is a wifi hotspot for my other devices, so, meh. Otherwise I'd flash back to 10.1.3 in a heartbeat. No real advantage to 10.2 over 10.1.3 that I can see.
[Verizon Samsung Galaxy S III] buschbarber:
I have been using 10.2 Stable and ML1 for some time. I seem to be stuck on 3G. I have not seen 4G in some time. A random freeze and reboot once in a while.

Edit: Somehow, a network setting got changed. Now, I get LTE. I still get random freezes requiring reboots.
[Verizon Samsung Galaxy S III] wpcprez:
I've been running this rom for a week or so and zero reboots. on CM11 I had many random reboots daily. This is rock solid!
[Verizon Samsung Galaxy S III] vforaci:
Just had another, I only noticed since I checked my uptime. Happened after about 12 days up time.
[Verizon Samsung Galaxy S III] buschbarber:
I have a freeze about once a week that requires a battery pull. Many times, it freezes during Screenlock. Also, the Menu and Back Arrow stay lit. The phone seems to still operate in the background, receiving email alerts, etc., but I cannot Unlock the Screenlock or change the screen orientation by rotating the phone.
[Verizon Samsung Galaxy S III] npro1464:
I've been having terribly annoying problems with Maps on CM 10.2. Randomly, my gps won't be able to connect and it will keep searching for a signal. Rebooting doesn't work, I *think* pulling the battery might do the trick, but man, it's annoying. And it happens at the worst times. Has this happened to anyone else?

I'm still on Maps 6.1.4, but it didn't make a difference when I tried updating to the latest Google Maps (in fact, I thought it might have been worse).

edit- Oh, and I haven't updated to ML1, but will it really even help? Thanks!!
[Verizon Samsung Galaxy S III] buschbarber:
I have been having a problem with the People app. When I launch the app and Search for a Contact, the Search crashes. I have to scroll down the list of Contacts to choose the Contact.
[Verizon Samsung Galaxy S III] wolficus:
people keep mentioning screws being tightened as a possible fix for gps.

ml1 helps data... i think gps is its own antenna.
[Verizon Samsung Galaxy S III] nh2123:
Hey, I have an issue with all sound muting (ringtones, media, alarms, etc.). The only way I can get it back is with a restart. I tried booting recovery and clearing cache and dalvik to no avail. Anyone have ideas?
[Verizon Samsung Galaxy S III] h82or8:
I converted to CM 10.2 (stable) when the recent upgrade kept annoying me to update to sammy's newest bloated garbage. At the same time, I update the modem to ML1. Not had a single issue with the radio.

SMS in Hangouts FCs always and the newest Maps frequently FCs. Other that those, which I didn't really need and don't really use, I'm satisfied with the switch.
[Verizon Samsung Galaxy S III] wolficus:
curious.. do you have separate ringtone volume and notification volumes set?

i had the same issue... and had them both separate. when i linked them back together.. issue went away.
[Verizon Samsung Galaxy S III] nh2123:
No they are linked, thanks.
[Verizon Samsung Galaxy S III] funnyperson1:
There was a 10.2.1 release, did anyone try it?
[Verizon Samsung Galaxy S III] h82or8:
You actually have the ROM of the 10.2.1 build for the d2vzw?
[Verizon Samsung Galaxy S III] timmyk465:
CM10.2.1

I've flashed the new update. So far nothing really noticeable from my day to day use. The alarm volume trying to go through the dock audio still happens, so it looks like I still can't dock my phone at night :mad: