yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
...don't reboot the phone like that?

I've never had audio problems on a reboot, although I've never had my phone reboot without me wanting it to. I would suggest that, until the "sticky" volume bug gets fixed, maybe you shouldn't have TiBu rebooting your phone when you need the alarms to make it to work on time... Although you should probably invest $15 in an alarm clock if you insist on using pre-beta software on your phone and need to be up in the morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
could this be made an option? S-voice never worked well for me. Google now did. Now that this is enabled, Google now works as bad as s-voice did. I don't think I have bad hardware, as this is a replacement phone and both had the issue in stock firmware.

Normally I'd assume this just isn't fully functional, but since its behaving the same way s-voice did, I think its my voice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock79:
I've actually had the problem with Google now not picking up what i say (dirty flash and full wipe). I flashed another non JB rom and Google Now worked perfectly. Eventually flashed back to cm10 cause TW is too slow for me. Also, i still have to boot recovery and hit fix permissions to get my data working (M1 nightly). Lastly, is there a way to change the lockscreen weather icon images?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaskwith:
Never have had an iPhone to which I have had this phone number linked. The MMS she sent me was in fact a picture so I guess its just pictures I'm not able to receive...

On another ROM related note I have been getting some bad screen flicker and i think it might be related to the onscreen navigation bar...because when I was using aokp they said the flicker was fixed as well and I used the Nav bar and it was flickering here and there. I have used cm10 since the nightlues started and have never experienced flicker but I recently added to my build.prop to get the Nav bar and I'm seeing flicker when I do some things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
thanks smartass. if you have nothing constructive to offer how about trolling elsewhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reinbeau:
Stay on topic

Remember, this is a development thread, let's stay away from turbo discussions (although I see the discussion was pulled back on track - pun intended ;) )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirrkitt:
MMS has been wonky and really unreliable for me, too. Try switching to another messaging app for now.

Sometimes I'll send an MMS and it won't send for 6 hours or it just doesn't send at all. Or I'll get a picture and it just doesn't ever finish downloading.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
You would have to take your sim put it in a iPhone go into imessage and log out. I know it's a hassle but it's worth it. Because I started not to receive messages later down the road. Apple has been slacking on ways to fix it easier. It's unfortunate but worth it.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock79:
Figured I'll reply to my own message. I tested the mic with voice dialer and it worked perfectly. Google now and voice services are just not working well with each other.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tylerlaczko:
Google Now

I am also experiencing Google Now voice issues and using Voice -> Text

Used to work flawlessly!

:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brocabortzfield:
Anyone else having issues with the alarm clock just vibrating instead of going off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
As mentioned previously, there is a volume bug that requires you to change the volume of each option in Settings > Sound to reset the volume to the proper level. Try moving the Alarms slider down, wait a second, then turn it back up to whatever level you would like it at.

---------- Post added at 01:30 PM ---------- Previous post was at 01:30 PM ----------

outz, I'm not being a smartass. I'm telling you to not rely on an incomplete ROM to be your alarm clock, as stated by Cyanogen in the first post of this thread. You know that it's the reboots that are breaking your alarm volume, so stop rebooting overnight or get another alarm. There is no possible other answer to your problem, aside from telling you to go code your own ROM and fix the bugs yourself (which would definitely be trolling)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I've had MMS issues too. Mainly when receiving pictures.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
For Google now, talk to the top of the mic

Sent from my JellyBean Galaxys3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I don't use the stock app. I use Go SMS because of the group messaging function. Try that, because I haven't had an issue with MMS with that app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaskwith:
Just downloaded go SMS and rebooted and suddenly I have a new test message from her...but there was not a new message so I scrolldd through the history and her MMS downloaded. So thanks for the tip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
This guy found the issue. Hopefully this will be fixed in the next nightly.

