Develop Bugs

[Q] MMS APN Settings

I am running CyanogenMOD 6.1 for the CDMA Desire and I was wondering if anyone knows the APN settings for MMS on Cellcom (from Wisconsin not israel)
I did backup the settings using a market app but they don't seem to work
Code:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="3">
<apn name="CDMA" numeric="00000" mcc="000" mnc="00" apn="0" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="" mmsc="" type="*" />
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="80" mmsprotocol="2.0" mmsc="http: / / mms.cellcom.com / cellcom / mms.php" type="mms" />
<apn name="Android" numeric="310995" mcc="310" mnc="995" apn="internet" user="*" server="*" password="*" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="null" />
</apns>

try to search "APN" in market. It helps you to set the APN, as well as the mms setting~~

Cellcom HTC Desire
I'm having the same problem. Did you ever find a fix?

Hey, Anyone figure this out? Damn Cellcom has to ruin this phone for me!!!

bump, anyone ever find because i have not found on google

I know it's an old thread, but a common issue. And comes up at the top of searches yet, relating to cellcom (wisconsin) and APN settings. So here's what I got....
I was told by Cellcom tech support that these are the only settings you need to fill out. Particularly if you are using a 3rd party app. Although you can just call them to get the APN settings. They have no problems giving out that information. She specifically said that fields such as proxy, login, pass, etc are not set for cellcom's network/devices. Which is unlike other carriers, such as USCC, where you need those items for MMS to work. Don't waste your time at the store, call 611 and ask about it. They'll transfer you to a tech.
MMSC http://mms.cellcom.com/cellom/mms.php-Cellcom
MCC 300
MNC 610

I got the APN to work with Cellcom.... MMS works again! Android 6.0.1
The facts:
Moto Maxx XT1250 from Cellcom (Wisconsin) not Israel
CyanogenMod 13.0-20161221 (Andriod 6.0.1) because Cellcom stopped supporting the phone and stopped at Android 5.0.1
All this broke the APN so no MMS. Called their support and they gave me the APN settings. However when I entered the MMC and MNC it broke again.
The fix:
Go into settings and find your APN modifications.
Locate the VZWINTERNET APN settings or make your own and modify it to these settings:
Name = Cellcom
APN = VZWINTERNET
Proxy = Not set
Port = Not set
Username = Not set
Password = Not set
Server = Not set
MMSC = http: // mms.cellcom.com/ cellom /mms. php ( Do not have spaces. XDA won't let me post this as it thinks it is a link. Put this as one line!)
MMS proxy = Not set
MMS port = Not set
MCC = 311 (this is the default, do not change it, this is what will break the APN profile. Cellcom Says to make it 310 but leave it)
MNC = 480 (this is the default, do not change it, this is what will break the APN profile. Cellcom Says to make it 600 but leave it)
Authentication type = Not set
APN type = default,mms,dun,supl
APN protocol = IPv4/IPv6
APN roaming protocol = IPv4/IPv6
APN enable/disable = will be grayed out and cannot be modified
Bearer = Unspecified (you must turn off all the others and only check the box for Unspecified)
MVNO = SPN
MVNO value = Cellcom (this will auto populate when you change the MVNO to SPN)
Press the 3 dots upper right and click save. Reboot and enjoy MMS again!
I tested with the Cyanogen messaging app, Googles Messaging app, and Google Hangouts and the all work sending photos and multiple people texting.
Now will this work for other handsets or ROMs? I do not know. Please reply to the post with your results.

jellybean AOKP UNOFFICIAL November 3

hey, just a little something I cooked up using source found here http://aokp.co/index.php/news
aokp for the sgh i957,
choose mtp or camera connection once connected
paid apps work
Mtp works with win 7 and ubuntu
Mass storage does not work so well, just there for testing
Download:
http://goo.im/devs/damantea/AOKP_UNOFFICIAL
Gapps:
http://goo.im/devs/damantea/Gapps
Please factory reset before install
issues:
usb devices don't have an unmount option in task tray
nfc no work

Wow! I love aokp, rockin it on my skyrocket for months now. Can't wait to try this.
Sent from my SGH-I727 using xda premium

Sweet!
Gotta try it.

Wow, ROM flies!!!!!, feels like brand new tablet. Still testing out everything, but so far so good. Android is so awesome because of the great devs, thanks!!!

Only issues so far are MHL out doesn't work (anyway to get this working?) and the touch sensitivity seems off. Have to press hard and hold links in browser for example. Other than that, this ROM is awesome!

Can i use this rom in P7320 LTE 8.9 tab ?
What should work, and what shouldn't?

VTEChump said:
Only issues so far are MHL out doesn't work (anyway to get this working?) and the touch sensitivity seems off. Have to press hard and hold links in browser for example. Other than that, this ROM is awesome!
Click to expand...
Click to collapse
You try calibration?
Sent from my SGH-I727 using xda premium

