yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] whoopingchow:
I'm currently on the 20120911 CM10 Experimental build on my S3, and I've had a couple issues with my SD card. It's not recognized when I plug it in my computer, and even though I can access it through root explorers, I can't format it or otherwise access anything that's stored on it. Today, I figured I had had enough, so I formatted it through Recovery Mode, but it's still not recognized by my PC, and as such, I can't move the new nightlies, etc. onto the external SD. I moved it onto my internal storage and flashed it from there (I think that's somehow incorrect though...), and it seems to be okay-ish right now, but I'm just wondering if I'm the only with this issue.

Sorry for being noobish, any reply is much appreciated!

Noticed that too, figured it was just a product of my rage-flashing-a-recent-CM10-nightly
[Verizon Samsung Galaxy S III] juancaperez2000:
dont feel afraid is even around the world on a lot of devices

http://xdaforums.com/showthread.php?t=1895790
[Verizon Samsung Galaxy S III] tv31284:
I'm using the 9/18 build and I was wondering if anyone else was having a sign in error. When I go to the notification to sign into my account, it fails and says there was a problem communicating with Google servers. Google Now also isn't able to connect, saying there's a network error and to check my connection. The rest of the phone is working fine though. There is an internet connection as I'm able to browse the web, look up emails in the gmail app. I was on the original modem when this happened so I flashed the newest one from the OTA thinking it might help. but it didn't. I wiped data from the Google search app, rebooted and tried taking off my account and resigning in. None of it has helped. So before I wipe my phone and start anew, I was wondering if anyone else has the problem or suggestion. Or maybe it really is just Google Now's servers, as I only seem to get the error when I access Google Now.

Edit: just saw the response ahead of me. Glad its not just me.
[Verizon Samsung Galaxy S III] juancaperez2000:
please guys dont start to blame CM is not the rom is a Globlal Problem, reported in AOKP, G7 device, here, Australia Canada Maylasia so no more complain about "i just flash an then get this problem" thanks
[Verizon Samsung Galaxy S III] revolt1:
The only thing that's bothers me is the updated browser that the full screen option is not under labs and is under settings

But is not sticking after reboot
[Verizon Samsung Galaxy S III] the_gonz79:
Well, everything besides GoogleNow seems to be working so I guess we'll just have to deal with it!
[Verizon Samsung Galaxy S III] kls629:
i have been having a problem with "sign-in error" for my gmail account. never had this problem until tonight, anyone else?

when trying to sign in, i get "problem communicating with google services"

Sent from my Transformer Prime TF201
[Verizon Samsung Galaxy S III] juancaperez2000:
it is a google problem around the world just wait
[Verizon Samsung Galaxy S III] guthrien:
I'm having it on a TouchWiz ROM, it's a system thing.
[Verizon Samsung Galaxy S III] juancaperez2000:
Android Central reporting: http://www.androidcentral.com/some-users-experiencing-couldn-t-sign-error-their-devices
[Verizon Samsung Galaxy S III] FrostyOrDie:
Im on synergy and just got it. Switched into airplane mode then back and now all is well.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] revolt1:
that didn't work but thanks for the idea
[Verizon Samsung Galaxy S III] juancaperez2000:
FACEPALM, is not a system problem stop to blame roms is GOOOOGLE SERVERS REPORTED BY ANDROID POLICE AND ANDROID CENTRAL, what else do you want to know
[Verizon Samsung Galaxy S III] Nightwind Hawk:
I've noticed since flashing this ROM (9-17) that the "home" button doesn't always turn on the screen... most of the time it's fine, but sometimes it just doesn't respond and only the power button will turn it on to the lockscreen. Is that something that others have noticed or is it just me?
[Verizon Samsung Galaxy S III] goldsmitht:
I've noticed it, but just find it more annoying than problematic
[Verizon Samsung Galaxy S III] alee:
http://changelog.bbqdroid.org/#d2vzw/cm10/1348122289

Looks like 9/20 was mostly kernel optimizations dealing with caching. Been running it without any issues.
[Verizon Samsung Galaxy S III] jdubau55:
Had a SOD last night in class while on 9/19 and then this morning after flashing 9/20. Had to battery pull to remedy.
[Verizon Samsung Galaxy S III] tyrnight:
I got around the sign in problem, which I believe was caused by the new Google Maps Update, by going to settings/accounts/google then Maps and latitude, then by unchecking Enable Location history and then rechecking it so that you can "re-accept" the terms of service.

I also went to settings/location services and unchecked all the ticks and then rechecked them and selected agree to all the new terms of services.. and the Login error disappeared..

