yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SJUnion:
Blazingly fast ROM, awesome. :highfive:

That being said I had a couple hiccups but most were easily fixed.

Bluetooth audio would sync but not play through my car. A reset and toggle fixed that.

Wifi wouldn't see nearby networks. Another reset and toggle fixed that.

GPS couldn't get a fix. Wiped the google frameworks data, reset, and toggle and then that was fine.

So most of the major technical hiccups were easily straightened out.

Only one problem I havent been able to fix. Switftkey 3, installed from the Amazon Market just force closes when I try to set it up. Ive tried making it my default input method but the app still force closes when I try to set it up. Ive tried reinstalling and got the same results. Any ideas?

Thank you!
[Verizon Samsung Galaxy S III] josh995:
I just installed from the cm update under about phone. It says I have the 10-11-12 experimental M2
[Verizon Samsung Galaxy S III] scriz:
Yup, just installed 10/11 nightly over m2
[Verizon Samsung Galaxy S III] imp3r10:
What do you mean by reset and toggle?
[Verizon Samsung Galaxy S III] SJUnion:
Im sorry I meant reboot. So I reboot the phone and toggled the radios off and on.

---------- Post added at 06:05 PM ---------- Previous post was at 06:01 PM ----------

Also one other small and intermittent issue.

Occasional screen flicker pulling down the notification bar.
[Verizon Samsung Galaxy S III] Brian Gove:
nope, other way around. AOSP is generally better than TW
[Verizon Samsung Galaxy S III] That Baker Guy:
my call volume seems fine, just spent 45 minutes on the phone with no echo and it wasnt loud at all granted i did turn it down all the way. but it was fine
[Verizon Samsung Galaxy S III] Restola:
Haven't used the cm update utility built in yet. Does it automatically create a backup? And it only works on cwm right?

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] dvaderx:
the echo is on the other end you won't hear it. and its only with sp
[Verizon Samsung Galaxy S III] neyenlives:
It uses only CWR but if you tell it to install it will boot into TWRP still, but you then have to manually navigate to and execute the flash. It gives you the option to wipe and stuff too.
[Verizon Samsung Galaxy S III] TechSavvy2:
Its not a single call that's the issue. If you're in a dynamic environment and need it to be higher and lower on different calls, you'll notice your next call will usually just be maxed out again.

And others haven't reported this, but if I mess with the volume too much during a call, it actually fc's the phone app. Then I have to pull battery to even hang up. This happens about 5 tines a day.
[Verizon Samsung Galaxy S III] fix-this!:
When your wifi wouldnt work did it say out of range or wps failed? You said you fixed it by turning the radio off and on?
[Verizon Samsung Galaxy S III] thewebsiteisdown:
Ok.. Here we go. I saw the m2 thread which is now locked. I saw the directions stating to flash to a stock rom but there was no link to how to obtain such rom.. My question is this.

Should I flash the " VRALHD_I535VZWALHD_1092717_REV09 " rom / the hd radio then upgrade to m2?

I saw some one mention not using a leaked rom or something along those lines some where so I'm concerned if that's a good idea or not at this point based on spotting that but I can't tell information wise from my research if that rom is considered leaked or not???

I made a backup of my imei but I would rather not have to use it if something goes wrong trying to go back to what I'm unsure is a stock rom at this point or not for a good base to start a new, like the directions suggest in that thread.

Any help is greatly appreciated here.

I have random issues like my signal bars disappearing and random activation issues with my phone and I'm wondering if I need to start a new mind you.

Thanks again.
[Verizon Samsung Galaxy S III] SJUnion:
WPS Failed. I rebooted the phone then toggled the wifi radio and then it saw the networks fine.
[Verizon Samsung Galaxy S III] josh995:
Which one from this list is the newest one that I should download?
[Verizon Samsung Galaxy S III] Jay Evans:
HD is not an official OTA, last was G7. Should you? As in all flashing "you pays your money and takes your chances."
[Verizon Samsung Galaxy S III] Restola:
I know this doesn't help you, but I've never had that happen. I wonder how many people have to battery pull to hang up after changing the volume too much.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] thewebsiteisdown:
Are the bars disappearing a normal thing?

If so then who cares I'll stay like this but if it's not normal, then perhaps I should start a new to see if it alleviates the issues I'm having.

