yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
USB OTG

When you attach a USB key via a USB-OTG cable, it is automatically mounted and available to the OS. When you unmount the USB key and remove the cable, you now have a persistent notification asking you to re-insert an SD card (can't be removed). If you do NOT unmount the key, you just get the one-time warning about removing a SD card without unmounting, and it goes away.

Formatting a "damaged SD card" that is a USB key does not work either. It tries to unmount it and ends up just waiting forever. Also sometimes fsck_msdos fails. Logcat attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I had this on mine this morning went back to CM9 cause I had a few things that CM10 lacked. CM9's nightly from 8/7 is horrible so I'm going back to CM10 for now.

Is there a way to adjust the grid like you can in CM9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tyro.Eh:
Found a fix for picture messaging not working!

Install this app:

https://play.google.com/store/apps/details?id=org.lytsing.myphonenumber

Open app>Go to setting >Input your phone number

MMS should start working again. Well worked for me anyways.

EDIT: This is only a temporary fix as it doesn't stick through a reboot. Must re-enter phone number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
New build is up! Seriously MAJOR kernel and driver update. Hardware VSYNC ("butter") is supported (not 100% optimal yet, Qualcomm is still pushing code out every morning). Big interactivity boost due to some performance work I did. Bugs fixed, A2DP is working, Trebuchet is in, LED is working properly....

Fixing the camera bugs is next on my list.

I don't recommend using a different kernel with this build. Over 250 patches have gone in, and no third-party kernel developers are up to speed yet.

This has basically consumed my entire life for the last week. Have fun :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
Oops, posted too soon. Still copying the file to the server! Give it 5 mins.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Woooh thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegandroid:
been waiting for this!!!!!!

---------- Post added at 04:14 AM ---------- Previous post was at 03:52 AM ----------

just flashed this and now my phone wont boot... it vibrates then shows the samsung logo then shuts of immediately... help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigmike34:
Have the same issue, after flashing (following factory reset, format /system, wiped Dalvik) the phone briefly flashes samsung logo then shuts off. I've been able to get it back into recovery once. Was hoping it was a mistake on my part but looks like the issue is with the latest release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I couldnt get the 8/8 build to Boot.. Im doing a restore now, not sure what the problem is.

---------- Post added at 05:22 AM ---------- Previous post was at 05:20 AM ----------

I see we all posted the same thing at almost the same time lol... i tried to get a logcat via adb but it couldnt see my device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegandroid:
I DO NOT ADVISE ANYONE TO FLASH THIS AS OF YET!!!!

we need to wait till we can figure out this problem before it starts ****ing peoples phones up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
when the phone screen went black and wouldnt boot up i just put the phone back into recovery and restored a previous stock rooted 4.0.4 build i had
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegandroid:
thats pretty much what i had to do. damn, i was waiting up for this... i had a feeling tonight was the night haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastarifla:
Yea unfortunately it boot loops, oh well I can wait it out a bit longer :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I think since im running stock rooted firmware i might try to flash the 7/29 CM build first & then flash the 8/8 build and see if it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegandroid:
i already tried that... let me know what you find.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
I thought I was the only one lol No luck booting up. I should have made a Nandroid.. Time to grab some popcorn and start up Odin!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
well that didnt work... lol..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itaintrite:
Anxiously waiting for the camera to work properly :) cheerio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
I saw some of you were Full wiping, I just tried out wiping the Cache and Dalvik to see if it would yield anything different. But still the same. I'm thinking Kernel issue. I know Cyanogen said try not to use another Kernel but has anyone else flashed to see if they could at least get booted up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
I mean he is probably going to reupload a new one whenever he gets a chance, it isn't anything other than something small he forgot to put in or something, I see no reason to hurry to try a bunch of alternative ideas.

Cyanogen;

The phone bug where you can only make 1 call and the 2nd call out won't do anything -- I have it, and if I hit speaker on and off it fixes it. Just in case that is useful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Got it to boot but flashed aokp kernel.

