Hi
I'm using CM9's 13/05 build. The lock screen set to disabled.
When I unlock the device using the Home button, it unlocks, than makes the sound as if I've long pressed it, and shows the recently used apps menu.
This happens when using stock kernel or Siyah Kernel (didn't make a difference).
When I use any lock screen the problem goes away.
Has anyone seen this and knows how to fix? If not, can I somehow debug this, or disable the "recently used" feature completely? Not using it anyway.
Thanks
No CyanogenMod 9 nightly builds | DISCUSSION THREAD
has it died ???
Plus its a question posted in the wrong section .
jje
Oh right, sorry.
Sent from my GT-I9100 using XDA
Related
Hi!
I'm using a recent CM9 nightly with default kernel.
I would like to have your opinion : about 3/4 a week my SGS3 is "stuck" when it's locked : impossible to wake up using home or power button, the screen stays black.
The weird thing is that when it happens, the phone is not frozen : I can still hear music on the headphones and control volume using Up/Down buttons.
Sometimes I let it stuck and receive a notification some minutes later and the phone magically can be unlocked again, screen wakes when I push Home button.
Very weird and annoying when that happens.
My question is : what do you think it could be? An app? How can I debug this and know what prevents the screen to wake up when that happens?
Thanks.
Wipe and reflash the rom
zodiaxe66 said:
Wipe and reflash the rom
Click to expand...
Click to collapse
Thanks, but is that the kind of easy answer you all tell when you don't know the exact answer?
When I installed CM9 a week ago, I did do a full wipe...
I think that next time it happens, I will try to connect my SGS3 on USB and do a adb logcat, maybe I'll find useful information.
Have you tinkered with any of the could settings or voltage settings?
Sent from my GT-I9300 using xda premium
ricey1986 said:
Have you tinkered with any of the could settings or voltage settings?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nope
slainer68 said:
Nope
Click to expand...
Click to collapse
Having a similar problem to yourself. Installed CM9 rom had a play and then went back to omegaV9 performing a full wipe using the instructions on this site before reflashing.
Since then when my phone is locked screen off then i unlock either via swipe or using security code (digits ) it looks like the phone unlocks but sort of does a warm boot with black screen for a few seconds with the two buttons down the bottom light up.
When it starts it looks like all the apps have stopped and are restarting again.
I re flashed again omega 9 thought i had it sorted but it started playing up again this evening.
If anyone has any ideas please post..
Hi, I'm a newbie here. I also exprience this problem with my samsung GT-i9300. I hoping to see a fix with this problem.
This forum has been so helpful to new android users. Thank you guys.
ok, so I read around the web and xda and didn't found any reasonable solution to this frustrating bug...
when the screen is of, it takes around 1-2 seconds to wake up...regardless if I press home button or power button...
I tried stock rom, flashed another samsung based, AOSP, AOKP and the lag is present on every rom...even with a fresh install, restored apps, installed everything manually...
tried removing sd card and still nothing
is anyone experiencing this also? is there a fix?
please help out, it is driving me crazy!!
btw can this be used to fix this?
http://forum.xda-developers.com/showthread.php?t=744655
What's so important in your life that you can't wait one second?
Install an app to keep a wakelock and you'll have instant-wake. But get used to plugging your phone in.
BTW, linking to a kernel for the Samsung Vibrant and asking if it will help ... wow.
why the flame? no one is born perfect, not even you
it is annoying because the sg2 is the one of the best phones out there with impressive hardware and it sould be without bugs like this...
I linked that topic because there is something about this lag that may be helpful...
btw, xda search engine provided the link
JKAY's framework v 14.0
have you tried JKAY's new framework for ICS v14.0 .. it has a lot of new options and settings to personalize or S2 just the way u want it
including it has 2 precious options :
1)fast unlock ( can be found under lockscreen options >>set common options )
2)fast lock ( can be found under set misc settings )
I found a topic related to this..
http://forum.xda-developers.com/showthread.php?p=29994420#post29994420
so even though JKAY has this feature, it is not a fix but a battery drain...
the app softlocker cures it but does use a little more battery
I have zero lag at all.. You can try my setup in my signature if you care that much
Sent from my GT-I9100 using xda premium
they say wake lock app is even better
Pretty simple question here, I recently installed the three UK JB update on my unbranded phone (got confused and wasn't concentrating, but anyway...) anniversary noticed that when the screen dims and turns off, if I press the home key to turn it back on in the short space of time that you get before it auto locks, then not only does the screen turn back on but it also backs out of the app I was reading. Is anyone else experiencing this? I never had this issue on ICS.
I am using smart stay, but this happens at times like when I'm reading in the dark or have the phone on my desk without my head directly over it.
Cheers in advance!
Sam
Sent from my GT-I9300 using xda app-developers app
Yep, it's a Samsung bug that I guess they haven't fixed yet...
CyanogenMOD fixed the bug back when CM10 wasn't even usable on our devices
It's already fixed in the XXDLJ4 release.
Sent from my GT-I9300 using xda premium
wtfshouldidonow said:
It's already fixed in the XXDLJ4 release.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
No it is not
Sent from my GT-I9300 using xda premium
I flashed about a week ago the official JB Update and the Bug was gone - till yesterday -.-
Now the Bug is back and i really don't know why. Is there any working solution? (execpt to reflash everything)
As far as I can see the bug depends on the lockscreen type and appears only, if you activated pattern locking and you have a relock delay.
still have it here, no special lock screen set up, just swipe to unlock
samwhiteUK said:
press the home key to turn it back on in the short space of time that you get before it auto locks, then not only does the screen turn back on but it also backs out of the app I was reading.
Click to expand...
Click to collapse
If you set SVoice to launch on home double press it should solve the issue of it backgrounding the app.
Yes this problem seems to appear when S-Voice is turned off. Which sucks cause I'd rather have google voice search.
I freeze Svoice in Titamium backup. And I have a problems with home button as some decribes in posts.
I was looking around for solution and I am happy that i finaly find answer here.
Many thanks for help with this S-Voice app
Samsung SVoice also introduces a delay to home button.
Hi all,
I've recently flashed my GS3 to UltimaRom 4.0. (Very nice Rom btw)
I have no complaints, other than this one small thingy. (don't know if it's a known issue or not but a search didn't reveal anything)
When I press the 'power' button to turn off the display and to put away my phone, it sometimes keeps turning the display on.
Pressing the power button turns it off and immediately turns it back on.
I have to unlock the phone first before I can lock it again and the display stays disabled.
It's not a big deal but annoying if you just want to check something fast and the screen keeps popping up.
Is there any known fix for this? Or am I just forgetting something configuration wise?
Thx for any advise.
No issue here. Maybe one of your apps is causing this.
Sent from my GT-I9300 using xda app-developers app
Same here
I've got the same problem, I've not managed to nail it down to a single rogue app yet that may or may not be causing the issue. I'm running Omega v28 Jelly Bean, so I presume this isn't something wrong in either ROM, just an app like Arsaw says.
It could be:
The CRT bug (fixed in 5.1)
or
Something waking your screen a rogue app, or perhaps something asking for permissions and waking to do that (I had that once).
I'll place money on it being the CRT bug, though
Update to 4.1. There's lots of new features
So it was a bug, I had that too at 4.0 but I didn't pay much attention to it.
Quite late reply, but only had yesterday the chance to flash v4.1 i havent had the issue yet.
So it was probably indeed the problem mentioned above.
Thanks for you help!
Sent from my GT-I9300 using xda app-developers app
For the past week or so my phone has had flickering multicolored lines flash across the homescreen(s)/lockscreen when I turn the display back on. Sometimes it will also happen if I'm sitting on the homescreen with the display already on.
Here is my Rom history as the problem began:
Was on supernexus (Android 4.2.2 I believe) - issue was not present
Flashed Unofficial Slim build 6 (wiped cache/dalvik/factory reset before install)- started having the issue
Flashed Unofficial Slim build 6.2 (wiped cache/dalvik)- issue still present
Flashed AOCP 5.7 yesterday (wiped cache/dalvik/factory reset and formatted internal SD)- thought issue was gone, but it started happening again today.
I tried taking screenshots but the issue disappears as soon as I press the volume+power button to take the screenshot. This only seems to happen when I'm on the homescreen/lockscreen, I dont think it has happened while in any other apps.
I'm wondering if this might be an issue with the specific version of the Nova launcher, as I believe that is the common denominator between these Roms (isn't AOCPs launcher based on CM's nova?). I just installed go launcher and the problem seems to be gone (for now).
Has anyone else seen something like this? I apologize if this has been discussed somewhere, I spent several hours searching Google and XDA before posting. I can post a picture later when I have access to another camera phone.
Same issue here
I have the same issue at the lock screen. Prevalent on all JB roms I have tried, carbon, revolt & slim bean.
I'm currently using Carbon nightly. I have not seen a fix for this yet. I have heard it might be an issue with the processor waking up from sleep.
After installing Go Launcher Ex opening it a couple times and then going back to using the Aspire launcher that came with AOCP, I haven't had this issue again all afternoon. Didn't have it at all yesterday though, so it might come back.
I played around with all the brightness settings but it didn't seem to do anything. Do you happen to have any pictures of the effect you are getting? I'll try and post a picture of mine tonight if it happens again. Thanks!
About 3 hours ago, I changed some GPU & lock screen settings and the issue has not reappeared.
I will post back either later tonight or tomorrow morning with some info.
I haven't taken any photos of the problem yet. By the way, do you usually experience the issue on lock screen coming from a screen off state?
ditto on this. I have Cyanogenmod 10.1 installed and I get these lines intermittently.
Try turning off CRT animations and disable hw overlays.
Sent from my SAMSUNG-SGH-I717 using xda premium
disabling hardware overlays always fixes it for me
same issue
Have the same issue going on had freezing and resolved that now I'm stuck on these lines multiple diff ROMs I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it? Attaching screen shots of these multi color lines we speak of
Nvm can do it with the browser will edit this later and add them with a pc
nimixes said:
I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it?
Click to expand...
Click to collapse
Go to settings, developer options scroll half way down and you will find it. You will have to disable it every time you reboot or you can use two paid apps from the market. These apps are tasker and secure setting they are both worth every cent.
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have any backlight handling apps? I used lux all the time and it stopped after I disabled it.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Just enabled "Disabled HW overlay" and "Force GPU rendering". Like some of the users suggested, I found about the possible solution from this video:
http://www.youtube.com/watch?v=yhhPPke_Nbw
(go to 1:40)
I usually get the flickering with the lock screen (I use WidgetLocker Lockscreen). I was having some flickering this morning and checking both of those options seemed to immediately cut out the flickering.
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Please elaborate
Demmonnixx said:
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Click to expand...
Click to collapse
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
nimixes said:
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301558&page=22
Scroll down to my post there. If you still need help, just let me know.
Trickster mod I believe is mainly for Rom's that have Kernels that can be OC'd or Under Clocked. Kind of the same as Android Tweaker or SetCPU but is a little smoother for me IMO.