Related
I seem to be having a problem connecting to my wireless router.. I can't get an IP. I keep getting a 169.something IP.. I restarted the router, it has the newest available firmware, tried connecting while I was right next to the router, deleted all the references to the IP in the registry.. and then tried all that again with no encryption on the router. Basically everything I could think of. It works after a hard reset or when I flash the ROM with any other rom.. But only connects once.. not more..
Worked with the original ROM (I-Mate JasJam.. Arabic version).. Windows VI Black.. 3 DES and the Testra I-Mate).. Works the first time.. then never after that..
Any suggestions?
That's... odd. Have you tried flashing to the original ROM to see if it still works properly? Also, and this is just a blind guess, is your SSID pure ASCII or do you have Arabic characters in it? I'm not sure that's even allowed in the 802.11 specs, but who knows.
the SSID is pure ASCII.. and I tried flashing back to the original ROM and it's still the same thing..
It's not a router problem either cuz the problems is the same with other routers
What do you mean by "still the same thing" - it still works with the old ROM or it still doesn't work like the other ROMs?
As in still connects the first time but never after that.
When you downgraded to your original ROM, did you downgrade the OS only, or the whole thing? If you downgraded the ExtROM, did you allow the customizations to install from it after hard reset?
If you didn't downgrade the radio, try it. Technically, the radio ROM has nothing to do with wifi, but I think it would be beneficial to have your Hermes as close to its original state as possible when troubleshooting.
What brand of router are you using?
169.254.x.x is APIPA; basically, the DHCP isn't working. Can you confirm that you have enough IP's in the DHCP range? and/or, create a reservation for the MAC address of the phone?
Perhaps you are limiting connections to certain MAC addresses only? or only to 'known' MACs?
He said this is happening with other routers as well, so DHCP range, etc, probably wouldn't apply. Then again, if they're all set up the same way...
Try giving your device a static ip adress, see if that helps.
I downgraded everything and allowed the ExtRoms to be installed. I also tried the Static IP address route but to no avail.
Haven't tried MAC Address allocation yet though..
I realized that after I flash it I test the wifi connection and then install some programs right away.. could one of the apps be causing this?
Anyone else having trouble with att tilt vpn over edge? I've had several smartphones in the past, the last being tmobile wing, and have never had any problems creating a vpn connection with url exceptions. With this new tilt it seems like I can connect the vpn only over wifi, it does not attempt to connect to the vpn when just using edge. I've reset the device several times both with and without the att customization.
Any ideas for this problem would be appreciated.
Thanks,
-J
TILT VPN Connection problems
I have been trying to make VPN connections over EDGE and 3G also. I find that the connection does get made if I connect manually, but as soon as I try to access something through IE, RD or Opera, it drops the connection. I have seen the connection maintained for up to a minute, but I cannot access anything.
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Round 1
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Sorry for that last double post. I did go back to the att kiosk again today and tried another tilt, which had the same results. I decided to return the one I had purchased and think i may try the regular htc kaiser with the front camera.
If anyone can verify that that version of phone works with pptp, that would be great.
From your last message I tried a few other things and I too was able to manually connect ( even get a prompt for login credentials to the vpn ) however the IE still will not try to connet with the url exception or keep the vpn connection open after IE is opened.
It's sad to think the att tilt is not working in thie regard. It takes away quite a bit of functionality for those who do use the vpn feature.
-J
PIE will "ignore" exceptions for work connection using EDGE
I see similar problem with 8525 at&t WM 5.0 device (HTC Hermes) exact version Microsoft ® Windows Mobile™ Version 5.0 with the Messaging and Security Feature Pack. 5.0 OS 5.1.478 (Build 15706.3.5.2)
PIE will "ignore" exceptions for work connection using EDGE. However other applications like “ActiveSync” and “Terminal Service Client” work properly.
If Wi-Fi connection used for Internet, PIE as well works properly.
FYI on previous device 8525 Cingular
Microsoft ® Windows Mobile™ Version 5.0 OS 5.1.195 (Build 14955.2.3.0)
work exceptions works with PIE
it continues...
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Today I setup a vpn server with a 192.168.x.x scope. Using wap.cingular i was able to connect to the vpn and hosts within the vpn.
I tried again to connect to the 10.x.x.x vpn and try to edit the routing table using the PocketLan but each time I try to edit something it returns an error.
I'll have to try to find another utility or see if there a way to edit the routing table.
I'm hoping theres a way to change the default route for the 10.x network.
Here's some of the info when connecting over a wap.cingular connection
ip: 10.67.x.x
gateway: 10.67.x.x ( same as ip address )
subnet mask: 255.0.0.0/8
DNS: 66.209.10.201, 66.102.163.231
WINS: 10.11.12.13, 10.11.12.14 ( kind of hard to imagine any reason for wins entries? 10-11-12-13 seems like they may just be fake address. I dont know how window mobile does it's resolution, but that doesnt seem like it would be in the customers interest to be pointed to non-existant wins, if thats what they are. This may just be place holder entries for the PocketLAN software?)
Here's some of the info when connecting over a isp.cingular connection
ip: 166.128.x.x
gateway: 166.128.x.x ( same as ip address )
subnet mask: 255.255.0.0/16
DNS: 209.183.48.11, 208.183.48.10
WINS: 10.11.12.13, 10.11.12.14 ( same comments as before )
See Arin Whois for this netblock
OrgName: Service Provider Corporation
OrgID: SPC-10
Address: 442 Route 202-206 North
Address: # 485
City: Bedminster
StateProv: NJ
PostalCode: 07921-0523
Country: US
NetRange: 166.128.0.0 - 166.255.255.255
CIDR: 166.128.0.0/9
NetName: NETBLK-CDPD-B
NetHandle: NET-166-128-0-0-1
Parent: NET-166-0-0-0-0
NetType: Direct Assignment
NameServer: NS1.WIRELESSDATASPCO.ORG
NameServer: NS.CDPDSPCO.ORG
Comment:
RegDate: 1993-07-09
Updated: 2005-01-07
RTechHandle: WDSPC-ARIN
RTechName: WDSPCo Helpdesk
RTechPhone: +1-215-489-7599
RTechEmail: [email protected]
OrgTechHandle: WDSPC-ARIN
OrgTechName: WDSPCo Helpdesk
OrgTechPhone: +1-215-489-7599
OrgTechEmail: [email protected]
# ARIN WHOIS database, last updated 2007-11-02 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
I just thought of testing tracreroutes form both isp and wap.cingular. It does then show the problem with the ip information when trying to route.
When using the tilt though at first, none of this seemed possible at the time ( as I thought I was going a little nuts ) since the url exceptions never seem to attempt to connect to the vpn at all. As if the exceptions were ignored when using anything except WIFI.
Thats it for now. Post something new later.
-J
jakedahs,
Very informative. Looks like its' been a few weeks. New insights?
Best,
Things are still working good with the kaiser and the isp.cingular. I haven't come across another ATT Tilt again to test it out again. Any other things you can think to test to put on this forum?
Thanks,
-J
LOL! I'm so far behind, I don't have a clue.
Tilt and VPN PPTP
jakedahs said:
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Click to expand...
Click to collapse
I too am having issues with my Tilt and VPN. So when I got the Tilt 10 days ago, I had a blackberry 8300 (Curve), when i left the store they had me on the same BlackBerry Data plan. The VPN worked fine - Perfectly in fact. A few days later when I questioned why I was still using a blackberry plan the CSR at AT&T said I should be on a PDA data plan and changed my service. After that the VPN stopped working. I contacted AT&T chat support and also called their complex data device support department and after changing a bunch of settings on the phone they finally gave up and said they could not support the VPN option. Nice Huh?
When I get home I am going to try connecting over WiFi and trying the VPN. This should tell me if the routing / VPN issue is related to traffic over AT&T or if there is something wrong with the phone.
Additionally, when the VPN worked it used to show a " balloon status " telling me VPN was connecting. Now it no longer does that. Even if I do force the VPN to connect and then try to use the connection is disconnects immediately.
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
VPN
jakedahs said:
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
Click to expand...
Click to collapse
What kind of tests were you thinking?
wap.cingular - isp.cingular / netowrk settings
jakedahs said:
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Click to expand...
Click to collapse
Since they had me change my plan and settings around I called and confirmed that I now have the PDA Connect Unlimited plan. However, in the phone's connection settings what should the two network and subsequent individual network setting be? Mine was set to Media Net and Media Net.
I tried setting it to ATT ISP but it still did not work.
I just use isp.cingular all the time. Have you created work url exceptions for your vpn connection? The problem I was having when I had the tilt is even though I had the exceptions it would never attempt to dial the vpn when going to a web site on the vpn network. I'm thinking it may have been ATT that cripled the phone somewhat. The regular HTC Kaiser I have now works fine.
VPN - TILT
So I confirmed that if I use my WiFi connection the VPN works perfectly.
There is some issue with routing over AT&T data network. I tried chatting with their online chat support and they could not give me the settings I needed. It was clearly beyond their scope of knowledge. I will try calling their complex data support department to see if I can get the right settings.
How can a company offer data services and not understand their own network?
Vpn - Tilt - Settings
I found this posting at the cingular.com forum.
Since I need to call tomorrow to confirm my provisioning and my data plan subscription I cannot tell if they will work but I thought I would make the info public.
Here's what I've done to VPN using L2TP successfully... (someone else)
- Have PDA Unlimited Plan
- Call to have your account "provisioned" to use isp.cingular
- Create a new connection using the isp.cingular settings
- Configure device to always use that connection
- Create a new VPN connection
- Import appropriate certificates (if necessary)
- Disable (preferably remove) Proxy settings in Registry
- Create an Exception list for Intranet addresses
- Configure device networks to use isp.cingular for Internet access and vpn for 'Your Work/Intranet' network
One thing I have noticed is that if I let the device connect automagically to VPN, it will disconnect after a short period of inactivity. If I manually/force connect to VPN, it stays that way until I disconnect session.
I can connect either via 3G or Edge with no issues/problems.
VPN Access over anything on the tilt would be nice
I am unable to either one of my 2 vpn's using any connection configuration. I It seems like it wants to connect but then gives me an error msg telling me to check username and password.
Can anyone shed anylite what I'm doing wrong?
Tilt Vpn over Edge
With a little patience i figured it out! if you connect to your VPN first and then go to IE it will disconnect you. But if you go to IE, Opera, whatever first and then go to the address that you have in your exception list the tilt will connect to MediaNet and then connect to your VPN server and work!
So I think I got free tethering to work on my MG with tmobile $30 prepaid plan by changing the APN, but not 100% sure if I got the process down correctly since I've been tinkering, rooted and still on 4.3.
Anyways, maybe you guys can give a try and see if it works. This is aimed towards t-mobile users who don't have hotspot as part of their plan or have already exhausted their monthy tethering limit.
steps:
- go to settings > More....> mobile networks > Access Point names
- add a new APN by hitting the "+" sign
- Set "Name" to what ever you'd like (e.g. Hotspot4life)
- Set "APN" to fast.t-mobile.com
- Set "APN protocol" to IPv4/IPv6 or IPv4
- Leave everything else untouched
- hit menu button then select save
- Select the APN just created.
- Active native tethering (assuming you've adjusted ID and password already to your liking)
- If it works, go back into settings and select old APN... and check if tethering has been blocked.
Note: there's no need to reboot when switching APNs.
If it doesn't work, then a file change I did beforehand while rooted made a difference or something else was a factor.
neugenusis said:
So I think I got free tethering to work on my MG with tmobile $30 prepaid plan by changing the APN, but not 100% sure if I got the process down correctly since I've been tinkering, rooted and still on 4.3.
Anyways, maybe you guys can give a try and see if it works. This is aimed towards t-mobile users who don't have hotspot as part of their plan or have already exhausted their monthy tethering limit.
steps:
- go to settings > More....> mobile networks > Access Point names
- add a new APN by hitting the "+" sign
- Set "Name" to what ever you'd like (e.g. Hotspot4life)
- Set "APN" to fast.t-tmobile.com
- Set "APN protocol" to IPv4/IPv6 or IPv4
- Leave everything else untouched
- hit menu button then select save
- Select the APN just created.
- Active native tethering (assuming you've adjusted ID and password already to your liking)
- If it works, go back into settings and select old APN... and check if tethering has been blocked.
Note: there's no need to reboot when switching APNs.
If it doesn't work, then a file change I did beforehand while rooted made a difference or something else was a factor.
Click to expand...
Click to collapse
t mobile and Three use Packet Sniffing to check the file headers to detect tethering. If you tether an iOS device or an OSX device to your phone, often they will not get flagged and the tethering will work. If you use a Windows PC or other device it will be detected immediately. I mention this, as it could be a factor if you tried tethering with an ipad or something and got it to work. Messing with the APN on Three has no effect, so I'd be surprised if it works with T Mobile.
Thanks for the tip! I found that this works, but unreliably on my Moto G.
I just got a MG last week and was frustrated to find tethering would not work at all out of the box. I stumbled across your post and made the changes you recommended and it worked very well at first - for maybe15 minutes or so. Then I noticed my Chromebook lost connection and upon further diagnosis it was the Moto G that lost connection to the T-Mobile network. I tried to turn of tethering, but that didn't help and I finally had to reboot the phone to get it back on the network. I switched back to the default APN and the phone worked reliably again, but obviously not tethering. In the past couple days I've tried the new APN with your settings a few times and get similar results - it works for a while, but then the phone loses cell connectivity. I've since found that I toggling Airplane Mode on and off will restart the cell connection and tethering will also start working again, so it kind of works but not as well as it should.
I've been doing more searching regarding the fast.t-mobile.com APN and other threads seem to indicate that APN is specifically for LTE phones. Since the Moto G doesn't have an LTE chip, I wonder if that's causing the reliability problem?
Brandon
PS - I think there might be a typo in your instructions and fast.t-tmobile.com should be fast.t-mobile.com - with just 1 t in the t-mobile. Thanks again!
theragtopman said:
PS - I think there might be a typo in your instructions and fast.t-tmobile.com should be fast.t-mobile.com - with just 1 t in the t-mobile. Thanks again!
Click to expand...
Click to collapse
You're right. I've fixed it. Thanks.
I rarely tether, so I haven't used it in every scenario. But when I do tether, its while tethering to my tablet, my friend's phone, or desktop/laptop WITH user agent switcher on Chrome to mask the desktop/laptop as a mobile device. After reading your post, I tethered to my laptop for an hour and did not encounter any issues. Do you lose connectivity even when the phone's signal strength is strong? Have you tried tethering to a different device (mobile)?
Thanks for the follow up. I've been trying it again today from my home where I get better cellular signal strength, but I'm getting similar results. It connects up and runs for 15-30 minutes and then starts flaking out. After rebooting both the phone and Chromebook, the Chromebook kept trying to go to a T-Mobile sign-in page, but couldn't even load that. And I too am using a Chrome extension to change the user agent to Android. The Moto G seems to be working fine and not losing it's connection this time.
I have also been able to test tethering on a Nexus 4 running Android 4.4.2 today and the Chromebook is connecting just fine and staying connected - no problems at all. I compared the APN settings between the 2 phones and the Nexus has the MMSC entry filled out (which xda won't allow me to post here because i'm too new), so I added that into the Moto G, but it did not help. Darn. I really like the Moto G, but really need reliable tethering. Thanks again...
theragtopman said:
Thanks for the follow up. I've been trying it again today from my home where I get better cellular signal strength, but I'm getting similar results. It connects up and runs for 15-30 minutes and then starts flaking out. After rebooting both the phone and Chromebook, the Chromebook kept trying to go to a T-Mobile sign-in page, but couldn't even load that. And I too am using a Chrome extension to change the user agent to Android. The Moto G seems to be working fine and not losing it's connection this time.
I have also been able to test tethering on a Nexus 4 running Android 4.4.2 today and the Chromebook is connecting just fine and staying connected - no problems at all. I compared the APN settings between the 2 phones and the Nexus has the MMSC entry filled out (which xda won't allow me to post here because i'm too new), so I added that into the Moto G, but it did not help. Darn. I really like the Moto G, but really need reliable tethering. Thanks again...
Click to expand...
Click to collapse
You need install a User Agent String changer addon in your browser and change the string.
I use this one: https://chrome.google.com/webstore/...r-c/djflhoibgkdhkhhcedjiklpkjnoahfmg?hl=en-US
I have instructions for another device here: http://forum.xda-developers.com/showthread.php?t=2201062
Good luck.
Thanks for the recommendation! Sorry I didn't make it more clear in my reply above, but I am using a user agent switcher - currently the Ultimate User Agent Switcher. Just to be sure, I disabled that extension and installed the User-Agent Switcher for Chrome that you linked to, but unfortunately I'm getting the same result - the Chromebook takes forever and keeps trying to connect to the "Welcome to T-Mobile" page.
And I tried again with the Nexus 4 and the Chromebook connects up immediately and runs great - no T-Mobile page or any other problems. I did a little more research and found a post on the Nexus 4 forum recommending disabling IPV6 in the APN Protocol, so I switched both phones from IPV6/IPV4 to just IPV4 and am getting the same result on each. Both phones work fine on the cell network and Internet, but the Chromebook only tethers successfully to the Nexus 4.
theragtopman said:
Thanks for the recommendation! Sorry I didn't make it more clear in my reply above, but I am using a user agent switcher - currently the Ultimate User Agent Switcher. Just to be sure, I disabled that extension and installed the User-Agent Switcher for Chrome that you linked to, but unfortunately I'm getting the same result - the Chromebook takes forever and keeps trying to connect to the "Welcome to T-Mobile" page.
And I tried again with the Nexus 4 and the Chromebook connects up immediately and runs great - no T-Mobile page or any other problems. I did a little more research and found a post on the Nexus 4 forum recommending disabling IPV6 in the APN Protocol, so I switched both phones from IPV6/IPV4 to just IPV4 and am getting the same result on each. Both phones work fine on the cell network and Internet, but the Chromebook only tethers successfully to the Nexus 4.
Click to expand...
Click to collapse
You need to set the Firefox string in my thread. That is the only desktop browser string that works. The reason why Chromebook/Ipad/Ipod devices work is because T-Mobile allows those devices since they can all have Cellular radios in them for radio. It would block legit paying customers.
Hey - thanks for the quick follow up!
Unfortunately, I just tried all 3 of the Firefox settings in the user agent switcher and rebooted the Chromebook each time, but no joy - each time after restarting and connecting to the Moto G wi-fi hotspot the Chromebook just tries to redirect me to the T-Mobile site.
theragtopman said:
Hey - thanks for the quick follow up!
Unfortunately, I just tried all 3 of the Firefox settings in the user agent switcher and rebooted the Chromebook each time, but no joy - each time after restarting and connecting to the Moto G wi-fi hotspot the Chromebook just tries to redirect me to the T-Mobile site.
Click to expand...
Click to collapse
Do you have the T-Mobile branded Moto G? If so you may need to disable the upsell app as I did in my L9 thread. You may also need to edit /etc/apns-conf.xml
Also, use this app instead of the builtin tethering. It may be notifying the carrier of tethering.
https://code.google.com/p/android-wifi-tether/
Thanks again for more suggestions.
I am using an unlocked US GSM model of Moto G I purchased from Amazon.
I have not rooted yet, but may try that and the tethering app you linked to. I'm wondering if the stock app included on the Motorola device is the culprit, whereas the stock tethering app on the Nexus device may not be reporting back...
There is a WiFi network in my school. All my friends can use it without problems, Android or iOS... but with my GT-I9505 on Samsung ROMs (even the stock one) I can't connect to internet because of DNS. This WiFi needs static IP and a different gateway, not in the same range of the IP to work. Chrome always gives me DNS_PROBE_FINISHED_NO_INTERNET, whatever DNS I choose. But the fact is that the problem vanish with any AOSP/CM ROM! I can connect to the network without issue.. set it up and go!
How this is possible? Is there any solution without having to use other ROMs if not the Samsung ones?
Can't you just input a dns manually? Press and hold the wifi network and select modify network. There you can input a manual dns.
Try these ones:
208.67.222.222
208.67.220.220
No matter what DNS I set, internet with that WiFi doesn't work if I use a Samsung ROM.
Sorry I didn't read that part.
According to this it's a bug in older versions of Android. That's probably why AOSP and CM roms work. Because they are atleast at Android 5.1.1. while stock Samsung is stuck at Android 5.0.1.
https://code.google.com/p/android/issues/detail?id=79504
I have LG V20 H915 (from Freedom Mobile), and I've been having HotSpot DNS issues ever since I got it. When I start a hotspot on the phone and connect any device to it, the built in DNS server (192.168.43.1) doesn't work (if I try using nslookup command, I get error - "*** Unknown can't find hostname: Query refused). I can work around this by setting Google DNS servers (8.8.8.8 and 8.8.4.4) in my device connected via HotSpot, but it's a big pita, and I have one laptop from work where I don't have admin rights and can't even set my custom DNS servers, so not able to use that device with the phone hotspot.
I haven't yet tried doing a factory reset, but I would like to avoid it at all costs possible, because otherwise I would have to set up Android Pay from scratch, which is a pain. I have installed 2 updates so far (the LTE one in December and the VoWiFi couple of days ago), and they don't seem to have changed anything.
Did anyone else ever run into this issue? Anything I could possibly look at inside the phone's engineering menu?
I had the same issue with a Freedom LG G6. Going to the APN menu and restoring default settings fixed it for me.
I went for a more permanent fix - got op5 ))