Due to some SIP calling issues I’ve been having, I recently switched my APN protocol from the default of IPv6 to IPv4—and, once I did this, all my SIP issues were immediately resolved. What I didn’t expect though, was doing this caused my bandwidth speed to increase. Just prior to making the change, I did a speed test and got ~10/10 down/up—immediately after making the change I went to 30/15.
Anyone else experience the same? You can change the protocol to IPv4 via Settings, More, Cellular networks, Access Point Names, clicking on your APN, APN protocol, IPv4, clicking on the three vertical overflow dots and Save.
Cheers.
Related
Somehow I can't get the MEdiaNet Proxy to work properly. I've configured my internet settings to what is widely available information.
_______________________________________
When I have IE configured as follows:
IE > Tools > Options > Connections > Select Network: WAP Network
I can't access the MEdiaNet homepage nor any other site on the web. Instead I get a return error that says: "The Requested Page can not be displayed."
_______________________________________
When I have IE configured as follows:
IE > Tools > Options > Connections > Select Network: The Internet
I can get access to the web (which is more important at this point) but still not the MEdiaNet homepage.
_______________________________________
The puzzling thing for me is that I didn't have this problem when I was under the unlocked T-Mobile ROM. Any help or insight is much appreciated.
proxy
I am not on cingular, but used to be a while back. this is what you should have.
gprs
APN: wap.cingular
username(CAPS): [email protected]
password: CINGULAR1
CONNECTS TO THE INTERNET
PROXY SET UP
connects from the INTERNET
to THE wap network
Wireless.cingular.com:80
make sure you deletet anyother proxy settings
in PIE tools/options/connections
choose wap network, try again auto detect on/off not sure.
that should work.
Yup. Those are my exact settings. I've checked it 100 times and still can't figure it out. Again, "THE INTERNET" works but the "WAP NETWORK" does not.
Something happened when I migrated to the HTC based rom. I'm wondering if there's a registry value that changes the way proxies are handled within wm5.
I had the same problem. Someone on howardforums.com told me to use 66.209.11.61:9201 as the proxy and to switch the proxy type from HTTP to WAP.
Worked like a champ (not sure why the normal settings don't work though).
Now if I could only get MMS to work...
Thanks for the tip! It works perfectly.
Just tested out my MMS settings to be sure that it was working. It is indeed working both for sending and receiving. Settings are as follows:
Go to messaging > MMS > Menu > Options > Account Settings > Menu > MMSC Settings
Create a new item:
Name: Cingular MMS (But you can call it anything you want)
MMSC URL: http://mmsc.cingular.com
WAP Gateway: wireless.cingular.com
Port: 80
Connect via: The Internet
Max Sending Size: 300k
WAP Version: WAP 2.0
Cheers
What most likely will break is if you use wifi or your AS connection. It seems the settings are backwards on this device. And if you get that working, it will alwasy try to use a gprs connection even when a wifi or as connection is available.
Kind of sucks!
Proxy while using WiFi
Because Cingular uses a proxy setting you will not be able to use the WiFi as stated in the post above. You really do not need the proxy settings in to access the internet. I have had many devices with WiFi and have disabled the proxy on all of them and have been able to access full internet. With the proxy set you will only be able to get to "pda" or tiny screen sites. Try it out and let me know if it works. I have been thinking of getting either the HTC version or the Samsung Blackjack. I would rather have this one becuase I would prefer the WiFi over the 3G.
What are you thoughts?
Cingular MEdia Net
Wow...there is a GOD.
I made it a goal to get MEdia Net working on my phone, afterall, I am paying $20 a month for it. Like other users, I could get to any website, but not MEdia Net. This also happened after I upgraded the ROM (to remove the T-Mobile branding). I tried all suggested settings for IE, GPRS, and Proxy all from the various forums - xda, hofo, Cingular FAQ, called Cingular tech support. Nothing was working. Tonight I was farting around and stumbled upon this thread. I tried the Proxy settings above, and still nothing. I made several other changes and here is what I have now...
IE: tools/options/connections
Unchecked - Automatically Detect Settings
"Select Network" - Work
GPRS:
Connects to: The Internet
Access Point: wap.cingular
User Name(CAPS): [email protected]
password(CAPS): CINGULAR1
Primary DNS: 66.209.11.61
Proxy:
Connects from: The Internet
Connects to: Work
Proxy (name: port): 66.209.11.61:9201
Type: WAP
I know just like everyone else that MEdia Net itself does not have much to offer, but it was pi$$ing me off that it was not working. Now that I have it working though, I understand that there is a newer version of MEdia Net out or something?
when i had the cingular 2.06 rom my mms limit was 600k. Since upgrading to XDAlive and having to manually enter the media net and mms setting i'm limited to 300k. did anyone else notice this
dabears05 said:
Wow...there is a GOD.
I made it a goal to get MEdia Net working on my phone, afterall, I am paying $20 a month for it. Like other users, I could get to any website, but not MEdia Net. This also happened after I upgraded the ROM (to remove the T-Mobile branding). I tried all suggested settings for IE, GPRS, and Proxy all from the various forums - xda, hofo, Cingular FAQ, called Cingular tech support. Nothing was working. Tonight I was farting around and stumbled upon this thread. I tried the Proxy settings above, and still nothing. I made several other changes and here is what I have now...
IE: tools/options/connections
Unchecked - Automatically Detect Settings
"Select Network" - Work
GPRS:
Connects to: The Internet
Access Point: wap.cingular
User Name(CAPS): [email protected]
password(CAPS): CINGULAR1
Primary DNS: 66.209.11.61
Proxy:
Connects from: The Internet
Connects to: Work
Proxy (name: port): 66.209.11.61:9201
Type: WAP
I know just like everyone else that MEdia Net itself does not have much to offer, but it was pi$$ing me off that it was not working. Now that I have it working though, I understand that there is a newer version of MEdia Net out or something?
Click to expand...
Click to collapse
I tried those settings but it still won't work?
philocity said:
Yup. Those are my exact settings. I've checked it 100 times and still can't figure it out. Again, "THE INTERNET" works but the "WAP NETWORK" does not.
Something happened when I migrated to the HTC based rom. I'm wondering if there's a registry value that changes the way proxies are handled within wm5.
Click to expand...
Click to collapse
Check the Wiki for the registry tweak to add 600k MMS. Involves changing one value and making one more.
I forgot the exact details (location of keys/values) off the top of my head but it involved changing SendDataLimit to 4 (or next number higher) and making SendData4 value = 614400 D_WORD(decimal)
Thats off memory...so double check the wiki.
Interesting here as too (have AT&T Wirless) and both MEdianet and Cellular Video were (apparently) removed with a cooked WM6.1 ROM...
Not really a biggie, but I wanted a 'morale victory'...to get both pages (URLs) to work with Mobile IE (without having to tweak/modify any connection settings..
Cellular video is: http://cingularvideo.cingular.com
Alternative MEdianet is http://infospace.com/infow.sbcw/
Because a I recently received a AT&T MEdianet email advising me of a lot of customization changes...and wanted to see what was up...
Both pages report: We are temporarily experiencing technical difficulites
I noticed that my AT&T was set originally to just IPv4 APN protocol. I switched to IPv4/IPv6. Is there any advantage or problems to doing this?
I have a T-Mobile G3 and I am unable to set my APN (a copy since the built-in one is not editable) to IPV4. If I do that, the phone does not connect to the mobile data network. Looking at the logs, I get this error:
D/MobileDataStateTracker(28614): default: Received state=DISCONNECTED, old=CONNECTING, reason=apnFailed
Setting IPV6 or IPV4/IPV6 will quickly connect.
I also found some references to 6to4 when connecting to the network. I didn't copy them, but I'll dig through to find them and update.
On other versions, can you use your APN with IPV4 only? If my theory is correct, the T-Mobile version being IPV6 only is breaking international roaming, which is a pretty big deal (most of the internet, let alone other operators, is not IPV6 enabled yet).
If anyone with a handset that isn't T-Mobile test this, it would be appreciated. Really need my international roaming and nobody is sure of the cause yet.
Sent from my LG G3
I'm having ipv4 issues and roaming issues as well. I called tmobile twice about it and they won't help me unless I'm in a foreign country having the data issue or after my data resets because I'm maxed on roaming data allowance
NewZJ said:
I'm having ipv4 issues and roaming issues as well. I called tmobile twice about it and they won't help me unless I'm in a foreign country having the data issue or after my data resets because I'm maxed on roaming data allowance
Click to expand...
Click to collapse
What is the max allowed??
50mb/month
Im wondering why in aosp, why the apn setting using ipv4 T-Mobile US LTE......kills my data connection but T-Mobile US LTE IPv6 works.
Anything i can do on my end?
Kernel, rom related?
I'm not sure why this works (especially seeing both names resolve to the same two IP addresses) but I've found I can always get the IPv4 APN to work if I go in and edit the APN to fast.tmobile.com from fast.t-mobile.com.
Tethering still gives me problems when IPv6 is available so I am glad changing the APN destination works, even if I still can't explain it.
Weird....that did work. I'm actually getting faster download speeds under ipv4 compared to ipv6 lol
Here's another question, why can't I send or receive MMS on AOSP while on Wifi??
This note 5 is the first phone I have with AT&T that's getting a non-local (2600::380::....) IPv6 address from the cell tower. I wasn't getting ipv6 on my nexus 6 last week (same LTE network.)
Does anyone know if this was something that AT&T recently enabled, or if they are only doing router announcements to specific APN's and/or h/w?
garyd9 said:
This note 5 is the first phone I have with AT&T that's getting a non-local (2600::380::....) IPv6 address from the cell tower. I wasn't getting ipv6 on my nexus 6 last week (same LTE network.)
Does anyone know if this was something that AT&T recently enabled, or if they are only doing router announcements to specific APN's and/or h/w?
Click to expand...
Click to collapse
From what I have read AT&T has started their plans for IPv6 since 2012 and started roughly mid 2014 rolling them out on the cellular network. They state the roll out will be slow, so it is possible they just turned it on by you. Is it possible also that it was not enabled on the Nexus 6 by default?
KennyG123 said:
Is it possible also that it was not enabled on the Nexus 6 by default?
Click to expand...
Click to collapse
It's possible, but I'd think it would have to be on the carrier side if that was the case. With the nexus device, I was using the same firmware that everyone in Europe (and most of Asia) is using - and many of them were getting ipv6 numbers.
As well, my home wifi network (ipv6 dual stack) would result in an ipv6 address assigned to the handset.
Actually, to be more accurate, they were getting RA's. Android doesn't do DHCPv6 at all.
It's quite possible that AT&T just got around to turning it on in my area at the same time I switched phones, but that'd be an interesting coincidence. The more I think about this, the more I'm convinced it was related to the APN. I'm unable to check now, but I'm starting to wonder if the default APN for the nexus6 on AT&T blocks ipv6.
garyd9 said:
It's possible, but I'd think it would have to be on the carrier side if that was the case. With the nexus device, I was using the same firmware that everyone in Europe (and most of Asia) is using - and many of them were getting ipv6 numbers.
As well, my home wifi network (ipv6 dual stack) would result in an ipv6 address assigned to the handset.
Actually, to be more accurate, they were getting RA's. Android doesn't do DHCPv6 at all.
It's quite possible that AT&T just got around to turning it on in my area at the same time I switched phones, but that'd be an interesting coincidence. The more I think about this, the more I'm convinced it was related to the APN. I'm unable to check now, but I'm starting to wonder if the default APN for the nexus6 on AT&T blocks ipv6.
Click to expand...
Click to collapse
This guy states his was set for IPv4 by default instead of the normal ipv4/ipv6 setting.
Where are you seeing ipv6? In system settings >about device>status ? That looks like ipv4/ipv6 from your phone to att's internal network.
I did check ip6.me and that showed an ipv6 address, but couldn't be sure that was legit. ..
quordandis said:
Where are you seeing ipv6? In system settings >about device>status ? That looks like ipv4/ipv6 from your phone to att's internal network.
I did check ip6.me and that showed an ipv6 address, but couldn't be sure that was legit. ..
Click to expand...
Click to collapse
I'm using a third party program to check the IP addresses (one that specifically shows IPv6.) The same IP shows under settings->about->status.
The 2600:: address it's showing is a legit global IPv6 assignment, and android ONLY does SLAAC (not DHCPv6) so it must be seeing an ipv6 RA.
On the other hand, I can't ping it from the outside, so it appears that AT&T has some proxy between the phones and the "rest of the world." What I don't understand is why they'd be assigning proper global IPv6 addresses behind a proxy unless it's a stage in a larger rollout. (If they intended to keep things behind the proxy, they should be using fc00::/7 range addressing - or addresses starting with FD.)
For YOU, what ipv6 address are you seeing when wifi is turned off? If it starts with "260", it's part of AT&T's global block.
garyd9 said:
I'm using a third party program to check the IP addresses (one that specifically shows IPv6.) The same IP shows under settings->about->status.
The 2600:: address it's showing is a legit global IPv6 assignment, and android ONLY does SLAAC (not DHCPv6) so it must be seeing an ipv6 RA.
On the other hand, I can't ping it from the outside, so it appears that AT&T has some proxy between the phones and the "rest of the world." What I don't understand is why they'd be assigning proper global IPv6 addresses behind a proxy unless it's a stage in a larger rollout. (If they intended to keep things behind the proxy, they should be using fc00::/7 range addressing - or addresses starting with FD.)
For YOU, what ipv6 address are you seeing when wifi is turned off? If it starts with "260", it's part of AT&T's global block.
Click to expand...
Click to collapse
Yep, when not on WiFi, and just on data, IPv6 block starts with 2600. Interestingly, my IPv4 address starts 10.102 - so guessing that's internal IP. Not at all surprised that 2600 block is not accessible from "outside". That said, I'd be curious to see if two phones on the same ATT switch would be able to communicate with each other over the internal network? My inclination is that it's not at all possible, but...who knows?
quordandis said:
Yep, when not on WiFi, and just on data, IPv6 block starts with 2600. Interestingly, my IPv4 address starts 10.102 - so guessing that's internal IP. Not at all surprised that 2600 block is not accessible from "outside". That said, I'd be curious to see if two phones on the same ATT switch would be able to communicate with each other over the internal network? My inclination is that it's not at all possible, but...who knows?
Click to expand...
Click to collapse
I have a broadband modem (LTE) on my work machine, and when I connect to AT&T with that, i do NOT get an ipv6 address. Then again, it's using the older LTE apn of "broadband"