Hope this helps others..
[Verizon Samsung Galaxy S III] Imatoasta:
I'm on PA 2.13 and noticed this as well. I've read posts about it before in both threads. It just does it randomly. Weird.
[Verizon Samsung Galaxy S III] the_gonz79:
This has been around for a while from what I remember. I had the problem on every nightly I've installed (started around 9-2), including the current one. I usually double tap it and it works, but ya, still annoying.
[Verizon Samsung Galaxy S III] littleneutrino:
Just did a Clean install of 9/20 still no USB audio :( other than that, it is running much smoother and the flicker is completely gone (previous build was on was 9/18 and the flicker only occured during screen off.
[Verizon Samsung Galaxy S III] anothermbdusted:
anyone notice when your on the phone and on bluetooth and take a picture that the sound routes to the speaker phone then back to the bluetooth headset? I'm on build 9-18-2012 11:52PDT

I also got a few pictures on MMS that came to me in black and white.After i restarted phone I haven't had any problems at all.... everything seems to be working good and got Google wallet working np at all.. thanks for the hard work!!
[Verizon Samsung Galaxy S III] goldsmitht:
Data / Signal Drops

was running latest (9/17 and then 9/19) and started having serious data drops / signal loss -- 9/17 was a clean install, and will admit to just deleting data and dalvik before i flashed 9/19. but was having problems with 9/17 as well

was sitting in my house, hooked up to wifi, and couldn't send out a text message. was getting "no service available" but could see both bars and my wifi was active.

not sure if it is the regional wifi or not, but noticed i kept having to re-check the USA bubble. wasn't sticking for some reason. IF anyone knows a fix for this, would appreciate it, as i was loving the ROM, but hate not being able to use my phone
[Verizon Samsung Galaxy S III] rfmodeler:
wifi region isn't sticking for me either. I don't really use wifi much though since I have a crappy connection at home. Can't wait for Google Fiber to start spreading.
[Verizon Samsung Galaxy S III] Excessiveidling:
running 9-20-12 nightly so far so good. Came from clean rom 2.1. Did full wipe (formatting system, dalvik, etc)and the only real issues I've found are dead trigger messes up graphically...and no saving pictures to external sd card....all notifications work. Wifi works fine, 4g works fine...even gps locked on fine. Will give it a go for a day or two and see.

edit: one more bug found....volume control on phone calls. I know I've seen this mentioned before but don't recall a fix: upon calling someone (say my wife) the volume is rather loud until i turn it up a notch then back down. There IS no echo though according to my wife (and thats with the noise cancelling enabled NOT voice privacy enabled) Any ideas?
[Verizon Samsung Galaxy S III] ercDROID:
This phone doesn't pick up wifi signal very well at all. My router is in my gameroom. I never had a problem getting a full signal upstairs before till this phone. I usually only got 1 bar on this phone. Since I'll have this phone for a while, I decided to get the wifi extender from linksys yesterday. Very easy to set up and now I get full wifi signal upstairs. Cost was $70. Pleased so far.
[Verizon Samsung Galaxy S III] goldsmitht:
see, that is the bad thing, i was sitting across the room from my router. Was just curious why the region check wasn't sticking. And not just due to rebooting, but i would check it, then go back and it was unchecked again.
[Verizon Samsung Galaxy S III] yznhmr:
Is there a fix for this? "and no saving pictures to external sd card...."
[Verizon Samsung Galaxy S III] gf7z:
Lots of mixed information on this REAL problem. What I'm experiencing (under certain circumstances*) is that the phone -- while in an active call -- will NOT respond to dial pad touches -- that is, pass them on to the call you're connected to. This is whether it's voicemail (press '1' to listen to your messages) or a corporate conference call system ('enter your pass code, then press #').

This is not working consistently on ANY AOSP rom I've tried (AOKP or CM). It DOES work on stock.

I'd be real interested in knowing whether the folks having problems have set up their voicemail (or any other contact) to use 'pause' characters in the phone number, i.e. "*86,1111#" and if they use it.

I've found that IF I have setup a pause in my voicemail and call voicemail using it, then NO OTHER dial pad touches will register for that call or any subsequent calls. If I then reboot and dial voicemail manually, the dial pad DOES work and continues to work.

Can anyone else try this and verifiy?

(* those certain circumstances being, as described, having added a pause to a number and then used it.)
[Verizon Samsung Galaxy S III] kls629:
How do you enable noise cancelling? Have you tried a call on speakphone, my wife says there is a huge echo when i put speakerphone on

Also can you test video recorder volume, recorded volume is always extremely low on previous builds
[Verizon Samsung Galaxy S III] Excessiveidling:
Damn found a big bug... I indeed have my voice mail setup with a pause and then my pword set in and when I try to do any sort of menu features aka press 7 to delete a voice mail no response what so ever from the dial pad

---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------

While you're in the phone app go into its settings and scroll down and you can select noise canceling

---------- Post added at 02:21 PM ---------- Previous post was at 02:10 PM ----------

Have not tried speaker phone but unfortunately can confirm low video audio volume recording with today's nightly... So to sum up:

Recorded video audio low issue

No response from dial pad after pause

No saving pictures to external sd card by default on camera

And loud volume on phone call

---------- Post added at 02:39 PM ---------- Previous post was at 02:21 PM ----------

While this might be a kernel issue (I'm using the kernel that came with the official njghtly) I noticed down in my basement (which IS like a ferodine cage) I now only get 3g when before I was able to get 4g...while this isn't much of a concern since my wifi works fine... Still something to notice.... This is with the newest modem vrlg7
[Verizon Samsung Galaxy S III] rfmodeler:
I use G voice for my voicemail, so I'm not sure if I have this problem with voicemail. I can use the keypad for paying bills, checking cc balances, etc as of the 9/18 build. I'm currently on 9/20 and haven't tested it again.

I would recommend the VRLF2 modem unless G7 is giving you better coverage.
[Verizon Samsung Galaxy S III] MG386:
Thank you for figuring out this workaround. This is confirmed by me. As long as I don't use my automated pin entry using pause, I do have working touch tones in a call.
[Verizon Samsung Galaxy S III] gf7z:
And you didn't before?

If this is confirmed, can anyone suggest the best way to report it?
[Verizon Samsung Galaxy S III] littleneutrino:
I have not experienced this issue, only time i have used touch tones is when calling verzion for something and it worked without issue.

I use Gvoice as my voicemail carrier.
[Verizon Samsung Galaxy S III] MG386:
Correct. I've had the touch tone problems for weeks, and I've been clean flashing almost every nightly. I normally call VM using a shortcut on my home screen that dials *86 Pause, then dials my pin. after testing your idea several times, it looks confirmed to me that if you reboot and dont use the pause function in auto dialing, the touch tones work fine. as soon as pause is used, touch tones fail to transmit. I also tried listening on a different phone while i dialed numbers on my S3. same thing happens. I can hear the tones coming through on a fresh reboot, but as soon as i use pause, i can t hear tones on the other line.
[Verizon Samsung Galaxy S III] gf7z:
Thanks for checking this out and confirming!
[Verizon Samsung Galaxy S III] blu3poptart:
Hey everyone, I'm thinking about switching to this rom from stock. How's everything running? I've been trying to keep up with the thread but school has been keeping me busy. Any small or big bugs you'd like to point out? Thanks in advance!
[Verizon Samsung Galaxy S III] Excessiveidling:
Look at the last 10 posts and that should give you an idea
[Verizon Samsung Galaxy S III] mastamoon:
Had like 3 of 4 random SODs/reboots on my way home from work today. Just wiped caches, see what happens. 9/19 build.
[Verizon Samsung Galaxy S III] juancaperez2000:
I tottally forget which is the dial code for factory reset can somebody help me whit that please my gps on N20 is not working properly
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Which is the best nightly so far?

With the recent nightlies I've been experiencing bluetooth disconnects and crackling on the audio too.. Speaker sounds pretty bad
[Verizon Samsung Galaxy S III] TechSavvy2:
Which nightly are you on? There were merges to fix this a day or two ago. Don't know if it actually worked though, haven't checked.
[Verizon Samsung Galaxy S III] manywelps:
I'm rocking 9-15+leankernel 0.15, have not tried BT audio streaming though, even though I added it to my car a while ago, maybe I should test.

9-18 has BT audio streaming fixes though...
[Verizon Samsung Galaxy S III] Marcismo55:
This has not happened to me on the latest 9/20...might want to give this one a shot
[Verizon Samsung Galaxy S III] NegativeOne:
I had no problems with this under the first nightly ever, but on any of the new ones that I've tried, like 9/12, 9/16, 9/19 I'm having serious problems with the voice typing. It misses words and doesn't catch words. I am currently on a clean flash with this problem.

Anyone else?
[Verizon Samsung Galaxy S III] Zalithian:
*2767*3855#
[Verizon Samsung Galaxy S III] Nightwind Hawk:
Yes... I felt the voice recognizition isn't as good as Android usually is either.... Have not looked into it much more though.
[Verizon Samsung Galaxy S III] nfamouswun:
flashed. didnt work for me either.

clean install cm10 and gapps.

tried nfc. not working

flashed that nfc fix.

still not working.

any suggestions?
[Verizon Samsung Galaxy S III] jmill75:
I really want to come back to CM10, does anyone have a link to a nightly when the in call volume (LOUD) bug wasn't present? Only problem is if i remember correctly the echo was an issue back then?
[Verizon Samsung Galaxy S III] Marcismo55:
Flash a touchwiz ROM and enable nfc to get NFC back and then do a fresh install of CM10. That's worked for me in the past
[Verizon Samsung Galaxy S III] gf7z:
I saw the talk about a fix in the nightly of the 19th so that's what I tried. It was still broken.
[Verizon Samsung Galaxy S III] Trumps:
Still having issues with the phone locking in the middle of an SMS quick reply. (edit: to clarify, the phone locks, it doesn't lock up)

Bluetooth volume is abnormally low even if set high. I have to lower the volume, and then halfway down it starts blasting loudly. Once it lowers all the way, you can turn it back up just fine.
[Verizon Samsung Galaxy S III] whoopingchow:
I'm currently on the 20120911 CM10 Experimental build on my S3, and I've had a couple issues with my SD card. It's not recognized when I plug it in my computer, and even though I can access it through root explorers, I can't format it or otherwise access anything that's stored on it. Today, I figured I had had enough, so I formatted it through Recovery Mode, but it's still not recognized by my PC, and as such, I can't move the new nightlies, etc. onto the external SD. I moved it onto my internal storage and flashed it from there (I think that's somehow incorrect though...), and it seems to be okay-ish right now, but I'm just wondering if I'm the only with this issue.

Sorry for being noobish, any reply is much appreciated!
[Verizon Samsung Galaxy S III] rfmodeler:
I'm thinking this is a mic level problem. If you talk really loud it seems to work.
[Verizon Samsung Galaxy S III] Dcox28:
I flashed the nightly 9-20 build today and when I made a phone call and had them on speaker, the person I'm talking to says there is a horrible echo when they talk. I thought that got fixed?
[Verizon Samsung Galaxy S III] NegativeOne:
I dunno about that. I tried a voice recorder and the volume seems fine
[Verizon Samsung Galaxy S III] rgrossie:
I'm on 9/20, dirty over 9/18. No serious issues so far. No echo on calls, speakerphone ok. Data fine. NFC working. Small issue for me has to do with an app that uses the video camera (coach's eye)- the colors end up inverted, i.e what is blue looks red when I playback. It doesn't defeat the purpose of the app but it's annoying. I tried a permission fix, no go. Been this way since m1 I think. Also the app does not pick up volume on the video camera.

That is a minor annoyance though. Overall I'd say CM10 is in a great place so far, getting closer to being a permanent ROM, very stable. The improvements over the last month are remarkable. I'll keep flashing nightlies every couple of days as improvements are made.
[Verizon Samsung Galaxy S III] SymbioticGenius:
Been crack flashing since late august. Actually started with CM9 in late July, Went stock for a bit again, Then went to CM9, then CM 10 been crack flashing since. All Dirty, All the time. All Good. Great Job Devs Pretty much as stable as CM7 on my DX2. I honestly feel as though upgrading from CM9 to 10 has somehow helped me evade all these bugs. I've had minor issues like less bars, and the occasional random restart but otherwise been good. Next time you clean flashers update, Try and clean install CM9 first, then dirty flash to the next nightly, see if that helps any.

Just a theory.

P.S. Many thanks to the Devs that make all this possible
[Verizon Samsung Galaxy S III] jasonxlee01:
Speak into the top mic. It seems like for things like Google Now, its only using the top mic which is used for noise cancellation.
[Verizon Samsung Galaxy S III] Srambo217:
Are there still 3G data drops with this ROM?
[Verizon Samsung Galaxy S III] apacseven:
This has really been on a per-user basis. Some people claim to have problems, others swear its fine. There may be yet-unrealized contributing factors. Best bet is to install it and see how it goes.
[Verizon Samsung Galaxy S III] wingchun108tek:
Same here!..but i've been having this problem ever since moving to ASOP/AOKP ROMs. 90% percent of the time the person will complain of hearing their own echo when I have them on speaker. I've posted this numerous time but nobody seems to know the reason. I never had this issue on any of the TW ROM's running ICS.
[Verizon Samsung Galaxy S III] TechSavvy2:
Everybody "knows" the reason, but nobody has a solution for you. Its a very well known bug. Only hits select users also though. I don't have the issue at all. Clean flash for me took care of things.
[Verizon Samsung Galaxy S III] maniac2k:
For the voice search app, if you delete the one out of the system/app dir and reinstall it from market, its a different one and works a lot better. Also disable google voice typing in language settings.
[Verizon Samsung Galaxy S III] NegativeOne:
But Google voice typing worked before and it worked great - better than voice search had ever worked!

Also, in response to an earlier post, speaking into the top microphone seems to help a lot. However, the top microphone is clearly not as sensitive so it's not all that practical. I wonder what happened and weather another night we could fix it to use the normal microphone again.
[Verizon Samsung Galaxy S III] ssmaster:
I keep getting a 404 error good sirs.

Where art thou my rom?
[Verizon Samsung Galaxy S III] NegativeOne:
Don't make useless posts
[Verizon Samsung Galaxy S III] ballpoint:
new nighty wont dl ?

is it just me goo manager or stright dl ?
[Verizon Samsung Galaxy S III] elreydenj:
I have the dreaded echo issue as well. When you say clean flash, did you wipe data, cache, and dalvik? Or did you format system and format internal sd as well? Everything is solid besides the horrible echo the person on the other end hears of themselves.
[Verizon Samsung Galaxy S III] WhammyDroid:
9/21 nightly does not exist at the moment.
[Verizon Samsung Galaxy S III] NegativeOne:
I clean flashed to what I have and I still have the issue ; don't hold your breath
[Verizon Samsung Galaxy S III] C0ntr0lfr33k:
I reset the headunit and it's working now. Thanks for the advice. :good:
[Verizon Samsung Galaxy S III] Version_3:
Followup on my camera freezing issues.

After getting a logcat for the unofficial bug tracker, I looked at it and figured out that the SmartStay app from the market was causing the issue. When it would scan the front camera, it caused the camera app to lock up. I've uninstalled it, rebooted, and now I took pictures, tapped to focus, and after 2 minutes, still no lock-up
[Verizon Samsung Galaxy S III] scriz:
NFC isn't working for me. Meh.
[Verizon Samsung Galaxy S III] alee:
Grab 9/21 off of Jenkins...

http://jenkins.cyanogenmod.com/job/android/8454/

Working fine for me.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Is this legit?
[Verizon Samsung Galaxy S III] rfmodeler:
The domain "cyanogenmod.com" is in the link, so I would assume so.
[Verizon Samsung Galaxy S III] alee:
Yes. Jenkins is what actually builds the nightlies.
[Verizon Samsung Galaxy S III] JWorth:
Is the native hot spot (or foxfi) working on the latest? 920 or 921?

Thanks
[Verizon Samsung Galaxy S III] NegativeOne:
I reported the microphone issue here. Please vote for it if you're experiencing it to get it some notice:

http://code.google.com/p/d2vzw-cm10-bugs/issues/detail?id=74&thanks=74&ts=1348227011

This is regarding a few things:

1) Echo of death while on speaker

2) Bad performance with voice recognition