I need solid advice though from some one on the sIII scene longer then me or perhaps I could say using these roms longer then me on this device in particular.
[Verizon Samsung Galaxy S III] fix-this!:
Glad we have another person with that issue, that makes 3 now. Hopefully the cm team look into this. I just flashed m2 and after every reboot WiFi shuts off and I have to either toggle it back on or toggle airplane mode.
[Verizon Samsung Galaxy S III] SJUnion:
The flicker on the notification pulldown was caused by an option in Nova Launcher. I like to run my home screens with the notification bar hidden....turns out having that Nova feature active makes the notification pulldown flicker. Shut it off and the flicker went away.
[Verizon Samsung Galaxy S III] f3liC:
I'm having weird flickering issues even as I'm writing this out as we speak. Its like a ghost image of a screen that happened a few seconds earlier.

Note that i did dirty flash over m1. I want to see if this is happening to anyone else first. If not I'll just do a clean flash. Thanks.

Edit - using stock launcher
[Verizon Samsung Galaxy S III] ercDROID:
On M2.....having all kind of web browsing issues. All sites would only load part way and then just stop. This is on WiFi or regular data. Had to reboot. Something still isn't right.
[Verizon Samsung Galaxy S III] danstar:
I have tried a few of the JB roms and with each one, after I get things set up, I keep getting a text message from it appears to be Verizon generated, but there is nothing in the message. Is this something others are experiencing?
[Verizon Samsung Galaxy S III] coldhardtruth:
http://xdaforums.com/showthread.php?t=1866558
[Verizon Samsung Galaxy S III] ercDROID:
Web browsing problems on WiFi and data appear to be kernel related for me. I tried everything on stock kernel and nothing worked. I flashed imoseyons latest experimental and it fixed the problem.
[Verizon Samsung Galaxy S III] apacseven:
You don't need to flash stock before you update to M2. Theres no reason to wipe and install a different base just to reinstall the original base. That thread wanted to start on the assumption that wiping clean is the only way to install a new CM10. If this were true, the CM updater itself would wipe your phone (which last time I used it, it did not).
[Verizon Samsung Galaxy S III] edwards311:
Gotta give the cache and everything to get settled in.... Battery life always sucks the 1st day or so, at least from my experience.
[Verizon Samsung Galaxy S III] Brian Gove:
You're responding to like 5 different posts lol.

Ignore the M2 thread. That was just an overanxious user making threads. He had an idea that EVERYONE should wipe their phone and start over so we could all start from scratch on M2... needless to say we're not all wiping our phone for him lol.

I believe it was probably my sticky in the Q&A Forum, or a response to someone elses thread that said not to flash the ROM you mentioned. But you took it out of context. My sticky is directed at making your phone stock so you can bring it to Verizon if needed without the modding being detected, so therefor you cant flash a leak that's not officially out if you want your phone to pass for official lol.

