yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] stkiswr:
Not fore. Did you wipe system? If not just go back into re every wipe cache dalvik and system and reflash rc1 and gapps

Edit only issue I have is going to a lower than 8mp resolution
[Verizon Samsung Galaxy S III] mastamoon:
The camera fix was only merged about 2 hrs ago, when did the RC1 build go live?
[Verizon Samsung Galaxy S III] Obaterista93:
Do the RC builds go through the same code freezes as the milestones? I know the milestone builds freeze code for like a week in advance.
[Verizon Samsung Galaxy S III] dvaderx:
how about low cam corder volume? I tried AOKP a few weeks ago and it seems that bug was still around.. has it be fixed recently?

Thanks
[Verizon Samsung Galaxy S III] uberbdon:
Any reason there aren't any known issues listed in the OP?
[Verizon Samsung Galaxy S III] aaron1006:
So what's the trick to not losing data after flashing? I've read of numerous people having the problem, and ways to fix it, but never a way to get back on CM and have it working. After every time I flash I get constant roaming, and to regain my connection I have to root66 back to stock, do the dialer code for a factory reset, and adb reboot nvrestore. Obviously I already tried the easy stuff (like everything in the second post), but my issue is whenever I flash to it the problem comes back. Am I missing a key step or something?
[Verizon Samsung Galaxy S III] RedRumy3:
I just flashed latest nightly and camera still hangs when I try to change settings hmm.
[Verizon Samsung Galaxy S III] titanshadow:
You know, I've never had any of the problems like that. Could it be your unlocking method?
[Verizon Samsung Galaxy S III] mastamoon:
Still buggy but here is how to fix.

Change camera scene from auto to whatever. Camera will lock up. Reboot. Now you should be able to change all settings no problem.
[Verizon Samsung Galaxy S III] Argent36:
Another option to getting around the camera problem (at least because I have no issues with the camera) is to use a different camera app. I'm using Vignette as my main camera app with no lock up etc on RC1

what doesn't work is wireless sync to my Fitbit flex - Samsung apparently has some special code implemented to work with the Fitbit's for wireless sync but it so far only appears to work on TW based roms' - anyone have a clue if that can be ported out to work in CM?
[Verizon Samsung Galaxy S III] blueblur:
I'm getting 15 minutes tops without rebooting when actively using the phone. Apollo (music player) is playing everything through the right channel only, spotify plays it in stereo. Cellphone bluetooth kept dropping when used with my pioneer z120BT stereo. last successfully used a nightly from 3/15 (before they switched to the newer kernel) but had issues with bluetooth audio not being crisp and foward and backwards track control is not working from the car, however it does work from my computer. Too unstable for me, unfortunately.

completely fresh install, format dalvik cache etc, definitely not a dirty flash.
[Verizon Samsung Galaxy S III] invisiblek:
Please try this kernel and let me know if it crashes (pm is fine)

http://invisiblek.chickenkiller.com/testkernels/caf_207-korg_3.4.11.zip

(I didn't include the wifi module, so your wifi wont work with this. Reflash your rom later to get back to where your'e at)

This goes for anyone getting random reboots. I need to know if this particular kernel revision suffers from the random reboots. Do whatever you can to make it fail!!!
[Verizon Samsung Galaxy S III] jweavis:
Dirty flashed RC1 over unofficial nightly, running amazingly smooth.
[Verizon Samsung Galaxy S III] Restola:
PM me some known issues with RC1 (besides the camera app)
[Verizon Samsung Galaxy S III] Restola:
Does this fix it going forward through additional reboots?

*EDIT* this does fix it through repeated reboots. I'm using 5/9 nightly.
[Verizon Samsung Galaxy S III] uberbdon:
I always check OP for known bugs, then I move on to comments to see what bugs I should be ready for in case I flash it. Is the camera considered a "known issue"?
[Verizon Samsung Galaxy S III] Restola:
yes and ill update it when im done testing something
[Verizon Samsung Galaxy S III] zach471:
I've been searching for an answer on that question as well, since it works on my wife's stock unrooted Note II. I flashed a TW ROM to test it on my S3 and it worked flawlessly. What it comes down to is the Bluetooth stack. AOSP BT software is the problem (it's not just CM, it's all AOSP-based ROMs), and until Fitbit comes out with a fix on their end, or until Google updates the stack on its end, I bet we're out of luck.

I'm not aware of any AOSP-based ROM that incorporates Samsung's BT stack -- but that's exactly what you'd need to get it to work.
[Verizon Samsung Galaxy S III] mastamoon:
Possible 1 channel Audio fix/workaround...

