yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
just tested mine and it works with my desktop speakers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mph122074:
Neverends...

I bet you would have 4000 thanks if we could find the thanks button where your arrow points...lol :laugh:

(your signature arrow is pointing the wrong way)

Never mind... I see in the new XDA they moved the button... My bad...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
I'm still getting the occasional flicker here, not just when changing screen orientation either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
You can dirtyflash upgrade until you run into a problem and/or want to report a bug, in which case you should wipe for a clean slate and then reinstall the ROM, apps, & settings.

Even if everything seems like smooth sailing, I like to do a clean install every couple weeks when I have the extra time. I've dirtyflashed all of the nightlies since the preview without a problem, but i'll probably do a clean wipe regardless on Sunday.

EDIT: Loving this new "Whisperer" ringtone...

EDIT2: Has anyone yet heard a fellow CM user's ringtone go off in public and exchanged headnods? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Just installed 8/24 build. The LTE toggle doesn't seem to switch LTE off: can anyone confirm so we can have this in "known bugs" list?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
It's not a bug. AT&T phones can't toggle LTE on or off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
Yea, thats what I heard, I also heard that you can change your APN to get it to go on and off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I flashed this new boot animation and it makes my phone reboot twice when I reboot it. Anyone else having this issue with it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
It automatically reboots the phone back into recovery at the end of the flash to make the change take effect. Reboot system like normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I understand that. But when I am not in recovery and just do a reboot from the home screen, it will boot to the new logo, then go to a black screen then reboot again. I've reflashed the 8/24 build and put the logo from page 11 on this thread back on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
I'm not having this issue, just reboots normally for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mike21pr:
Anyone had this happen? My launcher in time starts to display the icons leaving a blank spot in the bottom instead of taking all the screen like normal

Pic attached. Reboot fixes this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
That's weird. I haven't had any problem with it. Try searching through that thread to see what people are saying. Could be a bad download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
I'm using Apex and it happened to me a few times on some of the older builds - Haven't had it happen on 8.24 yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moah9998:
awsome this is the best rom!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
before i flashed cm10 my phone showed to get 4g but now that i flashed cm10 i dont have 4g anymore it always says H....also i am having an issue where in the main sms window i can see the newest sms from each person but when i go into the threads themselves i cant see any recent sms's...idk why this started happening...it started before i flashed 8/24....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rsxy:
You have to manually change the network mode under Mobile Networks-Network Mode to select the LTE option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Does anyone else get screen flickering when switching b/w portrait and landscape?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
here

here are the settings i have. the text message thing is a way bigger issue than the 4g though....i cant fully read any text that i have received in the last 12 hours since once i go into the individual sms threads it doesnt show sms from a certain point in time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meaintsmart:
Yes, it happens to me, and it was reported a few pages back too.

I have a questionabout dirty flashing, is it okay to only wipe dalvic? And not cache? Because from my past experience with aokp, I flashed from nandroid, then wiped cache and dalvic, then upgraded and I was logged out of my Google account and couldn't access any Google apps like gmail or even the play store. It would close upon opening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
Do you get LTE in your area? On stock HSPA+ shows up as 4G. On stock it will say 4G LTE when you have 4G but on here or will just say 4G.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
all i ever get is the H....and i am pretty sure there is lte here....

the text thing is really getting annoying...it also seems to not be putting the newest threads at the top either.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Might want to double and triple check that there is LTE in your area. I thought for the longest time that I had LTE, and only thanks to this ROM did I find that I didn't. If you don't leave near a rather large city, you probably don't have it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mfratella:
I'm on Ultimatum right now and love it...very swift. Did anyone else move from Ultimatum to the nightlies? How does it compare?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
no one has any ideas about the sms issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecoach1999:
+1

I did the same thing yesterday. I spend over an hour trying to LTE only to find out I'm just outside Rogers coverage area. Doh!!!!!

Not sent from my iPad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
Flash gapps immediately after upgrading.

