Related
Does anyone else suffer from random reboots with there device? it does it twice a day or more for me???
Is there anything i can do to stop this issue from happening again?
I.e wipe user data???
I've had it once or twice. Presumably a rogue app or a bug in the system.
I haven't suffered from a random reboot at all since having the phone on the second day of availability in the UK.
Then again, I haven't rooted mine, unlike others...
Yes I have had a few reboots in the few couple of days. Been ok since though
0Mudassar said:
Yes I have had a few reboots in the few couple of days. Been ok since though
Click to expand...
Click to collapse
Im glad its not just me hopw they will fix the issue in the volume fix!
garner said:
Does anyone else suffer from random reboots with there device? it does it twice a day or more for me???
Is there anything i can do to stop this issue from happening again?
I.e wipe user data???
Click to expand...
Click to collapse
Not a single crash or random reboot so far. I rebooted last Friday after charging my battery and it's been running since without problems. My best guess is that culprit is one of your applications that you've installed, especially any application that tries to do something with Android and the device itself.
kristovaher said:
Not a single crash or random reboot so far. I rebooted last Friday after charging my battery and it's been running since without problems. My best guess is that culprit is one of your applications that you've installed, especially any application that tries to do something with Android and the device itself.
Click to expand...
Click to collapse
I had these reboots on a G2X and it drove me bonkers so I am always worried about phones doing it and I watch uptime like a hawk. Nexus has been rock solid since I turned it on the first time. No reboots. Sometimes it's apps and sometimes your use case just exposes a bug in the OS. Try doing a wipe and installing a few apps at a time so you can figure out what's causing it n
I had a couple within the first few days... nothing for a while...
This is just speculation, but I remembered seeing a thread somewhere in another form, in which a user with another device with the same random reboot problem was advised to check his sim card. A bad sim card may "vanish" for a while, causing the device to reboot. Again, just speculation, or if you wish, a hypothesis you can check.
I have something similar, the first time was when I was charging my phone, I woke up in the morning and I found my phone off and hot as hell. Battery pull and everything went perfect. then it happened to me 5 times, the phone freezes and turns itself off, then I have to do a battery pull! the last time was today I was listening to some music, then the music went weird, then the phone froze and turned itself off.
I called Three for a new phone as I have it for under 14days
It looks like there is an issue that google hopefully acknowledges like they did with nexus s.
I was listening to music on my way down the sidewalk thus morning and the mp3 started doing a loop of about 1 sec of the track over and over. Finally heard a pop and it went silent. Had to do a battery pull when I got on the subway.
Then on the subway about 10-20 seconds into a track after starting some music back up the track restarted. So I stopped playback thinking it may happen again.
I'll try to do what I can over the coming days to recreate this.
Sent from my Galaxy Nexus using Tapatalk
bad file or maybe filesystem?
mobilehavoc said:
bad file or maybe filesystem?
Click to expand...
Click to collapse
I would think that would cause more problems than that. I was listening to some tunes for a bit last night with no issue. And the issue this morning happened with two different tracks.
I had added a battery gauge widget to my home screen last night, I removed it just now. I'll try to recreate the problem from here without adding more apps or widgets. If I can successfully recreate it I'll try to hook up adb and get some logs.
Sent from my Galaxy Nexus using Tapatalk
I'm having random reboots too. I'm suspecting its something to do with either GO SMS or SlideIT. Do you guys have any of these installed too?
Luckyman79uk said:
I'm having random reboots too. I'm suspecting its something to do with either GO SMS or SlideIT. Do you guys have any of these installed too?
Click to expand...
Click to collapse
None of them and no reboot so far.
Gesendet von meinem Galaxy Nexus mit Tapatalk
I'm getting another problem now. I've taken off GO SMS so I dont think its that. But when I get a notification (i.e SMS, email), I go to wake up my phone and the unlock screen appears. However it wont recognise any touches on the screen, then sometimes it will come back to life and other times it will reboot itself.
Never had a random reboot, I have go SMS installed.
Sent from my Galaxy Nexus using XDA App
Just had a random reboot with none of the aforementioned apps installed.
I was having random reboots when the phone was just sitting there with the screen off.
I had SetCPU under clocking when the screen was off, I removed SetCPU and my random reboots went away.
All the sudden, my display keeps turning on for no apparent reason. I have to push power 5 or 6 times to put it to sleep and it does the same thing every 10 minutes or so. If anyone knows what the issue may be feel free to drop a comment. Thanx.
Sent from my Desire HD using XDA
You installed an new app? I have an app ClockSync that will turn the screen on and sync, then turn the screen off.
You could hook up to your computer and run a logcat of it happening, that should identify the cause.
Din't have clock sync but I do have lots of Go apps installed that might be causing this. I will pull a logcat if it happens again. Thanx Andy.
After installing the 5.0.1 update on my ATT Note 4 I noticed the red light was on when I put my phone down. After testing it for a while the heart rate sensor red led comes on when anything touches it. I restarted phone and killed all running apps but nothing stops it. Sometimes it goes off after a few minutes and sometimes it doesn't happen but sometimes it comes on and stay on until whatever made contact with the sensor goes away.
So for now I can't lay my phone down on it's back because the sensor can come on. I can't put it anywhere where anything could touch the sensor because it will eventually come on. No pocket nothing. I never had this problem until right after the 5.0.1 update.
For now I'm stuck putting my phone face down and carrying it because that is the only way I can be sure the sensor won't light up and kill the battery.
I may have never noticed this except that it took the update so long to download and it was bedtime when I finished and noticed the light.
Anyone else seeing this or more importantly anyone able to tell me how to stop it?
@phobia09 made this post in one of the "lolipop is out" threads.. see if it helps you...
http://forum.xda-developers.com/showthread.php?p=59666946
Basically start s health, take a heart rate reading and close s health.. his light stopped coming on
Tried S Health but that didn't work.
Thanks for the info. I previously started SHealth and took pulse, stress and PulseOX readings but it still comes on.
What running the heart rate check in S Health did for me was stop it temporarily. Within an hour of doing that, it was back. Wish it had been permanent. Leave it to AT&T to screw up, I don't believe international N4's had this issue.
Sent from my SAMSUNG-SM-N910A using Tapatalk
This is what I have done so far but it has not solved the problem. I still can't put my phone in my pocket or lay it with the back down.
Wiped the phones cached partition
restarted phone several times
removed battery for about 15 minutes
cleared data and cache from Shealth App
disabled Shealth app
It seems like starting SHealth and taking your heartbeat stops it for a short time but the problem comes back quickly wether SHealth is running in the background or not.
I can put up with some issues but I can't live with this. It seems pretty serious and is a big battery drain.
phobia09 said:
What running the heart rate check in S Health did for me was stop it temporarily. Within an hour of doing that, it was back. Wish it had been permanent. Leave it to AT&T to screw up, I don't believe international N4's had this issue.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Yeah they do. I read the other Note 4 forums too and this issue appears on all Note 4 versions running 5.0.1
Same issue here. I ended up doing a factory reset and starting over with Lollipop. So far, the sensor has not lit up again, but then, I have not started up S Health since resetting the phone. When it was happening it only lit up when I lay the phone down on a light colored surface. On a dark surface, it didn't light up at all.
Fixed
I was told it was Google FIT in another forum and it was a known problem. Uninstalled FIT and now everything is fine!
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.
Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.
Damnit, I wish I didn't update.
Battery is also noticeably worse.
airjordan223 said:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Click to expand...
Click to collapse
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
antknee2016 said:
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
Click to expand...
Click to collapse
Can you found a way to fix it?
Enviado desde mi SM-N920I mediante Tapatalk
The first issue is because the watch now comes on in ambient mode first. Even if you don't use ambient mode. It sucks. Luckily i use Watchmaker for my watch face so I went in and made all the parts (hands date etc...) to be visible in ambient mode.
I have noticed that if I wait a couple of seconds the notification does appear on my watch screen but it is after the vibrate, not immediate. I thought it wasn't showing up at first too. Still, I wish it was quicker as I look right away.
Sent from my SHIELD Tablet using Tapatalk
I went back to using Facer for my watchface and the delay is gone.
Also did they completely remove the restart option? Now it's just power off, and then press and hold the side button.
I'm experiencing both issues as you do on 6.0.1.
Also yes, reboot option is gone from update.
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Click to expand...
Click to collapse
Reboot is not reset...
I've also noticed that theater mode does not work after the mm update (unrooted, ota). I usually set it to theater mode at night to avoid burn in and just because I don't want it on all night. Now, it looks like it's blacked out, but when I wake up, the charging screen is lit up. Anyone else getting this?
I have the exact same issue after the update. Theater mode will not keep the display off if the watch is being charged. Off the charger, it works as expected. Quite an annoying bug.
If I turn ON the theatre mod with double press the power button before I put the clock on the charging dock, after that screen continue charge with screen off.
For me it's work.
Can anyone try it?
Sent from my D6503 using XDA Free mobile app
Just tried that - doesn't work for me. Screen turns off but once I put it on the charger, it comes back on after a few seconds. I'm watching it and it's still on a few minutes later.
Same here. Screen always turns back on
I'm getting the first bug the OP mentioned havn't noticed the second one though.
However the first bug is annoying enough, hopefully there'll be a quick patch.
Little patience, update to Marshmallow is great.
Here's what I mean with screen off when charge:
So in the morning until you take it out of the dock and go to work.
Sent from my D6503 using XDA Free mobile app
still on 5.0.1
man i just boughjt it 2 days ago and battery sucks,now i am trying to update cause i heard batter improved,but i cant ,watch start download but take too long and then show me a message charger to update blah blah but phone is charger is over 90 percent i have reset phone and uninstalled app many times this is ridiculous now i know why motorola was giving away this pos when yopu buy the 64gb moto x pure edition arrrrgggg
Srandista said:
Reboot is not reset...
Click to expand...
Click to collapse
Sorry I read wrong...but wouldn't you just use the power off option and then turn back on to reboot?
I am curious whether anyone else is having this problem as I cannot find anything about it online. I have an issue that my Pixel XL starts turning DND mode on and off repeatedly with no interaction from me. It cycles back and forth every second or so and the DND icon comes and goes from the notification bar as it does this. This also seems to run down the battery and heat up the phone. No clearing out of applications seems to fix this but if I reboot the phone it goes away. I should also note that I find my Pixel goes into DND mode all the time unintentionally . About half the time I take it out to make a call I see that DND is on. This happens even when it is not cycling like this repeatedly. Anyone else having problems like this?
Are they any DND rules setup that might be triggering? Do you have any other automation app installed, like Tasker, that could be causing thisre
I have seen this happen on my phone a few times - during the day, which is against the schedule that I set. It's not often enough to bother me, but it is somewhat worrisome.
These bugs man!
also experienced it. i wondered if it was impacted by android wear because i dont see it when i dont have my watch on.
i also noticed it goes into that DND mode when you make a call. so maybe it's not coming out of it when you hang up
DND is flaky
dr_gibberish said:
I am curious whether anyone else is having this problem as I cannot find anything about it online. I have an issue that my Pixel XL starts turning DND mode on and off repeatedly with no interaction from me. It cycles back and forth every second or so and the DND icon comes and goes from the notification bar as it does this. This also seems to run down the battery and heat up the phone. No clearing out of applications seems to fix this but if I reboot the phone it goes away. I should also note that I find my Pixel goes into DND mode all the time unintentionally . About half the time I take it out to make a call I see that DND is on. This happens even when it is not cycling like this repeatedly. Anyone else having problems like this?
Click to expand...
Click to collapse
I tried using DND when i first got the phone but it was inconsistent and flaky.
Went back to silence premium and havent had any issues since.
i have the same problem, but also using android wear.. very odd.
I also have a smartwatch connected. Perhaps the bug is related to Android Wear.
nabbed said:
I also have a smartwatch connected. Perhaps the bug is related to Android Wear.
Click to expand...
Click to collapse
So that's really interesting. I have a first gen Asus Zenwatch and I removed the Zenwatch Manager app late last week and the problem appears to have stopped. I still get the occasional DND turning on when I don't think I have activated it, but the cycling back and forth appears to have stopped. I should also note that I apparently got an upgrade to the watch firmware last week (it said upgrading when I woke up) so this could have resolved the issue as well. Regardless it does not seem to have happened in several days.
Android wear related I'm sure. When I go to hit volume down it says dnd- android wear
Sent from my Pixel XL using Tapatalk
Im using android wear and i am seeing the same problem.
Same here. Huawei watch.
Sent from my Pixel XL using XDA-Developers mobile app
Only notice it when on phone call. Zenwatch 2. But, currently my watch isn't paired with phone.
Happens with Samsung Gear Fit 2 as well.
Sent from my Pixel XL using XDA Labs
Here to add to the Android wear list, using an LG urbane.
Someone in another thread suggested deleting the three default automatic rules for do not disturb. I did that a couple days ago and haven't had the problem since. I have an Android Wear watch connected too.
Happens to me also, while connected to my Misfit Ray.