Related
Hi just got one of these tablets from factory direct. got home, charged it and it was clear they didn't test it. the display is lite up weird were its hard to make out txt and there is alot of flickering like you would see if you watched someone use an old crt on television. not to mention, the tablet looks like its running on 256 colors.
it was supposed to be on hc 3.2 but when i booted it up it was on ics 4.03.
is this an issue were someone had it, messed around with it and possible screwed something up software wise? is this a driver issue or faulty hardware?
i tried factory reset, didn't do anything. I am downloading a fresh ics image and will try re flash with it but im not expecting much,
1 more thing, upon turning the unit on, the display is messed up like i mentioned above right from the get go.
can i save myself a 45 minute drive back to factory direct or do i go there and throw it at someones head?
swebosdev said:
Hi just got one of these tablets from factory direct. got home, charged it and it was clear they didn't test it. the display is lite up weird were its hard to make out txt and there is alot of flickering like you would see if you watched someone use an old crt on television. not to mention, the tablet looks like its running on 256 colors.
it was supposed to be on hc 3.2 but when i booted it up it was on ics 4.03.
is this an issue were someone had it, messed around with it and possible screwed something up software wise? is this a driver issue or faulty hardware?
i tried factory reset, didn't do anything. I am downloading a fresh ics image and will try re flash with it but im not expecting much,
1 more thing, upon turning the unit on, the display is messed up like i mentioned above right from the get go.
can i save myself a 45 minute drive back to factory direct or do i go there and throw it at someones head?
Click to expand...
Click to collapse
Aim well, that's all kinds of broken.
Sent from my HTC DNA
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
You answered your own question. You need to try a factory reset. Problems happen when you upgrade to new software without wiping.
dschachm said:
You answered your own question. You need to try a factory reset. Problems happen when you upgrade to new software without wiping.
Click to expand...
Click to collapse
Dschachm is correct. Then if you root and install TWRP you can back it up with all of your apps and data. So if there is ever a problem again, just restore and done.
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
I've gotten the sprint yellow screen and nothing else.phone doesn't turn on? When I try turn it on after removing batteryou I get the android figure and phone turns off? How can I reboot or start the phone..?and can I save my contacts?
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
agentfazexx said:
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
Click to expand...
Click to collapse
I have the same problem too!
I've tried the reset multiple times, battery is always at 100% when trying. Getting very frustrating. Any ideas? Google has not been helpful.
Just says "Resetting, please wait" then "Restarting" then goes black until I dock it again, at which point it boots back up like all I did was reboot it.
Any help at all here?
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
gd6noob said:
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
Click to expand...
Click to collapse
None of that is working for me. It just turns off when trying to reset while at 100% battery.
I think this watch is just broken. I had it off the charger and when I re-docked it and it turned on with 54% battery. 5 mins later, it was at 100%.
I have the exact same issue :/
Still unable to factory reset this..
So, finally got this reset to happen...now ~30 minutes after the initial setup has finished, the watch battery is dying while on the charger. Thoughts?
It's (kinda) charging now. I just have no watch faces to pick from. Not really syncing.
I had the same problem - after multiple tries it worked.
After several days of waiting, I still have no ability to pick watch faces from the Android Wear app. Thoughts?
Moto 360 first gen. reset
The trick is to un-pair and reset it while is charging. good luck!
RD
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.
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