I've been having a bit of a strange problem lately - sometimes my phone won't enter the lock screen. I'll turn the screen off, or let it go to sleep, and then when I go to turn the screen back on again (could be hours later), it goes directly to the home screen, and never see the lock screen. This makes it very easy to pocket-dial, or launch apps - my pocket started blaring music one day.
A restart seems to fix it for a little while, but within a day it will start doing the same thing, and I don't think I saw the lock screen at all yesterday. Does anyone have any idea what might be causing this? It started a couple months ago, but it seems to be more frequent now.
I am currently running Motorola Milestone, CM7 (kabaldan's beta with swap enabled). It was also happening some with CM7.2.1
Thanks in advance!
Anyone have any ideas?
Another interesting point is that after NOT seeing the lockscreen, and then playing around on the phone, I'll open one of the apps (say the browser), and THEN it will drop into the lockscreen. So right in the middle of doing stuff, it will make me have to unlock the phone. Can be a little frustrating.
Related
So within the last two days I have been having problems with my phone coming out of sleep mode, just to give a little more information when i hit the power button to turn the screen on and go to unlock it, the screen doesn't respond and fades back out. The task bar stays on at the top for about 10 seconds as well. SOMEONE please help lol. I've only had this phone for about a week and this is very frustrating. (phone is rooted btw)
Thanks in advance
If you're having touchscreen malfunctions, then you should exchange it. You've had it one week, you can do that. I will say though, the screen timeout for the lock screen is 5 seconds long. As in, when I wake my phone if I don't touch it, five seconds later it fades out again. It sounds like you're having more serious issues however mentioning the notification bar staying on the screen like that. I recommend you look into exchanging it. Make sure you restore it and unroot it before you do that.
Unroot thread
I was just wondering if anyone had these issues, it didn't appear to do it the first couple days I had it, and I've installed a ton of apps since then. I un-installed some things today and it seems to have subsided, i'm still wondering if anyone else has had problems like this. It may have had to do with a task manager, but i can't be sure. Any insight is appreciated.
So, I downloaded and launched it perfectly... everything so far i tried is working fine except the lock screen... Some times when i press the Cancel key the button lights lid up but there is nothing on the screen and sometimes it appear the lock screen but nothing happen....
Do someone have any solution to this...
Thank you.
I have the same problem. I have been reading that possibly going back to an older kernel / roofs fixes this problem but have not seen and confirmed reports.
Can anyone confirm this and what version?
Thanks
Same problem at me. Both builds are running very fine for some tine but after that are running slow.I don't know why. Maybe is somehow related with the lockscreen problem?
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
+1 one for me... I have got a TOPA100, it's almost impossible to wake up the device, sometimes the lockscreen is visible, but it's impossible to move the unlock slider. Usually I need about 10 times and something around 5 Minutes to wake up the device.
Same problem here, would be great if this can be fixed...
RaZz0r12 said:
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
Click to expand...
Click to collapse
For me it's the same and the battery runs only for one hour, I think a (system?)process is running with 100% CPU time. I am new to android, so I don't know where to look.
Same here on an AT&T Pure. Sure would love to get this fixed however I'm reasonably noob to the Android world (not completely novice to linux in general, and I have successfully flashed my AT&T TyTN II thanks to this site.) Fixing this would be a huge help!
Thanks
More specifically on my device I encounter. The following:
- Turn screen off via end button.
- Turn on screen via call button.
HW button lights come on for a few seconds then cut themselves off.
Screen does not turn on at this point.
- Turn on screen via call button again
- Screen comes on with HW button lights
about half the time screen is unresponsive and will not all me to unlock with swipe of finger
Other times will accept input and unlock to the home screen
When unresponsive repeating entire process above will likely allow me to unlock successfully.
Thanks!
Sent from my AT&T Pure using XDA App
same
my screen never wakes up
end up using soft reset to windows mobile
(it could be something to do with startup??)
I've got a Captivate running base Andromeda 3. I believe I had this issue prior to that, but I cannot be sure. Here's the behavior:
I use the Google Desk Clock overnight while I charge my phone. In the Morning, when I unplug it, everything works fine, regardless of whether I let the screen time out or press the power button to turn it off. Somewhere in the next hour, it may be 3 minutes it may be closer to an hour, the screen decides it WILL NOT turn back on.
The phone is still on, the softkeys still light up, the phone still rings and receives messages. I can even answer the call and talk, just based on knowing where the answer slider is.
Interestingly, if I wait for the call to STOP, the screen will come back ON, but then won't really work. It wants to hang and/or freeze on whatever given home screen you come back to.
Holding volume up plus power to force reboot fixes the issue until the next morning.
I had other issues a long time ago on another rom with LauncherPro, and had switched to ADW. When I mentioned this issue in the Andromeda thread, it was suggested I switch to Zeam. The problem persists and interestingly, about 50% of the time when the phone turns back on, Zeam has decided I only need 3 instead of 5 home screens. Editing the setting brings back the home screens and their setup, weird.
I thought maybe it was Clockr, not clockr.
Using BattStat, SiMi Clock, GVoice, and Keyring widgets. I can't imagine any of my installed apps would make a difference, I'll list them if necessary.
I believe Andromeda (Froyo?) does some weird things with shutting down apps, I'm wondering if it possibly has something to do with that. The problem never happens again during the day, so clearly it either has to do with charging or with the GDesk Clock, or both. Happy to hear any thoughts. Please?
One more thing: While the screen is off but the phone is on, it DESTROYS my battery. Seriously, it'll eat 15% in 20 minutes.
TomMelee said:
I've got a Captivate running base Andromeda 3. I believe I had this issue prior to that, but I cannot be sure. Here's the behavior:
I use the Google Desk Clock overnight while I charge my phone. In the Morning, when I unplug it, everything works fine, regardless of whether I let the screen time out or press the power button to turn it off. Somewhere in the next hour, it may be 3 minutes it may be closer to an hour, the screen decides it WILL NOT turn back on.
The phone is still on, the softkeys still light up, the phone still rings and receives messages. I can even answer the call and talk, just based on knowing where the answer slider is.
Interestingly, if I wait for the call to STOP, the screen will come back ON, but then won't really work. It wants to hang and/or freeze on whatever given home screen you come back to.
Holding volume up plus power to force reboot fixes the issue until the next morning.
I had other issues a long time ago on another rom with LauncherPro, and had switched to ADW. When I mentioned this issue in the Andromeda thread, it was suggested I switch to Zeam. The problem persists and interestingly, about 50% of the time when the phone turns back on, Zeam has decided I only need 3 instead of 5 home screens. Editing the setting brings back the home screens and their setup, weird.
I thought maybe it was Clockr, not clockr.
Using BattStat, SiMi Clock, GVoice, and Keyring widgets. I can't imagine any of my installed apps would make a difference, I'll list them if necessary.
I believe Andromeda (Froyo?) does some weird things with shutting down apps, I'm wondering if it possibly has something to do with that. The problem never happens again during the day, so clearly it either has to do with charging or with the GDesk Clock, or both. Happy to hear any thoughts. Please?
One more thing: While the screen is off but the phone is on, it DESTROYS my battery. Seriously, it'll eat 15% in 20 minutes.
Click to expand...
Click to collapse
I've read something about that couple days ago. If you do a little search, I'm sure you'll find it (can't remember what the thread was called)
Also, black screen usually happens with UV. which brings me to ask.. Do you OC/UV?
Andromeda doesnt do anything differently than any other rom including stock when shutting down apps. there was nothing changed that would change that behavior from any version of 2.2
Unless andromeda does onboard OC/UV, then no, I don't.
Seriously nothing that I can find has changed. I've scoured the boards looking for similar threads, but I suppose I'll start over.
Oc/uv is not available in andromeda without flashing a different kernel
Sent from my atrix
Of course, this is about the Droid 3. Mine has had LauncherPro since day one.
I ran into an odd problem, and repeated it on another Droid 3, even with the new system update. I'm getting a random black screen whenever I turn the screen on from being off. It could be a few seconds, could be minutes, hours, or whenever. Slightly moving the "home screen" left or right allows it to show up.
The bottom task bar is unaffected. Any ideas on how/why this would be happening or how to fix it? I've tried various homescreen and behavior settings in LPro, but nothing has solved it.
Thanks,
yes i have this to, I think it is a gingerbread thing, cause I never had this problem on my D2, until after the gingerbread update, I also have this problem on my D3 as well.
Same here
Sent from my DROID3 using XDA App
I have this problem too but only when I exit an app.
Sent from my DROID3 using XDA App
Same sort of
I also have the dread blank screen (though it's not black, I can see the wallpaper) after exiting apps, especially camera apps, or web apps (e.g.Opera). Sometimes the homescreen stuff does flash on and off, once or more - sometimes bunches. Found that rebooting seems to restabilize things, but it is becoming more annoying over time.
Anyone out there got solution?
I usually just swipe to another home screen. That fixes it (temporarily).
the only time i have this issue is when i first turn the phone on. everything boots up, i swipe the unlock screen and get the black screen with the launcher and everything below in tact. i shift the screen a little to get it to show up and i dont see it again until the next reboot. i never see the issue while switching apps or anything like that. i have arctic grey theme if that says anything to the issue, tho it never really bothered me that much. i could see it getting annoying if it happened all the time.
I have a strange problem, well a few. If I lock my phone (C6903) using the physical button I can't unlock it again. I try for about 5-10 minutes sometimes and it just wont work. If I hold it down I can feel it vibrate as if it's bringing up the power menu but the screen just stays black. Eventually it will randomly wake up then I can play around as normal. If I leave it to lock itself I can unlock every time, fist time no worries. This is what pointed me to it being a SW problem rather than a hardware problem.
I also noticed that when I do have the screen turning off in the dark, I can see that the screen is still lit up! Just it is black, not completely asleep. It's really quite bright when I have it next to the bed. Also when I am outside I can't see the screen at all really, even with the brightness turned right up.
It's really strange all these happened about the same time. I figured maybe it was a ROM problem and a fresh install of stock ROM would help. Tried it and at first most of these problems went, just the fact I still couldn't really see the screen in the sun. I tried another ROM and at first was just the same but then these problems started again.
Has anyone had any or all of these problems or got any ideas what it could be? I am left thinking now that the problem is more likely hardware related as the problems are so sporadic and happen whatever I have installed.
Any help / suggestions would be appreciated but I have the feeling I will have to just admit the phone is dogged
You say that most of the problems desapararecen to install a new ROM, it is likely that installing something extra to be the cause, I was introduced me something similar with Expoxed Notifications Module.
Try a clean installation without installing test applications to determine if the problem recurs.
Thanks, yes I guess I will try that, bit of a pain having to reinstall apps after every install and restoring messages etc so I might just put up for now.
I also have realised that the screen not turning on and the screen staying on but black happen at different times. i.e. I can now randomly turn the screen on and off no problem (don't think I have installed or deleted any apps or changed anything), but the screen stays awake when off. When I was last not able to turn the screen back on after turning off the screen actually went to sleep. Very strange