I've done a quick search of this forum and [ALARMINGLY] can't find a solution (or any references) to a continualy cycling reboot on my daughter's day-old Sony Tablet S.
What's happening is, the system boots, I see the unlock screen for a few seonds and then it reboots again!! No time to do anything.
The power button (in combination with either of the volume buttons) doesn't do anything when the boot animation is being displayed. And the reset button (in the tiny hole) simply turns the tablet off, but the cycling reboots start again when powered back on.
Just so you know, I have owned and used the Morotola Xoom since August 2011, so do have some experience with Android Honeycomb, but nothing like this. Oh, and I have not attempted to root either machine.
Here's what I believe is the cause: I was copying a file off a network share (using a third party file manager), but it was VERY slow. The transfer mustn't've finished when I turned the tablet off (completely) for the night.
Therefore, I assume it is trying to resume the transfer, but there is a problem (possibly the WiFi connection is slow to connect). Nevertheless, I would have thought Andorid was more robust than to simply reboot... an error message would be a bit more "professional" and much more welcome than a cycling reboot that does not allow me to do a F%^&$#G thing about it!!
PLEASE HELP or point me to a forum that may be able to.
Thanks in advance.
Wow. That tablet is toast. Something must have been corrupted when you turned it off.
My girlfriend had an HTC Sensation 4G that had similar problems the day she bought it. HTC and our cell provider gave us the run around denying responsibility. We rooted it and flashed a new ROM which completely fixed it though. In your case for the Tablet S this solution is impossible as the tablet hasn't been rooted yet.
Return it to the store asap and tell them it's not working properly!
Have you tried the reset button on the side underneath the volume button. Just stick a pin in thhere and hopefully voila.
Let us know if that works.
Sent from my Sony Tablet S using Tapatalk
Cycling reboot - FIXED!
mightyfo said:
Have you tried the reset button on the side underneath the volume button. Just stick a pin in thhere and hopefully voila.
Click to expand...
Click to collapse
motoscoddie said:
And the reset button (in the tiny hole) simply turns the tablet off, but the cycling reboots start again when powered back on.
Click to expand...
Click to collapse
Yeah, mightyfo, I did. Thanks for your reply, though.
Anyway, I have attempted a few more "fixes". Among them was to delete the partial/currupted files from the SD card, without result. Then, for some reason, I turned off my WiFi access point, and, bugger me, the tablet booted! I turned the WiFi back on to be certain it was responsible for the problem and, yes, the reboot cycling started again.
Obviously, I turned off the WAP again, booted the tablet and killed the saved connection. Once I turned the WAP back on, I re-established the connection and the tablet has behaved ever since!
Just so you know, I did have the latest System update (v3.2.x) when all this was going on...
Makes me wonder if it is an Andorid issue, or something Sony have done while tinkering with Andorid. I just hope my findings can help someone else in the future.
Sounds like you need to do a system reboot.
Comprehensive explanation of the problem
Please take a look at the following very thorough explanation of the underlying cause of the reboot problem:
[Can't post links] Search for "android stops renewing lease" in Google and select the Princeton link (should be top of list).
My fix was to turn off the WiFi AP (to stop the reboots), delete ("forget") the connection and then set a static IP outside my DHCP range.
Hope this helps someone else...
I've searched high and low, and can't seem to find anyone with this same issue caused by flight mode. I'm having an issue with TWLauncher on my SGS2 running 4.0.3 (Optus official update in Australia).
I've had this rom installed since its release in early April 2012, and have only been having issues with the occasional MAPServiceSamsung crashing with the SMS app.
This arvo I flew interstate, and hence turned the phone into flight mode, and then turned it off. When I turned it back on in the plane, the phone refused to open into the home screen, as TWLauncher kept crashing.
Initially I thought it may have been a flight mode issue, and somehow I struck some luck and managed to turn off flight mode so I had HSPDA connectivity again. But this made no difference.
I did a soft reset, wiped the cache, took the battery out for 30mins, and ended up having to do a factory reset to get use of my phone again.
Being interstate I have a work laptop, which doesn't allow me to use Odin and hence flash any different firmwares on.
I'm wondering if anyone else has experience this, and/or whether anyone has any suggestions on how to fix/make sure it doesn't happen again? Could the TWLauncher error be linked to flight mode in some weird way (I only ask as the phone had never done this previously).
Thanks in advance for any ideas.
cjhod1 said:
I've searched high and low, and can't seem to find anyone with this same issue caused by flight mode. I'm having an issue with TWLauncher on my SGS2 running 4.0.3 (Optus official update in Australia).
I've had this rom installed since its release in early April 2012, and have only been having issues with the occasional MAPServiceSamsung crashing with the SMS app.
This arvo I flew interstate, and hence turned the phone into flight mode, and then turned it off. When I turned it back on in the plane, the phone refused to open into the home screen, as TWLauncher kept crashing.
Initially I thought it may have been a flight mode issue, and somehow I struck some luck and managed to turn off flight mode so I had HSPDA connectivity again. But this made no difference.
I did a soft reset, wiped the cache, took the battery out for 30mins, and ended up having to do a factory reset to get use of my phone again.
Being interstate I have a work laptop, which doesn't allow me to use Odin and hence flash any different firmwares on.
I'm wondering if anyone else has experience this, and/or whether anyone has any suggestions on how to fix/make sure it doesn't happen again? Could the TWLauncher error be linked to flight mode in some weird way (I only ask as the phone had never done this previously).
Thanks in advance for any ideas.
Click to expand...
Click to collapse
I am also running on the Australian stock version (XWLP8), but not having this issue.
Can you reproduce the issue?
Or is it now fixed after wiping cache partition and doing a factory reset?
If the issue is still existing, you can try to flash another firmware (first another kernel, and only if that does not help another ROM) ... or you should use an alternative launcher.
I will try and replicate it again in my flight home on Wednesday. Whilst I am away from home I will limp the phone around as stock as I can.
Thanks for the reply.
Ah! I had the same issue and it drove me crazy cos it would take ages for the phone to restore itself..
I was using a stock Indian ROM and I guess my issue too was repeated after I switched on the flight mode.. Tried all the resets and other workarounds but to no luck..
Just installed a custom ROM now and everything's back to normal..
You can google for some workaround on TwLauncher, but for me none worked..
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Hi guys,
I have tried to search for a solution but couldnt find anyone having the same issue....so here goes
I am using a stock Vodafone AU rom 4.0.4 which is rooted......rooted used to remove drop box, navigaton (or something like that) and other bloatware.
However, after rooting - when Wifi is turned on but not connected to any network i seem to have screen issues. No response at all - when i press power button it doesnt turn off just dims, i press it again and screen lights up but yet no response. When i turned wifi off - this issue doesnt seem to happen. Also when i turn it on and connnect to my home network - no issue. Only seems to happen when after rooting + when wifi on and not connected to network.
Has anyone encountered this issue? Any help suggestions would be appreciated.
PS. I have restored factory settings, reinstalled firmware via odin and gone thru all settings on the phone. But under the above mentioned conditions - this issue happens. Seemed with out rooting - phone had no issues for last 5 days.
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.