Sent from my Motorola DynaTAC 8000X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Anyone know how to get Google Voice working? When I try to set my voicemail service (in Call settings) to Google Voice, it says "Couldn't retrieve and save current forwarding number settings. Switch to the new provider anyway?"

I push YES but it then fails with "Couldn't change the forwarding number".

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
here is a map of my area....i live in Little Rock which is right where the 3 interstates merge in the middle

it looks like i should get 4g....so i guess that would be hspa+ right?

anyway....back to the sms issue....it seems it is also not showing the messages i send, but they are being sent
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
this is a common thing...there is a code that you can use to switch it...i am unsure of it at this moment but i think that it is in the preview thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
I had the same problem. Go to the Google voice site and get your Google voice number, then manually input it phone>menu>forwarding number for unanswered/busy. Then hit activate Google voice for voicemail from the site, it'll spit out a number, copy and paste this number to your dialer, dial it and... voila. Google voice.

Hope it works for you, its a common issue. Maybe OP can add it to FAQ or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
Badass Boot animation!

http://xdaforums.com/showthread.php?t=1833939
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
My Home Screen! In case your wondering where my drawer button is, its invisible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Are you with Att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tenorntex:
I had that problem before. Just uninstall Google voice then reinstall it. Sign in and reconfigure your settings.that worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
There is a bunch of camera updates in the pipeline for tonight's nightly....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Good to see you over here, tenorntex.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
ive merged those into todays build for aokp. i have seen any difference yet. were you guys over here getting camera crashes or something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeeSlivers:
Has there been a way to permanently enable LTE for either CM10 or AOKP? having to *#*#*4636*#* every time, or create a shortcut is garbage. I'm almost feeling stock root coming back. (Wrong Thread but same sh!t).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Haven't had any camera crashes but an occasional reboot after a phone call. Also noticed that disable HW overlay doesn't stick especially if I reboot but the .5 transition scales stick with no problem.

On another note, any news on the CWM date issue?

Sent from my i747 running CM10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yes I am.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Strange, light flow was working perfectly on 8/22 nightly, not working on 8/24. Anyone else experience this? I did a full wipe when flashing 8/24 too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
You have to do the initial settings over again. You don't have to set the notifications but toggling accessibility and enabling the Samsung s3 root mode even if it's already good to go do it again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
camera hasn't been giving me any trouble, i use it quite a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
To get Google Voice to work properly on your AT&T Galaxy S3, do the following:

If you have already tried going through Google voice setup and it failed...

First try setting call forwarding by going to dialer... Menu... Settings.... Call forwarding.... Leave first entry disabled and set next three to Google Voice number... If you get a forwarding failed or network connection error then follow these dteps

1. Uninstall Google Voice if you have it installed

2. Go to your dialer and enter ##004# send. Next

3. Reboot

4. Go to dialer and enter *004*1"10 digit G-voice number"# and hit send

***** If the above does not work and you get any error codes regarding "invalid code","network error", or "mmi error".... Call the at&t tech support and tell them that when your attempt to forward calls you get a network error.... Have him/her reprovision your phone.... After he/she reprovisions you can set forwarding options 2,3, and 4 to your Google voice number by going to your dialer, hitting menu, and going to "other call setting" and "call forwarding" then set forward when, busy, unanswered, and unreachable to your Google voice number, next back out and go to "voicemail", leave carrier on "My Carrier" click setup, and change number to your Google voice number.

That's it.... it works and you don't have to do this again, even after a full wipe

After you do this once you will not have to do it again.... Even after a full wipe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
^ Did I not post a way easier and confirmed fix already...

