Database Info

[Q] T-Mobile IPv6 Beta for Nexus S

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.

[Q] CM10 on Rogers, no LTE.

All right, so, I have tried everything I can think of, but nothing has worked, so I decided to try asking here. I am have been on the CM10 builds for about a week, and I am loving them. I never really liked sense, so an AOSP JB rom is great (aside from the battery life). Before CM10, I was on ViperXL, and LTE worked fine, but after switching to CM10 (or any other AOSP roms) it just stops working. I can get everything else, Edge, 3G, and HSPA, but LTE just won't work. Just a couple hours ago I did a wipe and a clean install of the October 3rd nightly, and I am still having the issue.
One thing I haven't tried is flashing a 4.0.3 rom, and then the CM10 rom, but the FAQ says that issue has been fixed so I doubt it would help.
Anyway, thanks in advance for the help!

Check your APN settings. These settings worked for me.
http://forum.xda-developers.com/showpost.php?p=19434188&postcount=2

I've had the exact same issue. I'm on Rogers too. I've double and triple checked the APN (ltemobile.apn) and it is definitely correct. I first noticed this on PA, and now get the same thing on CleanROM. Yesterday, I ran the Rogers RUU and that got LTE. So I went back to CleanROM (same radio image) and now only get HSPA. If I try to use the ltemobile.apn APN it fails with the message "Connection failed due to incorrect APN setting." Hope this info is useful for anyone with educated guesses

andyondroid said:
Check your APN settings. These settings worked for me.
http://forum.xda-developers.com/showpost.php?p=19434188&postcount=2
Click to expand...
Click to collapse
I checked, I had all that set correctly, still no LTE
If anyone else has suggestions, I would be glad to hear them.

person66 said:
I checked, I had all that set correctly, still no LTE
If anyone else has suggestions, I would be glad to hear them.
Click to expand...
Click to collapse
From my experience i've had no issues with Rogers LTE on Sense roms and CM10. I would probably try deleting the APN and re-adding it.
I'd also check the network type. In dialer, dial *#*#4636#*#* and under Phone Information check that the network type is set to 'GSM/WCDMA/LTE auto'
Beyond that, trying running the latest Rogers modem/baseband. I'm using 0.18as.32.09.28L with no issues.
I've only had my One X a week so beyond this, i'm out of ideas.

andyondroid said:
From my experience i've had no issues with Rogers LTE on Sense roms and CM10. I would probably try deleting the APN and re-adding it.
I'd also check the network type. In dialer, dial *#*#4636#*#* and under Phone Information check that the network type is set to 'GSM/WCDMA/LTE auto'
Beyond that, trying running the latest Rogers modem/baseband. I'm using 0.18as.32.09.28L with no issues.
I've only had my One X a week so beyond this, i'm out of ideas.
Click to expand...
Click to collapse
there is an option in setting...you have to change from wcdma to lte...in mobile settings...
i can confirm lte works with cm10...worst case try flash a 4.0.3 rom then flash cm10..

Here's my experience: you no longer need the sense flash method. Make share you do a system, factory, cache and dalvik wipe. Do system and factory twice, as it did not always 100% work for me.
Then boot up. Go to apns and delete all the non-lte ones. Set the lte/wcdma/gsm setting there.
Next go to *#*#4636#*#* in dialer. Check phone information so that network says lte/gsm(prl).
Reboot and hopefully it will all stick.
Also I noticed that the default lte APN has port 80 and not MMS port 80. Make sure that is correct
Sent from my One XL

Okay, I've made some progress on this. I did a factory reset and system wipe from TWRP recovery then re-installed CleanROM 5 from scratch. When it booted up I added the ltemobile.apn APN. This time it successfully connected to the APN, but it still did not get past HSPA. I then booted back into recovery and replaced /system/build.prop with the build.prop from the Rogers 1.94.631.3 stock ROM (http://forum.xda-developers.com/showthread.php?t=1812544). When it booted up it got LTE coverage.
So there must be something key in build.prop required to get LTE to connect. I've attached the two build.prop files in case anyone with trained eyes wouldn't mind diffing them and suggesting what setting might be the key to unlocking LTE.