The mics are switched for voice input - use noise-cancelling mic for voice input (doesn't work well at all).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Thanks for the suggestion. I am loving this SMS app so far much better than the stock SMS app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I agree, and the ICS theme is pretty sweet too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Well that's just reeedonkeylous and I'm not re-training myself to talk to the top of my phone. :)

(OFFTOPIC: So sad that summer is coming to an end in a week... because it's also the end of the hotties walking around in skimpie clothes. SCHWING. (also glad my wife doesn't read my posts).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andriel:
Data issues

I've been wracking my brain for a week or so now on data issues. I've been using since the 8/14 and have routinely full-wiped if an issue arises. About a week ago I noticed a data issue using regular ATT data services. (The issue may have actually started sooner - as I have WIFI available most of the time & may not have noticed).

Essentially this issue is that I will show H+ and full bars, yet cannot browse. It may be two minutes of waiting before finally getting the connection to jump to life. Likewise I'll try Speedtest.net app and it will take MINUTES to simply get me a ping (which, ironically will always be 130 milliseconds or so... never figured that little calculation out).

Other times I'll jump right online. I absolutely love this ROM and want to stay committed to the end, but this issue may end up being a deal breaker for me.

I've noticed some other threads (with other ROMs) where data stalls are noted. In every case, this issue only seems to affect certain people. But - long story short --- I had outstanding data service on stock. I just can't seem to get it to be faithful on CM10.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock79:
I've had data issues as well. I usually have to fix permissions in recovery mode for it to work again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew149:
Okay, this explains why voxer doesn't work properly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Have you checked your APN settings? Because before changing my APNs I had the same problem but then I put in the LTE APN, deleted the others and it works flawlessly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
you're completely being a smartass. i never once said OMG GUYS MY ALARM DIDNT WAKE ME UP OMG THIS ROM SUX

i asked if anyone discovered a workaround to a known bug and stated the reason (as people tend to do in these types of threads) you told me to get a $15 alarm clock... that is definitely trolling. i never once stated i depend on the clock or i'm late for work. you made all of these assumptions yourself, which is typical of a troll.

all you had to do was either ignore the post or state a known workaround. if no workaround exists, thats fine with me... but you never know until you ask.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Just got a BSOD. I had my audio jack plugged into my head unit of my truck listening to spotify. The screen was off and I wanted to change the song and it would not wake. Had to hold down the power for it to reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Has this issue occurred previously while listening to Spotify? If you replicate the environment (in your truck, listening to Spotify), does the issue happen again?

BSOD = Blue Screen Of Death = Windows

SOD = Sleep Of Death = Android

*twitch* Got that out of my system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jetpackjeff:
Anyone have a fix for voicemail notifications? They work fine on stock Samsung ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andriel:
The APNs look like everyone I've seen for a S3. What in particular did you have to change? I'm set at ATT LTE pta with default settings underneath.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
What is your minimum CPU frequency? Bump it up one and see if it happens again. It seems many issues can be solved with a simple tweak of the min freq to 486. Don't know if this is something that needs to be addressed in the kernel from CM or if it's more hardware related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Oh you're on AT&T, I'm on Rogers and when I first flash CM10, I have to input the LTE apn. Before I input it, I get really unreliable internet, but once I'm on it, works perfectly. Maybe google AT&T apn and make sure to have the right one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
BSOD=black screen of dealth (android)

Its all the same. I have had this issue since cm10 was released for our phones. Mine happens on Pandora.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] captiv123:
I got the BSOD today when I tried to turn the phone back on. It was in Evernote when turned off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illest_evo:
Can someone message me any info o. How to change camera to save to extrrnal sd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Not possible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andriel:
While my APN is set up according to every example I can find - it was indeed none-the-less an APN issue. Changed the APN to the built-in wap.cingular option and she jumped to life. No issues at all there; except I'm not close enough to town to check speeds.

I may not be able to hit LTE speeds, but I'm hitting 6 to 7 mb; which beats the nothing I was getting all to pieces! Thanks for shaking the right bushes for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crunk954:
My memory card doesn't show up in gallery is there a fix for that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I'll try again in the morning on my way to work and reply to this post. This is the first time its happened.