The method I explained manually forces it. But hey, have fun calling support lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Geo411m:
First off I'm new to the Galaxy S3 (just got it a few hours ago) so forgive me if this is a known bug but is anyone else having issues with Wifi not connecting after a reboot? It won't work till I toggle wifi off and on again. It works flawless on my galaxy nexus and nexus 7 so I'm wondering if it's a galaxy s3 bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
This is not a competition... the method you mentioned is in the first 4 steps ... I simply provided all the codes. now as for calling support, if you research the issue there are S3's on AT&T that will not allow you to use Google's activation codes and will throw and MMI code error and/or Network Failure dialog. These phones have for whatever lost provisioning and need to be re-provisions. after doing this once the info sticks and this does not need to be repeated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigblue95z:
Wipe data/factory reset, wipe cache, wipe dalvik, flash cm10. Fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
i noticed this also..but it doesnt happen all the time..but every once in a while..if your connected to wifi, then reboot for whatever reason..once booted back up it is disconnected from wifi and i will have to re enter my wifi password..strange but like i said, only every once in a while
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
I work at best buy mobile, have helped 20+ people not once hit issues like youre saying.

It not a matter of competition cause I could care less if it made peoples phones explode. Just easier.

And with that, have a good day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] musa13:
I had the same issue few times after flashing a new version. It was a bad flash every time. After new flash ( this time I did 3xwipe of data, system, cache and delvik before flashing) Wi-Fi was working after every reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigblue95z:
Could be the cm10 kernel. I'm on faux and haven't had any issues I can remember. Just a thought. But I'm on an older build though, 8/14. Been so solid, I don't want to update. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Testing this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
The method you posted may work very well for newly activated (and provisioned) phones, and devices that are not rooted however as I mentioned some people may get a forwarding failed or network connection error when trying to manually input the forwarding numbers... The next step is what I posted.... If the Google activation code fails as well and you get an MMI error code then you have to get phone re provisioned to allow you to manual input forwarding numbers via settings.

MMI codes which are carrier exclusive i.e. call forwarding don't always work with CM dialers.

