Hello everyone. Just got my hands on this beauty, but I cannot for the love of any deity known to me get it to go past the second step of what is the initial, first boot of Android: it turns on, asks me to select the location and the language, takes me to the next screen saying "select Wi-Fi" and...that's it! there are no networks available and the only info I see is "Turning Wi-Fi on", which stays there forever. The device itself works fine I guess - volume buttons raise/lower the volume, the power button switches the screen on/off, I can enter recovery mode... I tried literally everything I could think of, from wiping the cache and the data, to trying to roll back to 5.0.1 (though I keep ending up with 5.1 somehow, but that's a different story).
Anyway, does anyone have an idea about what this could be due to? Any help will be greatly appreciated as this issue has got me going nuts over here
EDIT:
so, I plugged in the earphones and was somehow able to bypass that step! now, I can freely use the tablet, but when I open Settings -> Wi-Fi, the Wi-Fi toggle is gray and cannot be switched to 'on'; in ADVANCED, the MAC and IP addresses both appear as 'unavailable'; it seems as if the Wi-Fi module was missing/not working. what could this be???
Related
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 have a MyAudio 708w on android 4.0.4, and i was using it when it suddenly dropped the wifi signal. When I tried to go to settings to reconnect, it froze, and i could only reboot it by long pressing the power button. After rebooting nothing changed, i can't even touch the lower right corner where the settings and notifications are because it freezes immediatelly. I also did a factory data reset from the recovery menu. After that I found a way to go to the settings (by adding a settings widget on the home screen) and the wifi line disappeared. I don't know how it is possible... the wifi radio is working by the way, i know that because i tried to add a new google account, and when i chose "existing account" it said i have to connect to the internet, and there i could activate the wifi and it also found the networks but it couldnt connect (it's stuck at obtaining ip adress).
Has anyone seen anything like this? Do you have any idea what i could do to fix it?
Thank you in advence!
Hello! I've updated my D6503 (DE unbranded) with 23.0.1.A.0.167 and I've got the issue I can't turn WiFi on.
1. Settings -> WiFi shows the grey screen with 'Turning WiFi on...' message.
2. On/Off button is greyed out (doesn't work) in Off position.
3. WiFi widget (stock one) is slowly 'flashing'.
Restart through now available software option doesn't help. Phone starts and WiFi is immediately in turning on.. mode.
Power off doesn't help as well.
I've managed to turn it on by switching to airplane mode, then restarting via hard reset (power on+volume up) then turning on, disabling airplane mode. This way it turns on, connects to my access point but in a minute it's disabled again and starts to show this 'Turning WiFi on...' message again.
I've made factory reset through phone. Now 'Searching for Wi-Fi networks...' message is on welcome screen step 3. None access points are seen.
I've made factory reset through PC companion. Now 'Searching for Wi-Fi networks...' message is on welcome screen step 3. None access points are seen.
Support basically trolls me (I live in Cyprus, without any local service centers), so it's no use as well.
Please help me, thanks in advance.
So I know this topic has a few posts many a year or so old but I'm looking for a possible work around for this issue. Here's a background of what happened:
I have a rooted note 4 originally running cm12, I wanted to return to a stock build and when I did something happened (can't remember what) and my wifi stopped working it would click on them immediately off my first thought was kernel so I flashed a new one but didn't help I tried a different stock build 5.0.1 instead of 5.1.1 but still same issue. I went back to the cm12 and that seemed to work fine still, I looked for another stock build because I'm stubborn and flashed a different kernel than the previous ones I've tried. This seemed to fix my wifi issue at least for a day then back to the same issues. Anyway here's what I've been messing with to try and figure this out.
I'm focused around the file wpa_supplicant.conf as I've tried restarts and all that but that won't do anything. What I have noticed recently is when I don't have any networks saved in that file I can toggle airplane mode and try toggling wifi, after a few sometimes dozen attempts it comes on and works fine so long as it stays on. If I turn it off I have to restart my process of going into wpa_supplicant.conf>deleting my saved network>toggling airplane>then spamming wifi. As I'm able to repeat this it leads me to believe it's not hardware related, slim chance on loose cable, But if there's a way to prevent the system from auto saving a password that might help with a workaround. I've tried changing that files permissions as well as the ones in the system>etc>wifi folder but they get changed back
Anyway I'm still working on finding the root cause but will update if I find anything also tried deleting the wpa file and that works to after a restart but issue comes back and so does file which doesn't seem to me that its a corruption issue
Update:
So I somehow crashed my Samsung messenger app switch to hangouts and then back so decided to wipe my phone and refresh the OS. I factory reset then advanced wiped cache, dalvik, system and data. When it rebooted I tested the WiFi in the system setup and it worked fine I could turn it on and then off normally so I decided to continue setup once fully setup and no other apps installed I retested the WiFi. It worked fine I connected to an access point and it stayed connected I then forgot the network cycled wifi and tried again and again still worked so I let it sit and would test it throughout the day. About an hour or so later the problem reappeared which was odd. I did my old workaround deleting wpa_supplicant.conf and toggling wifi until it turns on. I got it to turn on and connect to my home WiFi and left it, so far I've kept my wifi on and it's stayed active for 24hours now and reconnects fine to my home router when I'm in range and back to lte when I'm away so right now it seems I can have wifi if I don't toggle it off. Still not sure what's causing this issue as since I'm currently using wifi to write this I don't see it as a hardware issue. After trying multiple kernels I don't see that as the cause either, although possible. Will keep messing around and update if I find anything further
Update 2: so far I've been able to keep my wifi working great as long as I keep it on and don't toggle it off. Doing this has kept it active and auto connecting to my home wifi for a week straight. I make sure to keep wifi I during sleep so it won't disconnect but it also seems to stay active through restarts which is great. This still leads me to believe it's software related and not hardware but not sure where the issue is.
Update 3:
So far I've just kept my wifi on while trying to find the issue. The only other issue I've come across was since my wifi is on 24/7 and auto connects if I want to use my lte instead i have to either turn off wifi or forget my home network which neither is an option. But I have found a solution:
I was able to add a shortcut to my home screen that actually disables the current wifi connection without disabling wifi and forgetting the password. To do this you must have Tasker just create a new task in second tab, I named mine disconnect wifi, click the plus sign and select "net", next select "wifi net" there is an option that says disconnect. Have that selected then go back and thats it,add in icon on bottom right to use as a shortcut. I've tested this and it works great one tap and it disconnects the wifi but keeps wifi turned on and if I want to re connect just go into WiFi settings and choose the one to connect to
Has anyone had this and fixed it, or do you know how? I have a Swift2Plus.
Since the Nougat update I have random disconnects from WiFI (gets turned off) Bluetooth (gets turned off) and phone (SIM taken out of service). It makes my phone pretty useless as it's a pain repairing all of these and I miss calls and messages. Also Bluetooth is always showing in settings as disconnected, even when it's turned on and working.
So far I've tried a network reset and deleting the system cache but nothing changes.
slowswift2 said:
Has anyone had this and fixed it, or do you know how? I have a Swift2Plus.
Since the Nougat update I have random disconnects from WiFI (gets turned off) Bluetooth (gets turned off) and phone (SIM taken out of service). It makes my phone pretty useless as it's a pain repairing all of these and I miss calls and messages. Also Bluetooth is always showing in settings as disconnected, even when it's turned on and working.
So far I've tried a network reset and deleting the system cache but nothing changes.
Click to expand...
Click to collapse
I'm also having Network issues, my Hotspot turns itself off at least 3 times in a row before staying on, and I get a lot of 3g connection indicators, my network hasn't changed and I'm in a strong 4g area . . eventually the phone settles on 4g . . I'll also point out the pointless duplication in the UI, previously the pulldown menu was a straightforward tap and select for Bluetooth etc . . now it takes you to a second screen where you can turn Bluetooth on/off . . total waste of time and poor interface design.
I've no problems with wifi and bluetooth, but there is an OTA update fixing these issues (see WileyFox facebook). So wait a few days for the update...
badwolf69 said:
I'm also having Network issues, my Hotspot turns itself off at least 3 times in a row before staying on, and I get a lot of 3g connection indicators, my network hasn't changed and I'm in a strong 4g area . . eventually the phone settles on 4g . . I'll also point out the pointless duplication in the UI, previously the pulldown menu was a straightforward tap and select for Bluetooth etc . . now it takes you to a second screen where you can turn Bluetooth on/off . . total waste of time and poor interface design.
Click to expand...
Click to collapse
Wileyfox suggestion of clearing the system cache seems to have fixed the random disconnects, so you could try that. On my phone there didn't seem to be any issues created by doing that.
They did say in reply that the issue of Bluetooth being permanently shown in settings as disconnected (even though it's on and working fine) was a known problem they were working on.
That tallies with the helpful post below from rivierakid saying a Wileyfox fix was in the works.
badwolf69 said:
I'm also having Network issues, my Hotspot turns itself off at least 3 times in a row before staying on, and I get a lot of 3g connection indicators, my network hasn't changed and I'm in a strong 4g area . . eventually the phone settles on 4g . . I'll also point out the pointless duplication in the UI, previously the pulldown menu was a straightforward tap and select for Bluetooth etc . . now it takes you to a second screen where you can turn Bluetooth on/off . . total waste of time and poor interface design.
Click to expand...
Click to collapse
BTW here are the instructions for clearing the system cache, courtesy of Amy at Wileyfox-
"If you are using a model previous to the Swift 2 series, please try the following.
"Wipe cache partition"
To do this, please turn off your Handset.
Press and hold down the Power and Volume down button together until a menu appears.
Select "Factory reset", "Wipe cache partition" and then "Yes".
this should not take long, now go back and select "Reboot system now".
Please monitor your handset over a few days to see if this has resolved your issue.
If you are using the Swift 2 series, please try the following.
"Wipe cache partition"
To do this, please turn off your Handset.
Press and hold down the Power and Volume up button together until a menu appears.
Press the volume down button until you see "Recovery mode", your Handset will restart and enter another menu Select "Factory reset", "Wipe cache partition" and then "Yes".
this should not take long, now go back and select "Reboot system now"."
I didn't understand the reference to factory reset and just used "Wipe cache partition", which seemed to do the job.
Good luck!