Fixes wifi connection issue when 802.11w protected management frames is enabled in your access point. Replaces wpa_supplicant with new one from LineageOS and sets pmf=0 in /system/etc/wifi/wpa_supplicant.conf
Still a bit slow, after hitting connect it appears to fail, but connects after a minute or so. At least it works now.
You may need to set pmf=0 in /data/misc/wifi/wpa_supplicant.conf too, I'm not sure if it will automatically overwrite, but the change wouldn't stick until I modified the one in /system.
I'll try this one. Thank you!
Related
Hi Guys,
If you experience Wifi connection problem, you may want to try tuning the WLAN driver. In fact, I found that the default settings are inappropriate for a consistent and stable connection. So, I'd like to share how I got through the problem.
1. Root your phone. Download and install Root Explorer or ES File Explorer (Explorer).
2. Make sure you manage how to use the Explorer as a tool to modify files in the /system folder.
3. Using the Explorer, browse to /system/etc/firmware/wlan/qcom_cfg.ini
4. Make a backup if you wish. Most of the parameters inside need not be changed except the followings:
a. gTxPowerCap=30 (change to 60 increases the TX power)
b. gDot11Mode=auto (change to n to always connect as n, but if you sometimes want to use g, don't change this)
c. You may wish to play around with the other parameters as well
5. Now save the file.
6. Browse to /system/etc/firmware/wlan/hostapd_default.conf
7. Again make a backup copy.
8. This is a long file. So please hang on. Amendment of the following is recommended:
a. max_num_sta=2007 (change to 10 to only display 10 wireless AP)
b. channel=6 (change to 0 can solve most wifi connection problems)
c. You may wish to play around with the SSID options such as disabling SSID broadcast.
9. Cheers !
The changes to hostapd_default.conf will only affect using your phone as a wifi access point. But the first set of changes are worth looking at.
Thanks for this BookBu,
I've constantly been having dropouts on my wifi irrespective of ROM. I've used void, B160, even stock and still I constantly have dropouts. I only made the TX power change but I'll see how it goes.
It seems to be a problem that nly affects a few users, so if it continues to happen I will change my phone as I only just bought it as it may be a hardware problem. My router at home isn't the best either so hard to contribute to whats actually causing it.
Would doing this cause more power requirements for the battery? Just out of sheer logic. Would it be significant? I don't have wifi on all the time only when downloading so it's not that big a deal for me but I'm just curious
Yes,I think boosting up the transmission cap should make the hardware draw more power from the battery. However, the hardware will enter into idle state in which no power is wasted when not in use. From my experience, the idle time is about 50 to 60 % Just imagine that you must use a more powerful flash light if you wish to see far things in the dark.
Sent from my IDEOS X5
I have a network with a hidden SSID. today, I changed my google account password due to google telling me mt accounts was accessed from malaysia (....), so when I got home and turned on my tablet, it prompted me to re-sign in. except I forgot the new password. so I hit home and pulled up the browser, at which point it disconnects from wifi. and I couldnt get it to reconnect or see my network. I reboot, nothing. So I changed the password on my macbook, which works fine on the same wifi.
then i tried to connect on the tablet again, nothing. so i deleted the network from the tablet, then re entered it. nothing. so i changed the configuration on the router so it wasnt hidden. it does now appear in my tablet's list of visible networks, starts to connect, says obtaining ip address, then disconnects and tries again.
any ideas? fyi my android phone is working fine.
It's a well known issue, though with all the 3.1 update threads lately, it's been pushed off the front page.
http://forum.xda-developers.com/showthread.php?t=1138905
http://forum.xda-developers.com/showthread.php?t=1167387
http://forum.xda-developers.com/showthread.php?t=1169458
http://forum.xda-developers.com/showthread.php?t=1158039
thanks for that, one of the people in those topics said using the reset button worked so i tried that and it did. got the newest OTA too, hopefully that has a fix for this. if not, i also downloaded superuser, TB and Android terminal emulator, so i'll have those as options for a fix if it happens again.
of course, i'll need to be rooted to use them, so is there any way to root on 3.1 yet? gingerbreak is broken, I know that cause I just tried.
Yes, there's a thread on it in the dev section. It was rooted about 20 minutes after it was released.
Well it looks like the OTA didn't fix it because it just happened again. So I tried the reset and that worked this time too. Come on Acer, you can do better.
The OTA patch didn't work fully for me either...
Every once in a while when changing WiFi's (work to home, home to a friend's house, etc...) it'll not find the Access point name and disable that connection. I have to turn off Wifi and then turn it back on before anything will connect or search...
I still have the path where to delete the .lease file so I continue to check for that.
The .lease file has not been there the last two times, but connecting is still an issue.
Fortunately, it's a simple thing to turn off WiFi and then Turn it on again and then Ask the connection to do it's thing...
..but yeah. Acer? A little help over here...
I'm stuck.
I soft reset my A500 four times in a row with no luck, so I went ahead and rooted the thing to delete the lease file as mentioned in other posts, and as it turns out I didn't even have a dhcpd_wlan0.lease file in /data/misc/dhcp -- I had no files in that directory at all.
I don't want to deal with a factory reset, but if I do, I'm still sunk because I have no lease file to delete to fix my problem in the future, since that seems to be not my problem.
Running 4.010.13_com_gen2, updated yesterday I think to this version, went to work, everything was great, got home, nothing is great.
Any other ideas besides a factory reset?
Static IP's FIX this issue.
Sent from my A500 using Tapatalk
Returning to work has fixed my issue temporarily anyway -- I am connected once again on my work network. I will shut down before I leave for home and see if that allows me to connect to my home network again.
After which, static IP is the way for me, I s'pose.
Thanks!
setting the static IP worked immediately for me as well. I found a great guide for any users who are unfamiliar with how to do this.
Step 1 is to know your lan network topography: ipconfig /all at a command prompt will give you your computer's IP address, as well as your host/gateway (usually a router). It also helps to know how to log into your router (usually the first octet in your IP range, eg. 192.168.1.1 is a router running DHCP, while your computer might be 192.168.1.4). Examine the IP range that the DHCP is assigning..often it is limited to a certain number of clients already, or you can do so yourself (I have mine set to hand out 10 IP's only via DHCP, while my actual LAN is manually assigned throughout).
Step 2 on the Acer is to open wifi connection properties and select your own network. The Properties Dialog will pop up, and right below Signal Strength, is says 'Network Setup, with a little marker for a dropdown. Select the marker/dropdown and click 'Manual'. Scroll down in the dialog, to IP settings, click the dropdown marker and select 'Static'. Plug in an IP address, subnet and Gateway (router) IP addresses..I left network prefix alone at 24. I also use custom DNS addys (OpenDNS) but you can also simply point them to your Gatewat/Router IP with no problems. Scroll back up and enter your Network Key for the level of encryption you're using on your WLAN, and you should connect right away, since we are no longer relying on the router's DHCP server (and the DHCP/IP assignment bug on the Acer), and once this is done, it will stay that way indefinitely.
Click to expand...
Click to collapse
I had issues pulling an IP connecting mine to my old router, so excluded part of the routers subnet from its dhcp scope and entered a static IP into the A500 for that connection and it has been working fine since.
So my work has banned all cellphones and wifi capable devices. I work graveyards and absolutely DEPEND on my Nook for reading all night long. Is there a way with Root Explorer or ADB that I can totally kill Wifi?
I want to be able to hit the wifi toggle and show a supervisor that it won't work.
Hopefully someone can help...
You can do it quite easily with Tasker. Disclaimer: the way I did it, each time you hit the toggle, it will show the hollow (not connected) wifi bars for half a second, then nothing. This is on cm7 by the way.
There is a 2 week trial of Tasker if you want to try it. There may well be a better way to do it in Tasker too.
Context: State > Net > Wifi Connected (any time wifi tries to connect it will do the following)
Task: Net > Wifi > Set to Off (it sets wifi off)
Exit Task: Net > Wifi > Set to Off (this sets it off so it doesn't continuously attempt to reconnect)
Only a few clicks in Tasker to re-enable wifi if you need it too.
Thanks for the reply, I figured out a way with Root Explorer while I was at work last night. I navigated to /system/lib/modules and renamed the only file there (something like wlan.ko but longer) with an added .kill suffix to the end. No need to reboot or anything. Hitting the wifi toggle now does nothing, going into wireless settings and pressing the wifi on toggle shows ERROR where it would normally say TURNING ON or SCANNING or whatever. Easy to reverse when needed.
Thanks again!
I don't post much (obviously, and keeping me from putting this in Dev forum or posting external links :| ) but I do work a lot on the sides and figured out how to get a Verizon non-smartphone to act as a 3g dongle for the Acer A500. This is a copy of my tutorial originally posted on TegraOwners.
First off my setup;
Acer Iconia A500; Running Thor v14.2 ROM (Possible to work on other ROMs/kernels that support 3g dongles)
Build.prop mod installed from -snipped because of limit, will edit when able-
Phone; LG EnV2 Verizon prepaid.
Solution should work for any tether enabled verizon phone, POSSIBLY Verizon Dongles, and other brands of phones besides LG.
This guide assumes you either have, or know how to flash Thor's rom, and other flashable zips. I will not provide ADB instructions, but if someone would like to send me instructables how; I will add them into this post.
From a 'fresh' or unmodified version of Thor's ROM (I used v14.2, follow the build.prop install instructions in the link above. (Link removed because of limitations on posting)
Then using root explorer (or equivalent root browser) remount /system rewritable and open the build.prop file in a text editor.
Comment out ro.carrier=wifi-only and uncomment the rest of the block. It should match the following when done;
#ro.carrier=wifi-only
picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true
Save the file and check permissions; they should still be rw-r--r-- and reboot the tablet.
This enables the 3g menus, and using the previous build.prop, lets your A500 read as an A500 instead of an EPAD.
Note: You DO NOT need to set an APN, Verizon, being a CDMA network, does not use APNs. The 'login' information is in the phone itself. It just needs the commands to initiate a data connection.
Now is where it got tricky to figure out; If you open a terminal emulator as root (type su at the prompt) and type ppp-start.sh you will get a couple of lines with this error;
pppd: In file /system/etc/ppp/peers/3g: unrecognized option '/dev/ttyUSB2'
or similar.
In the terminal prompt, type dmesg | grep tty it will return several lines, I noticed I had a device on ttyUSB0 not ttyUSB2.
On study, some modems make several ports for control, monitoring, etc. mostly data connections are on ttyUSB2, which is my guess why it was default.
I figured out by editing the ppp config file that ttyUSB0 wouldn't error, but wouldn't start either. I looked back at the grep and noticed something else that matched and I had seen before in my studies; ttyAMC0
So using the same method as editing build.prop, edit /system/etc/ppp/peers/3g it should read as follows;
ttyACM0
921600
crtscts
defaultroute
modem
noauth
noipdefault
persist
updetach
usepeerdns
connect 'chat "" AT OK ATD#777 CONNECT'
Note the ttyUSB2 being changed to ttyACM0, apparently the data serial for the phone, and atd number being changed to #777, Verizon's 3g number. (Speculation that you could increase the 921600 for higher USB bus speed, but I've not tested this).
Save the file and confirm the permissions are; r-xr-xr-x
Open terminal emulator with root permissions and again try ppp-start.sh
This time after it says pppd, after about 5 or so seconds, it should list your IP and other information confirming the connection. You should see TX and RX packet info on the phone screen. If so, congrats you are now connected via 3g with the phone.
To turn off the connection, use the command ppp-stop.sh I suggest making a couple script manager widgets to 'shortcut' these.
Note; If the screen turns off, the phone will disconnect and you will have to unplug the phone, restart the ril daemon, plug the phone back in, and run ppp-start.sh again.
You can install the ril-daemon_restarter.apk to easily restart ril, or in terminal emulator; stop ril-daemon then start ril-daemon
(Had to remove link for limitation, google for now, will add in when I can. suspected credit goes to dmatusek76 on XDA.)
Things that I've tested;
Browser works despite saying 'no connection' at the start.
Market can browse apps, but not download them.
GMail seems to receive, but not send emails.
Netflix works.
Edit: OpenVPN works.
Google Maps/Navigation works (downgrade to stock, latest update FCs)
Best part; The Portable Wireless Hotspot option in Settings > Wireless & Networks > Tethering & Portable Hotspot menu works to create a 3g Wi-Fi hotspot.
All connections through the hotspot are NOT BLOCKED; i.e. using my android to connect to the tablet, I was able to browse apps, download them, send emails, etc.
My theory on the reason the tablet won't; Some apps (like Google Voice and AndroIRC), check for an internet connection BEFORE TRYING, and if it isn't 'available' it just gives you a warning and stops without actually TRYING. Other apps just try to access the internet without checking for a connection first (Like Netflix), and they work.
This theory is backed up by the Browser first checking for a connection (hence the 'no connection available' popup), but then loading as it continues to try anyway after the check.
Using the wireless hotspot, the phone sees it as a full connection, so nothing stops during the 'network check'.
I hope this information might be useful in getting other devices, phones, dongles, etc. working with this masterful tablet.
Please let me know if it works and if you use other equipment.
Credits;
Thor for his awesome rom that supports USB 3g in the first place
pimpmaneaton for the build.prop
Hall,
I got a TM530, rooted with Towelroot, no modifications otherwise.
When trying to connect to phone's WiFi Hotspot im getting asked for the password, after entering it there's the message "Connecting..." for a second or so - but I won't get a connection [emoji17]
A few days ago this was no problem - I'm a bit lost here.
My phone's running with Slimkat ROM with two weeks old weekly build, didn't change anything there, too.
Changing Hotspot setup and deleting the connection from WiFi menu on the tablet led to no success either ?
Any hints anyone? I'd appreciate
husky69 said:
Hall,
I got a TM530, rooted with Towelroot, no modifications otherwise.
When trying to connect to phone's WiFi Hotspot im getting asked for the password, after entering it there's the message "Connecting..." for a second or so - but I won't get a connection [emoji17]
A few days ago this was no problem - I'm a bit lost here.
My phone's running with Slimkat ROM with two weeks old weekly build, didn't change anything there, too.
Changing Hotspot setup and deleting the connection from WiFi menu on the tablet led to no success either ?
Any hints anyone? I'd appreciate
Click to expand...
Click to collapse
Pretty common problem tethering from a phone to tablet with the native tether method due to its lack of settings. Download the app WIFItether Router by Fabio Grasso. When you set it up, under "hotspot/tethering settings" make your SSID whatever you desire, use wpa2-psk for encryption type, then set a password, and desired channel (I usually use 11). Then under "device settings" for Interface select wlan1, under method use Method 3-HostApd, under drivers select nl80211, select WiFi -g for wifi mode. Then under "tweaks" check MTU adjust and also check HostApd patch. Now go back and select "enable wifi router". That should solve your issue.