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
A number of people have problems with their Nexus 5X roaming on CDMA when using Project Fi.
This issue occurs in areas of weak/no cell coverage for Sprint. The device simply will not roam on CDMA. At the same location it has been reported that the 6 and 6P roam with no problems so the issue seems to be with the 5X only.
When Project Fi activates it removes the options for Settings>Wireless & Networks>More>Cellular networks. The only options that show up are for data roaming.
Without this option available the there is no way to view System Select and change roaming mode from Home to Automatic. So.....the phone will not roam.
I have found a partial solution but it is far from perfect. It involves editting one word in one line of code in an android manifest file.
https://app.box.com/s/c3vfaecmrjugevgx37uklu1w5hm3611j
Sweet! Can you detail exactly what you changed? Doing so would be a massive help.
Thanks,
ealbitz
ealbitz said:
Sweet! Can you detail exactly what you changed? Doing so would be a massive help.
Thanks,
ealbitz
Click to expand...
Click to collapse
/system/tycho/project fi
Line 40
<uses-feature android:name="android.hardware.telephony" android:required="false"/> TO: TRUE
That change allows the phone to display the cellular settings and change from home to auto and global.
But.....there are other problems created by that change. WiFi calling stopped working for one.
I'm trying to locate a settings file that would control the telephony but no luck yet.........like a blind hog.....I got lucky once.
This is basically what I did to get the settings to stick and allow roaming on cdma:
1. Copy file /system/tycho/Project Fi to PC
2. Decompile
3. Change Line 40 :
uses-feature android:name="android.hardware.telephony" android:required="false"
To “true”
4. Recompile
5. Copy New file to phone
6. Reboot Recovery
7. Use File manager to open /system/tycho/
8. Rename existing project fi to project fi old
9. Copy and paste new file into the tycho folder
10. Reboot
11. Reinstall project fi app
12. Check settings in cellular
Thanks! There are a number of people that would be interested in this workaround that don't have the skills/knowledge you obviously have.
It appears you have rooted phone and have access to /system directory as well as decompile/compile tools. Would you be willing to expand on your instructions to add setup and prerequisites to do what you did? I have development experience, just not much with android as of yet. If I can get the process working, I can assist the others I've been in contact with on the google product forum. (I have Android Studio installed and have compiled a couple of apps. I also have decades of development expertise so once I get the basics down, I'm off and running.)
Thanks,
Toby
Known Issues So Far
Wifi Calling Not working
CDMA Calling Not working when WiFi is ON.
Need Testing:
GSM Calling
Wifi Calling on GSM
Check GSM APN settings. May need to add APN info for TMobile
It appears the the Nexus 5X has a version of PFi app installed in the /system/tycho folder. This is named project fi but shows up as tycho.apk when copied to PC.
This app remains installed even when the PFi app from the Play Store is uninstalled so it must be originally in the Android image. This could be due to the fact that the phone was bought thru Project Fi. Other phones bought thru Google may not have this app. Don't know.
Theory: The P6 may have some difference in the original project fi app that allows it to roam. The play store versions probably don't make any/many changes to this base app when the are installed.
So....does anyone have the original project fi app from a 6P phone bought thru Project Fi?
It would be good to compare that file with the one from the 5X.
tobewan said:
Thanks! There are a number of people that would be interested in this workaround that don't have the skills/knowledge you obviously have.
It appears you have rooted phone and have access to /system directory as well as decompile/compile tools. Would you be willing to expand on your instructions to add setup and prerequisites to do what you did? I have development experience, just not much with android as of yet. If I can get the process working, I can assist the others I've been in contact with on the google product forum. (I have Android Studio installed and have compiled a couple of apps. I also have decades of development expertise so once I get the basics down, I'm off and running.)
Thanks,
Toby
Click to expand...
Click to collapse
I'm no expert...just have an inquiring mind!!
My phone is rooted with TWRP recovery installed. Running Pure Nexus rom now.
I am using AdvancedAPKTool to decompile and root around.
Another mod attempt
Tried a different mod on a line of code that was suggested by tobewan with some better results. Not great but better. Still some problems
1. Decompile Tycho 1.4
2. Modify line 78 in NovaCarrierService.smali located in Tycho.apk \smali\com\google\android\apps\tycho\services
3. Uninstall Project Fi app from settings/apps/project fi
4. Mod Tycho 1.4 to allow ‘show’ instead of ‘hide’ in line 78 const-string v0, "hide_carrier_network_settings_bool"
5. Rename original tycho in /system/app/tycho to bak
6. Paste modded apk into tycho folder
7. Reboot phone
• Settings now avail in cellular networks for cdma roaming home/auto
• Project Fi app crashing often. No calling or texts.
• Install Project Fi C.1.0.9-all and crashes stop.
• CDMA calling with WiFi on okay. No issues when not roaming.
• When phone roams in cdma mode: inbound calls ok
• Outbound has long delay when roaming then calls but shows the #200 that is in Phone Info on receiving end phone
• Inbound texts good
• Outbound texts slow (about 3-5 mins) but make it thru.
• Switching to Tmobile GSM works but somewhat slow with Fi switcher and cellular network settings are available
• GSM connect to LTE here ok. All GSM signals here are weak from AT&T and TMobile.
• PFi activation works and cellular settings are still available.
• Wifi calling not working outbound or inbound. Inbound goes to VM. Nothing out.
• Auto switching works to go back to Sprint when TMobile signal drops. Some failure msgs from Fi Switcher but switches happen.
• When mode changes back to CDMA have to go back to cellular settings and change to auto
• Roaming still works.
• CDMA data seems okay.
• CDMA Signal has to be very weak before switching to roaming when wifi is on. This is probably normal.
• Wifi off and switch to roaming occurs fast.
Will try to get some video.
rezz93 said:
It appears the the Nexus 5X has a version of PFi app installed in the /system/tycho folder. This is named project fi but shows up as tycho.apk when copied to PC.
Click to expand...
Click to collapse
I think you are just stating for the record, not saying it is something significant, but all project fi apps have fully qualified name com.google.android.apps.tycho.
https://play.google.com/store/apps/details?id=com.google.android.apps.tycho
rezz93 said:
This app remains installed even when the PFi app from the Play Store is uninstalled so it must be originally in the Android image.
Click to expand...
Click to collapse
You are correct, it is in the original MDA89E android image, but it is disabled by default so it won't show up for most people unless they go in settings->app to enable it. I remember I was on WiFi and didn't insert the Project Fi SIM for a couple of weeks and Project Fi was disabled the whole time. I suspect, but don't know for sure, that when you insert the Project Fi SIM, it enables the Project Fi app. Personally I enabled manually and downloaded the latest Project Fi app prior to inserting the Project Fi SIM so I can't say for sure whether Project Fi SIM would have enabled the app on its own.
rezz93 said:
This could be due to the fact that the phone was bought thru Project Fi. Other phones bought thru Google may not have this app. Don't know.
Click to expand...
Click to collapse
I've heard some Project Fi reps claim they have a special version of 5x, but the generic factory restore system.img for MDA89E has tycho so I think all 5x phones have it, it is just disabled by default so most don't notice it.
rezz93 said:
Theory: The P6 may have some difference in the original project fi app that allows it to roam. The play store versions probably don't make any/many changes to this base app when the are installed.
Click to expand...
Click to collapse
I am not sure, but I thought 6P folks had the same problem and it was only Nexus 6 users that didn't. I didn't follow this issue that closely so I could be wrong.
Thanks for working on this.
I just got thru doing a complete recovery, starting with stock 6.0.1 due to snowballing problems that began with the camera not working any more.
When it booted and was setup I stopped Play Store auto updates and then checked the /system/app/tycho folder. There were 2 items in that folder: Tycho.apk and folder 'oat'. The folder had sub folder arm64 and in it was file 'Tycho.odex'
The phone activated PFi and only the original 1.4.0.7 file was on the phone. I'm still running that version and haven't got the Playstore update yet.......so it sounds like it was ready to go on PFi when the phone left Project Fi. Not sure if that even matters though unless there is some major differences between the two.
Thank you for the detailed responses. Very interesting stuff in this PFi thing!!
More later.
rezz93 said:
checked the /system/app/tycho folder. There were 2 items in that folder: Tycho.apk and folder 'oat'. The folder had sub folder arm64 and in it was file 'Tycho.odex'
The phone activated PFi and only the original 1.4.0.7 file was on the phone. I'm still running that version and haven't got the Playstore update yet.......so it sounds like it was ready to go on PFi when the phone left Project Fi. Not sure if that even matters though unless there is some major differences between the two.
Click to expand...
Click to collapse
So it sounds to me that having the Project Fi SIM inserted enables the otherwise disabled Project Fi (tycho) app as I have factory restored MDA89E many times with the Project Fi SIM not inserted and tycho has always come up disabled by default.
The oat folder is the pre-compiled version of tycho.apk. It can be generated from tycho.apk
Sounds about right.
The problem as I see is the missing settings>wireless>more>cellular>home/auto
The phone stays in the home mode and will not roam on cdma. I'm pretty sure it has roamed on GSM though....
Changing the setting in the tycho xml file or in the other location to enable those network settings causes things to break. So even though the phone roams with this change the routing of calls is affected. In the phone info tool *#*#4636#*#* show 2 different phone numbers. On GSM mode the actual # of the phone is shown. In CDMA however, there is a completely different # that is in the same area code as the other #.
So it seems that changing the phone roaming mode from home to auto affects the way cdma calls are routed and wifi calling also affected.
Also, the original setup allows the tycho app to use its own settings instead of the phone network settings:
Code:
<uses-feature android:name="android.hardware.telephony" android:required="false"/>
Changing from home to auto then seems to cause conflicting settings and problems.
Where are the actual phone network settings stored in android?? I haven't found them yet. Not sure what would happen if they were changed to match whatever tycho uses.
A pure guess on my part, but I think you have stumbled on why the selection is disabled. Sounds like it screwed up something else when selected, so their fix was to disable it since CDMA roaming affects relatively few people. Functional wifi calling is way more important than CDMA roaming as an example.
I think they're going to have to work out a lot of bugs by the time they release (hopefully) a new set of phones later this year. I bought the inexpensive 5X in anticipation of upgrading when their next phones come up. Hopefully, with a year or whatever of actual experience from users, the next ones are more functional out of the box.
rezz93 said:
The problem as I see is the missing settings>wireless>more>cellular>home/auto
Click to expand...
Click to collapse
Honestly I think they intentially disabled the default UI and this isn't a bug from their standpoint, though they could have disabled the UI and left CDMA roaming set to auto.
rezz93 said:
Changing the setting in the tycho xml file or in the other location to enable those network settings causes things to break. So even though the phone roams with this change the routing of calls is affected. In the phone info tool *#*#4636#*#* show 2 different phone numbers. On GSM mode the actual # of the phone is shown. In CDMA however, there is a completely different # that is in the same area code as the other #.
Click to expand...
Click to collapse
Are you saying there is one number in CDMA 4636 but it doesn't match your GSM 4636 phone # or are you saying there are 2 phone #s listed in the CDMA 4636?
My stock ProjectFi setup has a different phone # under CDMA 4636 than my actual phone # (actual # shows up in GSM 4636) so that part seems normal.
rezz93 said:
Where are the actual phone network settings stored in android?? I haven't found them yet. Not sure what would happen if they were changed to match whatever tycho uses.
Click to expand...
Click to collapse
Have you looked in /data/data/com.android.phone (files and shared_prefs) for the xml files?
Dynamic stuff is probably in some sqlite db somewhere.
sfhub said:
Honestly I think they intentially disabled the default UI and this isn't a bug from their standpoint, though they could have disabled the UI and left CDMA roaming set to auto.
Are you saying there is one number in CDMA 4636 but it doesn't match your GSM 4636 phone # or are you saying there are 2 phone #s listed in the CDMA 4636?
My stock ProjectFi setup has a different phone # under CDMA 4636 than my actual phone # (actual # shows up in GSM 4636) so that part seems normal.
Have you looked in /data/data/com.android.phone (files and shared_prefs) for the xml files?
Dynamic stuff is probably in some sqlite db somewhere.
Click to expand...
Click to collapse
In the GSM mode of phone info the phone # displayed is the actual # of the phone.
In the CDMA mode the phone # is a completely different #. Same area code of the actual but different 7 digits.
When calling that CDMA # from another phone it rings about 10 times then goes silent.
Calling it from the 5X it goes to voice mail system and entering my pin allows me to listen to msgs.
There is a 3rd # also in the phone settings>about phone>status>phone>status>imei information listed under "Min". Same area code but completely different #.
When calling this # from land line it goes to voice mail...but that VM does not say Project Fi customer like the regular VM does.
Calling this # from 5X goes to same VM system. Leaving a msg does not come to my phone voice mail.
This sounds confusing because I'm confused.
My guess is this all has something to do with Google Voice.
Looking in /data/data/com.android.phone there are 4 folders. cache, code_cache, files and shared_prefs. The 2 cache folders are empty.
The files folder has 4 xml files.
/data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig-89011201004001880640.xml
/data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig-8901260971103773923.xml
/data/data/com.android.phone/files/carrierconfig-com.google.android.apps.tycho-89011201004001880640.xml
/data/data/com.android.phone/files/carrierconfig-com.google.android.apps.tycho-8901260971103773923.xml
The shared prefs has 2 xml files.
/data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
/data/data/com.android.phone/shared_prefs/com.android.phone_preferences.xml
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<boolean name="_has_set_default_values" value="true" />
</map>
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="carrier_alphtag_8901260971103773923"></string>
<string name="vm_number_key_cdma0">+1xxxxxxxxxx</string>
<string name="carrier_subscriber_8901260971103773923">310260970377392</string>
<string name="operator_branding_89011201004001880640">Fi Network</string>
<string name="preferred_network_mode_key">10</string>
<string name="carrier_subscriber_89011201004001880640">310120400188064</string>
<string name="operator_branding_8901260971103773923">Fi Network</string>
<string name="build_fingerprint">6.0.1-20160506</string>
<string name="carrier_number_8901260971103773923">+1xxxxxxxxxx</string>
<string name="carrier_number_89011201004001880640">+1xxxxxxxxxx</string>
<string name="vm_number_key0">+1xxxxxxxxxx</string>
<string name="network_selection_key1"></string>
<string name="network_selection_short_key1"></string>
<int name="curr_subid0" value="1" />
<string name="vm_sim_imsi_key0">310120400188064</string>
<string name="carrier_alphtag_89011201004001880640"></string>
<string name="network_selection_name_key1"></string>
<string name="enabled_networks_key">10</string>
</map>
The xxx #s are my phone number
The other 4 files have config info as well. Here's an example of one carrier config:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<carrier_config>
<package_version>1</package_version>
<bundle_data>
<boolean name="dtmf_type_enabled_bool" value="true" />
<int name="smsToMmsTextThreshold" value="6" />
<boolean name="enableSMSDeliveryReports" value="false" />
<int name="maxMessageTextSize" value="-1" />
<boolean name="supportMmsContentDisposition" value="false" />
<boolean name="allow_non_emergency_calls_in_ecm_bool" value="false" />
<boolean name="voicemail_notification_persistent_bool" value="true" />
<boolean name="support_swap_after_merge_bool" value="false" />
<int name="recipientLimit" value="40" />
<int name="maxImageHeight" value="1944" />
<boolean name="enableMMSDeliveryReports" value="false" />
<boolean name="apn_expand_bool" value="false" />
<int name="maxSubjectLength" value="80" />
<string name="httpParams">X-MDN: ##LINE1##|Proxy-Authorization: Basic ##NAI##</string>
<boolean name="show_cdma_choices_bool" value="true" />
<boolean name="carrier_settings_enable_bool" value="true" />
<string name="emailGatewayNumber">6245</string>
<boolean name="use_hfa_for_provisioning_bool" value="true" />
<int name="maxMessageSize" value="1048576" />
<string name="naiSuffix">:pcs</string>
<boolean name="enableMMSReadReports" value="false" />
<int name="maxImageWidth" value="2592" />
<int name="volte_replacement_rat_int" value="6" />
<boolean name="enabledMMS" value="true" />
<boolean name="enableMultipartSMS" value="true" />
</bundle_data>
</carrier_config>
Here's an example of the carrier tycho files:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<carrier_config>
<package_version>21300</package_version>
<bundle_data>
<boolean name="hide_sim_lock_settings_bool" value="true" />
<int name="vvm_port_number_int" value="0" />
<string name="vvm_destination_number_string"></string>
<boolean name="force_home_network_bool" value="true" />
<boolean name="enableSMSDeliveryReports" value="false" />
<string name="default_sim_call_manager_string">com.google.android.talk/com.google.android.apps.hangouts.telephony.TeleConnectionService</string>
<boolean name="allow_non_emergency_calls_in_ecm_bool" value="true" />
<boolean name="ignore_sim_network_locked_events_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="false" />
<string name="carrier_vvm_package_name_string"></string>
<boolean name="carrier_volte_available_bool" value="false" />
<string name="vvm_type_string"></string>
<string name="emailGatewayNumber"></string>
<boolean name="hide_carrier_network_settings_bool" value="true" />
<boolean name="require_entitlement_checks_bool" value="false" />
</bundle_data>
</carrier_config>
I think the MIN # is used for intermediate phone call routing. MIN # used to be the same as your Phone # before number portability.
Our phone #s are from TMobile's phone # pool. I wouldn't be surprised if Google is using the MIN # to do some special routing into Sprint's system as Project Fi members, our "phone #" needs to be good on to separate cell phone network infrastructure.
I am not exactly clear which method they are using to pull that off but there is some stuff going on underneath the hoods.
For example if we get an incoming call, how does it know which network we are on, do our phones register that information when they switch networks or is Fi just taking advantage of Google Voice infrastructure to call multiple #s for a single incoming. If the latter, do we have some "shadow" phone # on Sprint tied to our TMobile phone #.
The Tycho xml files look like configuration for the Project Fi app that you edited in the apk. I'm curious, what happens if you change the setting (in the xml file found in the /data directory rather than the one in the apk) to false?
<boolean name="hide_carrier_network_settings_bool" value="true" />
does that have different behavior than changing the setting in the .apk and repackaging? I know sometimes when the package signatures get messed up due edits, apps sometimes behave differently than when they were originally packaged.
The Tycho xml files look like configuration for the Project Fi app that you edited in the apk. I'm curious, what happens if you change the setting (in the xml file found in the /data directory rather than the one in the apk) to false?
<boolean name="hide_carrier_network_settings_bool" value="true" />
does that have different behavior than changing the setting in the .apk and repackaging? I know sometimes when the package signatures get messed up due edits, apps sometimes behave differently than when they were originally packaged.
Click to expand...
Click to collapse
You must have read my mind. Just tried that and more.
Code:
FILE: \com.android.phone\files\carrierconfig-com.android.carrierconfig-89011201004001880640.xml
Line 16 <boolean name="apn_expand_bool" value="false" /> Change to True
FILE: \com.android.phone\files\carrierconfig-com.google.android.apps.tycho-89011201004001880640.xml
Line 8 <boolean name="force_home_network_bool" value="True" /> Change to False
Line 17 <boolean name="hide_carrier_network_settings_bool" value="true" /> Change to False
FILE: \com.android.phone\files\carrierconfig-com.android.carrierconfig-8901260971103773923.xml
No changes
FILE: \com.android.phone\files\carrierconfig-com.google.android.apps.tycho-8901260971103773923.xml
Line 8 <boolean name="force_home_network_bool" value="true" /> Change from True to False
Line 18 <boolean name="hide_carrier_network_settings_bool" value="true" /> Change to False
FILE: com.android.phone\shared_prefs\_has_set_default_values.xml No Changes
FILE: \com.android.phone\shared_prefs\com.android.phone_preferences.xml
RENAME EXISTING FILES TO BAK AND PASTE MODDED FILES INTO FOLDERS
Changed files, rebooted, no change in cellular settings or roaming.
Uninstalled the PFi app from the play store and reverted back to the original one in the tycho folder. Can now change the home/auto and get some roaming on cdma.
Rebooted and activated PFi. Settings now gone. Checked the modded files and they were back to original.
That one phone # may be my old Google Voice #....didn't use it much so don't remember. Somehow the numbers are routed together.
am not exactly clear which method they are using to pull that off but there is some stuff going on underneath the hoods]
Click to expand...
Click to collapse
Under the hood you say??? Sounds more like PFM to me!
and the tycho app seems to do the magic.
News from Google
Here's a post from the Project Fi forum related to this topic:
Hi everyone,
Yes we are still investigating this issue and it's a high priority for the team.
As many users have noted on this thread, this is occurring because the CDMA settings inside the Nexus 5X device are not adjusting properly and are reverting to a "Home" state instead of an "Automatic" state. We're actively looking into how we can change this. There aren't any known workarounds that we've identified but we're investigating how to resolve this as quickly as possible (it's not a simple fix unfortunately). Thanks for your patience in the meantime, and I'll post back once I have another update.
- Jordan
Project Fi Community Manager
Click to expand...
Click to collapse
rezz93 said:
Here's a post from the Project Fi forum related to this topic:
Click to expand...
Click to collapse
If the issue is just changing the default setting from Home to Automatic I can't believe it is really that difficult for them to fix.
Perhaps there are other issues though.
Yes, the problem does appear deeper than just changing a setting.
My attempts to force roaming seem to indicate a much more complicated problem that affects the phone's routing of calls when in automatic mode CDMA.
Hopefully all this can be resolved soon by Google. I really like the phone and wifi calling keeps me connected at home where the GSM and CDMA signals are weak. There is a very strong CDMA signal here but it requires roaming to work in order to use it.
Overall, this issue is not a deal breaker for me with Project Fi, but a fix of the problem would make a great idea for a phone and phone service live up to its potential.
Posts on the PFi forum indicate that the problem is just with the 5X, not PFi's system, since its reported that the N6 and N6P both function well on CDMA and roaming.
So, maybe the Big G will come through and get this straightened out.