yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dnorthington:
From what I've seen you need to restore a backup. If you dirty flash 8/24 over 8/25, it won't fix the issues. If you don't have a backup, you'll have to wipe data (and I'd do system too for good measure).

This is why nightlies are nightlies. Always make a backup. Or at least wait and see what others reply with on the forums before you flash a nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
But if everyone waited. Nobody would know :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] egyptshun:
The 23rd I think, the battery life is insane, lost 25 percent in 7 hours!!! Only thing is that it couldn't connect to the camera once.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AmazingSpanoMan:
I was able to flash 24 over 25 and haven't found any adverse effects. Although I do a backup every time I flash a new nightly anyway. Just an FYI it did work for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 3NDL3R:
Yes ... 8/25 KILLS ANY SOUND !!! Just flash again the 8/24 and everything is perfect again. Same to SKANK 8/25.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rpavich:
So the battery life on 8/23 is "insane"...what is it like on 8/24?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] megagodx:
If you're a moderately heavy user or a heavy user, you're going to garner better battery life from a stock custom rom than any of these CM10 ones. That's just my take after using both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rpavich:
I hate to be a noob but I am so I'll ask....what's a "stock custom" rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
A ROM that is based off of Ice Scream Sandwich (ICS 4.0.4) which is what our phones came with officially when we got them. CM10 is based on Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cr1mson:
hi guys, I am having a few problems with consecutive nightly builds.

All versions i flash have these types of problems:

Camera, after a few pictures will freeze up and FC, then when I try to open it, it says cannot connect to camera. Also my phone gets really hot sometimes, so hot to the point where if i press my skin against it, it actually feels like it is burning it :S. As a result, my whole battery will drain in a few hours from a full charge. I have tried several clean flashes, where I do factory reset, wipe cache and dalvik cache...flash the rom, google apps and have even tried a new kernel, always producing the same results. After the flash, i will wipe cache again and fix permissions. I do not know how to solve this, any suggestions? Also, would this much heat be damaging my phone or battery in the long run?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dnorthington:
Try wiping system too in addition to the other wipes. If that doesn't work, you can try to flash back to stock. Sometimes you have to really clean everything out. You shouldn't have to wipe cache or fix permissions after the flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cr1mson:
is wiping system same as factory reset, then format system? Because I did both :'(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dnorthington:
Factory reset only wipes data and cache.

Also, make sure you reinstall gapps if you wipe system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
Folks, let's move any conversation concerning ANY NIGHTLY BUILD to the appropriate thread.

There are a lot of people still using 8/14 PREVIEW, and this thread is for them

Sent from Galaxy S3 via. Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
My camera would freeze and freeze my whole phone making me have to do a hard reboot anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dnorthington:
Seriously? Why would you still be on that build? I agree, this thread should be locked at this point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
Also the camera says can't connect to Camera then it stops?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] egyptshun:
Can't play music, screen starts to flicker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Agreed, time to lock this thread and move on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WMguy:
Really like the lock screen wallpaper but can't find it anywhere to apply it to the desktop. Can someone tell me where to find it?

And I too am using this build. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Quick question guys, my device is rooted already, so I guess I would need to dl the recovery from http://www.clockworkmod.com/rommanager 6.0.1.2 and flash it right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iBotPeaches:
Ugh. How does a development forum sound for you to post this in here? Use the Q and A.

Yes it does. Just use Rom Manager to make sure you get the most up to date version. I don't have it memorized what's up to date.

Sent from my SGS3 AT&T Variant
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
Updated the thread for nightly status.

Some stuff we are working on:

- Still a few graphics issues, minor flicker when switching between GPU and overlay rendering.

- Need to enable the noise cancellation (Audience) chip.

- Occasional fail-to-wake-up issue, requiring multiple power button presses.

- More camera features

- Improved font rendering

- Getting kanged

- Etc etc etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
What's really impressive to me is that google now voice recognition beats the pants off of s-voice.. s-voice had that chip working, but google now's great behavior is without that? Amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
Is anyone else having issues with a pretty laggy lock screen on 8/29? It almost feels like the ONDEMAND CPU governor isn't responding when on the lock screen and dragging the unlock button is really slow and juddery.

