yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

What does nightly builds imply? Is it full roms for install or just specific file changes? Never dealt with nightlies so not sure what it entails
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

They're full ROMs built automatically everyday with the latest changes. No guarantee of stability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
Ok thanks! I'll avoid that for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Sorry, there will be no change log, though you can still get an idea of what's different by looking at the CM change log and AOKP, AOSPA, and PACMAN commits which are linked in the change log post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

I'm not understanding what's going on with "nightlies".

been looking around on the Internet to no avail.

Could someone explain in blonde terms, please? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Frequent updates (every night)

Small changes.

Instead of an update with once a week or so with a handful of updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Caduceus46:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

I'm getting a lot of random reboots from the March 29 ROM. I actually have to pull out the battery at least 2-3 times a day. Anyone else that issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bugity:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Yes there are a few freezes but you never need to pull your battery. To reboot just hold the power button for a long time (it will work) or hold all three (vol+vol-pwr) and voilà

(emphasis on the "long time") it can take up to 30 seconds (usually doesnt)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Installed the 22.0.1 yesterday and even though I didn't experience any FC's or freezes, I did experience some performance degradation on game's fps. I did perform a benchmark test and the results were similar to the results on 21.0.0 with Kt747, so I'm unsure of what all of the was...

I've reverted back to 21.0.0 until all these issues are sorted out. I'm unsure if the performance issue is related to the new linux or not, but I thought I should report this. If it's useless information or if I'm the only one experiencing this feel free to ignore/delete my post. ;)

Cheers

Ps: thanks a bunch for your work - it's highly appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
In general, AOSP ROMs seem to do worse in benchmarks than proprietary TouchWiz ROMs, though there seems to be no effect on the actual performance. It's actually quite the opposite...AOSP 4.2 with the new 3.4 kernel feels faster and smoother than TouchWiz. Besides, we all know that benchmarks do not accurately "benchmark" the performance of a phone ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gs2usr:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

The change log is included in the ROM, you can find it in: Settings>About phone>View change log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Zero issues here. Dirty flashed the nightly over the last stable...thanks for this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Wait, so why would I want a PACMan nightly if I'm running a PACMan stable?

I don't mean to be rude, I just want to be excited like everyone else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM Nightly Builds for SGH-I747

Because the nightlies always include the latest code and features, aka the bleeding edge. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aironite:
Apr-04 nightly with latest kt kernel rock solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Will you be posting any official stable updates from time to time still, or are nightlies your thing now? I don't mind either way, I'll just have to educate myself a little better on the nightly lifestyle.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harihacker:
Is the March 21st version the last "stable" release for this rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I've been running the March 29 build since it was released and I haven't had any ROM related issues. There doesn't seem to be any huge issues yet with the nightlies so far, otherwise people would probably be posting about it.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
For you personally are you wiping data each for update?

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I actually jump between CM and Pacman. When I see a new commit or fix in the CM Gerrit, I cherry-pick it and build and flash it to test it out. And when it gets merged into CM, I merge it (and fix conflicts) into the pacman sources and then do a test build of pacman to make sure everything is alright.

So to answer your question...I full wipe all the time, sometimes twice or three times a day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Just flashed the latest nightly except it took me a bit longer than usual thanks to TWRP acting stupid but that issue has already been posted in the respective thread. So far I'm liking the latest setup after finally getting it going after a clean, albeit tedious, flash. Now that its nightlies, should take care of my flash itch. Big ups to you again klin for another smooth release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
I can't even get the nightly to flash...2 downloads, dirty flash or clean flash..I'll wait till tomorrow's...it's just a day lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SKIMMAH:
Flashed the latest nightly a few hours ago. This is the first Rom I have flashed on my S3 and I'm not disappointed. :thumbup:

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Just beware, all the aosp ROMs just switched to Linux 3.4 and there's a bit of instability but it's getting much better. Enjoy not having touch wiz!

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
The 3.4 kernel is 97% stable I'd say, since there is really nothing that doesn't work...everything runs smoothly on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
:good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rs3freak:
Unable to flash the latest. Says unable to open zip..what could it be?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Basketbuild is still working on improving their servers and fixing the issues of the ROM hosting, as stated in the TMO thread. So please be patient as they investigate and try to fix the current issues of their servers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
Hey guys quick question how can i make the status bar transparent? If possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Check out the per-app color under hybrid properties. I personally haven't used it to make the status bar transparent, but I think that's how some users did it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
I have to say great work on the rom, really smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SKIMMAH:
So, I searched the thread and it seems I'm not the only one who has encountered the issue of "systemUI has stopped working." However, I did not find a solution to this. I changed the Android and SystemUI colors in Hybrid Properties, as well as the colors of the clock and signal bars under ROMControl. Switching to Phablet mode makes it stop dispalying the error message, but I do not like the Phablet DPI settings. Help?

EDIT: I ended up having to Format Data from recovery and re-flash. This time, I took note of which settings I changed and the order.

Hybrid Properties-Interface:

Nav Bar-0%

Global Color-Status Icon Color

(No issues)

Rom Control:

LED Control-LED Color

(no issues)

I then head back into hybrid properties and attempt to change,

