I recently installed AOSP 2.3.5 on my vibrant and well APN settings are setup fine automatically. However when I look at the carrier name it only shows numbers like 302320 I know that is Mobilicity network but it doesn't show the name.
I was reading somewhere to create a spn-conf.xml file and push it to system/etc/ however when I do that and reboot it still says the same numbers. I am in Canada and would like to have them display properly how would I go about this as all the networks I search for seem to be numbers except for Rogers Wireless,
Thanks for any help. I have adb setup in a linux environment and know how to use it so thanks again.
custom rom or stock? i think there was problem with rom.
jpeckover said:
I recently installed AOSP 2.3.5 on my vibrant and well APN settings are setup fine automatically. However when I look at the carrier name it only shows numbers like 302320 I know that is Mobilicity network but it doesn't show the name.
I was reading somewhere to create a spn-conf.xml file and push it to system/etc/ however when I do that and reboot it still says the same numbers. I am in Canada and would like to have them display properly how would I go about this as all the networks I search for seem to be numbers except for Rogers Wireless,
Thanks for any help. I have adb setup in a linux environment and know how to use it so thanks again.
Click to expand...
Click to collapse
CyanogenMod 7.1 is doing this for me too. Did you find a fix that works?
I too have this happen when I have tried MiUI and Cyanogenmod. I would be interested in a fix as well.
I don't suppouse there has been a resolution this yet?
I have a Samsung Galaxy 2 running CM 7.1.
I have this problem too. Edit spn-conf.xml, apns-conf.xml, optable.db but still no luck.
Anyone pls help.
TKS
Carrier name on CM9 June 15th nightly on GT-i9100
I noticed initially that I saw only the carrier number on my GT-i9100 running the June 15th, 2012 nightly of CM9. However, after a period of time, the carrier Name (Bell here in Canada) did show up, so perhaps for those on CM7, maybe this is fixed in the latest CM9 builds?
After over a week of trying, I've come up with a solution to enable WiFi Calling (probably also VoLTE) in Fulmics ROM for LG G6 and probably G5 running any stock based ROM.
THIS GUIDE WILL ONLY WORK IF YOUR DEVICE IS ON THE LIST OF YOUR CARRIER'S VOWIFI/VOLTE SUPPORTED DEVICES AND THE SERVICE IS ENABLED THROUGH AN OTA UPDATE FOR YOUR STOCK, BRANDED ROM PROVIDED BY YOUR CARRIER!
I don't believe in magic, you shouldn't either so don't think this guide will make VoWiFi/VoLTE work on your device regardless of your carrier's support for your phone model.
Also, if your provider offers VoLTE/VoWiFi through an external app available in Play Store, don't bother reading any further.
General idea described in this guide is to tweak your rom in a way that it is recognized by your carrier as their own VoLTE/VoWiFi enabled build that has a "green light" for IMS and Xcap apns registration in your provider's VoLTE/VoWiFi service. During my attempts you make the service work on my G6 running V10t based Fulmics ROM i discovered that adding IMS and Xcap apns plus getting all the IMS and GPRI VoLTE/WoWiFi hidden menu settings right is not enough. I had everything set up right and still couldn't make a WiFi call. Then it occured to me that maybe i can't make it work because Fulmics ROM is based v10t, and my provider's VoLTE/WoWiFi enabled rom is the v10h? So i tweaked Fulmics 1.6, then 2.0 so it masks itself in front of my provider as v10h while in fact it still is v10t Fulmics ROM 2.0. And guess what... IT WORKED!!! My Carrier's IMS and Xcap apns, manually added by me to the default open-eu apn list storred in /system/etc/apns-conf.xml, got registered in the service activating WiFi Calling on my device.
How to do it step-by-step guide below
1. PREREQUISITES:
- /OP/[YOUR CARRIER'S CUST FOLDER IN XXX_XX NAME FORMAT] in your main dir /root. If you only have OPEN_EU in your /OP you must get your carrier's specific cust folder or install Fulmics over your carrier's VoLTE/VoWiFi enabled rom then the cust folder you need will appear in /OP
- build.prop file from your Carrier's VoLTE/VoWiFi enabled rom for your LG model (make sure following line is in the file: ro.lge.cupp_capss.rootdir=/OP
- /OP dicectory in your device main root directory with your carrier's VoLTE/VoWiFi enabled ROM's subfolder (XXX_XX format). OPEN-EU or
GLOBAL-COM are not the ones .
- files from your carrier's rom: /root/data/ipsec/wo_apn.conf, /root/data/ipsec/wo/apn_xcap.conf
(You can try without those 2 files if you can't get them).
2. TO DO:
!!! AT SOME POINT OF CHANGING STUFF LISTED BELOW YOU WILL GET ALOT OF FC OF VARIOUS APPS. DON'T PANIC, JIST REBOOT YOUR DEVICE AND CARRY ON WITH CHANGES !!!
- in /OP directory delete folder _COMMON if you have one
- in /OP directory create a new directory called SUPERSET and set perms to 755
- copy all content from your carrier specific folder in /OP to SUPERSET. You can also just try renaming cour carrier's folder to SUPERSET instead of creating new filder and copying stuff to it.
- edit cust_group_mapping.cfg in /OP and change whatever you have after = to GLOBAL-COM
- open cust_path_mapping.cfg in /OP and make sure you have 999999,99=/OP/SUPERSET there on the list of providers
-edit official_op_resize.cfg and add SUPERSET_SIZE=[copy size value of your carrier's folder which should also be listed in the file]
-in /OP/SUPERSET (with your carrier's files coppied) edit cust.prop and in second line in the file change whatever you have after = to SUPERSET
- edit your rom current build.prop file and copy all additional stuff (in my case it was all the Fulmics ROM part of build.prop so from #Software Version down) to the build.prop acquired from your carrier's VoLTE/VoWiFi enabled rom. Add the coppied stuff at the bottom of the list.
- add following lines at the end of stuff coppied to your carrier's build.prop from step above:
persist.sys.cust.lte_config=true
persist.lg.data.iwlan.enable=true
# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
# applying GPRI auto-commit
ro.lge.radio_gpri=1
ro.lge.amrwb_gpri=1
wlan.lge.softap5g=false
# 2015-10-12 [email protected] LGP_DATA_IWLAN [START]
persist.lg.data.iwlan=1
persist.lg.data.iwlan.ipsec.ap=1
# 2015-10-12 [email protected] LGP_DATA_IWLAN [END]
Save the build.prop file and place it over your current system default build.prop. set perms to 644
- open your device's hidden menu, go to
Field Test->GPRI VoLTE/VoWiFi->UX and tick 3rd, 4th, 5th, 6th and 9th for WoWiFi only, all except 8th for VoLTE/VoWiFi and 1st and 2nd for VoLTE only.
- go to your apns in network settings and make sure you have all the apns needed (in my case the are: internet, mms, ims and xcap). If you don't have them, try sending settings request message to your carrier's apn service center, if that doesn't help, add the apns manually (you must find your carrier's specific manual settings on the internet). You can also edit /system/etc/apns-conf.xml file and add missing apns manually to the list in above file. To do that you must find your carrier's apns on the list first, (list order by MCC-MNC code) under your carrier's last apn enter your VoLTE/VoWiFi apns in the same way the other apns in the file are typed.
-save apns-conf.xml, go back to apn list in network settings, tap overview->restore defaults and the missing apns you added to your xml file should appear on the list in network settings.
-make sure you have all permissions right of the created/coppied/edited files and reboot your device.
When your phone boots back up to Fulmics you should have your carrier's boot animation instead of default LG one, then you should see initial boot screen with "android is setting up" for a couple of seconds, then your homescreen. When configuring of your sustem is done, open quick settings and your VoLTE and WiFi Calling tiles should appear there. Turn on what you want and test if it's working. Remember, with VoWiFi you must have both WiFi and WiFi calling ON. The easiest way to tell if WiFi Calling is active is the presence of a headphone with little WiFi icon on the status bar and other places in your dialer etc. To test, turn on airplane mode, wait till WiFi gets turned off, turn it back on in airplane mode, wait for WiFi calling icon on status bar and try to make a call with airplane mode on .
REMEMBER! This guide will will only work if your carrier verifies WiFi enabled devices by 3 conditions: 1. Device supported, 2. Apns present, 3. ROM build match (info from build.prop).
I might have forgotten about something (or not ) but will edit if or when questions start to be asked
A picture of WiFi Calling working on my device with Fulmics rom 2.0 below. (WiFi Calling icon next to WiFi icon in status bar.
@mrbeem tried flashing back the kdz trough lgup but in OP i found only three folders: _COMMON, lost+found and OPEN_EU, plus a lot of individual files.
Any clues? Can you specify what files the operator folder should contain? Thanks in advance!
Killua96 said:
@mrbeem tried flashing back the kdz trough lgup but in OP i found only three folders: _COMMON, lost+found and OPEN_EU, plus a lot of individual files.
Any clues? Can you specify what files the operator folder should contain? Thanks in advance!
Click to expand...
Click to collapse
What rom did you flash in LG UP? Was it your provider's stock ROM with WiFi Calling service enabled or was it Open EU rom? OP should contain your carrier's config files of you flash your provider's ROM. The files should be in a separate folder with your Carrier's name (for example, Vodafone Italy should have a folder in /OP named VDF_IT etc.). Carrier specific folder should contain subfolders called: config, overlay, apps, media, poweron, poweroff. Most impostant are: config and overlay. Also in /OP there should be 3 files apart from the subfolders: cust.prop, official_op_resize.cfg and except_buyercode.cfg
Pics of content of cust.prop and official_op_resize.cfg from my carrier's folder (P4P_PL)
mrbeem said:
What rom did you flash in LG UP? Was it your provider's stock ROM with WiFi Calling service enabled or was it Open EU rom? OP should contain your carrier's config files of you flash your provider's ROM. The files should be in a separate folder with your Carrier's name (for example, Vodafone Italy should have a folder in /OP named VDF_IT etc.). Carrier specific folder should contain subfolders called: config, overlay, apps, media, poweron, poweroff. Most impostant are: config and overlay. Also in /OP there should be 3 files apart from the subfolders: cust.prop, official_op_resize.cfg and except_buyercode.cfg
Click to expand...
Click to collapse
The OPEN EU that Bridge downloads when my phone is connected, and is the same one which is referred as "Vodafone Italy" on LG Firmware.
In /OP i have these files: op_list, official_op_resize, custom_path_mapping, custo_group_mapping, client_id, buerycode, strangely are almost the same found on fulmics.
In Open_EU i've overlay and config folders, and these files: official_op_resize.cfg, except_buyercode.cfg and cust.prop.
The strange thing is that the vodafone brand remains also with the fulmics, in fact at everye clean installation i found vodafone apps and vodafone configuration before restore my lgbackup, what a mess lol
Killua96 said:
The OPEN EU that Bridge downloads when my phone is connected, and is the same one which is referred as "Vodafone Italy" on LG Firmware.
In /OP i have these files: op_list, official_op_resize, custom_path_mapping, custo_group_mapping, client_id, buerycode, strangely are almost the same found on fulmics.
In Open_EU i've overlay and config folders, and these files: official_op_resize.cfg, except_buyercode.cfg and cust.prop.
The strange thing is that the vodafone brand remains also with the fulmics, in fact at everye clean installation i found vodafone apps and vodafone configuration before restore my lgbackup, what a mess lol
Click to expand...
Click to collapse
Ok so you have the everything. Just delete _COMMON filder, create SUPERSET and copy all from OPEN_EU to SUPERSET. Basicly follow the steps. Build.prop is most important part. Plus check if you have all apns needed for WiFi Calling, if not, add manually as described. It is a mess, but the key is to put that mess in an order that enables WiFi Calling. Carrier's boot animation on fulmics is a very good indication that you're on the right path to make it work. Just a small tip... Maybe start from the UI part to enable the ability to turn VoWiFi on/off and then the rest. This way you'll be able to see if or when your service becomes active. So.....
1. Copy this to your carrier's build.prop after you've coppied the Fulmics part:
persist.sys.cust.lte_config=true
persist.lg.data.iwlan.enable=true
# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
# applying GPRI auto-commit
ro.lge.radio_gpri=1
ro.lge.amrwb_gpri=1
wlan.lge.softap5g=false
# 2015-10-12 [email protected] LGP_DATA_IWLAN [START]
persist.lg.data.iwlan=1
persist.lg.data.iwlan.ipsec.ap=1
# 2015-10-12 [email protected] LGP_DATA_IWLAN [END]
2. Replace stock fulmics build.prop with the one from your carrier's rom with Fulmics part and above lines added. Check permissions and reboot.
3. Ho to hidden menu Field Test->GPRI VoLTE/VoWiFi->UX and tick all ON apart from 1, 2 and 7. Go back to main hidden menu screen and to to Service Menu->WoWiFi and change value to 1.
4 reboot and check if you have WiFi Calling QS Tile added and WiFi Calling settings enabled in call settings.
mrbeem said:
Ok so you have the everything. Just delete _COMMON filder, create SUPERSET and copy all from OPEN_EU to SUPERSET. Basicly follow the steps. Build.prop is most important part. Plus check if you have all apns needed for WiFi Calling, if not, add manually as described. It is a mess, but the key is to put that mess in an order that enables WiFi Calling. Carrier's boot animation on fulmics is a very good indication that you're on the right path to make it work
Click to expand...
Click to collapse
This evening i'll try, thanks!
@mrbeem so i have done almost all the procedura, just one thing missing, apns. Do you know if there are any for vodafone? Mine is italy, but who knows, it could work with other vodafone ahahaha
Killua96 said:
@mrbeem so i have done almost all the procedura, just one thing missing, apns. Do you know if there are any for vodafone? Mine is italy, but who knows, it could work with other vodafone ahahaha
Click to expand...
Click to collapse
What apns do you currently have on the list?
Can you check what is your sim MCC-MNC CODE? Go to hidden menu, field test->SIM Info and check values under MCC and MNC. Is it 222 and 10??
mrbeem said:
What apns do you currently have on the list?
Can you check what is your sim MCC-MNC CODE? Go to hidden menu, field test->SIM Info and check values under MCC and MNC. Is it 222 and 10??
Click to expand...
Click to collapse
These three
Killua96 said:
These three
Click to expand...
Click to collapse
Ok. I found apns for you. There are 3 more to add. Give me an hour or so and i will make apns-conf.xml for you. Make backup of your apn-conf.xml file and when i send you new one you will just replace your file with mine, go to settings wi
th apn list (one from screen above) and hit restore defaults .
One more thing... Can you tap on the top apn from the list to open it? Then scroll down to see apn type , take a screenshot and post it here
mrbeem said:
Ok. I found apns for you. There are 3 more to add. Give me an hour or so and i will make apns-conf.xml for you. Make backup of your apn-conf.xml file and when i send you new one you will just replace your file with mine, go to settings wi
th apn list (one from screen above) and hit restore defaults .
One more thing... Can you tap on the top apn from the list to open it? Then scroll down to see apn type , take a screenshot and post it here
Click to expand...
Click to collapse
Here
Thanks for everything, hope it'll work xD
Killua96 said:
Here
Thanks for everything, hope it'll work xD
Click to expand...
Click to collapse
PM me with your email address and i will send you edited apns-conf.xml. replace your /system/etc/apns-conf.xml with the one i will send you, go to apn settings tap 3dots at the upper right corner and hit restore defaults and updated apns should come up. Don't forget to tap the empty circle on the right by your internet apn to set the top one as default. I've seen on your screenshot the circle is empty and it shouldn't be
Struggling to get wifi calling on my device. H870 Fulmics O2 UK
Spoke to O2 who told me it doesn't support wifi calling?!
Even though the app allowed me to turn wifi calling on etc?!?
Need help with this as I get no signal at work
Can anyone share me your volte/vowifi working OP files.
Zerter said:
Can anyone share me your volte/vowifi working OP files.
Click to expand...
Click to collapse
:highfive: +1 i need that files.
Isn't enabling WiFi Calling in hidden menu enough to make it work? It seems to be working for me.
[email protected] said:
:highfive: +1 i need that files.
Click to expand...
Click to collapse
Link to the files below. Instructions in .txt file inside the folder.
https://mega.nz/#F!4cdDzTBR!S-_R0c3niD1PsIiJAUwVPQ
Vatt`ghern said:
Isn't enabling WiFi Calling in hidden menu enough to make it work? It seems to be working for me.
Click to expand...
Click to collapse
Which ROM do you have installed?
Im using latest fulmics. And also i'm trying to create manually ELE_EE configuration. I have all information that i need from operator but not sure is it possible. Anyway i got this phone from LG baltics to do it.
I was looking at the customizations page on XperiCheck and I was wondering which is best. I don't want to root and lose my DRM keys.
https://xpericheck.com/device/G8341
Customized GR, NOBA, IT, KR and GEL seems to be getting updates the fastest. Any disadvantage of running those in the US? I don't use VoLTE or WiFi calling.
SOLVED: The one thing I would like is to be able to turn off the NFC icon. I'm assuming there's some law or something that says that has to be on in some regions cause security or something. Is there a region where this isn't the case? Is it one of the regions I listed above?
NFC is able to be disabled in the Customized KR firmware. I also checked the XZ Premium it seems KR is the way to go.
Update:
I downloaded all carrier unspecific FTF roms and extracted their properties. When I said KR was the way to go, what I mean is KR is already updated to the latest OTA update .51. So I assume Korea gets the new software sooner most of the time. However, it seems like it has a LOT of props set. Like "ro.camera.sound.forced". So that's maybe not so good.
Update:
OK, I guess I got this totally backwards. I'm assuming if ro.nfc.icon.enable=true then I -->cannot<-- turn it off.
Here's a list of all the ones with "ro.nfc.icon.enable=true". Do not use these.
AR
BR
DE
FR
KR
UK
Here's a list of the ones that are already on .51:
GEL
GR
IT
KR
NOBA
KR is the only overlap, so avoid.
Based on what I'm looking at, NOBA seems to have the most sub configuration files, which I assume are per carrier changes? Maybe that increases the chances of VoLTE and WiFi Calling? Not sure.
IT has the least folders and settings. Maybe THAT is best since you would think MOST things are not disabled? Not sure.
dokujaryu said:
I was looking at the customizations page on XperiCheck and I was wondering which is best. I don't want to root and lose my DRM keys.
https://xpericheck.com/device/G8341
Customized GR, NOBA, IT, KR and GEL seems to be getting updates the fastest. Any disadvantage of running those in the US? I don't use VoLTE or WiFi calling.
The one thing I would like is to be able to turn off the NFC icon. I'm assuming there's some law or something that says that has to be on in some regions cause security or something. Is there a region where this isn't the case? Is it one of the regions I listed above?
Thanks!
Click to expand...
Click to collapse
If you don't use VoLTE or VoWiFi, then there's no difference. The band support is the same.
If you don't want the NFC icon, you'll have to download each firmware, extract the OEM sin file and look at the system-properties/config.prop file.
If the icon is enabled, the file with have a line with "ro.nfc.icon.enable=true" in it.
You can extract the OEM sin file with UnSIN and it will produce a ext4 image which can be opened in 7zip.
I would look for you, but I'm not all that keen on downloading multiple GB's of firmware just to check.
pbarrette said:
If you don't use VoLTE or VoWiFi, then there's no difference. The band support is the same.
If you don't want the NFC icon, you'll have to download each firmware, extract the OEM sin file and look at the system-properties/config.prop file.
If the icon is enabled, the file with have a line with "ro.nfc.icon.enable=true" in it.
You can extract the OEM sin file with UnSIN and it will produce a ext4 image which can be opened in 7zip.
I would look for you, but I'm not all that keen on downloading multiple GB's of firmware just to check.
Click to expand...
Click to collapse
Is there anywhere I can get a generalized list of differences between firms? Like, which one use 4G, 4G+, and LTE icons? That's probably the only thing I've ever noticed.
Updated main post, I downloaded many Customized XXXX firmwares and KR seems to be the way to go.
Which firmware support Volte
KumarAnup said:
Which firmware support Volte
Click to expand...
Click to collapse
Short answer: All firmwares support VoLTE for someone and no firmwares support VoLTE for everyone.
Long answer:
VoLTE support is handled by the files in the OEM sin file and is different for each carrier.
See here where I describe the bits in the OEM partition that handle VoLTE. I'm specifically talking about T-Mobile US, but it works the same way for all other carriers as well.
Basically, your MCC/MNC is looked up by the CustomizationSelector.apk and converted to a 3 digit "config_id". That config ID number is then used to select the proper modem file and to overlay the system UI to allow the VoLTE controls to be shown and used.
Each region / carrier firmware has different carrier specific configurations that are used for this.
So you would have to check your region's firmware to see if your carrier is supported.
Specifically, you would need to decompile the /oem/overlay/com.sonymobile.customizationselector-res-305.apk file, then look at its res/xml/configuration_selectors.xml file, which contains a number of "sim_config_id" values that look like "S264.1".
Then you need to find that value in the res/xml/service_providers.xml file and look at the MCC/MNC values associated with it to determine if they match the MCC/MNC values of your carrier.
If you have a match, then the "config_id" value in the res/xml/configuration_selectors.xml file will be used to set your modem to the value found in /oem/modem-config/XXX/modem.conf, where "XXX" is the 3 digit "config_id".
Finally, the overlay APK's found in /oem/overlay-XXX/ will be applied to the base applications. Specifically, the com.android.carrierconfig-res-XXX.apk should contain values in res/xml/vendor.xml such as <boolean name="carrier_volte_available_bool" value="true" />.
That's how VoLTE is handled.
EDIT:
Additionally, if the modem has a name that includes "ims" then it probably supports VoLTE for your carrier. If not, it probably doesn't. The actual modem files are found on the system partition at /system/etc/customization/modem if I remember correctly. But you still need the OEM partition bits to get that modem selected and the VoLTE controls enabled.
Updated to contain all the property files I extracted and an analysis, based purely on property files, on which ones I find most desirable (spoiler, it's IT).
Someone already found a Firmware which supports VoLTE in Germany - Deutsche Telekom?
I'm sorry to add my question, could anyone point me to a way to change my firmware using a Mac?
Sony's tool is Windows only and the other NewFlasher the same.
Also, where can I download FTF files?
Thank you in advance to anyone who will kindly help
I'm on Customized BLX (Belgium-Netherlands) and apparently I don't receive updates. Even though 374 has been out for a while, even on BLX, I'm stuck on 324.
pbarrette said:
Basically, your MCC/MNC is looked up by the CustomizationSelector.apk and converted to a 3 digit "config_id". That config ID number is then used to select the proper modem file and to overlay the system UI to allow the VoLTE controls to be shown and used.
Click to expand...
Click to collapse
Not only MCC/MNC is looked up, but the GID1 is important, too. That's my problem with German carrier "Congstar" (uses "Telekom" network) which supports VoLTE now, but the config has not changed in the firmware of course...
MCC = 262 (Both Telekom and Congstar)
MNC = 01 (Both Telekom and Congstar)
GID1 = 44 (Only Congstar! No GID1 for Telekom)