Ever since I flashed CL3ANTH3ORY 1.1 (now on 1.2) I have not been able to connect to wifi at home. I was running AO5PTH3ORY before and it connected fine. Before that I was running BAMF Remix 2.1 and it connected fine.
It scans, it finds, it connects, it tries to obtain an IP Address, then it disconnects, scans, finds, connects, tries to obtain an IP Address, then disconnects, repeat, repeat, repeat, etc.
Any help would be greatly appreciated... Thanks in advance!
Its a known issue that is being worked on. Look for a fix soon.
sent from my thunderbolt running CL3ANTH3ROY, using the XDA premium app
Good lookin out... that means I May need to go back to a different ROM for now so that I can use some of the apps I have that communicate to my laptop via WiFi.
I appreciate the info!
Sent from my Thunderbolt using XDA App using CL3ANTH3ORY 1.2x.
The fix is in the candystor3 in the app drawer
sent from my thunderbolt running CL3ANTH3ROY, using the XDA premium app
+1 For the candystore fix.. worked for me
I'm not able to find anything in there to address wifi connection... I would imagine it'd be under system fixes/tweaks, but all I see is Solid BG Notification, Remove location and add alarm, and Tether Fix. Under Mods I do not see anything in regards to fixing wifi.
I apologize if I'm missing something easy... I appreciate the advice and time helping me address this problem.
djsnake210 said:
I'm not able to find anything in there to address wifi connection... I would imagine it'd be under system fixes/tweaks, but all I see is Solid BG Notification, Remove location and add alarm, and Tether Fix. Under Mods I do not see anything in regards to fixing wifi.
I apologize if I'm missing something easy... I appreciate the advice and time helping me address this problem.
Click to expand...
Click to collapse
Ahh sorry, I piggy backed off of the previous commenter with the wifi tether track
Wifi is working for me.. In fact, I have better range than I did stock (might be me imagining it though). Is it open or encrypted? I'd try deleting the profile and re-adding it if you haven't already
Yeah I tried that... I was hoping moving from 1.1 to 1.2 would do the trick, but it didn't help.
I have it protected with WPS. I tried using all 3 methods to connect (forgetting the network between each test)... the password, the button, and the pin. What's strange is even when it says "connected obtaining ip address" it doesn't show as an attached device on my router. Maybe that's just because it hasn't been assigned an ip address yet.
Question... Is this something that is usually controlled by the ROM or the kernel?
I'm sorry... It's WPA protection... but tried connecting through WPS as well as manually.
It's Kernal based...
And the fix in the candy store worked perfectly.
I was cruising along on his AOSP build before this morning, now that tethering is working again...back to things making "sense"...
I think you may have misread my issue... It's not an issue with WiFi tethering... It's an issue with the phone connecting to my home WiFi network.
I hope this helps. Thanks!
Sent from my Thunderbolt running CL3ANTH3ORY v1.2 using xda app.
djsnake210 said:
I think you may have misread my issue... It's not an issue with WiFi tethering... It's an issue with the phone connecting to my home WiFi network.
I hope this helps. Thanks!
Sent from my Thunderbolt running CL3ANTH3ORY v1.2 using xda app.
Click to expand...
Click to collapse
No reports of a WiFi issue at all... Have you flashed a different kernel? I would wipe Cache/Dalvik and Format /system then reflash.
Sent from my SHIFTAO5P using XDA App
DroidTh3ory said:
No reports of a WiFi issue at all... Have you flashed a different kernel? I would wipe Cache/Dalvik and Format /system then reflash.
Sent from my SHIFTAO5P using XDA App
Click to expand...
Click to collapse
I did flash dream kernel 2.3.6. I just read in the main thread for this ROM that someone else had the same issue (post #591). I guess I should have given the HTC Kernel a chance, ay?
Do you have just the kernel available for downloading and flashing? I checked the official list and it isn't posted there. If not I'll just wipe and flash... I know this should fix my other issue as well with the advanced power menu (thanks again for the input), but since I have a workaround for that now (Quick Boot app) I was hoping to alleviate another wipe/flash until 1.3 of clean was available.
Thanks again for your help!
Another workaround I would suggest trying is manually setting your connection instead or relying on dhcp. You probably have a network id of 192.168.1.1, broadcast id of 255.255.255.0 and can attempt to try an ip in the rage of 192.168.1.1 to 192.168.1.149
For more detailed stats, run ipconfig /a for windows or ifconfig -a if you are on linux/unix/osx
yareally said:
Another workaround I would suggest trying is manually setting your connection instead or relying on dhcp. You probably have a network id of 192.168.1.1, broadcast id of 255.255.255.0 and can attempt to try an ip in the rage of 192.168.1.1 to 192.168.1.149
For more detailed stats, run ipconfig /a for windows or ifconfig -a if you are on linux/unix/osx
Click to expand...
Click to collapse
Good lookin out! As soon as I set it to a Static IP I connected right up!
I would still be interested in reflashing the HTC kernel mod, but at least this is working.
Thank you sir!
djsnake210 said:
Good lookin out! As soon as I set it to a Static IP I connected right up!
I would still be interested in reflashing the HTC kernel mod, but at least this is working.
Thank you sir!
Click to expand...
Click to collapse
no problem
glad it worked out.
it sounds like the kernel has an issue with dhcp.
Related
I have a rooted phone running aospcm7 gingerbread. Everything was working fine til about 2 weeks in. The wifi just stopped obtaining the ip address and no matter what access point i try it just simply cannot connect. From what i read a factory reset seems to work? i'd really rather avoid that...
i have the same problem too but im using miks cm7 6.5.5. half of the networks i try to connect to just stay stuck at obtaining ip address. anyone know why?
sweetnsour said:
i have the same problem too but im using miks cm7 6.5.5. half of the networks i try to connect to just stay stuck at obtaining ip address. anyone know why?
Click to expand...
Click to collapse
Have you tried connecting to the same Wifi networks through other devices? like a laptop? It may not be a problem with the phone.
gkarthik16 said:
Have you tried connecting to the same Wifi networks through other devices? like a laptop? It may not be a problem with the phone.
Click to expand...
Click to collapse
Yes i have in fact right now my computer is connected to my school network but my phone cannot connect. So it's definitely the phone, thank you though!
Go to WiFi settings - press the menu key - advanced - try a different regulatory domain (13 or 14). ;-)
Sent from my LG-P500 using XDA Premium App
sholimar said:
Go to WiFi settings - press the menu key - advanced - try a different regulatory domain (13 or 14). ;-)
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Yes. Also try setting the Wifi sleep policy to 'Never'. Also if possible try to change the authentication type of your network. I always face this issue with WEP authentication.
Sent from my LG-P500 using XDA App
Happens to me sometimes, be sure the password is correct.
I've tried all of these things and still i cannot optain the ip address, what should i do now? are there anythings i can do in recovery such as deleting caches? and stuff?
What Happend?
wilfmeister said:
I have a rooted phone running aospcm7 gingerbread. Everything was working fine til about 2 weeks in. The wifi just stopped obtaining the ip address and no matter what access point i try it just simply cannot connect. From what i read a factory reset seems to work? i'd really rather avoid that...
Click to expand...
Click to collapse
Any news here?, what happend to Wilfmeister???
wilfmeister said:
I've tried all of these things and still i cannot optain the ip address, what should i do now? are there anythings i can do in recovery such as deleting caches? and stuff?
Click to expand...
Click to collapse
Wipe dalvik and cache partition, reboot and try
Sent from my LG-P500
Hi this a excelent ROM!! i love it! but the Wifi disconnects every 5 minutes or less...and reconnect, How i can fix this?
same here,
using slade's new ROM, "GinTonic.SE | v1.3" ....
any ideas ?
I don't know why, but using ondemand or performance profile I don't have that issue. Test it and tell me
kem06 said:
I don't know why, but using ondemand or performance profile I don't have that issue. Test it and tell me
Click to expand...
Click to collapse
Thanks for your reply,
Just tried changing the profile ,,, rebooted ,,, but still the same problem ,,,
it seems that i'm missing something !!!
aymanxp said:
Thanks for your reply,
Just tried changing the profile ,,, rebooted ,,, but still the same problem ,,,
it seems that i'm missing something !!!
Click to expand...
Click to collapse
Mmm.. Do you have bluetooth or EDGE/3G activated ? It might make some problems.
Another thing, which policy suspension do you have for WiFi ?
after trying everything, i used a static IP to connect and finally it seems to work.
thanks for your interest.
i haven't bluetooth or EDGE/3G active, the policy suspension of is never! i format sd card and reinstall rom but the problem continues....
aymanxp said:
same here,
using slade's new ROM, "GinTonic.SE | v1.3" ....
any ideas ?
Click to expand...
Click to collapse
Same for me
The same problem in almost all these ROMs.
I'm using the MiniCMPro V7 and I'm trying to debug it by reading the logcat and editing some config files, will post/edit any advance later.
It worked by using aymanxp's method as a workaround.
By reading the logcat I found that something is forcing the dhcp server on the phone to lease a new IP after some time [receives a SIGTERM] although it obtained an infinite lease.
In other topic, why android does not have a separated config (Static/dynamic, IP, DNS, etc...) for each wireless connection?
B.R.
Update:
Well, my actual conclusion is that the WifiStateTracker Daemon is forcing DHCP to request ip renewal every 5 minutes or so, and if there are a valid or infinite lease in place, dhcp returns an error after waiting, so WifiStateTracker gets the wifi down and restarts DHCP, so lame.
Tried to find any config file but found none, only dhcpcd and wpa_supplicant, but nothing about the daemon.
So to have the wifi working properly, from now, the right way is to don't use dhcp?
Try to change wifi sleep policy to "Never" instead of "when screen turns off"
XxLordxX said:
Try to change wifi sleep policy to "Never" instead of "when screen turns off"
Click to expand...
Click to collapse
Nope, won't work either.
@Pierrot12:
As a temporal workaround, yes
We can use static IP, but that would work just if using only one Wi-Fi network (as in the house OR the work), but for people like me, using more than one network, it's very annoying to edit the parameters every time the AP changes.
I'm tempted to write an app to replace the android's very simple AP managing system
I flash to Sonybread 7 SP3 and the problem continues...
I'm using v6 and I have not had any problems with WiFi. In fact, I think it's the most stable ROM. I have downloaded files flawlessly, which means that WiFi is not disconnecting right? Anyway, I'll put it to test..
RozenTensai said:
I'm tempted to write an app to replace the android's very simple AP managing system
Click to expand...
Click to collapse
Great! good luck
Actually found the problem, but don't know if it would work for anyone.
After some research and hits and misses, found that the problem with the DHCP client running in the MiniCM7-based ROMs does have a incompatibility with "Reserved IP" or "Infinite IP Lease" for a certain MAC, in other words you should use:
A) IP Assigned by the router (not reserved), or
B) Static IP configured on the device.
If that's not your case, then just wait for a fix from the devs or my app (still brainstorming ) or any workaround posted in this thread
@Pierrot12: Thank You!
@eysonfm Yeah, I was on that ROM and it's really stable. But I want MiniCM7 Pro
I have also problems wifi DHCP issues with MiniCM7 Pro V7+
I don't understand, because I got it from one moment to the other
Only
B) Static IP configured on the device.
is working for me
in terminal with netcfg I could see that I got an ip adress over dhcp. In Wifi manager stands getting IP address
I won't do an factory reset, maybe I can help somebody to find the bug by testing somethings
i'm having these issues with minicm7 pro v19 as well...
RozenTensai said:
Actually found the problem, but don't know if it would work for anyone.
After some research and hits and misses, found that the problem with the DHCP client running in the MiniCM7-based ROMs does have a incompatibility with "Reserved IP" or "Infinite IP Lease" for a certain MAC, in other words you should use:
A) IP Assigned by the router (not reserved), or
B) Static IP configured on the device.
If that's not your case, then just wait for a fix from the devs or my app (still brainstorming ) or any workaround posted in this thread
@Pierrot12: Thank You!
@eysonfm Yeah, I was on that ROM and it's really stable. But I want MiniCM7 Pro
Click to expand...
Click to collapse
Also, i discovered that i had the "backup" and "restore..." options enabled under Settings -> privacy enabled. They were causing my phone to receive bad configurations saved in my google account in googles's servers...
so i disabled these otions, re-flashed minicm7pro, set up my router to "not reserve" the address for the minipro's MAC address and everything is working as it should since then!
I have an issue when running ATT based ROMs like Aura and Alien.
When I activate the Hotspot on my Phone, the PC connects and gets an IP, but no Internet. While running ORFR based ROMs, everything works!
Any suggestions to fix my issue? Keeping in mind that when I flash ATT based ROMs, I flash ATT radio too.
Tried on Kholks Kernel and faux123 Kernel, the Phone is purchased from OrangeUK.
Hi
Did you ever find a resolution to this issue?
I'm currently experiencing this issue with Alien-4 and I'm pretty certain I was using it without any issues on stock 4.5.91 ROM.
I searched through some threads and thought it might have been an APN issue but I've tried the bundled APNs with the Alien-4 ROM as well as deleting them and adding new ones with the settings from ausdroid. I've tried it both on Telstra and Optus and cannot seem to work it out.
Assuming you are using a rom that allows it, try using this to help rule whether it's an APN or an app problem:
http://code.google.com/p/android-wifi-tether/
I have used this program to great success in the past.
Sent from my MB860 using xda premium
xfinrodx said:
Assuming you are using a rom that allows it, try using this to help rule whether it's an APN or an app problem:
http://code.google.com/p/android-wifi-tether/
I have used this program to great success in the past.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Hi xfinrodx
That little app works although due to the stock kernel included with Alien-4 I stuck with a completely open connection. I figure it's the stock motorola mobile hotspot app that's the issue, did you have any suggestions on how to resolve this issue? Would reloading the hotspot app fix this?
Thanks in advance
I'm pretty well sure I used encryption with this app and Alien... Just take another quick peek at the settings page in the app to be sure if you don't mind. :-/ It always gives the "access control" warning to me, but hasn't inhibited my encryption. Near as I can tell that relates more to ipconfig type stuff.
As for using the stock application... I would probably first go into CWM, "fix permissions," clear cache and dalvik then try again. If that fails, I would attempt to remove the stock tether app through titanium backup and reinstall from some .apk if I could find one. Failing these, I would reflash.
Hopefully you can work it out and post your method for others to find!
Sent from my MB860 using xda premium
Thanks again for your reply xfinrodx
I'm currently inbetween jobs so I have a bit more time to look into it. What I think the issue for me is, is that the wireless hotspot assigns itself as the dns server to the device connecting to it. Now I just need to somehow specify a dns to assign or force the client to use a specific dns
Thanks
fmflex said:
Thanks again for your reply xfinrodx
I'm currently inbetween jobs so I have a bit more time to look into it. What I think the issue for me is, is that the wireless hotspot assigns itself as the dns server to the device connecting to it. Now I just need to somehow specify a dns to assign or force the client to use a specific dns
Thanks
Click to expand...
Click to collapse
What OS are you trying to tether? Self-specifying dns addresses is commonly done and generally very easy. I personally recommend google's dns. 8.8.8.8 and 8.8.4.4 if memory serves me... Anyway, I think google has a write up for you on their dns page that is better than I could throw together in a reasonable amount of time!
Do try this as a troubleshooting step, but don't be too surprised when it doesn't help. I have a sneaking suspicion the problem lies elsewhere, though I know not exactly where. Hopefully this is it!
xfinrodx said:
What OS are you trying to tether? Self-specifying dns addresses is commonly done and generally very easy. I personally recommend google's dns. 8.8.8.8 and 8.8.4.4 if memory serves me... Anyway, I think google has a write up for you on their dns page that is better than I could throw together in a reasonable amount of time!
Do try this as a troubleshooting step, but don't be too surprised when it doesn't help. I have a sneaking suspicion the problem lies elsewhere, though I know not exactly where. Hopefully this is it!
Click to expand...
Click to collapse
I'm trying to tether my Asus TF101 running 3.2.1 as well as a mate's ipad2. Neither worked. I've looked high and low on my TF101 and haven't been able to locate the DNS settings.
If you go to wifi settings-[menu button]-advanced there should be something in there... You might need to manually specify everything from there, but it's a shot. I'm away from my tablet at the moment or I'd look.
Sent from my MB860 using xda premium
Hi All,
I have a very odd issue.
My phone can connect to my wifi router no issues. When it first connects it will browse and receive services from the internet no issues. However, after maybe 1-2 minutes all internet service requests die, the phone is still connected to the router as the wifi signal is there and strong.
I have tried changing the security on the router, updating the kernel / rom and i still encounter the same issue. I'm convinced this is a small bug.
If anyone has come across this please let me know how you dealt with it.
Thanks in advance
are you on stock ROM/kernel? Does it happen after you turn your screen off and back on?
Had same problem, router issue something about firewall, had to manually enter phone's Mac address into router
Sent from my SAMSUNG-SGH-I997 using xda premium
Rockin_Zombie said:
are you on stock ROM/kernel? Does it happen after you turn your screen off and back on?
Click to expand...
Click to collapse
On a stock kernel using warrior rom. But i have tried different combos but with no success.
Have now lowered security level on router after reading some posts, now just doing tests.
coachcory said:
Had same problem, router issue something about firewall, had to manually enter phone's Mac address into router
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I've reserved the address on the router that includes the MAC
Seems as though security setting above WEP e.g. WPA-PSK/WPA2-PSK/WPA-PSK [TKIP] + WPA2-PSK [AES] causes the issue.
Anybody know of a fix for this?
the_last_don said:
Seems as though security setting above WEP e.g. WPA-PSK/WPA2-PSK/WPA-PSK [TKIP] + WPA2-PSK [AES] causes the issue.
Anybody know of a fix for this?
Click to expand...
Click to collapse
Hi, anyone have any pointers to the above issue?
Varsinki ku mennäänki hiihtolomal himoksel ehkä
Sent from my GT-I9100 using XDA App
For some reason I am unable to connect to my home WiFi network. It acts as if it is about to connect by saying authenticating and then stops and does not connect act all. Then after if I try to connect to the network again it says "Failed to connect to network". I have noticed this has happened to me before when I flashed the Viper ROM so I just went back to stock. I do not know why this issue is occurring.
Try fixing permissions in recovery. This appeared to work for me.
Something else to check is the setting called "Keep Wi-Fi on during sleep": System Settings --> WiFi --> Menu --> Advanced. Try a different setting and see whether that works.
vbanagas said:
For some reason I am unable to connect to my home WiFi network. It acts as if it is about to connect by saying authenticating and then stops and does not connect act all. Then after if I try to connect to the network again it says "Failed to connect to network". I have noticed this has happened to me before when I flashed the Viper ROM so I just went back to stock. I do not know why this issue is occurring.
Click to expand...
Click to collapse
I too have been having Wifi connection issues. I was on Viper with no issues. I was trying Carbon and thats when it started. I tried crpalmers kernel with no luck. I was trying to follow his instructions to check for modules but it seems to be over my head. I dont have much experance with adb. The last time I flashed the kernel i wiped cache and dalvik before and after and fixed permissions.
Thanks
Gr8Jeepin said:
I too have been having Wifi connection issues. I was on Viper with no issues. I was trying Carbon and thats when it started. I tried crpalmers kernel with no luck. I was trying to follow his instructions to check for modules but it seems to be over my head. I dont have much experance with adb. The last time I flashed the kernel i wiped cache and dalvik before and after and fixed permissions.
Thanks
Click to expand...
Click to collapse
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yup, I'm a moonshiner. I just read that CM 10 ROMs aren't liking WEP. And to change it to WPA2. Going to try that here in a few minutes.
Sent from my HTC DROID DNA using xda app-developers app
That was it changing the router security to wpa2. Hooked right up.
I get the same problem on AOSP roms. Doesn't happen on stock though...
axe97 said:
I get the same problem on AOSP roms. Doesn't happen on stock though...
Click to expand...
Click to collapse
Hopefully this will work for you as well.
Sent from my Nexus 7 using xda app-developers app
Gr8Jeepin said:
Yup, I'm a moonshiner. I just read that CM 10 ROMs aren't liking WEP. And to change it to WPA2. Going to try that here in a few minutes.
Click to expand...
Click to collapse
WPA2 on both home and work routers. That's not the issue for me. It seems that when I try to connect manually, it fails. When Android connects by itself, it usually succeeds.
wep has no security if you want wep to work change router to wpa/wpa2 then connect then go back to wep and then you weill be able to connect at starbucks or mcdonalds whileiing eatting or drinking your self high as hell
t1gartist said:
wep has no security if you want wep to work change router to wpa/wpa2 then connect then go back to wep and then you weill be able to connect at starbucks or mcdonalds whileiing eatting or drinking your self high as hell
Click to expand...
Click to collapse
Wait so are you saying I change my router to WPA/WPA2, connect, and then change back to WEP and it will work?
Side note, will all of my devices still connect without having to reenter everything if I keep the WEP password the same?
schott12521 said:
Side note, will all of my devices still connect without having to reenter everything if I keep the WEP password the same?
Click to expand...
Click to collapse
Most likely yes.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Most likely yes.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Guess it's worth a shot, would logs before and after changing and hopefully connecting help at all?