Wifi - obtaining ip.. [Workaround] - Galaxy S I9000 General

I just wanted to share a "fix" that i found recently to avoid this problem.
I use the app WiFi Static, this app sets several static ip profiles (you have to add them) and switches to the right one automatically, avoiding the obtaining ip address problem, while allowing you to connect to several networks using a static ip.
Sometimes it takes a little longer to make the switch (in busy hot spots) but still works. I've only done some tests but for me this app was a great solution.
I encourage you to try it since for me this was the major problem i had with my cell.
Hope this helps others,
Cheers.
Edit: I'm very thankful for the "Thank you" but if you guys could also leave a comment i think this thread would help more people. Thnks

Good thread!
I also suggested Wifi Static several times before.
It worked great on Android OS v2.1 and v2.2, but on v2.2.1 I had troubles to automatically change the IP address.
Now I'm using IP Manager, with this app you have to make a widget/icon on the home screen and manually change the IP by taping on a profile (static/dynamic).
For me this app is better than Wifi Static.
I had the WiFi "error" message problem upon switching WiFi on in some places.
If I want to connect to a public WiFi network (with a dynamic IP) I first need to select a static IP profile from the list (so the WiFi is turned on thru this app) and then the dynamic IP profile, else there is a great chance I could get the WiFi "error" message after trying to connect for several minutes.
Hope this helped anybody!

I (luckily) rarely get that error,
but thanks for leaving here another option,if anyone has your problem they know how to workaround it now.
Thanks for the reply.

thanks for ur fix

lulz - just make fix permmisions in advanced cwm menu =) if not i will hopefully find the thread where i mentioned the proper fix and paste it here

and here it is - http://forum.xda-developers.com/showpost.php?p=13235272&postcount=19

Thanks somator,
this workaround was directed more for those of us that don't feel comfortable with flashing.
But still thanks for the link.
Sent from my GT-I9000 using XDA Premium App

so stick to fix permissions in cwm advanced this should work also and does not include flashing
this bug does not apear on nonrooted phones so anyone having this issue must be rooted -> flashed something already so one way flash my file other way try with advanced menu
your workaround is worthless basicly, will make it connect but every time youll have to set the connection up its like buying a ferrari to push it down the streets coz you dont want the engine to be used =)

Ok, it's weird because this happens to me and my 2.2 rom it's completely stock, no root or flashing involved.
I'm sticking with my fix since it works without any problem so for me no need to do anything else.
Sent from my GT-I9000 using XDA Premium App

if it is stuck on "obtaining ip adress" its most likley the system files are 'messed up' like i like to say - in this case it is some permissions problem but hey free world stick to yours =) goodday sir ;d

$omator said:
this bug does not apear on nonrooted phones so anyone having this issue must be rooted -> flashed something already so one way flash my file other way try with advanced menu
your workaround is worthless basicly, will make it connect but every time youll have to set the connection up its like buying a ferrari to push it down the streets coz you dont want the engine to be used =)
Click to expand...
Click to collapse
FALSE. My phone has never been flashed before nor has it been rooted and I have the "Obtaining IP address" bug. After doing some google search, it looks to me that this is a known problem.
Right now I'm just using the AllShare workaround which has worked well for me so far.
Solid_Snake.Pt said:
I just wanted to share a "fix" that i found recently to avoid this problem.
I use the app WiFi Static, this app sets several static ip profiles (you have to add them) and switches to the right one automatically, avoiding the obtaining ip address problem, while allowing you to connect to several networks using a static ip.
Sometimes it takes a little longer to make the switch (in busy hot spots) but still works. I've only done some tests but for me this app was a great solution.
I encourage you to try it since for me this was the major problem i had with my cell.
Hope this helps others,
Cheers.
Edit: I'm very thankful for the "Thank you" but if you guys could also leave a comment i think this thread would help more people. Thnks
Click to expand...
Click to collapse
I appreciate Snake Pit for your HELPFUL contribution. I'll try this in case I'll have trouble with the AllShare workaround.

Thanks for the support,
I also used allshare for a while (thanks for leaving that fix here) but it started to be annoying to turn on the app everytime i wanted to use the wifi.
This does everything automatically and I don't see any background service so it can't be using much mem.
Sent from my GT-I9000 using XDA Premium App

what stock fw do you use that produces such problem?

