Since a few days my screen keeps turning on by itself for no aparent reason. Tried to clear chache and turn on in safe mode but no solution, no difference if its charging or not.
Anybody has a clue on this?
Thanks in advance.
Related
I have been experiencing a periodic problem where the screen on my Fuze will be on, and it will not dim or go to sleep. Even if I press the power button it does not shut off. So the screen stays on completely and will, of course, eventually wear the battery down. While this is happening, it is not frozen - I can still use TF3D. The only way to get the screen to go off is to do a soft reboot, after which it will perform normally (including the power booting working like it should). This happens about once a day.
This generally seems to happen when the phone is charging. When I unplug it, the bar at the top still shows the phone as connected to the power. I also notice that the battery seems a little warmer than usual at the times when charging causes this to happen.
In searching the forum I found one other user who had this issue, but did not see any fixes. Coincidentally or not, that other user was using Blackberry Connect, which I am also.
Anybody else have this problem? If so, any proposed solution?
While I am at it, I have a Blackberry Connect issue as well. The phone will periodically (usually, but not always, in the middle of the night) just stop receiving Blackberry Connect e-mails, even though everything in the Blackberry software looks normal. Again, I need to soft reboot to fix it. If anybody has experienced this or has a solution, it would be helpful also.
Thanks in advance.
my button seams to have quit working all together, soft reset doesnt help, tryed the hard reset mabe im,doing it wrong. it never ressets data basicly has the same efect as a soft reset.
not sure if its a hardware or software issue at this point. it randomly pops up the are you sure you want to quit txt.
Battory compleatly drained overnight, put it on chager and power button works again. No settings where lost that i see, kind of rules out a hardware issue.
I have identified the culprit, but I have not been able to find a solution.
As I said, my screen will not timeout. I have to manually hit the lock button to turn the screen off. Also, the softkeys stay lit. I started going through app settings, etc. No luck. I began to notice after reboots and battery pulls that it only started occuring after I entered mode (*#0011#) to fix the wifi disconnect issue.
After doing that, the screen will no longer timeout. So, at this point, I either have to deal with wifi turning off and on randomly, or a screen that won't go dark on its own.
Can anyone help?
I've run into this issue with a few ROMs on this phone now, notably Blisspop but a few others as well. When I turn the screen off or it times out I'll have to do a hard reset in order to get the screen back on, on occaison. I's not the end of the world, but it's kind of annoying. Has anyone else had this issue?
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
XDA Visitor said:
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Dalvik cache trick throws a wrench into things, but I used to have a similar issue with an older device - the screen wouldn't come one, but the hard button backlight would - pulling the battery and rebooting relieved the problem for that fit. I ended up scaling down the max processor speed (as it was being overclocked on the current custom ROM) back to the stock value. The problem went away at the point. But that was for my device, and because yours requires a dalvik cache wipe, it is probably a different cause.
At any rate, please go ahead and create an XDA account. Then, venture over to post in the [Q&A] Help thread. Ask away! (Noob friendly) thread, (or at least) in the > OnePlus One > ONE Q&A, Help & Troubleshooting forum. Your device experts can be found there.
Hope this helps, and good luck!
When i receive a phone call the screen turns off when i put it to my face, but when i move it away the screen never turns back on. I can't hang up the phone i end up having to restart the whole damn thing. Anyone else experienced this?
Yes I have the same issue going on now. I'm trying to see if there's some kind of manual over-ride or if the phone can cycle the screen on and off with just the side button / power button click alone. Would be fantastically helpful.
Mine is not dirty, it is broken, I have tried cleaning it with no avail.