Database Info

[Q] Problems - Reboots and Wifi

Hi,
After switching from my old trusty Desire, I'm beginning to regret getting the One s!
Anyone else having reboot problems? Mine hard restarts at least twice a day even if left completely idle (as it just has having been on charge for the last hour).
Wifi - Stays connected to access-points long, long gone. Was connected to my home according to the settings screen 5 hours after I left home. Data then stops flowing. Solution is to turn off and back on wireless.
HTC gave me a rather poor response. I have exactly the same apps (bare the new sense) on the new phone as the old, less even.
Anyone else having the same issues? I guess it's a software issue, but I want to return it if it's a faulty handset.
Thanks.

I think you should do a factory reset and then try the phone for a day whithout doing any changes to it. If it still restarts you should really send it back.

pjsmith said:
Hi,
After switching from my old trusty Desire, I'm beginning to regret getting the One s!
Anyone else having reboot problems? Mine hard restarts at least twice a day even if left completely idle (as it just has having been on charge for the last hour).
Wifi - Stays connected to access-points long, long gone. Was connected to my home according to the settings screen 5 hours after I left home. Data then stops flowing. Solution is to turn off and back on wireless.
HTC gave me a rather poor response. I have exactly the same apps (bare the new sense) on the new phone as the old, less even.
Anyone else having the same issues? I guess it's a software issue, but I want to return it if it's a faulty handset.
Thanks.
Click to expand...
Click to collapse
i have exactly the same problem. sometimes my device reboots without doing nothing. i had this on my black device and on my grey device after i gave the black one back. i contacted htc and the woman at the chat support just said it is a software problem and i should do a factory reset. to do that i should remove the battery (lol). because of that i think htc-employees are really unqualified.
same issue with wifi here.it stays a few hour connected without any problem. then it disconnects and doesn't reconnect.only if i turn it off and on again.It doesn't appear evertime wifi is on but it is annoying.i hope htc will fix this soon

wayne850 said:
i have exactly the same problem. sometimes my device reboots without doing nothing. i had this on my black device and on my grey device after i gave the black one back. i contacted htc and the woman at the chat support just said it is a software problem and i should do a factory reset. to do that i should remove the battery (lol). because of that i think htc-employees are really unqualified.
same issue with wifi here.it stays a few hour connected without any problem. then it disconnects and doesn't reconnect.only if i turn it off and on again.It doesn't appear evertime wifi is on but it is annoying.i hope htc will fix this soon
Click to expand...
Click to collapse
Certainly sounds like we have the same issues. let's hope HTC are listening and fix soon.

I have also some reboots. I think at least twice a week. And always when the phone is on standby. I hope also that htc will fix this soon =)

Not only with phones, but look at Windows or games, they also have bugs at start, but with time most of them get fixed

Mine also only reboots in standby. In my pocket, on the desk, etc. It's never done it during use, and I do use it a lot.

WiFi problem is noted. An annoyance, but no deal breaker as long as I have the WiFi toggle on the home screen. Guess it will be fixed when developers get their hands on the kernel source.
Had the phone for one week come Friday, and had one shutdown (not reboot) this far, and that happened as I was surfing multiple tabs in dolphin. Guess the phone ran out of operating space and had to clean itself out in a bad way

Got mine today so will let you know.
Sent from my HTC One S using XDA

Had the same reboot issue since 2 days (at least once a day). I have the phone since 10 days. The last program I installed was "adfree". I couldn't use it as I have no root rights yet but didn't uninstall it. Finally I uninstalled it yesterday and no more self reboot since. Hope this helps.

I've had the reboot problem on several occasions. Twice the 'One S' has even got stuck in a reboot loop (after login the phone restarts as soon as I try to start an app or report the error). This problem seems to be related to some problematic app running in the background constantly restarting itself and not the actual phone or ICS.
SOLUTION (worked for me):
1) Reboot the phone.
2) When 'HTC One S splash screen' appears hold down 'volume down' to enter safe mode. (Note: If you hold 'volume down' while powering on the device you may end up in a different mode. Don't panic just choose 'reboot' or 'power down' by navigating with power button and volume buttons and try again.)
3) The text "Safe mode" will appear in the lower left corner of the screen.
4) Login and uninstall any app that may be causing problems. Reboot the phone and see if the problem has disappeared, if not repeat 1-4.
Hope it helps!

Just wanted to update this thread on my reboot problem. Since the OTA update the other day, I've not had a single reboot, yet. The wifi connection / disconnection problem seems gone as well.

this is happening to me as well. Once I turn on wifi/ wifi calling the phone searches for a network then freezes up and reboots.. it keeps rebooting until I turn off wifi. This all started for me when I got the OTA 1.78 update. No idea how to fix it. blah!