Apps:

Android System-Status Icon Color

Settings-Status Icon Color

SystemUI-Status Icon Color

I apply the new color and don't see any effects, so I reboot. Now, I'm again notified "SystemUI has stopped working." This prompt continued to pop up even after resetting the changes to default. I also reset the overall settings from Hybrid Properties-Interface/Workspace and it stops, however, the navigation bar is enabled again so I disable it. What do you know, "systemUI has stopped working"..... I can no longer disable the Nav bar without this error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Try going into settings--> apps and clear data for system UI. Then go back into hybrid properties and configure the settings however you like again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
The corrupt uploading issue from the buildbox has been fixed. Nightlies should be resuming very soon..:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blanco613:
Hey klin any news on the audio popping issue? Basically whenever music/audio is playing and you press any sort of onscreen button it pops and studders the audio for a second. I've noticed this since v21.

That is literally the only thing keeping this Rom from being perfection. Great job :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
This is a bug on a lot of ROMs right now so I think it may be upstream. Current fix is to disable touch sounds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
??? :confused:

How does this relate to PACMan and the development of it??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SKIMMAH:
The only option I have is 'Clear cache' and even when selected, does nothing.

EDIT: I'm using Nova Launcher. Could this be a possible cause?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
You're right...there is no option to clear data for systemui... Then try clearing then cache and then force stopping it, then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SKIMMAH:
Still no dice. It seems the only time I won't get this error is after a fresh flash before my apps are installed and restored. None of the apps I have backed up contain any system data. Just the Apps themselves including their data.

EDIT: I was FINALLY able to figure it out. I re-flashed for about the seventh time and reboot after EVERY change made. The culprit was disabling Quick Settings under Settings-Sytem-Status Bar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I had that problem a while ago. I believe the culprit was one of the system elements I had been restoring with Titanium Backup. I never figured out which one it was exactly. Messages, maybe?

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nopnopnop:
You're not getting any responses because you're just not very good at trolling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basketthis:
Nightlies are back on tonight for all included official PACman ROMs! :D

Please check pacman.basketbuild.com in the morning for your daily fix. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x-geo:
gives me error when i start flashing in twrp (I747) and when i open the zip in the pc... appears damaged...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
General rule of thumb: if you have nothing productive to post, then DON'T post at all. It saves our time and also the space on the servers that XDA is hosted on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
Thread cleaned of trolling commentary....See the above comments and abide by them - plus, they are what is expected as they are in the XDA posting rules.

If you have nothing to say of value, then do not post. Thanks for honoring the rules and the work of the developers and contributors by not cluttering threads with garbage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
Which nightly did you flash? when i tried to flash the 4/5 nightly it failed in TWRP but the 4/3 flashes perfectly. I think klin1344 said it was an issue with the basketbuild servers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basketthis:
The issue wasn't the server and the issue wasn't the buildbot. The issue was the data transmission. So, it was transmitted. However, there was nothing to verify the upload was correct. We now have systems in place to verify that the upload is complete and not corrupted by transmission/transfer errors. Hope that clears things up! :)

EDIT: I will be removing all previous builds so there is no confusion on which builds are corrupt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zeke757:
Thank you. You guys are awesome! Lol How long until 3.4 runs as stable as 3.0? Is that trolling too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
I've been running ktoonsez kernel for a few days and i haven't had a problem yet

Edit: and my apologizes for getting the issue mixed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Has anyone had this problem where occasionally the phone will freeze while on a phone call? Usually, when I pull the phone away from my face to hang up, I can't because it is frozen. It's happened a couple of times in the past few days.

If not, might be time for a clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TeknoGodz:
So uhh all the nightlies are gone on your file host site...

There were three downloads earlier now they're all gone.

@

http://pacman.basketbuild.com/index.php?dir=main/d2att/nightlies/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
They were removed as not to cause confusion on which build is corrupt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] randman2011:
Oh. I missed the "in the morning' part. Well, I guess I know what I'm doing in the morning!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basketthis:
Nightlies will build and post as soon as github is back up :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
New nightly is up now . downloading now ! Been waiting all day haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
great rom, first time flashing it, love all the customization options

the only thing I'm getting random reboots left and right, any suggestions to cut down on it? I did a full wipe before flashing it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] randman2011:
I had all kinds of problems on older versions of PACman, ParanoidKANGdroid, and PA. This is the first and only 3.4 based ROM that I haven't had that freezing/rebooting problem with. All I did was a dirty flash. No wiping cache, dalvik, or factory reset. I just installed it over an old version of ParanoidKANGdroid and everything has been perfect!

In case anyone was wondering, I have had the phone running for 14 hours with more than two hours of constant Drive use and a lot of music playing, and right now I'm at 42%. Battery life seems excellent so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
What kernel are you using and what are your settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
everything stock as it came in the rom

---------- Post added at 01:47 AM ---------- Previous post was at 01:22 AM ----------

