Related
Hello,
I open a thread to describe my problem since nobody could help me until now. I guess this must be an advanced problem, because I don't think I'm noob enough to have screwed something up.
So fisrt of all, the background :
Had a problem with wifi after a fall: low range, crappy bandwith, disconnected all the time
Sent my phone to RMA service TWICE : not fixed in the first time, some hardware piece changed the second time
Got back my phone : firmware updated to 3.14, radio 2.15, wifi working perfectly under WinMo
From there, it gets complicated. At first, I decide to try my old cedsmith sense build, the first with new initrd.gz : wifi works fine
Then I try Darkstone froyo RAM build : wifi connects, gets an IP (I see my device from my router's control pannel), BUT NO DATA, market, browser, web apps won't load...
Then I go to cedsmith's desire HD build (not RAM) : wifi works fine...
Then I decide to try MIUI Star RAM build : wifi works for 2 day, with data freezes and timeouts, then it do not work anymore...same problem as Darkstone's RAM build.
Then NAND arrives :
I try DFT Desire build : wifi ok
I try Gauner1986 Desire HD build : wifi ok
I try CM6.1 build : wifi not ok
I try tytung's Nexus build : wifi not ok
Now I'm back to DFT's desire build, and wifi works perfectly.
So after processing data in my mind, the main common factor in working build is Sense, and no Sense for non working builds...
May I assume that HTC RMA service may have replaced some wifi chipset or antenna for a different one, working with only with HTC builds because they have specific drivers?
I have tried to ping from non working builds with Terminal Emulator :
Router is fine (192.168.0.1 : every packet is transmitted)
www.google.com is not fine (around 1 packet off 5 is transmitted...)
I have an european HD2 with 512Mo of internal storage, so I would like to be able to use non sense build, essentially for space matter...To conclude, I have to questions, mostly for programmers since this is an advanced issue : what do you think my problem is, and what can I do to to fix it...if it can be fixed?
Thank you for your help.
UPDATE : My issue has been solved by adding another router to my local network, dedicated to my phone. It is a Hercules HWNRi-300, with 802.11n feature , so maybe it's the différence with my previous router which only supported 802.11g or maybe it was due to an IP conflict, traffic issue, I don't know...But now that my HD2 has its own dedicated AP, with its own IP sub network, it works perfectly fine, even with non-sense builds.
But anyway, if someone can find a solution for other dudes with the same problem, it would be cool, that is why I'll let this thread hanging around and matbe update it from time to time, since, even if a workaround has been found, the real issue hasn't been really fixed yet.
Thanks everybody for helping and goodluck to others.
It's unlikely any of the ROM programmers will come here.
Do you have a firewall installed?
I was having similar problems before with data/wifi working on some builds and not others but then I figured out it was DroidWall - it was behaving differently on different builds. On some builds, I had to "allow all" in the "white list" in order for data to work.
pkchips said:
It's unlikely any of the ROM programmers will come here.
Do you have a firewall installed?
I was having similar problems before with data/wifi working on some builds and not others but then I figured out it was DroidWall - it was behaving differently on different builds. On some builds, I had to "allow all" in the "white list" in order for data to work.
Click to expand...
Click to collapse
No, I don't have any firewall installed. And I have DMZed the IP obtained by my HD2...
Actually, on these builds, wifi NEVER WORKED, blank data.img no app installed, nothing at all...
Suggested by RedWave31 :
About your problem, seems ur having conflicts about either build.prop, or modules.
One solution i thought about:
- Launch a sense build in wich the wifi works
- Go into system/lib/modules and backup all files in there
- Launch the CM6.1 build
- Replace the cm6 modules with the sense modules
- chmod 777* the folder
- reboot and try
>This may take time like 15 minutes, but for now, it's the only solution that came to my mind
Click to expand...
Click to collapse
My answer :
Thx, I'll add it to my thread (to remember it). I will try to apply solution when I have several suggestions, but I think it won't changer anything : I have already tried to change the kernel on RAM builds, with RAM compliant Hastarin 8.6 with CIFS, copied the bcm.ko and tun.ko modules, and it did not fix the issue...
Click to expand...
Click to collapse
I have also tried to modify build.prop's DNS with google public DNS,no success...
The wifi did not work for me on the CM 1.02 NAND build either, it just said error even tho 1.02 was supposed to fix the wifi lol
i dont think its your phone, iv had on and off wifi issues with every rom sense or not since i began using android builds on my HD2.
and dont even get me started on bluetooth !! I ended up switching to a HTC Desire until just recently NAND came out. Still then i had no wifi on the CM 1.02 NAND build
Nexus wifi worked and MDJ gingerbread wifi and bluetooth worked for me
Visentinel said:
The wifi did not work for me on the CM 1.02 NAND build either, it just said error even tho 1.02 was supposed to fix the wifi lol
i dont think its your phone, iv had on and off wifi issues with every rom sense or not since i began using android builds on my HD2.
and dont even get me started on bluetooth !! I ended up switching to a HTC Desire until just recently NAND came out. Still then i had no wifi on the CM 1.02 NAND build
Nexus wifi worked and MDJ gingerbread wifi and bluetooth worked for me
Click to expand...
Click to collapse
I NEVER had ANY problem with wifi, using more than 10 different builds, Sense and non Sense, for months until sending my phone to RMA for...wifi issue (on Android and Winmo).
So I'm kind of sure it is related...
Tried JAWS' MIUI nand build, and JMDS ultimate build, same issue...
Help please !
I think your issue is the age old RMNET vs PPP builds. Using 3.14 rom and radio 2.15, you should be using a PPP build, which is why I think only those that use PPP, which I believe is only the Desire Builds, is what is causing your issues. But I'm only taking a stab in the dark with one, because I Jaws MIUI is working just fine for me, and i had both 3.14 rom and 2.15 radio, and everything works just fine. If the other builds are working, then why not just use those till something else comes out?
My problem is about WIFI man c'mon, did you even read my first post?
And it's not a winmo version problem or a radio problem : I had switched to chuckydroid and radio 2.10.50.28_2 before flashing MAGLDR....And problem was the same.
Thanks for trying to help really. But I think it is a very specific issue : if twas not, I surely wouldn't have opened a thread about it...
Sent from my HTC HD2 using XDA App
well its certainly not sense vs non-sense problem. it could be a number of issues, one of them possibly being a kernal issue with specific builds. NAND is still very buggy right now, with lots of problems popping up that people didn't expect, so if you find one that works and really want NAND then use the one that works, pretty simple. I can tell you its not a hardware problem because if it was, it wouldn't work on anything, sense or non-sense, sd, ram, or nand build.
@ OP I have the the same problem. Check out the thread I started. Tell me if this is the same problem your having. Been dealing with this forever. http://forum.xda-developers.com/showthread.php?t=879482 I want to fix this problem once and for all.
try this :
when u connected to wifi
check gateway ip and dns
i believe for ip u already have a correct one because you can ping your router, but if gateway and dns has wrong value then data from wifi will not work..
to do that, run terminal or adb shell from ur pc, type :
#busybox ifconfig
find wlan0 and look at ip and gateway
#getprop net.dns1
#getprop net.dns2
this dns value must match with your router dns value (or whatever the internet provider backbone in ur router)
the easy way to look at ur dns router is by looking at status network conection in control panel..
Beretta93 said:
Hello,
I open a thread to describe my problem since nobody could help me until now. I guess this must be an advanced problem, because I don't think I'm noob enough to have screwed something up.
So fisrt of all, the background :
Had a problem with wifi after a fall: low range, crappy bandwith, disconnected all the time
Sent my phone to RMA service TWICE : not fixed in the first time, some hardware piece changed the second time
Got back my phone : firmware updated to 3.14, radio 2.15, wifi working perfectly under WinMo
From there, it gets complicated. At first, I decide to try my old cedsmith sense build, the first with new initrd.gz : wifi works fine
Then I try Darkstone froyo RAM build : wifi connects, gets an IP (I see my device from my router's control pannel), BUT NO DATA, market, browser, web apps won't load...
Then I go to cedsmith's desire HD build (not RAM) : wifi works fine...
Then I decide to try MIUI Star RAM build : wifi works for 2 day, with data freezes and timeouts, then it do not work anymore...same problem as Darkstone's RAM build.
Then NAND arrives :
I try DFT Desire build : wifi ok
I try Gauner1986 Desire HD build : wifi ok
I try CM6.1 build : wifi not ok
I try tytung's Nexus build : wifi not ok
Now I'm back to DFT's desire build, and wifi works perfectly.
So after processing data in my mind, the main common factor in working build is Sense, and no Sense for non working builds...
May I assume that HTC RMA service may have replaced some wifi chipset or antenna for a different one, working with only with HTC builds because they have specific drivers?
I have tried to ping from non working builds with Terminal Emulator :
Router is fine (192.168.0.1 : every packet is transmitted)
www.google.com is not fine (around 1 packet off 5 is transmitted...)
I have an european HD2 with 512Mo of internal storage, so I would like to be able to use non sense build, essentially for space matter...To conclude, I have to questions, mostly for programmers since this is an advanced issue : what do you think my problem is, and what can I do to to fix it...if it can be fixed?
Thank you for your help.
Click to expand...
Click to collapse
I had the same problem than you and fixed it.
Go in advanced wifi settings and click on 14channel wifi regulator
zachmerrill504 said:
well its certainly not sense vs non-sense problem. it could be a number of issues, one of them possibly being a kernal issue with specific builds. NAND is still very buggy right now, with lots of problems popping up that people didn't expect, so if you find one that works and really want NAND then use the one that works, pretty simple. I can tell you its not a hardware problem because if it was, it wouldn't work on anything, sense or non-sense, sd, ram, or nand build.
Click to expand...
Click to collapse
It has nothing to do with NAND, it occured before MAGLDR's release. You can tell me it's not a hardware problem without even reading my first post? How do you know it's not a driver problem, which is hardware related?
Please, this kind of advice won't help, thank you for bothering but do not anymore.
Regards.
mattfmartin said:
@ OP I have the the same problem. Check out the thread I started. Tell me if this is the same problem your having. Been dealing with this forever. http://forum.xda-developers.com/showthread.php?t=879482 I want to fix this problem once and for all.
Click to expand...
Click to collapse
I've read your thread. It seems like a similar issue, but it's not quite the same. For me, even browser is not working, the loading bar is stuck at the very beginning.
The only proof of connexion Icould get was this ping to google, 1 packet of 5 reaching destination, and I with speed test, like 3 to 4 minutes after launch, I could get the button "Begin test". The results were 999 for the ping, -0kb for the download, and for upload, I had some positive, like 20 to 50kb. But the test was very long...
So it makes me conclude that it's not quite the same issue...
lesjaw said:
try this :
when u connected to wifi
check gateway ip and dns
i believe for ip u already have a correct one because you can ping your router, but if gateway and dns has wrong value then data from wifi will not work..
to do that, run terminal or adb shell from ur pc, type :
#busybox ifconfig
find wlan0 and look at ip and gateway
#getprop net.dns1
#getprop net.dns2
this dns value must match with your router dns value (or whatever the internet provider backbone in ur router)
the easy way to look at ur dns router is by looking at status network conection in control panel..
Click to expand...
Click to collapse
I thought it might be a DNS problem, but since I've modified the build.prop with google DNS values, I assumed that it should have settled it. For the gateway, since I can ping 192.168.0.1, gateway must be correctly set up right?
I'll test your idea and will let you know the results. Thank you for helping.
asphaltkiller said:
I had the same problem than you and fixed it.
Go in advanced wifi settings and click on 14channel wifi regulator
Click to expand...
Click to collapse
I already did that and it solved nothing. But thanks for helping.
lesjaw said:
try this :
when u connected to wifi
check gateway ip and dns
i believe for ip u already have a correct one because you can ping your router, but if gateway and dns has wrong value then data from wifi will not work..
to do that, run terminal or adb shell from ur pc, type :
#busybox ifconfig
find wlan0 and look at ip and gateway
#getprop net.dns1
#getprop net.dns2
this dns value must match with your router dns value (or whatever the internet provider backbone in ur router)
the easy way to look at ur dns router is by looking at status network conection in control panel..
Click to expand...
Click to collapse
DAMN I can't believe it ! Wifi worked for like ONE hour ! Then plop, went bugging again !
I flashed MDJ Froyo Revolution, then in order to check your idea, went back to tytung's Nexus NAND, and wifi worked ! Then I went to JMDS build, and wifi worked again at first, but when I tried to connect later, bug was back !
So I checked your commands, DNS displayed is the one of my provider (even if the build.prop is different), and gateway is strange : 192.168.0.255 instead of 192.168.0.1, but the fact is that I did the same thing with fully working sens build, and result was the same...
I'm getting more and more confused there.
So...any idea?
Help...Please guys....
Hi all,
Wondering if anyone knows how to make Android open the ports necessary for incoming connections for server apps to work without having to ping the client first under su?
Or failing that, is there a way to run a script that will ping the client IP instead of having to run the command by hand in terminal?
Thanks!
New, clearer, catchier title
This is the dev section not Q&A.
TheATHEiST said:
This is the dev section not Q&A.
Click to expand...
Click to collapse
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!
i would really love to see a solution there too!
RemoteSMS over wlan would be awesome
Yom said:
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!
Click to expand...
Click to collapse
.............
Any takers?
Posted from My Hacked HD2
Second that! Something's off in 99/100 ROMS, TCP doesn't seem to do anything. Only one Sense ROM by cotulla seems to work.
I disabled the adblocking hosts file to test if it had anything to do with it (e.g. SSHDroid doesn't work with it) but that didn't help anything either
Agreed, does not seem to work on any rom I've tried, only Cotulla's 'Stock Desire' Sense build seems to work (this one: http://forum.xda-developers.com/showthread.php?t=893620).
Too bad Sense's so completely dire, otherwise I'd use that. I want CyanogenMOD.
Having the same question. I am sure here must be someone who knows how to enable inbound connections....
Little update:
I noticed it is possible for me to ping and use all services when using the gateway to access everything, in my case the access point/wifi router.
So it looks like this is some kind of routing/firewall issue but I can't find anything about default blocking or firewalling on android...
Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future
im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2
SantanaNL said:
Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future
Click to expand...
Click to collapse
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...
Yom said:
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...
Click to expand...
Click to collapse
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.
Unfortunatly your steps do not work for me :-(
strikernl said:
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.
Click to expand...
Click to collapse
engst03 said:
Unfortunatly your steps do not work for me :-(
Click to expand...
Click to collapse
That's unlucky. Those steps seem to "work" for me on CleanDroid 1.30. Maybe we can just hope it works again when the stock wifi hotspot is fixed.
Alternate "solution":
Get Cotulla's "Stock Desire" ROM: http://forum.xda-developers.com/showthread.php?t=893620
It definitely works on that. Too bad sense is dog****, and your battery will last for a day max.
strikernl said:
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
Click to expand...
Click to collapse
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again
clyder said:
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again
Click to expand...
Click to collapse
Don't know, it's probably in the kernel, so shouldn't be too difficult, but then again, I haven't really got a clue about building ROMs.
agarp said:
im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2
Click to expand...
Click to collapse
RAFDROID is also a sense build, we want it to work on all builds, stock and CM
My wifi is spotty, at best. I've tried every ROM but every ROM has the same issues: wifi will work for awhile, then it won't, then I power the phone off, then it doesn't work after I power it back on, then I disable it and re-enable it, and it may/may not work. Basically, it's totally unreliable.
I AM running a 2.4 mouse/keyboard combo, but I've tried different channels on my router: 1,6,11 ... they all have issues. My router is a D-LINK 615 and supports 801.11b-n.
I have an iPhone and it is rock solid on the wifi; plays nicely with the keyboard and mouse and doesn't miss a beat. But I REALLY want my HD2 to work: it's more baddass!
Can anyone help me out?
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
danxtian said:
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
Click to expand...
Click to collapse
Where's the setting?... I must have missed it! I can restart the phone and get the wifi symbol, but the reception bars aren't fully lit... only the very lowest (I'm on a sense build now).
I go into wifi settings and it says 'connected' ... but I try to load the browser, or marketplace, or Amazon AppStore ... and I'm not connected. I disable wifi then I renable it and my wifi bar is full! And the wifi works for, maybe, 30-45 seconds before it doesn't work again.
Really, really odd. And this is how it behaves on all ROMs I've tried.
*EDIT* I just saw that my wifi sleep policy is set to 'never' go to sleep.
I just turned on "best wi-fi performance" but I have my doubts that it will work... and my battery is going to suffer, big time.
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Thanks! Help installing a new kernel...
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
Hrmm.... I've been searching high and low for a good kernel and was thinking it might be the issue. I found g.lewarne's kernel http://forum.xda-developers.com/showthread.php?t=917590 ... but I have no idea how to apply it to my current build: http://forum.xda-developers.com/showthread.php?t=1027768
Is it possible to apply the g.lewarne kernel to CME Desire HD2?
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
I just flashed g.lewarne's GL_CORE_V5 from here:
http://forum.xda-developers.com/showthread.php?t=917590&highlight=reboot
... I flashed the whole ROM and I'm getting zero wifi. Even with the other kernels I was able to get some wifi, but none with this one. I like the ROM look a lot, but nothing doing on the wifi front.
Anyone else have suggestions??
WPA vs WPA2
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
diznanl said:
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
Click to expand...
Click to collapse
Ah. Unfortunately I have little control over the wifi infrastructure on campus (I'm in a college environment). That said, I'm not connected to the WPA2 Enterprise ssid but the unencrypted one.
Good to hear you found a resolution!
I have found that WiFi works just as good as my laptop when I'm running Windows Phone 7. Much faster at connecting and can connect further to the edges of signal then Android. I wonder why this is.
I have an HD2 with CyanogenMod7.1 HTC Leo 080111.
I changed my wifi access point and lost connection to it.
Everything else is connecting: Laptops, Motorola Defys and other.
Even the same HD2 with Windows 6.5 (prior to booting Android) connects fine.
I tried to vi wpa_supplicant.conf several times with different settings but at no avail.
I guess the problem is in the ROM. But where? Any clues?
Thanks
makhd2 said:
I have an HD2 with CyanogenMod7.1 HTC Leo 080111.
I changed my wifi access point and lost connection to it.
Everything else is connecting: Laptops, Motorola Defys and other.
Even the same HD2 with Windows 6.5 (prior to booting Android) connects fine.
I tried to vi wpa_supplicant.conf several times with different settings but at no avail.
I guess the problem is in the ROM. But where? Any clues?
Thanks
Click to expand...
Click to collapse
had similar problem on HD2 CM mod (ACA), not sure if it'll work for you but try to disable and enable SSID Broadcast on your router (saving the router settings each time)
Your solution works for me
Thanks a lot. It worked also after disabling/re-enabling the wifi on the android.
Thanks again.
The problem returned
This solution is temporary. After the phone get really out of range and returns, it does not recognize the SSID.
Do you know what is the root cause of the problem?
Thanks
makhd2 said:
This solution is temporary. After the phone get really out of range and returns, it does not recognize the SSID.
Click to expand...
Click to collapse
strange, and I'm out of any ideas, apart from the painfully obvious ones:
- is your wifi hidden? allegedly some roms have problems sometimes with reconnecting to hidden networks
- try changing routers channel to 1, 4, 6 or 11
- seems you're using SD build, if so maybe update it to the newest version, with fresh data.img, do not restore wifi access point but set it anew
Once again it worked
Out of your list I tried everything except setting the channel.
My Access Point worked with Auto channel, meaning that it could change it to the least busy one. For some reason, HD2 did not like it.
Now it works (meanwhile) with channel 4.
I hope for some stability.
Thanks again.
It works fine for the last couple of days. So the proble is the dynamic channel allocation. I guess that at least this ROM feels better with static one.
Thanks.
This thread is intended to be a gathering point for all wifi issues on Android Touchpad ROMs.
Having a separate specific issue thread for this will serve several purposes.
Avoid wifi issues getting lost in the more general Touchpad ROM threads.
Allow issues common to wifi operation on all the different ROMs to be concentrated in one thread.
Reduce annoyance to those who are currently enjoying good wifi operation and who see repetition in the issues being aired.
Make it easier to report tests and experience on different set ups and as new drivers / ROM integrations appear.
Make it easier for users with questions to see if it has been asked before.
Background
Wifi operation on Android Touchpads currently is a hit and miss affair. Some users report flawless operation regardless of access point. Others can get stable operation with careful set up and / or choice of access point but problematic operation on access points over which they have no control. Others still fail to get conditions right for any form of stable operation.
This is in comparison with WebOS based operation where the problems seem to be much fewer. Probably most of the explanation for this difference is the current lack of suitable drivers integrated into the ROM environment. Hopefully this will be fixed at some point and there are some encouraging signs already that improvements are possible.
Factors affecting operation
There are several factors which could potentially affect the wifi performance with Android Touchpads including the type of Access point, the set up of the Access point, the local signal strength and interference conditions, variations in Touchpad hardware build, and how the ROM software has been installed and set up. A key factor on top of all these is the wifi drivers used and how they are integrated.
General advice
Until the fundamental performance is improved the end user of the Touchpad can do some things to help get better performance particularly if they have control over the Access point. Typically this will be in the home situation. Possibilities for adjusting setting for work or public access points tend to be small or non-existent.
Note that not all suggestions work for everybody affected so you have to be prepared to experiment a little to see what may work for you.
The primary suggestions I offer that worked for me in my home situation is to lower the channel setting on the router to Channel 1 even though for me that was worse from a local interference point of view. Other suggestions include avoiding dual band operation and experimenting with security settings (like using WPA instead of WPA2).
Posting
Please post to this thread if
You want to ask Android Touchpad wifi specific questions including problems you are encountering
You can answer Android Touchpad wifi specific questions posted here
You have reports on specific problems that may help resolve wifi issues
You have suggestions on how to improve operation in the short term with existing drivers
You have reports on new driver operation either better or worse.
Please also include the ROM and version used in any specific reports. Although wifi issues have been present on 2.3( e.g CM7) and 4.0 (ICS) the focus for development is now firmly on ICS and that is where improvements are likely to be made.
It is unhelpful at this stage just to post here that you do not have any wifi problems unless you have some specific advice on how that can be generally applied. We already know there are many who enjoy good wifi performance.
Currently I am using CherryKANG 0.2a which does have some experimental new drivers in and for me gives much better performance.
I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?
rochford77 said:
I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?
Click to expand...
Click to collapse
My experience so far with 0.2a of Cherry has been 60 hours of operation without a wifi issue. This includes about 6 hours on a work network where before the wifi fix in Cherry about the only way I could gt a connection was by moving very close to the access point and it would drop out within 5 minutes of moving away. During that 6 hours with Cherry it found the connection straight away, maintained it all the time and even reconnected automatically when I tried a reboot. I'll report further on this when I have had more time on the work network this week.
lafester said:
Nice post but wrong forum
(@ op)
Click to expand...
Click to collapse
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.
Clearing /data/misc/wifi and rebooting makes my touchpad connect to the router without any hesitation, I guess it is similar to forgetting and rebooting(but haven't tried that)
ROM: 0.2a Kang
ClassicNerd 0.0.4
My home network is a Netgear N600 dual band router with WPA2 security as well as a guest SSID. i connect to the 5G band with no issues with the exception of when I have to reboot. On rebooting if I connect to an access point I have to keep the screen alive for around 10 minutes. After that everything is fine, otherwise the system reboots when the screen goes off.
My work network is an overlapping pervasive network using PEAP authentication. On reboot if I do not shut down with WiFi off my settings get into a state where it refuses to connect, or even try. Forgetting the network and then entering the information again fixes the issue. I also get the sleep reboot if I don't leave the tablet on for a bit of time problem here.
I never have any disconnects that are tablet related on ether network.
Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium
guho said:
Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for that. I had been holding off switching to 0.4 based on the kernel issue comments but it looks like 0.4.8a is good to go so I'll try that.
I note with sympathy the response you got from your comment in the other thread. Some guys can get very territorial even though all these ROMS are largely based on same open source and rely heavily on the work of some central devs .
Here is my feedback from 1st full day using CherryKang 0.4.8a in my work environment.
Bottom line is that the wifi fix is giving me a big improvement over previous builds but I don't think is totally problem free.
At the start of the day it found and connected automatically.
Over a 10 hour period it dropped the connection twice after staying connected about 4 hours each time. It didn't reconnect automatically after a drop but required the wifi control to be turned off and then on again to perform the reconnect which it did very rapidly.
This is still a dramatic improvement over before where I struggled to get a connection at all and it would always drop in less than 5 minutes.
To get a better handle on comparative performance I plan to run it under WebOS tomorrow just to get a baseline on how the native tablet performs under the local conditions. I had previously tried out WebOS here and it was stable over the hour or two I had it on but I've never tried it for a full day.
Having said that I also have an ICS Nook Color here which is absolutely rock solid on this access point and has never dropped the connection over several weeks of use so I know its not a fundamental access point issue.
bobtidey said:
I'm fairly neutral about whether this is better in general or development. My original thinking that it was Android based discussion rather than general chit chat, that the end goal was the 'development' of improved wifi operation, and that it might be better local to much of the ROM discussions where wifi can be a trigger issue..
Click to expand...
Click to collapse
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc. It's usually something that you need to flash on your device that affects performance or functionality in some way (themes and visual mods are not included however).
Any sort of "Discussion" or any troubleshooting is usually in General or Q&A, since it can usually span across different roms, and/or software settings. No offence to you, as it is sometimes confusing to people exactly what belongs in the dev section. Usually, if it's not something you are flashing on the device, it goes in another section.
That said, I'm running ClassicNerd Butta v1, and have no issues connecting to my 2.4ghz channel on my router, but it won't connect to the 5ghz channel for some reason.
I have a netgear wndr3700 N600 router with dd-wrt firmware flashed on it.
Edit: changed "wireless networking mode" on the 5g channel from "N only" to "Mixed", and I'm now able to connect.
Since I just had some pretty bad Wi-Fi issues, I guess I should share what I found and how I fixed it.
I've been using my TouchPad very reliably on my home and work networks. I don't know what channel either are on, but at home I'm pretty sure I've been on an 802.11n access point (5 GHz channel). The router at home is a Netgear WNDR3700 v.1, but after problems with the firmware dropping countless other devices, I installed the dd-wrt firmware and configured it to only be an access point, and I'm relying on another router upstream to provide my DHCP and private network. This configuration has been rock solid for a couple months now, and I've never had to reset the access point since! After I installed CM9 alpha 0.6, I've had maybe 3 or 4 times where I've lost network connectivity on my TouchPad, but other devices continued to work; clearly a problem with the TouchPad in those cases since simply rebooting the TouchPad restores connectivity. I do not stop Wi-Fi before rebooting. This is a reliability I can live with since outages have been quite infrequent and easily fixed.
Currently I'm traveling, and I needed to setup a temporary wireless network. To do so, I used Connectify on an older Windows 7 laptop, and I'm using the Wi-Fi board built into the laptop to share the wired connection I've plugged into it. The wireless board is a Broadcom 802.11g with a BCM43XX chip set. When using Connectify, the wireless board runs on channel 11, with no way to configure it that I can find.
After ~48 hours uptime, I tried to use my TouchPad today and found Wi-Fi was not working. Using "Wifi Analyzer" from the market, I observed the TouchPad could "see" a few different access points, but it was unable to connect to any of them, while I was still able to measure things such as signal strength. Forgetting the network connection and reentering the WPA2 key did not work. Connectify showed that my Nexus S running Android 4.0.3 was still connected, but my TouchPad was "Disconnected." Rebooting the device did not restore Wi-Fi. Shuting down my laptop and rebooting did not restore Wi-Fi, although I observed my Nexus S reconnecting. I then rebooted the TouchPad into WebOS, where I could connect again, but booting back into CM9, I could not reconnect. I then turned Wi-Fi off, and rebooted. After turning Wi-Fi back on, I could see the access points again, but still couldn't connect.
What seemed to finally unstick things was turning Wi-Fi off, setting Airplane Mode on, turning Wi-Fi back on, and when I observed that turning Wi-Fi on was not automatically turning Airplane Mode off, I manually toggled it myself. Almost immediately, Wi-Fi connected.
I believe in my case, toggling Airplane Mode in the future may be a simple fix, but I only have the one data point to go by so far.
Sent from my cm_tenderloin using XDA App
For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?
Cubicsilver said:
For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?
Click to expand...
Click to collapse
Your experience I think is very similar to mine. I could get home wifi access OK by adjusting router, but work access was a complete nightmare with none of the ROMs being perfect. Most were very difficult to connect and would disconnect after a few minutes making them unusable.
I find CherryKang is much better and typically lasts about 3 hours for me. I did also try all the wpa_supplicant tricks like you say, short hostnames etc but I can't get it perfect at the moment. What is interesting is that if I turn wifi off and on to get it to reconnect then it either obtains ip straightaway or there is a delay of about 30 secs and then just says saved and isn't connected and won't recover from that. It is about 50/50 which happens and I suspect something similar is happening with a rescan to cause the drop out after it has been functioning. The work SSID is also not published and I wonder whether that can have an effect.
I tried out WebOS at work again to get a benchmark, and got 8 hours with no drop outs so the hardware and access point can function OK.
I am a little puzzled by the nature of the wifi fix in Cherry Kang so plan to post a message in there and I notice some other wifi drivers for a similar device seem to be surfacing. So I'm optimistic that this issue will be finally sorted out soon.
Bobtidey,
I also have done some in depth research regarding the wifi issues and the patches some are compiling into their kernel or as the other post in the CherryKang thread suggested manually inserting and removing the new/old modules. I definitely am noticing an increase in performance when I tried the rom, wifi was stable but for me I just got lucky and have not really had problems besides the random disconnects and what I thought was hanging turning it on. Anyway let me quote from the commit of which both these fixes originate from "Patch Set 1: I would prefer that you didn't submit this This needs stress test before it can be committed (dalingrin)." "Patch Set 1: I'm wondering if you get any firmware crashes using the new ath6kl module (check dmesg - it was the main reason why activating Wi-Fi sometimes takes very long). That's the main reason that I withheld this patch for now." So that prompted me to be a little skeptical on using this as obviously I would consider dalingrin's advice over all. There's some more to it than this as there is also a timing issue that causes crashing :
"This is not quite ready. It is the most promising driver for us going forward. However, none of the android specific functions are implemented yet. There also a crash related to timing issues though I think I can fix that. I will upload another patch set when I get a chance."
Anyway just thought I'd chime in on the subject especially after the last comment which in my opinion is rather unsettling
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk
Classicnerd Butta v2 vs v2.1
Add'l infoI have been running the succession of Classicnerd team builds including the predecessor Xron series. I had no problem in either WebOS or in any build until Classicnerd-Butta-0.1.0-v2. Then I had several instances of connection failure after waking.
I also noticed that the signal strength was shown as dismal even right next to the router. I'm thinking that some of the problem may be the radio not waking up when the tablet does. I was able to connect by tapping the SSID listing on the TP. Then the signal strength returned to normal.
I updated to v2.1-Odex yesterday and haven't experienced any more connection failures.
All of my flashes have been done with factory reset and wiping everything on clockworkmod, reinstalling Gapps and reinstalling apps. I have not restored any backups or backup data.
Update: I have now experienced a couple of instances where the wi-fi is not connected and doesn't automatically reconnect after the TP has been sleeping. Simply turning off and turning on the wi-fi has fixed it.
Just an update on the issue I was having with my 5g network. I changed the "wireless networking mode" on my router from "N only" to "mixed" and am now able to connect.
Nizda1 said:
Bobtidey,
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
I had looked at those before, but I think they may have changed a little now and clarified things. If my current understanding is correct then Cherry Kang has the new board file referenced in the 12342 and gets some wifi benefits but this is a temporary measure. 12341 then refers to fundamentally replacing the drivers when more work has been done on them, hopefully leading to even better long term wifi support.
bobtidey said:
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.
Click to expand...
Click to collapse
WiFi has been beat to death in almost every thread in the development section, I encourage this thread and hope it can decrease the the clutter in the ROM threads.
mike-y said:
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc...
Click to expand...
Click to collapse
I have said this many times, and this is very true in most instances...however in this case I feel differently.
krook6023 (mod team)
Sent from my HTC_Amaze_4G using xda premium
This morning at work my wifi was dropping out more frequently than recently even using Cherry Kang build; it was lasting about 15-30 minutes.
It seems to be correlated with the probability of it connecting properly when wifi is toggled off and on. When it works it immediately says getting IP address. When it fails it delays and then just says saved. This morning this was happening 50% of the time and I had to toggle it off and on again a few times to get it to connect.
I suspect it is also something to do with re-activating the device from screen off even though I have wifi set to the default of never sleep.
So in the afternoon I left it on WiFi Analyser app with the setting to prevent the screen turning off. It stayed connected for 5 straight hours leading more credence to a theory that is somehow a re-connection on screen waking up that could be part of the issue.
Has there Ben any fix for the wifi issue? I'm almost ready to ditch Android on the tp and get a real tablet.