yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Try increasing your min freq by one step and please report back if that fixed ur home screen wake locks. Every CPU is different and some cpus can take lower freqs better than others

---------- Post added at 02:59 PM ---------- Previous post was at 02:55 PM ----------

I was part of the Dev team looking at the lock screen issues that first appeared in SGS2 and we found our that was a CPU issue not being able to handle freqs in the 192mhz but as soon as you increase the min one step higher it wouldn't have a problem. The HP touchpad had the same issue as well. We concluded that every CPU is different and is nmwas not a code problem rather than hardware. See if increasing the min freq helps your issue and please report back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Thanks man. Working great. Went from 384mhz to 486mhz. Have tried it numerous times and now wakes everytime so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Try undervolting 486 MHz down to save battery juice if you want. There shouldn't be any differences but you never know some ppl freak out if u go one min less than what u r supposed to. For me as long as my phone lasts for more than a day with heavy use I'm good that's why chargers were invented after all LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
I don't think the stock kernel supports undervolting... Which kernel are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
Balls, just had another bsod.

Glad we got into the nightlies stage though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
Should someone create a new "CM10 Nightly Build" thread to better inform people of the new releases?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi guys after flashing the nightlies and flashing Google apps. Google (Now) search keeps crashing about 5 seconds after I open it. Did a dirty flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Since cyanogen is posting in this one still I'd leave it alone. I'm sure he'll change the op when he has time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReggieSmith:
installed the 8/20 nightly and there is definitely something off with the audio-in for the video recorder... it records VERY low. I had an otterbox on the phone at 1st so I took that off thinking maybe it was blocking the mics a little. No difference. I had to get right next to the subject I was recording and THEN had to turn the phone mic directly towards the sound.

There doesn't seem to be controls in the camera (or the phone) for adjusting recording volume.

Videos from other sources, Youtube, etc., and music seem to play just fine. only seems to affect something you record on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
You're right.

I just fired up "Easy Voice Recorder" -- which I sometimes use to record audio for dubbing over videos -- and recorded a new test track at regular voice levels, and then compared its playback to one made 10 days ago, and there's a huge difference in volume. Maybe there's a setting in DSPManager... (lemme check... edit: nope)

edit2: Also, sending audio "notes to self" are very low-volume as well. (to send a note2self: run GoogleNow voicesearch and say "note to self the quick brown fox jumped over the lazy dog")
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sleepwalkers:
Installed the latest 8/20 nightly, and then had to encrypt my device for a work email account. The encryption went fine, but then I'm unable to do anything on the phone without it immediately rebooting. Wish I was able to use this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
i got it for the first time on this build, 8/20. getting random reboots also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I did a dirty flash and cannot replicate your issue. Maybe try fully wiping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
If you have nothing to compare to previously, you really wouldn't know for sure, since you can still hear the recorded audio being played back, just at much lower levels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Thanks for that suggestion. I'm also experiencing the same issue with the home button not waking up the device occasionally.

Although increasing the min frequency is a good workaround, I'm almost certain that this is a software issue.

If I flash back to the 7/29 unofficial build, the home button to wake issue is completely resolved. It's only occurred with [all] builds after 7/29, and it's definitely replicable.

Edit: workaround didn't work, still experiencing wakeup problems using the home button
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I quoted the wrong post sorry. Meant to quote the Google now problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Does anyone know how to restore lockscreen settings? either from nandroid or from TiBu?

Also, TeslaLED is still able to kill latest nightly by keeping the flash on for under 30 seconds straight. It's interesting. The on time before reboot might be cumulative.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
Netflix

Any update on the Netflix issues?

Also, I too am seeing random screen flickering and had multiple reboots on 8/18. 8/20 hasn't had any reboots yet, but the flickering still persists.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
+1

That and the fact that I ran a couple ROMs with ktoonsez kernel and had it underclocked to 192 MHz with no problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
The workaround worked for a bit but yes its again not waking properly all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Concur, I just noticed it again too. Still having wakeup problems using the home button
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
When updating nightly builds, its OK to just wipe cache & delvik?