Sent from my SGS3 i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
I am sure cyanogen is aware of *Not Booting* as t mobile n atnt both have the same issue...patience ...must say gerrit shows a big change log ...anxiously waiting for this update Thanks Cyanogen n the team for their time n efforts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Get a Logcat. It will help out. Telling him that fixes it can help, but not as much as an error log which a logcat is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Wow thank god for a jig I was late to work after flashing this :banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Why would you need the jig? I installed got no boot and booted into cwm just fine. Just flashed my backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Could not get into cwm no boot screen no Samsung screen only blackness almost a full brick I came from a full wipe had to Odin back to rooted stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I did a full wipe just pulled battery and got it in cwm no problem. That's weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kevinl86:
Thank god I didn't flash this one right away. Sounds like a mess!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
No need for all that. Just hold power for ten seconds to power off, then hold home, volume up, power buttons. Release power upon buzz. This will get you to recovery where you can restore or flash a previous build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
thank you so much for this. you truly are a great person. all your doing is taking the stock POS software from our phones and turning our our phones into power houses that we rely on everyday. thats major respect. i was more then happy this morning to see a new build up with MAJOR changes. Ever since 29 i have been running some pretty horrible builds that were deemed great. But i can always rely on the official. thank you again.

---------- Post added at 01:49 PM ---------- Previous post was at 01:37 PM ----------

do not flash this build yet. It will not boot up. You can STILL GET into recovery still. Pull the battery hold volume up power and home button and when it vibrates release power button. It will bring up the samsung symbol and go into recovery. Just restore nandroid. Wait for a fixx.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
Strange, I too get the Samsung logo, then black screen. I always do a nandroid backup prior to any OS update/ change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Could be a small error that cyanogen forgot to fix. He is prolly up seeing that his community is having issues and is making a fix lol

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] speedy_11:
Taking a peek a the t-mobile forum they're having the same not booting issue. And euroskank's jellybro kangs are suffering from the same fate, makes sense they're built from the same source. So it's not just us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Motokorth:
With the error and non booting happening did anyone successfully flash or is it everyone so far with the problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I installed last night's JellyBro build and it wouldn't boot for me either. Until I did a full wipe AGAIN and went through cache, dalvik, and fixed permissions. I think I may be one of the only ones that the ROM works for though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
It flashes fine, since it errors with T-Mobile also the issue isn't a flash issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
i

maybe the second time around it boots. Can anyone else confirm

I also came from PA and had a flashed kernel. Did regular wipes

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
Flashing 8/8 now!

Really looking forward to the new build! if A2DP is actually working this time around you'll get a beer from me this weekend!

just flashed it after a full wipe, and it wont boot past the 1st samsung flash. any idea's?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
You should probably read the thread before you do that and hold off on that. It's broken for the time being and does not boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Didn't for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
this is a first when i downloaded the rom it asked if i wanted to keep it in chrome. acting like a bug or something
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
But it doesn't work for most. I thought I'd be the exception, until I couldn't boot either. Either way, posting won't help cyanogen speed up just for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
yeah ill admit i didnt read the thread and i should have. i cant even get this thing into CWM :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Nothing to do with the ROM. There was a recent Chrome update, you may have not noticed. I've seen that message in Chrome since then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
Take out battery. Wait for 10 seconds. Put the battery pack in . Hold Home Button + Power Btton + Volume Up , until vibration and text above right hand corner that says booting in recov. Let go, and you should be in recov.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradyonly:
Just look for your Galaxy S3 on that page that he linked to. The AT&T recovery image is what you need if you're looking for the D2ATT img.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
.

I've been trying that for ~30 minutes now...

w00t For ODIN!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradyonly:
What I do is hold power and home for about 7 seconds then let go. When it vibrates then hold power home and vol up and after about 3 seconds it'll vibrate again and go into recovery. Seems to work almost every time for me, no battery pull. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeNitE:
Wouldn't boot for me either... did a factory reset... still nothing... Even tried to install previous version after... nothing...

