yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JimmyStale:
A "dirty flash" seems to indeed work.

I originally wiped cache and dalvik then flashed the 7-29 build. I had no call volume after 1 call and had to rebo yqrrtot to get it back. I restored to the 7-27 build and reflashed 7-29 without wiping anything. (I did reflash gapps as well) Calling seems to be working as expected now. No need to reboot phone after every call.

Sent via raven from Winterfell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cojak777:
Neither USB or WiFi tethering is working for me on the 7/29 build. I also had a mini heart attack when I could only get edge after flashing, I thought I wiped my imei. A reboot fixed it though. Thanks for a great ROM, its super smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Edited because I was wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I forgot to mention that I did have to reflash gapps to get Google Now up and running (this build is the only one I've had to do that with so far) but aside from that dirty flashing has worked for me every time with every build so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
I reported the problem of the call issue.

I have wiped everything, did a clean install, tested, everything worked.

Did a titanium backup of my data and tested, everything worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hayst99:
This is not always true, when I lost my imei I could still use edge but hspa and lte did not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I can confirm that outgoing call audio bug here, too (clean wipe install of 7/29). After the first outgoing call, there's dead silence. My incoming calls seem to be fine, though.

(And instead of rebooting, the easy workaround is to just toggle the speaker on/off when initiating a call if you hear no ringing before connecting.)

EDIT: Added about 30 seconds of logcat of the bug being reproduced. After freshly rebooting and letting the phone settle, I started logcat, then:

1) opened the dialer

2) touched the call log tab

3) dialed the automated National Weather Service for my area (which is (631) 924-0517)

4) call connected and audio was fine, so I hung up

5) redialed, and heard nothing

6) toggled speakerphone on/off, and audio returned

7) hung up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Please post logcat instead of confirming, can debug a confirm ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Explain what logcat is unless that derails the thread, because if it helps, Im all for doing it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
http://www.lmgtfy.com/?q=tutorial+how+to+logcat&l=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
nevermind
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Always a good idea. Just added a logcat and the steps taken to reproduce the call audio bug to my post above. HTH.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cojak777:
I read that you can't get anything higher than edge, but I haven't really looked into it. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not true. I have an sgs3 for testing (no imei) and it gets edge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I edited my original post, cause I was wrong...

Tried to "thank" you, but I hit my quota for the day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iastonish:
Don't have the audio bug. Came from a clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calceltic:
audio works if you use the dialer to input the phone number manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
Lost my imei on my first s3...had lte and voice....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luciobarreto:
Gmail notifications?

After flashing cm10.2 and new gapps, for some reason, I am no longer receiving any notification for new emails on Gmail... (need to open the app to find out that I have emails). And I checked the settings, I have notifications on (I guess).

Is this something that someone else is also experiencing or is it a particular problem that I got on my phone only?

Any ideas?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dual_Everything:
Great Tip. I went into dev options after tapping build number 7 times.

Then I checked usb debugging. Unfortunately it didn't change anything.

This is probably more of an issue with my phone than with cyanogenmod (which is awesome!)

BTW I did resolve a problem with not being able to read an sd card. I noticed that the permissions

were all null in /storage/sdcard1. So I set the permissions to 777 and rebooted. The sd card works now.

Also the group was changed from system (I think) to sdcard_rw. So something must have gotten triggered

during the reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Anybody flash 9/8 yet? Does it boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
Just finished. Working this time around
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iamjerico:
Boots for me as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Same. Seems a little random. Sometimes no flashing light, but will have notification bar indicator.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
It's any build for a year.

If I enable location services, I get this.

All I can figure is that some app, a widget or background process is hammering for location data.

I have weather on hd widgets on home screen, weather on the lock screen... I think I took those away once with no benefit.

I use exchange... otherwise, nothing too special. If I could just get some logging...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Better battery stats
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Attached the partial wake locks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Google drive synchronisation (sic) error

Anybody getting this annoying error message (see Title line), plus "Runtime Exception"? How can I fix it? On latest 10.2 nightly (09/08), though it's been behaving like this ever since flashing 10.2 (...I think).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Title line doesn't show on tapatalk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] icedmayhem:
Just installed this latest nightly to my buddies att s3 and cannot get his lte to even turn on. Under network mode it will only stick to wcdma and gsm. This is really frustrating, alrdy installed recent rc2 and updated boot and radio for mg2. Any ideas, anyone have this before?