Will the nightly update via system update feature ever be implemented?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
Re: your first question: Yes, it's OK to do that. I've had no issues simply wiping cache and dalvik. There is no need to wipe between nightly builds. YMMV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dnorthington:
Yes on wiping. What do you mean by system update feature?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Not sure if this has been reported or not yet, but when on a call and using the keypad to enter numbers while on the call it is very slow in responding to the key press.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Not sure if I'm remembering correctly but I could of sworn on one of my previous devices running cm7 you could update to the latest nightly in settings > about > system update. Like an ota
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
You can do that with ROM manager.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
I thought you needed to have Rom Manager premium to do that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
To do the update in one fell swoop, you do. But you can just browse ROMs and download the new ROM within ROM Manager with the free version. But not much benefit vs. just downloading via the web.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksujace:
Anyone else having an issue with Contacts? I'm getting "Unfortunately, Contacts has stopped"

I'm on the 8/20 nightly, tried reinstall of the nightly as well as fix permissions.

Can you downgrade to 8/18 without doing a full wipe? This is preventing me from being able to make calls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
No issues with contacts here. Dirty flashed over 8/14. Just wiped cache/delvik and fixed permissions.

Still having slight screen fluctuations tho. Disable HW overlay still solves the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You're OBVIOUSLY not wiping or even at all... Expect to have errors when you don't do things properly...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksujace:
I did wipe dalvik before installing 8/20
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You dirty flashed... You need to wipe more than that when you're having specific problems... Wipe and install with these steps:

Wipe Data \ Factory Reset

Wipe Cache

Advanced => Wipe Dalvik Cache

Mounts and Storage => format /system

Mounts and Storage => format /data

Mounts and Storage => format /cache

Advanced => Reboot Recovery

Wipe Data \ Factory Reset

Wipe Cache

Advanced => Wipe Dalvik Cache

Mounts and Storage => Mount /system

Mounts and Storage => Mount /data

Flash ROM

Flash Gapps

Advanced => Fix Permissions

Reboot system now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Flashed 8/20 , running alot more smoother, screen flicker is gone, phone did reboot while on a call once today. Hope its a once a day thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GerardAnthony:
Overkill. Enough said.

Now go wash your car three times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] id10terrordfw:
Ditto.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
If your phone is a bell sgh-i747m, it is an AT&T galaxy S3, flash that recovery in Rom manager, you will be golden. I do recommend you find out what to do with .img files, before you proceed with flashing a preview beta rom on your phone, as well as more flashing basics you can find with search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
lol wish I knew this earlier today.

Can't wait for the next build :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mash2k3:
does google now work with this preview
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Yep. If you're outside the US make sure you change the settings to "google.com".

Does anyone know if there is any way to map the double-home-tap to Google now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spdapimp217:
Flashed the build this morning and it already had my directions to work with traffic. Google Now is already pretty badass in my mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grahamn214:
Thank you. Finally a real response that is informative.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Google now and voice search are force closing for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Yeah I've reset it 5 times today. It's this damn modem/router that my internet and cable run through I'm afraid. But it was connecting and disconnecting on stock also. Turned off WiFi power save and it worked good. With no way to turn it off in cm10 I don't know what to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Sounds like a cable gateway those are trash... Several different devices have trouble with the gateways such as ipad, xbox360s, some phones...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lukesjeans:
i havent installed the rom (Cant even root) but i can answer that. in the play store download {its a paid app} quick launch (app launcher) you can set any app to open at double press, single press or even the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frankdogg:
I was getting duplicates in the gallery earlier. Has anyone else seen this old familiar bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carlitos29:
Google Now

I can't seem to find Google Now anywhere on the phone. I have flashed twice and when I press the mic button all I get is the regular voice search. Please help. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Did you flash jb-gapps? Its part of that package...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carlitos29:
I flashed them after I booted up the phone for the first time. Should I flash them right after flashing the rom while still in cwm? Thanks for the quick response.