Other than that, the build seems great.

EDIT: Same lagginess with pattern unlock, set CPU governor to performance, same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mlemonds:
Awesome!

Request: any way to add a link to a changelog in the OP? I dont know what most of it means but i enjoy reading it :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Just use this: http://cm10log.appspot.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Not noticing that here. I'd say full wipe it if it doesn't get better on the next build for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
Alright. I'm wondering what the issue could be. I might just wipe. But since you mentioned it, what is the best method of wiping? I tried it from the Stock ROM before I installed CM10 and it didn't just wipe data, it formatted my SD card. I'd like to avoid that, if possible.

Thanks for the input on the lock screen though, just needed to know if it was a solo problem for me :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noy-z:
Yea I'd have to agree with above. Lock screen as well as overall butteryness has only gotten consistently better. On 8.29 now and I swear this thing is smooth. Only wiped cache partition and dalvic cache in advanced menu in cwm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Just flashed the 08/30 nightly. I have no audio on incoming calls at all. I can't hear the caller and they can't hear me. Outgoing calls seem to work fine and I didn't notice any echo. Obviously this isn't going to work out for most, since I assume most would expect to receive a phone call once in a while....:laugh:

Edit: Not all bad news, according to these two Gerrit entries, http://review.cyanogenmod.com/#/c/22433/ and http://review.cyanogenmod.com/#/c/22434/ , it looks like the Audience dual mic noise cancelling chip in our phones is going to supported. I would think this would clear up the echo issues for good. Hopefully those get merged for the 08/31 build!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MallCop:
Downloading 8/30 as I type, but I have one main concern:

I'm currently running 8-27 nightly, came from the preview build, and I've experienced this issue on both versions...

I use the swype lockscreen for access to messaging, google now, etc. but then also use a pattern lockscreen behind it. At random the pattern lock screen will automatically switch to just the swype lockscreen (no pattern is requested to unlock device). This had happened three or four times with the preview build during about a month of use, and with two days of use with the nightly it has happened once.

I do use tasker to disable the pattern screen under some circumstances (home, work) but it's never given me any other problems. I've disabled these profiles for now and have not had this happen, but the issue is so rare that I can't tell if this is the root of the problem or not.

Even so, this still is a security concern for me. Has anyone else found this issue, and/or have a way to fix it? I can provide more details if necessary, I just wanted to keep the post fairly short and to the point. Let me know what I need to provide.

Thanks!

EDIT: Hooray for Netflix!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Almost done installing....just restoring data will post on what I find XD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
No audio issues here on incoming calls an 8/30
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
dirty flash? full wipe then flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
For anyone complaining about battery life, here's my stats from yesterday, which was only my first cycle on the 8.29 build. Seems pretty good to me. Using KT kernel.

What I'm getting at here is the battery life in this ROM is fine, and if you're having issues with it don't blame the ROM, it's something you are doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Sorry for the double post, tapatalk is being screwy and won't load the pics...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Tapatalk has been screwy with the image attachments lately... Nice battery life for right after a flash!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JBTY:
Hey guys i juat want to say i jumped from stock to 8/29 nightly restored about 120 apps via TB and no mayor issues here this is freakin awesome!

I have only experienced a few random wifi drops and little call echo during speakerphone use, minor screen flickering on certain screens such as settings and thats pretty much it! Its def better than just Daily driver! working great i think ill hold out till RC on 8/29
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
If its external just remove it before wiping. I had to do it when cm and aokp first came out for the s3 but I have been fine ever since. Also make sure your sdcard is formatted for fat32, assuming that is what you were referring to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aex90832:
I having a serious problem.

I just flashed 8/30 (from 8/29) wiped cache and dalvic, and now the phone wont fully boot. I only get the brief "Samsung" then "Samsung Galaxy S III" boot logos...no more Cyanogen Mod...the screen just goes blank and nothing happens whatsoever..Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
Restore the backup you made right before flashing 8/30.

This probably also belongs in the q and a thread as your post is unrelated to development.

Sent from my Motorola DynaTAC 8000X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cypho:
On 08-24: This has happened twice now.