Settings>Sound>Volumes.. uncheck "Volume Keys control ringtone volume".

Apparently you can recheck this after turning off and stuff should still work.
[Verizon Samsung Galaxy S III] blueblur:
The only options I see under 'volumes' is "Link Ringtone & Notification Volumes" and" Silent mode affects notifications" - both are unchecked and still only right side. I looked several other places and didnt see it
[Verizon Samsung Galaxy S III] Vidfreek:
Tried out the new RC1 this morning, havent had much luck with any AOSP type roms lately and this is no exception, although it did let me get further than some others recently. I got all booted up, waited the normal 5 minutes or so and started the setup, Wifi was broke right away and couldnt turn on, I bi-passed that and went into the main screen, had to reboot the phone which then completely froze it up. After a battery pull and restart Wifi was working again, got connected to the wireless here and proceeded to setup google and my accounts. Got Titanium backup downloaded and ran that for the first time, as soon as I did my SD card suddenly disappeared all together and wouldnt come back, couldnt mount or unmount anything so I took the back off of the phone and pulled out the SD card and re-inserted it, nothing happened, tried it again and the phone rebooted and then got stuck on the boot up Cyanogen mod splash screen

Needless to say that isnt going to work to use this as a daily anything, cant figure out what is going on with these AOSP roms not liking my phone anymore, I had no issues before running them, someone said it might have to do with some Linux kernel that they are using now? Can I flash a different kernel that doesnt use that to get something to work? I cant imagine an RC of Cyanogen having that many problems right out of the gate, it has to be some incompatibility that isnt normal with my phone compared to others.....really sucks because I would like to run to run an AOSP ROM, but so far in the past month or two I've been stuck using TW roms only.....sigh
[Verizon Samsung Galaxy S III] ugachris:
What date are you running? This issue popped up with the 5/8 nightly.
[Verizon Samsung Galaxy S III] har02052:
I just flashed RC1 last night. It runs super smooth, except I am having two issues. The fist is the camera. The first time I open it up, it is working but then quickly hangs and says that the gallery isn't working. I leave the app and try to go back in and it says, cannot connect to camera. I then did a clean install. Same thing. Can't open the camera at all. 30 minutes later though, it seems to work. No hang up. Didn't reboot. Weird.

Second thing is the battery life. I was 100% this morning. Died at 945am with normal usage. I put in a new battery and did the clean install (for both the camera and battery reasons) and it seems to be better so far, only 2% used in an hour. I will repost with an update.
[Verizon Samsung Galaxy S III] Hybridnoob:
From a few posts above...

Still buggy but here is how to fix.

Change camera scene from auto to whatever. Camera will lock up. Reboot. Now you should be able to change all settings no problem.
[Verizon Samsung Galaxy S III] blueblur:
build # cm_d2vzw-userdebug 4.2.2 JDQ39E eng..20130508.085552 test-keys (supposedly RC1 from get.cm and d2vzw)
[Verizon Samsung Galaxy S III] ugachris:
Are you having the one channel sound issue?
[Verizon Samsung Galaxy S III] sanjsrik:
In terms of the echo during a call. I still get this complaint from almost anyone on the call with me on their side.

Does anyone have a fix for this yet, or should I just try to do a clean flash of 5/9 nightly and see what happens?

Thank you in advance.
[Verizon Samsung Galaxy S III] toddrosenberger:
Just saw the post above about the one channel sound issue. Not sure if this is what im having but im on M2 and when I plug my phone into some things the sound is very low, can't even hear it without turning volume to max on whatever your plugging into. For example my mp3 hook up in my car, when I plug my phone in I can't even hear the song unless I turn the volume on the car stereo to max. But I can plug it into my surround sound and it works fine, headphones are fine. I thought it was the car hook up but plugged my wife's phone and it sounded fine. Anyone else have this issue. I flashed the rc1 and had same issue plus the camera issue so I went back to m2 for now..
[Verizon Samsung Galaxy S III] will.bates94:
I feel ya man. I'm from northern Michigan but I'm on a server 2008r2 class in Chicago and I don't get 4g where I am at...and I have an unlimited data plan...and I hate how slow the WiFi is at the hotel -.- I hope they resolve this soon...
[Verizon Samsung Galaxy S III] thafngame24:
What kernel are you guys using or recommend for CM 10.1?
[Verizon Samsung Galaxy S III] will.bates94:
Just the one that came with the unofficial build. No reason to change mine really. I'm just waiting for a good nightly build
[Verizon Samsung Galaxy S III] goldsmitht:
Don't think anyone has dev'd any for 4.2 yet. KT was working on it, but with the problems CM is having getting the official build bot going, guess he is waiting to turn one out.

