Hi,
Around August this year, after some firmware update, my phone started to reboot spontaneously one or more times per day. I didn't find any particular circumstances for this behavior -- it may happen when I'm typing a message, scrolling Instagram or just laid on a table... The most problem is that it can reboot at night time (while charging) so after reboot, the alarm clock I've set at the evening doesn't work %()
Any ideas how to fix this really annoying bug?
Thanks.
You are on stock without modification? Root? Substratum... Etc?
Related
I've read a lot about people having issues with their alarms. This morning, I had the first one of those.
Alarm was set for 7.30, when I woke up around 8.30 and picked up the phone, it seemed the clock was stuck at 4.30 am and took about 3 seconds to update (not the fancy HTC clock, the one in the notification bar!). I went to bed last night around midnight and didn't touch the phone all night.
Alarm did not go off even belatedly once the clock updated. This is also not a recurring alarm issue since I only set this one last night. Also not a sound issue, the volume was up quite high and not mistakenly set to silent as has happened to some people.
Has anyone else experienced this?
(and yes, I'm still running a T-Mobile G2 stock ROM, too much of a chicken to update to the new leaked ROM! Hoping HTC will roll it out officially ASAP!))
Thanks for any input!
I've had the same problem with my Hero, and I had the same problem with my old XDA Orbit (also made by HTC) that was running Windows Mobile.
I wonder if it's a hardware issue with the way HTC interfaces their firmware with the hardware clock or something like that.
i do also have the same problem, sometimes. it helps to simply reboot the phone. i don't know why it goes in some kind of "deep-sleep", but i hope it will be fixed in the next update.
I've had the same thing (ish) but it was just a crash - I'd been installing and uninstalling apps all night, didn't reboot my phone before going to bed at 11pm. When my alarm failed to go off, I looked at the clock and it was stuck on 11.03pm and the screen wouldn't slide down to unlock, so it had crashed just after I'd gone to bed.
Since then, if ever I'm installing and uninstalling and testing apps and fiddling with settings, I always reboot when I'm done just to make sure nothing's misbehaving. Not had the problem since.
I tend to turn on the alarm each night and turn it off in the morning.
Not had an issue with it failing yet.
Not that that is the right way around it as it should go off at the same time each day when left on all the time.
But it may help if some are having a recurring issue.
I'm experiencing some problems after getting the Froyo update and then the latest OTA update. Not sure how to correct these, and would appreciate some feedback..
After Froyo update:
When using alarm clock, it will go off and not display the Dismiss/Snooze buttons to turn off the alarm. Even if I navigate into alarm options and uncheck it, still keeps going. Only way I can get this to turn off is by removing the battery. Not fun to try doing at 4am in the dark after I just had the crap scared out of me by the alarm. This doesn't happen every day, only a couple days a week, very randomly.
After latest OTA update:
When I am typing in text messages, the haptic feedback suddenly stops working. Doesn't happen when i type letters, press menu buttons, or touch anything else on the screen. Sometimes it will randomly start working again, other times it doesn't work until i put the phone in sleep and pick it up a few minutes later.
anyone else having the market force close occasionally when try to update apps?
Yep, I do.
Hello
I'm getting 1-2 restarts almost daily, and what is consistent is that the phone will short-vibrate once, then a pause of about 8 seconds, then two quick short-vibrates in succession (about .25 sec apart) and then the phone restarts.
This can happen when in my pocket, it can happen while actively using it, can also happen when just sitting there on my desk with screen on. I haven't seen a pattern regarding app use or activity triggering the restart.
I posted a question a month ago about how people with Androids can troubleshoot restarts. There HAS to be a way (app, etc) that allows you to see crashlogs **without** rooting your phone. Yet, I got no replies here to my last post.
Is this really such a hard thing to do with Android? Please, tell me if I'm wrong and missing something completely obvious. I'm right now factory resetting my phone cause I can't figure what's causing this.
Thanks in advance for the help.
I have the some.
Any once have fix for this random reboots ?
Same problem at any moment. And sometimes it stays at a boot loop.
I have changed the firmware to a custom one and the problem persist.
I've had two random reboots after my 2:30am finishing time with the update. Once during the night, because my Gsam battery said it was only on for 33 minutes when I had woken up. And just a few minutes ago??
I think they are both "not so random" though. This morning and this afternoon, both corresponded with receiving a text message? I use YAATA, which has "chatheads".....So, I'm not sure if that caused it or what? I've used it many times since then, and in-between, with no issues, but those two reboots were the same time I received a text?
Factory reset always solves after update glitches...usually
Mine has been doing this every night and it's very inconvenient because I have enter PIN to boot so I can't use the alarm. I did a factory reset after updating.
Mine has not done it again since starting this thread... I had a text sending error and had to turn off/on data, (but I also had 2 text messaging apps installed at the time to test out, so this could have been my fault). I also had a Playstore issue where the Playstore didn't load....But I also installed the newest APK I downloaded here on XDA (once again, could have been my fault). A restart fixed these issues. I also "Wiped the Cashe" in the stock recovery while I was trouble shooting.
Initially, right after the Nougat upgrade, I did a wipe/factory reset before I let it boot the first time. I haven't had any issues since yesterday afternoon, but if I have any more I'll probably do a factory restore and start over from scratch.
I have not had any other issues that I see others are having (like with Instagram)
I have noticed almost every single night for the previous two weeks my Essential phone restarts itself. The only way I can tell this is when checking my phone in the morning the pin lock comes on and says pin must be entered after restarting. This happened with the November security update and still happening after downloading the December security update. Is anyone else noticing this?
From the title I thought you found randomly placed red boots every day just walking around..
Mine has done that a few times but it's not every night. I'm running the oreo beta and have automatic updates enabled so I assumed it was due to that.
Happening to me too and it's causing my alarm to not go off in the morning (using Sleep as Android). Been late to work twice now this week because of it. Super annoying, probably going to reach out to Essential support for it.
Edit: Found this: https://www.reddit.com/r/essential/comments/7hqf8s/ph1_restarts_every_night_when_charging/
And that seems to be the case on my phone - it's not restarting overnight but it is going into doze and requiring the additional security when waking. This, unfortunately, is also suspending Sleep As Android. So I've tried excluding it from the battery optimizations to see if this will help.
bavarianblessed said:
From the title I thought you found randomly placed red boots every day just walking around..
Mine has done that a few times but it's not every night. I'm running the oreo beta and have automatic updates enabled so I assumed it was due to that.
Click to expand...
Click to collapse
Ha thanks
ShadowDrake said:
Happening to me too and it's causing my alarm to not go off in the morning (using Sleep as Android). Been late to work twice now this week because of it. Super annoying, probably going to reach out to Essential support for it.
Edit: Found this: https://www.reddit.com/r/essential/comments/7hqf8s/ph1_restarts_every_night_when_charging/
And that seems to be the case on my phone - it's not restarting overnight but it is going into doze and requiring the additional security when waking. This, unfortunately, is also suspending Sleep As Android. So I've tried excluding it from the battery optimizations to see if this will help.
Click to expand...
Click to collapse
Well I guess that's good to know. The aggravating thing being that it resets the Smart Lock when doing this. So now " I " have to restart my phone every morning so I can reset the Smart Lock so my phone stays unlocked while connected to my Android.
Final-Mac said:
Well I guess that's good to know. The aggravating thing being that it resets the Smart Lock when doing this. So now " I " have to restart my phone every morning so I can reset the Smart Lock so my phone stays unlocked while connected to my Android.
Click to expand...
Click to collapse
Coming back to this, because I'm still having issues. Sleep As Android gets suspended overnight. It initially was happening randomly, now it seems to happen every night.
I still believe the phone may be crashing, just not completely rebooting. I noticed that a reddit app I use (Relay) was using much more CPU recently and making the phone warm, draining the battery... while previous use didn't really do this. So I went to clear the cache for the app from system settings.
The phone froze... touchscreen became unresponsive. I gave it 15-20 seconds and it was still stuck so I tried to hold the power button in an attempt to find which button combination would force a reset. During this time, the phone decided to respond again and took all of the input I had tried at once - the power menu came up and it returned to the lock screen.
At the bottom of the lock screen - "Unlock the phone to use all features and data" just as it shows up every morning after "deep doze"
But the phone's uptime didn't restart. 131 hours and counting now.
So maybe this is a warranty-able issue after all.