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.
Related
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...?
Hello XDA,
I love Cyanogenmod, it's so much better than TouchWiz! My only issue is that on my Sprint Galaxy S3, on the Credo Mobile network (an MVNO of Sprint), I don't get LTE...I know I have fair LTE signal in my area because on TouchWiz, I get LTE. On Cyanogenmod, however, I get 3G, and when I turn on the LTE toggle, it either stays on 3G, switches to 1X data, or loses data connection altogether. I've done PRL and Profile updates, and the problem remains.
Any help would be greatly appreciated!
Thanks!
drsn0w
I'm also on Credo. I moved over from AT&T, which is a company I never cared to do business with and which also always seemed to treat my business as an annoyance, but which had great coverage. I put our whole family on Credo because my wife was a longstanding customer. I haven't had decent coverage at any time.
BuckMulligan said:
I'm also on Credo. I moved over from AT&T, which is a company I never cared to do business with and which also always seemed to treat my business as an annoyance, but which had great coverage. I put our whole family on Credo because my wife was a longstanding customer. I haven't had decent coverage at any time.
Click to expand...
Click to collapse
Credo runs with Sprint, so i wouldn't expect decent coverage. I know that I do have LTE coverage in this area, but I can't use Touchwiz because my SIM somehow got PUK blocked and Credo refuses to give me the PUK code because I'm rooted. So yeah.
drsn0w said:
Credo runs with Sprint, so i wouldn't expect decent coverage. I know that I do have LTE coverage in this area, but I can't use Touchwiz because my SIM somehow got PUK blocked and Credo refuses to give me the PUK code because I'm rooted. So yeah.
Click to expand...
Click to collapse
While it's true that Sprint's coverage isn't great, the OP said he got coverage before installing CM. So it's likely that weak coverage is not the issue.
Also, I'm having the same problem. :/
More info...
It's not rooting itself that is the problem. I simply went back to the Nandroid backup I'd made before loading Cyanogen, and internet connectivity returned while I was still rooted.
I had the same issue with Liquid Smooth that I had with Cyanogen, and got out of it the same way.
And I've seen posts where people said that "Your signal isn't really any different - it's just that Sprint and other carriers pad their signal strength meters to make themselves look better, and loading a new ROM omits that," but that can't be the core issue either, because with CyanogenMod and Liquid Smooth, I was unable to connect to sites/apps with a "check your internet connection" error, whereas I could connect to them in the same place once I returned to my rooted/stock ROM status.
I'm a Credo member in Minneapolis experiencing the same issue with my GS3. What I figured out by accident is that I can get an LTE connection by making a backup of my phone, then wiping it, restoring the backup, and wiping my cache and dalvik. Two times in three I get LTE when the device reboots, but only until I restart the device or switch to a wifi connection and back. I've been experimenting with different radio/baseband versions (as described here http://forum.xda-developers.com/showthread.php?t=1787677), but so far have had no luck getting LTE to stick. Hopefully this will be resolved with further development, but fortunately my 3G speeds are pretty decent, so I can wait for a long-term fix to (hopefully) fall into place.
FireflyNerd said:
While it's true that Sprint's coverage isn't great, the OP said he got coverage before installing CM. So it's likely that weak coverage is not the issue.
Also, I'm having the same problem. :/
Click to expand...
Click to collapse
uptownkenshi said:
I'm a Credo member in Minneapolis experiencing the same issue with my GS3. What I figured out by accident is that I can get an LTE connection by making a backup of my phone, then wiping it, restoring the backup, and wiping my cache and dalvik. Two times in three I get LTE when the device reboots, but only until I restart the device or switch to a wifi connection and back. I've been experimenting with different radio/baseband versions (as described here http://forum.xda-developers.com/showthread.php?t=1787677), but so far have had no luck getting LTE to stick. Hopefully this will be resolved with further development, but fortunately my 3G speeds are pretty decent, so I can wait for a long-term fix to (hopefully) fall into place.
Click to expand...
Click to collapse
I've figured out what my issue is, I'm not sure that it will apply to you. Somehow, the internal LTE SIM card got PUK locked, which is why i can't get LTE on cyanogenmod, or use touchwiz at all...and Credo doesn't even have access to the PUK codes! I'm wondering if I can use this to leverage my way out of my contract without paying ETFs...
drsn0w said:
I've figured out what my issue is, I'm not sure that it will apply to you. Somehow, the internal LTE SIM card got PUK locked, which is why i can't get LTE on cyanogenmod, or use touchwiz at all...and Credo doesn't even have access to the PUK codes! I'm wondering if I can use this to leverage my way out of my contract without paying ETFs...
Click to expand...
Click to collapse
so here a question while you're rooted. backup apn in touchwiz. then when you flash cyanmod. which has to be rooted. restore the touchwiz apn. issue solved.
kaos420 said:
so here a question while you're rooted. backup apn in touchwiz. then when you flash cyanmod. which has to be rooted. restore the touchwiz apn. issue solved.
Click to expand...
Click to collapse
No, APNs are not the issue. I can't even use the phone AT ALL in Touchwiz...when I boot in to touchwiz, even unrooted, it asks for a PUK code, which I don't have and can't get.
drsn0w said:
No, APNs are not the issue. I can't even use the phone AT ALL in Touchwiz...when I boot in to touchwiz, even unrooted, it asks for a PUK code, which I don't have and can't get.
Click to expand...
Click to collapse
you said. " I don't get LTE...I know I have fair LTE signal in my area because on TouchWiz, I get LTE."
kaos420 said:
you said. " I don't get LTE...I know I have fair LTE signal in my area because on TouchWiz, I get LTE."
Click to expand...
Click to collapse
Sorry, I should have clarified. I USED to get fair LTE signal on TouchWiz, when TouchWiz worked. Sorry haha
drsn0w said:
I've figured out what my issue is, I'm not sure that it will apply to you. Somehow, the internal LTE SIM card got PUK locked, which is why i can't get LTE on cyanogenmod, or use touchwiz at all...and Credo doesn't even have access to the PUK codes! I'm wondering if I can use this to leverage my way out of my contract without paying ETFs...
Click to expand...
Click to collapse
Dumb question: the cursory bit of reading I did on PUK codes after seeing this post suggested they applied only to GSM phones, where I understand Sprint/Credo to use a CDMA network. How is the issue applicable even in your case, and where would you go in CM to enter the code if you did have it?
"I know enough to tinker; I tinker enough to do dumb things."
uptownkenshi said:
Dumb question: the cursory bit of reading I did on PUK codes after seeing this post suggested they applied only to GSM phones, where I understand Sprint/Credo to use a CDMA network. How is the issue applicable even in your case, and where would you go in CM to enter the code if you did have it?
"I know enough to tinker; I tinker enough to do dumb things."
Click to expand...
Click to collapse
It is true that Sprint is a CDMA network and does not need a SIM card to function for basic voice and 1X or 3G data, but 4G LTE requires a SIM card on both GSM and CDMA, most CDMA LTE phones have that SIM card embedded. In Cyanogenmod if you go into Settings -> Security -> SIM Card Lock. That's how I accidentally locked myself up.
Anyone figure out how to get 4g or LTE to work with the samsung galaxy s3 on credo with cyanogenmod 10.2? I was reading that 10.2 fixed the issue, but I still get no connection when I try it out. I also can't send mms on my phone, so i'm thinking of flashing back to stock, fixing the APNs, and then hopefully re-flashing cyanogenmod. Wonder if that'll fix it.
---------- Post added at 06:21 PM ---------- Previous post was at 06:11 PM ----------
I'm going to just flash with the stock ROM, update the prl, profile and everything to the newest versions, and then backup that rom again, then install cyanogenmod again.
I'll let you know how the process works.
It worked with Credomobile in the Atlanta area using Sprint LTE. See instruction below
robosllim Old 4th November 2013, 06:06 PM #49
Member - OP
Thanks Meter 2
Posts: 34
Join Date: Jan 2011
Ho. Ly. Crap. That finally did it!
From the APNs menu (I accessed it with a shortcut in Nova Launcher, but I believe you can say "open APNs" in the dialer to do it?) I selected Sprint Internet and edited the name to n.w1.ispsn. After that, I toggled airplane mode and my phone was finally able to connect to an LTE signal! Huzzah!
Thanks for everyone that helped out in this thread. Hopefully this'll be helpful to others in the future.
And now I am off to get my shiny new CM ROM set up
ATTACHED THUMBNAILS
Click image for larger version
Name: Screenshot_2013-11-04-12-00-33.png
Views: 33
Size: 141.8 KB
ID: 2371093
drklrdbill said:
Anyone figure out how to get 4g or LTE to work with the samsung galaxy s3 on credo with cyanogenmod 10.2? I was reading that 10.2 fixed the issue, but I still get no connection when I try it out. I also can't send mms on my phone, so i'm thinking of flashing back to stock, fixing the APNs, and then hopefully re-flashing cyanogenmod. Wonder if that'll fix it.
---------- Post added at 06:21 PM ---------- Previous post was at 06:11 PM ----------
I'm going to just flash with the stock ROM, update the prl, profile and everything to the newest versions, and then backup that rom again, then install cyanogenmod again.
I'll let you know how the process works.
Click to expand...
Click to collapse
This worked perfectly for me. For the first time since I got my G3, I have LTE.
---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------
Damn, quoted the wrong post. I was referring to hanson's post about renaming the APNs.
Latest Credo Mobile APNs
Ok, Cyanogenmod doesn't come with the correct APNs for 3rd party Sprint Network users. You have to remove the default APNs and then add the latest Preferred Roaming List. Also known as the Access Point Name (APN).
Here is the file with the new Credo Mobile APNs for any ROM that can't connect to LTE or to Sprint's servers to get MMS messages.
https://www.dropbox.com/s/7es3vh5c67jdqwh/apns-credo.xml
This xml file is structured to be used with the app "APN Backup & Restore" .
Make sure the APN app is moved to the system folder. I used "/system/app mover" to do this.
Below is the code to the XML file.
Code:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="4">
<apn name="APN0 LTE ota" numeric="310000" mcc="310" mnc="000" apn="otasn" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="fota" />
<apn name="APN0 EHRPD ota" numeric="310000" mcc="310" mnc="000" apn="otasn" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="fota" />
<apn name="APN2 LTE internet" numeric="310000" mcc="310" mnc="000" apn="n.w1.ispsn" user="" server="" password="" proxy="" port="" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mms.plspictures.com" type="default,mms" />
<apn name="APN2 EHRPD internet" numeric="310000" mcc="310" mnc="000" apn="n.w1.ispsn" user="" server="" password="" proxy="" port="" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mms.plspictures.com" type="default,mms" />
</apns>
UPDATE: This list of APNs provide 3G, 4G LTE EVDO, and 2G CDMA but NOT MMS support. I don't know why. I am looking into updating my code.
2015 cm 12.1 credo mobile APN settings
since this is the first XDA thread showing in my search results, I'll just bump this for posterity. CM has implemented the Credo APN settings into the frontend settings app since at least CM12 (poorly, but they try. I'm sure the carriers don't make this a simple task with ongoing network config changes. )
I had to switch my network mode to LTE-only in order to get my APN settings to actually list the props available. Once they were shown, I finally figured out that I could just edit the Sprint-LTE-internet profile and just edit the correct gateway (n.w1.ispsn instead of just n.ispsn)
Here's some screenies for the entire prop settings that got me connected to LTE after an airplane-mode toggle:
Dudebowski said:
since this is the first XDA thread showing in my search results, I'll just bump this for posterity. CM has implemented the Credo APN settings into the frontend settings app since at least CM12 (poorly, but they try. I'm sure the carriers don't make this a simple task with ongoing network config changes. )
I had to switch my network mode to LTE-only in order to get my APN settings to actually list the props available. Once they were shown, I finally figured out that I could just edit the Sprint-LTE-internet profile and just edit the correct gateway (n.w1.ispsn instead of just n.ispsn)
Here's some screenies for the entire prop settings that got me connected to LTE after an airplane-mode toggle:
Click to expand...
Click to collapse
@Dudebowski how did you change apn? I have no option to change it.
fenz4rt said:
@Dudebowski how did you change apn? I have no option to change it.
Click to expand...
Click to collapse
What version of cm are you running? Should be in
System settings
Mobile networks
Access point names
If the profiles list doesn't populate, try using different " preferred network types" but lte-only worked for me.
On other aosp roms you might have to open voice dialer and say "APN" to get into the cdma settings/ hidden menu
How, thanks in advance.
Sent from my SM-G925T using Tapatalk
I would like to know aswell.
Got it working with this tut, had to buy the app for 3 bucks but its worth it! https://youtu.be/qNJrzgRp4wM
Sent from my SM-G925T using Tapatalk
If your rooted then follow the tut in my Sig
Sent from my SM-G925T using XDA Free mobile app
Those play store apps are pointless when you can do it native. And they don't work anymore without using a vpn because T-mobile scans user-agent strings to determine the device being used.
All I do is, Replace TetheringProvision.apk with the modded one, Set the permissions to 644 (rw-r--r--), go into customer.xml and change all non ims profiles to ipv4 (leave the ims protocols ipv6 or VoLTE and WiFi-Calling won't work), go to settings and change the apn by adding dun to default,mms,supl and change it to ipv4. Then I reboot my phone. In this state you will still use hotspot allotment. That is because T-mobile is using user-agent strings to decipher device being used. Only way to fix that is to get a vpn and use it on the devices you connect to your hotspot.
jmc302005 said:
Those play store apps are pointless when you can do it native. And they don't work anymore without using a vpn because T-mobile scans user-agent strings to determine the device being used.
All I do is, Replace TetheringProvision.apk with the modded one, Set the permissions to 644 (rw-r--r--), go into customer.xml and change all non ims profiles to ipv4 (leave the ims protocols ipv6 or VoLTE and WiFi-Calling won't work), go to settings and change the apn by adding dun to default,mms,supl and change it to ipv4. Then I reboot my phone. In this state you will still use hotspot allotment. That is because T-mobile is using user-agent strings to decipher device being used. Only way to fix that is to get a vpn and use it on the devices you connect to your hotspot.
Click to expand...
Click to collapse
What is the point if you're still using the Hot spot allotment?
I use WiFi Tether for Root users and it's awesome. I average 10 to 20 gigs a day when traveling with my family. I use it for the Roku I have attached to the in-car entertainment system. I've had a few months where my usage was north of 500GB and never heard a peep from T-MO. That does not include my wife, mother in-law and Kids Ipads all hooked up to the Hot Spot in the car. Heck, I'm the only one not surfing at those times.
njdevils28 said:
What is the point if you're still using the Hot spot allotment?
I use WiFi Tether for Root users and it's awesome. I average 10 to 20 gigs a day when traveling with my family. I use it for the Roku I have attached to the in-car entertainment system. I've had a few months where my usage was north of 500GB and never heard a peep from T-MO. That does not include my wife, mother in-law and Kids Ipads all hooked up to the Hot Spot in the car. Heck, I'm the only one not surfing at those times.
Click to expand...
Click to collapse
Which rom are you using and anything else you had to change?
ktetreault14 said:
Which rom are you using and anything else you had to change?
Click to expand...
Click to collapse
I'm stock 5.02 with PingPong Root. I had to change the APN settings to IPv4 and then the in-app setting for my phone. It was not too difficult.
If you're rooted, just follow the instructions in my sig you should be good to go.
-NJ
P.S. this should be the direct link to the instructions.
Thanks you. Will try after work on my Xbox One
njdevils28 said:
What is the point if you're still using the Hot spot allotment?
I use WiFi Tether for Root users and it's awesome. I average 10 to 20 gigs a day when traveling with my family. I use it for the Roku I have attached to the in-car entertainment system. I've had a few months where my usage was north of 500GB and never heard a peep from T-MO. That does not include my wife, mother in-law and Kids Ipads all hooked up to the Hot Spot in the car. Heck, I'm the only one not surfing at those times.
Click to expand...
Click to collapse
The point was not installing another app to do what the phone already can. With vpn it does not use allotment. I tried WiFi Tether for Root and it did not work good enough. It connected me but with slow speeds even with the recommended settings from the developer. And sometimes still pulled alottment. With the native way I get 30 - 60 Mbps/sec. With vpn same speed no allotment and the added protection of privacy and they never know what I am doing online. I personally see more benefit my way. Also most places I have read that recommend WiFi Tether for root have tons of posts about having problems getting it to work right. Also if you just switch your apn to ipv4 you lose VoLTE and WiFi-Calling because they use ipv6. So you would have to switch back and forth. All I have to do is hit my hotspot widget and I am done. On my other device I just connect and then connect vpn. Perfect. But maybe it is just about personal preference. Also I use damn near 1 terabyte a month for watching videos while I'm out and about so I know how it is for you there.
I have to agree with you on the native tether being superior but I do not VPN for all my devices, especially the Roku.
As for slow speeds, I have tested it on connected devices using the speed test app and the results were just as fast as native
njdevils28 said:
I have to agree with you on the native tether being superior but I do not VPN for all my devices, especially the Roku.
As for slow speeds, I have tested it on connected devices using the speed test app and the results were just as fast as native
Click to expand...
Click to collapse
Maybe the app depends on rom setup. Though I tried WiFi Tether Router as well with the same results as the other app. I use the Sick As Hell rom. Dunno if it makes a difference. I am not sure if Roku and Chromecast even use data. They do their thing mostly over the same network. So they only use data if you use their native apps I think. Not sure.
jmc302005 said:
Those play store apps are pointless when you can do it native. And they don't work anymore without using a vpn because T-mobile scans user-agent strings to determine the device being used.
All I do is, Replace TetheringProvision.apk with the modded one, Set the permissions to 644 (rw-r--r--), go into customer.xml and change all non ims profiles to ipv4 (leave the ims protocols ipv6 or VoLTE and WiFi-Calling won't work), go to settings and change the apn by adding dun to default,mms,supl and change it to ipv4. Then I reboot my phone. In this state you will still use hotspot allotment. That is because T-mobile is using user-agent strings to decipher device being used. Only way to fix that is to get a vpn and use it on the devices you connect to your hotspot.
Click to expand...
Click to collapse
Can you go more in depth on this? I'm looking at my customer.xml and see scattered ipv6 entries but don't know which to change to ipv4 and which to leave the same. I don't see a distinction between "non ims" and "ims protocols".
Also do I need to create a copy of my current apn to edit it? The active one is non editable.
Thanks!
bad_HABIT said:
Can you go more in depth on this? I'm looking at my customer.xml and see scattered ipv6 entries but don't know which to change to ipv4 and which to leave the same. I don't see a distinction between "non ims" and "ims protocols".
Also do I need to create a copy of my current apn to edit it? The active one is non editable.
Thanks!
Click to expand...
Click to collapse
I will explain to make it easier.
the customer.xml section you will be editing is <Profile> there are 10 of these sections. You only need to edit 4 of them. The sections contain:
Code:
<Profile>
<NetworkName>XXXX</NetworkName>
<IpVersion>XXXX</IpVersion> <---------This gets changed
<Editable>XXX</Editable> <------------- This gets changed
<EnableStatus>XXXX</EnableStatus>
<ProfileName>XXXX</ProfileName>
<Auth>XXXX</Auth>
<Bearer>XXXX</Bearer>
<Protocol>XXXX</Protocol>
<MTUSize>XXXX</MTUSize>
<Proxy>
<EnableFlag>XXXX</EnableFlag>
</Proxy>
<PSparam>
<APN>XXXX</APN> <---------------Take note of this
</PSparam>
</Profile>
The way to tell if it is an ims profile is by looking at
Code:
<APN>XXXX</APN>
if is says
Code:
<APN>ims</APN>
then it is IMS and leave it alone.
The 4 you should change are
1.
Code:
<Profile>
<ProfileName>T-Mobile US LTE</ProfileName>
2.
Code:
<Profile>
<ProfileName>T-Mobile MMS LTE</ProfileName>
3.
Code:
<Profile>
<ProfileName>T-Mobile MMS EPDG</ProfileName>
4.
Code:
<Profile>
<ProfileName>IOT Test</ProfileName>
In those profiles change
Code:
<IpVersion>ipv6</IpVersion>
to
Code:
<IpVersion>ipv4</IpVersion>
to make your APNs editable in settings do the following
change
Code:
<Editable>no</Editable>
to
Code:
<Editable>yes</Editable>
Some people may have to edit their feature.xml in the same folder to make editing work if the above didn't. To do that search for
Code:
<CscFeature_Setting_HideApnList>
and delete that whole line.
That should be all you need. I hope I made it easier for you to understand.
jmc302005 said:
I will explain to make it easier.
the customer.xml section you will be editing is <Profile> there are 10 of these sections. You only need to edit 4 of them. The sections contain:
Code:
<Profile>
<NetworkName>XXXX</NetworkName>
<IpVersion>XXXX</IpVersion> <---------This gets changed
<Editable>XXX</Editable> <------------- This gets changed
<EnableStatus>XXXX</EnableStatus>
<ProfileName>XXXX</ProfileName>
<Auth>XXXX</Auth>
<Bearer>XXXX</Bearer>
<Protocol>XXXX</Protocol>
<MTUSize>XXXX</MTUSize>
<Proxy>
<EnableFlag>XXXX</EnableFlag>
</Proxy>
<PSparam>
<APN>XXXX</APN> <---------------Take note of this
</PSparam>
</Profile>
The way to tell if it is an ims profile is by looking at
Code:
<APN>XXXX</APN>
if is says
Code:
<APN>ims</APN>
then it is IMS and leave it alone.
The 4 you should change are
1.
Code:
<Profile>
<ProfileName>T-Mobile US LTE</ProfileName>
2.
Code:
<Profile>
<ProfileName>T-Mobile MMS LTE</ProfileName>
3.
Code:
<Profile>
<ProfileName>T-Mobile MMS EPDG</ProfileName>
4.
Code:
<Profile>
<ProfileName>IOT Test</ProfileName>
In those profiles change
Code:
<IpVersion>ipv6</IpVersion>
to
Code:
<IpVersion>ipv4</IpVersion>
to make your APNs editable in settings do the following
change
Code:
<Editable>no</Editable>
to
Code:
<Editable>yes</Editable>
Some people may have to edit their feature.xml in the same folder to make editing work if the above didn't. To do that search for
Code:
<CscFeature_Setting_HideApnList>
and delete that whole line.
That should be all you need. I hope I made it easier for you to understand.
Click to expand...
Click to collapse
Just went ahead and did this. All seems to be working. Thanks so much for the time and effort on this guide. I'm sure it'll help many of us!
bad_HABIT said:
Just went ahead and did this. All seems to be working. Thanks so much for the time and effort on this guide. I'm sure it'll help many of us!
Click to expand...
Click to collapse
No problem I am more than happy to help people if I can. I am glad you got it figured out.
Samsung s6
jmc302005 said:
Those play store apps are pointless when you can do it native. And they don't work anymore without using a vpn because T-mobile scans user-agent strings to determine the device being used.
All I do is, Replace TetheringProvision.apk with the modded one, Set the permissions to 644 (rw-r--r--), go into customer.xml and change all non ims profiles to ipv4 (leave the ims protocols ipv6 or VoLTE and WiFi-Calling won't work), go to settings and change the apn by adding dun to default,mms,supl and change it to ipv4. Then I reboot my phone. In this state you will still use hotspot allotment. That is because T-mobile is using user-agent strings to decipher device being used. Only way to fix that is to get a vpn and use it on the devices you connect to your hotspot.
Click to expand...
Click to collapse
Will this work also on T-Mobile s6 today?
Twowolves1919 said:
Will this work also on T-Mobile s6 today?
Click to expand...
Click to collapse
It should work fine.
Update: This module won't make VoWiFi or VoLTE work. It will enable the menu options but they won't work.
I'm leaving the module up for anyone interested in playing with it, but be aware that it probably won't be useful to you.
Hey guys,
I'm on Three in the UK who support VoLTE, but not on the OnePlus 5 (yet).
So I made a module to enable it.
Important: This isn't going to just magically make VoLTE work, but it will show you the VoLTE options. If your carrier enables VoLTE for you, then you shouldn't need this module.
I'm hoping someone else who has a VoLTE compatible device can share whatever settings are missing. I suspect it's something like the (ims) server to connect to for VoLTE, but I'm not sure since I don't own any compatible devices.
Please feel free to give it a try and let me know.
Thanks Volte active but operator does not support oneplus 5
I have T-Mobile and voLTE was not enabled on my 5. The option was always there in my settings to enable it. I toggled voLTE in my settings and it worked. No need for the module for me.
Try setting up an ims APN for 3?
Settings should be:
APN name 3UK IMS
APN ims
APN Type ims
APN protocol IPv4/IPv6
APN roaming protocol IPv4/IPv6
MCC abs MNC same as the normal 3 APN.
I've been trying to get it working with my O2 SIM.
Works natively with EE, but silly that the device is exclusive to O2 but doesn't support their settings.
At the start of apn.conf there's a comment that the ims APN was added for O2. But it wasn't.
I added my own.
Just added vowifi toggle
Doesn't look like it's actually working though.
Fairly sure I've got it enabled through myo2
Code:
persist.radio.rat_on=combine
persist.data.iwlan.enable=true
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1
persist.radio.calls.on.ims=1
badcrow35 said:
Thanks Volte active but operator does not support oneplus 5
Click to expand...
Click to collapse
I also have the same problem. I've been told it requires OnePlus and Three to release some drivers. Someone shared some Polish T-Mobile ones so maybe I'll look at those eventually.
dracoboss said:
I have T-Mobile and voLTE was not enabled on my 5. The option was always there in my settings to enable it. I toggled voLTE in my settings and it worked. No need for the module for me.
Click to expand...
Click to collapse
Yeah, if you're on a carrier that has OnePlus 5 support, then it should enable automatically. No need for the module. I was just hoping using the module could work around it not being enabled even though the phone supports it.
fards said:
Try setting up an ims APN for 3?
Settings should be:
APN name 3UK IMS
APN ims
APN Type ims
APN protocol IPv4/IPv6
APN roaming protocol IPv4/IPv6
MCC abs MNC same as the normal 3 APN.
I've been trying to get it working with my O2 SIM.
Works natively with EE, but silly that the device is exclusive to O2 but doesn't support their settings.
At the start of apn.conf there's a comment that the ims APN was added for O2. But it wasn't.
I added my own.
Click to expand...
Click to collapse
Thanks for sharing. These are the same settings I have on my Three IMS APN after installing the module. What's in your APN.conf then?
fards said:
Just added vowifi toggle
Doesn't look like it's actually working though.
Fairly sure I've got it enabled through myo2
Code:
persist.radio.rat_on=combine
persist.data.iwlan.enable=true
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1
persist.radio.calls.on.ims=1
Click to expand...
Click to collapse
I made a separate module for VoWiFi, I just didn't "publish" it (it's on github public).
There are new lines in here I haven't seen before! Where did you find all the definitions.
Also, you've got persist.data.iwlan.enable=true twice.
Raharazod said:
I also have the same problem. I've been told it requires OnePlus and Three to release some drivers. Someone shared some Polish T-Mobile ones so maybe I'll look at those eventually.
Yeah, if you're on a carrier that has OnePlus 5 support, then it should enable automatically. No need for the module. I was just hoping using the module could work around it not being enabled even though the phone supports it.
Thanks for sharing. These are the same settings I have on my Three IMS APN after installing the module. What's in your APN.conf then?
Just added vowifi toggle
Doesn't look like it's actually working though.
Fairly sure I've got it enabled through myo2
I made a separate module for VoWiFi, I just didn't "publish" it (it's on github public).
There are new lines in here I haven't seen before! Where did you find all the definitions.
Also, you've got persist.data.iwlan.enable=true twice.
Click to expand...
Click to collapse
That's what you get for playing Early morning lying in bed instead of going to work!
Btw this is the start of the APN conf.
Code:
<!-- If you edit this version, also edit the version in the partner-supplied apns-conf.xml configuration file --> <!-- modified by [email protected] 2016-10-29 --> <!-- modified by [email protected] 2016-11-28 Modify TMO APN roaming type --> <!-- modified by [email protected] 2016-11-29 modify 23410 APN for prepay/TESCO/giffgaff card. [RAINS-6121]--> <!-- modified by [email protected] 2017-01-03 Sosh (orange)20801/Canada fido network 302370/koodo 302220/Vodafone UK 23415/T-Mobile US 310260 --> <!-- modified by [email protected] 2017-01-05 add O2 IMS APN (23410) --> <!-- modified by [email protected] 2017-05-19 modify O2 Pay Monthly/O2 Pay As You Go. [TPM-182] -->
There was no o2ims APN in there. So i added it..
It will work on thai carrier?
Sent from my ONEPLUS A5000 using Tapatalk
---------- Post added at 06:32 PM ---------- Previous post was at 06:19 PM ----------
fards said:
That's what you get for playing Early morning lying in bed instead of going to work!
Btw this is the start of the APN conf.
Code:
<!-- If you edit this version, also edit the version in the partner-supplied apns-conf.xml configuration file --> <!-- modified by [email protected] 2016-10-29 --> <!-- modified by [email protected] 2016-11-28 Modify TMO APN roaming type --> <!-- modified by [email protected] 2016-11-29 modify 23410 APN for prepay/TESCO/giffgaff card. [RAINS-6121]--> <!-- modified by [email protected] 2017-01-03 Sosh (orange)20801/Canada fido network 302370/koodo 302220/Vodafone UK 23415/T-Mobile US 310260 --> <!-- modified by [email protected] 2017-01-05 add O2 IMS APN (23410) --> <!-- modified by [email protected] 2017-05-19 modify O2 Pay Monthly/O2 Pay As You Go. [TPM-182] -->
There was no o2ims APN in there. So i added it..
Click to expand...
Click to collapse
When i add my carrier. It will work?
Where is apn.conf
Sent from my ONEPLUS A5000 using Tapatalk
Unlikely unless your carrier supports it
@Raharazod
Found a bug.
persist.data.iwlan.enable=true
Causes WiFi calling to stop writing on EE. (At least on oos 4.5.7
Don't understand why, but as soon as that is commented out and rebooted it works.
@fards: I updated the version to 1.1 and took out the "persist.data.iwlan.enable=true" line for you. Attachment on the main thread in the Magisk forum is updated.
Thanks for letting me know!
Honestly, I'm not sure what all the values do exactly. I can guess and some of them are obvious, but others are less so.
Try with Salt in Switzerland, and sadly doesn't work
Raharazod said:
@fards: I updated the version to 1.1 and took out the "persist.data.iwlan.enable=true" line for you. Attachment on the main thread in the Magisk forum is updated.
Thanks for letting me know!
Honestly, I'm not sure what all the values do exactly. I can guess and some of them are obvious, but others are less so.
Click to expand...
Click to collapse
No worries.
I'm getting intrigued enough to want to set a remote server up and rummage through the source to see what's going on. (Don't have a PC at the mo).
Odd thing with iwlan is that EE uses it, which is why forcing the mode should work..
fards said:
No worries.
I'm getting intrigued enough to want to set a remote server up and rummage through the source to see what's going on. (Don't have a PC at the mo).
Odd thing with iwlan is that EE uses it, which is why forcing the mode should work..
Click to expand...
Click to collapse
Interesting. I'm on Three.
My "Set Preferred Network Type" is TD-SCDMA/CDMA/UMTS by default. Have you changed yours?
Also, "Data Network Type" is LTE, not iwlan. They do support WiFi calling and VoLTe, just not on the OP5.
Edit: UPDATE. After making your adjustment and removing the iwlan... re-enabling VoWiFi... I now get the icon in my status bar! The plot thickens!
Edit 2: And *#*#4636#*#* now says iwlan. I turned off the SIM but it disconnected VoWiFi when I did. I thought you could be connected without the SIM and still use it?
Raharazod said:
Interesting. I'm on Three.
My "Set Preferred Network Type" is TD-SCDMA/CDMA/UMTS by default. Have you changed yours?
Also, "Data Network Type" is LTE, not iwlan. They do support WiFi calling and VoLTe, just not on the OP5.
Edit: UPDATE. After making your adjustment and removing the iwlan... re-enabling VoWiFi... I now get the icon in my status bar! The plot thickens!
Edit 2: And *#*#4636#*#* now says iwlan. I turned off the SIM but it disconnected VoWiFi when I did. I thought you could be connected without the SIM and still use it?
Click to expand...
Click to collapse
You need the sim active. However if you lose signal it switches.. if you make a call it should show it's using WiFi calling on the stock dialler. (Set it as preferred obviously) .
Don't think it does on Google dialler.
fards said:
You need the sim active. However if you lose signal it switches.. if you make a call it should show it's using WiFi calling on the stock dialler. (Set it as preferred obviously) .
Don't think it does on Google dialler.
Click to expand...
Click to collapse
While I get the VoWiFi icon, when I dial out, I get a picture of SIM 1 instead of something else.
Raharazod said:
While I get the VoWiFi icon, when I dial out, I get a picture of SIM 1 instead of something else.
Click to expand...
Click to collapse
Hmm i just disabled mobile data and tried on EE.
I get this using Google dialler.
Not sure how disabling mobile data makes it preferred.
Work perfectly with french band (SFR/RED), i have tried call without data, only wifi and it work
Thanks @Raharazod
Pho3nX said:
Work perfectly with french band (SFR/RED), i have tried call without data, only wifi and it work
Thanks @Raharazod
Click to expand...
Click to collapse
Exciting! Glad to hear it worked!
@fards: I've installed the Google Dialer to test. It doesn't say "Calling via Wi-Fi..." but it does display the Wi-Fi signal icon. I'll try it tomorrow on the tube on my way to work.
Raharazod said:
Exciting! Glad to hear it worked!
@fards: I've installed the Google Dialer to test. It doesn't say "Calling via Wi-Fi..." but it does display the Wi-Fi signal icon. I'll try it tomorrow on the tube on my way to work.
Click to expand...
Click to collapse
Thanks mate, i use also the Google Dialer/Contact module (Magisk)
I had already posted this somewhere inside a thread but many people still keep asking the same question.
Attached is a simple Magisk module to enable VoLTE if it is not enabled for your country/carrier.
I don't guarantee that it will work for everybody ... it did work for me though ...
Of course you must be rooted and have Magisk.
Just install attached module in Magisk, then reboot.
The mod has properties for 5G and VoWifi ... BUT absolutely no guarantee here!!!
I do not have 5G and I do not have VoWIFI ... so I cannot even test if these properties do anything or not.
How to check if this is working?
BEFORE installing the module, go to dialer, type *#*#4636#*#*
Select: Phone info, you will see a screen like the screenshot attached below.
Check the line called: 'VoLTE-registration', if the radio button if OFF, you do NOT have VoLTE.
Now install the module, reboot and check the same screen again. If all is well, the radio button for VoLTE-registration should now be ON.
Finally, go to the dialer, dial your voice mail. Your data icon the the statusbar should still be LTE(+)/4G(+). If that is the case you now have VoLTE.
If it does not work for you ... bad luck ... just un-install the module in Magisk.
i tested 5g is still unworkable.
luke1018 said:
i tested 5g is still unworkable.
Click to expand...
Click to collapse
Thanks ... well ... it was worth a try ;-/
Hey man, thanks for posting this.
Hmm so I have "VoLTE Provisioned" rather than "registration", which is toggled on but greyed out (like Wi-Fi Calling - which definitely does work and is supported by my UK EE carrier).
So in theory, based off these settings, perhaps VoLTE should work given the setting looks the same as WiFi Calling and is supported by my carrier, but I don't see HD calling work (this is without this module...)
After installing this module, what I did notice change in the *#*'4636*#*# menu is "Video Calling Provisoned) became toggled on, but also remained greyed out but weirdly when making a call my signal dropped to saying "3G" and "H", with no VoLTE being activated. Removing the module made calls return back to 4G calls, still with no indication of VoLTE.
Posting my experience nonetheless!
Thanks
cd993 said:
Hey man, thanks for posting this.
Hmm so I have "VoLTE Provisioned" rather than "registration", which is toggled on but greyed out (like Wi-Fi Calling - which definitely does work and is supported by my UK EE carrier).
So in theory, based off these settings, perhaps VoLTE should work given the setting looks the same as WiFi Calling and is supported by my carrier, but I don't see HD calling work (this is without this module...)
After installing this module, what I did notice change in the *#*'4636*#*# menu is "Video Calling Provisoned) became toggled on, but also remained greyed out but weirdly when making a call my signal dropped to saying "3G" and "H", with no VoLTE being activated. Removing the module made calls return back to 4G calls, still with no indication of VoLTE.
Posting my experience nonetheless!
Thanks
Click to expand...
Click to collapse
What do mean precisely with "indication of VoLTE"? There is no icon that pops up when you have VoLTE (as opposed to for example OnePlus phones which show a "VoLTE" icon in the status bar).
HD calling is something different - AFAIK nothing to do with VoLTE.
It is normal that you cannot toggle the buttons - similar as in my case.
If during calling, your data remains on 4G then actually there was no need to install this module ;-)
In my case:
- before module installed: VoLTE registration was OFF, during calling data icon changed 4G -> H
- after module installed: VoLTE registration was ON, during calling data icon remained 4G (and I actually verified I still had same mobile internet speeds during not calling)
foobar66 said:
What do mean precisely with "indication of VoLTE"? There is no icon that pops up when you have VoLTE (as opposed to for example OnePlus phones which show a "VoLTE" icon in the status bar).
HD calling is something different - AFAIK nothing to do with VoLTE.
It is normal that you cannot toggle the buttons - similar as in my case.
If during calling, your data remains on 4G then actually there was no need to install this module ;-)
Click to expand...
Click to collapse
Ah, my presumption by "indication" was either a status bar icon or perhaps something on the dialler screen e.g. with Wifi Calling I see the WiFi icon next to the contacts name in my call history.
Wasn't aware about 4G being on and VoLTE - so that's something new!
But also upon checking my call history properly just now I see some calls actually do have not only a WiFi icon but also "HD" next to them (see attached screenshot) so indeed I perhaps didn't need this module!
I guess I've been wrongly looking out for a HD sign on the dialler screen during a call to indicate VoLTE....
Most of those properties are persistent properties. You just set them once with "setprop persist.blahblahblah whatevervalue" and they'll stick through a reboot.
There is definitely no need for a "magisk module" for this.
Only these 4 are non-persistent properties, and from what I can tell, they're all bogus.
ril.subscription.types=RUIM
ro.nubia.nr.support=1
ro.telephony.default_cdma_sub=0
ro.vendor.radio.5g=3
The "5g" ones are probably not advisable. For everything else, it would be nice to know what they actually do before trying them out.
AFAIK the HD (high definition) icon has in principle nothing to do with VoLTE (voice over LTE).
It is a voice codec with better quality as it suppresses background noise.
However, I believe (although I'm not 100% sure) that the HD codec is only avaible when you do VoLTE calls.
And it will only show if the caller also has VoLTE/HD and in certain network areas.
So technically it is possible to have non-HD-voice on VoLTE, although most of the time they will go together.
And the other way round, it is technically possible to have HD calls when you're not on VoLTE.
That is my understanding ... but I'm certainly not an expert in this and could as well be wrong ;-)
When a VoLTE UE originates a voice call from LTE, it executes the normal mobile origination procedure as defined in 3GPP TS 23.228 [5] section 5.6.2. The VoLTE UE initiates a SIP INVITE request, containing the SDP offer with IMS media capabilities as specified in GSMA PRD IR.92 [54] section 3. The SDP offer shall contain the AMR Narrowband codec, and it is recommended that the AMR Wideband codec is included to provide support for HD Voice and shall indicate that local preconditions for QoS are desired but not yet met, using the segmented status type (as defined in RFC 3312 [70]) and that the media stream is set to inactive as described in 3GPP TS 24.229 ([9]) clause 6.1.2
Click to expand...
Click to collapse
96carboard said:
Most of those properties are persistent properties. You just set them once with "setprop persist.blahblahblah whatevervalue" and they'll stick through a reboot.
There is definitely no need for a "magisk module" for this.
Only these 4 are non-persistent properties, and from what I can tell, they're all bogus.
ril.subscription.types=RUIM
ro.nubia.nr.support=1
ro.telephony.default_cdma_sub=0
ro.vendor.radio.5g=3
The "5g" ones are probably not advisable. For everything else, it would be nice to know what they actually do before trying them out.
Click to expand...
Click to collapse
Nope .. Magisk uses resetprop ... when you remove the Magisk module the properties are gone, even those that were persisted. So it has nothing to do with sticking or not.
foobar66 said:
Nope .. Magisk uses resetprop ... when you remove the Magisk module the properties are gone, even those that were persisted. So it has nothing to do with sticking or not.
Click to expand...
Click to collapse
I don't care what magisk uses. It is NOT USEFUL for this.
96carboard said:
I don't care what magisk uses. It is NOT USEFUL for this.
Click to expand...
Click to collapse
If you manually set the persist property manually, it will persist after reboot.
If Magisk sets the persist property, you remove the module and reboot, then the property will be gone.
No?
I'm not a fan of people throwing Magisk modules at this phone and seeing what sticks. Seeing far too many threads like that.
It's not a Qualcomm phone and should stop being treated like one.
foobar66 said:
I had already posted this somewhere inside a thread but many people still keep asking the same question.
Attached is a simple Magisk module to enable VoLTE if it is not enabled for your country/carrier.
I don't guarantee that it will work for everybody ... it did work for me though ...
Of course you must be rooted and have Magisk.
Just install attached module in Magisk, then reboot.
The mod has properties for 5G and VoWifi ... BUT absolutely no guarantee here!!!
I do not have 5G and I do not have VoWIFI ... so I cannot even test if these properties do anything or not.
How to check if this is working?
BEFORE installing the module, go to dialer, type *#*#4636#*#*
Select: Phone info, you will see a screen like the screenshot attached below.
Check the line called: 'VoLTE-registration', if the radio button if OFF, you do NOT have VoLTE.
Now install the module, reboot and check the same screen again. If all is well, the radio button for VoLTE-registration should now be ON.
Finally, go to the dialer, dial your voice mail. Your data icon the the statusbar should still be LTE(+)/4G(+). If that is the case you now have VoLTE.
If it does not work for you ... bad luck ... just un-install the module in Magisk.
Click to expand...
Click to collapse
Still no volte after flashing the module
Yes. Same here. VoLTE not activated. VoLTE uses IMS, so IMS service status needs to have Registered status.
Plus EAB is also needed for continue having internet data while on normal phone call
it works to me (VoLTE)
We need a MBN file from another vendor that is known to each if our users country if I am right?
Btw this was sent to me by @ziand
Releases · swangjang/Pixel-Redbull-Carrier-Patch
This is a Magisk module (in testing) for Pixel 4a (5G) and Pixel 5 that enables 5G for Unlisted Countries, VoLTE switches in the settings and add support for more countries/carriers. - swangjang/Pi...
github.com
Sound exactly like what we need?
foobar66 said:
AFAIK the HD (high definition) icon has in principle nothing to do with VoLTE (voice over LTE).
It is a voice codec with better quality as it suppresses background noise.
However, I believe (although I'm not 100% sure) that the HD codec is only avaible when you do VoLTE calls.
And it will only show if the caller also has VoLTE/HD and in certain network areas.
So technically it is possible to have non-HD-voice on VoLTE, although most of the time they will go together.
And the other way round, it is technically possible to have HD calls when you're not on VoLTE.
That is my understanding ... but I'm certainly not an expert in this and could as well be wrong ;-)
Click to expand...
Click to collapse
In many parts of Europe, HD calling works without VoLTE but in most parts of the world, HD Calling goes hand-in-hand with VoLTE i.e the HD icon in Dialer represents if the call went through 4G or 3/2G.
In those countries, no VoLTE = no HD calling = no calls over 4G = potential inability to use data while on a call.
The Magisk module like most others just enables the props i.e. It exposes the switches and will work only if the carrier configs are on the device. Without the right configs, the module is a placeholder.
Utini said:
We need a MBN file from another vendor that is known to each if our users country if I am right?
Click to expand...
Click to collapse
Nope. Those were only applicable for Qualcomm modem.
Pixel 6 Pro is using Samsung modem. The module is enough.
I get mine successfully activated
fuadhdmini said:
Nope. Those were only applicable for Qualcomm modem.
Pixel 6 Pro is using Samsung modem. The module is enough.
I get mine successfully activated
Click to expand...
Click to collapse
Can you tell me in which country you are and somehow post a proof that the module works?
If I am correct then the module basically only changes the following things in the android system?
persist.data.iwlan=1
persist.data.iwlan.enable=true
persist.data.iwlan.ipsec.ap=1
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.nubia.5g.power.config=1
persist.radio.calls.on.ims=1
persist.radio.data_con_rprt=1
persist.radio.data_ltd_sys_ind=1
persist.radio.dynamic_sar=false
persist.radio.force_on_dc=true
persist.radio.NO_STAPA=1
persist.radio.rat_on=combine
persist.radio.VT_HYBRID_ENABLE=1
persist.rcs.supported=0
persist.sys.strictmode.disable=true
persist.vendor.dpm.feature=1
persist.vendor.radio.5g=1
persist.vendor.radio.5g_mode_pref_0=1
persist.vendor.radio.5g_mode_pref=1
persist.vendor.radio.5g_mode_pref_1=1
persist.vendor.radio.calls.on.ims=1
persist.vendor.radio.data_con_rprt=1
persist.vendor.radio.data_ltd_sys_ind=1
persist.vendor.radio.enable_temp_dds=true
persist.vendor.radio.force_ltd_sys_ind=1
persist.vendor.radio.force_on_dc=true
persist.vendor.radio.manual_nw_rej_ct=1
persist.vendor.radio.mbn_load_flag=3
persist.vendor.radio.mbn_wait_s=60
persist.vendor.radio.redir_party_num=1
ril.subscription.types=RUIM
ro.nubia.nr.support=1
ro.telephony.default_cdma_sub=0
ro.vendor.radio.5g=3
Click to expand...
Click to collapse
Is there any way to read my "current values" and export them into a file (e.g. cat system.prop > backup.prop) to restore my values in case the module breaks something?