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
Related
I bought my Smartwatch 2 from amazon and apart from being totally disapointed by the fact that Sony removed the shake2wake, music widget and auto brightness I have found an other problem: it gets stuck (happens like once a day) and it usually happens when I let it turn the screen off by its own, it will just dim the screen and get stuck in a dimmed screen state, showing my apps, but I can't interact with it, is anyone else experiencing this, and did anyone manage to fix this problem, or is my devices defective and I should send it back for repairing, and if that's the case can I send it to Sony Roumania instead, cause I don't like the idea of sending it to Amazon UK?
Ranomez said:
I bought my Smartwatch 2 from amazon and apart from being totally disapointed by the fact that Sony removed the shake2wake, music widget and auto brightness I have found an other problem: it gets stuck (happens like once a day) and it usually happens when I let it turn the screen off by its own, it will just dim the screen and get stuck in a dimmed screen state, showing my apps, but I can't interact with it, is anyone else experiencing this, and did anyone manage to fix this problem, or is my devices defective and I should send it back for repairing, and if that's the case can I send it to Sony Roumania instead, cause I don't like the idea of sending it to Amazon UK?
Click to expand...
Click to collapse
Do you think you might have downloaded an app that is causing this? I haven't had my watch for long but, I downloaded a calander app which would cause my watch to freeze whenever I'd open it.
MO3iusONE said:
Do you think you might have downloaded an app that is causing this? I haven't had my watch for long but, I downloaded a calander app which would cause my watch to freeze whenever I'd open it.
Click to expand...
Click to collapse
Downloaded only Sony's apps (most of them) and WatchIT and the xbmc and tasker extensions, don't think any of one can cause that...
EDIT: Forgot to say it also happened when my phone was dead, so the watch was not connected to anything.
Just if anyone is interested and has the same problem as I did, I managed to solve it by unpairing the watch from the phone, reseting the watch and doing the whole repairing process.
Ranomez said:
Just if anyone is interested and has the same problem as I did, I managed to solve it by unpairing the watch from the phone, reseting the watch and doing the whole repairing process.
Click to expand...
Click to collapse
Yep, I'm experiencing the same problem as I'm typing. I was just viewing an email and, exactly like you said, the backlight slowly turned off and it just stopped working. I'm going to soft-reset the smartwatch.
InjecTioN said:
Yep, I'm experiencing the same problem as I'm typing. I was just viewing an email and, exactly like you said, the backlight slowly turned off and it just stopped working. I'm going to soft-reset the smartwatch.
Click to expand...
Click to collapse
Hope you fix it man, the smartwatch 2 is a beautiful device, unfortunately mine is no more (screen got burnt so I sent it back to amazon and got my money back) so I really hope you fix it and keep enjoying it cause I really miss it but oh well, waiting for a g watch and hoping to be as satisfied of it as I was of the smartwatch 2.
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
Hi guys I have a problem with the touch response on my G4 (H815)
Basically when I use multi touch (and sometimes just normal scrolling) in certain apps the phone will recognize screen taps at the bottom of the screen at the home and back buttons and sometimes other areas, I have used the 'multi touch app' from the play store to confirm that this is indeed the case. This is extremely annoying as apps exit by themselves because of this. It doesn't happen every single time either, just sometimes but often enough for it to be annoying and so may be hard to prove to my carrier or LG if i send it back cause they may say there's nothing wrong with it.
It seems like a hardware issue and in that case the phone should still be under warranty right? I got it in August and haven't rooted or done anything invasive.
There are many people having issues with the G4 touchscreen. Check with your carrier and see if you can exchange it or what your options are.
Hi,
Same problem for me, the back and home button seems possessed. Se this video dropbox.com/s/540ozmvdnhemv8f/MOV_0005.mp4?dl=0 for an example. I bought the phone Thursday last week and it have been this pretty much since unboxing. After a factory reset the phone acts normal for a couple of minutes or hours, but goes back to that stage were I can't use the phone at all. I've managed to update to the latest software but the problem didn't go away. I'll try to contact the supplier I bought the phone from and exchange it tomorrow.
Since I do not have enough posts to post external links you have to figure out for youself what to type infront of the "link" I included.
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?
Hi.
My Z1C seems to have a similar case of faulty display as described in some other threads here, but actually a bit different. The phone is stock, not rooted, running 5.1.1
Whenever I do something, there are ghost touches in the upper quarter or third of the screen. They only happen when I am not touching the screen myself. It happens no matter what I do. When I browse internet, it clicks links, when I scroll contacts, it calls people, when I am on facebook it gives likes etc... It seems like the more demanding task the phone is performing, the more ghost touches.
I turned on the developer settings and the "show pointer location" option, which leaves track of the last touch on screen, so I can research the issue.
I found out that when the phone is on home screen, it happens very rarely or not at all - the track of my last touch stays until screen turns off.
When I jump into the touchscreen service test, it does not happen at all. I can draw a line around the whole screen and it stays higlighted indefinitely.
In lock screen, it also doesn't happen.
I tried it in Sketch and it confirmed what I thought, when I was just sketching, from time to time a dot appeared in the upper part of the screen, but when the phone was downloading or installing in the background, the screen literally had seizures. I touched and released and then a storm of dots started to appear around the top part of the screen. It stopped after 5+ seconds, and after another input from me, the screen got another fit, drawing more dots.
I don't have any experience, but I think that since the problem doesn't happen constantly and it doesn't even happen at all in test mode, it could be a SW mistake.
I have found this thread https://forum.xda-developers.com/showthread.php?t=2691849 and I'm willing to try, but 1) my phone is still under warranty and 2) I have never done a root so I am not too eager. Do you think I should try that? Or has anyone found another solution for this problem?
Thanks.
Slivovidze said:
Hi.
My Z1C seems to have a similar case of faulty display as described in some other threads here, but actually a bit different. The phone is stock, not rooted, running 5.1.1
Whenever I do something, there are ghost touches in the upper quarter or third of the screen. They only happen when I am not touching the screen myself. It happens no matter what I do. When I browse internet, it clicks links, when I scroll contacts, it calls people, when I am on facebook it gives likes etc... It seems like the more demanding task the phone is performing, the more ghost touches.
I turned on the developer settings and the "show pointer location" option, which leaves track of the last touch on screen, so I can research the issue.
I found out that when the phone is on home screen, it happens very rarely or not at all - the track of my last touch stays until screen turns off.
When I jump into the touchscreen service test, it does not happen at all. I can draw a line around the whole screen and it stays higlighted indefinitely.
In lock screen, it also doesn't happen.
I tried it in Sketch and it confirmed what I thought, when I was just sketching, from time to time a dot appeared in the upper part of the screen, but when the phone was downloading or installing in the background, the screen literally had seizures. I touched and released and then a storm of dots started to appear around the top part of the screen. It stopped after 5+ seconds, and after another input from me, the screen got another fit, drawing more dots.
I don't have any experience, but I think that since the problem doesn't happen constantly and it doesn't even happen at all in test mode, it could be a SW mistake.
I have found this thread https://forum.xda-developers.com/showthread.php?t=2691849 and I'm willing to try, but 1) my phone is still under warranty and 2) I have never done a root so I am not too eager. Do you think I should try that? Or has anyone found another solution for this problem?
Thanks.
Click to expand...
Click to collapse
As You have warranty, I would strongly suggest that You go for a repair. I had the same issue in beginning, ghost touches appearing randomly, going away only after reboot. I was rooted and xposed, so went full stock without restoring any apps or data from internal storage, yet the problem remained, thus ruling out the point that it was software problem. And then after a week or so, that much part of screen stopped responding to touch entirely. You can see details over here, Another user had same problem as Mine and had the same end result,
OK then, I'll go for a repair. Thanks for the tip.
Slivovidze said:
OK then, I'll go for a repair. Thanks for the tip.
Click to expand...
Click to collapse
I am having exactly the same behaviour as you described .
Ghost touches happening on the upper part, and triggered when a demanding task is running.
Actually I didn't realized completely about this, I thought it was just random, but right now after I saw your post, I tried an app similar to Sketch while upgrading apps or playing a video in the background. And dots in the upper part start appearing crazily.
Did the phone repair solve your problem ? Mine is not in warranty, so I'll have to pay for it.
But also in my case, before this thing happened, I got some water damage and that upper quarter of the screen stopped responding.
After replacing screen+digitizer I got this very specific behaviour you described.
karamaz0v said:
I am having exactly the same behaviour as you described .
Ghost touches happening on the upper part, and triggered when a demanding task is running.
Actually I didn't realized completely about this, I thought it was just random, but right now after I saw your post, I tried an app similar to Sketch while upgrading apps or playing a video in the background. And dots in the upper part start appearing crazily.
Did the phone repair solve your problem ? Mine is not in warranty, so I'll have to pay for it.
But also in my case, before this thing happened, I got some water damage and that upper quarter of the screen stopped responding.
After replacing screen+digitizer I got this very specific behaviour you described.
Click to expand...
Click to collapse
In my case, I realized that I bought (probably) a badly re-fitted phone. Display's backlight was visible around screen panel edges, where I'd say it shouldn't be visible at all. I decided to return the phone and got a refund.
Sorry for not being able to help you.
Slivovidze said:
In my case, I realized that I bought (probably) a badly re-fitted phone. Display's backlight was visible around screen panel edges, where I'd say it shouldn't be visible at all. I decided to return the phone and got a refund.
Sorry for not being able to help you.
Click to expand...
Click to collapse
Ok. The aftermarket screen I got has that issue with the screen edges also. Very probable you are right.
In my case I water damaged myself. It seems that after 2 years of intensive use, waterproofing is gone, by accumulation of slight hits or so, never had a single crack on the screen. I read many posts reporting this happening, even with much less use time.
Too bad, I loved the phone, but I'm afraid that sending it to repair will mean to change the PCB or similar for a complete fix, which can come to a ridiculous price.
Seems it will be time to move on...
Yeah. If you want it fixed properly, you'd need to send it to Sony, and for the money it would cost you, you can probably gen a new phone. Sadly, similar phones aren't made anymore.