Sent from my Galaxy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I use hd widgets and found them to consume battery pretty rapidly until I found the battery saving settings in them. Have you turned all those on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I had no idea if those settings. Thanks! Will report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
perhaps you guys can explain to me why I can't flash cyanogenmod to my i747m. every other cm-based rom flashes just fine...but not cyanogen itself....

even when I flash d2att CWM recovery manually (via dd), I still can't install cyanogenmod builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Could be because your *bootloader* is one of the older ones. As some point, the nightlies start to check if the *bootloader* was up to date, and will quit during installation if it was found to be not udpated.

Link to bootloaders http://xdaforums.com/showthread.php?t=2321310

Optionally update your modem: http://xdaforums.com/showthread.php?t=1831898

Thanks for correcting me polobunny :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Not firmware but bootloader. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
After a few days of checking this out, this has given me at least 3 more hours of battery life daily. Nice post flex!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So here's two things I have yet to understand.

1. My wife has a stock rooted gs3. She gets about twice the battery life I get. Over night, she loses maybe .6% an hour, while I lose at least twice that. Her wifi is on constantly at home, bt always on, and all the Samsung crap running in the background. I, on the other hand, have pretty much everything off and no Samsung ****. What's up with that?

2. Her phone gets better service than mine. I'm running cm 10.1.2 with the CM kernel and newest modem. See the screen shots below. Again, what's up with that?

EDIT: Screen shots removed because of phone numbers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Perhaps you are using an old modem firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Try wakelock detector from Play Store may help you find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alpha Geek:
If I recall, your phone is AT&T & hers is tmo, correct? That means you spend a bunch of time on edge network. And it had been my experience that edge drains battery badly. Consider getting a T-Mobile phone and all your problems will go away and you and your wife's phone will be equal! :)

Sent from my SGH T999 Galaxy S3. using the XDA app. If I have helped you out in any way. please click thanks. I'm new here and need help establishing my rep. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
We're both on att. I'm using the latest modem, as is she. The only difference in our phones is that she's on stock and I'm on cm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
If I'm connected to wifi, at home for example, my battery life is *significantly * increased. If I stay at home over the weekend, after pulling it off the charger Saturday morning, the battery will probably be around 30 or 40% come Sunday night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I really hope you have taken the time to revert back to stock and do a full wipe of your phone before wasting everyone's time here trying to figure out your batter life issues. Perhaps you would be better off taking your search to the Q and A section as this really doesn't have anything to do with this ROM specifically as no one else has this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
Thanks, but none of the options worked.

I flashed back to stock 4.1.2 - no dice.

I flashed back to sock 4.1.1. - no dice

