Related
Anyone try the IPv6 Beta for ICS Nexus S? They have IPv6 enabled on 3G now.
https://sites.google.com/site/tmoipv6/lg-mytouch
Didn't work for me. Lost data.
I set up the apn for it, still waiting on the confirmation from t-mobile saying they've provisioned my number for use of ipv6.
dls5375 said:
Didn't work for me. Lost data.
Click to expand...
Click to collapse
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
its not working for me either. ive been exchanging emails with a person from that tmobile beta program, and he has a theory why its not working for me, custom rom. im on cm9. cm9 might not include the correct RIL files. i will try with a stock rom later on.
elgato99 said:
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
Click to expand...
Click to collapse
I set it up the way the instructions said to, rebooted and lost my data connection. It came back when I restored default.
IPv6 works fine for me with the stock Nexus S IML74K firmware, both with the special beta APN and the standard epc.tmobile.com APN (which is IPv6-enabled in the Bay Area). I did some reading on the topic last night for a friend, and it does look like you need support from the cellular radio for IPv6 to work correctly (for Android, I assume that means both baseband and RIL).
Apart from just doing it, what are the advantages of doing it?
mobilehavoc said:
Apart from just doing it, what are the advantages of doing it?
Click to expand...
Click to collapse
Fair question.
To people with mobile phones, the benefits are real public IPv6 addresses that allow for the bidirection flow of traffic. Read -- inbound connections... can have a web server or ssh server on your phone... A phone now becomes a real node on the real Internet, not a "mobile web" experience. Actually, each mobile phone is assigned 2^64 IPv6 addresses... that is a codified standard (yes, there are a lot of IPv6 addresses, no i dont think this a bright, but it is not actually a problem). There is no NAT from IPv6 to IPv6 addresses. But, other than that, not a whole lot is different from a user perspective. One can wax poetic about re-establishment of the internet's end to end principle, or how IPv6 is going to help battery life... but it gets kinda hand wavy. This is why IPv6 has been around for 10+ years without much traction.
The real benefit i see is to the mobile network providers, or Internet in general. Mobile devices are growing at a very high rate and there is just not enough IPv4 addresses to go around. Internet wide, IPv4 is pretty much exhausted.
I thought this article had some interesting pointers http://tech.slashdot.org/story/12/01/13/2348206/ipv6-only-is-becoming-viable
And, Facebook, Google, Bing, Yahoo ... are all turning on IPv6 for good in June. On the Internet, IPv6 is a pretty big deal in terms of how data flows through the tubes.... But, ideally, plane old joes dont have to care about IPv6. It should just work.
Here is some info on the World IPv6 launch day http://www.worldipv6launch.org/
Thanks. I noticed on the site they say P2P services like Skype won't work with IPv6 and there's obviously going to be some compatibility issues. I'm excited to try it out but at the same time I don't want to break apps or functionality. Guessing by this fall people will adopting it more and there'll be less breaks.
Right, some technologies are going to evolve quicker than others. The slashdot article had a link to a list of apps that work and dont work, i think it said 85% work fine... but a few fail. In any event, for this beta, switching between the IPv4 APN and the IPv6 APN is pretty easy (3 taps). I think one of the goals is to create an early adopter critical mass to find the broken things, complain, and get them fixed.
Here is another interesting link about getting the apps cleaned up http://www.gossamer-threads.com/lists/nsp/ipv6/32908
And, if you really want to go deep, there is this code which fixes the broken apps by doing translation on the phone from IPv4 to IPv6
http://code.google.com/p/android-clat/
Works fine for me....CM9 Euroskank kang and the Trinity t132 kernel. The lack of mms support makes it a non daily use apn for me..(kids, grandparents, etc...lots o' pictures)...but otherwise...good to go here...
working here now too. cm9 kang and trinity t144. i did have to flash the newest radio then let it sit there for a bit before it connected to data for the first time. now it connects quick every time. ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
mobilehavoc said:
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
Click to expand...
Click to collapse
syncs here just fine with blue bars.
simms22 said:
syncs here just fine with blue bars.
Click to expand...
Click to collapse
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
I tried it again and it worked this time with the blue bars and sync using the scpcf000 APN. Wonder why it didn't work before? Wonder if different towers/regions have issues because I was travelling when it wasn't working. Who knows.
I would keep it but no MMS is a bummer - if there were some practical advantage to using IPV6 right now I'd stick with it but there doesn't seem to be. Yet.
mobilehavoc said:
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
Click to expand...
Click to collapse
epc-scpcf000.t-mobile.com
simms22 said:
ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
Click to expand...
Click to collapse
Yeah, no Internet connection on my laptop when I try to tether either. It looks like Android's tethering infrastructure isn't IPv6-aware yet -- the laptop isn't picking up an IPv6 address, and the phone doesn't have an IPv4 address, so it's not capable of routing IPv4 traffic to the Internet.
That said, even if Android were to grow IPv6-aware tethering, providing Internet access is going to be a problem. I can see four possible approaches:
(1) The phone assigns IPv4 addresses to tethered devices (as it does now), and implements NAT46 to translate that traffic into IPv6 traffic to send upstream. I don't know of any NAT46 implementations, though, never mind any ones suitable for a phone.
(2) The phone assigns IPv6 unique local addresses to tethered devices, and implements NAT66 to push that traffic upstream. (Basically, this is like the current tethering setup, except with IPv6 everywhere instead of IPv4.) Highly experimental NAT66 standards and implementations exist, but their very existence seems to be controversial (one of the original ideas behind IPv6 was to have enough address space to not have to use NAT in the first place).
(3) The cell provider assigns a /64 or larger block of globally-routable IPv6 addresses to the phone, and the phone assigns those addresses to tethered devices. (This is the approach fixed-line broadband providers are taking.) As far as I know, though, there isn't a standardized way to hand out prefixes (other than DHCPv6, which people don't seem to like either), and of course, this requires carrier involvement, with implications for everyone who wants to tether without a carrier-approved tethering plan.
(4) The cell provider assigns an IPv4 address (public or private) to the phone, and tethered clients use the existing IPv4 tethering infrastructure. This requires no changes on our end (it'd work right now on carriers that provide dual-stack access), but T-Mobile has apparently decided to assign IPv6 addresses only and use NAT64/DNS64 to provide access to the IPv4 Internet, so this won't work for us.
I found this article to be well written and informative for IPv6 on ICS http://www.androidpolice.com/2012/0...ere-is-what-it-all-means-and-yes-no-more-nat/
http://dan.drown.org/android/clat/
I tried this code out. It is pretty cool since it allows some additional functionality by doing a NAT from IPv4 to IPv6 locally on the phone. Skype and a few other apps that require IPv4 now work while they did not work before.
I have a corporate intranet site I need to access from my phone (it's a SSL site with a port - ie https://example.com:1234/). Had no issues getting to it on my N4 using the stock browser, FireFox and Chrome.
Have tried both FireFox and Chrome on my N5 and I keep getting Server Not Found error on both browsers. Pop the SIM back in my N4 and it comes right up.
Have tried the 'Request Desktop Site' on Chrome and FireFox as well without success.
Chrome reports a ERR_TUNNEL_CONNECTION_FAILED error.
As an update, I have found that I can access the page when connected to a wi-fi network, but not when on AT&T cell network.
Intranet=internal network. If it's reachable from an outside network it isn't intranet. FYI
Sent from my Nexus 5
Pirateghost said:
Intranet=internal network. If it's reachable from an outside network it isn't intranet. FYI
Sent from my Nexus 5
Click to expand...
Click to collapse
Yep. Sorry. The keys here are the non-standard port and the fact that I can access the site on any wi-fi network but for some reason not AT&T's cell network on my N5.
I am going to dig out my N4 and see if there is something different in the AT&T network settings between the two devices next. Was hoping that rooting might help (the N4 was rooted), but that didn't work either.
Anyone working on a custom 4.3 ROM ....
Success!
The N4 did not have a proxy set up in the APN settings, but the N5 did. Deleting it fixed the problem.
Sorry. My former boss used to keep calling our website an intranet, and he refused to acknowledge the difference. Lol. It became a pet peeve of mine. Apologies for interrupting.
Sent from my Nexus 5
So I was trying a trick that user greatlands posted on the Oneplus forums about being able to boost your LTE speeds by changing what the radio searches for. This was through the *#*#4636#*#* phone info area and selecting the radio bands. Good news is i've never seen speeds like this before. the bad news is that i fiddled with it some more and now i dont have roaming data. I didnt have MMS either though LTE anymore but that was fixed by using hangouts sadly. I switched from davlik to ART runtime then back to Davlik, but nothing seems to work with the Roaming Data.
I've included some screens of the pertinent settings and maybe you can help me.
In the screenshots Andriod tuner says that i'm connected to roaming but have no data connection.
I included the Speed test pic to show there is external IP, but no internal IP. is that normal?
Also included my APNs. Should there be that many? it seems excessive.
The reason why roaming data is important to me is that i work on a riverboat and am in the boonies most of the time, or some small city with roaming. i can do wifi on the boat but to do picture messages i need roaming. Please help.
kurtmintz said:
So I was trying a trick that user greatlands posted on the Oneplus forums about being able to boost your LTE speeds by changing what the radio searches for. This was through the *#*#4636#*#* phone info area and selecting the radio bands. Good news is i've never seen speeds like this before. the bad news is that i fiddled with it some more and now i dont have roaming data. I didnt have MMS either though LTE anymore but that was fixed by using hangouts sadly. I switched from davlik to ART runtime then back to Davlik, but nothing seems to work with the Roaming Data.
I've included some screens of the pertinent settings and maybe you can help me.
In the screenshots Andriod tuner says that i'm connected to roaming but have no data connection.
I included the Speed test pic to show there is external IP, but no internal IP. is that normal?
Also included my APNs. Should there be that many? it seems excessive.
The reason why roaming data is important to me is that i work on a riverboat and am in the boonies most of the time, or some small city with roaming. i can do wifi on the boat but to do picture messages i need roaming. Please help.
Click to expand...
Click to collapse
Holy balls. I fixed it. Not a bug. I dont know if these settings i switched it to are pertinent, but i fiddled around and fixed it.
cellinfolistrat=0
(it should SAY this after)
Turn ON IMS registration
Turn ON sms
Turn ON lte Ram dumb
Toggle dns Check not allowed.
then hit top right and enable data. data comes through now. False alarm
Hoping someone can help. I have a Nexus 5 on the AT&T network. Been using it without issue since Halloween 2014. All of a sudden, the past couple of days, I'm having some issues with MMS messages. I started a new group message and only one person received it. I haven't been able to text pictures to people. And today I have been receiving notification stating "Can't download MMS - check your APN settings". I can send regular one on one text messages just fine and sometimes group messages do go through. Sometimes not. Pictures don't seem to be going through at all.
Nothing has changed on my phone and I definitely haven't touched the APN settings. I'm using the "phone" APN for AT&T with all of the correct settings founds online.
I had a friend who's using a 2014 Moto X Pure Edition send me his APN (also AT&T) and he has one called "nxtgenphone" but all of the other settings are identical to the "phone" APN. I've tried added a new APN for "nxtgenphone" but when I select it and then reboot, the phone goes back to the "phone" APN automatically.
Anyone know what could be going on? Is it an AT&T issue? My issue? Other? I'm not sure what to do or check at this point.
Again, everything has worked just fine for months. This is a recent issue the past couple of days.
Thanks!
Bronson
I had a similar issue with Net10. What fixed it for me was moving my active APN to be the first APN.
I just noticed I have the same problem. I am on AT&T with my N5 running 5.1(D) also, my APN it set to ATT Phone, and all settings are confirmed. googled the problem and the "google messenger" app seems to be buggy. It has been updated recently and I think its now more messed up than before...
If on LTE and WIFI I have mms problems
If on LTE, 3g or H only mms goes through!!!
If I use "hangouts" (which I hate becuase if you search for a contact, it puts your google+ contacts up 1st) things seem to work fine in all forms of connection LTE/WIFI/3G/H etc....
So till they fix the "Google Messenger" App, I am forced to use "Hangouts" as it is more reliable for now
I'm on AT&T & the last time I tried the "Google Messenger" App a couple of weeks ago, I had trouble with MMS. I run CM and just went back to the CM messanger, and it was fine. So it seems there is an issue with AT&T & the Google Messenger app that didn't exist before. I wonder if it is specific to the N5 or on other phones.
Well here's another funky thing to add... As stated above I have problems with sending and receiving mms with Google's messenger application at "home" but not with Google's hangout application at "home" where I first noticed the problem. Well while I was at "work" today about 15 miles away from home. I tried Google's messenger application and it worked!!!
So I am now thinking it has something to do with AT&T tower at my home location and Google's messenger application. Since Google's hangout works when I am "home" and away...
Now what???
Sent from my Nexus 5 using XDA Premium HD app
Another update to my dilemma, when at "home" and I turn my "WIFI" off and restart the phone. Things seem to work, as I look more and more into this problem I am having with sending and receiving mms on AT&T. I am starting to see a pattern that Google's Messenger application may have an issue where it is suppose to "Turn Off" Wifi use cellular data to send and receive the mms and then "Turn On" wifi after it is done with the mms process.... But this does not explain why things work while I am not away from my "Home" location!!!!
Getting to the root of my problem!!!! FIXED!!!!!!
I am starting to think that the MMS problem is not with AT&T and the google messenger app, or 5.1(D), or my APN setting!!!!
But with my wifi router at home!!!
After more reading up on this and also the fact that I have "No" problems sending or receiving MMS while "Away" from home using another WIFI source or with WIFI off. I was starting to think if the problem was "Caused" by my wifi router a linksys wrt54g running dd-wrt??? So what I did was to connect to a Public Wifi I have outside of my house and I was able to send and receive MMS without any problems!!!!
Just recently I had to change a setting on my router to allow my xbox360 to download some content.
That setting was to "Allow - UPnP service" I went back into the router, reversed my settings and rebooted the router, made sure my phone was connected to the "home" wifi and checked my IP address to see if it was connected to my ISP. Attemped to send a MMS and GUESS WHAT!!!! IT WENT TROUGH!!!!! for a short period of time then it stoped again... I went back into the routers setup page and also turned off the STATIC IP I set for the phone, no luck. Then I remembered I have OpenDNS and my router was using the OPENDNS DNS addresses. went to my opendns dashboard and looked at what was blocked by them and found that that MMS proxy site "proxy.mobile.att.net" was "Blocked" by openDNS. So I put that domain in the "Never Block" list and rebooted the router. So far I am able to send and recieve MMS again when I am on my Home network... This still does not explain again why "hangouts" works with all of setting I have chenged before coming to this conclusion. Unless Google Hangouts is not using the APN and uses some other form of traffic to the net???? Also Google's Messenger app is also using DATA via whatever WIFI connection. Thus is my OPENDNS was blocking the proxy it was not going through!!!!
I AM FIXED for now!!!!! :good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
So all of you who have problems with Google's Messenger APP sending and/or receiving MMS. Yes check to make sure your APN settings are correct. If your are on WIFI, disconnect WIFI attempt to send and receive a MMS. If it goes through when your WIFI Connection is off, but cannot if your connected to WIFI. Then go into your routers setup page and see if UPnP is "ON" or "OFF". When I turned my "UPnP to OFF" and make sure your phone is not assigned a static
IP.... If your using a OpenDNS filter/Blocker check to see if its not blocking the MMS Proxy!!! Lets hope this is it!!!!
Holy crap, thank you for this!! I've had this issue pop up over the last few days and couldn't for the life of me figure out what was wrong. It seems that un-blocking the proxy did the trick for me, too. I took it one step further, though, and whitelisted the whole att.net domain.
Oddly enough, I noticed that with the domain un-blocked, I could not resolve proxy.mobile.att.net on my desktop. So our phones must know to hand-off to the wireless network if that happens. But with the site "blocked," it WAS being resolved, which is probably what confused the heck out things.
Anyway .. thanks again. Yes, I hit the button.
Pretty much what it says on the can. If I'm in a voice call and flip over to email, or a browser, all I get is "ERR_INTERNET_DISCONNECTED" and even apps like third party file browsers(Astro) that assume network connectivity to load ads or the like hang up because there's no data network available during voice calls. Once I end the voice call the internet connectivity comes right back and works fine to load the same sites or use the same apps that I wasn't able to use before.
This is a black Pixel 2 XL, unlocked, ordered directly through Google, with a Sprint SIM that I double-checked against the online discussions for compatibility. The device works fine in most other ways. The activation was clean and everything else seems to work.
When I'm at home and on my Wi-Fi I can use both voice and data to multitask, so this is something in how it's working with the carrier. I've tried the LTE(Preferred), 3G, and Global network types in the "Preferred Network Type" section of the "Mobile Network" options for my carrier.
I've looked through all the settings and can't see anything like "enhanced calling" which was the solution with the single-radio Samsung devices. Any ideas how to get the Pixel 2 to share the radio during voice calls?
Thanks,
Steven
I don't think Sprint has the backend to support VoIP and LTE at the same time. So that's probably just a network limitation.
Sprint has one antenna so there's.o voice and data at the same time like GSM. Sprint is CDMA been like that since 2014
smerr612 said:
Pretty much what it says on the can. If I'm in a voice call and flip over to email, or a browser, all I get is "ERR_INTERNET_DISCONNECTED" and even apps like third party file browsers(Astro) that assume network connectivity to load ads or the like hang up because there's no data network available during voice calls. Once I end the voice call the internet connectivity comes right back and works fine to load the same sites or use the same apps that I wasn't able to use before.
This is a black Pixel 2 XL, unlocked, ordered directly through Google, with a Sprint SIM that I double-checked against the online discussions for compatibility. The device works fine in most other ways. The activation was clean and everything else seems to work.
When I'm at home and on my Wi-Fi I can use both voice and data to multitask, so this is something in how it's working with the carrier. I've tried the LTE(Preferred), 3G, and Global network types in the "Preferred Network Type" section of the "Mobile Network" options for my carrier.
I've looked through all the settings and can't see anything like "enhanced calling" which was the solution with the single-radio Samsung devices. Any ideas how to get the Pixel 2 to share the radio during voice calls?
Thanks,
Steven
Click to expand...
Click to collapse
I actually have this issue on VZW! Has anyone seen this on VZW? Also, is there a setting to VoLTE? This is stock Android on a VZW Pixel.
Thanks!
-Sofie
Hello. I have a Google store bought Pixel 2. I just placed a call to my voicemail and was able to surf the web on my browser at the same time. It works both on WiFi and with WiFi switched off.
SweetSofie said:
I actually have this issue on VZW! Has anyone seen this on VZW? Also, is there a setting to VoLTE? This is stock Android on a VZW Pixel.
Thanks!
-Sofie
Click to expand...
Click to collapse
Check to see if "advanced calling" is enabled. Settings/ Network & Internet/ Mobile network/ advanced.
robocuff said:
Check to see if "advanced calling" is enabled. Settings/ Network & Internet/ Mobile network/ advanced.
Click to expand...
Click to collapse
It is on, but it also seemed to stop having the issue on it's own. I wonder if it was a carrier issue?
err_internet_disconnected
This error basically means that your browser is unable to establish internet connection to the host. The primary reason for getting this error is because your computer itself is not connected to the internet. This particular error messageerr_internet_disconnected belongs to Google Chrome and there are various reasons leading to this error, includes computer issue, or web server issue or Network setting , Internet connections, etc. It doesn't matter, you can take the appropriate solution to fix it. The following article can gives you some specific advice to solve this issue.
Try a different web browser
Check your cables
Check your WiFi connection
Check Your LAN Settings
Delete WLAN Profiles
Disable Antivirus and Firewall
Restart Your Router