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.
Hello everyone,
I had a lot of problems setting up my Huawei E173 3G USB Dongle with TF101 on newly installed KatKiss-KitKat #023c ROM, so after finally getting it to work, here are some tips that might help the others.
# First of all, dock battery should be over 25% [ whether it makes sense or not...it worked better for me ]
# Unlike default system (4.0.3 if I remember well), this ROM will not auto-detect/mount your USB device
# WIFI shloud be OFF
These are my PPP Widget settings
---------------------------------------------------------------------------
Access Point Name [required] - mine was minternet.bhmobile.ba (check with your carrier/provider)
Check and set PIN [required] - enter your PIN - BHMobile default is "0000"
Use WiFi to show PPP connection status : ON
Disable USC Device sleep : ON
Automatic device detection : ON
Manual port selection : ON [important]
Modem port - enter "ttyUSB0" --- do not use another USB at te same time!
Notify system about network access : ON
Enable logging : ON
---------------------------------------------------------------------------
Turn your Android OFF now (rebooting does not work).
Go to PPP Widget screen. Press green PPP widget icon.
Widget should be waking your device up... Connect button available soon.
Do not get discouraged if you do not connect from the first attempt.
Keep trying - it really works! I will try to upload some screenshots later.
Hope it helps!
By turn your Android off, you mean the device? We are supposed to turn off and turn on instead of using Android 's re boot?
Regards
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.
In the past week my Galaxy S5 (SM-G900V - Android version 5, Kernal 3.4.0) has lost the ability to connect to the internet a few times when wifi is on (under wifi, it appears that it is connected successfully to the wifi but when using the internet I get an error message about DNS not working).
This first time it happened was at at home and I thought that maybe my router just needed to be reset (which didn't fix the issue) but it happened at work today.
Both at home and at work, the only thing that I could do to fix the issue was restarting the phone (resolved the issue at both locations).
I tried all of the following suggestions with no luck:
Turning wifi off and then back on
Making sure that 'Always allow scanning' and 'Smart network switch' were both turned off on my phone
Choosing the wifi network on the phone and 'forgetting' it and then connecting to it fresh
Setting the DNS servers on the wifi network of the phone to use a static IP address and static Google DNS servers
Trying a different browser on the phone
The only thing that has resolved the issue once it starts is to restart the phone.
Any other suggestions?
@superdragonpt Due to the fact that I'm not allowed to post to the original ROM thread, I'm providing my feedback via this channel.
As already reported under the thread "Jiayu S3 Adv - AOSP N stable 8 - automatic reboots, wifi, camera and sound profiles" (https://forum.xda-developers.com/jiayu-s3/help/jiayu-s3-adv-aosp-n-stable-8-automatic-t3563631) the phone sometimes reboots automatically and I had to enter my SIM pin again.
The problem still persist with MadOS stable 10, but I think I've now catched a situation in which the reboots are happening more often. Although the wifi connectivity has been improved with the latest release I found out that the phone sometimes freezes if an app is running in foreground and a wifi connection is automatically established or a wifi connection is lost in the background. I hope this will help you in one or the other way.
Concerning wifi connectivity I've also realized that a connection to a known network is sometimes not established automatically, although I can see available networks in the "Wifi Analyzer" app. I'm also able to connect to one of these networks by forcing a connect.
@superdragonpt I think I can provide some additional information about automatic reboots. Last week I've been at a location where the primary wifi network was WPA2 secured. I realized that automatic reboots only happened two times in eight days.
Back in my usual environment, where an EAP secured wifi network with Radius authentication has been installed, automatic reboots happen at least once per day. I come to the conclusion that the used wifi security protocol impacts how often an automatic reboot happens.
@superdragonpt I wrote:
Back in my usual environment, where an EAP secured wifi network with Radius authentication has been installed, automatic reboots happen at least once per day. I come to the conclusion that the used wifi security protocol impacts how often an automatic reboot happens.
Click to expand...
Click to collapse
Last week it was time to investigate further on the annoying reboots and the wifi network connection problems. I realized that many people reported wifi problems after upgrading from Marshmallow to Nougat and when trying to connect to EAP secured wifi networks in e.g. company environment. Some people wrote that setting the following parameters have solved their wifi problems:
EAP method: PEAP
Phase 2 authentication: MSCHAPV2
CA certificate: Do not validate
I've also used that settings in the past but without any positive impact on the result.
Therefore I decided to add my CA root certificate to the wifi setup, using "Advanced -> Install certificate". It was a big surprise as I saw that wifi connections were established much faster and that no automatic reboots happened during the last 4-5 days .
My conclusion is, that although the CA certificate parameter has been set to "Do not validate", the certificate check is not fully disabled which causes the mentioned wifi problems and also automatic reboots, because of wifi reconnection attempts which might have happened in the background.