That's odd. I can confirm that since the update (more than a week now?), I've had only 1 reboot whilst in 'Dolphin'. I was getting them at least daily before even when not using the phone. It's reboot in standby. All my wifi issues have gone. Wifi now seems to work perfectly.
I use the phone quite heavily. I'm pretty convinced that the update has fixed or at least significantly improved the issues I was experiencing. Let's hope it didn't break thinks for others who were not having the issues in the first place!
<oh, and btw - I do use internet calling (only in the last week though since the update)>

"UIDs on the sytem are inconsistent" error message + deleted data partition

Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3

Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.

Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.

Probably the cleanest solution HERE

Dead N5?

Is this N5 hosed?
Android 5.1.1
( I know the following because I have a second N5 that was purchased at the same time that Is still running flawlessly and they both would update within a day or so of each other, assuming this info is the same)
Baseband Version
M8974A-2.0.50.2.26
Kernel Version
3.4.0-gbebb36b
[email protected]#1
Tue Mar 10 18:17:45 UTC 2015
Build Number
LMY48B
I have a completely stock N5 that started presenting problems some months ago with random reboots, just occasionally. It would just restart no big deal, didn’t worry to much about it pretty soon the restarts came more often.
I installed the “Device Assist” App as suggested in a google forum group, to which it immediately started to recognize “Device Randomly rebooting? Try Safe Mode” ( which I didn’t at that time) it did give me the option to call a google tech and speak with them about the issue, they saw, through device assist that indeed the device had been randomly restarting. The tech ran me through clearing the device cache from the recover menu, I rebooted and everything worked fine for several weeks.
Then the reboots started again, but this time more seriously, often the unit would just power down and attempt to reboot would be meet with a short vibrate with a flash of the word google.
Eventually it would boot back up, often it would run through an “optimizing apps” routine.
I remembered as well, often the reboot(s) would begin with the “power off” screen coming up, even if I didn’t choose it it would shut down anyway and often if I dismissed it, it would wait 10 seconds or so then shut down.
All really strange.
So I got a hold of a google tech again, this time they suggested rebooting in safe mode and running several days like that to see if it was a software or hardware issue.
In safe mode it ran without issue for 48 hours( normally this would have resulted in a handful of restarts at best. Google tech seemed to think it was an app issue since the problem didn’t return in safe mode and suggested a complete factory restore,( and to setup the phone as a new phone rather than restore any back info form google) I was backed up so I ran the factory restore from system settings “back up and restore” .
Once restored it worked fine for a day and then it all went downhill from there, power off screen would appear (often when I short pressed the power button to sleep the unit) and again if I dismissed that dialogue it would power down anyway and it would take numerous tries to get it to power back up, almost every time it would run through the “optimizing apps” routine.
Within a day, it just stopped powering up. If I plug the unit in to charge it does this odd cycle of black-screen/short vibrate/Flash the word Google, about every 2 seconds, it never shows a battery charge indicator
If it is not plugged it won’t do anything, if it is plugged in when I tried to boot into recovery, the recovery screen would appear for a brief second and then it will start the vibrate/flash “google “ cycle.
It does nothing when placed on a wireless charging plate.
Google tech said it is out of warranty ( which I knew) and gave me a number to LG to see what options they suggested.
I suspect it has something to do with a sticky or malfunctioning power button, but wanted to see if anyone here has and experience with this type of issue or has a suggestion.
Thanks

Question Z flip 3 bootloop

The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer

Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.

I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.

Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left

twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer

There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.

I see, alright, thanks a lot, I'll consider resetting it

It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.

Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )

ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.

Question Why does my phone randomly keeps shutting down?

As the title says: Yesterday, my phone turned off by itself even though it had 80%+ charge. It went into a bootloop when I tried turning it back on and after a while, it booted into Recovery Mode and refused to reboot to system. When I came home, I plugged it in and it started working normally again. After an hour or so, same thing happened. This time, it didn't bootloop or go into recovery mode, it just refused to turn on till I plugged it back in. It has been happening ever since. Will randomly turn off, won't turn back on if I don't plug it in once. Also, it only happens when the phone is folded and sitting idly. It doesn't turn off if I'm using it.

Any new updates, upgrades or apps?
Boot loops are many times 3rd party app related.
Back up all critical data as next time it may go down for the count.
Clear system cache.
Try a hard reboot.
If it persists try running in safe mode to try to rule out a 3rd party app. 3rd party launchers and power management apps are always suspect.
Try to track down the cause, and always suspect malware if nothing else can be found. Avoid a factory reset useless it's malware that can't be purged or if you really can't find the root cause.
Otherwise it's likely to reoccur with the next load.
If a factory reset doesn't get it, the cause could be a SEU, these are rare but can happen. If it's in the user data partition, a factory reset will fix it.
If it happen elsewhere in the firmware it will need to be reflashed. It causes no hardware damage.
Lastly if all the above fails, it's likely a hardware failure. A Samsung Experience Center at a Best Buys can run advanced diagnostics on it and reflash it if needed. If you get stuck this may be a good option if stateside.