I've also noticed that the phone gets unusually hot, sometimes will reboot even when I'm not using it and the screen is off. I haven't played around with any settings in the "performance" section, so isv default kernel and settings, in the post above I uploaded a couple screenshots, lmk if somehow I can optimize it, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
What I do is I change the default governor to conservative. Interactive is too jumpy for me and the phone can get really hot from using it. I recommend that you give it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I found this : https://github.com/CyanogenMod/android_kernel_samsung_d2/commits/cm-10.1

Seems like that patch caused instability and power drain like you described. It has been reverted now, and should be included in the 4-10 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Can anyone tell me if they are able to turn off the 3-dot menu in this rom? I have tried both ParanoidKangdroid and the latest Deviant Xone and the option to turn it off doesn't have any effect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] randman2011:
I have heard of other people having this issue. I like it there, but I just disabled it and everything still has the menu button. This ROM is a mashup of PA, AOKP, and CM, so there might be some conflict with that setting from the framework of each individual ROM.

The other ROM that I use, ParanoidKANGdroid, is of the same lineage and has that exact same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Can someone tell me where/how to reinstall the voice to text thing. Every time I go to Google now or to use the microphone in texting it says Google search has stopped responding
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Try clearing it's data and opening the Google icon again

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
That didn't work:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Hmm...try doing a backup in recovery first and then doing a full wipe...also make sure you are flashing the latest GApps for Android 4.2.1, dated 3-01-13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Question regarding the nightlies. I am on v 21.0 right now.

Do I need to install the 4/9 nightly and then the 4/10 or can I just install the 4/10?

This is my first rom based off of cm/aosp so not really sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I know it takes time setting up but I'd just clean flash with a factory reset straight to the latest nightly. You could make a backup and try dirty flashing but there's a lot of changes, like Linux 3.4.

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] randman2011:
Dirty flashing from a 3.0 kernel to 3.4 kernel worked for me. It was great for almost all of today, until as with all other 3.4 kernels I have used, it decided to no longer recognize my external SD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamng:
Gmail FC on 4/10 Nightly

Gmail (downloaded from Google Play) closes on me whenever I try to read email. It doesn't happen if I flash it back to the 4/9 build. It seems repeatable for me.

Flash 4/10 build. Run Gmail, crashes.

Flash 4/9 build. Run gmail is fine.

Flash 4/10 build. Run Gmail, crashes.

I've cleared caches as well between flashes.

I hope I gathered the logcat and attached it correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Ah Ok. Well then I'll have to do that another day then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
EDIT: LOL sorry, wrong thread. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I haven't had time to look at your log yet but I advise you to try the next nightly and flash the latest gapps and see if gmail still force closes. Also try a fix permissions in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamng:
4/11 Nightly build has the same problem not only with gmail but the google email client.

I've fixed permissions and have the latest gapps, but I was under the impression that gmail was not part of gapps anymore and downloaded separately.

4/9 works again.

I've attached a logcat of the problem running the google email client but the behavior looks the same as gmail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Im also experiencing gmail crashing whenever i open a mail. This only seems to happen if the mail contained images i think. Since im able to open plain text emails fine. Maybe it crashes rendering HTML?

Edit: anyone experiencing default browser crashing to? It seems theres something wrong with the ROMs web engine which is used by gmail and browser?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
I'm experiencing the Gmail issue as well, but intermittently.

I have 3 Gmail accounts,

On my main personal account, I don't have an issue.

On my general spam account(used for entry signup things) crashes on every other email.

On my 3rd business account, crashes only on new emails, not on old ones.

Also, the Engadget app keeps crashing when trying to read an article.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
My Gmail is crashing as well on the latest nightly...so is browser so I went to another
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
as other people said, email clients and stock browser crashing on 4/10

Does anyone have a link where I can get any 3.0 kernel build from this room that's more stable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Just flash the 4/9 nightly and it works fine.

Once they fix it I'll move to that nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I have experienced this issue as well and I am currently looking into it. I am trying to find out which commit is causing the force closes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I just noticed youtube is also crashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Please try tonight's nightly and see if the force closes are still around. There is really nothing in the code that seems out of the ordinary and could be the culprit for causing this issue. Also it's strange that CM does not have this problem but PACman does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamng:
Sorry same problem on the 4/12 Nightly for me. Reverted back to 4/9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Same issue... Reverted back to 4/9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
For people who are experiencing the problem when scrolling down in an app it randomly jumps back up, it has been fixed in this commit: http://review.cyanogenmod.org/#/c/35585/

There should be no more cached frame redraws anymore in the next nightly.

Still searching for a fix for the apps closing issue...if anyone has anymore logs it would be helpful. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I filtered all the logcat with "com.android.google.gm" in it, hope it helps. I can get logs for other apps too if you want.. (Youtube and Browser)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamng:
Logcat from the 4/13 build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seano666:
Thanks everyone for looking into the force close problem. I really love this ROM and don't want to give it up, but being able to read my email would be nice! Lol Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Not finding any working links to stable releases...

Should I convert to nightlies? If so, why?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SKIMMAH:
I did some searching in the thread and haven't found an answer to this quoted issue either. Anyone? I only ever clean flash...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
Is there an option somewhere that will allow the lights on the capacitive to stay on as long as the screen is on? Currently they only stay on for about 5 seconds after I touch the screen. If I remember correctly it was an option in touchwiz...