This is a screen with my firmware specifications.

Related

Captivate & 802.1x

I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.

[SOLVED] Wifi issues

Um, Hi. I'm pretty new to this. So I just flashed the froyo rom 6.0.2.1 yesterday, and it worked perfectly fine. I'm just wondering if the wifi is one of the known bugs to it, or is it just me experiencing it. Well the thing is, I'm trying to connect to my wifi, but it only says "obtaining IP address from ___________" or" scanning" and it just stays like that. Is there any settings that I have to change or is it a bug? Thanks =]
I have the same issue, and I believe it is a known bug. Mine will connect every now and then, but mostly not. You may want to disable your wifi if your battery starts dying too quickly. I know this doesn't solve your problem, but hope it helps to know that you aren't alone in your wifi woes.
Sent from my Liberty using XDA App
I got it fixed! Try looking up Hidden SSID Enabler from the Market, and first turn off your wifi. then the program on. then turn on the wifi. After that, put in your SSID. That should work.
Hopefully it works for everyone!
Credits to: @Attn1 and @Jambi
thatkidjoe said:
Um, Hi. I'm pretty new to this. So I just flashed the froyo rom 6.0.2.1 yesterday, and it worked perfectly fine. I'm just wondering if the wifi is one of the known bugs to it, or is it just me experiencing it. Well the thing is, I'm trying to connect to my wifi, but it only says "obtaining IP address from ___________" or" scanning" and it just stays like that. Is there any settings that I have to change or is it a bug? Thanks =]
Click to expand...
Click to collapse
Why didn't you ask this in the proper thread instead of creating a new one like a total noob?
bkmo said:
Why didn't you ask this in the proper thread instead of creating a new one like a total noob?
Click to expand...
Click to collapse
'Cause he said he's new to this. Give him a break. YOu come on here just to say that. If you don't like it being here, well no one made you enter the thread.
As for the Hidden SSID, I can confirm it works.

Wifi issues - most likely not the phones fault

