I received a calendar event notification on my lock screen yesterday. It kept my screen on for 3 hours and drained the battery down into the teens. My Note was in a case and when I pulled it out it was very hot. Anybody else have this happen? I am new to touch wiz. All my phones have been Nexus devices. I haven't applied the OTA updates yet so maybe those will fix it. I may play around around bit to see if I can recreate the problem before I update. Until then I have turned off lock screen notifications.
Pretty sure the home button wasn't being held down. I will look into that too.
Brewbud said:
I received a calendar event notification on my lock screen yesterday. It kept my screen on for 3 hours and drained the battery down into the teens. My Note was in a case and when I pulled it out it was very hot. Anybody else have this happen? I am new to touch wiz. All my phones have been Nexus devices. I haven't applied the OTA updates yet so maybe those will fix it. I may play around around bit to see if I can recreate the problem before I update. Until then I have turned off lock screen notifications.
Pretty sure the home button wasn't being held down. I will look into that too.
Click to expand...
Click to collapse
Also looking to see if there is a solution for this. I am also having the same issue. I've had it happen three times already and it completely drained my tablet. Couple times I caught it before it turned off and the tablet was hot, like yours. I'm stock. Received last 2 ota updates. Mine sits in a pouch ( if that makes a difference with sensors or anything. ) I set the screen time out to be 30 secs. Still doesn't work. Something broken with the notification.
Related
Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
you guys try to do a reset on the watch yet?? not just a reboot..
Any updates on this? I'm having the same issue
Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...
Same issue here as well
OK, so now that I have lollipop, I have noticed a few things are broken and I am wondering what other problems others are having and what we can collectively do to try and fix them.
If I tilt and say "OK Google" and "Show me my heartrate" I get a momentary black screen and then back to the watch face. Happens with both Fit and the Moto app
I noticed it happens more when I have a partial notification card showing. If I clear the notification and turn the screen back on it will usually work right.
Also, downloaded the update while on the charger then ran the update with 100% battery, now three hours later I'm down to 34%. Yikes. I've had the watch for only a couple days so I'll give it more time to settle in.
David
FWIW whenever i run updates i lose an easy 15%+. all of that on-screen time and processing shows the inefficiencies of the processor. i generally try to re-charge it after any update.
additionally its been reported several times to perform a factory reset on the watch after any update. i haven't performed one yet myself, but by battery life has been on-par with before.
lollipop
Do you have lollipop on your phone? I notice that when i got lollipop on my 360 the battery went down pretty quick! I had the 360 connected with my M7 on kitkat! Now i have my 360 connected with my Nexus 6 and its working ok!
DaveTN said:
OK, so now that I have lollipop, I have noticed a few things are broken and I am wondering what other problems others are having and what we can collectively do to try and fix them.
If I tilt and say "OK Google" and "Show me my heartrate" I get a momentary black screen and then back to the watch face. Happens with both Fit and the Moto app
I noticed it happens more when I have a partial notification card showing. If I clear the notification and turn the screen back on it will usually work right.
Also, downloaded the update while on the charger then ran the update with 100% battery, now three hours later I'm down to 34%. Yikes. I've had the watch for only a couple days so I'll give it more time to settle in.
David
Click to expand...
Click to collapse
Anyone have problems with the unlock your phone feature using a different launcher like nova. I have mine paired to my nexus 6 and it works great on Google launcher but only about a third of the time on nova, thanks
Sent from my Nexus 6 using Tapatalk
I recently bought an unlocked Amazon Fire phone ($125; it came loaded with Fire OS 4.6.4). The phone seems solid and well-built. The only change I made to the stock phone so far was to load Google Play, using the instructions on the spinyourfire website.
I have noticed that the screen timeout does not work anymore. Whether I set the interval to 15 secs or any other setting, the phone does not go to sleep until a good 4-5 minutes have elapsed. I Googled this problem but did not find anything. Has anybody run into this, or am I overlooking something obvious? Thanks much!
Do you have a screen protector? I had to remove mine because it was messing with the proximity sensor.
I do have a screen protector. Did you experience similar problems with your phone (screen timeout not working), and did they go away after you took the screen protector off? I'd never though of that...
philharvey said:
I do have a screen protector. Did you experience similar problems with your phone (screen timeout not working), and did they go away after you took the screen protector off? I'd never though of that...
Click to expand...
Click to collapse
I had a tempered glass screen protector. I didn't notice that specific issue. The 2 major issues I immediately encountered was (1) the screen would remain off during a call and (2) the home button wouldn't wake the phone up. Maybe either of those issues are also happening to you?
I did not experience the 2 problems you described (screen off during a call, and home button not waking the phone up). My screen timeout problem is really intermittent: it seemed to work fine yesterday as the phone went to sleep after 15 secs of inactivity, as I wanted it to. Today, the phone remained stubbornly on for 10 mins and refuses to go to sleep.
I wonder if sideloading Google Play has something to do with it. I'll try uninstalling the Google Play stuff and see if it affects my timeout problem. I will update the thread.
I may have stumbled on the cause, as well as the solution, of my problem: apps running in the background may have prevented the phone from going to sleep.
I used the "Quick Switch" feature on the phone to display all running apps, then killed most of them by dragging them towards the top of the screen. Now my phone is going to sleep within 15-30 secs of inactivity, like I wanted it to. I hope this thread helps someone else struggling with the problem.
philharvey said:
I may have stumbled on the cause, as well as the solution, of my problem: apps running in the background may have prevented the phone from going to sleep.
I used the "Quick Switch" feature on the phone to display all running apps, then killed most of them by dragging them towards the top of the screen. Now my phone is going to sleep within 15-30 secs of inactivity, like I wanted it to. I hope this thread helps someone else struggling with the problem.
Click to expand...
Click to collapse
That's good news. Glad you didn't have to rip off your screen protector. Now all you need to do is figure out which app in particular is keeping your phone awake.
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've had the note10+ for about a month now. And as of recently I keep getting random vibrations. I downloaded nice catch. All it shows is system notification.
Galaxy note 10+ random vibrations
I've noticed this since the last update.
It doesn't happen after a restart for a couple of hours but after that, it happens after interaction with the touch screen. Nice catch doesn't catch it because it logs only from apps. Even the edge panel doesn't get registered. Initially I thought it was my case causing a touch on the part of the screen that vibrated but even after a case change the issue is still there. Its concerning but not too serious.
And it seems I'm not alone.
Several users of other galaxy phones have also faced a similar issue.
The vibration is very short, like a single tap, like when you type on the keyboard.
And I've even managed to recreate it by putting my hand very close to the screen (once it starts acting up)
It mostly happens when the device is warm.
My NFC is left disabled. And Bluetooth is off.
Only WiFi is on all the time.
This has been puzzling me for quiet sometime.
Could be NFC icw cover with cards in it?
With NiceCatch module of GoodLock (or NiceLock) it is logged and shows you what caused the system (or other-) sound and vibrations...
Sorry folks the day I posted this I was involved in a head on motorcycle accident with a gmc Sierra. I am alive and well. And now I have the fold3 obviously I never figured out what caused the unusual vibrations.... but oh well