Just installed Cyanogen 6.1.2 with the stock kernel (savage's wouldn't pass validation in recovery for...well idk why. In fact, if anyone knows what is causing this, help would be appreciated.)
This issue wasn't occurring earlier today (before I flashed Cyan), but now when the screen is off and I push the power button to bring up the lock screen, it will either:
A) Work just fine.
B) The buttons on the bottom will light up, and nothing will happen.
C) There will be about a 5 sec. delay, and then the lock screen will come up.
It's reeeeally bugging me, and ruining my cyanogen experience :/
Please and Thank you!
I have the same problem on 6.1.1. So far I have uninstalled widget locker, removed my custom brightness profile and I'm currently testing the unlock delay under cyanogenmod settings. It seems to happen less when I have the unlock timeout set to immediate. I'm curious if your screen slowly dims before turning off when you hit the power button, out if it turns off immediately like a sense rom?
Sent from my PC36100 using XDA App
Yes, mine has been slightly dimming everytime as well. I'm wondering how common this is.
Sent from my PC36100 using XDA App
Try and set your lock timeout delay to immediate and let me know if you see improvement. Also, if you haven't figured out yet, the touch screen still works and you can unlock by swyping where your slider would be.
Sent from my PC36100 using XDA App
That seems to have fixed it to a point. It's still kind of intermittent, but for the most part there is no more issue. The strange dimming still occurs when locking though.
Related
i'm using the standard rom
since i've installed launcher pro to get rid of motoblur's home, the screen doesn't lock screen anymore
it just turns off backlight, but any hw key awakes it and i find it unlocked
i already checked in settings and screen timeout is 30 and screen lock is enabled
That is not typical. Not sure what other settings to look at, but never known launcher pro to disable the lock screen.
Sent from my MB525 using Tapatalk
A reboot of the phone fixed that
Windoze style
Sent from my MB525 using XDA App
Alessandro71 said:
A reboot of the phone fixed that
Windoze style
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Same here.
i've seen it happening from time to time
it seem that after the phone is on for a couple of days, the screen lock stops from kicking up after screen blank
if i reboot the phone it will work again
it never happened before, when i used the standard motoblur desktop
I've been having the same problem, as of a short while ago.
I notice that it happens when you manually lock (for me by pressing the Galaxy S power button) the phone while you're still in an application.
Every time it happens, I have to go and reenable the pattern lock.
I bought the new EX ADW launcher and threw it in CM 6.1.1 before I flashed it. This thing is great, well worth the money and by far the best launcher out there. My main issue though is that for the life of me I can't get my phone to lock now. I can press power and the screen will time out like normal but when I 'unlock' it the screen just comes back on - no lock screen or anything. Even tried setting a pattern and got nothing. Anyone else have this issue or figure out how to fix it? I figure I just did something wrong
The second issue is I can't get my home button to do anything. No previews and it won't take me back to the home screen - in fact aside from vibrating when I touch it, it doesn't work at all. Could it be conflicting with the cyanogen settings or something else?
Any ideas would be appreciated and helpful.
KCRic said:
I bought the new EX ADW launcher and threw it in CM 6.1.1 before I flashed it. This thing is great, well worth the money and by far the best launcher out there. My main issue though is that for the life of me I can't get my phone to lock now. I can press power and the screen will time out like normal but when I 'unlock' it the screen just comes back on - no lock screen or anything. Even tried setting a pattern and got nothing. Anyone else have this issue or figure out how to fix it? I figure I just did something wrong
The second issue is I can't get my home button to do anything. No previews and it won't take me back to the home screen - in fact aside from vibrating when I touch it, it doesn't work at all. Could it be conflicting with the cyanogen settings or something else?
Any ideas would be appreciated and helpful.
Click to expand...
Click to collapse
Hmmm...I'm using adw launcher ex and I don't have either of those two problems you mention. I'm running 6.1.1. I'm using lock screen gesture to unlock the phone instead of pattern lock. For me, turning off screen and immediately waking it shows the lock screen. As for your home issue there is a home binding option in the settings, maybe there is your problem? I have mine set to default screen/previews when I press the home button.
Sent from my HTC Vision using XDA App
Lockscreen issue has to be due to CM because ADW EX doesn't mess with that.
Check the input settings in CM Mod to make sure you don't have the lockscreen disabled.
I ended up re-flashing the ROM and it works now. It does it randomly - the last time it occurred after running a fix permissions, kind of strange. No sure if that's what caused it or not.
Whats up with the latest nightlies? Display timeout settings are very limited (max being 1 min). Screen also automatically darkens while using google navigation (5.7 ownhere)...im assuming after a minute or so... making unuseable until i can brighten it up by swiping gently on the notification bar. But it gets distracting while i drive...any ideas? Flashed using amonra, since i dont think cwm is wiping caches(+dalvik) properly... didnt have this problem before jul 11 nightly (just flashed newest 138 and nothing looks changed as far as settings)
Am i the only one with this issue or is this a known bug?
Only thing I can suggest is maybe trying the app Screen On from the Market and set Google Nav to stay on while using.
I have to use this program while in a call to keep the screen from sleeping so I can hang up. App is very handy and works well.
Thanks for the suggestion, although i just wanted to clarify, you're using the app made by the greek guy (blue power button icon) right?
If you keep it plugged in when using navigation, you can set it to never turn off while plugged in under "settings>application>development>stay awake"
Just check that box, and while plugged in it never goes off. But I may be misunderstanding your problem.
nee_vak said:
Thanks for the suggestion, although i just wanted to clarify, you're using the app made by the greek guy (blue power button icon) right?
Click to expand...
Click to collapse
Yep. That is the one.
I did a quick search but didn't find anything on this. For whatever reason, whenever I switch apps from the drop down notification menu, it forces me to input my lock screen pattern, even when I have the lock screen toggled off. I have my settings set to auto lock after 1 min, but this happens whenever I switch apps, even before a minute has passed.
Is this a known issue? Is this happening to anybody else? Is there a fix?
Thanks.
Edit: I'm still on 4.02. It hasn't updated to .04 yet.
No one?
:T
Has this always been happening or did you install/flash something before it started happening?
Sent from my Galaxy Nexus using XDA
I just got my GN yesterday, and it updated by itself to 4.02.
It's been happening ever since I turned on the lock screen. It goes away when the lock screen is turned off. But it's bizarre that it would ask for the lock pattern every time I switch apps from the notification drop down. It doesn't ask for the pattern if I were to switch apps with the App Switcher button.
Really perplexing...
Hate to keep bumping this, but this is just incredibly bizarre.
Can someone test on their GN if the same happens? Turn on a lock screen input, anyone will do. I happen to have the pattern lock. And try to switch between apps or alerts from the pull down notification menu (you can send yourself an email or something, or turn on the music player) and see if you are forced to put in your pattern/passcode/etc before you can switch over.
I have to put in my pattern to unlock the phone every single time I switch apps ONLY from the pull down menu. It's bizarre. If I switch apps from the App Menu, it doesn't do this.
I don't know what's going on. Is this a "feature" of ICS? Seems a bit overkill on security. Or do I actually have a faulty phone (but it seems software related?).
Any help would be great. If need be, I'll make a video to demonstrate what I'm talking about.
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Yes happens to me sometimes too on both 4.02 and 4.04 stock. I don't use a pattern lock but it just fades out and when I turn screen back on it's lockscreen.
Never had this problem. That is weird. I suggest flashing a stock image and see if it still happens. Make a nandroid first of course but throw it away and make a new nandroid if problem goes away.
bow chicka wow wow.
gravis86 said:
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Click to expand...
Click to collapse
I will try this. Thanks for the suggestion. Hopefully it will work. Will update.
gravis86 said:
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Click to expand...
Click to collapse
Yes, this solved it. Thank you! Oh, Ice Cream Sandwich.
I spoke too soon. It's back. I noticed when I toggle the lock screen off, the problem exists. But if I toggle the lock screen on, the problem goes away.
So it may be an issue with the widget itself. I'm using "No Lock" (https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en)
I'm gonna test other toggle widgets to see if it's app related.
onthecouchagain said:
I spoke too soon. It's back. I noticed when I toggle the lock screen off, the problem exists. But if I toggle the lock screen on, the problem goes away.
So it may be an issue with the widget itself. I'm using "No Lock" (https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en)
I'm gonna test other toggle widgets to see if it's app related.
Click to expand...
Click to collapse
So.. it's a third party app you're using and not the stock ics lockscreen..
It would've been wise if you told us that on the first post
qtx said:
So.. it's a third party app you're using and not the stock ics lockscreen..
It would've been wise if you told us that on the first post
Click to expand...
Click to collapse
Yes that would have been good info to have, but I am not running anything custom on my lock screen (though I am on CM) and had this same problem.
I had to reboot the phone after every time I changed the lock screen from anything to anything or I'd run into problems. When changing from no lock screen to a lock screen, I would lose notifications when waking the screen up if the notification was for the last app open.
For example, I was in the Messaging app and locked the screen, without going to the home screen first (so if I were to unlock the app would be right there). Then I received a text and notification worked. I pressed the button to wake the phone and the lock screen showed up (pattern unlock) and the notification for my new text message in the notification bar disappeared. But I hadn't even unlocked so I could get to the app yet...
Does anyone know how to fix the problem whereby the screen's sensitivity gets worse the longer the screen stays on? Some obvious problems of this are missed keys on the keyboard while typing. Others have looked into this and have been able to properly assert that sensitivity worsens as the screen stays on longer, for some reason.
Sent from my Galaxy Nexus using xda app-developers app
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1576739
Something I discovered.
If you change the long press for home to be recents, the problem still persists.
If you access the recents screen but press back, the bug won't show in whichever app is already open until you go back home.