:cyclops:
[Verizon Samsung Galaxy S III] PerCompLLC:
I'm seeing the same thing as well... I'm sure it will be resolved soon (I hope).
[Verizon Samsung Galaxy S III] vincatzero:
I'm getting significantly decreased signal as well
[Verizon Samsung Galaxy S III] Div033:
Glad its not just me then. I hope they fix this quickly because good god the battery life on 4.2 is phenomenal. On TW I could get 4.5-5 hours of 4G screen on time, but with this ROM I'm projecting at least 6 hours.

After reading about how many issues the nexus devices were having with reboots and freezes on 4.2 I became skeptical of how much of an improvement it would be. I feel those concerns have been laid to rest as things are running great.

I did notice a bit of homescreen lag this morning whereas it was perfectly smooth the previous night. A reboot fixed it, but I shouldn't have to reboot each morning to have a smooth experience. I'll chalk it up to early alpha software and hope for improvements as time goes on.
[Verizon Samsung Galaxy S III] mastamoon:
My unofficial 12/19 build, repo sync as of 9:15am EST. Fixes NFC without having to flash back to a TW rom then forward again, working radio & MMS size tweak.

Enjoy.

http://d-h.st/oky and http://goo.im/gapps/gapps-jb-20121212-signed.zip

**REUPLOADED**
[Verizon Samsung Galaxy S III] will.bates94:
You. Are. Amazing.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Does this fix tethering?
[Verizon Samsung Galaxy S III] will.bates94:
I'll try to confirm this once I get a chance to flash it.
[Verizon Samsung Galaxy S III] mastamoon:
IDK, I dont tether but unless a tethering fix got merged overnight, I dont think it should fix it.. but stranger things have happened :D
[Verizon Samsung Galaxy S III] will.bates94:
Hey man your dropbox link got stopped due to traffic.
[Verizon Samsung Galaxy S III] dpaine88:
I've been having some issues with my data connection crapping out.

It goes like this.

I am driving to a destination. I get to destination and look and see there is full bars, but they are white and there is no 3g/4g symbol at all. If I go into "About Phone" it says "Mobile Networks: Disconnected".

The phone can sit there all day long and won't get data back until I cycle airplane mode or reboot.

Anyone else getting this?
[Verizon Samsung Galaxy S III] PerCompLLC:
PM me and I can share a folder with you on my Dropbox (50GB) account. Would that work?

Edit: I guess that won't work either if Dropbox is stopping the shares due to traffic. Try Google Drive?
[Verizon Samsung Galaxy S III] Argent36:
mastamoon - I can try putting it up on my Google Drive
[Verizon Samsung Galaxy S III] mastamoon:
I

Im not sure PerCompLLC

also I reuploaded at another host.. http://d-h.st/oky

---------- Post added at 10:55 AM ---------- Previous post was at 10:51 AM ----------

I rehosted at d-h.st so should be ok, ill just use that from now on. Thanks anyway though :D
[Verizon Samsung Galaxy S III] will.bates94:
Seems like NFC is still not turning on for me...
[Verizon Samsung Galaxy S III] Phush:
Just adding another experience report:

Came from one of the recent CM10 nightlies

Flashed newest TWRP from OP's link

Wiped cache/dalvik

Flashed mastamoon's 1219 unofficial

Flashed 1212 gapps

Everything working beautifully (except NFC I think, greyed out after checking. Never used it before and no way to test)

Thanks to everyone!
[Verizon Samsung Galaxy S III] ctheory83:
Confirm tethering, if you could.
[Verizon Samsung Galaxy S III] Restola:
You dont see this?
[Verizon Samsung Galaxy S III] WhiteBoy997:
So I flashed rc1 today before I headed out for my finals and it was running perfectly until I kept getting setup wizard fc's and than the camera kept saying "can't connect to camera". So I restored my m2 backup. Hopefully there will be an rc2 soon that will fix all of our issues.
[Verizon Samsung Galaxy S III] NegativeOne:
Just did a clean install of rc1 and I'm getting random reboots.

One thing I noticed was -- i flashed through rom manager and told it to clear data and cache, and i forgot to flash gapps, but when flashed I still had gmail and google play market. (I did have to go through the activation dialog though)

Was my flash not clean?