I am having intermittent Wifi on my phone; but at work only. Everywhere works perfect without dropping the signal, but at work the signal drops once every 10 minutes and I have to toggle Wifi to get it back. It doesnt matter of I sit still or have the screen on or off, it always happens.
One thing to point out is that on my iphone I used to use WPA enterprise as security, but on this phone WPA doesn't work, only EAP security. Its the kind if network where you have to login with a username and pass.
Anyone else experiencing this?
Sent from my Atrix using XDA App
This is driving me nuts (as well as the many other things I have posted about. I have a feeling I need to head to a networking forum or something. Can anyone reccomend one?
Even with all the problems im having, I still prefer Android to iOS.
Sent from my MB860 using XDA App
Ok I've figured out where my wifi disconnects are coming from at work. It IS an Android issue so I'll keep posting it here. The problem is that my work needs to use a certificate from entrust.net in order for the wifi to connect and stay connected. I can connect to the network and have full internet access, but after a few minutes its as if the network checks my phone for the certificate, and when it can't find it, throws me offline. Now here's the annoying part. I went to entrust.net to look for the certificate I would need to put on my phone, and found that they offer 4 different certificates. I then looked on the phone at the bottom of settings>location & security and found, "manage trusted certificates". There was a big list of certifcates preloaded on the phone. And guess what? All 4 entrust certificates came pre-loaded on the Atrix. So the problem is not that the certificate is not on my phone, the problem is that I can not associate the certificate to my wifi profile for work.
There are even 2 options under the manage wifi connection that reference certifcates, but when I click them to try and load a certificate, it won't allow me to select anything. I'll post a screen shot of that at the end of this post. If it means anything, the iPhone 4 will auto-pull that certificate when trying to connect to my network here at work. As soon as you connect it will ask to accept the certificate. My work uses WPA Enterprise.
Screenshot: Oh yea.... I forgot, I can't find a single app that will screenshot on the Atrix. What a cool feature we are missing out on. Actually a very needed feature in my opinion.
Please help me or point me in the direction where I can find help. WPA enterprise is pretty common in the business world so someone has already come across this, I am sure.
Sent from my Atrix using XDA App
Android does not have native support for LEAP either. I went through a similar mess as you trying to get my Atrix to connect at work. I had to download the wifi advanced app in order to get a connection.
I'm sure you're already searching "WPA Enterprise Android". It may be worthwhile to see if there's a wifi app out there that could fix your problem.
I have that app and can add extra options yes, it still doesn't allow me to deal with the certificate problem though
Sent from my Atrix using XDA App

[Q] Able to connect to many different WiFi Networks except school ones

Hello all.
I can connect my Nexus 10 to my home wifi (password protected), my girlfriend's home wifi (password protected), and the wifi at public places (I've only tried ones without passwords so far). My only problem is when using my University's Wifi. They have one that you use with an account and password, and one that is free (though you need to sign in using an email via a website. Kinda like hotels).
This is surprising to me because I have a Galaxy Nexus running the same OS (4.2.1) and it can connect just fine. When my N10 tries to connect, it says "connecting" for a second or two, and then it just says "Saved" but never "connected" and it never shows a wifi connected symbol at the top right.
I have read multiple posts about wifi problems from 4.2 but couldn't find any specifically buggy wifi problems like this. Have any of you heard of this or a solution to it? Any help would be appreciated!
Have you tried a reboot? Also check to see if your frequency band is set to auto under advanced wifi settings.
Gotta love university security and logins... they can't leave stuff simple
Oh yes. I have rebooted many times and tried using auto, as well as both frequency bands separately.
Hmmm...are you on stock?
Yes I am. Stock on both my Gnex and N10.
I wonder if using a third party wireless manager would help. Search the PlayStore and try one or two. Before you do that, go into your normal WiFi settings and click "forget this network" on the university one.
Hi there,
I work at a University in the midlands and had the same/similar problem. It's to do with certificate revocation in Jellybean (and also the latest ios my colleague tells me). For example on my Nexus 10 I was able to see the network and obtain an ip address but the webpage where you login wouldn't redirect or load. I don't know what Uni you go to but we are advising people to give the IT dept a call and give them your mac address and they can create a fixed profile.
Hope this helps
I'll definitely try the third party app. As for telling the n10 to forget the WiFi, I tried that many times too
Well that's why I mentioned my gnexus because they're the same android versions so if it works on one it should on the N10. I actually work for tech support at my university and my boss couldn't figure it out or suggest a process like you described. Thanks, though!
yodasoja said:
I'll definitely try the third party app. As for telling the n10 to forget the WiFi, I tried that many times too
Well that's why I mentioned my gnexus because they're the same android versions so if it works on one it should on the N10. I actually work for tech support at my university and my boss couldn't figure it out or suggest a process like you described. Thanks, though!
Click to expand...
Click to collapse
Oh yeah you did mention your Galaxy Nexus, my bad! let us know how you get on with the third party app. You could try giving your N10 a static or reserved IP if you have access, as a workaround!
Hey guys,
I'm from France and had such trouble with my Motorola Milestone and my HTC HD2 (and friends too with Samsung Galaxy S2 and Sony Ericsson Xperia Active) with my school's network. If it's an Eduroam network, try Eduroam Fixer from PlayStore, it helped all of us except one Samsung Galaxy S2. Give it a try
https://play.google.com/store/apps/details?id=nl.luqq.eduroamfixer&hl=fr
I wish I could use that app, but it says I can't use it in my country (USA)
yodasoja said:
I wish I could use that app, but it says I can't use it in my country (USA)
Click to expand...
Click to collapse
Make sure you have the EAP set correctly and check if you need a phase 2 authentication. For example, here at UofM we use PEAP for eap and mchapv2 for the phase 2. If you don't have details like these, your tablet won't connect even if you have the proper login.
You will find them at the top of the page you use to login to a secure network.
Hope this helps!
Yes, that is exactly how the secure WiFi is set up at my University, too! What should I do in this case?
Edit: Nvm, Just noticed this was already tried
I had a similar issue with my One XL. It was a frequency issue. I switched it from 5ghz to auto and all was good.
Settings/WiFi/advanced/WiFi frequency band/auto.
Sent from my Nexus 10 using xda app-developers app
Okay so I found out that my N10 is able to connect to the exact same WiFi network when in another building. I believe there is just an issue connecting to the specific router used at a computer lab. Will update when/if a resolution arises for that lab.

Nexus 4 Wifi Issues - connects to router but no internet