Far as the IMEI backup, if you used the method that uses terminal emulator and the /nvbackup command you theoretically should never lose IMEI. Quick and simple, the theory is that people were losing IMEI because of triggering a restore of a faulty IMEI(This is on Samsung, it's nothing any individual did). The faulty IMEI is whats considered "losing IMEI". The /nvbackup method overwrites the faulty one with your current one, which is good. So if in the future you trigger that restore then it restores a good IMEI and you don't "lose" it.

Signal bars dissappearing is more than likely the dreaded data drops on all AOSP ROMs. Happens often in a 3g area.

Far as the activation issues, describe them in more detail.
[Verizon Samsung Galaxy S III] alee:
Not exactly. The thread was intended to get everyone back to the same baseline because we have a lot of folks that are clouding the thread with bug reports when they have effectively tainted their installs after messing around with several roms and kernels. It has already been proven that some people who claim their NFC doesn't work have to flash back to stock and then install CM10 after to get it to work.

I still stand by my position. If the CM team wants to mark milestones, at the very least, everyone here should "reset" as well. This thread is mess, there is no way to determine whether people have screwed up their own builds over time or whether it's a legit bug. Following some best practices would help a lot.
[Verizon Samsung Galaxy S III] blmetzger:
Rear Speaker Problem

I ask very few questions and read the forums for weeks before posting but have an issue I cannot resolve. I'm currently on the 10/10/12 build, but have had the same problem on nightlies for the last couple of weeks. All sound that should play through the rear speaker, like phone calls on speakerphone or youtube videos play on a very low volume through the external speaker, even with the volume turned all the way up. When I make a call it plays normally as I hold it to my ear, but once I activate speakerphone it appears to mute all sound. Any help would be appreciated and I apologize if this has already been addressed, but I simply cannot find an answer. Thanks.
[Verizon Samsung Galaxy S III] fix-this!:
found a fix for anyone having issues with the wifi saying out of range or wps failed. go into your router settings and change your ssid name and password, restart your router and connect on your phone. worked great for me. don't now why this would happen on aosp roms but im glad i got it solved.
[Verizon Samsung Galaxy S III] dmeadows013:
Does m2 fix the data drops or do I need a patch

Via my Google Galaxy S3 running AOKP goodness
[Verizon Samsung Galaxy S III] SymbioticGenius:
For the record, I dirty flashed CM10 over CM9, and each Cm10 nightly I've ever flashed since then. I have had none, I repeat NONE of the major issues people have complained about on this thread. All of the minor issues were fixed with a fixed permissions or a dirty flash of the proceeding nightlies. Last I checked when you get an OTA update on a stock rom, it doesn't wipe anything, I don't see why people see the need to do so on a nightly flash

With that said. M2 is awesome. I love what CM has come to since my old Dx1 and DX2 on CM7. I only want Tablet mode to place my status bar on the bottom and I will have acquired something I like to call perfection. Thank you.
[Verizon Samsung Galaxy S III] thewebsiteisdown:
I will answer it detailed for you in short terms if possible. I had tried a newer hd modem after flashing to cm10 from stock rom. I had cleared caches etc. before the install of cm10 and tried that modem, and I kept having activation issues. I flashed back to the g7 and the issue went away or so I thought.

It came back and mind you that, I was clearing caches reinstalling cm10 etc.... and everything was running smooth and then the activation thing came back on me. I can't send mms while this is going on. I wil exit out of it by pressing each corner in a circular motion until it shuts the window but its like its still running stopping me from sending mms while it's at it.

I've had that happen twice now. since flashing back to the g7 modem.. One time I was able to get it to stop by rebooting and it went away and another time I had to wipe dalvik and it stopped, which I will duly note I do when needed so it wasn't because I had missed it or something along those lines.

I also notice that my signal bars will just completely disappear. I wouldn't think they would disappear like that, it's almost odd the way it looks. That part makes me think it's all jacked up some how.. They don't even show an outline of the bars when it happens like it's resetting itself. My signal / phone quality in iffy signal areas is flaky and will drop calls in my house where I could normally talk semi decent with my thunderbolt which everyone called a piece for signal issues lol...

Just all this combined makes me wonder but maybe I'm being paranoid and this is normal for this phone..

I understand what you're saying. I honestly think some things that get left behind or wiped out need to be in place at the base in order for there to be order.

There are some things you and I can't touch perhaps I should say.

I came from an hd2 originally and I swear I remember that being preached in that forum sub category. Maybe I don't remember correctly been to long. I'm to lazy to look lol.

.
[Verizon Samsung Galaxy S III] Zacharybinx34:
These Data drops are killing this experience.
[Verizon Samsung Galaxy S III] apacseven:
I understand that you believe that flashing one ROM, then flashing another ROM, somehow messes things up. This simply is not the case. The point of these milestones is not to 'reset' everyone. You cant screw up a build over time if you are continually flashing newer builds. The 'you gotta wipe data every time you install a nightly' philosophy is bunk. I know this thread can seem like a mess, as its gotten so lengthy, but starting multiple threads for a single build would be in and of itself, a mess.
[Verizon Samsung Galaxy S III] imp3r10:
Don't know if this is a big or not but when choosing an alarm in the clock app, but when you click a sound it doesn't play even if the sound is on.
[Verizon Samsung Galaxy S III] alee:
Consider one of the reasons why carriers lock bootloaders. They have a single baseline release that every consumer has, with an upgrade process that is as reliable as it can be. That process is tested and retested over and over again. An update is built with a purpose.

If you want to dirty flash, that's fine, but a clean install from stock to CM10 with an M release does everyone a favor.

It's pretty clear that I'm in the minority here, so this will be my last whine on this. But continuing on this path is no way to test software and generates a lot of unnecessary noise about what is supposed to be one of the highest quality Android projects out there.
[Verizon Samsung Galaxy S III] kichard:
Toggle the sound up or down then select one.
[Verizon Samsung Galaxy S III] Zacharybinx34:
So why are there two 10-11 builds?

Also, when full wiping does anyone know what I need to restore to get settings back and how to have my apps auto download from the store?

Full wiping is such a pain and takes too much time...
[Verizon Samsung Galaxy S III] tv31284:
If people have been flashing between kernels and ROMs without wiping it would be a good idea to wipe and start anew, but if you've only been upgrading from cm to cm, there's really no reason too. Many prominent members of the cm team have already stated so.
[Verizon Samsung Galaxy S III] apacseven:
One of the 10-11 builds is the M release, the other is a normal nightly. Im not sure what you can restore to get settings back. System data with titanium I guess would restore settings. I dont wipe data when I flash newer CM because its "such a pain and takes too much time" (I also dont have any issues). Also, I dont want to talk down to the people who do have issues, I feel for them. But their issues are not from dirty flashing.
[Verizon Samsung Galaxy S III] masri1987:
everyone calm down, 10-12 will be out soon and resolve all this confusion lol
[Verizon Samsung Galaxy S III] imp3r10:
Absolutely when going from nonCM to CM a wipe is necessary but not for the night little updates unless M(milestone?), is released. I agree with you that the major updates warrant a wipe.
[Verizon Samsung Galaxy S III] Imatoasta:
Somebody repost the cm devs quote about wiping and "dirty" flashing being BS.

On topic: these data drops are making me want to throw my phone.
[Verizon Samsung Galaxy S III] tv31284:
http://xdaforums.com/showpost.php?p=32256595&postcount=3856

This post
[Verizon Samsung Galaxy S III] Brian Gove:
You're assuming everyone gives a sh!t...Flashing back to stock isn't going to do much more than irritate people because the OTA will start downloading.
[Verizon Samsung Galaxy S III] iofthestorm:
Not even, M builds are just blessed nightlies. They're from the same branches and everything. If you go from M to M that's sort of a big change but as arcee said there's never a reason you *have* to wipe data from build to build.
[Verizon Samsung Galaxy S III] goldsmitht:
Just to add my 2¢; I've been dirty flashing since my DX; never saw any reason to wipe out a base if it is working. And unlike those who seem to be having problems, aside from a few odd data drops, my call volume is fine after I set it, songs play fine out the speakers, Bluetooth works, and volume on video record is fine.

But that's just my experience, YMMV.
[Verizon Samsung Galaxy S III] NegativeOne:
Can we discuss flash theory somewhere else?
[Verizon Samsung Galaxy S III] Restola:
This bug has been around a while. If you lose notification/alarm sounds go into settings/sound and toggle "link ring tone and notification volume"

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] kimsj756:
I partially agree. I always dirty flash when updating on cm nightlies. And I have no problem. But I partially don't agree with you about the low volume recording. It does use the top mic only and records with low volume. I think I'm extra sensitive because I record my daughter to keep good memories of her. And it is different between when I record it on any cm based rom and touchwiz. Just my thought. Haha
[Verizon Samsung Galaxy S III] thewebsiteisdown:
I swear to you my phones volume during a phone call hasn't adjusted up or down for me properly ever, so far. It just stays loud. I have to hold the phone away from my ear and you can hear it across the room it's so loud.

