Database Users

Wifi not starting - solution yet? (Maybe WMWifirouter related?)

My wifi won't start. Whether it's through TouchFLO's comm manager or Window's own Wifi connection, it will give me the "Busy" rotary and then nothing happens.
I know exactly when the problem first appeared, though. I was using WMWifirouter (an ancient version, .8 or .9 something) while it was tethered to a Macbook for power (I think on ActiveSync, but I don't remember). From what I gather, that might not have been a good idea, or, rather, that theoretically should not have worked. But, it did. I disconnected the phone, and since then I've had the aforementioned wifi issue.
I've searched XDA and Google, and it seems the best answer I can find is to hard reset and see if it works. However, it seems that for a large majority of people who tried this method, the problem doesn't go away.
I'm hesitant to try a hard reset, as my HD's been working fine for the past 5 months and I've got a lot of time and work put into it, when it might not get me anywhere.
Hence, I'm asking if anyone's come across a solution to this problem that might work. I'm hoping it might be as easy as a registry tweak (I have seen some "solutions" that involve the registry, but they don't appear to apply in this case).
Since I'm in the US, and the HD is not officially provided by any carriers, I might have a lot of trouble getting any kind of warranty work done on it, and that also entails losing the phone for 2+ months, as best I can tell.
I might try flashing a newer HTC ROM, although I would be pretty mystified that my old ROM suddenly wasn't good enough. Maybe it's just that a new factory ROM would place the correct registry settings back in order?
Sorry for the long post, I'm just frustrated that I am unable to use wifi and that I'm starting to think the only solution will be to get a new phone or live without it.
Does anyone have any thoughts?
(I've looked at several threads on XDA already, none of them were at all resolved or even directly discussing the HD, so I think it's okay to post this thread.)
EDIT: I could tell I was going to get no response here, so I just went ahead and hard reset the device. That seems to have fixed it, for now. Wifi's working how it should. I'm adding this edit here for anyone else has this problem.

Just a bump, and also to add that when I run WMWifirouter with logging, it shows that it fails to Rebind the WLAN and also the CM-Set fails, if that is any clue.

Another detail, I notice that under Settings > Connections > Wi-Fi > Advanced > Advanced, there is nothing under Status, MAC, IP...I'm guessing that will always be empty if it's not connected? If not, are there values I should fill in?

Bell Atrix , lost wifi, bluetooth and rebooting lots

Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks

A friend of mine has the same problem, Im pretty sure thats a hardware issue already. !

running gb 2.3.6 #4 - still no wifi/bluetooth

Having the same issues. Does anyone know if wifi and BT share an antennae?

try flashing a differnt radio? for your phone specs
look in ihop thread or fruit cake thread for your radios

r0nz3y said:
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
Click to expand...
Click to collapse
schufly73 said:
Having the same issues. Does anyone know if wifi and BT share an antennae?
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue... I have been having this problem myself, and have tried flashing many of ROM and Radio's since it has reared it's ugly head - all to no avail. The WiFi an Bluetooth do share the same Broadcom chip... maybe there's enough of us experiencing the problem that we can collaboratively order a dozen of these things (they only seem to sell in bulk).

Had the same issue, ATT had to replace the phone.

Any more news on this issue?
Same thing happened to my Atrix last week (Bell, 2.3.6, locked bootloader, unrooted).

Same here
Same problem on my original Atrix, which was replaced under warranty by AT&T six months ago. Recently my replacement Atrix has been having the same problem. Wifi won't enable and frequent reboots.
Although the phone should still be under the 1-year warranty, AT&T refuses to honor it because the screen is cracked (so much for Gorilla glass).
After getting two phones with the same problem, and hearing about countless others having the same problem, and getting screwed out of the warranty, this is definitely my last Motorola phone.

EDIT:
The "fix" that was originally posted here doesn't actually work. I'm almost certain that this is a hardware problem. As of now there is no software fix, if one even exists.
Check this thread for more info:
https://forums.motorola.com/posts/0c2f1387d6
I recommend that you post to acknowledge you have the same problem.

i tried the script and it tells me "oops... did NOT find wpa_supplicant.conf! any help?
cafe. said:
I found a permanent solution to the problem. It was probably more obvious than I originally thought it would be. This is probably what will fix it if you recently ran some sort of 3G tweak as it probably damaged/corrupted /data/misc/wifi/wpa_supplicant.conf. Before I get started with what what problems my phone was having:
-'Wifi Error' message when enabled
-Random reboots when trying to enable wifi
-Bluetooth worked fine (and if you are having issues with bluetooth it may be due to a similar bluetooth related file having problems)
-Impossible to fix by flashing new roms, wiping/factory reset, and virtually every other possible thing I tried
So, just before giving up, I found something called 3Gturbocharger--which can be downloaded from here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 REMEMBER: IT'S 3GTURBOCHARGER, NOT ANY OF THE OTHER SIMILARLY NAMED FILES.
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
I'm assuming that in your case the bluetooth equivalent of "wpa_supplicant.conf" was corrupted. Possibly /data/misc/bluetooth/dynamic_auto_pairing.conf or /data/misc/bluetooth/incoming_connection.conf. Worth a shot trying the method I described on those files as well. Try it out, you've got nothing to lose.
Click to expand...
Click to collapse

im getting that to