Which leads me to my final point that, if the method does not work, then you need to re provision your phone from the carriers side (something I personally encountered and researched.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
This did not work for me when someone calls my voicemail it says please try again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Check call forwarding under phone settings... Is your Google voice number in the last three items in forwarding menu... If not then...

Try the mmi codes I posted... First deactivate then reactivate and check forwarding numbers... That might work.... Leave voicemail on carrier and not Google voice....

If that fails and you get mmi error call at&t to re provision... then manually update forwarding under phone settings and change voicemail number under dialer menu.... Settings... voicemail... Setup
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
The *004*<insertGVNumberHere># AT&T code works for me, and is the only way I've gotten GoogleVoice to work on my S3 with either CM10's dialer OR TouchWiz's. I have to do this after every clean rom install, and does indeed work. After entering the code, the Dialer settings will still show "My carrier" for Voicemail, though, but the actual forwarding #s are correct, and callers will ring through to GV after 60 seconds.

(fwiw, I didn't need to use the dial code for GV with CM9 on my Captivate. Not sure what's up. Something 4G-related?)

(fwiw2, having Visual Voicemail on your ATT account or not doesn't matter. I had this problem before and after I had that feature removed when troubleshooting)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] urbanboy:
Screen is still flickering with the new update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Well, on 8/24 nightly, your method DID NOT WORK.

I am going to try his method of calling support tmw and will report back if it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CheesyNutz:
just got my sgs3 today rooted and installed the BEAN ! lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
When I put my phone on Speaker during a call...the person on the other side tells me that they can hear themselves. Does anyone else have this issue? seems like noise cancellation is broken or something...(on my phone atleast :( )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Same issue here. Mom noticed it the other day :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
If you also read the flow light help section it talks about letting the application run in the background till they find a way to fix the service running as system service or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Tried that mmi and it says it can't call forward.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Next nightly is building: http://jenkins.cyanogenmod.com/job/android/6802/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
so you are having the same problem I had.. All you need to do is call AT&T and tell them that when you try to forward your phone numbers it fails and says network error. the CS will tell you to power of your phone... the the cs will reprovision it and when you turn it on you just go to dialer and manually set the forwarding numbers manually to your google voice number
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
It's a know issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
New Build 8-25​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Heck yes! Can't wait. Tried a TW ROM and its so bad I hate it lol

---------- Post added at 02:58 AM ---------- Previous post was at 02:50 AM ----------

Is yours taking forever?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Nope
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
mine is installed and ready to go!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Took 11 minutes for me on a 30 meg down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Google Now force closing on 8-25. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Celidonius:
Me too. Dirty flashed though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Mine is crashing as well, and I too dirty flashed... anyone do clean install and can report on this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I did a clean install and I'm getting no sounds.

Edit: Google now force losing here also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
ATTENTION: Before anyone installs this build please be warned

This build has NO SOUND

no ringtones, no notifications, no pandora, no power amp

Also Google Now, You tube, Asphalt 7 and some other apps FC

Again NOT A SINGLE SOUND WILL COME OUT OF THE SPEAKERS.

INSTALL AT YOUR OWN RISK​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I reflashed 8/24 and sound is back. Really weird. YouTube doesn't load either on 8/25.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Me too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatg:
What's the deal with these night lies. The latest preview build has been working fantastic for me and I've been able to get 1day and 15 hours battery life out of the preview build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
I'm gonna assume(guess) this is cuz a jb for the tmo version was leaked, and the drivers were updated, but only on the tmo device, tho changes to the jellybean branch dependant on the drivers were pushed out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
The cycle is preview build, then nightly, then release candidate, and final
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Ya but that was for touchwiz so I doubt the leak was merged into cm10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
But the device driver files (you know, the ones that aren't included with the git source, you have to grab them from your device, or a compiled nightly) have probably been updated, and the source reflected the changes, but they weren't included in the ATT build, I didn't see anything about no sound on the tmo forums.

Just a possible guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Just so you know if you flash the latest update you will have to fully wipe your device to revert back to a previous update if you did not back up sounds no longer work after dirty flashing back to 8/24
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
good post my friend!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
Thanks guys! Giving it a go now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
if this is the new/official thread, perhaps mods should now lock the other two.

or should we all begin checking 3 threads now for q&a/bug confirmations? :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chinyuk:
Google Voice Search Speak Out not working

I know when I first jumped on the CM10 bandwagon, I believe it is either 8/10 or 8/14 build, the first one that support AD2P, when performing a google voice search for item that can speak out, it would. However, I think since the 8/18 build and onward, it won't work. Something as simple as "what is the weather like today", it used to speak out the result, but now just show the result. Any idea. I having done a full wipe since 8/14 though. Any other people experiencing this as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
This is for the nightly... if you are running a preview build you would look at the preview build thread... as for the Q&A thread, its in Q&A section and separate from dev thread. I have no problems with the ROM being discussed here in this thread however its up to our mods to determine what should happen with the others
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
That specific command works for me (talk back and all) along with "How tall is Kobe Bryant?", and "how many championships did Michael Jordan win?" ... I get a voice response to all three questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
Installed and working great! One issue though, I flashed the gapps as instructed but it did not seem to install all of them (gmail and google talk installed). Missing the others. Should I try to reflash the apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Any app that can be found on Google play is not in gapps.... So maps, voice, street view all need to be downloaded from playstore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I believe the later gapps only installs the frameworks necessary to support the actual google apps themselves along with the Play Store. The rest of them get downloaded from the market to keep the file size down. It also helps ensure you have the latest apps as they get updated more frequently than the frameworks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
Gotcha! Thanks. I went ahead and got the from the store. Installing from web is quite the time saver!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
New nightly coming up for us guys, should be done in about 40 minutes if it doesnt fail...currently 30 min into the build..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
How can you tell on Jenkins?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
http://jenkins.cyanogenmod.com/view/All/job/android/6705/

if you select "Back to project" you will see a list labeled "Build History" it shows what is pending, currently being built, and previously built. I found the d2att one on there and was shown the status.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
Jenkins is awesome if you know how to navigate it, it tells you exactly where the build is if you click on the little terminal icon on this page: http://jenkins.cyanogenmod.com/view/All/builds

Link it in the OP if you like.