and yes, I tried using the methods to update bootloader (even though I'm pretty sure my bootloader was already up to date).

???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rrryan2:
I've got the same problem and have had it since about April or so.

Developer options, Root and USB debugging enabled, pathname set to /legacy/, ext. SD card removed. It's just hit or miss, restores some apps fine but hangs interminably for others.

I've managed to figure out that if I can restore the app itself from the Play store I can use Tibu to restore the data for most of the apps where it hangs otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What is the error you are getting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
The RIJL wakelock has woken my phone over 1400 times in the last 12 hours. This is almost always my largest wakelock. Anyone have any ideas on it in CM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I dirty flashed from 7/22 10.1 to 9/8 10.2 + 8/13 gapps yesterday and haven't noticed any issues in typical use, but I'll see if I can reproduce some of the ones mentioned in the last few weeks. I'll also be trying out the ones I've had issues with, such as low recording volume, wifi handoff issues at school, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Of course, done the stock thing too many times to count. I'll look for the Q&A thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Is her phone newer? A newer battery could explain the difference.

Definitely download Wakelock Detector and GSam Battery Monitor to look at what apps/ processes are draining battery on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Phones were bought at the exact same time. I have both Wakelock Detector and BBS. The RIJL Wakelock is running like mad on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Bit of a hassle, but if you would backup everything and run the stock rom for a day or two you could see if it's really CM10, if you haven't done it already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, I've tried before... I couldn't correlate any particular activity that triggered the battery death drain, but I've found how to use battery stats to get faster analysis on the location service...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That was directed at slicetwo, but as for your problem I would be inclined to say it's something you install afterward. Something in the apps you're using is doing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
yeeeeeeah... i've thought about that... ugh... haha. it just sounds like such a bloddy hassle. im going to update to the NEWEST bootloader (i have the 2nd to latest one) and see what happens there. i didn't realize until today that i was one behind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think it would help upgrading the bootloader, but never know. And yeah, I feel you. Going back to stock... bleh! But for one day, just one day, and you'll know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
yeah, i know. i'd just have to reinstall everything and set it all back up properly so that it ran the same apps and such as what i'm rocking now. do you not see a big RIJL wakelock on your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope. No unsual RILJ wakelock, albeit a tad of connectivity related one because at work my reception isn't wonderful (and the wifi has issues, heh).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Yeeeeeah... In 6 hours I can see up to 1000 from rijl.

I guess the rijl wakelock also gets worse with worse cell service?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Sure does. But +400 in 22 minutes is kinda bad, unless you were on a fringe area. It's not that much of a problem that it holds a small wakelock every now and then, just an issue if it does for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Yeah. That's with was service at work. It just does up to 1400 small ones a day. That can't be good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
And what's the wakelock time? Tell yourself that you're going to see a wakelock every time it connects to a different cell tower and the like, so many wakelocks are expected coming from RILJ. I think you should only be worried if it holds them for a while or if you're on a fringe area for LTE and it keeps switching back and forth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cre4per:
I have the same problem as you 11 hours on and over 3000
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
The only down side I see so far of these CM10.2 Nightly's that I am running is they are making my Nexus 10 seem slow! haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
usually, the time is very short. like maybe a few minutes tops. i just assumed that it was a big deal as when it wakes up, it then takes some time to go back to sleep. i'm going to revert to stock for overnight and see what happens while it's on my nightstand (which is what i've been basing this all off of).

question. when i want to go back to CM, can i just restore from my nandroid, or do I need to flash CM again, then restore from nandroid? i'm already on the latest bootloader and modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
If I recall correctly, Quiet Hours also turned LED notifications off. That doesn't seem to be the case in 10.2. Is this a bug or a feature that was removed. I know I can probably run another app to turn them off at certain hours, but is rather not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
so super crap on a stick.

i wiped my phone. (even formatted the sdcard to clean out old ****). then i tried to install cm10.1.2. said my bootloader was wrong. i flashed the bootloader from my external SD card. tried again, didnt work. then i plugged my phone into my computer, odin'd the samsung stock rom, that finished, and now i'm stuck on the SAMSUNG screen wiht the blue hue pulsing... wtf....

i have no idea where to go from here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AshishPyala:
Just go into the stock recovery and wipe data and cache and reboot. You'll be fine from there on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
i did that. then it booted up, but when the white ATT screen was supposed to come on, the screen was black. the LED was on, and i heard the bootup sound, but no screen image... i'm reflashing the stock image to see what happens.

EDIT: reflashing worked. now i'm gonna update to the newest 4.1.2 and then try and insstall CM again. my damn nandroid was erased when i wiped the sdcard... oops!

aaaand while i'm at it, the whole reason for all this was to see if my signal was better on touchwiz than on CM. turns out, i do get better signal on touchwiz than CM. the signal strength is much stronger. this is stock TW vs. stock CM 10.1.2. i used the Root Checker app, and it says that I'm on the MG2 bootloader. any ideas as to why that may be?

---------- Post added at 07:40 PM ---------- Previous post was at 07:08 PM ----------

alright. so i got the phone working fine. it's booted up. i did the 4.1.2 update to make sure my bootloader and such was updated. i flashed CWM. now when i try to flash CM10.1.2 from my external SD card, i get the bootloader error. i then flashed the bootloader itself, then tried CM again, and still got the bootloader error. what am i missing?

---------- Post added at 07:47 PM ---------- Previous post was at 07:40 PM ----------

im getting status 7 error

and my last update for the evening... i got cm10 installed on the phone. i checked the bootloader and the modem again... both are the newest of the new. i downloaded 10.1.2 from the CM update in settings, still got the same damn error. what the hell am i doing wrong?!?!?! ugh. i've been reading over the last tons of pages of this thread trying to find an answer and have come up empty handed every single time. i should have never messed with this stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's because the bootloader you have now is newer than nightly/stable you're trying to install so it's not on the list. Just open up the rom zip and edit the update-script file and add your bootloader in there. Open that file with a text editor such as notepad++ or notepad2, not the classic notepad or wordpad because it contains important characters that both don't display properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
i'm going to try this now. if this works, i will love you forever.

IT SASSAFRASSINGFRIGGING WORKED!!!!! you are a beautiful human being.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Focal still seems just as buggy as always... Any big plans there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
Building ROMs

I know this is a little off topic. Sorry. But it's close.

I have setup a build environment. I have successfully built about 10 d2att ROMs from the CM 10.2 source.

I've had some miscellaneous questions that I wanted to ask. But now I've got a problem that I need help with.

Is there a forum where I can go to ask for help building ROMs?

Thanks...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Quiet hours and their disabling of the LED notifications when set works fine for me. Running the latest 10.2 nightly but also haven't seen any issues with this since the beginning of the 10.2 nightlies.

I'm sure it is but there is a check box in the quiet hours settings area to turn off notification LEDs. Are you sure it's checked?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
Oh my! Yes. It was unchecked. Didn't even look there. I've been racking my brain to the point of uselessness I guess. I just set NFC Task Launcher to set a temporary fix. Guess I don't need it now. :)

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droideastcoast:
Where do I find USB debugging? I have looked in all system menus and can't find it anywhere

Edit: never mind I found it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
A few notes on my experience on the 9/8 nightly of 10.2 w/ 8/13 gapps.

Focal is pretty buggy. Widgets loaded in the sidebar disappear after I switch camera modes and switch back. They're no options to even display them, but they come back once I close the app and reload it. PicSphere renders complete garbage when I take a series of photos with it. Also, there was no storage location setting (that I saw) after going through every setting meticulously. Perhaps its not in the widgets?

polobunny, the stock messenger app seems to work fine on resizing images properly on d2att. I sent several and had no problems with it.

Battery life seems OK. PicSphere rendering ate 12% of my battery in the 2 minutes it took to (incorrectly) render the photos I took, but that may just be a battery reporting/display bug, since it's impossible for it to be sucking down that much juice.

My wifi handoff issue is no longer a problem when going from one building on campus to another. Seemed completely fine today when running around multiple places on campus.

Low audio recording volume seems to still be a problem. In the two lectures I recorded today, sitting in the same spot as last week, with the same professors, volume was still nearly inaudibly low on the recordings, yet in person it's fine.

I don't see any show-stopping bugs, yet, but I also haven't really used it much. Will report more as I go through various other usage scenarios.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == I747MVLDLK4") || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == I747MUMBLL1"

E: Error in /external_sd/cm-10.1.2-d2att.zip

(status 7)

Installation aborted

>> I've re-downloaded the zip file and re-tried - it fails each time w/same error.

>>I've flashed (Odin) back to stock with SamMobile firmware packages

>>I've used dd to copy recovery (CWM and CWM-touch)

>>I've updated the bootloader manually (both zip and Odin file)

I'm curious though: I have flashed every other CM-based ROM, but CM itself.

LMGTFY ftw >_>

I found this: http://www.youtube.com/watch?v=QW1znjDLe-k

The guy says to remove the getprop check at the beginning of the "updater-script" file found in META-INF\com\google\android of the unzipped ROM file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The getprop check here checks for the bootloader. The CM10.1.2 stable didn't have all the recent bootloaders so that's normal that you get an error. Either remove the whole line or add your bootloader to the update-script file and you'll be able to flash it. I would highly recommend flashing CM10.1.3 RC2 rather than the CM10.1.2 stable though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
Ok. Thanks, Polobunny! I appreciate the help here.

I'll give it a shot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Don't forget to edit the file with either Notepad+ or Notepad2 and not simple notepad or wordpad because it's a Linux formatted file and the later doesn't support all the characters, which can lead to problems. Slicetwo had the same issue just before you. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgp77:
I'm getting this as well. From what I can tell, it only happens when I'm at home connected to wifi. It doesn't happen with Touchwiz.