How about storage? Can i use my 16GB internal storage i p7320 ?

I am guessing this can't be used on the 7320
Sent from my SGH-I727 using xda premium

I can't get cellular data to work for some reason.
Anybody else?

neubauej said:
I can't get cellular data to work for some reason.
Anybody else?
Click to expand...
Click to collapse
Try rebooting without a charger connected and make sure wifi is off. If that doesnt work, wipe and reinstall the ROM. If THAT doesnt work, maybe try flashing a skyrocket modem similar to the CM10 stuff.

Tried all but a skyrocket modem.
Ill give that a go.
I show bars of service, shows att, then states no internet connection.
Imei is still good, and stock or cm10 work.
Weird..

neubauej said:
Tried all but a skyrocket modem.
Ill give that a go.
I show bars of service, shows att, then states no internet connection.
Imei is still good, and stock or cm10 work.
Weird..
Click to expand...
Click to collapse
What is your APN settings?

orlandoxpolice said:
What is your APN settings?
Click to expand...
Click to collapse
My APN settings were incorrect.
Doh!
Thanks.

neubauej said:
My APN settings were incorrect.
Doh!
Thanks.
Click to expand...
Click to collapse
No problem. It may be helpful to post the settings here for other users who may have the same issue.
Code:
Name: Broadband
APN: Broadband
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: Not Set
MMS Proxy: Not Set
MMS Port: Not Set
MCC: 310
MNC: 410
Authentication Type: Not Set
APN Type: Not Set
APN Protocol: IPv4
Bearer: Unspecified

Default APN settings are determined by system/etc/apns-conf.xml. The specific ones used are determined by the SIM's MCC/MNC settings, in the case of an ATT SIM, 310/410.
The default file has 310/410 set up like:
Code:
<apn carrier="ATT" mcc="310" mnc="410" apn="wap.cingular" user="[email protected]" mmsc="http://mmsc.cingular.com" mmsproxy="wireless.cingular.com" mmsport="80" type="default,supl,mms" />
<apn carrier="ATT LTE" mcc="310" mnc="410" apn="pta" mmsc="http://mmsc.mobile.att.net" mmsproxy="proxy.mobile.att.net" mmsport="80" type="default,supl,mms" />
<apn carrier="StraightTalk ATT" mcc="310" mnc="410" apn="att.mvno" mmsc="http://mmsc.cingular.com" mmsproxy="66.209.11.33" mmsport="80" type="default,supl,mms" />
The first and last line there can be nuked, and the ATT LTE line like:
Code:
<apn carrier="ATT LTE" mcc="310" mnc="410" apn="Broadband" mmsc="" mmsproxy="" mmsport="" type="" />
That'd result in working connectivity for users with a data-only LTE plan from ATT, as usually sold with these devices.
The quirk I'm trying to figure out, though, is how to get LTE. The RIL seems to default to WCDMA preferred (3G), but AOKP's settings don't seem to provide the selector to select the "other" setting, LTE / WCDMA, which enables LTE.
Probably just a toggle to flip in framework-res or some other similar config setting area... finding it is the fun part!

Can anyone confirm/deny if the touch screen seems wonky?

orlandoxpolice said:
You try calibration?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Calibration option is greyed out and not selectable.

VTEChump said:
Calibration option is greyed out and not selectable.
Click to expand...
Click to collapse
you try wiping and reflashing?

any bugs
I am really curious to see if I should flash this (getting tired of honeycomb constant restrictions and constant crashings)
Are there any bugs or any features not working at the moment?
Thanks

[Q] Mobile Network not connecting: LU6200

Hi,
I installed YongShi's ROM last night. (http://forum.xda-developers.com/showthread.php?t=1705667) It's a nice ROM, despite the bloatware still being in /system/apps, though they aren't installing.I edited build.prop to change the language, region, and time zone (4 lines). Later, I try to go online w/o wifi, but there's no mobile network. 3g/4g is connected (mobile data on) but it doesn't detect a network, even though the plan has 4g. I did a factory reset, just in case, but no dice. Does anyone have any ideas, how to make the mobile network work? Any help'd be appreciated.
I've also tried to re-flash stock 167 (http://main.develoid.com:81/lg/Optimus LTE/LG-LU6200/Stock Firmware/LU620167_00.kdz) but the KDZ_FW_UPD program had a problem at unpacking the kdz file (or something like it). I tried re-flashing via the LG Support Tool, but it pauses at 4%, right when it goes into download mode. FlashTool (UpTestEX.exe) also crashes when checking for mobile phone info., so I can't use that.
I know the ROM is customized for Shanghai, so maybe something's off in /system? BTW, I'm in Korea and the phone's under an LG plan, if that helps.

all you would have had to do was add your apn settings and your network would have worked

