My phone screen turned on and turned off automatically while it in locked screen state.
i used two ROMs that the same problem in...CM7.2 stable,and Leaked ics ROM.
i found one of my friend has a stock ROM also face the same problem.
and this problem doesn't happen when the phone has a fresh state with no user apps.
So what is the solution for this?
anees02 said:
My phone screen turned on and turned off automatically while it in locked screen state.
i used two ROMs that the same problem in...CM7.2 stable,and Leaked ics ROM.
i found one of my friend has a stock ROM also face the same problem.
and this problem doesn't happen when the phone has a fresh state with no user apps.
So what is the solution for this?
Click to expand...
Click to collapse
I had this issue on my droid X2, it was actually a misbehaving app, I had to slowly uninstall apps and see which one caused it.
Sent from my Paranoid Android
Related
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Noticed something strange for the first time , screen is laggy and not responsive while charging the phone , I think it maybe is the kernel as its the first time to notice this , It happened after flashing franco-r6 kernel and iam using insert coin 6.3.1 Rom
Is this normal ?
Sent from my HTC One X using XDA
You flashed a ROM, You're not stock therefore you need to consult the dev of that Rom about the issue.
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Is it still present ? What did u do about it ?
Sent from my HTC One X using XDA
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Yep I get this issue at times as well. Especially when I've left it to charge for a while and try to perform a pattern unlock. Happens about twice a week or so. Screen returns to normal after 10 seconds or so. Weird.
+1 this happens on stock roms all the time. it's intermittent, and often can be temporarily fixed by switching the screen off then on again.
I'm about to send my phone in for repair because of this problem. I actually have a dead patch on the screen which is intermittent. If I go to Developer Options > Pointer Location, and then trace my finger around the screen, I can see the patch where it's not picking up the input. Also sometimes the phone behaves erratically and can become completely unresponsive and flicks back and forth between home screens. Turning the screen off and then on again fixes it temporarily.
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
I don't know but think people either don't know the meaning of stock or I have to learn the meaning
What you described is not stock Rom.and to your answer no I don't get sod.
True. I'm not on stock, I guess I meant to say that my ROM was created from stock. Good to know that someone else is not experiencing this though. Thanks.
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
Click to expand...
Click to collapse
+1
I was having screen freeze while using the google reader app. Had to pull battery.
Am running the same ROM, with battery percentage mod as well. Stock kernel. Not sure why.
possible sleep of death fix?
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB?.
Click to expand...
Click to collapse
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
chorner said:
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
Click to expand...
Click to collapse
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
063_XOBX said:
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
Click to expand...
Click to collapse
good point. i also was wrong about the sd card anyways. i flashed cm9 back on it. turned auto brightness off. it had the issue. rebooted. turned it back on. re-enabled autobrightness. no issue.
thanks for the compliment.
I'm on 4.2 and have the issue. A few times a day, I'll pull it out of my pocket and I see the "backlight" turn on but screen is on. (I'm not sure how there is a backlight if is amoled but i do see some kind of something very very faint )
In Developer Options put all animation scales to .5x.
el_charlie said:
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
Click to expand...
Click to collapse
I experienced a similar issue on 4.1, but it would happen almost once day (very annoying). I'm now on a 4.2 rom and I haven't seen the issue in weeks. :laugh:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
willjr0k5 said:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
Click to expand...
Click to collapse
I'm having the same problem with the stock ff18 rooted...started out of the clear blue, can't place my finger on a consistent pattern. I'm gonna try installing a new kernel and see if that helps. If it works I'll let you know.
I disabled facial recognition security and cleared dalvik and normal cache with clockworkmod. My phone hasn't rebooted basically all day so far.
Something must have been stuck in the cache possibly that was causing issues.
Sent from my SPH-D710 using xda app-developers app
This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.