I've been on the scene for ahwile so it's not something I'm doing wrong per say.
[Verizon Samsung Galaxy S III] ms262c:
Ive found that pressing the volume rocker and then sliding the pop up volume to a higher level and then back down works. Only way i could get it to work.
[Verizon Samsung Galaxy S III] kimsj756:
Talking about volume issue...

Is there any way to increase the mic gain (top mic)? So it can record video little louder?
[Verizon Samsung Galaxy S III] gwallers:
Everyone has different ears... but I'm on board with you... Mine is way to loud for use.. Everyone in my office gets to share my phone calls....
[Verizon Samsung Galaxy S III] NegativeOne:
I feel like this thread needs to be closed and we need to have a whole section for CM nightlies discussions. The same issues and questions keep getting circulated over and over again. That means new people that come in have to keep asking over and over and waiting to have someone regurgitate the answer.

It'd be useful to have separate posts for separate issues so that people could EASILY find answers to their questions, and to reduce the chatter and noise here.
[Verizon Samsung Galaxy S III] tyrnight:
Since 10/11 ive lost access to my EXT-sd card.. it literally doesnt show up.. and its been in there since i bought this at launch.. ive reseated and ive even pulled it out and reformatted it fat-32 in a computer.. it physically will not see the card.. I cant even format it in the phone cuz its as if it is not there..

