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!
Related
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Blitztorm said:
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Click to expand...
Click to collapse
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
pigstew said:
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
Click to expand...
Click to collapse
Good Lord!! It actually did work, but how to explain the ART and Dalvik thingy?!
thanks
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
mtshure said:
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
Click to expand...
Click to collapse
The OE2 tar file shouldn't wipe your phone as it is not a full wipe tar. I don't know if your phone would do it with it's reboot problem but a dirty flash of clean rom shouldn't wipe your phone either. However, a reboot during the middle of either of those would not be good. Flashfire does seem to be able to keep a phone from rebooting once it gets going or at least it has for me when I have been caught in a bad way before.
Problem Solved!!!
Thank you Tulsadiver for your suggestions. But is it okay to do odin without wiping anything?
I almost gave up after struggling several hours and thought about doing a factory reset, but the problem is solved now.
I found it weird that the soft key lights never turn on, so I thought that there might have been something wrong with the power management. So I turned the ultra power saving mode on (fortunately the phone didn't reboot before I did that), and it didn't reboot itself. I turned it back off then now the problem is gone!
I am happy with it now, and this might be one of the things to try if you experience a random reboot.
So basically, around 2-3 weeks ago my phone's screen started acting up. Usually it'd take me two tries when turning the screen on to actually get the touch screen working. As in, I turned the screen off, the touch screen doesn't register any touches, then I shut the screen down and try again, and it sometimes works. Now, this didn't bother me - I though, maybe there's some short circuiting, it may fix itself. Fast forward 2 days later. my touch screen now needs minimum 3 tries to work, up to 9 or 10 sometimes. Note that when my touchscreen starts working, it works without a problem, all 5 fingers until the screen is shut down. Then I did something that COMPLETELY broke it - I restarted my phone. The touch screen never worked then. Like ever. I could try 100 times and it wouldn't work. I'd take out the battery, let it reset nice and **** - it doesn't work. So the next thing I did was a factory reset in recovery - the phone is restored to functionality before restarting it. Now, I didn't shut down my phone for 2 weeks, nor did it run out of battery - it's the same. Today, I've restarted it and the same problem occurred again - touchscreen completely unresponsive. So, I did the same thing as before, only this time I tested dalvik-cache and cache separately - none worked in any combination without a factory reset - at this point, I'm already certain the problem is in the software, and not the hardware. So, guess what - phone was restored to functionality with 2-3 tries after that reset. Then - an even more peculiar thing - I've enabled the touch gestures to turn on a screen. Most of the time when the screen turns on with a double tap, the password screen reacts to touch, but there are cases when I double tap, it opens, and then it doesn't work - it doesn't register touches. Most of the time, though, it doesn't even open the screen through the double tap. I've also noticed that it would sometimes happen when running - for an example, I play a lot of Cytus and Deemo - whenever there would be a break of more than 2 seconds between taps, if I didn't tap in between (so, when there are no beats to hit), it would sometimes completely ignore the next tap, as if the digitizer turned its touch detection off due to inactivity...
At this point, I have no idea what it is. I know that it's not the proximity sensor which I had originally suspected, and I know that the problem lies somewhere inside Android data folders or something a factory reset wipes. However, I have no idea where. My phone has been rooted and runs xposed, although I haven't used it since the reset - I wanted to flash a custom rom but found none other than Mstars 5.0 fresh install ROM. So, if anyone recognizes this problem, can I fix it with a new ROM flashed? Can I fix it by finding the **** that's causing this and always delete it at startup via script? Or should I just attempt to fix my phone in a repair shop?
Hello and thank you for using XDA Assist,
please ask in this section:
Android Q&A, Help & Troubleshooting
The experts there will be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist
So this is what happened, a couple of days ago I was using my Nexus 5x normally when it turned off. I tried to turn it on but nothing happened so i tried to turn it on whith the power and volume buttons it turned on but the screen froze when the loading the colored dots. I tried to turn it on again with safe mode and it worked but the screen froze again after a couple of minutes. Now this freezing thing happened every time i tried to turn on the phone.
A friend told me to wipe the cache partition but nothing happened. the told me to factory restore it, the I was able to turn on the phone but started to reboot some times or just froze when starting, so another friend who knows about android phones told me to do the wipe data/factory reset and thats when the phone turned off while wiping the data, now the phone doesn't turn on at all. I saw the red light like when the phone is out of battery so I started charging it but the red light started blinking a couple of times then stoped.
One more thing, one of the times I turned it one it looked like it was everything ok except that the finger reader wasn't working and there was no google imprint menu so I restarted the phone and de finger reader was working but the phone was rebooting spontaneously. This happened before trying with the wiping the cache and doing the factory reset.
Thats basically what happened, is there something I can do?
My phone is the LG Nexus 5x 16GB whit android nougat 7.0
XDA Visitor said:
So this is what happened, a couple of days ago I was using my Nexus 5x normally when it turned off. I tried to turn it on but nothing happened so i tried to turn it on whith the power and volume buttons it turned on but the screen froze when the loading the colored dots. I tried to turn it on again with safe mode and it worked but the screen froze again after a couple of minutes. Now this freezing thing happened every time i tried to turn on the phone.
A friend told me to wipe the cache partition but nothing happened. the told me to factory restore it, the I was able to turn on the phone but started to reboot some times or just froze when starting, so another friend who knows about android phones told me to do the wipe data/factory reset and thats when the phone turned off while wiping the data, now the phone doesn't turn on at all. I saw the red light like when the phone is out of battery so I started charging it but the red light started blinking a couple of times then stoped.
One more thing, one of the times I turned it one it looked like it was everything ok except that the finger reader wasn't working and there was no google imprint menu so I restarted the phone and de finger reader was working but the phone was rebooting spontaneously. This happened before trying with the wiping the cache and doing the factory reset.
Thats basically what happened, is there something I can do?
My phone is the LG Nexus 5x 16GB whit android nougat 7.0
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
> LG Nexus 5X > Nexus 5X Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.
Good luck
Hello all, I have a problem and was wondering if anyone could help or maybe is someone has the same problem.
I have the s7(SM-G930T) and am rooted running Echoe rom v1.5... Everytime my phone is charging for more than 10minutes or so it becomes unresponsive. When I go to check it while its on the charger the screen stays black when I click the home or power button but the capacitive button lights come on. Sometimes I can get the screen to come on but most of the time I have to hard reset it and then is fine again until its back on the charger. I've went back to stock and re-rooted a hand full of times but it just keeps happening. After a fresh flash of the Echoe rom it's fine for a couple hours and then happens again. Anyone have any ideas?
Sorry for the long post. Just wanted to be able to explain exactly what was happening
sparky2029 said:
Hello all, I have a problem and was wondering if anyone could help or maybe is someone has the same problem.
I have the s7(SM-G930T) and am rooted running Echoe rom v1.5... Everytime my phone is charging for more than 10minutes or so it becomes unresponsive. When I go to check it while its on the charger the screen stays black when I click the home or power button but the capacitive button lights come on. Sometimes I can get the screen to come on but most of the time I have to hard reset it and then is fine again until its back on the charger. I've went back to stock and re-rooted a hand full of times but it just keeps happening. After a fresh flash of the Echoe rom it's fine for a couple hours and then happens again. Anyone have any ideas?
Sorry for the long post. Just wanted to be able to explain exactly what was happening
Click to expand...
Click to collapse
I've never had this issue before. Sounds like the Sytem UI is becoming unresponsive... Try wiping the cache, freeing ram, and use greenify(great application) to hibernate apps.
KillerClaw321 said:
I've never had this issue before. Sounds like the Sytem UI is becoming unresponsive... Try wiping the cache, freeing ram, and use greenify(great application) to hibernate apps.
Click to expand...
Click to collapse
I've tried wiping the cache and freeing ram but haven't used greenify. I will try that to see if it helps, thank you
Edit: unfortunately greenify did not help. I guess I'm going to have to live with restarting it after charging or just revert back to stock. Thank you for your suggestions.
If any one else is having the same problem I was I fixed it by picking to keep the s7 apps instead of using the note 7 ux apps in the aroma installer on the echoe rom