My Sony smartwatch 3 does the screen turn on randomly and then also touch screen problem occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. It is mostly lying on table. It's on the latest wear version: mwd49b.
I have put the earlier versions back on it, also the 5.1.1 and it does the same. Alltrought it is rooted and I put the other rooms back with twrp from my backups. So I think, that it can be a problem in all of my backups, or it is more worse, if it is hardware problem, but I hope it isn't.
Is there any way to revert back to stock room and kernel? I done recently more factory reset, and deleted the android wear app from the phone also (xperia z2). I also reinstalled it with Sony companion software. Still have the same problem.
It seems like it is doing something in the background, and it is frozen, but it is not going to be hot. Inbetween if I touch the screen, it doesen't responding to my imput, but after some time it makes this strange screen touches, like it tries to make my imput afterwards. So this is why I think it is a software problem, not a hardware.
Please, if anybody know about this, or having the same of similar problem, write here, maybe there is someone in this forum, who can help.
Almost forget: Can someone please write me down, how I can do a full wipe on the SW 3 with twrp and then reinstall a clean rom?
For more info, please search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I know that are a little weird but you tried to remove the screen protector? in your video seems you use a screen protector, maybe that are making your sw3 crazy
nathansg7 said:
I know that are a little weird but you tried to remove the screen protector? in your video seems you use a screen protector, maybe that are making your sw3 crazy
Click to expand...
Click to collapse
Yes, once when the problem was there I tried to remove fast the screen protector, but then the touching problem was also there, so then I decided to leave it on. Now I removed it completly, but doesen't solve the problem.
I think it is a software problem, cause when it is for exemple in twrp, the problem never occur.
I'm gonna do full wipe, and then I will see. If somebody has a good idea, how to do a full wipe on the smartwatch 3, please, give me an advice. THX
Related
My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work
BUMP Help!
You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.
I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.
Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.
dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.
any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?
Hi folks,
since monday I have got my HTC Desire Z and it's my favourite phone of all time until now.
But there is a small problem with the touchscreen.
I get SMS messages and read them.
After that I want to answer the messages and begin to write with the HW-Keyboard.
Then the party begins. The Screen which shows my answer while I'm writing begins to jump up and down. If I try to stop it with my finger, like hunting a small bug or something , it shows me the little zoom windows for marking,copying and cutting text.
I've factory resetted the phone, but the problem is still there.
It has got the Stock ROM and 2.6.32.21-gd2764ed Kernel.
(I overclocked the phone yesterday, bu the problem appears since the first day, not since the OC)
Thanks guys,
sergioka
There's a known issue described at http://forum.xda-developers.com/showthread.php?t=829535
But on my phone at least, it just "jumps" once, it doesn't go up and down if that's what you're seeing (unless you specifically go and start swiping it etc).
Hi, I made two videos.
This time such a thing didn't happen in the Messaging Mode, but in the homescreen.
Should I send this phone back?
Thanks in advance
Sorry for the bad quality, had to record and recode it as fast as possible.
Edit:
second video had problems
sergioka said:
Hi, I made two videos.
This time such a thing didn't happen in the Messaging Mode, but in the homescreen.
Click to expand...
Click to collapse
I've had some weird things happening with my touchscreen in the last few days. But I'm pretty sure this is connected with a new screen protector that I put on, because the problems happened around the same time. If I lift the screen protector and touch the screen when it's gone non-responsive, it works.
Have you got a screen protector ?
Hi, I have a screen protector,
but the problem happened the same before.
....
....
Now, I have lifted my protector to test the device again without it.
The Screen responses in the same way without the protector and in cyanogenmod
It's like having a high end gaming pc which has sometimes problems with fifa soccer 2000
Did you do full wipes when flashing your rom? It looks to me like it's the rom glitching as it gets stuck between screens, then like a millisecond freeze up before it catches up again?
Does it happen all the time? Is it ever OK after a reboot? Do you have setcpu installed?... settings please. Any setcpu profiles?..if so, are the frequencies being set correctly at wake up?
Download your rom again, check the md5 checksum. Full wipes.
Sent from my HTC Vision using XDA App
Tried all the things you've described. At first I thought that it's ok, but after a while in some situations the saga continued
I'll send it back to get a new one
Your problem looks exactly like mine, except that mine seems to have been the particular screen protector. Given that's not the case for you, I can only think that your touch screen is faulty.
Send it back.
It's on its way to the grave now I think
Now, after I've sold my Nokia N900 and lent my homeboy my HTC Kaiser,
I don't have a phone with me.
Time for morsing my messages!
i agree. send it back. i just tried it with mine and it was fine no matter how i held it. This is supposed to be a high end phone that isnt very cheap...
you need to get your money's worth.
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
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 everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.
Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.
Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
2x post
when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks
Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.