Battery was low but I did not plug the phone in to charge overnight As expected, in morning battery is dead and phone has shut down. In the morning, plug in phone to charge. After a bit turn the phone on.

Phone turns on - but does not work right. Lots of force closes and no cell signal.

Wiping cache and/or wipe data do not help. Re-installing 8/24 nightly (with or without wipe) does restore functionality.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Electroz:
Not to be insulting, but you're on a 6+ day old release. Try updating to the newest release prior to posting bugs/complaints.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
+1, but - don't flash the 08/30 release because call audio is broken. Wait until 08/31.

But still no excuse to post bugs from an old release. I don't follow your post because you state that you're running 08/24 but flashing 08/24 fixes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yasirfaheem:
Does apps2sd work on this? What else does not work on this yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skizzy034:
Wow you switched too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
anyone know why it adds the wrong prefix to the numbers i dial.....never seemed to have this issue before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ForcedZucchini:
8/31 is shaping up to be a good update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnafer:
I don't know if it's a bug or just not an option but I have the Face Unlock for security and I select the show widgets before security thing, and when I unlock the screen, face unlock doesn't show up. Instead, the backup lock appears (pin/pattern). Any help with this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
I'm always on latest nightly, which is why I'm interested in comments about the nightlies being in the appropriate thread.

Sent from Galaxy S3 via. Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
This doesn't make sense....edit please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
It makes sense.

He misinterpreted my request to post preview/nightly comments in separate threads to mean that I'm a preview user.

In actuality, I'm a nightly user who was requesting nightly content be posted in the appropriate (OTHER) thread.

Since that time, CM renamed this thread to nightly, adding more "cluster" to our "****"

Main question is: can we plz close one thread and jeep nightly discussion to the other? There's no logical reason for requiring everyone to subscribe to both threads

Sent from Galaxy S3 via. Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] King Shady:
Its not out yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
I am not shutting down CyanogenMods thread, yall wanna talk bout nightlies. Go on ahead in here, since this is the real official nightly thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
anyone know anything about this at all...really annoying
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Is there a way to merge my thread into Cyanogens and close mine... That way we only keep Cyanogens and can continue the discussion in one thread

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
this would be great if possible ^^^^^
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
Agreed. Merging the threads would be ideal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
Will look into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
831 build is up

Sent from my JellyBean Galaxys3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
I assume there are many who have installed, tested and are using this that are on the non AT&T variant 747M even though it's not officially supported? Basically runs the same or more issues? The LTE option would be one of the only things I would assume needs to be manually adjusted after install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
Anyone know anything about it using the wrong area code...started after cm10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
http://xdaforums.com/showthread.php?p=30765540

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
I would think you could fix this without an app...shouldn't the phone know my location and do it in its own...it did stock...

Plus all my contacts are correct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AmazingSpanoMan:
OK here are things I'm running into that I didn't see posted yet (sorry if they have nothing showed up on search and I've been reading this thread since day one and don't remember anything)

1. When making a call via BT in my car the phone will randomly kill the BT connection and then will end the call.

2. Call volume will cut in and out on some calls. Similar to if the other person had bad reception.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crawlgsx:
Currently my only complaint is the answering calls delay. When you answer a call it takes a good 4 seconds before the other person hears you. This started with at least 8/28 (maybe earlier, that is when I first noticed) and still persists on 8/31.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
I didn't really notice it on 828, but now that you mention it. It was presend on 829 and current.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
Hopefully someone can refresh my memory, at some point I set the LED notification light to only blink when I miss a call and receive a sms message. I disabled it when I receive an email, but for the life of me I cannot remember whereI made this change. I believe the setting let me choose which apps or which notifications for the LED to blink on, something like that.

Thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
Menu>Display>Notification Light

I believe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miketigerwoods:
For the past two days I've been struggling with data issues. I live in an LTE area and have always had a strong 4G (LTE) signal. However, starting about three days ago with the 8/28 build I started to lose data and the connection would cycle from HSDPA:8 most of the time to all other modes except LTE.