---------- Post added at 02:14 AM ---------- Previous post was at 02:07 AM ----------

That was it man!! Thanks a lot I flashed them right after the rom and all is well now. Let's give this baby a run!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Holy, Google now is AMAZING, VOICE SEARCH OMGGGF
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
It does what I asked for but messes with my Apex preferences - was hoping for something more native to the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
It'll probably be a feature further on in cm10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] id10terrordfw:
Herp derp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
that is NOT always a true statement, I have done many FULL wipes (even /system) and still had odd ballcrashes!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
Actually I was having multiple random reboots after wiping everything and this process fixed my problems. So ill keep using it since it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
This is overkill. No need to do this. Wipe data factory reset, wipe cache, and dalvik. Then flash ROM. No need to wipe system because flashing zip already does that.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Yes overkill... but it will fix it... Wipe how you please... [mod edit - unnecessary comment removed]

The phone is finicky sometimes...

If you follow those steps, I guarantee you will have no issues.... and it will be fixed...

Once again, If any of yall folks have problems, and cant figure it out, maybe, just MAYBE, you should take some advice from someone who NEVER has problems with ANYTHING I run...

/EndFckWhoeverStatement

evidence right there

if yall folks wanna keep having problems and posting asking why, cheers to you!!!! My phone works beautimus!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Eagle117:
Not sure how to post a log about this, but with the screen flickering issue... I noticed that when I hide my status bar I get random flickering and when I don't hide it I have no issues with flickering. I'm using Nova Launcher.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
I got a reboot while in call, went to call the person back and phone rebooted again before it even rang the first time. Could be an issue, but hopefully tonight's nightly will fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Disable HW overlay in Developer settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jimbroski:
+1 that his step process works!

I followed BNaughty's step and never had any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
does this slow anything down? add battery drain or any other effects like that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I could care less if they don't get their issues fixed... I gave the steps to fix it, and was told its overkill, and pointless... I'm sure as I'm typing this, they are trying those steps, and when their issues are fixed, they won't even have the balls to post it worked... XDA has become pretty sad these days...

Yall see my join date? Ever see me asking any questions? Nuff said...

No adverse effects whatsoever...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Yea, I had that issue also, I attribute it to the changes that were made in the Audio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You could try clearing phone.apk data with TiBu but I doubt it will fix it... You're probably right about the audio changes... I went from AOKP to 0818 nightly with my looked down upon steps and it worked great... headphone jack didnt work with my headphones though, so I went back to AOKP because of that and center clock... I'm just waiting for SlimBean for this phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reinbeau:
Regarding wipes

One person's overkill is another's safety net. Don't argue the issue, just do what makes you comfortable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksujace:
Followed the steps to the T

Go to the "Got Google?" sign-in screen and immediately got the "Unfortunately, Contacts has stopped" error. Tried the steps twice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Which gapps are you using? Don't use the inverted ones...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksujace:
the regular 0726 from goo.im
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Try this... Wipe the phone with normal methods.... flash the rom... dont flash the gapps... reboot.... after a few minutes of it running doing nothing... flash the gapps, then fix permissions and reboot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
I am having the issue as well but only on the first call. When I call back, or they do, I don't seem to have any issues. I'll try to post a log cat when I get home.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milleirish:
I also had a reboot during a call, I called back and it worked fine after that. Also If you add a new contact, and then try to make a phone call, you dont get sound from the call. I had to reboot the phone to get the sound back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
All these problems are weird... I just did that and mine works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Ok this is just getting ridiculous. 3 phone calls and a reboot after each one. Praying next nightly fixes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You may have a bad gapps download...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bluefire118:
BN, slim bean is really coming to this phone.. Just a quick curious "?"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Nothings been said about it from Krarvind.... Was just saying I'd really like to have it on my S3... Best ROM I've ever used!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bluefire118:
Hmm, I might try to contact him & see if it's possible..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I haven't had any in-call reboots on 8/20 (only 2 calls, though), unlike a few others, but I have had TWO reboots immediately after turning the screen back on. The first happened while charging, and the second one while still on-battery after coming back from a couple hours at the park (tons of 1080p video & pics were taken without a hitch, though (woohoo)).

