Related
For some reason when I enable my location and my phone is connected to my Airave, it locates me in a city about an hour away. When I turn my airave off, it is able to tell the actually city I am in. Is there anyway to correct this?
I am using the stock ROM with WM6.5 which was recently released. The only modifications I have done is added the Taskbar and Co0kie home screen mod.
Thanks,
Same issue. Soon as the phone enters the building with the Airave it jumps 200 miles.
I can answer this one! I'm a Sprint employee and am extremely familiar with the Airave.
The Airave broadcasts signal allowing your phone to have signal in an area where Sprint signal is not normally available. It does this by receiving a request from your phone, connecting to the Airave, and then then sending the request via your broadband internet connection rather than through a Sprint tower.
The problem you are experiencing is because of settings with your Internet Service Provider (ISP). Your location, often refered to geolocation, is set by your IP address (provided to you automatically by your ISP). ISPs often base IP addresses in a city where the company is basing operations. For example, I live in Indianapolis, Indiana, and use Comcast as my ISP. My IP address however is based out of Rockford, Illinois.
If you go to http://whatismyipaddress.com, you will see the city to which your IP address is set. The city listed at this site, I would assume, is the city you see on your phone as your current location.
As far as a fix, I don't have much in the way of an answer. If the weather application is the issue, you could always set a city, rather than using the automatic location setting.
I hope this gives you some insight as to why the problem exists.
I had this same problem with my Touch Pro 2 using one of the Mighty Roms. I can't believe I didn't even think of the AirRave as the culprit. I figured the weather location came from my GPS coordinates, not which cell tower I'm connected to. This makes sense now. However, once I updated to Mighty Roms latest Rom, I no longer have this problem and my location is correct. Maybe Time Warner NY is doing something differently now and my AirRave is reporting the correct area. Before my phone was saying my location was "Jackson"...now it says "New York".
MrMaNz said:
Before my phone was saying my location was "Jackson"...now it says "New York".
Click to expand...
Click to collapse
Precisely the same has happened with me. On cooked ROM's my location is "Jackson" (NJ, I think) and on the Sprint 6.5 ROM it's New York. I'm on Comcast cable, not Time Warner. I doubt this is an issue of the ISP one uses to access the internet from the Airave's location but rather of Sprint as the ISP for the phone via the Airave - Sprint is supplying the IP address for the phone, not your personal ISP.
The likely explanation for the apparent location change, of course, is that between ROM flashes Sprint changed something that provides different geolocation data and that this has nothing to do with the ROM itself.
More interesting is the comment above about a recent cooked ROM providing correct location information. It seems as if it should be possible to hack the location feature to use GPS rather than IP geolocation.
It is not rom related you are wrong. It is all about the ip address location.
same thing for me, but dont think it has anything to do with airave, dont even know wat that is or if i even have it on, but my fone shows my current location as a small town about 20 miles away with a population of about 200 (not thousand, just 200) so dont think it has anything to do with towers, any ideas?
It is all about the ip address. If I plug in the phone to activesync I get one ip and one location. If I use the verizon data connection I get another ip and another location
It does not appear to be IP related as the website posted to check the ip shows me in Kansas... but my location on the TP2 shows Canton, OH while connected to the airave. I know that I put in a zipcode in the settings for the airave on sprint's website and even that zipcode is different than the city I get.
jobobusa said:
It does not appear to be IP related as the website posted to check the ip shows me in Kansas... but my location on the TP2 shows Canton, OH while connected to the airave. I know that I put in a zipcode in the settings for the airave on sprint's website and even that zipcode is different than the city I get.
Click to expand...
Click to collapse
When you go to the same website ON YOUR PHONE does it show you as being in KS or OH?
Your phone and your computer don't have the same IP, even if your phone is connecting through your computer.
jhworley said:
I'm a Sprint employee and am extremely familiar with the Airave.
...
The problem you are experiencing is because of settings with your Internet Service Provider (ISP). Your location, often refered to geolocation, is set by your IP address (provided to you automatically by your ISP).
Click to expand...
Click to collapse
You're quite wrong about this.
The IP for my phone is supplied by Sprint's DHCP servers when it connects via the Airave. It's not supplied by Comcast's DHCP servers at all.
At the moment, both my notebook and my phone are online. Both the wireless router to which my notebook is connected and the Airave go through the same Comcast cable modem. There is no cellular service available near my house except via my Airave.
At the moment, my notebook's public IP is 24.147.35.xxx and my phone's is 174.146.248.xxx. As you can see, they're quite different. If I switch off my cellular radio and connect the phone to my WiFi, it uses the same IP of 24.147.35.xxx as my notebook. The 24.147.35.xxx address gives a geolocation of Monson, MA even though I'm in NH. The 174.146.248.xxx gives a geolocation of Cedar Grove, NJ.
Thus, your answer is wrong on several fronts. The ISP that supplies internet connectivity to the Airave has nothing at all to do with geolocation on a phone connected through that Airave. Further, the location shown on the phone still does not match the actual geolocation that corresponds with the phone's IP address. In the real-life example before me right now, the location on the phone is 21 miles from the geolocation of the phone's IP address.
Finally, the location service on the phone does not depend entirely upon geolocation based on IP address. If I turn off my cellular radio and connect via WiFi, my phone decides that it's in Hancock, NH which is correct even though the phone's IP geolocates to a different state.
That last bit suggests that the location service on the phone is perfectly capable of using GPS if it can't use IP geolocation.
mstevens said:
You're quite wrong about this.
The IP for my phone is supplied by Sprint's DHCP servers when it connects via the Airave. It's not supplied by Comcast's DHCP servers at all.
At the moment, both my notebook and my phone are online. Both the wireless router to which my notebook is connected and the Airave go through the same Comcast cable modem. There is no cellular service available near my house except via my Airave.
At the moment, my notebook's public IP is 24.147.35.xxx and my phone's is 174.146.248.xxx. As you can see, they're quite different. If I switch off my cellular radio and connect the phone to my WiFi, it uses the same IP of 24.147.35.xxx as my notebook. The 24.147.35.xxx address gives a geolocation of Monson, MA even though I'm in NH. The 174.146.248.xxx gives a geolocation of Cedar Grove, NJ.
Thus, your answer is wrong on several fronts. The ISP that supplies internet connectivity to the Airave has nothing at all to do with geolocation on a phone connected through that Airave. Further, the location shown on the phone still does not match the actual geolocation that corresponds with the phone's IP address. In the real-life example before me right now, the location on the phone is 21 miles from the geolocation of the phone's IP address.
Finally, the location service on the phone does not depend entirely upon geolocation based on IP address. If I turn off my cellular radio and connect via WiFi, my phone decides that it's in Hancock, NH which is correct even though the phone's IP geolocates to a different state.
That last bit suggests that the location service on the phone is perfectly capable of using GPS if it can't use IP geolocation.
Click to expand...
Click to collapse
Well said. BTW, Sprint has still not been able to fix this. All of my phones show Galena, IL instead of Cedar Rapids, IA (where I really am). The latest reason I got from Airave Technical Support is:
The Airave unit gets GPS data from a satellite. The location you see, is the location of the specific satellite that the Airave is connecting to.
Oh... My... God... I couldn't think of how to politely disagree; so I just flat out said that makes no sense whatsoever. The floor manager tried to tell me the same thing. :| This was after she tried to tell me the GPS was only used to facilitate connection to the network; which I agreed was possible, but pressed her to why it showed me about 100mi off if it was to be used for network connection? I also asked if this would affect my 911 use as the Airave is suppose to provide E911 data in case of emergencies; she said it doesn't use the GPS location for 911. I pointed her to the Sprint website which claimed it did; after which she started me a 'Network' ticket. ::sigh::
I'm having this same issue. I originally got my airave for my office which was out in the middle of nowhere with no sprint service. I have since moved and changed jobs. Even though I live in an area with strong coverage due to the buildings (I think) I get signal fluctuations from full to nothing and dropped calls. I set my airave back up which solved that problem but when I am home my weather still shows the location of my previous office which is 200 miles from where I am now. I have made 4 calls to airave "support" and they have been unable to fix the problem. The last 2 calls I finally hung up after they left me on hold for about 45 minutes (I guess that's their current solution). Sad that after over a year since this thread was started sprint still hasn't figured out how to change the registered location of the airave. Not only is it annoying but it worries me that should I ever have to call 911 I may have issues. IF the registered location affects E911, and I have no idea if it does or doesn't, aren't they required by law to provide reliable E911 service?
I have a Captivate running Cognition V2.2.Beta1. Using either usb tether or wireless tether, I get pings of 600+ and slow upload/download speeds.
http://www.speedtest.net/result/1064395617.png
http://www.speedtest.net/result/1064400255.png
Anyone else getting better results? Anyone know how to optimize/fix the issue?
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
slifer315 said:
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
Click to expand...
Click to collapse
Actually I manually selected the server in San Diego as that is where I connecting from.
What I am really trying to do is get this to work with a good enough ping to play Aion an MMORPG when traveling and in a hotel room.
what are your results when you pick the recommended server?
San Fran:
http://www.speedtest.net/result/1064446975.png
http://www.speedtest.net/result/1064447880.png
http://www.speedtest.net/result/1064448553.png
you should try a rom with HSUPA support such as assonance, perception, axura, or even the latest cognition now has HSUPA support. you'll get higher upload speeds and therefore a lower ping. then maybe you'll be able to play in very low populated areas because too many other players or monsters would flood your bandwidth with data and therefore cause you to lag out.
Im thinking about it. You said the voice quality goes down with one of those roms however?
I also thinking the upgrade process from 2.2b1 is going to be ugly/hard to do since with this rom it doesn't support clockwork.
call quality used to be bad, but the jk3 modem included in most of them is crystal clear. just find an update.zip from somewhere on this forum that contains clockworkmod recovery, put it on your sd card, odin one click back to stock, do not master clear, reboot to recovery, reinstall packages twice to install clockwordmod recovery, data wipe / factory reset in recovery, and finally flash your rom of choice. as long as you don't change that update.zip, which you shouldn't ever need to, you can use this method to flash any rom in the future.
slifer315 said:
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
Click to expand...
Click to collapse
Where you are physically located has nothing to do with it (or not much in picking a server). Your phone gets on the cellular network near your house. Its data transits AT&Ts servers and hits the Internet wherever it exits the AT&T data centers - usually Dallas, TX. Best results are when SpeedTest tells you as that server is closest to the AT&T Proxy server that is putting you online.
Cell Phone networks were not built with Latency or ping times in mind, so tethering will give mediocre performance. Aircards tend to do better as carriers and prioritize traffic for PCs over phones - also depending on how you are tethered, there may even be one less hop.
alphadog00 said:
Where you are physically located has nothing to do with it (or not much in picking a server). Your phone gets on the cellular network near your house. Its data transits AT&Ts servers and hits the Internet wherever it exits the AT&T data centers - usually Dallas, TX. Best results are when SpeedTest tells you as that server is closest to the AT&T Proxy server that is putting you online.
Cell Phone networks were not built with Latency or ping times in mind, so tethering will give mediocre performance. Aircards tend to do better as carriers and prioritize traffic for PCs over phones - also depending on how you are tethered, there may even be one less hop.
Click to expand...
Click to collapse
that was exactly my point.
slifer315 said:
that was exactly my point.
Click to expand...
Click to collapse
Yes, but picking your IP address should give you the same physical location as the speedtest.net servers - that is how they locate you - IP geo-location. Your IP address is the last hop Speedtest sees - they are trying to ping you. If you pick your physical location then the speedtest has to cross the internet to your IP address then ride the carrier network back to your physical location.
Picking your physical address should make ping times and speedtest times longer.
I second using a HSUPA rom. I've been on perception for the last 2 weeks using it to tether my pc for some Black Ops Multiplayer. On the cognition rom i would regularly ping about 300+ with 1.5mb down/1up. Now with perception 7 i am pinging under <100 with 3.5mb down/ 1.5up. Its all in the modem the rom is using.
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
When I switch to 3g and Wifi, they resolve normally. On 4g, it's as if the dns server is having a tough time getting there. The weird thing is when I ping the sites by domain, I'm getting responses on my phone so I'm not even sure if it's DNS. Since if it was DNS I'd get slow responses, or I would only be able to ping it by I.P address.
So, I got an app on the market called SETDNS, and it seems to change my DNS server (I have it set to OpenDNS) and it still doesn't load up these sites fast.
Anyone in Houston having an issues with slow sites?
I've verified that it's not my rom (CUBEDROM) as my Co-worker here is on BAMF and is currently experiencing the same thing. I thought it was just the tower we both happened to be on, but we went somewhere outside of work on the other side of town, and still the same thing
Any ideas?
Samsuck said:
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
Click to expand...
Click to collapse
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Same thing with me in Pittsburgh. Even happens when trying to load the XDA app. Just takes forever on 4G but then 3G works fine.
NickWarner said:
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Click to expand...
Click to collapse
Yeah, you know what you're right. If it was strictly DNS then I would only be able to ping by I.P
So is 4g being routed through a proxy or something?
It's getting annoying because I use google search alot on my phone, and it will only load up properly on 3g.
Hrm, so apparently it's not just a Houston thing.
If anyone could continue to confirm this that would be great.
Purely just a theory, but with the big sites like google.com and yahoo.com, they are testing IPv6 (Global IPv6 test day, started yesterday at like 4pm West time i believe). Possible that your wifi and 3g can handle IPv6, but the 4g switches were struggling? Just a theory.
Same issues here in Detroit, was better 20 mins ago but back to the same problem again.
I agree that World IPv6 Day could be a cause, but that's only if you have trouble routing to the IPv6 address. I'm testing using purely IPv4 addresses for m.google.com (First response I get is 74.14.213.193).
On LTE, I'm averaging 300ms for the first hop (69.83.157.73), and ~75ms for the other hops.
On 3G, I average 130ms for the first hop (69.83.157.73), and ~115ms for the other hops.
If that's on each packet, I'm experiencing about double the load time for any traffic to m.google.com on LTE vs. 3G. Of course, that's not taking into account actual transfer speeds, so some of that might be recouped on larger packets, but still, it's significant.
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Same thing in socal so its a national thing
good thing we have options to change to 3g
and not 1x
Hrm, that's interesting.
Yooooo, i think you're right
check this article out
http://www.metro.co.uk/tech/865705-google-facebook-and-bing-test-ipv6-as-net-runs-out-of-space
I can't resolve google,yahoo, facebook,and bing is occasional.
They all will failover to IPv4, and I was testing using the IPv4 addresses. I still think there's something wrong here, and the World IPv6 Day stuff is masking it.
I can resolve all of the major sites in DNS and get both an IPv6 and IPv4 address for them. I chose to test with only IPv4 to ensure that my results would be comparable to each other.
Nick, i agree that there is an error here. I'm just outside of my 4g at work, but can you check what your IP is if you are on 4G? I have a sneaky suspicion that there is a correlation here. If we are on v6 and pinging to v4, could possibly see higher load times if there is software glitches on verizons end. Awfully suspicious if they are not related! And i do know the t-bolt is v6 ready, as all LTE on verizon are required to be v6 ready.
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Samsuck said:
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Click to expand...
Click to collapse
Well there goes my theory. Thanks for checking Samsuck.
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
I may have spoke too soon. This guy says his VZ LTE always assigns him a IPv6
www(dot)anandtech(dot)com/show/4289/verizon-4g-lte-two-datacards-wifi-hotspot-massively-reviewed/3
I can't seem to find any sites discussing for definite what IP's VZ deals out on LTE.
Samsuck, was the checker you used IPv6 capable?
cmhfdisker said:
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Click to expand...
Click to collapse
Same here in Reynoldsburg man. Went down forbme last night around 1am n spotty ever since...
4Geezy ON DopeDiculous's ROOTED TBeezy!
NickWarner said:
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
Click to expand...
Click to collapse
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
When you say checker what do you mean? How did I check my IP?
I just browsed to http://whatismyip.com
I pinged the different sites via the terminal emulator.
nbdysreal said:
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
Click to expand...
Click to collapse
Ok, when I'm on LTE, I do indeed get a public, routable IPv6 address. Using http://whatismyipv6.net on the phone, I can both see the address and traceroute back to it. Awesome.
On 3G, going back to the same site shows me that I only have an IPv4 address. It's a non-routable 10.0.0.0 address that gets NAT'd to a 166.250.0.0 address on the outside.
Ok, so, I have an OpenVPN setup at home, and I'm connected to it with my phone. I've been using VPNs for years and based on my previous experiences, I have a thought, and a couple questions...
Does every single packet go out through the VPN or only the ones destined for an IP on the private subnet? If it indeed passes every packet over the VPN (as with others I've used), why couldn't one just tether it after that? Would all data not then go over AT&Ts network and out to the internet via my home connection?
I've actually been musing about this for a while, but never bothered to actually connect my phone to my home VPN until now to even think about trying it.
Anybody have any unique insight on this?
N0ctrnl said:
Ok, so, I have an OpenVPN setup at home, and I'm connected to it with my phone. I've been using VPNs for years and based on my previous experiences, I have a thought, and a couple questions...
Does every single packet go out through the VPN or only the ones destined for an IP on the private subnet? If it indeed passes every packet over the VPN (as with others I've used), why couldn't one just tether it after that? Would all data not then go over AT&Ts network and out to the internet via my home connection?
I've actually been musing about this for a while, but never bothered to actually connect my phone to my home VPN until now to even think about trying it.
Anybody have any unique insight on this?
Click to expand...
Click to collapse
It entirely depends on how your VPN is set up. You can set up a VPN that will require all traffic to be routed through the VPN, or you can set up a VPN to only route traffic destined for that internal network to be sent over VPN.
And there's no reason you couldn't do that. If they are indeed detecting tethering by the content of data, you could set a VPN to pass all traffic through the VPN, and encrypt it so that they would never know what data was actually being sent. The biggest thing to be aware of is speed. If you are passing all traffic through VPN, your internet speed will immediately be reduced to the maximum speed your home internet connection can upload data. So if your home internet is 1 Mbps up, then your max speed is going to be 1 Mbps up now because you have to wait for that system to send the data along (plus overheads for encryption and processing of data, etc).
AJerman said:
It entirely depends on how your VPN is set up. You can set up a VPN that will require all traffic to be routed through the VPN, or you can set up a VPN to only route traffic destined for that internal network to be sent over VPN.
And there's no reason you couldn't do that. If they are indeed detecting tethering by the content of data, you could set a VPN to pass all traffic through the VPN, and encrypt it so that they would never know what data was actually being sent. The biggest thing to be aware of is speed. If you are passing all traffic through VPN, your internet speed will immediately be reduced to the maximum speed your home internet connection can upload data. So if your home internet is 1 Mbps up, then your max speed is going to be 1 Mbps up now because you have to wait for that system to send the data along (plus overheads for encryption and processing of data, etc).
Click to expand...
Click to collapse
Yeah, I fully understand the performance penalties of pushing all data through a VPN. Really, I only tether my phone down at my workshop to update orders and print shipping labels. It's about 200MB a week, and I could do it over dialup if I had one. Not an issue at all.
Thanks a bunch for your thoughts. It's pretty much what I thought. I'll just have to brush up on my OpenVPN knowledge and see if I can make sure it's all routed over the VPN.
Note: Consequently, I just got a text message from AT&T letting me know I'd automatically been switched over to a tethering plan since I was still tethering. The rub here is I have not tethered my phone a single time in the last 3 months! I actually have a 2GB plan on my old Captivate that I've been using. I called into AT&T and the lady I got was really cool. She said there must be something triggering the tethering alert on their side and she filed an extension for me so I wouldn't get switched over automatically.
So, I don't know what AT&T is really using to detect tethering, but it's indeed throwing out false positives. I've also only used 809MB since the beginning of my billing cycle (November 21), so I doubt very much that it's excessive data usage. I use some interesting things like wifi connected file managers and remote web desktop, but surely those don't trigger it (?).
Ok, so, I just did a test using whatismyip.com. It shows my wifi gateway here at work when using wifi with the VPN on, and it shows the AT&T IP when connected with wifi off. So, that shoots the idea that all traffic will go over the VPN by default when connected. I guess I'm going to have to dig a little deeper to get it working that way.
The "Redirect Gateway" option in the VPN settings seems to work perfectly. I'll keep testing and see what I can come up with as far as a tether goes!
Hi,
It seems that my 1S have a wifi issue.
I can successfully connect to a wifi network, but every 2-3 sec signal is lost, then the wifi icon in the status bar disappears, then it reappears and reconnect and so on.
I am running an unlocked german tmobile (from ebay), SW version 1.77.111.5
Is someone else having the same issue?
I dont have a device which is in that connect-disconnect loop, but it does not hold onto the Wifi signal, it seems to want to fall back to using 3G/HSDPA if it can, and only after a few mins of data on the 3G/HSDPA connection does it attempt to connect to Wifi.
Does you Wifi AP broadcast its SSID? Are there many devices on the same Wifi channel as the one you are using? Use Wifi-Analyser to find out.
pzboyz said:
I dont have a device which is in that connect-disconnect loop, but it does not hold onto the Wifi signal, it seems to want to fall back to using 3G/HSDPA if it can, and only after a few mins of data on the 3G/HSDPA connection does it attempt to connect to Wifi.
Does you Wifi AP broadcast its SSID? Are there many devices on the same Wifi channel as the one you are using? Use Wifi-Analyser to find out.
Click to expand...
Click to collapse
yes the ap broadcasts its SSID
As for WIFI channel, I'll check it out
Yea I get problem at work I think its more of a router issue cause at my house it stays connected to my WiFi all day
Sent from my HTC VLE_U using XDA
jguedj said:
Hi,
It seems that my 1S have a wifi issue.
I can successfully connect to a wifi network, but every 2-3 sec signal is lost, then the wifi icon in the status bar disappears, then it reappears and reconnect and so on.
I am running an unlocked german tmobile (from ebay), SW version 1.77.111.5
Is someone else having the same issue?
Click to expand...
Click to collapse
I'm having same issue - anyone found a solution.
It is really annoying, as quite often when I go to refresh email/facebook/twitter/ etc its says cannot update (or whatever app error), but if I wait a few moments again, it works. Really annoying when playing Draw Something, as it interrupts the game!
Any ideas - is it phone, or is it something on my router??
M
I was having this exact same issue. I went into settings, Wi-Fi, Menu, Advanced, and checked the "Best Wi-Fi performance" option and ever since I have had no problems.
jguedj said:
Hi,
It seems that my 1S have a wifi issue.
I can successfully connect to a wifi network, but every 2-3 sec signal is lost, then the wifi icon in the status bar disappears, then it reappears and reconnect and so on.
I am running an unlocked german tmobile (from ebay), SW version 1.77.111.5
Is someone else having the same issue?
Click to expand...
Click to collapse
Ok i think i had the same issue and i read in some threads around and you can try this:
1 - Connect to your wireless network but in settings disable DHCP and assign an manual IP (and you can disable the "best WiFi performance" because it drain lots of battery.
2 - Take out the SIM cover and pull up with care the contact pins for better connection with cover
Now i have a strong wifi signal without drops, before this i was thinking in return back my 1S but not now.
Sorry my bad English
If i help hit the "Thanks"
MRKikas said:
Ok i think i had the same issue and i read in some threads around and you can try this:
1 - Connect to your wireless network but in settings disable DHCP and assign an manual IP (and you can disable the "best WiFi performance" because it drain lots of battery.
2 - Take out the SIM cover and pull up with care the contact pins for better connection with cover
Now i have a strong wifi signal without drops, before this i was thinking in return back my 1S but not now.
Sorry my bad English
If i help hit the "Thanks"
Click to expand...
Click to collapse
Cannot find manual settings for ip. Please can someone direct me...
Sent from my HTC One S using XDA
Android_Mark said:
Cannot find manual settings for ip. Please can someone direct me...
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
First select "forget Network " then select your Network again, then bellow the password field select the manual configuration...
Sent from my HTC One S using xda premium
MRKikas said:
First select "forget Network " then select your Network again, then bellow the password field select the manual configuration...
Click to expand...
Click to collapse
I decided to attempt this manual configuration as well...and it works great! Very fast login, and my network speed even seems quicker (although it probably isn't, but who knows)?
But I had a few problems along the way, but managed to fix them. Here is what you need to do:
First, before you do this, you need to use any network info app to see what your wifi router gateway is. You can pick an IP number based on that number... [Also, while it is unlikely anyone did this, you should confirm that the router doesn't do any MAC filtering (this just means the router will only connect with specific devices based on their wifi radio unique ID number... it's a overzealous way to prevent someone hacking your router and it prevents any non-authorized device from associating with it).]
Once you get that info, change the setting under wifi connect from DHCP to "Static", and below this, enter the gateway and a IP number based on your gateway... Most routers have NAT configurations that allow ~100 or 255 devices, like 192.68.X.2 thru 192.68.X.255 (or 10.1.X.2 thru 10.1.X.255) where the IP number where X=1 is typically the gateway. So just pick a number where the last number is between ~10 and 50 (just in case your router hasn't allotted the full 255 addresses). This is a good range to choose from because if your router has DHCP on (which is typical), your household probably does not have more than 10 or 11 devices connected at any given time....so you are picking an IP address at the end of this range.... So for instance, if your gateway is 192.68.1.1, pick a static IP address of 192.68.1.11 or 192.68.1.15.
Below this enter "24" for Network Prefix Length.
Below this, it has boxes for DNS servers. I ran into some problems here. I figured that since my wireless router has DNS servers already configured in its settings, I could skip this (it lets you hit connect without entering then). You can try this, and it may work (depending on your router/setup), but when I left them blank, I noticed frequent reconnections and no signal really at all.
In my case I had to enter DNS server addresses. I already had purchased an app called "Set DNS Pro" (there is a free version though) so I used that to select publicly available DNS servers. If you don't want to use the app, you can enter Google's DNS servers, 8.8.8.8 and 8.8.4.4, or check with your ISP to use theirs (which they prefer because it is easier to keep track of or control your web browsing).
So my takeaway from this was that if you do not enter DNS, you might have problems.
Sent from my HTC One-S (rooted), stock ROM