I've been trying to get the tethering workaround to stick on my new G3, and I've run into a few issues.
First, the settings.db file in /data/data/com.android.providers.settings/databases/ already has a tether_dun_required entry, with a value of 1. I can set it to 0, but when I reboot, it comes back up as 1.
Second, the built-in APN is configured for IPV6, and in order for the workaround to work, it needs to be set to IPV4. The APN is not editable, so I created a copy with everything exactly the same, except for the protocol and set that to IPV4. If I activate the IPV4 copy, I lose data completely. If I edit the copy and change the protocol to IPV6, the data comes back.
So it seems there are two hurdles to get this working. It will probably just be easier to have a custom ROM to get around this, but I'd be curious if someone knows how to make this work without a ROM. A G3 Toolbox tweak maybe? I'm just not familiar enough with this.
havanahjoe said:
I've been trying to get the tethering workaround to stick on my new G3, and I've run into a few issues.
First, the settings.db file in /data/data/com.android.providers.settings/databases/ already has a tether_dun_required entry, with a value of 1. I can set it to 0, but when I reboot, it comes back up as 1.
Second, the built-in APN is configured for IPV6, and in order for the workaround to work, it needs to be set to IPV4. The APN is not editable, so I created a copy with everything exactly the same, except for the protocol and set that to IPV4. If I activate the IPV4 copy, I lose data completely. If I edit the copy and change the protocol to IPV6, the data comes back.
So it seems there are two hurdles to get this working. It will probably just be easier to have a custom ROM to get around this, but I'd be curious if someone knows how to make this work without a ROM. A G3 Toolbox tweak maybe? I'm just not familiar enough with this.
Click to expand...
Click to collapse
I use PDANet+ and it works without doing anything funky. I haven't tried FoxFi on it, but bluetooth and usb tether works perfectly for me right out of the box.
Semantics said:
I use PDANet+ and it works without doing anything funky. I haven't tried FoxFi on it, but bluetooth and usb tether works perfectly for me right out of the box.
Click to expand...
Click to collapse
Thanks, I know USB and Bluetooth are easier, but I want WiFi tethering to use with the Nexus 7 in my car. Bluetooth can be too slow for streaming music.
I'll have my tethering bucket back tomorrow, but I easily blow through the 3 gb, so it's nice to have a fallback.
havanahjoe said:
Thanks, I know USB and Bluetooth are easier, but I want WiFi tethering to use with the Nexus 7 in my car. Bluetooth can be too slow for streaming music.
I'll have my tethering bucket back tomorrow, but I easily blow through the 3 gb, so it's nice to have a fallback.
Click to expand...
Click to collapse
I use 30+ GB a month, I even stream netflix over bluetooth without issues. This app worked perfectly for me on the G2 when I had it, but I have no need now with USB and Bluetooth working so well.
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter&hl=en
Semantics said:
I use 30+ GB a month, I even stream netflix over bluetooth without issues. This app worked perfectly for me on the G2 when I had it, but I have no need now with USB and Bluetooth working so well.
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter&hl=en
Click to expand...
Click to collapse
Hmm. I had issues with streaming Netflix over Bluetooth, and they went away with WiFi. I use around 12 GB a month.
The one downside to using Bluetooth is that the Nexus 7 does a better job with GPS lock when tethering it over WiFi than over Bluetooth, and this is with WiFi enabled.
I'll have to give it a shot with the apps be the built in tethering over Bluetooth.
havanahjoe said:
Hmm. I had issues with streaming Netflix over Bluetooth, and they went away with WiFi. I use around 12 GB a month.
The one downside to using Bluetooth is that the Nexus 7 does a better job with GPS lock when tethering it over WiFi than over Bluetooth, and this is with WiFi enabled.
I'll have to give it a shot with the apps be the built in tethering over Bluetooth.
Click to expand...
Click to collapse
The app I posted WiFi tether router works fine if you rooted your phone. I use it when folks at work need a hotspot.
Sent from my LG-D851 using Tapatalk
havanahjoe said:
I've been trying to get the tethering workaround to stick on my new G3, and I've run into a few issues.
First, the settings.db file in /data/data/com.android.providers.settings/databases/ already has a tether_dun_required entry, with a value of 1. I can set it to 0, but when I reboot, it comes back up as 1.
Second, the built-in APN is configured for IPV6, and in order for the workaround to work, it needs to be set to IPV4. The APN is not editable, so I created a copy with everything exactly the same, except for the protocol and set that to IPV4. If I activate the IPV4 copy, I lose data completely. If I edit the copy and change the protocol to IPV6, the data comes back.
So it seems there are two hurdles to get this working. It will probably just be easier to have a custom ROM to get around this, but I'd be curious if someone knows how to make this work without a ROM. A G3 Toolbox tweak maybe? I'm just not familiar enough with this.
Click to expand...
Click to collapse
If memory serves..its been many months since I did it on N5..you need write permissions to make the 0 fix on tetherdunrequired.
Were you able to unlock tethering on the TMO g3? I tried the db edit as well no luck
wideasleep1 said:
If memory serves..its been many months since I did it on N5..you need write permissions to make the 0 fix on tetherdunrequired.
Click to expand...
Click to collapse
The /data partition is mounted rw, so with root access any changes will be made to the file. It just seems to be restored on boot:
Code:
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
megtanael said:
Were you able to unlock tethering on the TMO g3? I tried the db edit as well no luck
Click to expand...
Click to collapse
Not yet. The phone will default to using the pcweb.tmobile.com APN when enabling the hotspot, and then the change in the database file doesn't stick. I got my 3 GB tethering bucket back (new billing cycle) and even with tethering allowed, I have issues sometimes where the tethered devices get no data for a while. Usually until I change towers. I noticed that tethering fails at home, I think it's due to IPV6 tethering. The default APN for the phone does not let you change it to IPV6, and not sure what settings it is using for tethering.
I found this message in the logcat:
Code:
I/Tethering( 1000): Skip IPv6 Connectivity Check because IPv6 Tetheirng is supported.
Spelling errors aside, it looks like it doesn't care if IPV6 is enabled on the network and would tether it. When looking at the IPs assigned though, only IPV4 ones are getting assigned right now (I'll have to look at this in the places where tethering fails)
Code:
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - ID : 7
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - IPv4 Address : 100.106.90.82 IPv6 Address :
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - V4 Dns : 10.177.0.34 v6 Dns :
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - V4 Dns : 10.176.83.140 v6 Dns :
I debugged it again and I do see an IPV6 statement
Code:
I/Tethering( 993): Skip IPv6 Connectivity Check because IPv6 Tetheirng is supported.
D/Tethering( 993): Only IPv6. but tethering uses both IPv4 and IPv6, so add default v4 dns addresses too - LinkProp:{InterfaceName: rmnet0 LinkAddresses: [2607:fb90:60a:2f6c:730c:b36f:b138:a4fa/64,] Routes: [::/0 -> fe80::3890:dff4:7a18:a991,] DnsAddresses: [fd00:976a::9,] Domains: null MTU: 1440 Stacked: [ [{InterfaceName: clat4 LinkAddresses: [192.0.0.4/32,] Routes: [0.0.0.0/0 -> 192.0.0.4,] DnsAddresses: [] Domains: null MTU: 0} ],] }
D/TetherController( 315): setDnsForwarders(0 = 'fd00:976a::9')
D/TetherController( 315): setDnsForwarders(1 = '8.8.8.8')
D/TetherController( 315): setDnsForwarders(2 = '8.8.4.4')
I see this entry about a preferred APN:
Code:
D/Tethering( 993): chooseUpstreamType(true), preferredApn =5, got type=0
But then all other APN references while tethering is enabled point to pcweb:
Code:
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - ID : 7
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - Initiator : USER
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - Type : PRIMARY
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - NSAPI : 0
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - SAPI : 0
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - APN : pcweb.tmobile.com
D/CaptivePortalTracker( 1000): NoActiveNetworkState{ when=-1ms what=1 obj=NetworkInfo: type: mobile_dun[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: pcweb.tmobile.com, roaming: false, failover: false, isAvailable: true, smCause: 0, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
Whenever I change the value of tether_dun_required, the ID of the database entry changes. When I reboot and the value is back to 1, the ID has increased by 1, so something is restoring the value on boot up. If I tether right after changing the value to 0, but without rebooting, the phone will tether using the pcweb APN.
havanahjoe said:
The /data partition is mounted rw, so with root access any changes will be made to the file. It just seems to be restored on boot:
Code:
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
Not yet. The phone will default to using the pcweb.tmobile.com APN when enabling the hotspot, and then the change in the database file doesn't stick. I got my 3 GB tethering bucket back (new billing cycle) and even with tethering allowed, I have issues sometimes where the tethered devices get no data for a while. Usually until I change towers. I noticed that tethering fails at home, I think it's due to IPV6 tethering. The default APN for the phone does not let you change it to IPV6, and not sure what settings it is using for tethering.
I found this message in the logcat:
Code:
I/Tethering( 1000): Skip IPv6 Connectivity Check because IPv6 Tetheirng is supported.
Spelling errors aside, it looks like it doesn't care if IPV6 is enabled on the network and would tether it. When looking at the IPs assigned though, only IPV4 ones are getting assigned right now (I'll have to look at this in the places where tethering fails)
Code:
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - ID : 7
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - IPv4 Address : 100.106.90.82 IPv6 Address :
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - V4 Dns : 10.177.0.34 v6 Dns :
D/PDPContextStateBroadcaster( 1512): sendPDPContextConnected - V4 Dns : 10.176.83.140 v6 Dns :
I debugged it again and I do see an IPV6 statement
Code:
I/Tethering( 993): Skip IPv6 Connectivity Check because IPv6 Tetheirng is supported.
D/Tethering( 993): Only IPv6. but tethering uses both IPv4 and IPv6, so add default v4 dns addresses too - LinkProp:{InterfaceName: rmnet0 LinkAddresses: [2607:fb90:60a:2f6c:730c:b36f:b138:a4fa/64,] Routes: [::/0 -> fe80::3890:dff4:7a18:a991,] DnsAddresses: [fd00:976a::9,] Domains: null MTU: 1440 Stacked: [ [{InterfaceName: clat4 LinkAddresses: [192.0.0.4/32,] Routes: [0.0.0.0/0 -> 192.0.0.4,] DnsAddresses: [] Domains: null MTU: 0} ],] }
D/TetherController( 315): setDnsForwarders(0 = 'fd00:976a::9')
D/TetherController( 315): setDnsForwarders(1 = '8.8.8.8')
D/TetherController( 315): setDnsForwarders(2 = '8.8.4.4')
I see this entry about a preferred APN:
Code:
D/Tethering( 993): chooseUpstreamType(true), preferredApn =5, got type=0
But then all other APN references while tethering is enabled point to pcweb:
Code:
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - ID : 7
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - Initiator : USER
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - Type : PRIMARY
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - NSAPI : 0
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - SAPI : 0
D/PDPContextStateBroadcaster( 1512): sendPDPContextRequested - APN : pcweb.tmobile.com
D/CaptivePortalTracker( 1000): NoActiveNetworkState{ when=-1ms what=1 obj=NetworkInfo: type: mobile_dun[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: pcweb.tmobile.com, roaming: false, failover: false, isAvailable: true, smCause: 0, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
Whenever I change the value of tether_dun_required, the ID of the database entry changes. When I reboot and the value is back to 1, the ID has increased by 1, so something is restoring the value on boot up. If I tether right after changing the value to 0, but without rebooting, the phone will tether using the pcweb APN.
Click to expand...
Click to collapse
very interested to see if you've made any progress on this?
So there is the app Upsell.apk that does the actual checking. I would bet that the first thing to do would be to hack that app to always return that tethering is allowed.
Second, I'm not sure where this pcweb APN is actually stored and getting set, but wherever it is, it would need to be modified to use the regular APN.
Sent from my Nexus 7 using XDA Premium HD app
flinttownbrown said:
So there is the app Upsell.apk that does the actual checking. I would bet that the first thing to do would be to hack that app to always return that tethering is allowed.
Second, I'm not sure where this pcweb APN is actually stored and getting set, but wherever it is, it would need to be modified to use the regular APN.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I noticed the upsell.apk. It's probably being run when you get the message "Verifying your account" or whatever it says.
I would love to find where the APN is stored. I know there's /system/etc/apns-conf.xml and it contains a bunch of APNs for the different TMo MCC/MNC combinations:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
** Copyright 2006, The Android Open Source Project
**
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<!-- use empty string to specify no proxy or port -->
<!-- If you edit this version, also edit the version in the partner-supplied
apns-conf.xml configuration file -->
<apns version="8">
<apn carrier="LTE Attach APN (00101)"
mcc="001"
mnc="01"
apn=""
type="ia"
protocol="IPV6"
defaultflag="0"
/>
<apn carrier="LTE Attach APN (00102)"
mcc="001"
mnc="02"
apn=""
type="ia"
protocol="IPV6"
defaultflag="0"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="160"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="160"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="160"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="200"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="200"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="200"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="210"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="210"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="210"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="220"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="220"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="220"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="230"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="230"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="230"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="240"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="240"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="240"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="250"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="250"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="250"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="260"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV4"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="260"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="260"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="270"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="270"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="270"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="300"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="300"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="300"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="310"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="310"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="310"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="490"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="490"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="490"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="530"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="530"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="530"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="580"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="580"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="580"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="590"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="590"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="590"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="640"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="640"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="640"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="660"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="660"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="660"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile LTE"
mcc="310"
mnc="800"
apn="fast.t-mobile.com"
mmsc="http://mms.msg.eng.t-mobile.com/mms/wapenc"
type="default,supl,mms"
protocol="IPV6"
/>
<apn carrier="T-Mobile LTE Attach APN"
mcc="310"
mnc="800"
apn=""
type="ia"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="MetroPCS"
mcc="310"
mnc="800"
apn="fast.metropcs.com"
mmsc="http://metropcs.mmsmvno.com/mms/wapenc"
type="default,supl,mms,hipri"
mvno_match_data="6D"
mvno_type="gid"
/>
<apn carrier="T-Mobile Emergency"
mcc="310"
mnc="260"
apn="sos"
authtype="0"
type="emergency"
protocol="IPV6"
defaultflag="2"
/>
<apn carrier="LGE LTE Attach APN"
mcc="450"
mnc="00"
apn=""
type="ia"
defaultflag="2"
/>
<apn carrier="LGE DEFAULT"
mcc="450"
mnc="00"
apn="lte"
user="lge"
password="lge"
authtype="1"
mmsc="http://203.229.247.19/mm1"
mmsproxy="203.229.247.28"
mmsport="8000"
type="default,supl,mms,dun"
defaultflag="0"
/>
<apn carrier="LGE IPv6"
mcc="450"
mnc="00"
apn="lte6"
type="default"
protocol="IPV6"
defaultflag="0"
/>
<apn carrier="LGE IPv6 2G/3G Only"
mcc="450"
mnc="00"
apn="iv6"
type="default"
protocol="IPV6"
defaultflag="0"
/>
</apns>
When the phone boots up, it verifies the checksum of this file but it seems to leave it alone. I edited it for my MNC (260) so you'll see that mine above is set to IPV4, but when you pull up the settings on the phone, it still shows IPV6. I don't know what "T-Mobile LTE Attach APN" is, and it has an APN type of ia but no APN.
After typing all that, I decided to do a deeper search and finally found the pcweb APN. It's in the framework-res.apk
Code:
<string-array name="config_tether_apnlst">
<item>310260:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,260,,dun</item>
<item>310160:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,160,,dun</item>
<item>310200:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,200,,dun</item>
<item>310210:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,210,,dun</item>
<item>310220:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,220,,dun</item>
<item>310230:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,230,,dun</item>
<item>310240:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,240,,dun</item>
<item>310250:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,250,,dun</item>
<item>310270:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,270,,dun</item>
<item>310300:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,300,,dun</item>
<item>310310:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,310,,dun</item>
<item>310490:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,490,,dun</item>
<item>310530:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,530,,dun</item>
<item>310580:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,580,,dun</item>
<item>310590:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,590,,dun</item>
<item>310640:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,640,,dun</item>
<item>310660:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,660,,dun</item>
<item>310800:T-Mobile Tethering,pcweb.tmobile.com,,,,,,,,,310,800,,dun</item>
<item>310260gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,260,,dun</item>
<item>310160gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,160,,dun</item>
<item>310200gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,200,,dun</item>
<item>310210gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,210,,dun</item>
<item>310220gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,220,,dun</item>
<item>310230gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,230,,dun</item>
<item>310240gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,240,,dun</item>
<item>310250gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,250,,dun</item>
<item>310270gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,270,,dun</item>
<item>310300gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,300,,dun</item>
<item>310310gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,310,,dun</item>
<item>310490gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,490,,dun</item>
<item>310530gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,530,,dun</item>
<item>310580gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,580,,dun</item>
<item>310590gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,590,,dun</item>
<item>310640gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,640,,dun</item>
<item>310660gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,660,,dun</item>
<item>310800gid6D:MetroPCS Tethering,pcweb.metropcs.com,,,,,,,,,310,800,,dun</item>
</string-array>
I would think a fix is as easy as replacing the pcweb with fast. I did that and I'm working on getting the modified framework-res.apk to boot properly. I'll report back.
Update: Was able to edit the framework-res.apk file and changed all pcweb to fast. Unfortunately, tethering doesn't work. There are no errors on the phone, but there is no IP forwarding being done.
When tethering with the original framework-res (using pcweb), these come up:
D/Tethering( 1000): chooseUpstreamType(true), preferredApn =4, got type=4
I/Tethering( 1000): Skip IPv6 Connectivity Check because IPv6 Tetheirng is supported.
D/CommandListener( 315): TetherCmd::runCommand. argc: 5. argv[0]: tether
D/TetherController( 315): setDnsForwarders(0 = '10.177.0.34')
D/TetherController( 315): setDnsForwarders(1 = '10.180.12.172')
D/TetherController( 315): Sending update msg to dnsmasq [update_dns;10.177.0.34;10.180.12.172]
D/Tethering( 1000): notifying tethered with iface =rmnet1
D/Tethering( 1000): TetheredState.processMessage what=12
D/WifiStateMachine( 1000): processMsg: TetheredState
When using fast, these show up instead:
D/Tethering( 998): chooseUpstreamType(true), preferredApn =4, got type=-1
D/Tethering( 998): notifying tethered with iface =null
D/Tethering( 998): TetheredState.processMessage what=12
D/Tethering( 998): TetheredState.processMessage what=12
and repeat over and over. There is another check being done before tethering will be completed.
Not sure if you guys have followed this thread, but it may be worth keeping an eye on:
http://forum.xda-developers.com/tmobile-lg-g3/help/wifi-tether-router-root-t2826251
Tethering is confirmed by multiple users (including me) to be working using WiFi Tether Router by Fabio Grasso from the Play Store.
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter&hl=en
This is the same app that "Semantics" posted on earlier in this thread.
orbitalcomp said:
Not sure if you guys have followed this thread, but it may be worth keeping an eye on:
http://forum.xda-developers.com/tmobile-lg-g3/help/wifi-tether-router-root-t2826251
Tethering is confirmed by multiple users (including me) to be working using WiFi Tether Router by Fabio Grasso from the Play Store.
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter&hl=en
This is the same app that "Semantics" posted on earlier in this thread.
Click to expand...
Click to collapse
I tried the app when Semantics suggested it and could not get it to work. I was only trying it within my 15 minute trial so when it didn't work I just got a refund. Good to know it works. For $2.50, it's worth not bothering trying to get this stock stuff to work.
havanahjoe said:
I tried the app when Semantics suggested it and could not get it to work. I was only trying it within my 15 minute trial so when it didn't work I just got a refund. Good to know it works. For $2.50, it's worth not bothering trying to get this stock stuff to work.
Click to expand...
Click to collapse
I assume this app works without changing to the pcweb APN, right? Will it also work for USB tethering?
Sent from my LG-D851 using XDA Premium HD app
flinttownbrown said:
I assume this app works without changing to the pcweb APN, right? Will it also work for USB tethering?
Sent from my LG-D851 using XDA Premium HD app
Click to expand...
Click to collapse
I think it's WiFi only, hence the name. I don't see any USB options.
It's a HUGE battery hog on my G3 though. Anyone notice that? I also heard back from the developer about Tasker:
Hello,
Other users have asked for this
Unfortunately, this app is not compatible with Tasker
Tasker is not compatible with the app that verify the Google License
I'm sorry
Regards
Fabio
Click to expand...
Click to collapse
I'm not quite sure he knows what intents/tasker integration do, or, I don't understand why his licensing app would be incompatible with Tasker. Even though it works, I'd much rather get the built-in tether function working so I can use Tasker and not waste so much battery. I'll continue to play with that and see if I can get it to work.
$100 to whoever can hack stock tethering.
Edit: offer good for one week, or until CM for the G3 arrives, whichever is first
Sent from my Nexus 7 using XDA Premium HD app
flinttownbrown said:
$100 to whoever can hack stock tethering.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Why not bypass it? Isnt the goal to use regular data over hotspot data?
Sent from my amazing LGG3!
flinttownbrown said:
I assume this app works without changing to the pcweb APN, right? Will it also work for USB tethering?
Sent from my LG-D851 using XDA Premium HD app
Click to expand...
Click to collapse
Just download pdanet for USB tether, works like a charm and you can change a setting that hides tether usage so you never get upsell pages and don't need user agent switchers.
Semantics said:
Just download pdanet for USB tether, works like a charm and you can change a setting that hides tether usage so you never get upsell pages and don't need user agent switchers.
Click to expand...
Click to collapse
Don't you need to install something on your computer in order to use that? I can't do that on work devices, it's not allowed... It was enough of a pain to get the LG drivers installed
Sent from my SGH-M919 using XDA Premium HD app