yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
If you don't have something that would fit this scenario, please post in Q&A

Bug:

I'm finding trouble with x,y,z

Don't stray from that, simply state the bug.

Prior to giving info, search to make sure it hasn't already been posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dizzy21:
Is there a chance of getting wifi calling with this?.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Please see post #1201
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
Home button problem has been around for a while and nearly everyone knows about it. It's being worked on and the temp fix is reboot your device.

Chrome is laggy. Just something we've gotta deal with for now. The stock browser works fine.

Search the thread before asking questions in the future. This is a development thread and there is a dedicated thread for bugs in q&a.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LegobrandonCP:
Thanks for the help. Apologies for not searching. I'm still a nobb at this, will definitely research before next time.

Do you have a answer for the camera problem (photoshphere, tap to focus lag)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Don't be so hard on yourself. I wouldn't call you a nobb. You're more like a noob!

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
I get the camera lag on occasion, but not always. I have no use for or desire to use photosphere so I don't have an answer for you there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I get the focus lag across all ROMs sometimes. Found out that it was left on continuous picture focus mode so I switched to auto. Works fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Anybody notice that we don't have to disable hw overlays anymore?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I bumped from 384 to 486. After, I didn't encounter the audio hiccups with power/lockscreen, but the problem was intermittent to begin with. I'll keep an ear on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Alright yea should be intermittent because cpu is not always on same load.

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The recovery is not part of the CM package. You still have to install it manually. Check out clockworkmod.com/rommanager for the new version. It is a .img, not a flashable .zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
That's what I thought. So why the commits to the CM git then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
CWM Recovery is developed as part of CyanogenMod but they would never force you to use their recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Some devices require the recovery to be built into the kernel. Those kinds of commits are of no concern to you for this device considering we have separate partitions for kernel and recovery. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Google apps only installs Photosphere on Nexus models. You can change the updater script in gapps to make it install on the s3 but its buggy as hell.

It is also useless and is only cool to try then is just a waste of space in my opinion
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I don't take the sdcard out of my phone for normal transfers, so it doesn't matter too much what format it's in; it's network transparent. It's easier for me to just use a mix of adb, AirDroid, Gmail, FTPserver, rsync, and dropbox via wireless-G, than taking the case off and fumbling with a tiny card (now that usb mass storage is deprecated vs the FAIL that is MTP (especially on linux))

