[Solved] Cyanogen Wifi connectivity issues (all models) - Legend General

After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29

Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable

Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.

Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit

Work
Thanks u very much.worked on my milestone

Thanks. Actually worked.

Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".

I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App

pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please

Related

HD2 Web Connectivity Issues and Analysis

Seriously people....
I've seen lots of threads recently. People are complaining that the HD2's data connection cuts out, leaving them unable to access the Internet from their phones for who knows how long. I know, it IS kinda annoying...But the thing is..
I can tell you this IS NOT a hardware problem. It's something to do with either the OS....or something in the phone's registry settings which no one has picked up yet...I hear that phones like the TP2 do not have this error, and I agree. My old unbranded Touch Pro 2 was brilliant, I could use it for IM and texts anywhere...LOL I used to sit on the Bus while people stared at my phone, while I was on Messenger talking to my phone. Anyways, here's what I wanna tell you guys. Hope I help out everyone in some way or another.
What I have:
HD2
3 Mobile Sim-So yeah, My Operator is 3 UK
Living in London, UK
Using ENERGY's 17th March Version ROM
HUSPA, HDSPA Enabled
What I've noticed:
The phone cuts out the signal when the transition between 3G and H occurs in the icons. As a result, the Internet cuts out temporarily, and programs such as Messenger lose connectivity for a while. For example, when the icon is on H, and no one's talking on Messenger, the Icon changes back to 3G....during this moment it cuts out sometimes..until it reverts back to the H icon (Got that? I know, it's a little long and complicated when I word it like that, but read it out and it'll make sense xD)
Now, whenever I have the phone connected to my PC/Laptop (Either as a Wi Fi Router or through the cable and then using Internet Sharing, either way, the phone does NOT change back to 3G, it stays constantly on H (Mind you, I usually download during this period). Anyways, the point being that the connection is VERY stable and constant, when in this state, connected to my PC/Laptop and the device is accessing the Internet through my phone's Data Connection. So what do you all think? And what have YOU found out? Leave your responses and ideas below
Some things I have found out are, if you Enable ONLY HUSPA in the Settings/Connectivity options, the connections seem to be more stable. Furthermore, if you really want to, Disable Advanced Connections, stay only on 3G, and enjoy a LOT of stability (At the cost of slower speed surfing and downloading )
My HD2 does not connect at all anymore. I called in to support because I completely lost data connectivity (web browser, email, slacker, whatever - no connection). They verified no troubles on their end. I moved the sim to my old touch pro (running Energy ROM w/ winmo 6.5 and Sense 2.1) and that phone connects fine. So it's not the SIM, and it's not the network.
I've also done a hard reset to get back to stock and still have the problem, which tells me that it's not a registry / software setting.
They only thing that leaves is faulty hardware - or firmware that a ROM hard reset wouldn't affect. Either way I need to replace the device altogether.
Unfortunately, tmo is out of stock and so I can only wait for a more to become available before it can be replaced.
csharper said:
My HD2 does not connect at all anymore. I called in to support because I completely lost data connectivity (web browser, email, slacker, whatever - no connection). They verified no troubles on their end. I moved the sim to my old touch pro (running Energy ROM w/ winmo 6.5 and Sense 2.1) and that phone connects fine. So it's not the SIM, and it's not the network.
I've also done a hard reset to get back to stock and still have the problem, which tells me that it's not a registry / software setting.
They only thing that leaves is faulty hardware - or firmware that a ROM hard reset wouldn't affect. Either way I need to replace the device altogether.
Unfortunately, tmo is out of stock and so I can only wait for a more to become available before it can be replaced.
Click to expand...
Click to collapse
Which phone company are you with? I experienced the same problem with 3UK in North London for a couple of months up until the beginning of last week but it was a problem at 3's end, not mine. Other people have been experiencing similar issues with non-3 phones in London (http://www.3g.co.uk/3GForum/showthread.php?t=102192).
yes, I had problems in London too before Good Friday. Especially on Tues+Wed.
Others around me inthe library also had similar issues with their iphones. I kept on switching the baseband and modes, and reapplying my 3G settings to keep it alive and solve the outages.
Most people with issues were on vodafone or O2 (like me).
It would work, then cut, then work.
I thought at first it was because I had a custom ROM, but iphone users had the same - and lots of timeouts on requests.
I DO believe however that running ROMS like energy's and Dutty's HG 1.7 with 2.10 (which I'm currently running) bases as 2_08 radios is not great for the uk and exacerbates the connection issue. 2_07 is better...and in any event we SHOULD be using 1.72 based roms with 2_09 radio.
I have also noticed that on COM5 23544 builds the opera mobile 9.7 and 10 google boxes do not work. They come up as failed connection, but then i click on teh link and it works...weird huh???
So I think last week was because of network faults in London. But in general, these 2.10 based ROMS and their radios are not ideal for stability.
I had perfect call and HSDPA stability with 1.48stock+2_09 radio.
Having turned to a 23544 rom (Dutty's HG) with 2_08 radio I've had much less call and internet stability (and quality) over the stock with 2_09.
jakem said:
Which phone company are you with?
Click to expand...
Click to collapse
T-Mobile US.

VERY Strange WIFI problem

Ok
so for the last couple of days I've noticed that when at home, if I turn on the HD2's Wifi, my entire home network stops working. The router can no longer be accessed, even by wired Ethernet.
I figure it was a router issue, so I bought a newer better one by a different company - and what do you know: The same problem persists! As soon as I enable WiFi in my HD2 the router becomes unaccessible - and as I turn it off, all is well again.
I'm a computer technician, an MCSA and usually pretty good with those things, yet this issue baffles me. What on earth could cause that?
No other WIFI devices cause this issue, only my HD2.
Ambious said:
Ok
so for the last couple of days I've noticed that when at home, if I turn on the HD2's Wifi, my entire home network stops working. The router can no longer be accessed, even by wired Ethernet.
I figure it was a router issue, so I bought a newer better one by a different company - and what do you know: The same problem persists! As soon as I enable WiFi in my HD2 the router becomes unaccessible - and as I turn it off, all is well again.
I'm a computer technician, an MCSA and usually pretty good with those things, yet this issue baffles me. What on earth could cause that?
No other WIFI devices cause this issue, only my HD2.
Click to expand...
Click to collapse
What is the radio firmware version on the phone and what is the make, model and firmware revision of the router.
2 IT engineers are always better the one
My older router (with same problem) was 3Com 3CRWER200-75.
I replaced it with an Edimax BR-6524N. Same weird issue.
Both have latest firmwares.
My phone radio version... To be honst, I don't know how to check. My ROM version is 1.48.405.2 (71294) WWE - which is the stock rom of the Israeli version as supplied by Newpan.
Also worth mentioning, this didn't happen until a couple of days ago. Everyting was fine for months with the same exact configuration. SOMETHING must've changed, but what?
And how is it possible for my phone to kill two different routers?
I have the same problem with my laptop when running windows 7 but not linux....seems too me at least my problem is a driver issue.could be the damned for you too possibly. Was there a possible divert update on your phone?
I do not have an hd2 so I am not sure.
Edited for auto correct mistake
Ambious said:
My older router (with same problem) was 3Com 3CRWER200-75.
I replaced it with an Edimax BR-6524N. Same weird issue.
Both have latest firmwares.
My phone radio version... To be honst, I don't know how to check. My ROM version is 1.48.405.2 (71294) WWE - which is the stock rom of the Israeli version as supplied by Newpan.
Also worth mentioning, this didn't happen until a couple of days ago. Everyting was fine for months with the same exact configuration. SOMETHING must've changed, but what?
And how is it possible for my phone to kill two different routers?
Click to expand...
Click to collapse
You check your phone radio revision the same way you check your rom version. Go to settings, about phone, software information and look for the line "radio version".
Your actual rom version is quiet old and if you are still using a stock rom then you may want to have a look at the htc website for your country and see if you can get 1.66 rom or newer.
I personally have never experienced this problem but i always use linksys or netgear networking equipment. The linksys router i have at home i've had for many years (it's a wrt54g v2.0) and it still works perfectly even though it's cpu and networking chipsets are overclocked and it runs a custom firmware.
Well, the ROM is the latest available for my country :-(
But anyway, I managed to solve it by deleted all my wireless preferences and just 'rediscovering' my home network from scratch. Surprisingly that worked and solved the problem, even on my old router.
Now I'm wondering if I should return the new one and stick to my trust good old one, or stick with the new one? It was pretty expensive, and I don't really use an N wireless connection anywhere anyway, so... What do you think, XDA?
Ambious said:
Well, the ROM is the latest available for my country :-(
But anyway, I managed to solve it by deleted all my wireless preferences and just 'rediscovering' my home network from scratch. Surprisingly that worked and solved the problem, even on my old router.
Now I'm wondering if I should return the new one and stick to my trust good old one, or stick with the new one? It was pretty expensive, and I don't really use an N wireless connection anywhere anyway, so... What do you think, XDA?
Click to expand...
Click to collapse
You have no need for it, get your money back.
the hd2 is capable of N speeds. You just need to enable it in the registry. Personally i would use the old one till it dies and keep the newer one in a box till then but the choice is yours
The newer one is a lot of money I spent for something I didn't even need eventually. I'll be turning it back, I think.
Thanks to all who helped You guys rock!
Ambious said:
Well, the ROM is the latest available for my country :-(
But anyway, I managed to solve it by deleted all my wireless preferences and just 'rediscovering' my home network from scratch. Surprisingly that worked and solved the problem, even on my old router.
Click to expand...
Click to collapse
great to hear that you've found a solution!
A thought came to mind while reading this thread.
Wonder if it's possible that a certain radio file/setting on your HD2 might've been corrupted and instead of generating the usual wifi signal, it could've generated a signal on the same frequency that completely jammed you're router signal?
Similar to the radio jammer units available in some countries that can be used for GSM, Wifi, etc... just a thought!
Im glad you brought this up because I had the exact same problem (accept I could connect via ethernet just wifi went dead), almost brought a new router after spending 2 days trying to set it up :/ It wouldnt allow anything to see the router wifi wise let alone connect to it via wifi. I havent turned my wifi on the phone since then but ill try reseting my settings later to see if that works. I didnt wanna risk screwing the router over lol. Im on stock 1.48 rom and radio on o2 as well
bobbified said:
great to hear that you've found a solution!
A thought came to mind while reading this thread.
Wonder if it's possible that a certain radio file/setting on your HD2 might've been corrupted and instead of generating the usual wifi signal, it could've generated a signal on the same frequency that completely jammed you're router signal?
Similar to the radio jammer units available in some countries that can be used for GSM, Wifi, etc... just a thought!
Click to expand...
Click to collapse
That's an interesting thought, and if it's true - reversing it could be a tool for evil - just imagine being able to shut down networks just like that...
Anyway, I'm glad my issue was solved. That Edimax N router is really expensive, and I like my trusty old 3Com way better.
My N*kia n95 used to f*ck up the router like this sometimes

DEV: PPP Issues. Improvement + Summary

This possibly needs to be in the dev section but I will start here.
First off this is not a complaint. What I initially want to do is get an understanding (Technical) of the issues around the PPP dropouts and locks ups.
From where I sit this is the only outstanding issue around the current android builds. Simply the phone rocks on SD card and is ultra stable and fun.
I have noticed various wiki'sstate that internet access is complete however obviously not.
There are a number of issues such as
1: Network dropout. Data connectivity will stop responding. Restart of the radio or mobile data needed
2: Network freeze. Android restart as the radio will not turnoff.
3: console level networking not avail. Eg ping etc simply does not work. DNS does not resolve and ping cannot find a route. Std Android this works fine.
4: Related issues. GPS-A data not downloadable. Only via application layer tool.
Is PPP the default connection type on factory android builds?
What is the difference between the HD2 in dev and a std android with the implementation of the data connection.
How can I help. I have over 20 years in IT and have a thorough understanding of TCP IP layers and routing. I have reasonable understanding of Linux and the kernel IP stack but zero understanding of the android kernel or application layer.
I also have dollars to contribute.
Update:
Currently I am trying all four with isome improvements
1: Updated the Ril WRapper with no luck.
http://forum.xda-developers.com/showthread.php?t=794309
2: Change the phones default connection to GSM PL.
Change the setting found in the menu phone info when you "call" *#*#4636#*#*. There is a option to choose your preferred network. Set to GSM auto (PRL)
3: Update DNS settings.
http://forum.xda-developers.com/showthread.php?t=812930
4: Ensure the correct APN's are being used.
This is no internet versus unstable Internet.
Note. Currently trying all four and things are improving. Had my first dropout after 36 hours versus 2 per day. It happened whilst using the GPS and making a call which always tend to be a stresser anyway. Will try to keep this thread updated.
This thread also has a number of updates http://forum.xda-developers.com/showthread.php?t=813148
I am running a stock WinMo Rom (Latest European release 3.14 I believe). 2.15 radio on a Telstra Network in Australia. My phone is a T8585. Also running [19.10.10]|<<Mdeejay FroYo Sense Series>>|2.25.771.1| cos I like the transparent titlebars
Now I have been running all 4 of the above for around a week now and have to say there is a def improvement. Where it was common to get multiple disconnects per day I have only had 3 in the last week. Mainly when I use the GPS.
I am still searching and have yet to find a 100% fix the stability is now at a point of reasonable reliable. Also noted that the Devs are still hard at work on this.
Update 31-10-2010
A good test is to open google maps while driving. Its about the only time I get a drop out now.
The GPS kicking in always stresses the radio and that combined with the handover of cell sites is a great deal breaker.
This also seems to be consist with my suspicions around the poor handling of corrupt connections.
Eg the system on fresh boot only has a table for handling 50 connections line. This ensures it can handle multiple simultaneous connections as well as background coms.
Now when a connection is damaged or locked normally it should timeout and/or then be deleted from the table. My suspicions is that this is not happening and all the avail connection handling are slowly filling up until there are now free. Frozen this is why it seems to be very unlikely for a freeze to occur straight after a restart but more likely after a day. Also dependent on stress environments. Homes with lots of RF noise, Long way from cell towers, driving, lots of gps use, Wifi cut over.
http://forum.xda-developers.com/showthread.php?t=812930&page=7
http://forum.xda-developers.com/showthread.php?t=794309
Thanks for the response.
I was not looking for work around but more technical information to try and identify where the issue lies. curious to see if ppp is the default and if the ppp implementation should work or is it still a hack/work around.
The steps I have tried are
1: Updated the Ril WRapper with no luck. No improvement
2: Change the phones default connection to GSM PL. No improvement
3: Update DNS settings. Still testing however does not resolve console level network issues and unlikely related to ppp freeze. No logic?
4: Ensure the correct APN's are being used. No improvement
Note. Currently trying all three
This is also separate to a lot of people issues around APN's. From the application layer internet works fine except for the freeze.
I believe rmnet is android's default connection and ppp is winmo's. I think dft reengineered ppp for Android. Remember seeing it some where when ppp first started to appear. Of course this is how I remember it and my life is hectic so it might be the opposite.
Sent from my Mytouch HD2
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Also with the issues everyone is having why are we not continuing to investigate RMNET as at least this was initially more stable and more of a native option.
dusty_nz said:
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Click to expand...
Click to collapse
That is because it isn't implemented correctly. The radio receiver in our phones was made for PPP, not for RMNET. Latter is standard in native android devices. And there it works very fast and stable. So the devs had to implement PPP in android, which isn't proper working. But they're working on it to improve the stability, I'm pretty sure 'bout that. At least it does work and I had never problems with loosing my connection and bad speeds.
Edit: Those are the known steps to get it at least halfways stable working.
Cheers
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
dusty_nz said:
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
Click to expand...
Click to collapse
But did you also have a delay till it worked? It took me about 20 seconds before any reply came up. And does your ping test work if you try it in the hidden menu when you "call" *#*#4636#*#*?
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
dusty_nz said:
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
Click to expand...
Click to collapse
Right.
Have you seen this thread? It might be a possible solution.
Some people have reported that it works. But I had no time to test it. Had to move servers
That is fix number 3. Update DNS. Testing now. Only been 24 hours however no drops.
Seems strange thou. Hard to imagine it is a DNS issue.
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Update
Update on first post.
Def improvements to be found. DNS seems to be the biggest improvement for me but also running all 4 at once.
dusty_nz said:
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Click to expand...
Click to collapse
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
enneract said:
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
Click to expand...
Click to collapse
any build that says it uses michyprima r11 is still rmnet based. I don't think the nexus one-based kernels worked with ppp at all.
on another note, I was getting loads of Network Freezes (where flicking airplane mode wouldn't reset the data connection) since last week despite not fundamentally changing anything in my Android setup (see sig). However been doing some research around xda yesterday and may have found something else that's improved my ppp connection stability (so far) and resolved my constant network freeze issue... will update when I've tested this for a few more days.
Some improvment?
APNs are correct, Did the RIL_WRAPPER with no significant improvment. This morning I changed to GSM PRL and noticed an improvment.
Before the GSM PRL, I had many PPP drops, especially when streaming large amounts of data. After the GSM PRL update, I did try streaming youtube, Last.FM, slingpalyer together and NetTest, concurrently, everything is working with no PPP drop.
This is not enough to reach a conclusion, but nevertheless, I never could have done it before
Have a look here.
Stock rom 1.48 WWE, radio 2.15.50 and Froyostone 3.2
Thanks for the support!
BTW: How can I obtain the DNS information for my mobile carrier?
Just report.
I didn't believe change dns will work.
But after I change dns, the data suddenly work ( no need to restart!).
So I think it have something relate to dns.
Same thing. Updating the DNS in the build.pro file seems to have the greatest benefit.
I have a suspicion that the issues are caused with the network driver not flushing dead connections. Eg outgoing requests that to not get a reply. Ideally they should be flushed other wise the connection cache will fill until it can no longer take more connections. Symptom dead/frozen internet
All the symptoms seem to relate to this sort of issue
Things like ppp drop out more likely when on the move (More dropped packets). GPS and wifi but back. etc.
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
tgtoys said:
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Follow the link on post 3
will then lead you here.
http://www.opengear.com/faq383-Confi...-APNs.html#USA

[Q] Some apps can't connect using wifi (but can using 3G) on my Motorola Defy

Hello,
If you don't want the boring details of how I discovered the problem feel free to skip the next couple of paragraphs and go straight to the technical details.
I got my first Android phone (Motorola Defy) a couple of weeks ago and at first I was only using it with wifi because my data plan wasn't activated yet. While playing with it a little I realised that I saw a lot less ads than my boyfriend on his 6 month old Defy. I thougt it was weird but, well, seeing less ads is not a big problem.
Then when I got my data plan I saw that when I wasn't home I saw a lot more ads, so I began to suspect it had to do with how my phone was connected to the internet : wifi or 3G.
Next I wanted to try out Astrid and when I tried to log in using my Google account it failed repeatedly. Until I disabled wifi and it logged in fine using 3G.
Then I installed RTÉ DocOnOne to listen to documentaries while falling asleep. When wifi is enabled, it cannot start up because it can't connect (network timeout). Over 3G, no problem.
At first I thought it was my router blocking ports or something but it happens with different wifi APs and more importantly my boyfriend's phone, connected to the same access point, loads everything without a problem.
Let's sum up:
Some apps can't access the network using wifi but work fine when using 3G.
It happens regardless of the wifi AP (tried 4 different ones with different routers) and another phone using the same app connected to the same wifi AP can access the network just fine.
If I initiate the connection using 3G then switch to wifi (typically I launch the app with 3G, switch wifi on without closing the app), it still works after that (RTE DocOnOne has no pb streaming the documentaries once it has launched)
My phone is a Motorola Defy, French retail ROM, not rooted, no motoblur account (skipped the configuration), Froyo 2.2.2 (already on the phone when I got it), system version (if that means anything to you) Version.34.164.3.MB525.Retail.en.FR, kernel 2.6.32.9-g050ccf2, build 3.4.2-164
I can't give as much details about my boyfriend's phone (that doesn't have the problem) because he's not here right now but I can tell you that it is a Motorola Defy too, French retail (I think) ROM, Froyo updated from preinstalled Eclair (using the official Motorola update), not rooted, with a motoblur account
I have no idea if that's relevant or not, but my phone has the "google maps 5.7.0 crashes on Defy" issue (18446 in the android issue tracker) and my boyfriend's phone hasn't.
Has anyone encountered this issue before ? I couldn't find anything on this forum or with a google search.
Is there any tool I can use to try and find the cause of the problem ?
Thank you for reading all this, sorry if my message was long but I wanted to give as much detail as possible to help the nice people who may find what is wrong with my phone
I didn't read all..
but if your phone don't have problems then check this:
1. go to settings
2. Select "Location & security settings"
3. enable this "Use wireless networks" Location determined by WiFi and/or mobile networks
4. test does it work...
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Anne-Laure said:
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Click to expand...
Click to collapse
Hello, did you solve the issue?

Wifi Tether BUG - no Internet on newer kernels KG5 and higher on my Lenovo Laptop

I recently encountered a weird bug when SGSII would establish wireless "g" connection at 54mbps (instead of regular "n" at 65mbps) when doing 3G to wifi tether on my Lenovo Laptop.
My other 2 laptops work fine as expected, however after doing some troubleshooting, its concluded that the wifi router IP forms a "black hole" hope because of which the external communication to Internet dies after 4 or 5 hops (internal to the ISP). While doing a Trace route, the first hop (the IP of the phone's wireless router - 192.168.43.1) doesn't respond to the trace route ICMP requests and fails, however it does work for the next 4 hops before eventually dying after that.
This proves that wifi connectivity between the phone and laptop remains good despite it being downgraded as "g" network when my laptop is capable of "n" at upto 300mbps.
Never had this issue before KG5 or higher builds and it seems all the custom kernels and ROMs based on these newer kernels are affected.
As this issue is affecting only my Lenovo Laptop, not sure if it was ever reported.
Fortunately I am able to flash kernels based on earlier than KG5 build like Ninphetamine-2.0.x (till 2.0.5).
All Ninphetamine-2.1.x builds and kernels like "RAGEmod v1-T30" are also affected.
I am currently on "TOUCH X-treme KH3 2.0 'PERFORMANCE'" ROM and fortunately it seems to be working fine on Ninphetamine-2.0.5 as per my preliminary testing.
I have 2 more laptops which seems to be working fine otherwise on any latest kernels.
I would appreciate if someone could shed some light on the reason behind this bug as I am still investigating the cause and on a fix other than older kernel versions.
My primary usage of this phone is completely impacted by this bug and I hope Samsung would be able to resolve this bug before their next official release of 2.3.4 or higher version builds.
Hmm like the battery drain while charging bug on SGS1 I seems to be the only person shaken up by this bug which makes my SGS2 completely useless when using the latest kernels/ROMs.
My laptop has Intel WiFi Link 5100 AGN. Can someone having same/similar Wifi adapter report their experience?
Not surprised that Wifi tether is not used by most of us and hence such bugs go unnoticed and I paid a HUGE price of crashing my laptop which trying to fix the issue as I never thought it is the phone doing something weird which is preventing my laptop to get proper wifi connectivity.
Unfortunately no resolution till date. All the latest kernels and ROMs are affected. Not sure what is the issue as it defies logic why only one series of Wifi adapters are affected by this bug.
No resolution till date. All the recent kernels are still affected except the one on CM7 ROM.
Seems I need to wait for this update to become official in India before raising with Samsung here.
Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!
No internet
Prankey said:
Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!
Click to expand...
Click to collapse
I still get a no internet access notice on my laptop... Any tips?
Fix
leondb said:
I still get a no internet access notice on my laptop... Any tips?
Click to expand...
Click to collapse
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working
leondb said:
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working
Click to expand...
Click to collapse
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.
grgsiocl said:
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.
Click to expand...
Click to collapse
Latest Siyah 2.6.x kernels have AGAIN brought back the bug on my face!
None of the other options you suggested worked. I have spent hours trying to figure it out and this is what I get when I am affected:
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 * * * Request timed out.
2 164 ms 123 ms 127 ms 218.248.84.5
3 228 ms 68 ms 81 ms 10.42.43.101
4 79 ms 79 ms 80 ms 10.42.43.28
5 * * * Request timed out.
Doesn't make ANY sense on how the first hop is getting blackholed when it otherwise respond to ping requests. I am able to reach till the last hop of ISP before dropping off.
Can any network gurus out here explain this phenomenon? I am unable to locate any logic behind it.
Hope Siyah team fixes it soon for me to enjoy a glimpse of Voodoo Sound on my SGS2.
I have a Lenovo T520 and am using the KK2 stock firmware/rom with no problem whatsoever in tethering...using it at this very moment
It actually seems to be affecting only Intel 5100 adapters like on my R400. I have 3 other laptops and a mobile phone which are working fine otherwise
As I said, it defies logic why only this adapter has compatibility issue when even older Intel 39xx based adapters work perfectly fine otherwise.
Fixed in Siyah 2.6.2 kernel again
Finally got it fixed on Siyah 2.6.2 kernel (to be released shortly) while working directly with the dev "gokhanmoral" in the past few days. All seems to be working now like it was in 2.5.x builds for me.
I sincerely thank gokhanmoral for taking the pain of looking at this isolated bug by Samsung which has fortunately been resolved on the latest drivers (to an extend, still no n mode access).

Categories

Resources