I have a brand new Neo. I first connected to my home's WiFi without problems.
When I tried to connect to other WiFi networks, in many cases it fails by not
being able to get an IP address. It then tries continously and never fully connects.
When I went back home I can experience the same problem. I'm running 2.3.4
and the WiFi sleep policy is set to never (original setting). The only way I can
get it to connect again is if I power off the phone and power on again. And that
works only in some places.
I've seen similar problems reported by others. Some responses suggested
changing the router firmware because of "incompatibilities". What's the deal
here? I can't change the firmware in router's that I don't control. If there are
issues then they should be clearly stated. Who has the problem and what is it?
Note that other Android devices (from other manufacturers: LG, Samsung)
work just fine in the same WiFi areas! This is something specific to the Xperia.
I'm actually kind of shocked the such a problem even exists. SE QA must have
some real issues to let this kind of problem out in the field.
When I tried to connect to other WiFi networks, in many cases it fails by not
being able to get an IP address. It then tries continously and never fully connects.
When I went back home I can experience the same problem. I'm running 2.3.4
and the WiFi sleep policy is set to never (original setting). The only way I can
get it to connect again is if I power off the phone and power on again. And that
works only in some places.
I've seen similar problems reported by others. Some responses suggested
changing the router firmware because of "incompatibilities". What's the deal
here? I can't change the firmware in router's that I don't control. If there are
issues then they should be clearly stated. Who has the problem and what is it?
Note that other Android devices (from other manufacturers: LG, Samsung)
work just fine in the same WiFi areas! This is something specific to the Xperia.
I'm actually kind of shocked the such a problem even exists. SE QA must have
some real issues to let this kind of problem out in the field.