Just want to know who else on XDA has a similar problem to me on the Nexus 4.
Recently moved country and took my Nexus 4 with me, got a data plan, no problems there. I was also was given the stock router for my ISP (Movistar) when taking out my broadband contract and my Nexus 4 is the only device that won't connect to wifi.
So here's what happens:
1) Network can be seen on the Android 4.2.2 Wifi Settings
2) I can connect, either by WPS or by entering the password, and Nexus 4 shows connected with indicator
3) Indicator instead of being the standard blue is grey, which seems to be no internet connection. I can get some access but at very, very slow speeds (about 9kbps)
The Nexus 4 is the only device in my house with the issue, no problems on PCs, iPads, etc.
Google have acknowledged this is a bug and there is a fix which involves root, but I don't want to root at the moment. Google also say it'll be fixed in the next update, but they've said that and we've seen 4.2.1 and 4.2.2 come out in the meantime.
Google Support also sent me a rubbish response to my questions about when it'll be fixed, telling me what Wifi is and how to turn it on and off..
So just want to know, are you having the similar issues with certain routers on 4.2.2 (stock)? I know I'm not the only one but I couldn't find any other threads.
Thanks!
I started having this same issue man! care to show me whats the root needing fix?
Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
There are a lot of fixes in the Android Development Section.
Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.
Thanks for the responses guys
kbeezie said:
Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.
Click to expand...
Click to collapse
Tried that I'm afraid :/ No luck. According to Google it is the fact "they have no drivers for that router" considering they will probably have a generic driver for the average user to connect whatever the router.
Sadly I've had to practically try everything to get it to work. Thanks so much for your response though!
Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
Hi! It's an annoying issue, I'm currently tethering through Mac to get it to work. The root fix does work but drains battery life a lot more (instead of 0.5% per hour drain it's 5%). If you want to look I'll pass the link, but wouldn't recommend it.
Thanks!
carmichaelalonso said:
Thanks for the responses guys
Tried that I'm afraid :/ No luck. According to Google it is the fact "they have no drivers for that router" considering they will probably have a generic driver for the average user to connect whatever the router.
Sadly I've had to practically try everything to get it to work. Thanks so much for your response though!
Hi! It's an annoying issue, I'm currently tethering through Mac to get it to work. The root fix does work but drains battery life a lot more (instead of 0.5% per hour drain it's 5%). If you want to look I'll pass the link, but wouldn't recommend it.
Thanks!
Click to expand...
Click to collapse
See if you're able to do a traceroute from within android when connect to the router to see where it's failing.
Mine got fixed by changing the routers channel, weird cos' no other thing connected had a problem, not even my sister's nexus 4
Sent from my Nexus 4 using xda app-developers app
kbeezie said:
See if you're able to do a traceroute from within android when connect to the router to see where it's failing.
Click to expand...
Click to collapse
Hi, tried this and have no problems. The only issue is it takes too long to complete, which is the 9kbps download issue I was having. I'll attach a screenshot of the traceroute if needed. Thanks for the reply, much appreciated!
And about changing routers, not possible at the moment. I've just moved abroad and have my old router somewhere too hard to find. Google are no help with this which is the problem, but if it persists in the next update I'll get a new router whatever the case.
It's strange since my iPad and all my other devices work with no problems!
Good luck, hope yours works now!
Sent from my Nexus 4 using xda app-developers app
my friend's phone also has this problem....
policeman0077 said:
my friend's phone also has this problem....
Click to expand...
Click to collapse
Yep it's a common problem I'm afraid which is obsolete in the eyes of Google and not a device defect...
Just to get an idea, what router models are you using? I'm on Movistar's stock router - ASL-2665 - common issue with this router. I've also heard big brand routers having similar problems, anyone got any problems with a particular router?
kbeezie said:
Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.
Click to expand...
Click to collapse
Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
I've been looking a bit lately and I've found this flashable fix if you're rooted, take a look and let me know how it goes!
http://techmell.net/android-tips/fix-wifi-issue-40065-nexus-4-7-android/
I've bought a wifi extender to fix this today, I'll see how this goes and may have to be the non-root fix...
I am very close to buying the Nexus 4 for my wife. If this WiFi issue intermittent or consistent?
-T
T-BoneFL said:
I am very close to buying the Nexus 4 for my wife. If this WiFi issue intermittent or consistent?
-T
Click to expand...
Click to collapse
The Nexus is a great phone, just a few odd issues which hopefully will be fixed.
This issue is persistent but dependant on the router. For example, my extender works perfectly whilst the main router doesn't - let me know what your router model is and I'll check to see if this will be common for your router
Sent from my Nexus 4 using xda app-developers app
carmichaelalonso said:
The Nexus is a great phone, just a few odd issues which hopefully will be fixed.
This issue is persistent but dependant on the router. For example, my extender works perfectly whilst the main router doesn't - let me know what your router model is and I'll check to see if this will be common for your router
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
I have the "BUFFALO AirStation HighPower N600 Gigabit Dual Band Wireless Router WZR-600DHP"
-T
T-BoneFL said:
Thanks!
I have the "BUFFALO AirStation HighPower N600 Gigabit Dual Band Wireless Router WZR-600DHP"
-T
Click to expand...
Click to collapse
Hi!
Taken a quick look and doesn't seem to be any problems with your router. What you can do is to purchase the device and test to see it works on WiFi.
If it works, you're good to go!
If not, try some troubleshooting, so change channels, IP address, or even just a reset of the router could work.
Still not working? You can try what I did and buy an extender, but that'll set you back a bit of money.
You could wait until this is fixed, which we don't know when yet, or if you can't fix it you have a return period on which you should get a refund from Google.
Let me know what you decide to do, personally I'd try it out since it's likely to work, but I would return if not. But the Nexus 4 is a great overall device for the price.
Hope this helps!
Sent from my Nexus 4 using xda app-developers app
OP, have you checked to see if this is an issue with the wifi access point of your router, or actually a routing issue?
To do this, set up ftp services on your computer or phone and login from the other device and copy a file from one to the other. If the bandwidth is good, your problem isn't with wifi but rather a routing issue that can likely be addressed in its settings.
Solutions Etcetera said:
OP, have you checked to see if this is an issue with the wifi access point of your router, or actually a routing issue?
To do this, set up ftp services on your computer or phone and login from the other device and copy a file from one to the other. If the bandwidth is good, your problem isn't with wifi but rather a routing issue that can likely be addressed in its settings.
Click to expand...
Click to collapse
Thanks for your reply!
I'm about certain this is to do with the router itself and not a routing issue, this is a common nexus4-my router problem and various other models.
I've adjusted every setting possible in the router settings to no avail, and all of my other devices which include other android devices work perfectly.
Sadly it seems to lie with a Qualcomm driver from what I've seen, and hopefully Google can fix in the next update
Sent from my Nexus 4 using xda app-developers app
If you don't bother to check if you have good throughput over your LAN, you'll never know whether this is a wifi issue or a routing issue.
Drivers talk to hardware, i.e. Your wifi chip. That is all local, and has nothing to do with the routing (Internet) part of your router. Without knowing where the actual issue lies, you're just guessing if a new wifi driver will help.
Solutions Etcetera said:
If you don't bother to check if you have good throughput over your LAN, you'll never know whether this is a wifi issue or a routing issue.
Drivers talk to hardware, i.e. Your wifi chip. That is all local, and has nothing to do with the routing (Internet) part of your router. Without knowing where the actual issue lies, you're just guessing if a new wifi driver will help.
Click to expand...
Click to collapse
Sorry, you seem to have misunderstood me and you're obviously making the assumption that I haven't already checked for routing issues.
As I said, my Nexus 4 is the only device in my house with this problem, all others work perfectly. From what I've gathered from these issues, it lies within the drivers of the phone.
WiFi works perfectly on every other router I've used with my N4, it's only my home router with the problem. It's a Movistar default router and other users have the same problems with this router (the brand is fairly unknown).
And I'm definitely not guessing that it's a driver issue - I've had this problem for over a month, I've tried everything I can: changing router settings, resetting, etc. So I doubt this is a routing issue but more an issue with the device, and from what I've read on other forums, this could be down to a Qualcomm driver issue.
Thanks for your help anyway!
Sent from my Nexus 4 using xda app-developers app
I am not assuming anything. Simple troubleshooting 101. You're not getting a decent Internet connection. Could be wifi or router. I merely offered a simple method for determining which one.
Don't know who you spoke with at Google, but first couple of support levels don't have the stones to try and solve these things. And while I have no doubt other folks with the same setup are also experiencing this issue and that Google has recorded this info, that doesn't mean that a workaround is impossible.

Categories

Resources