I have min set to 486 already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaskwith:
Anyone using the monthly build? How stable is it? Or would it be easier to ask what's not working on it?? I'm running the 9-5 build and it doesn't really have any bugs so I'm nervous about regressing...?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
I'm running the monthly build and for me, it is as stable as it can be, which means that I so far have not found any bugs at all. I'm going to really test it for a full day tomorrow to see how much daily driver material it is, but other than that, I suggest to give it a go!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Exostenza:
I just loaded up CM10 M1 on my brother's S III and when he tries to set up swift key it says sorry settings has stopped when the program tries to take him into settings to make it the default keyboard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
Swift key has always been reported to not working great with jellybean
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
Swift key is working fine for me

Sent from my JellyBean Galaxys3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fortesquieu:
Has anyone got PowerAmp to test this issue for me?

http://code.google.com/p/cyanogenmod/issues/detail?id=6190&q=poweramp&sort=status&colspec=ID%20Type%20Status%20Version%20Model%20Network%20Owner%20Summary%20Stars%20Priority

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
See, for some it works, others it doesn't. If anybody has a swift key problem, I suggest to fully wipe, and reflash then if swift key is a must have for you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frelnik:
I'm curious about this as well. This is the main reason I went back to stock from CM10.

What carrier are you with? Some people report success by entering their number in the voicemail number setting, but I've tried that and tried entering the number that's in that setting in the stock ROM, but neither makes a difference. I'm on Bell for what it's worth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jetpackjeff:
I'm on bell too. Do you by any chance used to use blackberry?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I'm on att and don't get the voicemail problems. Maybe a bell problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
Yeah I've had this issue forever. I thought it was just my theme though. Now that I'm looking at it now though, it isn't transparent. But of course it's going to work fine now.

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EddyVercetti:
Very easy to solve, just go to Settings>Misc>Tweaks and uncheck "No ICS Notification Background."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
I get the same issue as well I noticed it annoyed me at first but its not really a big deal now....idk what its related to but it will taken care of eventually but yes I am aware of it.

EDIT: I will try the settigns in the post above and see if that fixes it...thaks it worked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
Kidding..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
That was built this morning (err yesterday morning now I guess lol) shortly after the M-Series experimental builds were made. I've a feeling it is actually the same build minus the M tags since its automated. Next build, 20120912 should be up in a couple hours per usual.

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
12 is up

9/12 - Anyone give it a shot yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
Would formatting /system in any way improve my battery life?

Either this last build or that has literally nearly doubled my battery life. I was getting ~2hrs total on-screen time and now am on pace to get about 4.

Whatever happened is excellent, but thought maybe others should know that possibly clearing system could help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
Today's nightly is up if anyone hasn't noticed yet. ;)

http://get.cm/get/jenkins/7921/cm-10-20120912-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zaeem1992:
My network type keeps reverting to wcdma. I am in lte area and I have the proper APN set up. Any fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Odd bug charging noticed on 9/11 build. Charge indicator didn't come on, didn't increase after several unplugs. In morning phone said 58% reboot then everything it's fine.... after unplug it says 100%

Also occasionally seeing no cell network, then reboot fixes it.

And loud calls.

Other than that great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I'm running the regular nightly from 9/11, and it is the same as the M1 build except for its name. I haven' t seen any major issues. I have really crappy signal at work, so my battery life isn't so great, even on WiFi. The cell radio is constantly toggling between search for 2G (yea, 2G). The recent builds have had great battery life over the weekend (unplug at ~9am, plug back in at midnight, have about 50% left), although I am on WiFi at home for a good portion of the day.

I say....make a NANDroid and give the new build a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaskwith:
Let me know how it goes... I'm thinking of full wipe to monthly build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illest_evo:
Which can't j save to ext SD card from camera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
If I'm understanding correctly, saving photos/videos directly to external SD has not been incorporated into the rom. At least not yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
So many changes coming for this nightly its dizzying. Best just wait two to three days then flash the latest, cause I would be so busy flashing I wouldn't have time to even use the phone. :cracking up:!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Ya there are a lot of changes for 9/12 and looking like there are for 9/13 too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tylerlaczko:
Updating

I do a dirty flash everyday to the newest nightly.

I do not experience and extra issues other than ROM bugs.

Dirty vs Full Wipe doesn't seem to make a difference.

Also update takes around 2 minutes on the S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frelnik:
I never had a Blackberry.

Are you getting voicemail notifications?