anyone else having this issue?

Ive tried 3 cards.. all the same outcome.. Bad reader in the phone?
[Verizon Samsung Galaxy S III] littleneutrino:
Is there any way to set a wallpaper image as the background without using that Grid slider thing. It will not allow me to use full images i would normally use as wallpapers, it makes me crop them.
[Verizon Samsung Galaxy S III] psufan5:
Any way to alleviate the issue where apps on the market wont download due to not being for this current version of the OS? :\ Even google+ wont download.
[Verizon Samsung Galaxy S III] Argent36:
Interesting - Google + works on the newest nightly...but I've just been dirty flashing - try restoring your missing apps from your backups...
[Verizon Samsung Galaxy S III] psufan5:
I did that, but it wont even show on the market - so the latest update from yesterday wont come down.. I think I may have to have a touchwiz rom on backup so I can get the latest apps, make a backup, then reflash this restoring them...
[Verizon Samsung Galaxy S III] PerCompLLC:
I use the Wallpaper Wizardry app available in the market. It's free and it works great!
[Verizon Samsung Galaxy S III] Argent36:
Ah ok didn't realize you were trying to update it
[Verizon Samsung Galaxy S III] josh995:
I'm not having ANY problems with CM10. Literally, zero problems. I mean, I've only had it 2 days now, I came from stock touchwiz. Maybe something will come up but so far, nothing.

I don't record video, so the low volume issue doesn't affect me. When I call someone/get a call, my phone volume is absolutely fine.

Really loving aosp. Google Now is just amazing, so much better than S-Voice. Hands down.
[Verizon Samsung Galaxy S III] mwep:
Running Clean Install of 10-11 nightly and for some reason Bluetooth Audio is not working through my Ford Sync.

I can sync bluetooth just fine but nothing plays out of the car speakers. I have tried Google Play, Slacker, and Pandora with same results.

Any suggestions ?
[Verizon Samsung Galaxy S III] sullivan1985:
Ugh! More annoying Dirty vs. Clean installed fighting. Seems like every few pages they start again.

Do whatever you feel works best! We have people reporting both good and bad results no matter what way they install. No official voice from CM is telling us what the suggested method is for each release.

I'm using the built in updater and only updating when a significant number of changes have been made aand all is well.

-Sully
[Verizon Samsung Galaxy S III] sparkerjc:
I can't wait until they add clean and dirty versions of the built in updater, that way there is always something to argue about. :D
[Verizon Samsung Galaxy S III] That Baker Guy:
im using nova launcher on m2, im having trouble getting it to stick as the default launcher, it will stick for a while but every now and then it will default back to trebuchet, any thoughts?
[Verizon Samsung Galaxy S III] jmill75:
I just can't believe this bug still persists...I mean how can you have 2 monthly "stable" builds out when the phone portion is not working correctly. Im not knocking anyone in particular just very confused how something so important is not functioning right but we have these M builds that are out.

People bashed me before because these are nightly buggy builds...then whats M's for
[Verizon Samsung Galaxy S III] NegativeOne:
Monthlies just mean that they are going to not put in risky changes for the few days before the nightly is due in order to avoid creating new problems.
[Verizon Samsung Galaxy S III] ashtro:
i flashed 10/11 yesterday and today i had more frequent data drops than i have ever noticed before. can any one relate?
[Verizon Samsung Galaxy S III] NegativeOne:
Yes, every time I am stealing emergency rations from my parents' bomb shelter, my girlfriend says she can't hear me well on skype :)
[Verizon Samsung Galaxy S III] TechSavvy2:
And even more, its not just d2vzw that has the call volume bug. All the d2common devices (all gs3's) have it with cm10. Its just taking a while to get audio libs straightened out.
[Verizon Samsung Galaxy S III] fix-this!:
m2 is running fantastic for me.
[Verizon Samsung Galaxy S III] razor237:
Is there a Fix for outputting audio to a radio using Bluetooth ...i cant get it working at all