Related
My wifi works as a charm connecting to my home router and most networks.
Some networks, however, disconnect me after ive been connected a few minutes and after that, I cannot reconnect to the same network without performing a soft-reset.
Signal is full strenght and the networks with issues are open networks without any passkey or such, i.e., they require only that you enter a login and password at a login webpage. These are "hot-spot" networks so to say, such that usually exist at airports, hotels or as in my case, the university.
Ive been searching this forum 10 times and read perhaps just as many threads about different wifi issues. Power consumtion is set at "best performance".
What happens is the following:
-After a soft reset, the kaiser connects me to the correct netowork and says "connected".
-I login at the webpage
-Start surfing for a while. And after a few minutes, I am disconnected.
-When trying to reconnect, it says "connecting" and then jumps over to "availible", where the phone immediately tries to connect to another network.
My thoughts about the problem:
1.) It is not the networks fault as I can connect to it after a soft-reset.
2.) I believe that it is something ugly written in the registry or in some sort of cache, which is cleaned after a soft-reset but prevents me to reconnect to the network without resetting.
3.) Ive been talking to the support here at univ. but they claim it is the phone since no one else (10 000 student and employees) has a problem such as I
4.) Same problem with a.) original rom b.) Duttys V3 c.) Duttys v4.
5.) I have tried altering : 3g, active sync, hspda, bluetooth, work/internet, power settings..
In some threads I read that other people have similar problems but in those threads, the problem never seem to have been resolved and the threads seem to be "washed away" over time (people not caring / giving up?..)
I would appreciate your help or even thoughts
Peter
bump! Come on now... someone has an answer.
Does it happen when you delete the offending connection and re-setting it up again?
I had the same problem before with a wifi connection on one of my local coffee shops. It'll connect for a few minutes, will say its connected and a few mins later it'll disconnect. After i deleted the connection under my "Wifi settings" and going through the setup, it works like a charm.
the same happends to me at home with my Buffalo WRZ2-G300N, and at many hotspots... i can't find any solution.
Prolab said:
Does it happen when you delete the offending connection and re-setting it up again?
I had the same problem before with a wifi connection on one of my local coffee shops. It'll connect for a few minutes, will say its connected and a few mins later it'll disconnect. After i deleted the connection under my "Wifi settings" and going through the setup, it works like a charm.
Click to expand...
Click to collapse
If by, deleting the connection, you mean deleting the settings for the offending connection, then unfortunately yes, I have tried that.
Thank you for the hint though!
Ok - I'm experiencing the exact same problem. I can connect fine to my home router - using a WEP key, however, when I connect to my university network via wifi - it connects (after a soft reset) works for a short amount of time and then stops. Only a soft-reset works.
At uni i have downloaded the SecureW2 SecureW2 Open Source EAP-TTLS client for Windows mobile as this is what my uni network requires - are you using something like this ?
As a first step, I am going to use my network sniffer to check the traffic and see whether the connection is dying over the air.
I think we might need to pool all our info on this one - as it's a really annoying problem that must be happening to alot of people.
isujosh said:
Ok - I'm experiencing the exact
I think we might need to pool all our info on this one - as it's a really annoying problem that must be happening to alot of people.
Click to expand...
Click to collapse
It is great (sort of ) to see more people with the same problem. Which radio are you on? I have never changed mine, which is 1.27.12.32.
I'm on Radio version 1.27.12.29... I'm going to run some tests at uni tommorow to see what I can come up with.
these are my versions:
CE OS 5.2.1620 (build 18125.0.4.2)
ROM: 1.56.405.5
ROM Date: 8/28/07
Radio: 1.27.12.11
Protocol Version: 22.45.88.07H
All,
I can confirm that I am having the same issues with the German HTC stock ROM.
This device has so many bugs that it is hard to believe.
Regards
GZ
Spent some time looking at the problem yesterday - can someone please try out the following;
Set Kaiser/TyTnII so that it stays on all the time (no sleep or power options set), reset the device and let it connect to the AP - leave it 'connected' for approximimately 10 minutes, open IE and see whether you can browse internet - and if you can - for exactly how long before the session hangs?
Do the exact same thing as above (soft-reset) only start IE just after the device connects to the AP and time exactly how long before it hangs.
With both these tests its very important that the machine does not go to sleep or standby etc...
I've dragged out my old Hermes which I am taking in to uni to test with on Monday along with my TyTnII.
Final question, can anyone who has this issue please post;
Device Name (I presume a TyTnII)
Radio Version
OS Build
Access Point Brand/Model
Exact Security used to connect with (WEP/WPA etc...)
Hi everyone,
I got my new Kaiser (AT&T Tilt) last week, unlocked of course, and I have reformatted it yesterday, and since then, I am unable to get Wifi to connect to any network! The device shows me the available network and everything, but it says it's connecting to them and then it just says they're available
Any solutions? Suggestions?
-W.
TyTN X said:
Hi everyone,
I got my new Kaiser (AT&T Tilt) last week, unlocked of course, and I have reformatted it yesterday, and since then, I am unable to get Wifi to connect to any network! The device shows me the available network and everything, but it says it's connecting to them and then it just says they're available
Any solutions? Suggestions?
-W.
Click to expand...
Click to collapse
same here.... but no solutions yet....
What ROMS/Radios are you using?
Actually, a solution that would work is to power cycle the device (remove the battery for a few mins out of the device, put it back in, and run again) however, I am not sure about this solution as it may be a temporary one!
The ROM I have is:
1.57.502.2
Radio:
1.27.12.11
Any suggestions on the ROM/Radio?
-W.
just a suggestion of what works for me.......my POS router, i can only connect to it if the wifi power mode on the kaiser is set to best performance. same sh*t with the wizard and the hermes. i seriously should get a new router
i had the same issue. But today i triedd q-mobile rom, which has a different radio than before. It works now. I am finally connected to my router. I have a Tilt as well.
I've noticed variations in performance and willingness to connect to APs depending on the Radio version. On 1.27.12.32 it would sometimes connect, other times not - and take a long time! On 12.17 it connects pretty quickly to most APs. If it doesn't, I turn Wifi off, then on.
Actually, It used to connect to the same network (probably different AP) with no problems at all!
I encountered the same issue today, and even after a powercycle the same thing happened..
BiPolarXpress said:
i had the same issue. But today i triedd q-mobile rom, which has a different radio than before. It works now. I am finally connected to my router. I have a Tilt as well.
Click to expand...
Click to collapse
I had the same problems you guys had. tried to connect then would say available.
i took your advice. first i tried to install the radio that comes with the q-mobile. i couldnt install it to my phone, the screen would black out.
next i went ahead and installed the latest version of q mobile. now it works. and btw q mobile is one fast freaking rom! the screen goes from landscape to portrait in a flash!
thanks!
Mine abruptly started not connecting to any network as well. I'll try the powercycle idea. I have the AT&T standard ROM.
ranger47 said:
Mine abruptly started not connecting to any network as well. I'll try the powercycle idea. I have the AT&T standard ROM.
Click to expand...
Click to collapse
So if I powercycle it it works, except that when I try and connect to what wifi it works for a minute or so and then causes the same problems.
ok, need help with my wifi also, if I go to Wireless Lan settings it says LAN is off, and has a link to click to turn it on, I click it and it connects, shows info including signal strenth, then it disconnects.........it wont stay connected
jsnone1 said:
ok, need help with my wifi also, if I go to Wireless Lan settings it says LAN is off, and has a link to click to turn it on, I click it and it connects, shows info including signal strenth, then it disconnects.........it wont stay connected
Click to expand...
Click to collapse
I am facing the same problem. anyone help?
Hmm, sounds like the same problem I was having. See http://forum.xda-developers.com/showthread.php?t=366526
Not really a fix but a better workaround than having to reboot all of the time.
Wifi Problems with TyTn II
I have a HTC TyTn II and i have some problems with "wlan".
I cannot connect with my router.
I tried it even withouth a security key but it says connecting and for the rest nothing happens.
Ive resetted my router to default settings so everything is open but still i cannot connect my phone to the router.
My router brand is:SMCWBR14S-N2.
Details of my Phone:
Rom version: 1.56.404.6
Rom date: 08/28/07
Radio Version: 1.27.12.32
I hope you guys can help me, Thnx
Hi,SMCWBR14S n2 router the same problem for me but when i turn it to 802.b it works.
I think there is something in the mixed mode what the pda dont respect.
I have a similar problem, but with a twist.
When I'm at my parents, I can connect to their BT Homehub Wifi with no problems at all, even on power-saving wifi mode.
At my house, I have a Siemens Wifi router (from Tiascali), and I cannot connect to this (says it is available, shows signal strength, but won't successfully connect) unless I turn off the encryption/security key.
The only difference between the two networks (apart from the names) is the BTHomehub uses 64bit WEP key and the Siemens uses WPA-PSK key (AES/TKIP not specified in router setup page). I can change the key method on the Siemens to 64bit WEP, but it still won't connect. My laptop connects without problems to both networks.
Is this a problem with encryption handling by the Kaiser?
ROM: Dutty's WM6.1 WWE 29/04/08
Radio: 1.65.14.06 (tried the other radio version of Dutty's rom with same results)
Chris
edit: verfarkas, that's something I haven't trued yet - I'll give it a go when I get home tonight. That would be a nice simple fix - by default, my Siemens router has the "b" (and other suffixes) chosen automatically.
Change to best performance
I was having all of the above problems until I set my power save mode to "Best Performance". Go to settings -> Connections -> Wireless LAN
Ok I have a very iritating problem.
My captivate works amazing in all ways... except one. When I'm at home connected to Wifi, within a few mins of me putting the phone down, or even mid use, the wifi will just stop working. The icon still shows it to be connected however no apps are able to actually get internet. A quick pulldown of the quick access menu and tapping wifi off and back on again gets it going great... for another 5 mins. Then the same thing happens.
Its been like this ever since I got the phone, even after flashing different roms. Now i'm running a Linksys Wireless - N router - maybe they're not playing nice?
I dont think its a hardware fault because when I serve wifi, IE the captivate is an infrastructure mode access point for 3g, it stays on consistently and my laptop can tether for 2 hours or more.
Anyone know what might be causing this?
Thanks
When you have wifi on, go to menu settings and 'Wireless and network'. In Wi-Fi settings you can change the Wi-Fi timeout.
nickbarbs said:
Ok I have a very iritating problem.
My captivate works amazing in all ways... except one. When I'm at home connected to Wifi, within a few mins of me putting the phone down, or even mid use, the wifi will just stop working. The icon still shows it to be connected however no apps are able to actually get internet. A quick pulldown of the quick access menu and tapping wifi off and back on again gets it going great... for another 5 mins. Then the same thing happens.
Its been like this ever since I got the phone, even after flashing different roms. Now i'm running a Linksys Wireless - N router - maybe they're not playing nice?
I dont think its a hardware fault because when I serve wifi, IE the captivate is an infrastructure mode access point for 3g, it stays on consistently and my laptop can tether for 2 hours or more.
Anyone know what might be causing this?
Thanks
Click to expand...
Click to collapse
Try goin to settings->wireless and networks-> wifi settings (menu key)advanced and set the sleeping policy to never
I've done that...
i *Think* i've fixed it. I was using WPA2 IPK encryption or whatever.. Switched back to the 64 bit crappy WEP. Wifi was on all night and all morning with no cut out.
Might be just another linksys-is-crap situation.
HI, I figured I keep my wifi woes within a singe thread so.
I have an old D Link WBS 2310 router.
I recently got a message from AT&T that I'm near my data limit. This surprised me as my last cycle I barely got near 500mb. Since my bill isn't ready yet, I can't see exactly what it is I'm doing to use so much data.
TO be safe I figured I'd pull out my old router and set it up. After hours of hassle getting it to work on my new computer, I wasn't able to get my Captivate to hook up to it.
My laptop works fine. It gets a fast wifi signal, but my phone just says "Obtaining IP address" for a while and then gives up.
My phone gets wifi at work, at friends', at coffee shops - but not at home.
I've tried this with no encryption, WEP encryption and WPA2 encryption.
Each time my laptop would hook up to the wifi but my phone wouldn't.
I searched some other forums and found similar problems with HTC phones.
Some answers say that D Link sucks. But that answer applies to other brands as well.
Do I need "n" wifi, rather than "g"?
I don't want to buy another router only to find it still doesn't work.
Any help?
gluvox said:
HI, I figured I keep my wifi woes within a singe thread so.
I have an old D Link WBS 2310 router.
I recently got a message from AT&T that I'm near my data limit. This surprised me as my last cycle I barely got near 500mb. Since my bill isn't ready yet, I can't see exactly what it is I'm doing to use so much data.
TO be safe I figured I'd pull out my old router and set it up. After hours of hassle getting it to work on my new computer, I wasn't able to get my Captivate to hook up to it.
My laptop works fine. It gets a fast wifi signal, but my phone just says "Obtaining IP address" for a while and then gives up.
My phone gets wifi at work, at friends', at coffee shops - but not at home.
I've tried this with no encryption, WEP encryption and WPA2 encryption.
Each time my laptop would hook up to the wifi but my phone wouldn't.
I searched some other forums and found similar problems with HTC phones.
Some answers say that D Link sucks. But that answer applies to other brands as well.
Do I need "n" wifi, rather than "g"?
I don't want to buy another router only to find it still doesn't work.
Any help?
Click to expand...
Click to collapse
part of the IEEE 802.11n standard is backward compatibility with all previous 802.11 standards IIRC, so there should be no need to buy a new n device.
HOWEVER, i am also having issues with my wi-fi and my g capable router. i will meddle around with some phone and router settings to see if i can fix this, this is one area were i can actually be of some use on this forum
Hi. It turned out the wifi was broken on my captivate. I reset it to stock and it's all better. It had been working up to the previous day so I assumed that it was still working. The router goes down intermittently in general, so I've ordered a new one to see what's up.
Hi, I'm back! So after resetting the phone and getting wifi to actually connect (rather than being stuck searching for IP address), I'm now having the exact same problem is the OP. The OP seems to have solved this by switching to WEP. I tried this and it doesn't work. My timeout is set to never. Also, it's the same at home (I replaced my router) as well as at Starbucks and a friends house.
I'm connected, but can't download or sync. It works initially and then stops, and then comes back in briefly and then stops, all the while "connected." Sometimes I can fix it temporarily by turning off wifi and then turning it back on.
SO what's the deal? Is it a hardware problem? Is there some secret magic code?
edit: Just disabled encryption - same problem.
I have looked at every thread and forum possible for the past 2 months. My wifes nexus and my own connects to our home wifi for a few minutes then disconnects itself (weather the screen times out or not) and will not reconnect at all. I have tried the wifi fix apps on the market, changed the settings on my router numerous times, factory rest my router and phone, changed roms, and even routers but nothing seems to work. My wife's nexus is stock and not rooted so I have been using hers as a reference thinking it was maybe a rom I was using but she is having the same problem. Any ideas would be greatly appreciated.
sigep235
I had that problem but as soon as I got to 2.2.1 and/or used a newer Radio version, the problem disappeared...
Although, N1s are still very picky on routers...try with another router and check if it keeps the connection alive.
Also check your router settings to see if they're optimal (try having no password set and see if it keeps the connection...if it does then it might be a problem with the N1 not crypting information well or so)
You could also try updating the router's firmware.
Make sure your wifi policy is set to "Never" (go in wifi settings the press Menu and click on settings)
Last thing you could try is manually set an IP address + gateway + netmask in the wifi settings as well as setting your N1's mac address to that same IP address in the router...
If nothing works then, I'm completely out of solutions
I just got on to look at some of the settings with my router when I noticed that some times when my phone says I am connected to the wifi there is no IP address assigned to the phone. Under connected devices it says "android device" but with no ip address associated with it...
I still have the problem
I still have the problem. I have pretty much given up on it. I have heard that if you increase the minimum CPU speed a little, it will help. I'm not willing to do that as it will undoubtedly waste more battery.
I have changed the wifi sleep policy back to "when screen turns off", because having it on "never" would make the phone think it's connected..when it isn't..leading to hours of no email notifications and such. But I can't imagine how frustrating this must be for people who don't have a data plan or some other similar situation.
I'm thinking about getting a Wireless N router (I have a G right now) and seeing if that helps. But even if I was to get one, I don't have much money to spare so I'd probably get the cheapest N routers, around 30-50 dollars..and I don't know if those are any good...or if there really isn't any difference between the high priced and low priced ones.
I said this in another thread, but I'll say it here.
I tried all of the things everyone could suggest and none of them worked. When I heard Broadcom updated the driver and CyanogenMod put it into his nightlies, I bit the bullet, unlocked my bootloader and installed CM6 and it changed NOTHING. So I went out and bought a new router: Cisco E3000. It works great. So I guess it was a bad combination of phone and router. I had to spend hundreds of dollars. Really ****ing pissed me off. But I wasn't going to buy a cheaper router without dual channel wireless N.
ksc6000 said:
I still have the problem. I have pretty much given up on it. I have heard that if you increase the minimum CPU speed a little, it will help. I'm not willing to do that as it will undoubtedly waste more battery.
I have changed the wifi sleep policy back to "when screen turns off", because having it on "never" would make the phone think it's connected..when it isn't..leading to hours of no email notifications and such. But I can't imagine how frustrating this must be for people who don't have a data plan or some other similar situation.
I'm thinking about getting a Wireless N router (I have a G right now) and seeing if that helps. But even if I was to get one, I don't have much money to spare so I'd probably get the cheapest N routers, around 30-50 dollars..and I don't know if those are any good...or if there really isn't any difference between the high priced and low priced ones.
Click to expand...
Click to collapse
Nexus has N connectivity but only on one band (2.4Ghz) and I don't think the technology matter (heck, I'm still on 802.11b ) it's really more of a phone/router combination problem...
I did actually test on my VERY CHEAP spare 802.11g router (DLink --> do not buy their products) and the connection did NOT stay...that was back when I was on stock FRG83 though...I should try again on Cyanogen but I'm wayyy too lazy ^^
btw, I really don't get why people always unlock when they wanna flash a rom....heck, keep your warranty!! there is an easy way of doing it without unlocking...meh
PS: I have a 50MB data plan (technically, I didn't buy a data plan, it came free) so I AM a heavy wifi user and it was such a pissoff to find out that my new Nexus One couldn't connect to Wifi and keep the connection alive...now I'm damn happy that it works after all that fiddling ^^
@sigep: try to assign a manual ip to your N1's mac addres...or update firmware, it definitely looks like a router problem...
The root without unlocking method wasn't too tested when I unlocked my bootloader.
I have made two swaps with no problems since.
pwig said:
The root without unlocking method wasn't too tested when I unlocked my bootloader.
I have made two swaps with no problems since.
Click to expand...
Click to collapse
Oh kay sorry then
Although all the new wikis and todos should emphasize on the locked bootloader methods to avoid voiding warranties...although I admit fastboot is always noobproof but I digress ^^
I've been testing several routers from different brands, and the only one that seems to work fine with mi Nexus One is the Linksys/Cisco WAG160N (802.11n, but 2.4 GHz only). However this one has other issues of its own, like not being able to connect to mapped ports after two days up and running (not even from the LAN). The N1 works fine, thought, it doesn't disconnect overnight.
I've also tried an SMC (SMC SMC7904WBRA-N, I think). This one is really bad, the router freezes after only two days of use, the lights freeze and it stops working altogether. I returned it after a week.
I'm currently using a Sitecom (300N WL-348). With this one the N1 WiFi is dropped over night, and the connection to this AP is disabled. I'm still testing if moving to a less crowded channel could fix that. I hope it does, since this router seems to have a more stable firmware that the Linksys/Cisco, same WiFi coverage (which is quite good), and even better WiFi performance. Not all is good, though, DSL performance is worse.
In the past I used Netgear routers. The firmware was stable as rock, but the hardware not so much and after a year of use they are very prone to failing. No idea if newer models are any better in this regard, they are impossible to find, so I don't think this has improved.
Since I have DSL at home, I'm looking at routers with DSL modem built in, so I don't have to have two devices (DSL modem and wireless router).
From my observarions - Nexus will disconnect from WiFi when the IP it has is lost and the network doesn't supply IP on time. After 1 or 2 IP assignment timeouts, it will skip the network and refuse to connect.
Every router I've connected to that supplied IP on time, even when revoked every X min, didn't cause disconnects.
Of course, WiFi on sleep set to "Never".
Success! Last night I updated the firmware of the Sitecom router, and changed the WiFi channels (it's set to use wide channel, so it uses two channels). This morning the N1 had still a solid WiFi connection and over night it updated all services just fine (weather, Facebook, email).
I've been using the Sitecom router since my last post with no issues. Then last friday arrived a small update that broke WiFi. On Saturday arrived the bigger update to Android 2.2.1 but the problem with WiFi remains. Before 2.2.1 Wifi has been working fine every day at home and work, now with 2.2.1 it's broken at home and work.
Are we moving forward? If Gingerbread doesn't fix this problem I'll have to do something about it: try cooked ROMs or even getting another phone . Currently my N1 keeps disabling my access points all the time.
I have a Samsung Galaxy S Vibrant device and a strange Wi-Fi connection problem.
It seems that the WiFi conneciton is being lost intermitently with no apparent reason. I ping the device, most of the time there is a 'Request timed out' and only sometimes a 'Reply from <address>'.
On the device side the connection behaves erratically as well, sometimes there is connection but most of the times there isn't. The strange thing is that under device's Settings->Wireless and network->wi-Fi settings the connection's status is "Connected" all of the time, signal strength is excellent, link speed is 54Mbps.
I had this issue on a native 2.1 Samsung Galaxy S Vibrant install, then decided to flash a custom 2.2 ROM hoping to end the mistery. The new custom ROM is an Axura21VE.zip and the WiFi connection problem is exaclty the same as before.
Does anyone have the same WIFi issue as I have? And yes, I did a search before posting this. In fact, I searched for several weeks and saw many SGS Wi-Fi problems being reported but either they are different or they are similar to mine with no solution. Since I need a stable Internet connection on the device for app development, next logical step would be looking at reverse USB tethering. Yet decided to post here before giving up on Wi-Fi.
For the record, the Wi-Fi acces point is under my control, i have a ASUS P5B-MX/WiFi i946GZ motherboard, windows XP sp3. I tried, I think,
every possible combination of Wi-Fi settings available. The only client device I have at home is SGS. At the office network, SGS is having the same
Wi-Fi issues, while a HTC Desire and many laptops don't.
here is what I just found out: if I do a constant ping form the device to google.com for example, then the conenciton is maintained all right. So, should I constantly ping something to maintain a decent connection? Is there a setting or something in Android OS I am missing?
I had this exact problem - changed my router and it works perfect now. Really weird and not an ideal solution but worked for me so far (touch wood!). Try playing about with your wifi config maybe, change encryption, channel etc. Good luck.
Hi, I'm having the same problem on my Galaxy S i9000 on Darkyy's v7.8. I never used to have this problem until I flashed the second to last release. The device says I'm connected to the network but I can't get any internet access. I tried reflashing my official firmware DXJPA, but I still no joy. I'm not really sure what to do.
YES... i have been searching for days. I feel I may have a similar issue. im connected, speed good, IP there.. no data, browser just hangs. seems to happen less in stock. (Rogers captivate, P10.1) also WiFi manager reads my WiFi channel off by 2!! so im set to use ch 9 on the router and WiFi manager on the captivate says its broadcasting on ch 7?? any ideas? ping to infinity??
side note: this happens on all routers and all roms. other galaxys on my network read proper ch... GF's Iphone see the right channel?? HELP..
I'm also having these problems, reposting my reply from another forum:
Just wanted to chime in that I am also having these problems with my samsung vibrant. Seems to only happen from my work router but happens very consistently. Wifi will work immediately after setting it up but after a short time period will stop working completely. It will say it is still on wifi but will in fact have no access to the local network or the internet. Stopping/restarting the wifi connection doesn't fix it. The router has to be manually 'forgotten' and then re-added for it to begin working again. (Update: sometimes this does not work either, in fact).
This is with a 2wire modem (standard issue by at&t) using WEP security in 802.11b/g mode.
Some people recommended switching from 201.11b/g to pure 201.11g. I tried this with no luck. It was also recommended to try to app 'wifi fixer'. This also did nothing to solve the problem. Given that it is my work router, I don't want to go changing the encryption and other crazy things as I'm not the only person using this router and it would break the connection for others.
MRSizzle in another thread (which xda isn't allowing my to link to) seemed to accurately describe the problem as such:
"It appears to be a driver issue with the Samsung base OS drivers in the phone. Possibly sleep policy is not operating correctly and the wifi radio is being disabled by the hardware and is not being controlled correctly by the software so the WiFI icon still appeers to indicate the phone is connected. Also the wifi signal is not being correctly reported. the signal appears to be attenuated more than it really is."
This description would line up with the OP's reports that repeated pinging will keep the connection alive.
Hi, I'm having the same problem on my Galaxy S i9000 on Darkyy's v7.8. I never used to have this problem until I flashed the second to last release
ASK DARKY its his rom and will know more .
jje
Anyone figure this out? I'm trying to use the Web Desktop app but can't because I can't even establish a connection with my phone!
Hi friends,
I have similar problem, but at first I easilly connected to Internet, but now I can connect to my WI-FI but no internet connection. I am not sure but maybe this has occur after updating to Android 2.2.
Any suggestion?
Thanks in advance.
explanation and apology
I was wrong in my assumption that it's an Android device problem. The problem was in the Asus motherboards embedded Wi-Fi access point. I bought a separate Wi-Fi router and now everything works like a charm.