Related
I just recently got this tablet from someone else. (This person had no problems and is trustworthy in reporting all that was done and care taken with it, even offering on advice on things you can do with it.)
My first step was to connect to Wifi. This happened without problems.
When returning home from work where I also connected, my wireless connection(s) said "Disabled" after trying to obtain the IP where they worked fine before. The first time this happened I had to do a factory reset to solve it (hardware reset didn't do it).
Today, it is happening again. I woke it from "standby" to start using again at home and received this message. In fact, any attempted WiFi connections comes up saying "disabled" after attempting to connect and obtain an IP. Again, these are saved connections that previously worked. I know for a fact that it's not the routers.
Please help if you can. I've tried:
1) power off/up 2x in a row to no avail
2) removing and adding back the connection with the appropriate passwords
3) a factory reset but I really don't want to do that again because I'm afraid flashing it back will bring back the same problem.
3) I haven't put any new apps on it since it last worked earlier today so I can't figure that as an issue. The first time it happened a week ago was when I'd just gotten it. It has worked for almost a week without problem. I did nothing special but travel home.
SPECS:
A500 Wifi
Rooted (was unrooted when it first happened); rooted now using IconiaRoot v1.3
(previously rooted and unrooted with Gingerbreak which would no longer root)
ROM: Honeycomb 3.1 with Virtuous Picasso v.1.1.0
Kernel: 2.6.36.4-UNITY-V5-ge7dee2a-dirty
Thanks in advance.
it's a known problem with this tablet when moving from one access poin to another, introduced with the update to 3.1. you have to reset using the pin hole near the micro USB port. i use a staple.
it may take a few tries. if it never works, there's a specific file you can delete if you're rooted. if you cant do that, you will have to do a device wipe.
There is a known issue of connecting to PEAP/EAP networks, which most work networks are. After connecting successfully, often many times, it will suddenly fail to connect. It also shows the signal from the access point to be very low or non-existent. After this happens, it can also cause problems with other PEAP/EAP access points as well.
If this is what happened to you, here's the fix. Try to connect to the access point giving you problems. While it is stuck on trying to connected, click the access point name and tell the tablet to Forget it. Then enter the same access point information manually and try to reconnect. This fixed my problem, and the fix sticks for a few weeks or so until it comes back.
Interesting, I had this same problem a few weeks ago when I visited my parents house. After a couple reboots it just started magically working again and didn't think anything of it. Their router is whatever the Verizon FiOS people install when you get their service.
Thanks, GeekGuy and Falkner, but.....
I've tried both before, but I went ahead and tried both of your recommendations again (pin reset and connection attempt/forget/add). Neither fixed it.
I would like to try to delete the file that Falkner mentioned, but you didn't specify a name and/or location of it. Can you share that?
I could never find what file to delete, so I've just installed a new ROM (thanks to XDA for info on all the how to stuff).
We'll see if it repeats.
Gone from V.Picasso v.1.1.10 with HC 3.1 to Taboonay 2.1 with HC 3.2.
Thanks for the attempted help!
Just guessing but I would say your problem is solved since no reply from yesterday?
Per my last post, I've switched ROMS. As it happened randomly before, I can only wait to see if it happens again. I will post back if it does.
And....as of tonight it happened again.
Note: Different ROM working since the last post 9-26-11.
ROM Taboonay 2.1
The only thing I can wonder about is if it happens when it tries to connect to a network that is actually down such that it cannot obtain an IP that actually gets internet access. However, it was "disabled" when I brought it up before ever trying to specifically reconnect to a network to realize the ISP wasn't doing their part.
Still....no reboots, or hardware resets have worked. I'm working on an image restore of only the system from the 9.25 install of the ROM rather than a factory data reset. Not sure if that would have been better. Trying to save some of what I've done recently. Gonna have to get used to a weekly backup if this is to continue.
Grrrrr..........restoring a backup turned out to be the last ROM. After reinstalling Taboonay 2.1, I still had all my apps and found the same problem. I'm doing a factory data reset as it's the only thing that fixed it before :-(
The only "oddity" I've experienced has been since last Thursday. The Android Market doesn't even recognize now that I have another device. Have communicated with them; they are investigating and saying they have received reports of this on free downloads giving an "unable to process purchase" message. It updates installed apps, but I cannot download any new ones through market, appbrain -even the appbrain app only and not to the market app. I can download through Amazon, so it's the Market issue. Still, that shouldn't affect this issue.
If you have any constructive feedback, I'd appreciate it!
This was happening to me. I had problems with every rom I tried until the following combo: Taboonay 2.2 with Richard's Villain ROM 3.7 kernel. Every other combo would lead to erratic wifi...now it hasn't happened in 2 days. I don't know why this is happening as many of the roms I tried claim to have the wifi fix integrated. I hope this helps. Just flash the latest Taboonay and then the kernel zip file on too of it. By the way, latest rabbinate is 2.2....NOT THE ONE YOU HAVE NOW.
Sent from my A500 using xda premium
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.
Wexberg said:
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.
Click to expand...
Click to collapse
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
DeadlySin9 said:
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
Click to expand...
Click to collapse
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Wexberg said:
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Click to expand...
Click to collapse
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
DeadlySin9 said:
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
Click to expand...
Click to collapse
Wexberg said:
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
Click to expand...
Click to collapse
I don't know why that would work. At this point I'm not sure what else you could do. I know I used to have WiFi issues after some flashes with my Inspire but i never really had a fix even then.
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Been there, done that.
It's not a hardware problem. It is, I believe, problems with the restrictive 4.3 update not playing nicely with some system settings. In short your system drivers or configuration settings are getting messed up to to bugs in how Knox and the bootloader are interacting with the modem.
I had your exact symptoms after installing certain custom ROMs, also noted that the problem could be temporarily "fixed" if the boot process was interrupted or by specific sequences of modem changes. The situation is not helped by Bell being more restrictive than other Canadian carriers e.g. Rogers, something that also caused me problems when I was enabling AWS on a Bell firmware.
The effective solution was to install a custom recovery to facilitate a complete wipe of files, then flash a Rogers stock image. Cured. And continuing to work properly if subsequently returned to a Bell stock image. Although, frankly you'd have a more stable and flexible platform if you you kept the Rogers image in the end. If the build properties edit doesn't solve your issue, then here is a path for you to pursue.
.
1/2 Lit Toggles - build.prop editing issue
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
jrwebdev17 said:
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
Click to expand...
Click to collapse
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
DeadlySin9 said:
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
Click to expand...
Click to collapse
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Editing build.prop is a plausible workaround if the OP has root access. If he doesn't wish to root his phone, then he can clean up his system configuration by reinstalling as I described earlier in the thread without requiring root. Two approaches to the same result.
And yes, you can add the entry if it doesn't already exist in your configuration.
.
jrwebdev17 said:
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Click to expand...
Click to collapse
UPDATE: I didn't have any luck using the build.prop fix, nor with the wpa_supplicant.conf fix that some of you may have seen mentioned. I ended up Recovering to stock MF3, (I was already on MF3). This gave up my root access, and I didn't take any additional steps to hide busy_box or anything like that, after my MF3 recovery it looked like I was safely unrooted and I contacted AT&T support via web-chat, and they asked some questions and sent me to a nearby AT&T device center. I took it there, they didn't ask a single question about how it happened, whether I had rooted it, etc(although I was paranoid that there would be traces left behind and they would turn me away). Long story short, they replaced the phone no questions asked!
In my opinion it would seem that while this problem could in some cases be caused by rooting and tinkering, it's enough of a known issue to AT&T that they would replace it under warranty. Hopefully Bell or other carriers would do the same. My advice is to try your carrier, particularly if you are with AT&T.
Just to help people who are searching for a solution. I had flashed a T-Mobile rom and my wifi stopped being togglable on my AT&T S4. That is, I couldn't turn on wifi. The button would get stuck on. After trying to flash what I thought was the right MK2 modem and still having the same issue, I thought I was out of luck. However, I found this one here: http://forum.xda-developers.com/devdb/project/dl/?id=3275 and hit paydirt. Flashing it using Safestrap and then wiping cache and delvik worked. The file is called jflteatt-MK2-modules.zip.
Only for WIFI, for me what worked was I had to open a litte bit the one side of the phone and close it again (removing a little the plastic, like if you were going to open the device) Wifi started working again, no need to flash any roms, it seemed to be something related with pressure, humidity or something inside the phone.
Regarding bluetooh I had no luck still not working, only keeps saying activating and never gets activated.
does anyone find a solution for this yet?
I have had the same issue for months. Started after warranty was up. I have AT&T on nc1. I tried everything mentioned here but nothing worked. Even left it with the phone repair guys for a week with no luck. It first started after I flashed Hyperdrive ROM. A reboot helped for a while. It actually came back for a week on Kevp's ROM, but then had an error that reboot the phone and lost it again. Phone is now on Craigslist and I am back to my S2. On a high note it's nice to not have a unlocked bootloader again.
you need to flash the exact same model/firmware's modem file atleast thrice before giving up.... i have a simalar issue the thing is my model number is 1377z and google doesnt have a working flashable modem file for it so basically i am screwed too wifi calling and video recording doesnt work....
update :: saw that you got it replaced !!
smoooth .....
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
Just tried this on my sgh-i337m that was having the same wifi issues after rooting and flashing a kernel. Rebooted and wifi is up and running. So far so good. Thanks a lot!
Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?
Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it
I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?
Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:
I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.
Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards
Hello all,
I've been searching for 3 days now and cannot find a solution to this problem. Normally I try to avoid starting a thread since there is usually one on the internet somewhere already, but this has me stumped.
I have a SGH-I337M on Bell, was running SlimKat 4.4.4 with no problems, and wanted to upgrade to LP. I first tried installing the CM12 optimized build, but it would never get past the boot screen. Then I tried GPE 5.0.2, and it looked beautiful and ran smoothly, but it would not automatically connect to Bell's network. If I went into the mobile networks menu and waited for it to scan, and then selected Bell, it would connect, but a few minutes later it would disconnect again. WiFi worked fine. Needless to say, having no constant service was unacceptable. After that I tried installing SlimLP (wiping cache, system, etc in between all installs) and had the same service disconnection problem.
Then I tried:
-flashing modems
-flashing back to stock from SAMmobile and reinstalling (where a similar problem persisted)
-starting from fresh to GPE, then starting from fresh to SlimLP
-reflashing GPE with all 3 kernel choices, cutting out as many installation options as I could
-trying different combinations of preferred wireless mode, APN, etc
Nothing works. I am back on SlimLP and I have got it to the point where the Bell service will work as long as the screen is on, but when I hit the power button and/or the screen goes off, the network disconnects again. If WiFi is NOT on, when I hit the power button and unlock the lock screen, it will automatically connect to Bell again, but this does not happen if WiFi is on.
Any ideas here..? I've read countless threads and nothing seems to work. Any help would be much appreciated as this is driving me crazy!!
The issue has been resolved! Apparently I was too impatient and was not using the proper modem
But I can't find a way to delete this thread. Damn I must be getting old
Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
try this rom
follow the guide completely
http://forum.xda-developers.com/oneplus-2/general/rom-hydrogenos-v1-2-0-sensors-t3264711
araaraara123 said:
Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
Click to expand...
Click to collapse
Earlier today, my fingerprint sensor/home button completely stopped working.
I tried restarting, wiping cache and dalvik cache, re-installing the ROM, and I even went back to OOS and H2OS (both stock ROMs) to see if it would work. Alas, nothing worked.
A friend of mine then called me. I told him my home button is dead. He told me it happened to him once, and all he had to do was force restart the phone and it worked again.
I'll suggest that you try the same.
Hold the power button for ten seconds while your phone is on and it'll force restart.
Hope this fixes your problems, mate!