I'm not sure how many of you have this issue but I sure do and it is annoying the living crap out of me. The symptoms are as described:
YouTube does not work on my WiFi network with my DLINK DIR-655 router. I'm using a static IP setup and am not going to rework my whole network to accommodate what worked fine on the EVO LTE and all other HTC phones. I have tried changing some settings around BUT have ultimately failed in getting YouTube to work. The video will begin loading, but never actually play, and will eventually timeout with "Connection to server lost." Switching to 3G or my neighbor's WiFi connection works fine.
I have searched on Google and have came up with a few results of people having the same problem, but no fix. Now, the GS3 uses the Qualcomm S4 SoC, what I want to know is if this SOC includes WiFi. If so then it has to do with Samsung's software because the HTC EVO LTE uses the same SoC and it works fine with YouTube.
At any rate, I'm going to try and dig around in the framework and see what I can do because this is unacceptable. If anyone else has had this issue please chime in.
Perhaps have you tried changing the channel being broadcasted?
Youtube works fine for me on my G S III 16gb pebble blue. This includes in the browser [using chrome] and the youtube app.
Router: Dual Band 2.4Ghz and 5Ghz Belkin 750N
Works fine on mine also, Linksys E3000 here
I'm having the exact same issue...I'm using the IP that my Epic 4G was using now that it is turned off. Youtube app, mobile, and web versions will not play and I get that error message. My router is a Cisco Valet Plus with dd-wrt firmware. The problem seems to be the with static IPs. I set my phone to DHCP and it Youtube works with no problem
Weird... I have a GS3 32 gb, with a DIR-655 router and I have no issues at all with Youtube Vids while on Wifi. Try changing the channel as others suggested.
klownin816 said:
Weird... I have a GS3 32 gb, with a DIR-655 router and I have no issues at all with Youtube Vids while on Wifi. Try changing the channel as others suggested.
Click to expand...
Click to collapse
Static ip?
Static IP seems to be the cause
I'm on my office wireless with a static IP and am having trouble with youtube as well. Says 'Connection to server was lost'. It worked on my wireless at home on DHCP so I'll switch it to static when I get home and test somemore.
Anyone else using a static IP getting Youtube to work? Would be nice to know if this is the problem or not.
kangol69 said:
I'm on my office wireless with a static IP and am having trouble with youtube as well. Says 'Connection to server was lost'. It worked on my wireless at home on DHCP so I'll switch it to static when I get home and test somemore.
Anyone else using a static IP getting Youtube to work? Would be nice to know if this is the problem or not.
Click to expand...
Click to collapse
Mine is static and yeah the problem is there. I thought it was due to the type of router but it's looking more and more like static IP is the issue.
Are you setting the ip static on the S3 , or are you setting the dir-655 to reserve a specific ip for you S3's MAC address?
I have every device (my S3 included) on my network reserved on my dir-655 so the ip's don't change but all my devices "obtain ip automatically"
If you need someone to test let me know. I have a stock rooted sprint S3
Sent from my SPH-L710 using xda premium
This has been moved to general section.
Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?
This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?
C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7
Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).
I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.
Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?
Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence
First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app
bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.
strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.
Bump.
Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app
Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.
Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!
its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know
bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).
I did a clean flash, but cannot connect internet through wifi. There wasn't such problem before lollipop.
Other devices connect without problem.
Chrome says DNS_PROBE_FINISHED_NO_INTERNET
Mobile network works fine btw.
What might cause that?
halloga said:
I did a clean flash, but cannot connect internet through wifi. There wasn't such problem before lollipop.
Other devices connect without problem.
Chrome says DNS_PROBE_FINISHED_NO_INTERNET
Mobile network works fine btw.
What might cause that?
Click to expand...
Click to collapse
Is it happening with all WiFi networks that you are connected to? Because it seems related to the DNS configuration.
speedsys said:
Is it happening with all WiFi networks that you are connected to? Because it seems related to the DNS configuration.
Click to expand...
Click to collapse
No, only University's WiFi
I have the same, really annoying problem.
I use a local DNS to resolve my LAN name server, but the device on Android Lollipop never use the Local DNS and it ends with a 404.
I use "Fing" / "Ping and DNS" to do my network test, it says the hostname can't be resolved... and the DNS used is one on IPV6 (2a01:e00::1)
I have a lot of applications inside my private domain ( *.dk.lan ) managed by a bind9 / dnsmasq (I have tested both) server on Raspbian, and all was pretty good with Kitkat and lower (and on Mac OS / Linux )...
I have 8 devices, 5 on Lollipop with this problem and 3 on kitkat without it.
Some thread seems to appear on Internet about this kind of problem...
And, after investigation, it seems the Android Lollipop device use an Ipv6 DNS name resolver instead those send by the DHCP server...
If you have an idea... I'm listening !
About this problem, I've opened a issue on the Android tracker : https://code.google.com/p/android/issues/detail?id=79504
I've been investigating this issue and it's seems that it's a kind of problem on how the OS stores the DHCP parameters.
If you try to make static the same configuration in my case it takes a /20 (255.255.240.0) network like /29 (255.255.255.248) ..... and this doesn't happen if the network it's the ussual /24 (255.255.255.0)
Not fixed in 5.0.1
Finally fixed in 5.1
My 7th generation fire HD can't connect to my Nexus 6P's portable wifi hot-spot. It connects, but fails to acquire an IP address. Other devices have no problem. I've tried 2.4 and 5ghz. Security is WPA2 PSK.
go into wifi options and edit the connection to use a static ip and see if that works. You'll have to know the ip range the nexus 6p assigns.
I've used mine on my AT&T hotspot, mobley, and my pixel xl (on verizon OG GUDP) with no problems.
madsquabbles said:
go into wifi options and edit the connection to use a static ip and see if that works. You'll have to know the ip range the nexus 6p assigns.
I've used mine on my AT&T hotspot, mobley, and my pixel xl (on verizon OG GUDP) with no problems.
Click to expand...
Click to collapse
How do I discover what IP range it uses?
Nevermind. It seems to be android default: 192.168.43.0/24
192.168.43.1 as the gateway and 192.168.43.43 as the IP seems to have worked just fine. Unfortunately it doesn't remember those settings and I must enter them each time. I wonder why DHCP isn't working? >_<
At least it works. I'm going to have to do that frequently though. Thank you! ^_^
Dr3x1 said:
How do I discover what IP range it uses?
Nevermind. It seems to be android default: 192.168.43.0/24
192.168.43.1 as the gateway and 192.168.43.43 as the IP seems to have worked just fine. Unfortunately it doesn't remember those settings and I must enter them each time. I wonder why DHCP isn't working? >_<
At least it works. I'm going to have to do that frequently though. Thank you! ^_^
Click to expand...
Click to collapse
The reason is because Amazon has 'blocked' the use of that function so anytime your reboot, the settings to it are reset.
I own a RN3ProSE with latest MIUI and unfortunately UDP/IP TV streams are NOT possible in this, because UDP is disabled completely. I also heard this is by default on ALL MIUI ROMs (googleot for confirmation). So what about the A1 OS? Anyone tested Multicast UDP IP TV? Like you have with Telekom Entertain in Germany?
Thx and regards
Arangato
No one owning A1 and Telekom Entertain?
Really? No one out there?