The display was cross-faded halfway between the lockscreen and the MyTracks app when it froze and rebooted.

Here's the relevant lines from /proc/last_kmsg

[14581.652951] dtv_pipe is not configured yet
[15934.151318] mdp4_overlay_iommu_map_buf: dropped, ndx=2 plane=0
[15934.156231] mdp4_overlay_iommu_map_buf: dropped, ndx=3 plane=0
[15934.402653] cypress_touchkey 16-0020: not real interrupt (1).
[15935.112160] msm_release_ion_client Calling ion_client_destroy

Also... do I spy a fix for this mdp crash in the next nightly's CHANGELOG (or maybe just wishful thinking :))?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I'm getting one strange problem. Made a call with speakerphone on to my local weather hotline and it hangs call up after about 10 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Also getting random reboots (3-4 times so far today) on 8/20. restored nandroid back to preview for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
is 8/14 still the most stable build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gocats7:
All reboots for me were within calls on 8/20.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ovoxo.:
The 8/20 nightly has been working pretty well for me. Only one reboot when loading up the camera, but no FCs. Wifi speeds are decent, but still not hitting what I should be. Battery life has been improved greatly with this build. I'm at 13 hours atm with 2.5 hours screen time and still have 50% battery remaining.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
No reboots here at all with the 8/20 build. About 10 phone calls today. Took a few pics, tried the speaker phone, streamed some music via Bluetooth in mg truck. Everything has been great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
i hope so!

i've been going by this as well:

http://cm10log.appspot.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theraker007:
I find that battery life hard to believe.. thats my battery life using up 90% of my battery on an average day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ovoxo.:
I'm surprised that it's draining so slowly as well. Gonna wait til it hits around 5% before taking some screenshots. For now, I'll be watching some YouTube vids to see how it fares with more battery intensive stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
did any one experienced the Home HW key stopped functioning after a few hours of flash? the button still works but when on functions like you press it to put an app to stanby or long press for recent apps does not work even if the option in settings > advanced > hardware keys are active.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Mine works fine. Only gripe with me is the reboots with calls. Otherwise its buttah

sent from < to there >
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
sweet....I have that issue on the earlier nightly....seems like it got fixed, or it's not a problem after all and it's just me.....thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Using unlock to camera crashes and reboots every time for me. Clicking on the phone app button works fine, takes pictures fine. Just the unlock shortcut crashes the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superj3211:
i am having so many issues with this....i cant copy files to my device now cause i cant select mass storage....it is grayed out.....someone needs to do a 1 click oden back to completely stock for this also....that would be great...something that has a master clear so that you go completely back to stock if something goes wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
You should try following some of the methods to completely wipe that BNaughty has suggested, you shouldn't be "having so many issues with this." You should have also done a nandroid before flashing, as that is a one button press to go completely back to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
As the poster above said, your one click master clear fix my broken phone button is the nandroid backup you should have made. I'm not trying to be a **** but why would someone need to make a 1 click back to stock because you skipped a step in doing a nandroid, or if you did backup , use it and your good to go. Again not trying to flame you, it's just when I see things like "someone NEEDS to do Yada Yada yada" it rubs me the wrong way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
Seconded. Although as a fix, I went into Settings > Lock Screen > Slider shortcuts and remapped the camera app.

It changes the icon, but it doesn't crash anymore.

---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------

Been using it since the build finished last night and no Home key problems for me. Did you do a complete wipe before flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
New 8/21 nightly should be out any minute now (build success).

I love having a jenkins buildhost RSS feed :) (a get.cm RSS feed would be nice too)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
actually it hasnt suceeded yet, its currently still building been about 20 minutes now..

http://jenkins.cyanogenmod.com/view/All/job/android/6677/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adlzian:
Yeah its about 20% done

---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------

Lol beat me to it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
usually takes about 57 minutes to build and be published on Jenkins.