KronicSkillz said:
all you would have had to do was add your apn settings and your network would have worked
Click to expand...
Click to collapse
haven't had a chance to get at it (it's the gfs). I've been looking for specific lg u+ apn info, but can't seem to find any.
so, to do this, are either of these methods that I found on the web valid? (I only have a flip phone and a wifi only device)
dial *#*#4636#*#* and select LTE only should the option appear
or
Type in-
Name: vpn APN
APN Type: default
under APN in Wireless and Network?
==
figures. I find relevant info out after posting. anyway, I found these settings from a github: (https://gist.github.com/imnuts/4319762)
<!--LG U+ Multi-PDN Requirement -->
<apn carrier="LG U+"
mcc="450"
mnc="06"
apn="internet.lguplus.co.kr"
type="default,supl"
protocol="IPV4V6"
/>
<apn carrier="LG U+ MMS"
mcc="450"
mnc="06"
apn="ims.lguplus.co.kr"
type="ims,mms"
protocol="IPV4V6"
mmsc="http://omammsc.uplus.co.kr:9084"
/>
<apn carrier="LG U+ Tethering"
mcc="450"
mnc="06"
apn="tethering.lguplus.co.kr"
type="dun"
protocol="IPV4V6"
/>
<apn carrier="LG U+ Roaming"
mcc="450"
mnc="06"
apn="wroaming.lguplus.co.kr"
type="default,mms,dun,supl"
protocol="IPV4V6"
mmsc="http://omammsc.uplus.co.kr:9084"
carrier_enabled = "false"
/>
<!--LG U+ Multi-PDN Requirement -->
Is this saying that I need to make four separate APNs, each with the above info entered via settings->wireless etc etc OR should I edit the apns-conf.xml and the /apps/common/res/apns.xml directly? also, the "wroaming"; is that a typo or should that be entered as written? I'm not a stranger to Android, but I'm green w/r/t 4G and LTE and the like...so the help is appreciated. Thanks!
===
also: when we (gf and I) talked on the phone, the service seemed...really bad. dropped several times. can I assume that she's stuck on the 2G CDMA line and can use the *#*#4636#*#* set preferred network type to...well, ok since I haven't seen or done this before and won't have internet whiel doing this, I know that the 2G Network is CDMA 800 / 1900, the 3G Network CDMA2000 1xEV-DO, HSDPA 2100 and the 4G Network LTE 800. I read that "LTE only" is data only...so...?

[Q] Where are APN - Access Point Names Menu Settings? LTE

Settings>Wireless & Networks>More...>Mobile Networks>Access Point Names
This menu is missing from the KVT49L deb 4.4.2 version, I have seen screenshots of 4.3 Nexus 7 LTE with this menu.
My device cannot connect tethering, VPN or MMS messages, I think due to a faulty or purposely disabled APN setting.

Sorry, more info; I have unlocked, rooted, installed the xposed framework and the SMS mod.
In Hangouts from the SMS settings, the APN settings are visible, but cannot be changed. When I make a change they disappear, and if I create a new one it doesn't save. Reset to defaults appears to read the Android APN settings and restore them back.
Timestamp Socket Connection Test HTTP Connection Test Network Type Mobile Data Network Type SIM State Is Connected Is Roaming Is Available Is Failover Data Activity Data State Extra Info SIM Operator SIM MCC SIM MNC Network Operator Network MCC Network MNC Is Network Metered Cell Signal Strength (0-4) Cell Signal Strength (dBm) ASU Level
3/13/2014 15:51 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -98 42
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -99 41
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -99 41
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -99 41
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -99 41
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -99 41
3/13/2014 15:50 PASS PASS mobile/LTE LTE READY 1 0 1 0 INOUT CONNECTED VZWINTERNET 311 480 Verizon Wireless 311 480 1 0 -98 42

Under /system/etc/apns-conf.xml I found the following. I am going to try changing the information here.
<apn carrier="Verizon Internet"
mcc="310"
mnc="004"
apn="VZWINTERNET"
type="default,supl"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="Verizon FOTA"
mcc="310"
mnc="004"
apn="VZWADMIN"
type="fota"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="Verizon Wireless"
mcc="311"
mnc="480"
apn="vzwinternet"
type="default,supl"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
authtype="1"
/>
<apn carrier="Verizon FOTA"
mcc="311"
mnc="480"
apn="VZWADMIN"
type="fota"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Roaming Internet"
mcc="204"
mnc="04"
apn="VZWINTERNET"
type="default,supl"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Roaming FOTA"
mcc="204"
mnc="04"
apn="VZWADMIN"
type="fota"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Test Internet"
mcc="246"
mnc="81"
apn="VZWINTERNET"
type="default,supl"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Test FOTA"
mcc="246"
mnc="81"
apn="VZWADMIN"
type="fota"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Test Internet"
mcc="246"
mnc="081"
apn="VZWINTERNET"
type="default,supl"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>
<apn carrier="VZW Test FOTA"
mcc="246"
mnc="081"
apn="VZWADMIN"
type="fota"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
/>

Nexus 5X Roaming Issues on Project Fi

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.