I had to do a recover to get it to boot again... Scared me! LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
not to be a jerk or a troll but i've been flashing ROMs for a Really long time, think HTC HERO. i know how to get into recovery, hell i got the s3 on launch day and had it rooted before the day was over...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hellfenix:
Can anyone post a logcat of the non-booting? I'm curious as to which part fails.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
how can you post a logcat if you cant boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flucks:
I think he was just stating that the S3's recovery can be a little finicky at times and you might want to try the method that worked for him. Come on down from your high horse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
Weird. Looking into it. I went to sleep after uploading it last night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] S4NDM4NN:
I thought the same thing, but what he suggested worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewdatrip:
Did you pull 8/8 build or are you re uploading?

thanks

Beautiful builds thus far man. Glad to be back with CM

Drew
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
No boot up this morning for me either. Thought I had a bad download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
i ended up pushing the stock rom through odin and then restoring paranoid rom. im really looking forward to this build when they get it working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
Did someone say they flashed a custom kernel and it booted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Its kernel related because I took the kernel and modules and flashed them on a working ROM and it didn't boot, so yes, flashing a custom kernel will make it boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kurant1:
I tried the KT747 kernel and it didn't boot. If that makes any difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
The kernel is where the good stuff is at :p. It's better to wait :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Exactly :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
I'm guessing new tweaks = more butter? :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
I flashed the kt kernel right after flashing the new CM10 with no issues. A2DP is working perfectly. I understand it's not what was intended but thought I'd share.

Sent from my SGS3 i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
Good for you. All the new and important stuff is in the new stock CM kernel. So you are basically running it with less features than intended. I think I'll wait.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Mistaken thanks.

I think he was posting this because some people asked if anyone got it running with a different kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
As others have said even tho you booted up with the new build on KTs kernel, all the fixes and new stuff from the stock CM kernel is gone, so what exactly is the advantage to having done that..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
question though once the kernel is fixed we can just extract it and flash that so we dont have to redo our setup correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
You can flash the fixed build cyanogen puts up by wiping cache and dalvik cache there for keeping your setup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
why would you do that? just flash over the top of a previous build, wipe cache and dalvik fix permissions, should be good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drksilenc:
i almost always wipe between flashes no matter the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
I usually don't if I go from aosp to aosp I don't. If I go from touchwiz to touchwiz I don't. The only time I full wipe is if I experience weird problems or if I go from aosp to touchwiz vice versa.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
You can still full wipe if you like. Nandroid first, full wipe, flash, advanced restore data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
I completely understand that the kernel has several features so I don't need your sarcasm. I was just letting the people who couldn't boot know they could try the new version using an alternate kernel. At some time, faux and kt will probably make their own versions for their roms anyway. Thanks for helping though.

Sent from my CM10 powered SGS3 i747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
Rule of thumb is on these previews you should fully wipe in order to make sure all new features or fixes work properly. If you run into a problem, and didn't fully wipe...s.o.l. and are going to have to fully wipe. Why not just do it from the beginning? That's the fun part of flashing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Mainly to check it out like I do every other ROM. I'm not saying it's a perfect solution not am I saying that everyone should do it. I'm just letting those who'd like to try it know what I did.

Sent from my CM10 powered SGS3 i747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Has anyone tried installing Cyanogen's kernel for the build manually through mobile odin or a push then rebooted to see if that worked?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Salty!:
YESSS can't wait for today's build. I'm so glad Trebuchet is back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
Anyone else checking this thread every 5 min?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
I was being nice by using sarcasm. Fact is, if you change the kernel, you are essentially no longer running CM10 8-8 as it was meant to be. And also, from cyanogen himself, posted in the OP:

Just leave it at that and wait for the fixed build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Sorry for the misinterpretation. Being the build didn't boot at all, I tried a different kernel after several wipes and failed boots to find out if it was kernel related.

