Hey everyone, first time poster here.
I've bought a Sony Smartwatch 3 after the contacts on my LG G watch broke, but I'm noticing a problem that's been happening on both watches.
I can be doing anything with it, or just having it resting on the desk in front of me, and all of a sudden it'll wake itself and then start scrolling up and down randomly and going into random apps. sometimes even calling people who text me. (you can imagine trying to fight with said watch while it goes about calling every text)
And that's another thing, I have to sit there attempting to reassert my touch control over some phantom user by polishing the screen with my finger.
How do I stop this from happening? I've tried turning off the tilt to wake, nothing. And I can't seem to physically lock the touchscreen with the side button like you'd expect. I can still unlock by double tapping (a function I'd like to disable) and the thing starts off all over again.
Is it something to do with static or is the unit just faulty?
Ratgrot said:
Hey everyone, first time poster here.
I've bought a Sony Smartwatch 3 after the contacts on my LG G watch broke, but I'm noticing a problem that's been happening on both watches.
I can be doing anything with it, or just having it resting on the desk in front of me, and all of a sudden it'll wake itself and then start scrolling up and down randomly and going into random apps. sometimes even calling people who text me. (you can imagine trying to fight with said watch while it goes about calling every text)
And that's another thing, I have to sit there attempting to reassert my touch control over some phantom user by polishing the screen with my finger.
How do I stop this from happening? I've tried turning off the tilt to wake, nothing. And I can't seem to physically lock the touchscreen with the side button like you'd expect. I can still unlock by double tapping (a function I'd like to disable) and the thing starts off all over again.
Is it something to do with static or is the unit just faulty?
Click to expand...
Click to collapse
If its happened on both watches it sounds like something is interfering with the watch, maybe the contacts could be environmental?? Try giving it a "good" clean. I have an LG watch R and my son has the Sony SW3 and we haven't seen those issues.
Have you tried pairing the watches with another phone?
TimmyUK said:
If its happened on both watches it sounds like something is interfering with the watch, maybe the contacts could be environmental?? Try giving it a "good" clean. I have an LG watch R and my son has the Sony SW3 and we haven't seen those issues.
Have you tried pairing the watches with another phone?
Click to expand...
Click to collapse
I've tried cleaning the SW3 with both screen cleaner and soap and warm water (as its waterproof for running water and none of them seem to help.
I've also tried resetting the watch 6 times since buying it a month ago.
Any ideas on how to turn off "tap to wake"?
Related
Hi folks:
Sorry if this problem has been covered before. I ran a search to try to see if I could find someone having this problem and could not find it. This problem started all of a sudden (without any ROM updates or nothing).
This is it: I make a phone call, and immediately after I press "TALK" on the screen, the screen turns itself off, and I don't have access to the keypad, or any of the touchscreen functionality.
I tried pressing all the hardware buttons to see if the screen would come back on, but nothing, it stays off.
Then, when I hang up the call (by pressing "END CALL" on the screen), the screen comes back on and everything is back to normal.
Can anyone offer any clues to solve this? Thanks in advance.
is the phone near something? maybe your ear?
is anything in front of aproximity sensor? (upper left, near speaker)
DN41
Nope... I use a BT headset since I got it (this only started happening 2 days ago, and I've used this device for over a month now).
It also happens everywhere (in my room, outside in the street, etc).
Very puzzling... I am thinking of doing a hard reset, but want to see if anyone has had this happen before...
Does it happen when you don't use the headset?
Yes indeed, I had already checked that and ruled out that the headset was causing the issue.
have you recently installed a "screen protector" ? This happened to mine as i hadn't quite got the holes lined up for the proximity sensors.
thanks,
scater1983
This happened to me as well today. Had the phone for 3 months now and can't say I've noticed it before. I do have a screen protector which also covers the proximity sensor (no holes in that area), but this was like a month ago and I have had no problem accessing the screen during calls until today. I have made a couple of calls after the one I mentioned but didn't remember to check if the problem was still there. Will try to see on the next one
ive been able to just press a face button to bring the screen back up. of course mine turns off when i put it near my ear thats intended. i had an issue where the touchscreen would not work at all durung a call. the screen would be on but only the physical buttons could do anything. a hard reset fixed that
Yeap, coincidentally, I just installed a screen protector and a protective case (darn). I will try this without the case and report back.
Thank you !
Problem solved ..
Been trawling these forums for hours for a registry edit to fix screen blank when making a phone call - LOL - who would have thought it was the cheap plastic case I whacked on the other day!
The proximity sensor seems to work. Is there a call screen replacement with a slider to hang up?
whens shes talking lock the screen via the power button and walla
If you're rooted, there are many applications that change the proximity delay in the build properties.
You could try that.
Or ya, manually turn the screen off with the power button.
My mother has owned her X as long as I've had mine (since day 1) and still hangs up on me almost every conversation.
I personally just angle the phone slightly away from my face along with the sensor delay changes I mentioned.
If she is like my wife she doesn't hold the ear piece to her head while she talks (thus the proximity sensor thinks she isn't near the phone), then she hits the screen on her cheek and hangs up on people.
Tell her to learn how to talk on the phone properly.
drhill said:
Tell her to learn how to talk on the phone properly.
Click to expand...
Click to collapse
Yeah, and report back on how sore and stiff you are from sleeping on the couch!
I don't understand why anyone would want to hold a device the size and temperature of a smartphone to their head.
I started using a BT headset when I bought my Treo 700P and have been using one since.
I actually did sleep on the couch last night, different reason.
I ended up teaching her to use the power button to turn off the screen.
kent c said:
I actually did sleep on the couch last night, different reason.
I ended up teaching her to use the power button to turn off the screen.
Click to expand...
Click to collapse
Sounds fun.
She no longer hangs up on a call she answers but she constantly mutes calls that she makes now. My phones rings and I'm like hello...hello...
Sell it and get a Razr flip phone. At this point there is no more help.
Let me guess, Blonde?
Be nice kids.
EDIT: ok, touchscreen unresponsiveness after long standby happens due to flip cover. so this could be a major bug in the 5.1 update that needs to be fixed. i hope we will get a few ota updates with fixes for our problems.
yeah, as the title said, i can't use my tablet after it was in deepsleep/standby for too long in android 5.1 lollipop.
Scenario: after long standby/deepsleep time i pressed the power button to turn the screen on. the lockscreen (swipe only gesture) appears. i want to unlock the device by swiping up but it doesn't work as if i didn't even touch the screen.
only workaround for me at this moment is to hold the power button for a few seconds so it shuts down (NOT Force reboot, it still says "shutting down" or something like that). after that i turn it back on, let it boot until it finishes. now the touchscreen works again.
short: long standby/deepsleep equals touchscreen completely unresponsive
rebooting equals a workaround solution that is really anoying for me everytime
did anyone experience this problem, too?
does someone know how to fix this?
EDIT: BTW everything works just fine and runs really smooth except for the unresponsive screen while too long in standby.
it could be that my flip cover causes this to happen.
I CANNOT confirm anything yet.
i will try it a few times more with flip cover on top of the display and without the flip cover on display. (could be bad calibrated magnetic sensor or just bad programming overall)
maybe i will know more after that. i will report back in this thread if anything happens.
seems to be solved due to clean restore of 5.1 (READ FIRST POST RED COLORED EDIT LINE)
back again, thought it went away. in the last hours the unresponsiveness bug happend again (2 times; probably due to flip cover)). my thought is that nvidia went on to the flip cover bug from kitkat, tried to fix it and made it worse instead of getting rid of it.
OMG, really? This bug not only still exists but has become even worse? Ridiculous... glad I don't even use my cover any more... I'm not even sure where I put it ^_^ It's stuff like this and the issues with the Shield Tab that kept me from buying the Shield TV, even though I really really want one.
not flip cover issue... its happening ever since i updated to lollipop. only stylus works and finger touch is unresponsive.. sometimes the stylus also doesnt works
Same problem here Blaze! Sometimes finger touch is unresponsive, only works with the stylus! This is terrible [emoji17]
Enviado do meu iPhone usando Tapatalk
Hello!
I recently picked up the Moto X PLAY. Have no real complaints about it other than the fact that I'll randomly hear it make the notification sound, yet there's no notification and the screen doesn't turn on (not even the wake screen). The phone will randomly wake itself to the wake screen as well while sitting on my desk or in the car.
Is anyone else having these ghost sound issues? At first I thought it was my e-mail client, but I've ruled it out. I've looked over the Help forums and didn't find anything that seemed related to my issue.
Thanks in advance
I've had this happen on multiple devices, with multiple different ROMs. It's a very strange bug, but I don't think it's just an X Play issue.
The phone is sensitive. In car it will wake due to motion thinking its being picked up. On your desk I can only imagine maybe your desk gets knocked or rocks a little?
Sent from my XT1562 using Tapatalk
ephumuris said:
The phone is sensitive. In car it will wake due to motion thinking its being picked up. On your desk I can only imagine maybe your desk gets knocked or rocks a little?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
If they are talking about the same thing I am, it's not about the screen waking. It's the device actually playing a notification sound to alert you you've got something to check, and when you do, there is nothing there.
My phone's navigation bar stopped working, it doesn't even show any light when I get a notification. Everything else on the screen works, but since the home/back/menu buttons don't work I have to reset the phone whenever I want to check something and I can't go back. I've tried to restart it, to do a hard reset but nothing seems to work.
Once this happened my phone also stopped playing sounds, I can't even listen to the sounds when choosing a ringtone.
Please help me, I've never seen anything like this! Thanks
I had the same problem, it was the cable inside the Phone that is disconnected.
You've to remove the back cover, remove the frame (remove all the screws and connect the plug)
It is not easy to remove the back cover, you'll need heat, and if possible a suction tool so you'll not force only one side of the back cover...
I was almost an half of hour to remove the back cover...but fortunately I had success!
[Solved - same as TiagoRveiga, cables were disconnected]
I also had this problem, the one were the buttons don't work. You can always go to the notification bar and from there go to settings where you can go to apps, chose one and open. Instead of rebooting. It took me a while to discover this easy trick... Now I've had my boyfriend install an extra onscreen home button, return and other thingy. You lose one cm room on the screen but I have settled with it.
Other problems are though: camera never works anymore, after six months. After four months rebooting sill helped sometimes...
With the camera also the flashlight...
Also the sound when calling, nobody hears me, but I hear everything... This after a year suddenly...
A week after this issue, all sound disappeared like with yours, but also gradually. First from time to time and then bam, nothing.
This shows me that there is nothing wrong with the hardware, the camera is not broken, everything on the inside is connected. It are glitches... The software on this phone stinks, really bad...
Umi zero desides when I get to call, listen to music, take pictures... I don't like that. Tomorow, after one year and three months, I give up, my new one plus x will arrive and umi goes with the garbage... I suggest you all folow my lead, the more you try, the more problems that will appear.