With CM10 I had to delete the APNs and re-add them, even if they were correct. Not sure why.

denversc said:
Okay, I've made some progress on this. I did a factory reset and system wipe from TWRP recovery then re-installed CleanROM 5 from scratch. When it booted up I added the ltemobile.apn APN. This time it successfully connected to the APN, but it still did not get past HSPA. I then booted back into recovery and replaced /system/build.prop with the build.prop from the Rogers 1.94.631.3 stock ROM (http://forum.xda-developers.com/showthread.php?t=1812544). When it booted up it got LTE coverage.
So there must be something key in build.prop required to get LTE to connect. I've attached the two build.prop files in case anyone with trained eyes wouldn't mind diffing them and suggesting what setting might be the key to unlocking LTE.
Click to expand...
Click to collapse
Any chance you have figured out how to get it working on CM10? I tried the other suggestions, like deleting the apns and then entering them again, wiping everything, and I checked that the network was set to lte/gsm(prl). Still no LTE unfortunately.

person66 said:
Any chance you have figured out how to get it working on CM10?
Click to expand...
Click to collapse
Nope. I'm still rockin' HSPA on CleanROM. Some day I will probably mess around with the build.prop to see if I can figure it out. I really have no idea though. You should try running the RUU just to see if you get lte like I did.

Just got LTE working on Rogers with CM10, finally!
1.) First, I flashed the official stock Rogers ICS Baseband/Modem. You can check to see if you already have the correct modem by going to Settings, choosing About Phone, and checking your "Baseband version".
2.) Second, I corrected the APN settings that come default with CM10. The APN for ltemobile.apn need to be change, since the CM10 settings incorrectly set the Port as 80 (should be left blank), set the MMS port as blank (should be "80"), and set the APN type as something along the lines of 'default' (should be either "*" or "internet + mms"). Make sure you click the menu hardbutton and choose "Save", and go back and check to see that it did indeed save. I also selected the Rogers LTE amonst the list of the four different APNs (Rogers, Rogers LTE, Rogers Tethering, Rogers WAP - not sure if this last step makes a difference but this is what I did anyway).
3.) Go to your phone dialer, and type in *#*#4636#*#*. A "Testing" menu should pop up. Select "Phone information", scroll down to the bottom and under 'Set preferred network type", I chose "LTE/GSM auto (PRL)".
4.) Voila, this worked. I did not need to restart, just gave it a minute and the icon changed from H+ (HSPA+) to 4G (LTE). You can confirm LTE status by either doing a speed test and seeing the results, or go to Settings, scroll to the bottom and choose "About Phone", then "Status", and under "Mobile network type" it should say LTE. On mine it said "LTE:13".
Others, please experiment and try to see if you get the same results.
Cheers

adams03 said:
Just got LTE working on Rogers with CM10, finally!
3.) Go to your phone dialer, and type in *#*#4636#*#*. A "Testing" menu should pop up. Select "Phone information", scroll down to the bottom and under 'Set preferred network type", I chose "LTE/GSM auto (PRL)".
Cheers
Click to expand...
Click to collapse
This I think is the main thing. I'm on AT&T but up until just recently every time I flashed an AOSP ROM I had to go into this menu and set it to LTE/GSM. It would always default to WCDMA Preferred for some reason. It doesn't happen anymore but it used to happen every time I flashed an AOSP ROM or even when I rebooted. I had to change it and then it would be fine until I rebooted again.

Thanks, this worked on my SGH-I727R on Rogers.
I wonder why the apn settings load wrong in CM10 when the system reads them from the SIM card...? This never happened to me on previous aosp ICS roms.