My Atrix wifi stopped working in the past, but started working again. It currently stopped working once more, giving me an Error if I turn it on. The Bluetooth has never had issues and still works, I am a month past warranty but with unlocked BL it doesn't matter anyway. This seems to be a slight issue with these phones unfortunately.
I could live with the phone without wifi, but the constant reboots are unavoidable. I notice that when I originally boot the phone, if I use it and keep the screen on it works, but as soon as I turn the screen off, it reboots. Odd to me.

Ya I have the Bell Atrix myself and I'm still on Froyo because of complaints of GB. (especially battery life) Maybe I'll do ICS, but I'll wait for some reviews since its not that easy to go backwards as say my OG SGS...
Sent from my MB860 using xda premium

Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
Click to expand...
Click to collapse
Anyone try doing this manually? I can't locate the file.

wpa_supplicant file
hi, the file is in etc/wifi and the bluetooth file is in etc/bluetooth/ i renamed the .conf files but this don't solved the problem.

[Q] Problem after 4.3 Update

My daughter has just been given a Nexus 4 phone - out of warranty - but in full working order. Not rooted. On switching on the phone, she recieved and installed the latest 4.3 update just yesterday. But she has experienced a number of problems since then. The phone is not a 'brick' but it has lost some of its functionality: camera not working, processing appears unduly slow for routine operation, apps such as Whatsapp not working and clearly something is amiss. She lives abroad and tried to resolve this direct, over the phone, with 'google support' but failed including hard resets etc. Assuming the hardware is fine, is it possible to 'flash' to an earlier version of android (4.2?) and if so, would someone kindly provide an idiots guide to doing this?
I did look for 'other solutions' to this problem (as many others, according to differing sites, appear to have experienced similar problems) but I couldn't find anything straightforward on here.
Grateful for any guidance or support.

Have you tried a factory reset?
Swyped from my Nexus 4 using Tapatalk 4

Lord Yurij said:
Have you tried a factory reset?
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Will check.

Sandy379 said:
My daughter has just been given a Nexus 4 phone - out of warranty - but in full working order. Not rooted. On switching on the phone, she recieved and installed the latest 4.3 update just yesterday. But she has experienced a number of problems since then. The phone is not a 'brick' but it has lost some of its functionality: camera not working, processing appears unduly slow for routine operation, apps such as Whatsapp not working and clearly something is amiss. She lives abroad and tried to resolve this direct, over the phone, with 'google support' but failed including hard resets etc. Assuming the hardware is fine, is it possible to 'flash' to an earlier version of android (4.2?) and if so, would someone kindly provide an idiots guide to doing this?
I did look for 'other solutions' to this problem (as many others, according to differing sites, appear to have experienced similar problems) but I couldn't find anything straightforward on here.
Grateful for any guidance or support.
Click to expand...
Click to collapse
Root.. is needed to flash... and yes its possible... like you said.. its not totally straightforward.. but definately possible.. needs time.. and patience... which I am in short supply nearing the end of day in office.. hope someone gets you the links and guides to do it..

Fix for Nexus 7 2013 (flo) Touchscreen Glitches

For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.

Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.

Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.

yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013

Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia

pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.

Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.

can anyone provide a flashable patch to try? Thanks

This problem is starting to annoy me really badly D:

I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.

This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5

Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133

Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.

[Q] Sensors dead?

I've been running on 5.0 for about a week (stock, rooted). I rather suddenly had the tablet fail to auto-rotate, but rebooting sorted it out at the time. Now it completely refuses to rotate. Not only that, but every app I've tried that reports sensor data doesn't even acknowledge the existence of any input other than the touchscreen and the microphone. I've tried reflashing 5.0 to no avail, and I'm in the process of going back to 4.4 to see if that does anything but I'm not feeling hopeful about it.
Does anyone have any ideas of what else I could try? I'm pretty sure it's well out of warranty (rooting aside), so I'm not sure how feasible it would be to get support on it from Asus. I'm considering popping it apart and seeing if anything obvious is wrong but I'm not sure what I'd be looking for.

Klades said:
I've been running on 5.0 for about a week (stock, rooted). I rather suddenly had the tablet fail to auto-rotate, but rebooting sorted it out at the time. Now it completely refuses to rotate. Not only that, but every app I've tried that reports sensor data doesn't even acknowledge the existence of any input other than the touchscreen and the microphone. I've tried reflashing 5.0 to no avail, and I'm in the process of going back to 4.4 to see if that does anything but I'm not feeling hopeful about it.
Does anyone have any ideas of what else I could try? I'm pretty sure it's well out of warranty (rooting aside), so I'm not sure how feasible it would be to get support on it from Asus. I'm considering popping it apart and seeing if anything obvious is wrong but I'm not sure what I'd be looking for.
Click to expand...
Click to collapse
I had same problem with my N7 2013. First: I opened the back and secured a lousy cable, closed, worked almost 1 full day till everything stops. I also used my book case with magnets. Then: I reopened, secured the other side too of the lousy cable and closed. No case till this, 5 days are passed and no error. So, due to my flaw in the modus operandi, now I don't know if it was for the cables of for the case with magets. I hope the second, I won't use that case either anymore :laugh:
Hope this can help (even if I have the 2013 version)

I have exactly the same issue. My Nexus 7 2013 is on 5.0.1 and rooted. I nnoticed the issue yesterday. First alerted by screen rotation not working, I used CPU Z to see if the compass was detected and I found the sensors page completely blank.
Any help would be greatly appreciated.