(One additional feature that would be nice to see added to CM at some point is a "Format ExtSdCard" option under Settings > Storage, which prompts you for ext4, fat32, or f2fs. That way you don't need linux, or another app, to format it in the first place. (I only see mkfs.ext2 and vfat on the phone currently)). This feature request is probably already in jira... and if not I'll add it.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
I mostly don't know what I'm talking about, but what about using terminal/busybox to format the card?

I'm interested in ext4 file system, because what is the point of having any ntfs partitions if you no longer have any windows machines.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
On the 3/8 nightly and noticed hitting the home button while in a dock tripping car mode went to my car home app not the normal home. Looks like they fixed that bug recently & car home stuff is working as it use to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boss Daddy:
I have a noob question, so what happened to the recovery options when you choose "reboot" when holding down the power button? It doesn't list rebooting into a recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Search is your friend. It's still there, just not by default, gotta activate a developer setting.

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk

---------- Post added at 05:32 PM ---------- Previous post was at 05:25 PM ----------

Not a huge deal, but anybody knows if the exposure bug/lack of support is being worked on? Is it a driver issue? I could be tempted to try and debug that as an intro to Android Os dev, if it's not a driver issue.

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Horribly stuttering Bluetooth

My Bluetooth audio streaming is suddenly horrible.

The 0309 build seemed to be working OK. I bumped up the lowest under clock to see if I could get rid of the lock screen stutter.

The next day, all streaming apps stutter audio very badly. I flashed up to latest, no wipe, and still bad. Deleted pairing, re-paired. Still stutters.

Ideas? I suppose I could full wipe, but that doesn't seem like a great option since it was working prior.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Same with mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Dont report unless u have full wipe is my suggestion... Nothing bt has been committed i think...

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pbwizkid:
While i agree that search is your friend (its how i found this answer as well) i also like to share what i have found. So all you have to do is go to about phone and tap the build number 7 times and it will tell you you are now a developer. Developer options will now show up in system setting and you can turn it on there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
CM 10 vs 10.1 stability

I posted this in the Q&A thread but only 1 person responded.

Were the latest nightlies of CM10.0 (most recent is December 16, 2012) more stable than the latest current nightlies of CM10.1?

From reading in these threads it seems the most common bugs on 10.1 are home screen button opens recent apps, no wifi tethering over LTE, and bluetooth issues.

Did the December 16, 2012 CM10.0 nightly have the same issues? Or was it more stable?

I don't really care about the new features in 10.1. I just want a stable AOSP experience. Considering whether the 12/16 CM10.0 nightly might be a better choice.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Can't comment about CM10 since I haven't used it on this phone, but the home button bug and wifi tethering have been fixed for about a week. I think there have been improvements in Bluetooth, but I'm not sure since I don't use that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I have no such issues w/0310, so it must be the 0311 that introduced the stutter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
It is 3/11 that introduced it. Pandora stutters everytime I touch the screen, as does Play Music. PowerAMP does not suffer from the issue (and does not stream music).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
My personal opinion is that the latest 10.0s were more stable than 10.1s.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Agreed. I am running the latest 10.0 M1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I also just formatted my external SD to ext4, and copied a bunch of music into it. A lot of my audio files weren't playing and carbon/Ti couldn't backup data to extSD, which I think was due to to file permission problems. After I recursively set permissions for all files to 666 and directories to 777, all was working fine. I guess in fat32, there wasn't any permission issues.

One issue I've come across is that now I can't write onto extSD from desktop (ubuntu) when connected via MTP. Can anyone else confirm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Black Adam:
I have been having the exact same problem since flashing the 3/11 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Look at changelog... No bt or audio commits in 3-11 therefore dirty flashing caused it. I full wiped my phone and no issues so far...

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I agree, I am still on 3/11 and I played music using Google Music the last couple hours using bluetooth on my car radio while playing ingress. Before that, I spent hours using my bluetooth headset at work. Either dirty flash, to much UV, or not using stock kernel... :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
And why do you think that is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Most likely that this version of the OS was not built for this device. That would be my guess
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Are you noticing features that worked in 10 but not in 10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Idk imo 10.1 is loads awesomer... But that's just me lol

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Yeah I love 10.1, phone runs super smooth and I'm getting almost 29 hours on one charge, haven't had a feature not work yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
Quick question in 4.2.2 when choose reboot, I do not get option as how to reboot -> Download, Recovery, Reboot. Is that the way it is now or I am missing some settings? Please, assist on this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Look in Developer Options. Best way to learn this stuff is to figure it out yourself through research. Unfortunately, prepare to be flamed for posting that question. Maybe the community will have mercy ha-ha maybe not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
Thnx, I did not know where to look for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
It's been asked about a dozen times in the past dozen pages or so of this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amarpatel:
I've been using CM10.1 for awhile now and I haven't been able to get voice search to work. every time I try to open it I get "unfortunately google search has stopped". Can't find "google voice search" in the apps menu to remove it.

I just tried a clean flash with the 3/13 nightly and the 3/01 Gapps. wiped cache, data, system, and cleared the dalvik cache.

same issue.

I've tried everything I can think of. Does anyone have any ideas on what I should do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Had a similar problem before. Try a different lower Gapps version. Then check the play store for any update on google search. It worked on mine. Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
This has happened to me using the 03/01 gapps PRIOR to doing the market update, just clear data for the market, reboot, update Google Search and you should be good to go
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
This has been well covered and you would have found it easily with a search if you had tried. You can enable it in developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
I'm gonna go with there were a solid 5+ months of development on 10.0 and we're only at about half that time for 10.1. 10.1 has been remarkably stable and very quickly became a daily driver after the code was merged but still needs a lot before it is truly stable.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
The question was around "stability". I took that to mean use of all aspects of the device, not just a random-reboot type scenario.

button shortpress=longpress requiring reboot (recently worked around), substantial BT streaming issues, (for a full 6+ weeks, and has recently started stuttering again, but as of today's build is working again for me), speakerphone volume issues, phone volume issues, data connectivity issues, Camera issues(both camera (low-res pic defaults) and video(warp-o-vision)).

All that being said, I'm on 10.1 nightlies. I never flashed back to 10. In fact, I need to check my sig. Even my nook color is on 10.1.

I don't recommend to anyone else that is not a flash addict/developer to not use 10.1. I generally assume they need stable devices over bleeding edge features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
10.1/4.2.2 has recently become, and currently is, hands down, the best OS that there is for our device. The speed and smoothness are unmatched, even as it continues to mature. It is a pleasure to drive. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So which nightly you are currently using which makes you say this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kb9nvh:
I'm now on 03-14 and the only thing that doesn't work for me is slingplayer very 1.0. Not sure when it stopped put maybe when 4.2 hit. I'm afraid to switch back to 10.0 due to the directory structure of 10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
We have a winner!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
Try reading the entire thread. If you want to run nightlies, its your responsibility to educate yourself on what changes every night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
There are 12234 posts in this thread. Assuming each post is 15 words on average (low bound), that amounts to 183510 words. According to wikipedia, average adult read 250-300 words per minute. Taking the best case of 300 words per minute, that's 10 hours of non-stop reading.

And since there are more than 15 words in the average post and the average read speed refers to reading a book instead of random shoutouts, I think we can up that to 20 hours easy.

So I don't think it's feasible to read the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Lol. Yeah, maybe he meant searching the entire thread? Or reading just the last few pages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Bluetooth, stuttering audio

Stuttering audio is back. Amazon player started up on BT. Didn't hear stuttering. Stopped, played pandora. Audio stutter present. Pause pandora and play, and stutter is gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
the 13th. It runs perfectly with everything I do, including A2DP while streaming over BT, at the same time as GPS tracking. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Since the past 2 nightlies, I've noticed there is some stuttering when a sound notification comes in while playing music. IIRC it was smooth before. Anyone else can confirm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
The battery life has been great for me on the latest nightly. I have lost only 1% in the last 3 - 4 hrs. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
I'm experiencing this too with the last 3 builds, IIRC.

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

Pandora keeps crashing even if it's not running in the background. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Just curious: do you have the Google Wi-fi Location turned on or off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
It's off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
My WiFi connection has been going grey every few hours. If I turn WiFi on then off it works again. This started happening a few days ago. My laptop stays connected without issue and I haven't changed my wireless network. Anybody else seeing this running nightly builds, or is this one just me? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Yup, I have the same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I don't believe your phone is losing internet connection, just the persistent connection to Google, if it is just greying. Try accessing some web page, or stream some music station next time you notice it.

If you still have internet access, start going through gmail, talk, g+ and see if they are receiving data or if that gets your connection blue again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
WIFI

Same issue here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
FWIW, just on a whim I double checked my WiFi zone setting and it had changed to Europe somehow. I moved it back to United States and now mine seems to be more consistent YMMV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Same thing with mine - somehow got switched to Europe on an update I guess. Wi-Fi is much more stable now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
i see this as well. right now as a matter of fact. though it went the past 4 or 5 days fine and then all of a sudden swype lag. it comes and goes for me. anyone figure out why or if there was a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
well i changed the governer from conservative/row to interactive/row and the lag went away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I've had three hard freezes related to calling in the last two days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Which nightly are you using? And did u dirty flash or factory reset?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Stutter after notification sound while playing music is FIXED in the 3/17 build! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deep Search:
I have clean flashed this rom the last couple of nightlies and also have been experiencing hard freezes when hanging up a phone call. I also think it if the other side hangs up first, but that could just be my imagination.

EDIT: I am also using TWRP to flash and sometime I underclock to 1350 in attempt to save some battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
0314 and 0315. Dirty. I see another user posting here with more detail, clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
On 0315 NIGHTLY, I have just experienced phone freeze-up during a call. I had to pull battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
People there is never any need to pull the battery, holding power for ten seconds does the trick.

Sent from my thumbs to your brain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdotagain:
Same here. Call freezes. Unable to hang up as screen is frozen. Had to hold power and home to reset phone. On 3-15 nightly and 3-17 nightly. Dirty flashed both.

Edit: 3-15 and 3-16. Haven't flashed 3-17 yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Try without the undervolting/underclocking.

For the others getting freezes, are you using stock voltages?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Is anyone having the issue where the thumbnail of HD videos are skewed in color or don't show at all in the gallery app or third party app?

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Never touched that part so assuming stock voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Ok, just throwing that out there, as it can cause weird problems ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I had this happen to me at the end of a call on the 16th nightly. Rebooted the phone and hasn't happened again, I am on the 17th now. Stock settings, did not flash anything custom. Each nightly is updated using cmupdater... If it happens again I am going to a full wipe... :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eAiur:
I got my first call related freeze this morning, running the March 14 nightly, flashing it through CyanDelta. Haven't touched the voltages at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deep Search:
Okay, I clean flashed nightly 3/17 and after the setting it up and signing in to everything, I placed a call and laid the phone face up on my desk face up and it hung up with out a problem. I made a second call, but this time I place my finger over the proximity sensor causing the screen to sleep and then removed my finger so it would wake and I was not able to hang up after that and had to hold the power button down to reset. after the reset I have placed seven to eight calls and during all of them toggled the proximity sensor and have not had the problem since. I will keep testing to see, but as of know a reset is looking like a promising solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
All stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Is everyone with freezes using gapps 3/1/13?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12th Planet:
It's not the gapps, it's the rom current nightlies. I'm running M2, and I'm not getting an errors. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I'm running the 17th ROM and get no errors or freezes of any kind. Runs great for me. Switching to Task's new build now with the updated kernel... Sweet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Do not use the latest nightly the phone would not boot past the Samsung bootloader:/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
Did you flash a kernel? If you did try flashing just the rom and see if you can boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yea I think that's to blame I guess I'll wait cause I'm not going back to a yellow tinted screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
It works for me but I updated recovery.img and boot.img.

It includes a 3.4 kernel now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Latest CM nightly is on updated 3.4.36 kernel as well.

---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------

Justin, I flashed it with KT kernel and it will not boot. CM has moved on to 3.4 and boots perfectly without custom kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deep Search:
Just flashed 3/18 clean install and made some calls to see if it would freeze up on hang up and have not had the problem yet after 4+ calls. For anyone that was wondering...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Bump

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Yes I've had that issue for about 6 weeks. Haven't found a resolution but its been brought up a few times in this thread...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gd1147:
I did, and now stuck only being able to boot to recovery. Have tried to load 3/16 from recovery but keeps going back to recovery on reboot. Is there something else I can try without having to wipe everything?