what setting do you have for the tethering apn?
i am having issues having other devices running off my hotspot
this is what i currently have for tethering
Name: Rogers Tethering
APN: ltedata.apn
Proxy: Not set
Port: Not set
User Name: Not set
Password: Not set
Server: Not Set
MMSC : Not set
MMS Proxy: Not set
MMS Port: Not set
MCC : 302
MNC: 720
Authentication Type: Not Set
APN Type: dun
thanks in advance

g35thrilla said:
what setting do you have for the tethering apn?
i am having issues having other devices running off my hotspot
this is what i currently have for tethering
Name: Rogers Tethering
APN: ltedata.apn
Proxy: Not set
Port: Not set
User Name: Not set
Password: Not set
Server: Not Set
MMSC : Not set
MMS Proxy: Not set
MMS Port: Not set
MCC : 302
MNC: 720
Authentication Type: Not Set
APN Type: dun
thanks in advance
Click to expand...
Click to collapse
It's funny you posted this. I am on AT&T and recently I have not been able to get tethering devices to work, but up until recently, I have never had a problem.

my bud has the same phone unrooted with rogers gonna check his apn settings and see if they differ.

K well I just got off the phone with rogers. All the APN setting are fine but still no tethering. Well if it don't won't it don't work. If anyone is successfully tethering on cm10.1 build Jan 12 2013 with Rogers plz let me know.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

SGS3 LTE 4.3 proxy settings problem

Hi
I have just upgraded a non rooted phone from 4.1.2 to 4.3
Now everytime I connect to wifi it shows a proxy. Even if I go into advanced and set it to None it comes back as manual. I've deleted and recreated the connection but always still there.
Shows as Manual with the loopback address of 127.0.0.1 and port 3128
I haven't installed a proxy service on the phone to use and I don't use a proxy on my networks but on some networks everything seems to work but on others some services don't?
So why won't this stay set to none?
Thanks for any help
Mart

Setting up VPN

Hi. I have an AT&T G3 but Im using a tmobile sim. I want to change the APN protocol to IPv4, however, in the APN settings, there is no option for APN protocol. Is this feature not present in the AT&T firmware? Im running stock Kitkat. Thanks
To clarify, VPNs do not with with IPv6 on tmobile - apparently switching to IPv4 is a solution to this problem

Lost IPv6 on AT&T

I've got a Moto G Stylus 2021 on Consumer Cellular in the US. My ISP uses carrier grade NAT so I have no public IPv4 but I *can* ssh from my phone to a machine on my LAN using IPv6. Or at least I could until CC sent me a new SIM card last week as part of their switchover from T-Mobile to AT&T. Now when I try to ssh via IPv6 (using the Termius app) I get an error "Connection failed. Disconnected with the message: network is unreachable. Error type: 1, error code: -101". Ordinary 4G data, like email and web browsing works fine.
When I go to test-ipv6.com it tells me "No IPv6 address detected. You appear to be able to browse the IPv4 internet only. You will not be able to reach IPv6-only sites" (Yeah, no kidding).
I wasted 45 minutes on the phone to CC talking to people who had no clue as to what IPv6 even was, and tried to tell me that the problem was because CC stopped supporting 3G two years ago. I said, "No, IPv6 has been around for 15 years." They said "Oh that's old technology then. We don't support anything 15 yeares old". Duh. I checked my APN and found that my APN type and APN protocol fields were now set to IPv4. I changed them to IPv4/IPv6 and rebooted with wifi turned off. Didn't help. I tried setting them to just IPv6. That didn't work either. I tried the suggestions here: https://www.att.com/support/article/wireless/KM1062162/ and here: https://www.4gapn.com/us/en/consumer-cellular and they didn't work either.
Anyone else with this problem? Does anyone know if CC even still supports IPv6 on AT&T? Is there anyway to get my IPv6 ssh back?

I don't know if I'm answering my own question but the Hurricane Electric list of ASN's (https://bgp.he.net/country/US) seems to suggest that Consumer Cellular does *not* support IPv6 now. :-(
However, I found a workaround. route48.org offers free IPv4 to IPv6 tunneling. Very easy to setup and works fine.