3) Low recording volume.

Because it looks like in the september nightlies d2vzw is using the wrong microphone for these features.
[Verizon Samsung Galaxy S III] Dcox28:
People I talk to on speaker hear a horrible echo, so I went to your link and submitted my vote
[Verizon Samsung Galaxy S III] nfamouswun:
reflashed jellywiz, clean installed cm10 9-20

still no go on nfc

i hit the check mark to enable, then it grays out
[Verizon Samsung Galaxy S III] psycho_asylum:
After updating to today's nightly, I'm having a number of issues. My phone slowed down to an absolute crawl after a few hours and then rebooted itself. Also, for some reason, Superuser will not remember allowed apps. If I open Root Explorer, it asks, allow, close, reopen, asks again. It's doing this for anything that asks for root including TiBackup and WiFi Tether.

edit: I should mention that I've dirty flashed over previous nightlies for quite awhile and have never had an issue.
[Verizon Samsung Galaxy S III] chetqwerty:
+1, on the subject i think SuperSU is better option now anyway.
[Verizon Samsung Galaxy S III] mwep:
http://goo.im/devs/cm/d2vzw/nightly/cm-10-20120921-NIGHTLY-d2vzw.zip

Nevermind, appears to be incomplete on Goo
[Verizon Samsung Galaxy S III] patt2k:
Hey guys wanted to ask i've been betweem the touchwiz and the cm10 roms , my microphone volume is VERY VERY low is there any fix for that? of course volume is at full