This just happened to me for about the fifth time.
1) After workout or other activity, I take the watch off and rinse it in the sink
2) I dry it off with a towel, and when I look at the face again, it says "Resetting..." (ARRRRRGH!!)
Now, I'm sure anyone reading this will guess the first thing I guessed: that somehow, I was holding down the buttons in some fashion while drying the watch off. But since thinking this, i've been very careful about trying not to press any buttons while drying it, and it still happened again recently. I've looked up the method for intentionally factory resetting, and supposedly it's a requirement that the watch is powered off before even starting. I can't imagine I could accidentally perform the exact sequence needed so many times according to those instructions.
I now have the watch automatically backing up every week. So it's not a huge deal to run a restore, but I still have to reconfigure my cards in samsung pay from scratch each time, and the whole process is extremely annoying because it just shouldn't happen.
Anyone else?
Phreaker47 said:
This just happened to me for about the fifth time.
1) After workout or other activity, I take the watch off and rinse it in the sink
2) I dry it off with a towel, and when I look at the face again, it says "Resetting..." (ARRRRRGH!!)
Now, I'm sure anyone reading this will guess the first thing I guessed: that somehow, I was holding down the buttons in some fashion while drying the watch off. But since thinking this, i've been very careful about trying not to press any buttons while drying it, and it still happened again recently. I've looked up the method for intentionally factory resetting, and supposedly it's a requirement that the watch is powered off before even starting. I can't imagine I could accidentally perform the exact sequence needed so many times according to those instructions.
I now have the watch automatically backing up every week. So it's not a huge deal to run a restore, but I still have to reconfigure my cards in samsung pay from scratch each time, and the whole process is extremely annoying because it just shouldn't happen.
Anyone else?
Click to expand...
Click to collapse
Only thing that I have encountered is that Samsung Pay resets itself sometimes. Has happened to me maybe 4 times in one year. Really embarrassing when I'm out shopping without phone.
Sent from my SM-G975F using Tapatalk
I had my watch factory reset by itself and now I'm with a watch with reactivation lock on.
Yep - mine was same situation - I took it off to rinse off in the sink, but didn't set water lock mode first. The screen locked, and the water running over the screen was interpreted as too many wrong passcode attempts -> self destruct. I was out of town at the time, too.
Freaking. Infuriating.
shmaque said:
Yep - mine was same situation - I took it off to rinse off in the sink, but didn't set water lock mode first. The screen locked, and the water running over the screen was interpreted as too many wrong passcode attempts -> self destruct. I was out of town at the time, too.
Freaking. Infuriating.
Click to expand...
Click to collapse
Now I know why my watch resets for a third time now. So it was the watch interpreting multiple wrong passcode attempts as a security threat thus resetting itself.
Watch self-reset for the second time--no water involved
Thanks for this thread! At least I'm not alone. I was hunting for clues because my Galaxy Watch just factory reset itself again for the second time. No water involved. The first time it happened, I had put it in my pocket while doing something messy, so I guessed that the bezel rotated randomly and caused a string of bad PIN attempts. This time it was on my arm when I discovered it had reset itself again. I can't be certain that I unlocked the watch after I put it on, so m-a-y-b-e I somehow bumped-in too many random PINs. It's possible, but I'm kinda doubtful.
Fortunately my watch backups restored after a few timeouts and repeat attempts. But restoring Samsung Pay was such a pain in the neck the first time that I think I'll give up on it for a while.
I am thinking to leave the PIN lock feature turned off for a while to see of the random reset happens again--to rule our some other defect.
I wish Samsung could handle this better, like hard-locking the watch and requiring us to enter our Samsung password into the phone app to unlock the watch.
Experiencing absolutely the same issue, guys.
I've been using it for a year and during this time it was unintentionally reset to factory defaults about 10 times, and I'm not even sure how that happens. The problem occurs on a lock screen (I use PIN to lock the entire watch, not just Samsung Pay), usually after a series of random screen touches and failed unlocking attempts (power button NOT involved). Most often, in a shower. Not exclusively though, so using water lock mode is not a solution.
I can't reproduce it intentionally, but I've noticed several times how after a series of random touches instead of setting the usual 30 seconds unlocking timeout the watch just displays a notification "Watch will reset", then a spinner with "Resetting..." label and then it reboots itself.
Every time it takes some time to restore it from the latest backup and load all my bank cards back, so it's really annoying and I'd like to know how to avoid that too. In my opinion, timeouts are pretty fine for security since it's completely possible to make bruteforcing a PIN a matter of years with them. Resetting a watch should be possible, but after several confirmations. Doing it after a couple of wrong PINs is too much, the harm is more than benefit.
Just sharing my experience...
Same as post #5
After 1 year and 3 moths of using and washing it (yes, with water and little tiny bit of liquid soap) every often and than, last month it showed the "Resetting" message.
I was really mad
I deduced it was the excessive wrong pin number attempts. I guess I was right :fingers-crossed:
Had it restored and had to activate the credit cards on spay again.
I used to have a problem with turning off the "water protection mode". Never again after a reset before the accidental one, but I stopped using it for sometime.
(just a tip I found here on xda.... if you don't restore, the battery tends to be better. Probably because something on the backup not allowing the watch to "sleep" properly)
For the people with random "Resetting", I suggest doing a "Reset" and do not restore the backup of the watch. I know it sucks, but... it might work
Related
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
Okay, so I've had this happen on more than one occasion but today it lasted for a longer period of time. I was playing Clash of Clans and looking for an opponent to steal from. I wasn't happy with the one presented and clicked to find another opponent. Well, I was launched into war. As I clicked on a location and held to deploy multiple troops, other troops were deployed elsewhere - as if I had touched the screen in multiple locations at once. Once the battle ended, I went back to train up more troops, and when I clicked and held to train multiple units of one type, it would add multiples of other troop varieties. So, it seemed as if the screen was interpreting a single tab-and-hold in one location as multiple taps in multiple locations.
At that point I figured it was time to try a reboot. Once the phone rebooted I went to enter my lock screen code and pressing a single digit resulted in multiple other digits being added to the input. I waited a minute and re-entered the screen lock code successfully.
I've gone back into Clash of Clans and it continues to demonstrate similar behavior at times. It seems as if it is more sensitive to this toward center-left (phone in landscape), which is where I usually double tap to wake the phone. Could it be related to the double tap gesture? I suppose I'll turn that off and see.
Anybody else experience strange screen-tap input issues?
StilsonCanyon said:
Okay, so I've had this happen on more than one occasion but today it lasted for a longer period of time. I was playing Clash of Clans and looking for an opponent to steal from. I wasn't happy with the one presented and clicked to find another opponent. Well, I was launched into war. As I clicked on a location and held to deploy multiple troops, other troops were deployed elsewhere - as if I had touched the screen in multiple locations at once. Once the battle ended, I went back to train up more troops, and when I clicked and held to train multiple units of one type, it would add multiples of other troop varieties. So, it seemed as if the screen was interpreting a single tab-and-hold in one location as multiple taps in multiple locations.
At that point I figured it was time to try a reboot. Once the phone rebooted I went to enter my lock screen code and pressing a single digit resulted in multiple other digits being added to the input. I waited a minute and re-entered the screen lock code successfully.
I've gone back into Clash of Clans and it continues to demonstrate similar behavior at times. It seems as if it is more sensitive to this toward center-left (phone in landscape), which is where I usually double tap to wake the phone. Could it be related to the double tap gesture? I suppose I'll turn that off and see.
Anybody else experience strange screen-tap input issues?
Click to expand...
Click to collapse
That's weird
turn on glove mode in the display setting, it will show the taps on the screen. Now you can tell if there are multiple taps. I'm not sure but maybe you can check out apps that troubleshoot screen sensitivity.
I hope it's not a hardware problem.
mr.dj26 said:
That's weird
turn on glove mode in the display setting, it will show the taps on the screen. Now you can tell if there are multiple taps. I'm not sure but maybe you can check out apps that troubleshoot screen sensitivity.
I hope it's not a hardware problem.
Click to expand...
Click to collapse
It is very strange. I did some googling and found this thread from android central: http://forums.androidcentral.com/htc-one-m8/453052-htc-one-m8-touch-screen-randomly-registers-multiple-places.html
I enabled developer tools and I have been able to see the screen register input points other than where I have touching the screen. At first I thought that perhaps it had to do with being on the USB charger, so I moved to an HTC wall charger, granted it's from my old M7. I was just playing a round of CoC when it did it again. I am now going to see if happens when not charging. If it does, then I am afraid it will have to be returned. I have only had it 18 days or so, and I believe that HTC offers a 30 day return policy.
mr.dj26 said:
That's weird
turn on glove mode in the display setting, it will show the taps on the screen. Now you can tell if there are multiple taps. I'm not sure but maybe you can check out apps that troubleshoot screen sensitivity.
I hope it's not a hardware problem.
Click to expand...
Click to collapse
An update: I turned off the developer mode option "show touches", turned on glove mode and then restarted the phone. When the phone is on the charger, if I press on the screen there are multiple dots displayed in a vertical manner along the screen. This behavior does not occur if I unplug the phone. I have tried 3 different charging devices (the one that came with the phone, an older one from an M7 and the laptop output) and with each the behavior is consistent: once plugged in and the charging circuit is active, the screen lights up in a vertical manner. If I unplug or it reaches 100%, then it behaves as expected.
Not sure if this is a software conflict issue, or a hardware issue. Feels like the latter and I have 10 days to return it to HTC.
Any ideas?
Are there any close antenna tower to you?
mr.dj26 said:
Are there any close antenna tower to you?
Click to expand...
Click to collapse
Well, funny you ask. We have an AT&T microcell just 15 feet from my office. And, here is where it gets interesting - this issue does not occur on the other side of the building from me. Our building is not big, 60' x 40', and on the other side of the building I can have the phone plugged in and everything works just fine. So...I am going to go turn off the microcell and see what happens.
<walks over and unplugs the microcell>
Bingo! The cause is the microcell. So...why does it have that affect?
By the way, thanks as I would not have gone there. I was wondering about the building's electrical and whether it was possible to have "noise", but figured it would be negated by the charger.
I have a surface pro 3 and I had the same problem when using the stylus, it kept registering points every where on the screen but when I took to the University the problem was gone. I was going to return it but thanks to the guys at the forms who figured it out. Anyway its not a big deal and I think the problem will go away after sometime. This is due to the magnetic field and things I don't understand lol.
You're good to go m8
The EVO3D had this problem too and was actually quite a common issue.
Makes me wonder what causes it and why HTC never bothered to fully protect against such issue showing up again..
sausje85 said:
The EVO3D had this problem too and was actually quite a common issue.
Makes me wonder what causes it and why HTC never bothered to fully protect against such issue showing up again..
Click to expand...
Click to collapse
its a normal issue HTC cant do anything about it
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
The other day I was sitting on the couch watching TV when I felt a vibration on my wrist. I looked at my watch and it was flipping out on it's own. At the time, I had Wear 2.0 DP installed (in which, you just swipe left/right to change watch faces) and my watch was switching between watch faces on its own, acting as if someone was holding their finger on the screen and rapidly moving it back and forth.
Using the hardware button, I pulled up the apps list and attempted to scroll down to Settings (so that I could try simply restarting the watch). It was like the watch was fighting against me, and each time I would scroll down on the list it would scroll back up on its own a little bit. After a brief struggle I was able to get it to restart, but the touch issues persisted. I opened the app on my phone and unpaired with the watch so that it would reset itself. I got through the Wear 2.0 first time setup screen, tho with enough touch input weirdness that I suspected the issue was still present... and I was right.
I managed to navigate to the Settings and got developer options re-enabled and then proceeded to flash the stock factory image. Hopeful that this was somehow just DP weirdness, I started the first time setup on the watch and could not proceed past the Language Selection screen. No matter how much I tapped, I could not select any of the languages. I noticed that the bottom 1/4 of the screen seemed to be the only part that seemed to be responding to touch input.
I pushed and held the button and got into the Settings and used gestures to get into developer options, re-enabled ADB (so that I could relock bootloader, since at this point it seemed likely that I'd need to send it in and didnt want that to be an issue) and also turned on the options to show touches and show cursor. I backed out to the language selection screen and confirmed what I had been noticing, only the very bottom of the screen was responding to touch input.
At this point, I am just looking for any additional ideas for things to try before giving up and sending it in for repairs. My watch has never been immersed in water or damaged in any way, I've always babied it. I do use Cape Cod's polishing wipes (which are lightly moistened with a polishing solution) periodically to remove minor, unavoidable scuffs and scratches from the body of the watch. I'm careful to avoid getting anything on the screen and always wipe things dry immediately after finishing, but I'm wondering if somehow a small amount of it got in around the screen somehow?
I'm a repair technician and am regularly taking apart and repairing phones, tablets and laptops, but I've never worked on a watch before. Since my watch is still under warranty (purchased in march 2016), I know the smart options is probably just to send it to Huawei, but I've heard numerous negative things about how slow their turnaround is and how they've tried to get out of providing warranty repairs for other customers. I've become quite dependent on my watch in my daily life, and hate the thought of being without it for weeks on end!
Thanks in advance to those who take the time to read this and give input!
I also having almost the same problem. Did u found any solution?
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.