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.
Related
hello,everyone.i'd like to ask a question,i modity , configurate the content of ''/system/etc/apns-conf.xml'' and i set my own network provider's APN settings.But when I use the restore default Settings ,it didn't show the APN information，which i set in the file ''apns-conf.xml''.is there any ways can mandate the system to identify it except WIPE.thx...
PS:
finally,i found the solution,you need to modify the file of ''framework-res.apk'', the internal value of ''apns.xml'' must be consistent with that in ''etc/apns-conf.xml''.only this can work,otherwise it will be invalid.
mapleshadow said:
hello,everyone.i'd like to ask a question,i modity , configurate the content of ''/system/etc/apns-conf.xml'' and i set my own network provider's APN settings.But when I use the restore default Settings ,it didn't show the APN information，which i set in the file ''apns-conf.xml''.is there any ways can mandate the system to identify it except WIPE.thx...
Click to expand...
Click to collapse
Gingerblur has a full apns-conf.xml . Pull it from there, and push it to your phone.
If your networks MCC-MNC do not match an entry in the apns-conf.xml it won't pull up any settings.
i already tried ''apns-conf.xml'' from gingerblur,but it didn't work.my network provider is not ATT,please tell me how to fix this problem.in other words,how can ''apns-conf.xml'' itself automatically set ,which i have modified it.besides,i don't want to WIPE my atrix.FYI,i'm now living in china.
the Configuration information of my ''apns-conf.xml'' is provided by MCC-MNC information of the network i am using.
Yeah the GingerBlur apns-conf.xml file didn't work for me either. Australian networks aren't in that one. I edited the stock xml file, put in my APNs, rebooted, clicked "Reset to default" (under the APN settings page), and my two APNs were there (default & MMS).
So it should work for you. Did you reboot after editing (or pushing & pulling) the file?
1.modify ''apns-conf.xml'',
2.use adb push access into /system/etc/ to Cover the original source files,
3.reboot phone,
4.enter APN settings,Restoring default Settings ,but it didn't work.
this is my operation.it confused me.If your modifications effective,is this because the MMC MNC of your network had not been shielding ??
Moved as not andorid development
After testing，i found that the original official version 1.5.2 Really can automatically refresh the APN configuration.but what's the reason??? is there any problems with my operation method??or i didn't notice some mechanism
finally,i found the solution,you need to modify the file of ''framework-res.apk'', the internal value of ''apns.xml'' must be consistent with that in ''etc/apns-conf.xml''.only this can work,otherwise it will be invalid.
I got a Sprint LS990 ZV6 phone from ebay. I decided to use it in T-Mobile, so rooted it. After following so many steps, the phone is not accepting any SIM card when I switch to GSM.
I followed below steps.
- Downgraded phone to ZV4 from ZV6
- Rooted the phone using Stump root
- Changed the carrier options as per http://forum.xda-developers.com/sprint-lg-g3/general/unlock-sim-gsm-how-to-t2853594
- Added APN settings for T-mobile changed network pref
- Inserted my SIM and rebooted the phone.... I shows No SIM card (the SIM is working properly in other phones & I tried couple of SIMs nothing works)
Can anyone please tell me after downgrading & rooting the phone, will it show Active SIM for GSM (i.e. signal bar not with red cross and No SIM icon).
If anyone faced this issue and resolved it, please help me also on this. I have been struggling from more than 2 months to fix it.
Try this http://forum.xda-developers.com/sprint-lg-g3/general/how-to-gsm-unlock-t2961099 I made it and listed people that confirmed it working if you need help pm me or them.
Finally after following below steps it worked
GSM Unlock for Sprint LG G3 (Works for US GSM Carriers & International Carriers)
1. Root the device using StumpRoot - Download here http://forum.xda-developers.com/lg-g...rizon-t2850906
2. Install SuperSU & Root Explorer & 920 Text Editor (or you can use Rom Tool Box for build.prop editing)
3. Copy build.prop from /system/build.prop to /sdcard
4. Open /sdcard/build.prop in 920 Text Editor
5. Edit line 268 and change ro.build.target_operator=SPR to ro.build.target_operator=spr
6. Save the file
7. Go to root explorer and copy build.prop from /sdcard to /system/ - try and delete existing build.prop and then copying the one from /sdcard instead of overwriting the existing file. I've encountered bootloops when overwriting build.prop
8. change permissions on /system/build.prop file you just copied to "rw - r - r". This is very important - when you copy and paste build.prop it loses the correct permissions and incorrect permissions will result in bootloop
9. reboot the device
10. It should now be unlocked. You will be unable to change the Network mode under "Mobile Networks" which will be grayed out so use the app "Network" from the play store to change the modem to "GSM (auto PRL)
11. In a few seconds you should see a signal. If not reboot the device once again and it should work.
12. Download "Tweakker" from the play store to get to APN settings and configure required APN settings for your carrier. After you are done with this step, you should have 3G/HSPA+ or Edge connectivity
1619415 said:
Try this http://forum.xda-developers.com/sprint-lg-g3/general/how-to-gsm-unlock-t2961099 I made it and listed people that confirmed it working if you need help pm me or them.
Click to expand...
Click to collapse
Thank you. I was using these steps as well.
Now the next search is using this phone in T-Mobile or at&t for LTE.
Does any one got any spell for this
As far as I know you cannot use LTE due to the face our device does not support it.
I have recently been trying to flash and root my NEXUS 6 device to try and get VoLTE to work on it ; The instructions I received (at a high level) involved flashing the device with a custom ROM (I have tried LMY47D, LMY47M and LYZ28K) , rooting It, updating the qcril.db (to include my MCC/MNC) , updating the apns-conf.xml (to add my IMS APN) and finally modifying the framework-res.apk to enable the 'config_carrier_volte_available' flag for my MCC/MNC.
After doing all the above, I can confirm that I am now seeing the extra option in SETTINGS->MORE->MOBILE NETWORKS called 'Enhanced 4G LTE Mode' which I have enable along with the extra config that can be done from the *#*#4636#*#* menu.......Unfortunately , my device does not try to REGISTER with the IMS network nor do I see any extra settings on the phone (like IMS calling) to configure IMS specific settings. I have checked the android logs and can see the UE is successfully loading the IMPI,IMPU,DOMAIN and P-CSCF from the ISIM Module however nothing seems to happen.
My one observation is that my added APN (in the apns-xml file) does not show up in APN settings and I have to manually add the IMS APN., so my suspicion is that perhaps I am either not setting this properly or perhaps there is more to all this....Therefore I would like to present this challenge to the clever brains in this forum and would appreciate any guidance that I can get,
Recently I had some bad experiences with bad reception.
At the place of my new girlfriend is very bad GSM and LTE reception. At her place of residence I could not be reached with my OP3T and I could not make outgoing calls. When I called her from home, our conversations were interrupted every few minutes.
Neither with T-Mobile (company card) nor with my Netzclub+ Sponsored card could I make any real phone calls. When I recently gave her a Oneplus 3 I decided to make both devices (+my OP3T) fit for VoWifi and VoLTE.
The goal was that it should work with Lineage 17 for microg.
I have seen here some instructions that helped. There was always just a little something missing to make it work.
Below are the steps necessary to get VoWIFI and VoLTE for T-Mobile up and running:
No root solution required, no bootloader unlock required.
Ony TWRP needs to be installed.
1. Install QPST, (have used 2.7.460)
2. Install Quallcomm Diag Driver, i used 1.1 (have used 10037.3)
3. Extract modem firmware via TWRP (system/etc/firmware, or use mine from download link)
4. Enable adb root in developer settings
5. Enable USB Debugging and connect to device via adb
adb devices (check if device is shown)
adb root
adb shell
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
6. Open PDC from QPST with admin rights and choose phone
7. Rightclick on "Overseas..." and deactivate for Sub0 and Sub1
8. Remove the "Overseas..." completely (select it and click remove)
9. Rightclick on "H3G Denmark Commercial" and set config for Sub0 and Sub1
10. Rightclick on the profile again (currently pending state) and select activate a few times until Sub0 and Sub1 are active
11. Modify Build.prop (system/build.prop)
Extract with TWRP and modify locally and add this new block underneath
block #VENDOR_EDIT
[...]
#VOLTE
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.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.sys.cust.lte_config=true
ro.radio_gpri=1
ro.amrwb_gpri=1
persist.data.iwlan=1
#end
[...]
Overwrite the original build.prop with your new one and chmod 0644 (both using
using TWRP File Manager) the file.
12. Put VoWIFI + VoLTE simcard into Slot 1 of sim tray.
13. In Lineage enable VoLTE and Wifi Calling (enable prefer wifi)
To check:
After step 13 wait 20 seconds until sip registration with provider completed, then dial USSD code *#*#4636#*#* to open Field test
Open "Phone information" and check ims registration state
Ims registration=registered means you had success
The provider profile change is done at the EFS partition and stay there until you restore this one via twrp.
If Wifi is off VoLTE is used automatically, sadly Lineage OS 17.1 does not have a VoLTE indicator. But you notice that LTE stays on during call and that there is no delay now.
Without VoLTE there was a 3 seconds delay to switch from LTE to 3G/2G to make the call.
If you call via VoWIFI a new Wifi Icon is displayed in Call window.
Sometimes VoLTE gets preferred over VoWifi, although in wifi call you have set wifi call is prio.
Not sure yet what triggers this.
If you use Volte OpenMarket Commercial profile VoLTE + IMS Video call works, but not VoWIFI. So for us Denmark profile is perfect.
VoLTE also works with Netzclub (O2) card in slot one, but not VoWIFI. Could work with switching to o2 IMS apn (not tested yet since i only plan to use it for telekom currently).
I read that only slot 1 supports VoLTE and VoWIFI (chipset related) which may not be true since during the process i had a condition with VoLTE working in both sim slots (+ ims registred for both). This happened when i loaded the "Idea..." profile for testing purposes. Somehow it triggered a connection crash and did not change the profile but enabled VoLTE for both cards (this time t-mobile volte working in slot 2, netzclub+ volte working in slot 1). But since VoWIFI did not work i loaded Denmark once again and now only slot 1 worked again.
Now it is even possible to activate airplane mode and to call with T-Mobile number via Wifi.
Really cool.
https://mega.nz/file/NUcUxYRR#V2sWJuHSYxHJOuh0vAK-j5777mpT3c6sMyNr24JEwjM
Edit 2020-Oct-03:
Temporary magisk installation no longer required with latest lineage os 17.1 / lineage os 17.1 microg.
Just enable adb root in developer option, and in adb shell type "adb root"
Also attached mbn files only work for 3t, will update download link soon to contain 3 files, too
Can confirm, works on NOS 11 without using *#*#4636#*#*#. No VoLTE logo on the Status Bar, but it has the HD Sign when calling on Google Phone. Thanks for the guide!
thes3usa said:
Can confirm, works on NOS 11 without using *#*#4636#*#*#. No VoLTE logo on the Status Bar, but it has the HD Sign when calling on Google Phone. Thanks for the guide!
Click to expand...
Click to collapse
Would you tell which provider u use? also t-mobile germany?
zezinho7 said:
Would you tell which provider u use? also t-mobile germany?
Click to expand...
Click to collapse
Nope, I'm from Sri Lanka and I use the only provider that gives VoLTE. I had to google which option works with my Carrier, which was "VoLTE_OpenMKT....". Basically works with any carrier that provides VoLTE, a google search is needed to find which description to enable and if you can't, you need to test which ones are required for VoLTE.
Just me dropping by saying this was super helpful!
Running an OP3 on LOS 18.1. Wanted to avoid going back to OOS 9.0.6.
Enabled VoLTE on jaMobil! (T-Mobile Germany Network). I used the "Volte_OpenMkt-Commercial-CMCC" profile.
My profiles were fairly empty - not a single European Country name in the profiles. But worked Thanks again.
EDIT: Since I used the OpenMkt Profile I got everything but VoWifi working. But I don't have any country-specific profiles. Can I load yours somehow?
Ive had this issue and ive found just changing the build.prop locally on the device - Using TWRP
# 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
Does the trick
Hallo, I have a problem with the device profiles for the modem. In the firmware there are the mbn-files in /system/etc/firmware/mbn_ota in two directories: mcfg_sw and mcfg_sw_NoCDMA. In QPST I can see the profiles from mcfg_sw, but not the ones from mcfg_sw_NoCDMA which are needed to use the op3 with the german telekom. What am I doing wrong? Trying to install the files via QPST also doesn't work, by using the load button I can choose a file, but the profile does not appear in the profiles.
Would perhaps sombody here who could explain the complete mechanism depending the mbn files in the firmware directory and the profiles shown in QPST?
Thank you very much in advance!
PS: VoLTE worked for a couple of days with the profile CMCC_Volte_OpenMkt-Commercial, but unfortunately the german telekom changed something, so it doesn't work anymore.
felixchris said:
Just me dropping by saying this was super helpful!
Running an OP3 on LOS 18.1. Wanted to avoid going back to OOS 9.0.6.
Enabled VoLTE on jaMobil! (T-Mobile Germany Network). I used the "Volte_OpenMkt-Commercial-CMCC" profile.
My profiles were fairly empty - not a single European Country name in the profiles. But worked Thanks again.
EDIT: Since I used the OpenMkt Profile I got everything but VoWifi working. But I don't have any country-specific profiles. Can I load yours somehow?
Click to expand...
Click to collapse
were you succesful enabling volte/vowifi in the meantime? I'm not able to make it working ...
accuphase said:
were you succesful enabling volte/vowifi in the meantime? I'm not able to make it working ...
Click to expand...
Click to collapse
Switched to a OP 9 Pro in the meantime. But as i have said. VoLTE worked vor me. VoWifi not.
I see lots of discussion on rooting, unlocking bootloader, etc. But I am wondering if there is guide describing how to enable volte for tmobile? That is all I am looking for and I am really not savy/technical when it comes to phones. I have the dual SIM 850 emw and I really dont want to lose use of the phone when tmobile dumps 3g next month. Thank you
Found this. Sort of cryptic.
I used the dailer code on my Samsung to verify VoLTE was enabled, otherwise it doesn't show the setting or that it's even HD.
Apparently AT&T supports this device if your carrier drops the ball. Verify this though...
armodons said:
Thanks for pointing me in the right direction! I now have VoLTE and Wifi Calling working on my LMG820QM (on T-mobile).
I have the BPT variant of the LMG820QM, for which VoLTE and Wifi Calling does not work. After bootloader unlocking and rooting, I tried the above VolteFix-v1 but wanted Wifi Calling. Forcing the option to appear via a profile in Universal Enabler in the hidden menu* did not work and instead caused LG IMS to continuously crash.
*For those interested in the hidden menu, first create an empty folder named "enable_ue" in internal storage. Then go to the dialer and type *#546368#*820#. In Field Test > Universal Enabler you can "Create New Config" and manually enable VoLTE, ViLTE, VoWIFI, and ViWIFI. However, even though these options became enabled in *#*#4636#*#* they didn't seem to actually work.
Next, I tried to crossflash partitions from the US Open kdz but was unable to due to a size mismatch of the OP partition (among other problems).
Finally, since I had already extracted the OP partition from the US Open kdz (G820QM20f_00_NAO_US_OP_0402.kdz), I extracted files that looked relevant and copied them over using a root browser into /product/OP. After setting permissions and restarting, I now have working VoLTE and Wifi Calling!
The files are cust.prop [update: apparently not needed; my existing one worked just fine], all the files in config, and a few folders in priv-app [update: these are the apps for Wifi Calling!] not present in my phone's kdz (not sure which ones if any of these apks are actually needed but since it works I'm not going to experiment more). See attached for details.
Note: Since these files are from the US Open kdz, it will likely only work for US carriers. But the process can be repeated for other regions with the right kdz.
UPDATE: Replaced the attachment, had the wrong files in Config.
** Noticed that upon factory resetting the wrong default APNs are inserted. Had to factory reset on original files, have APNs setup correctly, then copy the attached files (did not copy over cust.prop this time and still worked).
Click to expand...
Click to collapse
Hello jdapp,
I was able to get VoLTE AND VoWIFI on Mint (T-mobile) with these instructions. I also posted what I did on Post 50. The files work for firmware 20 but if you need the ones for firmware 30 let me know.
Awesome thanks. Yes if I could get the firmware 30 files that would be great.
dahveedsolorzano said:
Hello jdapp,
I was able to get VoLTE AND VoWIFI on Mint (T-mobile) with these instructions. I also posted what I did on Post 50. The files work for firmware 20 but if you need the ones for firmware 30 let me know.
Click to expand...
Click to collapse
jdapp said:
Awesome thanks. Yes if I could get the firmware 30 files that would be great.
Click to expand...
Click to collapse
No problem, let me know how it goes.
So I have tried to do the bootloader unlock and flash but every time I get a Download fail: Sahara Fail: Q SaharaServer Fail: Process fail?
Any thoughts?