Sent from my CM10 powered SGS3 i747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
No worries, I can't wait for it to be fixed, either.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
why are you waiting 5 min? i have the last page an op on auto refresh every 60 seconds :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
SORRY!!

New build is up now and actually working! Remind me to not do releases in a sleep-deprivation haze!

:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flucks:
Pst, there is a new build. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
op has been updated but im waiting for a few others to flash it first. can anyone confirm boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
Lol thanks. We are all human. No pbl at all. Thanks a lot for this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
Downloading now. 1 minute left.. will report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Confirmed: Boots and BUTTERY.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] speedy_11:
Be sure your zip has a 2 after the date, cm-10-20120808-2-UNOFFICIAL-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] irish.iolar:
Thank you sir, great work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
Booted up just fine. Thanks for the quick fix Cyanogen!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Same. I feel like I miss out on important fixes that I don't know about lol.

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
I no longer need to refresh every 5 min!

On behalf of Xda's bandwidth, my bandwidth, and my phone, i thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peaster3:
Dammit man! I'm about to run into a meeting. Means I can't download until tonight. :D

Looking forward to the "BUTTAH".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beakybuzzard:
Boots as expected! Thanks CM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
Nooo. The dl is so slow. The server must be getting pounded :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
sorry..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Woot. Get more Zzzzzzzs! ... No, wait, ... less Zzzzzzs!. So conflicted. :)

BTW - Any chance you can add md5sum checksums to the OP for the paranoid among us? Thanks.

my md5sum: acfdbb0292c718508c905481da0ff70a cm-10-20120808-2-UNOFFICIAL-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Motokorth:
Thank you, now to back everything up and give it a rip :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Getting a very respectable ~300KB/s here.

Length: 163986028 (156M) [application/zip]
Saving to: `cm-10-20120808-2-UNOFFICIAL-d2att.zip'

109,203,589 284K/s eta 4m 31s 70% [============> ] 114,891,333 263K/s eta 4m 3s
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
Nice revision. I was still using CM9 specifically because I didn't want persistant search bar and I wanted 5 homescreen rows. Now I will use this. Thanks alot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Booted perfectly, smoooooth as butta!! Wow, friggin' fast!! Thanks Cyanogen!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
JUST WOW. Noticeable butter improvements. Incredibly smooth when scrolling up and down, and side to side in home screen. Talk about moar butter!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boostnek9:
Although it is way to early, can people post their battery life? that will be the showstopper for me.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Does this ROM prescribe Narcos BC I'm hurting from Joy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
Why don't you just flash it and see your self?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
The new build feels like butter! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boostnek9:
Because I have a ROM with good battery life now and why would I when 200 other people can answer my question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
No one can answer your question any time soon. You know it hasn't been long enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Everyone uses their phone differently though, so battery life being posted on here means pretty much nothing. It also take 2 or 3 days of using a ROM for battery life to be represented accurately. Either way, it will take at least a day+ just to get any battery analysis at all. I would say you're better off just trying it yourself. You'll never know for sure. An hour or two off is definitely worth the butter anyway ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Task said it himself battery life all depends on user and phones itself. Not everything can be equal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
Was getting slow dl on phone, downloaded on pc in about 7 min, which is still slow considering my 50mb dl.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Its been like an hour... you probably should wait until tomorrow to ask this if you want an accurate answer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brorex:
Battery life will always vary between users just backup your ROM and try this one :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
1: Thats stupid.

2: If you have a rom with good battery life, then stay where you are, if your primary concern is battery life, then I don't think you should be using an alpha, am I right, or am I right?

3: You're lazy.

4: Don't be annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] irish.iolar:
I nandroid restored my stock rom then flashed the latest build and it didn't boot up, same as when I tried jellybro, it said "ro.build.prop" failed or something like that? Flashed from a blue cwm recovery. Idk... it's working fine for everyone else right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewdatrip:
Just had a black screen of death. Was not present in previous build (7/30)

Had to force reboot

Drew