On stock, I get the notification along with a text message indicating I have voicemail. On CM10, I get neither.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
I get voicemail notification and text just fine on all the builds including 0912
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maturola:
Similar issue on mine running M1. This morning battery was at 83% (after being plug all night long), after 2 reboot battery was at 100%, and now my battery is draining pretty fast, (83% right now after just 3 hours of pretty much standby).

Not a biggy, but just reporting what I am seeing. Everything else seen to work just fine.

For those with issue with SwiftKey, I had the same issue, it didn't let me set the keyboard and it crashed. all I did was unstalled it. reboot and reinstalled for play store (not from backup). that solve my issue. I don;t think is ROM related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Next build looks epic!!!!! Can't wait

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
No reboot needed to wake 4g up this time. :good: Last few times it was needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I noticed the same thing.

---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------

Well I tried Spotify in my truck again this morning (Headphone jack to radio head unit) and it didn't give me a BSOD (black screen of death). So I'm not sure why it did yesterday while doing the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atmospher1c:
can we get a link to changelogs in the OP?... i can never find them in google.

also, does anyone know if audio is working properly? i havent had working audio in apps since 8/26. phone works just fine still.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
:cool: http://cm10log.appspot.com/?device=d2att#cm-10-20120912-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Audio never stopped working. Just go into Settings > Sound and move each of the volume sliders down, then back up. This has been posted at least 5 times.

And just bookmark this: http://changelog.bbqdroid.org/#d2att/cm10/next
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
My B(Blank)S(Screen)O(of)D(Death) Happened twice, but hasn't since. I am not sure what caused it. Once I was trying to wake it up to get a Talk message and the other I was scrolling through social network app and it blanked out. It did not reset, only blanked and vibrated. I waited to see if Samsung would come up but it didn't so I had to hold the power button. I don't think it is something I can reproduce because the scenarios have been completely different each time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
If anyone has this happen again while near a PC, plug the phone in with USB and see if you can still ADB in to the device. I had this happen a couple times and I've always been able to access ADB shell and logcat functions, even while the screen is dead. It would be most helpful if you could, after confirming that you still have ADB access, type this:

adb logcat > logcat.txt

Let that command run for at least 30 seconds, and while it runs, pick up the phone and tap each of the hardware buttons once so that the logcat will show what errors are being thrown when the buttons are pressed. Once you've hit each of the buttons on the phone, you can tap CTRL+C on your PC to end the logcat capture. You can then unplug and reboot your phone.

This will leave you with a logcat.txt file on your PC that you can stick on Dropbox or Pastebin. Let us know when you've got the logcat posted (but don't put the link out publicly, sometimes information like IMEI and such can be listed in a logcat) and if Steve needs the logs, you'll be asked via PM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I see alot of A2DP related commits in the next build. Is anyone else not getting artist/track metadata on A2DP devices that can display it? My car's headunit isn't showing track info, nor does it allow control, but then again it never did with my Captivate (SGS1). Could be a issue with the head unit and not the phone/ROM, but it works with the iPhone just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Hey guys, I've read all about audio issues, done the fix (move the slider down then back up) and my audio works perfectly except in a call while on speakerphone: the volume is really really low, which kinda beats the purpose of speakerphone if I have to put my head 3 inches away to hear. Is this a known issue? Is there a fix for that that anybody know about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frelnik:
I haven't tried the latest couple of builds, but I've been unable to get voicemail notifications from 9/04 through to 9/09.

Did you have to make any settings changes to get this to work?

In the voicemail number section of the dialer settings, do you have your own number or the Bell voicemail number?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
A2DP is working fine, it's AVRCP that's not working. Any commits to A2DP-related fixes probably won't do anything for the non-functional track display.

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

Have you tried toggling speakerphone off/on again while in a call, or adjusting the speakerphone volume down/back up while in a call?

I've never had problems with my speakerphone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
I've tried all that, but I'm gonna try again today, see if it works. It's weird because when I was on the 09/05 build, I didn't have that problem, now it appeared out of a clear blue sky.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
I can advance tracks etc. using BT via my Sena SMH10 with no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jetpackjeff:
I get neither but get both on stock