In any case, are there any logs I can get for the random reboots?
[Verizon Samsung Galaxy S III] blueblur:
yes, with apollo does this in both headphones mode and bluetooth mode. spotify plays fine
[Verizon Samsung Galaxy S III] blueblur:
I positively don't see that.
[Verizon Samsung Galaxy S III] blueblur:
I had random reboots too. I am using a test kernel that appears to have resolved the reboots. invisiblek had me test it out. I haven't had a reboot in 3 hours and 11 minutes. I wasn't even making it to 20 minutes before the 'fix'; at the most, it was rebooting in under 10 minutes.

I don't want to say it fixes the problem without further testing but keep an eye out for an update regarding the reboots.
[Verizon Samsung Galaxy S III] Restola:
I finally found my headphones, this did not fix the issue for me on 5/9 nightly.
[Verizon Samsung Galaxy S III] NegativeOne:
Can I get my hands on this too? I'm a little surprised it's a kernel thing - then I'd imagine everyone would get it. I thought it might be some app causing the phone to crash.
[Verizon Samsung Galaxy S III] blueblur:
http://xdaforums.com/showpost.php?p=41217161&postcount=1564

Fair warning, wifi module is not enabled on this kernel, i dont particularly need it but as always, FYI.

clear cache, clear dalvik, flash zip. reboot. done.

I noticed it was a little choppy for a few minutes and I'm thinking ugh... but it's buttery smooth now and stable. still got some audio issues. the camera doesn't seem to have any problem with this kernel either, the scene change mode does NOT lock the camera and photos are being taken just fine.

EDIT

might be something with the specific model of the phone. I preordered mine on VZW and got it before it arrived in stores.

baseband version i535vrbmb1

I thought I saw a hardware version once but I'm not seeing it at all right now. shrug.
[Verizon Samsung Galaxy S III] sanjsrik:
Even on the 5/9 nightly that was meant to fix this, following the advice above still locks up the camera after a reboot. Anyone else having issues still with camera.

Echo is completely gone on at least 1 phone call i made today.

It's progress.
[Verizon Samsung Galaxy S III] airmaxx23:
Give the KT747 kernel a try, I've been using it on every build since 4/19-ish and have not had a single reboot.
[Verizon Samsung Galaxy S III] Restola:
No stereo logcat:

https://docs.google.com/file/d/0B89vrGhlDBcEM0ZqMGFGcFdCaXc/edit?usp=sharing

I started recording, launched Pocket Casts, hit play on a podcast, listened to it play from 1 headphone for a few seconds, and paused the recording.
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/37261/ - this might fix the 1 channel audio issue, making a build now myself, should be included in the next nightly

http://review.cyanogenmod.org/#/c/37274/ - should fix the camera issue for good, making a build now myself, should be included in the next nightly

:cyclops:
[Verizon Samsung Galaxy S III] AdMire:
Anyone have issues with Reception? I made a phone call today to Well Fargo and I had to hang up after about 10 minutes because how terrible the connection was. Also, do you have to re-flash the modem/RPM every time you dirty flash an update? When I use the camera when it works, I can't swipe to the right to view the picture. Sorry if that has been addressed already.
[Verizon Samsung Galaxy S III] invisiblek:
Those with random reboots, please test:

http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130509-UNOFFICIAL-d2vzw-3.zip

No need to wipe data, just dirty flash it.

Let me know if its still crashing...
[Verizon Samsung Galaxy S III] m52 power!:
FYI I used to have huge issues with aosp until I restored to stock with Odin 100% factory image. Then I rerooted my device and installed aosp. Ever since I did this my phone has run everything buttery smooth. I think along the way 6 months ago there was some garbage code floating around that corrupted some system files and for whatever reason wouldn't go away, even with 100% clean installs.
[Verizon Samsung Galaxy S III] dspcap:
Interesting, what kinds of issues were you having?

Also, what instructions were you following to restore to stock?
[Verizon Samsung Galaxy S III] apacseven:
No, you do not need to reflash the modem or RPM each time your flash an AOSP based rom.
[Verizon Samsung Galaxy S III] BlazingGlory53:
So... I've been getting a funny issue lately... With the TTS engine, (in GPS specifically), it sounds sped up. My joke is it's the GPS Woman on Speed, but it gets slightly annoying... I was wondering what may have caused that?
[Verizon Samsung Galaxy S III] dvaderx:
If you do a 100% clean install, what files are left to be corrupted?
[Verizon Samsung Galaxy S III] NegativeOne:
I don't know - Often when I flash a new version I get lots of battery drain from cell standby. Flashing the radio + rpm seems to fix it.

