I got my 360 a couple of months ago and I had no issues with it at all until a couple of weeks ago. Sometimes it would stop charging at around 60%. Started happening more frequently and then I noticed when it had been on the charger for a while, the display would brighten and then dim and repeatedly pulse like this and quit charging. I only found one reference online about this and it suggested a problem with the internal charging hardware so I took it back to AT&T and exchanged it for a new one under warranty. The new one is doing the same thing so now I am wondering if it is a 5.0.2 issue but I am not seeing any outcry over it.
I am kind of at a loss as to what to do here. Looking for suggestions from other users. Have any of you heard of this problem and can point me in a direction for help? My next step is to contact Motorola but not looking forward to that.
Thanks in advance
Do you have watchmaker installed for faces if so there is a bug in 3.3.2 it should be resolved in 3.3.3 testing beata now this is refering to the bright to dim while charging
Sent from my SAMSUNG-SM-G900A using Tapatalk
Yes I do have watchmaker! I have Facer as well but it has been crashing for weeks now so rarely use it. Will suck to lose watchmaker even for a little while but if that fixes it, then it will be a big relief. Thanks for the tip, i will give it a try.
Temp solution it to use a stock face
Sent from my SAMSUNG-SM-G900A using Tapatalk
Theres lots of good others anyways, use the moto connect for now for a custom one. I know its not the best but it still works...
Ratman2356 said:
I got my 360 a couple of months ago and I had no issues with it at all until a couple of weeks ago. Sometimes it would stop charging at around 60%. Started happening more frequently and then I noticed when it had been on the charger for a while, the display would brighten and then dim and repeatedly pulse like this and quit charging. I only found one reference online about this and it suggested a problem with the internal charging hardware so I took it back to AT&T and exchanged it for a new one under warranty. The new one is doing the same thing so now I am wondering if it is a 5.0.2 issue but I am not seeing any outcry over it.
I am kind of at a loss as to what to do here. Looking for suggestions from other users. Have any of you heard of this problem and can point me in a direction for help? My next step is to contact Motorola but not looking forward to that.
Thanks in advance
Click to expand...
Click to collapse
I have the same problem, my watch turned dead , I didn't know WatchMaker was causing this, for the moment my moto 360 is returned (SAV) (alternate.be)
I hope they will give me back a new one :'(
I did a video showing the problem on my youtube channel (lucaspart7) can't put link this is my first post XDA doesn't allow to
Ratman2356 said:
Yes I do have watchmaker! I have Facer as well but it has been crashing for weeks now so rarely use it. Will suck to lose watchmaker even for a little while but if that fixes it, then it will be a big relief. Thanks for the tip, i will give it a try.
Click to expand...
Click to collapse
Facer is the biggest battery hogger in Moto 360 if u have it installed.
Even if u dont use Facer it still has its processes running in the background.
I too faced this issue earlier but a reset fixed this for me.
Related
Hey guys i think ive got a problem, i have my a100 for a week now and i'm happy with it. But one time i used it, suddenly it reboots this was a few days ago. And just this moment i want to wake up it from sleep mode, but it was turned off, although it still has 50 % of battery. I think it's not that bad but i want to be sure that it is not a hardware problem. You have an advice?
Thanks
Try to reproduce the problem, and if you're able to, then just return it for a new one.
Wacko said:
Hey guys i think ive got a problem, i have my a100 for a week now and i'm happy with it. But one time i used it, suddenly it reboots this was a few days ago. And just this moment i want to wake up it from sleep mode, but it was turned off, although it still has 50 % of battery. I think it's not that bad but i want to be sure that it is not a hardware problem. You have an advice?
Thanks
Click to expand...
Click to collapse
honestly sounds like sleep of death...i had this with my first device..exchanged for a new one and havent had the issue yet. i have no idea what causes it...i spent plenty of time trying to adjust settings to fix it but couldnt. id suggest exchanging it bro
Sent from my A500 using xda premium
Thx for your replies i will give this device a few more days to test it. I cant reproduce the Problem.
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Any takers? If it is a hardware issue i want to fix it ASAP before my warranty is up!
I have it too, wipe doesn't help. I will try flash a stock rom..
dymex said:
I have it too, wipe doesn't help. I will try flash a stock rom..
Click to expand...
Click to collapse
i've found myself at 99% when it's plugged in and it won't charge anymore. not sure if it's a hardware thing or a rom thing. it's intermittent though... haven't found a fix yet...
Please share what you find out after you revert back!
Sent from my Galaxy Nexus using XDA
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
tokuzumi said:
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
Click to expand...
Click to collapse
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Hydera5 said:
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I've seen a similar issue where the device will not charge while connected to power. A reboot will resolve the issue but, for obvious reasons, this is less than optimal.
Is there any way to identify what application (since this only changed recently) might be causing the issue?
Thanks!
M
Oh come on!! Don't people use the search function anymore!?!? See http://forum.xda-developers.com/showthread.php?t=1676711 or the other 20-30 threads regarding this issue.
Basically, you need to replace your USB charging board, and Samsung will claim water damage and make you pay for the whole repair...
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Sorry, I'm not targeting you. I'm just not okay with people creating new threads instead of contributing in existing threads regarding the exact same issues.
MJMcMahon said:
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Click to expand...
Click to collapse
Problem solved (sorta) i called customer care and they said that it was a "common problem" and usually was a result of using a charger other than the one that came with the phone... Long story short they are sending me a new one, new post here if you are still in the helping mood (;
http://forum.xda-developers.com/showthread.php?p=26729008#post26729008
This issue just started happening on my Galaxy Nexus last week. I just called Verizon and explained what was going. I told the rep I hard reset the phone and it still occurs. He said it was a known issue and overnight ed a replacement. If you're having this issue Verizon seems very aware of it.
I had the same issue .... for me it went away with the newer CM builds [VZW].
Hydera5 said:
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Click to expand...
Click to collapse
Mine just started doing this yesterday. Tried a couple of battery pulls but it still seems to think it's constantly charging. When it starts flopping back and forth between charging and discharging the phone becomes unusable. I'm just wondering if the battery pull was a permanent fix for you or did you have to send it in eventually?
I ordered the Zenwatch during those few hours they were first available online at best buy. I picked it up yesterday and only have a few days left before I need to return my Sony Smartwatch 3. I want to decide between the two, and was leaning towards the Zen because of aesthetics and I actually like the charging cradle design.....
BUT, this watch lags like crazy and then freezes completely within a few minutes of booting. Even the very first time I turned it on, it took forget to register what I had selected for language. After rebooting, I got past that and it eventually installed a software update. Unfortunately, that didn't seem to help.
After 1 or 2 cycles of dimming the screen and being woken up, the watch freezes. The phone still thinks it is connected and I can feel it vibrate when swiping down to mute/unmute, but the graphics are frozen. The side drawer doesn't activate and the only way to shut it down is to hold the power button for 10sec or so.
I've done multiple "resets" on the watch and repaired the phone, but it keeps acting the same. Is there a hard reset for this watch? Anyone else experience this?
I'd exchange it at best buy but of course they are sold out so who knows how long before they can exchange it.
This happened to me when I had the 360. It froze when I was trying to turn it off. I eventually got it off, just like you did. It never responded the same afterwards. It would freeze at random times. I assumed it was the TI processor in the 360, but I hope this is not something to expect with AW. I took mine back to BB and got a refund so I could get this watch. I hope this is an isolated event.
All the reviews have been stellar and people have seemed happy even on the fortune, so I'm sure this is isolated.
I wonder if there is a way to reload the system software from the computer to the watch? Best buy is a no-go at this time. Sold out and unable to help aside from returning and refunding it.
Sent from my VS985 4G using Tapatalk
Based on the tracking status, I should get mine tomorrow. I'll let you know if I experience any funny business when I get mine up and running. Good Luck.
I really haven't noticed any significant lag. It's initially unresponsive sometimes which I attribute to an overly conservative cpu governor, but otherwise it's a pleasant experience.
I've had mine for almost a week now and definitely haven't seen those problems. There were updates to both the watch and phone app soon after starting up. Maybe you got a bad load on one of them. Have you tried the 'Resync apps' option from the Android Wear (Phone) settings menu? Have you tried the full factory reset of the watch? If so, sounds like dud might be the case. If of any significance, I'm connecting via a stock Sprint HTC One Max.
Yes, the watch did an update after the first successful boot, but it was laggy and had frozen during the language setup even the first time. I've done multiple factory resets to no avail, but it does not repeat the update with that (though it does require pairing to the phone again).
I wish I could manually reload the watch system software. I'm new to Android wear rooting,etc. Is it possible to manually completely reload the system software?
Yes, I've also tried the resync apps and have the latest phone software as well...
Sent from my VS985 4G using Tapatalk
I would maybe try once with a different phone then call it a dud. I don't know enough about it either to go deeper than that.
Saga over. Returned the watch today after trying clean installs of everything last night. It would even freeze when not connected. Sucks to get a dud, but glad this seems to be a unique occurrence.
Trying out the LG G watch R (what a horrible name). Big and sporty instead of subdued, but nice nonetheless.
Sent from my VS985 4G using Tapatalk
albertdc said:
Saga over. Returned the watch today after trying clean installs of everything last night. It would even freeze when not connected. Sucks to get a dud, but glad this seems to be a unique occurrence.
Trying out the LG G watch R (what a horrible name). Big and sporty instead of subdued, but nice nonetheless.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
I was having similar issues but wanted a couple days with the watch before i posted, I just requested a RMA for the watch, love the look of it, but was having issues with random reboots, very laggy ui especially when browsing through watch faces..had one time where the watch actually locked up and required a hard reset via the button on the back..also got significant battery drain, 2 percent every it seemed 10 minutes....Hopefully the replacement is better than this one...I could live with some of the issues, but the random rebooting i can't deal with. If the 2nd is a dud mite get the sony, till then back to my trusty g watch.
Battery Drain
djkinetic said:
I was having similar issues but wanted a couple days with the watch before i posted, I just requested a RMA for the watch, love the look of it, but was having issues with random reboots, very laggy ui especially when browsing through watch faces..had one time where the watch actually locked up and required a hard reset via the button on the back..also got significant battery drain, 2 percent every it seemed 10 minutes....Hopefully the replacement is better than this one...I could live with some of the issues, but the random rebooting i can't deal with. If the 2nd is a dud mite get the sony, till then back to my trusty g watch.
Click to expand...
Click to collapse
Did you get your watch back? I have to send mine in too because the battery dies in 5 hours without even touching it. ASUS said it is a bug with the lollipop update so they are going to re-flash it. Also did you have to ship it yourself or did you get something in the mail.
BretskiSmith said:
Did you get your watch back? I have to send mine in too because the battery dies in 5 hours without even touching it. ASUS said it is a bug with the lollipop update so they are going to re-flash it. Also did you have to ship it yourself or did you get something in the mail.
Click to expand...
Click to collapse
I sent mine in cuz it wouldn't turn on. I received an RMA, shipped it to them and they had it back to me in less than a week.
Hi. first of all. sorry for my bad english im from denmark so i hope you can understand what im wrighting..
I just got my brand new moto 360 yesterday.
1 of all really cool wacth!! BUT! while im using it almost all the time it vibrates and goes black and then showing the watch again..... and it is doing this at random times..... and i am going insane becous there is NO WHERE on the web which describes this problem,,,,
can some one PLEASE have an solution. i have reset it 4 times now and still doing it
firmware 5.0.1 lollipop.
With best regards Stefan Pedersen Denmark
Alienwalker30 said:
Hi. first of all. sorry for my bad english im from denmark so i hope you can understand what im wrighting..
I just got my brand new moto 360 yesterday.
1 of all really cool wacth!! BUT! while im using it almost all the time it vibrates and goes black and then showing the watch again..... and it is doing this at random times..... and i am going insane becous there is NO WHERE on the web which describes this problem,,,,
can some one PLEASE have an solution. i have reset it 4 times now and still doing it
firmware 5.0.1 lollipop.
With best regards Stefan Pedersen Denmark
Click to expand...
Click to collapse
I've had my watch since November with no issues, but yesterday I dropped it (not hard, not enough that it should have done any damage) and now I'm facing the same issue as the OP. Which unfortunately suggests that it may be a hardware issue. If anyone has any ideas other than reboot/reset I'd be really happy to hear them - otherwise I think I'll be taking it back to the retailer and seeing if I can get a replacement.
I've had the same problem since day 1.
I don't know what to do cause it happens occasionally.
I've been using my Moto 360 for 11 days.
watch vibrates when your bluetooth device is out of range with your watch.
when it does, look at your watch, you'll see an icon of a cloud with a line across it. it means your device is offline and only function is to show your time.
when you are back in range with your bluetooth device, it will vibrate again to let you know that the watch is back online and the icon will disappear.
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Never happened... Can you record a video or something
Sent from my Google Pixel 2 XL using XDA Labs
KevTN said:
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Click to expand...
Click to collapse
It is a known issue they'll rma it for this reason. On a side note I had that issue for about 12-24 hours and went away on it's own, no restart or factory reset was required for me. Really wish I knew what or why the cause but maybe it will go away, like mine did. :fingers-crossed:
Thanks I hope so too. Really liking the phone but for this money...
agreed I almost gave up, my first 2 were too blue and the 3rd fine except started that flash, but ultimately went away. Loving this phone!
KevTN said:
Sorry if there has been a thread I am at work but the last few times when ever my screen goes to being locked it will flash white then go the lock screen. Is this a known issue just got the phone Wednesday. Thanks
Click to expand...
Click to collapse
Happened with my girls phone..was gonna rma it but decided to flash 8.1 beta 2 and it has fixed it..so looks like Google fixed it in a software update..beta 2 is running well so I would enroll in the beta program and update... should fix that issue right up
Well it got worse so called good rma’d It. So we will see. Glad to see it just wasn’t me...thanks for your input..
KevTN said:
Well it got worse so called good rma’d It. So we will see. Glad to see it just wasn’t me...thanks for your input..
Click to expand...
Click to collapse
Mine just started this week flashing. Running 8.1 since last week. Does your new replacement suffer from the same issue as well?
Thanks
mrcndr82 said:
Mine just started this week flashing. Running 8.1 since last week. Does your new replacement suffer from the same issue as well?
Thanks
Click to expand...
Click to collapse
Mine started today but it has been getting better as the day goes on. I'm curious if its an issue with charging. Prior to a few days ago I had been only using the chargers with that I've received specifically for the phone, but this week--since I'm traveling for the holidays--I've only been using my pixelbook charger, so maybe something isn't properly shielded and the flash is caused by a built up charge? Reason I think that is that it has been less and less noticeable as the day goes on..
sovanyio said:
Mine started today but it has been getting better as the day goes on. I'm curious if its an issue with charging. Prior to a few days ago I had been only using the chargers with that I've received specifically for the phone, but this week--since I'm traveling for the holidays--I've only been using my pixelbook charger, so maybe something isn't properly shielded and the flash is caused by a built up charge? Reason I think that is that it has been less and less noticeable as the day goes on..
Click to expand...
Click to collapse
My flashing went away the next day. I did do a factory reset just because I only had it a few days and no issues since. Although Google RMA’d my phone I sent the replacement back without accepting shipment as mine has been running like a champ since.
KevTN said:
My flashing went away the next day. I did do a factory reset just because I only had it a few days and no issues since. Although Google RMA’d my phone I sent the replacement back without accepting shipment as mine has been running like a champ since.
Click to expand...
Click to collapse
Got my replacement a week ago, 0 flashes so far (finger crossed). I tend now to think it's a hardware issue. Also blue tint is slightly better on new device...
I just got my Pixel 2 XL delivered to me yesterday. Set it all up, didn't get the flashing screen issue at first but now it's doing it. Tried to chat with Pixel support from my phone, they don't have a resolution for it yet.... Hopefully it's a software issue?
Mine started doing this about 3-4 days ago. I noticed that it starts to do it when night mode is on. If I go the RMA route, this will be my 3rd replacement and tbh I'm not looking forward to doing this.
Mine did it once with always on display on, I don't usually use that so I turned it off and it hasn't happened since.
I just received a replacement device yesterday due to a faulty speaker. No issues with the last device, but this device is now exhibiting the screen flash when locking.
mferrara91 said:
I just received a replacement device yesterday due to a faulty speaker. No issues with the last device, but this device is now exhibiting the screen flash when locking.
Click to expand...
Click to collapse
Exact thing with me. I received a brand new device that I got because my previous one had a bad speaker (speaker phone distorted sound). This new one has the screen flashing problem. My original did not. Poor QC ... especially for $850.
Mine has been doing it for a couple of days, and it kept getting worse. On chat with Google Support now. Sounds like it's going to be RMA'd.