Windmobile SUPL certs? - T-Mobile LG G2x

does the windmobile network use SUPL certs like tmobile uses? also are the tmobile certs able to be used on googles supl servers? or are they meant for tmobile ones as intended?

Related

New ROMs and OpenDNS...

To speed up browsing I use the free DNS servers provided by OpenDNS. They are 208.67.222.222 and 208.67.220.220. See www.opendns.com for details.
Anyways, when I enter specific DNS servers for my ISP's connection, I cannot connect. I'm wondering if my ISP has changed their policy to prevent access to external DNS servers, or if there is something wrong with the way the new ROMs operate. Previously, I had been able to use these DNS servers with no problem.
So, everyone still uses their ISP's DNS servers?
floepie said:
So, everyone still uses their ISP's DNS servers?
Click to expand...
Click to collapse
I've noticed that on my current wm6 rom it doesn't matter if I specify the opendns servers in the gprs connection settings..it's still using the isp's...you can test this by going to http://www.opendns.com/welcome
If you get the oops page..you are not using the opendns servers and I'm not sure if it's a wm6 issue or a tmobile issue.

[Q] Why can I only use VOIP on some wifi networks?

I set up my Gizmo5 account for SIP calling yesterday on the wireless network provided by my Verizon Fivespot, and it worked fine. Now I'm on my home network (Verizon DSL), and when I try to use Gizmo5 on my Nexus S, I get the error "Account registration failed: (transaction terminated); will try later." Why does this happen on only my home network? Is there anything I can do to get Gizmo5 to work at home?
Device: Nexus S
OS: Gingerbread 2.3.1
Carrier: None (Verizon Fivespot)
It may be network related at your house. Possibly a router/firewall not allowing the traffic in/out. I doubt it but I suppose the provider could be blocking that type of traffic as well.
What can I do to fix it though? I already checked my router settings and the firewall isn't blocking anything.
aaronbp said:
What can I do to fix it though? I already checked my router settings and the firewall isn't blocking anything.
Click to expand...
Click to collapse
It isn't only the outgoing ports that need to be open (they definitely do), but the firewall has to support NAT *correctly*. SIP requires intelligence from a firewall, opening/keeping-track of outgoing/incoming UDP ports, etc. If your router supports it, try a third-party firmware like Tomato.
I had this same problem with new ubee modem/router. It is indeed NAT, and the ubee has no option to disable it.
I ended up putting my old router on the ubee DMZ and now gizmo and sipgate work.
Anyone have suggestions on making a ubee work with voip?
Sent from my Nexus S using XDA App

[Q] [i9020T] Current APN Settings?

i9020T T-Mobile East-coast USA
Most of the APN settings online are a bit dated and T-Mobile's site is for generic Android phones.
What is the current APN settings for us?
In also for an answer

Questions about APN Settings

I've searched all over this site and google to find out more about APN's. Can't find a good resource for the info I was curious about. Most of it was incomplete or just confusing. Hopefully someone here knows the answers.
Does what you name the APN matter? Are the codes case sensitive? What do these different codes stand for? Exactly what is their individual purpose? What does it mean when used together? Do some codes work better with others? Are there some that shouldn't be used, or are out dated? Does it matter the order in which the APN types are listed in settings? Are there more codes?
Thanks for your help!!!
APN-
Phone
Pta
wap.cingular
Broadband
APN Types-
default
admin
internet
hipri
supl
fota
mms
dun
APN Protocol-
iPv4
iPv6
Bearer-
LTE

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

Categories

Resources