I stopped getting texts as well, only to get them when I reboot and briefly have LTE for 5-10 minutes, then it drops back to HSDPA:8 and no SMS ability. I tried restoring to 8/24 and that was no good. Tried both 8/24 and 8/28 with a full wipe, no luck. Noticing that my IMEI was 0, I restored it according to the other guides in the other sections, but the same problem exists.

I just flashed the second newest and latest modem as well and I still have the same issue on today's (8/31) nightly.

Haven't really seen anyone report this kind of issue in the dev section yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Have you tried restoring to stock through Odin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Your IMEI is showing a 0 and you want to try messing with the modem? Please stop now and refer to the IMEI restore thread. You'll never get your phone working on any ROM until you fix that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
What's the difference between the gray WiFi bars and the blue WiFi bars?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You've lost your connection to google with grey wifi bars...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miketigerwoods:
Like I said, I restored the IMEI. But looks like I have to wait for Peoplearmy to post the new version of the QCN restore utility before I can continue and restore data connectivity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xijar:
You could restore to stock and go warranty claim it. Probably what I would do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clipsruck:
I'm getting arbitrary hang ups. Full signal and I just happened to flash this build from a completely blank slate. But if someone calls me it just may or may not hang up on them after a few minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
no one know why my area code is wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ookba:
Quick one for cyanogen or any other dev out there. So I got like 5 email accounts set up in the stock email app. Some IMAP, some Exchange. Seems like the email app chooses the color it wants to use for the account itself. Any way to change the color of the email account afterwards? I looked through the db files in /data/data/com.android.email but couldn't find a color field. Anyways, it makes it easier to distinguish in combined view. Any way to do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_boris:
While WiFi problems were already mentioned in this thread, I have to say that for me WiFi is noticeably worse on 8/31. Before it was switching off every couple hours now it does not last even 10 minutes or so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
There is a setting there to actually have it disconnect in a poor connection issue, aka if it detects slow wifi speeds. I had that issue last week before I discovered it, when the fringe of Issac caused AT&T to have piss poor DSL service to my area. I turned it off and everything has stayed connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rciomper:
My voicemail number was cleared out with 9/1. Make sure you write your number down before you flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mharmon:
Looks like 0901 has been pulled. The download link in the OP no longer lists it. Downloading it in ROM manager just gives you "download error". Tread carefully with this build, there may be good reasons why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigwill63:
It will show up in your forwarding numbers if you forget to write it down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Haven't had an issue yet. Just realized there is no option to choose for sound when connected to a2dp or headphones. Did they remove that option on 8/29 or later?

Sent from my i747 running CM10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
Interesting glitch...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_boris:
Yes, there is a setting "Avoid poor connection" but I keep it unchecked. Also "Keep WiFi on during sleep" is set to always. But it is switching off way too often now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
i have noticed that too...tapatalk has been acting a lil whacky on cm10..lots and lots of phantom thank yous
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I wonder why it was pulled? I haven't had a problem with it yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
I don't think there were any changes between 8/31 and 9/1 everything that was on the change log for 9/1 is still on change log for 9/2

---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------

I asked the mods to close my CM10 Nightly Thread. This thread is now your one and only source for everything OFFICIAL CM10. I will continue to help anyone I can here.

Thanks,

Neverends
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
I had a similar problem. The third or so post in the IMEI thread has a tool to restore data connectivity that worked fine for me after I fixed the imei.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
Kind of disconcerting that they pulled the 9/1 release. I got it straight after build and haven't noticed anything glaringly wrong. Still have that stupid call volume set to burst my ears problem and the occasional screen flicker. But everything else appears fine.

Sent from my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
I believe the 9/1 and the 8/31 are the same.... The changes that were listed for 9/1 never made it in and they are still showing up for next build.

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deserthi:
I can't get the goole play store to work after installing 9/1. Any suggestions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Go to settings - apps and clear cache and data - reboot in to recovery and wipe dalvik/cache and fix permissions

Reboot and try again.... If that does not work.... Revert to your 8/31 nandroid.... If you didn't to one then try flashing 8/31 over 9/1 with dalvik and cache wipe and remember to fix permissions

Tapatalked w/ AT&TSGS3CM10JB