Thanks invisiblek - haven't had a reboot since 5pm yesterday
[Verizon Samsung Galaxy S III] blueblur:
In a release made in early March, I didn't have GPS speech at all. That took some getting used to. I used "waze" recently and Samantha sounds 'great' - a bit startling at first since I'm used to no audio at all. My music player stops and then she talks and it goes back on. I can't tell if its sped up.

Are you hearing the chipmonks give you directions? :p
[Verizon Samsung Galaxy S III] toddrosenberger:
Flashed the 5/9 build. Did the camera fix and it's working but I'm having anther issue which I've had of and on with cm10 and cm 10.1. When I try to take a picture with flash on about half of the time or more it crashes the phone and I have to pull the battery to get it to boot again. Anyone else have this issue?
[Verizon Samsung Galaxy S III] Restola:
These camera issues should be fixed when the next nightly builds. It seems like they are reverting/fixing a bunch of stuff to try to get a stable RC for our phone.
[Verizon Samsung Galaxy S III] uberbdon:
After moving from Blur to Touchwiz and always preferring AOSP, I've come to the realization if I want AOSP I'm just going to have to buy a Nexus device. I haven't had as many problems as you have, but enough to make me not be able to rely on my phone to work when I need it most.
[Verizon Samsung Galaxy S III] cybertec69:
Just flashed the latest build, but a bunch of my apps will not update, I get this 920 error code in the play store, what gives.
[Verizon Samsung Galaxy S III] apacseven:
ROMs such as CM10.1 don't touch the modem/RPM information on the handset. You can observe this by noting the baseband version in About phone. If flashing modem/RPM is impacting battery drain then its coincidence, and simply a secondary or tertiary effect from rebooting or some other action.

I'm of course no expert, I'm just a casual user like yourself, and this is based on my gathered understanding of this process. If anyone has information to the contrary I'd love to hear it.
[Verizon Samsung Galaxy S III] cybertec69:
Fixed it, had to go to my Apps and clear Google play store data and download services.
[Verizon Samsung Galaxy S III] rockingondrums:
Can anyone tell me the last nightly that I can flash that doesn't have the mono audio bug? I can deal with the scene mode camera bug. Can't deal with messed up audio.
[Verizon Samsung Galaxy S III] CrimsinX:
Maps Force Close Issue

Has anyone noticed their Google maps being broken after an update to 10.1? In my crash report I see the issue is a java permissions problem preventing the service from starting. I have cleared data, reinstalled app, cleared dalvic, reflashed Rom/ gapps and nothing has helped get my maps back. Any advice or logs I can provide to get more help?

I'm currently on May 8, rc1 but am going to install the current nightly to fix the camera issue.

Thanks
[Verizon Samsung Galaxy S III] Restola:
It should be fixed in the 5/10 nightly.
[Verizon Samsung Galaxy S III] rockingondrums:
Cool. I flashed it and then flashed latest BMS 3.4 kernel, no camera or headphone audio channel issues here. Tested on PowerAmp, PlayerPro, Pandora, Spotify, UberHype, MediaMonkey beta, Now Playing (version 10 I think... Not the RC), and SoundCloud. I will inevitably use YouTube and Netflix later today, if I have any issues with those, I'll post. If not, I won't.
[Verizon Samsung Galaxy S III] RedRumy3:
I can confirm on my phone at least that audio and camera is now fixed with latest nightly. ^_^
[Verizon Samsung Galaxy S III] ryzilla23:
has anyone else experienced a poor battery life on the May nightlies?

I leave my phone idle at night, on wifi, and it is drained by morning. Thats only 7 hours! Not using it and the screen is off. It is typically around 75% before I leave it. This used to be no prob and would only go down about 10% all night.

I have seen cell standby and google services taking up a good amount of battery.

I don't have battery stats to post atm since I tried flashing kt474 kernel to help with this issue. I would prefer not to run a custom kernel on top of cm10.1 though.
[Verizon Samsung Galaxy S III] apacseven:
Get the free copy of BetterBatteryStats from the forums and see what service is causing the wakelock for Google Services. I had the same problem, and it turned out to be NetworkLocationLocator caused by a weather widget I had on my homescreen (was either HD Widgets or Beautiful Widgets, cant remember which). Turning off network location fixed it, but this was unacceptable to me and ended up removing the widget. Hope this helps.
[Verizon Samsung Galaxy S III] toddrosenberger:
5/10 running smooth, although when I take a pic with flash it still crashes the phone and I have to pull battery to reboot. But like I said this had been happening ever since cm 10. Pic without flash works fine, and sometimes it's ok with flash but most of the time crashes.