yashsingh1/xdaforums huggingface dataset:
[Windows 10 Mobile] Charkatak:
[MENTION=6541555]nate0[/MENTION],

Good:

So I did all of the above using my extra Lumia 950. T-Mobile features such as VoLTE, HD Voice and WiFi Calling do work(Band 12 need to test) Thanks!

Improve:

There is no LTE setting in sim settings. The highest is shown as 4G. As for the status bar, it just shows L, instead of usual LTE. Here comes the question, is there a way to change L to LTE and make sim settings to show LTE as well and not only 4G?
[Windows 10 Mobile] nate0:
4G is LTE. LTE is 4G. They are synonymous to carriers. I would not worry about it displaying no LTE in that drop down. The fact that is shows L and not LTE is something I would need to look at. To me I just add the entry manually here: SOFTWARE\Microsoft\Shell\OEM\SystemTray\DataConnectionStrings

Look for the LTE keys and set there value back to LTE from L.

---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------

Sorry I am lost as what your goal is...apologies.

What are you trying to accomplish?
[Windows 10 Mobile] Charkatak:
I tried to look for that software folder(SOFTWARE\Microsoft\Shell\OEM\SystemTray\DataConnectionStrings) and its contents, but don't seem to find it. Do you use a special program to view files? Initially I was using WPinternals to copy needed files to the phone.
[Windows 10 Mobile] nate0:
It's in the registry. It's part of the Shell keys under Software.
[Windows 10 Mobile] Charkatak:
Looks like I needed Interop Tools appx to make registry changes.

So I did change L to LTE in the status bar and I changed 4G in the settings to LTE. I don't know if you see selection for 3G and 3G only under highest speed list as well.

WiFi calling is working on wifi preferred, wifi only and when I select cellular preferred, it seems to work, but need to test in actual environment, when there is no cell signal.

So do you know if second sim will not be shown for sure and it is disabled on purpose by you or anubis?
[Windows 10 Mobile] nate0:
Correct, interop tools is the reg editor of choice for most of us.

As far as the modem file goes. The one I created was for a single sim model RM-1085. I think to make a dual sim modemconfiguration file would be simply duplicating the the nvi file and making trailing them with a 0 and a 1 in the file name. But I suspect it is not that simple....I could attempt a new modemconfiguration file for you if you want to test a dual sim Lumia with it. It would need to include a nvi file for each sim slot (0 and 1). Let me know...
[Windows 10 Mobile] Charkatak:
Your modemconfiguration.cab file contains 6 nvi files which have 0 at the end of their filenames. If you make a copy of them and just edit the title to reflect 1 will that be enough or contents of nvi file will need to be edited as well?

I normally don't need 2 sim cards, but when I do travel it really helps and don't need to carry 2 devices.

I believe it would be beneficial to users with 2 sim cards. Once it is working properly, you could have two options for users with single and dual sim phones.
[Windows 10 Mobile] nate0:
I do not know if just copying them will work. Do you want to try? I do not have a dual sim Lumia x50 series model to test with...
[Windows 10 Mobile] Charkatak:
I could, but haven't tried to run any tests on my dual sim 950, only tried on single sim device. Normally Lumia 950's modemconfig file contains a lot of nvi files. Your cab file only has 6 in it. How would you know which ones to remove? If I would somehow understand these nvi files, that would make things easier at least on my side.

If you could at least take a look at nvi files and possible spot where 2 files talk to each other. Once I'll be home, I will check my phone's modemconfig file and see if there are files with 0 and 1 in the title.
[Windows 10 Mobile] nate0:
The reason the default modem file contains a ton of files in it is because Microsoft set them up as multivariant phones. I am not certain how many variations of modemconfiguration files are actually out there, but for like the RM-1085/NAM for the US has modem nvi files for every other Country code and mobile network operator that coincides. So lets say you traveled to Italy, and needed a new sim temporarily. You bought a pay as you go sim. As soon as you pop that new sim in with a new/different imsi number tied to it, that triggers the ADC/NVI updater and it goes and looks for the coinciding nvi files. So you are on the right track in that you need the files together to get things to set up right.. If you want to travel and use your phone even with one sim card in it you in another country you would need to reconfigure the modemconfiguration file for your liking. I am no expert at this, was just experimenting to get something I needed out of my Lumia that was not working automatically. So it is not perfect and may not work in every situation the same way...
[Windows 10 Mobile] Charkatak:
So tonight I have tried files on my dual sim 950, but it isn't working as it did on single sim device. So something in modemconfig file forces device to be in airplane mode.

I did the following:

1) I first tried to copy all needed files to my dual sim device - airplane mode activates and I was not able to turn it off.

2) Tried all files, except modemconfiguration.cab and just kept my original in place. Phone works properly and I do see IMS and other toggles, but IMS is still unregistered

3) Made copied of 6 files located in modemconfig cab and changed files names to reflect 1 instead of 0 - still on airplane mode, can't disable it and can't access any sim settings.
[Windows 10 Mobile] nate0:
Normally when that happens. Airplane mode after an nvi update occurs, is due to a configuration sent to the phone that it's not capable of or compatible with.

Did you build a new cab file after changing/updating it?

I can hand over two cabs I modified for dual sim if you want to try them...
[Windows 10 Mobile] Charkatak:
I just edited titles to reflect 0 and 1 and made fresh cab files. Yes, I can try your files.
[Windows 10 Mobile] nate0:
You can test these. Jut rename the cab to the default name when you want to use it.
[Windows 10 Mobile] Charkatak:
Do I need to test one of these cabs at the time? As for the name I will use: modemconfiguration.cab for each file?
[Windows 10 Mobile] nate0:
Correct on the name. Just one at a time. You can paste them all there and rename them one a time.
[Windows 10 Mobile] Charkatak:
Here are the results:

1) Your modem file #0 performs the same way as my original modemconfig cab does. Meaning that toggle for VoLTE, WiFi Calling and IMS are there, but have no effect.

2) Your modem file #1 performs the same way as yesterday's file, which would enable Airplane mode.

3) I also tried taking my device's original ADC folder + your modem file #0 from step 1 - Toggle are present, but not working

4) Also took ADC from T-Mobile 640 + modem from step 1 - Toggles are there, but nothing is happening.

*In steps 1 and 2 - your updated ADC folder and its contents were used.

So file #0 at least is very neutral and doesn't introduce airplane mode. It may seem that files in ADC folder may need to be re-updated, what do you think?
[Windows 10 Mobile] nate0:
I think you are right. Might be they pertain to that single sim mode for that Lumia 640 (T-mobile branded) only.
[Windows 10 Mobile] Charkatak:
Do you know why your modem files have this folder: {38806042-8894-4002-a651-64130e88b4cf}. I did check the original modem cab file and yes, it does have this folder as well, but how do we know that it is connected somehow to MCC-310(T-Mobile)?
[Windows 10 Mobile] nate0:
I forgot how I stumbled upon that ID, but I knew about long before I tried making my own cab and had it logged as the ID folder for US models. I think it is in the registry maybe or in the ADC folder somewhere listed...?

I do not share all the info/details about this stuff because I am not an expert and I honestly just don't know certain things. I figured out what worked for me and shared the info for others to use if they needed or to reference...

But if you want we can try to work together to figure out the answers to your questions.

---------- Post added at 08:16 AM ---------- Previous post was at 08:09 AM ----------

Like right now I am using a 1520. A 1520.3 (RM-938) to be exact. For the life of me I cannot figure out how I am able to get HD voice on 3G with this phone but no VoLTE and no Wifi calling. On the other models of the 1520 it was impossible to get even just the HD voice with the same method I have used on the current phone. There are some things that we may never know since we are not the engineers at Microsoft or Nokia and then there are some items we can derive answers about or from, then yet there is other stuff that we can only theorize for. Why HD voice works on the 1520.3 but not the 1520 (RM-940), I may never know, on 3G is even more mind boggling to me. I thought VoLTE was necessary for HD voice, but who knows. . I can only conclude that at the SoC NVRAM level things are hard coded and/or static. They may only need to be linked at the Radio interface level via SW update/Provisioning. But the problem is we have no clue what is hard coded and what is not. That is why I have done lots of trial and error over time and that is how I stumbled upon most of what I know how to do.
[Windows 10 Mobile] Charkatak:
I believe HD Voice came from codec: AMR-WB or is using it. It was available on earlier networks such as 3G and up. I don't think it was named like that and we didn't see anything showing that we are using HD Voice. Caller could hear a better sound/voice when on a call.

I asked one Microsoft ex mobile team lead to find out if he still knows engineers that worked in Win 10 Mobile department. I also told him our/my situation about updating nvi files to make both sim slots work, but he told me that it isn't easy, you can't just rename the files :) Looks like we already know that one. Will see if anything good comes out of this and there might a took with GUI that can generate nvi files based on the user settings.

Your yesterday's package, the one titled with DS 0. It contained 4 files. Did you take first 2 files(_0) from your Lumia 950XL and then found 2 other files(_1) from another device? The reason I ask is because I want to take your initial files (that contain _0 nvi files) you provided in this thread and combine with (_1 nvi) files that you sent me yesterday. Will make a cab out of those.

One thing is really concerning is that why modem file contained in your: tmo-us_VoLTE_950xl zip puts the phone in airplane mode in DS phone, but not in single sim phone. I would at least assume single sim modem could just disable/not show the second sim and that is it, but not, it make phone useless.

Also curious to find out if anubis23's files are different from yours and they may work on my dual sim unit. He did mention that he made second sim not show in the status bar(probably in registry)
[Windows 10 Mobile] nate0:
I thought Anubis' files were different. And I'm glad you found the dual sim issue...
[Windows 10 Mobile] spe317:
I'm following this thread to see what you both come up with. I went through with the entire process and ended up with an airplane mode phone on my 950xl DS. I did spend an hour with an ATT tech who was adamant that they are now able to whitelist nonbranded ATT phones for VoLTE/HD.
[Windows 10 Mobile] Charkatak:
This was anubis's pretty much last post "I figured out what went wrong, i have to add some registry entries to the adc cab files and then i will repackage and update the original post. stay tuned."

I did some research and looks files such as Uicc_Connectivity.xml link to other files in ProvisionData.cab and ProvisionDataCriticalSettings.cab. I have tried to compare T-Mobile wording and strings in xml which do pointing to files in above cab. The interesting thing is that many settings are similar and I don't know where or if there are strings for second sim. So in some of the cab files, similar setting my indicate that "enable IMS" is set to 0 which is off and in some other files it may be set to enable IMS to 1. All this is for T-Mobile. How can the same setting for T-Mobile be in different locations, in different files?!

I also found this interesting MS page on how to configure IMS for carriers:

https://docs.microsoft.com/en-us/windows-hardware/customize/mobile/mcsf/settings-for-ims-services
[Windows 10 Mobile] nate0:
When I used AT&T I used this method for the dual sim 950 xl on AT&T. thread

This will set it with a single sim no airplane mode as far as I know...
[Windows 10 Mobile] spe317:
Thanks for the info. I'll retry the process and attempt to eliminate the issue (which is probably me). Did the VoLTE work without any sort of registry value changes?

Thanks, by the way. Your posts have been quite informative.
[Windows 10 Mobile] nate0:
With the method I linked above for AT&T the one caveat WAS to have AT&T update your account and match your sim card ID (ICCID) to a official AT&T branded Lumia 950 IMEI (RM-1105 variant)…

Now that you mentioned they can white list an IMEI for VoLTE/HD voice all you would need to do is provision the right files so the device is ready for it and then Have AT&T white list your IMEI...
[Windows 10 Mobile] Charkatak:
Link to AT&T thread doesn't work.
[Windows 10 Mobile] nate0:
It works now. I did some funky pasting earlier I guess.
[Windows 10 Mobile] Charkatak:
Looks like something happened to my phone. :( The airplane mode doesn't go away even if I replace the modem file or use WDRT to re-flash it. Searching online points to a possible issue of the "processor board or something like that" going bad.
[Windows 10 Mobile] nate0:
Did you try doing a reset of the modem to default with thor2?
[Windows 10 Mobile] Charkatak:
I thought about it, but I don't have thor2.exe app. I also believe I need to load it onto the phone. I have played with windows devices 2 years back, but since then forgot about a lot of tricks. I have used Tshell before to load apps/files to the phone.

So if you have the app and the command to load it onto the phone and how to run the reset of the modem, I would really appreciate it.
[Windows 10 Mobile] nate0:
If wdrt is installed you have thor2

thor2.exe -- C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe

Make sure your modemconfiguration and ADC files if needed are in place if needed and run thor2.exe -mode uefiflash -ffufile <path and file name of your FFU file> -do_factory_reset -skip_flash -reboot

The -skip_flash option keeps it from reflashing the ffu all over again if you do not want to.
[Windows 10 Mobile] Charkatak:
Now I remember...even found some notes that I made. Although I haven't used the command you mentioned above, but I ran it and it did help! Thousand thanks!
[Windows 10 Mobile] Charkatak:
[MENTION=6541555]nate0[/MENTION],

I know that you have seen "@MO_VoWiFi_Operator_Name_15818.dll" instead of "WiFi Calling" being named when wifi calling is active. Once I restart the device, then the name is displayed correctly. Then I disconnect wifi and then reconnect, now the name is back to "@MO_VoWiFi_Operator_Name_15818.dll" Basically to have it displayed correctly user would need to restart the phone every time phone reconnects to wifi. I did place the above dll file in the correct folder.

I was going though *.provxml files and see that "Mo_VoWiFi...dll" is mentioned in the file below.

What if I rename the value of it to "Wi-Fi Calling" will it eliminate the issue? Looks like Windows reloads this dll file only when it is restarted and not keeping it in the memory after wifi disconnects and reconnects.

Located in ProvisionData.cab file - Uicc_General_PhonePerSimSettingsIMSI_4.provxml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<wap-provisioningdoc>

<characteristic type="MCSF">

<characteristic type="Phone/PerSimSettings/$(__IMSI)">

<parm name="ShowVideoCallingSwitch" value="0" datatype="integer" />

<parm name="DefaultEnableVideoCalling" value="0" datatype="integer" />

<parm name="IgnoreMWINotifications" value="0" datatype="integer" />

<parm name="WiFiCallingOperatorName" value="@MO_VoWiFi_Operator_Name_15818.dll,-100" datatype="string" />

</characteristic>

</characteristic>

</wap-provisioningdoc>
[Windows 10 Mobile] nate0:
I guess you could try to change it in the registry to a string value and type "Wi-Fi Calling. Is that what you mean? I'm not certain what all the dll file does and if overriding it is a good idea.. I'm not certain why your device reloads it to each time. I've never experienced that.
[Windows 10 Mobile] Charkatak:
Yes, that is what I meant. It is happening every time. When I was at home, it showed "Wi-Fi Calling", then I left for couple of hours. Came back home and again it shows [MENTION=4420141]mo_[/MENTION]VoWiFi....

1) I took the zip named "T-mobile_640_NVI_updates" and only used ADC folder from it, but the rest came from your main 950XL...zip file. To me, ADC folder is the same if compared to above 2 zip files, unless you know that they aren't.

2) I do know that after hard reset, modem file and ADC folder stay intact, but what about the DLL file, does it get removed?
[Windows 10 Mobile] nate0:
It is removed on a hard reset.
[Windows 10 Mobile] Charkatak:
You know, interesting thing is going on. I am using your normal 950XL zip file which contained all needed files/folders. So after restart of the phone, Wi-Fi Calling is displayed and it auto connects properly. Then if I turn on airplane mode, turn off wifi, or turn off wifi calling, then the phone may not connect again about 50% of the time. If it would connect again, but it could take 5 or so minutes and this time, instead of Wi-Fi Calling, it just shows Wi-Fi, don't know why the work Calling disappears. Do you have T-Mobile Lumia 640 files, including modemconfig cab? I do have ADC folder + MO_VoWiFi files, but I don't think I have modem files from 640, if there is one. I believe wifi calling connected more reliably using Lumia 640's files, although the displayed name was "mo_vowifi..."
[Windows 10 Mobile] nate0:
The Lumia 640 used the older generation way of updating nvi settings with individual nvi files and not a modemconfiguration.cab file. Like modem_configuration_full.nvi and modem_configuration_update.nvi. You can grab those just about any file you want for any Windows phone granted there is an available ffu file for it. You can mount an ffu with imgmount found on the forums or dump the appropriate partition to a bin/img file and mount it that way using software.

Which files are you wanting exactly?
[Windows 10 Mobile] vijay_mum:
Hey nate0,

Could you Please say if this whole process would be possible on a Lumia 930 - INDIA Version? Or is there any other way to get the VoLTE calling on a Lumia 930 that you are aware of?
[Windows 10 Mobile] nate0:
For VoLTE in India? I would not know.

The Lumia 930 though does not support US LTE bands so to get VoLTE in US is not possible for the Lumia 930. In other countries though, I am unsure...
[Windows 10 Mobile] Talon Pro:
Any update on getting this to work without killing the Messaging app? Or getting the IMS to stay registered?

Also, you mentioned rolling back on the 830 to WP8.1 and doing all of this and then grabbing 10 and it sticking, but i cannot find anything to Interop Unlock while on 8.1.
[Windows 10 Mobile] nate0:
If messaging gets killed on windows 10 mobile after updating with modem settings that are for a single sim on a dual sim phone where it won't open you can try this.

After updating the modem/phone provisioning and the phone asks to restart you lose the 2nd sim slot. Now Messaging SIM 1 app won't open...This happens on my 950 XL DS quite often. So copied the Comms.Apps.Messaging.appxbundle file from the xaps folder into my Phones Downloads folder. Next Open Interop tools, go to General->Applications and then Package List. I uninstalled the Messaging app. Search for it and you should get two icons. I long pressed the icon that had the library symbol on it. Tap Uninstall and after it is finished check that is removed and reboot. Once rebooted I installed Comms.Apps.Messaging.appxbundle file I had copied to my downloads folder by tapping it. Messaging works again..
[Windows 10 Mobile] nate0:
[MENTION=1647275]Talon Pro[/MENTION]

I was able to cheaply get an RM-983. I am almost certain the NVI hard coded settings are going to be much different than a RM-984 or RM-985 since it is AT&T branded, but I am going to work with it. I need to sim unlock it from AT&T before I can attempt to get a T-Mobile sim to work for it. I will keep you posted.
[Windows 10 Mobile] Talon Pro:
Ok, cool.
[Windows 10 Mobile] nate0:
Ok. I finally sim unlocked the RM-983. I was able to get VoLTE and Wifi calling working on this AT&T variant with a Custom WP8 ROM that I made and flashed to it using WP Internals 2.5. I actually wanted to debrand this model to a RM-985 but it may not be possible or pretty difficult because the US model for AT&T was imaged with Reset Protection and that poses issues. I still kinda did debrand it using a custom OEMsetting reg and removing all the ATT xaps but the PLAT partition is still defined as a RM-983 ATT model. So I am content with that.

In short here is what happened. I had this model on W10M before I sim unlocked it. While on Window 10 Mobile I updated the NVI/NVRAM setting on the RM-983 with that of the 640 LTE T-mobile model using its nvi files. Then I rolled it back to WP8 using the stock FFU. Dumped the RM-983 MainOS and Data partitions from the original ffu. I took the OEMSettings reg from the RM-985 and made some modifications of personal choice. Used all the XAPs from the RM-985 and also replaced all the other files under C:\PROGRAMS\CommonFiles\OEM. Then loaded the ADC files and a set of nvi files from the 640 LTE to the RM-983 MainOS.. Bootloader unlocked the RM-983. Then flashed the MainOS I customized and the Data image. I had to do a hard reset though since there seems to be an issue flashing the data partition. The phone would not boot at first. After a hard reset it booted.

So for this model only (RM-983) I have enabled both of these things (VoLTE/Wifi calling). I still need to do some other changes to the Image files like adding the dll for wifi calling, and checking for any other issues. I also do not know yet if I update to W10M if everything will still work. Like the 5GHz wifi calling. I have never got this to work on W10M. But for some reason on WP8 currently it is working.

Update: A little clarification. Seems I was not extensive enough in checking out the WiFi calling. Even though the status icon shows wifi calling enabled for 5ghz it actually does not work if you switch it to the wifi-only mode. When switched to wifi-only mode the phone looks for 2.4ghz only. Once connected it registers ims. I have both and made a call successfully from 2.4ghz wifi while on WP8.
[Windows 10 Mobile] Talon Pro:
Effing sweet. I have one of those too. Are you planning on trying to update to 10? Let me know what the result is if so.
[Windows 10 Mobile] nate0:
I updated to W10M yes. Is on 10586.107 now. I had to push all the W10M cabs for that version manually because I changed the default DeviceTargetInfo values from their default using the OEMSetting reg. I just did not want to keep going back and forth editing...It never set the default APN after the update which happens sometimes. I have not hard reset it yet. Am updating now OTA to 14393 since it is on W10M now, it seems ok to update on its own.

Update: After adding the APN in manually. Then updating to initial version 14393 IMS registration was good and persisted through reboots. The wifi calling never showed signs of being active though (Tray Icon status). I have not tested any calls yet. It is updating to the latest version of RS1 (14393.2431). Will probably hard reset it there. Then will decide when or if to update further.
[Windows 10 Mobile] ALTXY:
How can start a high-definition video call?
[Windows 10 Mobile] dipayans24:
Chances are i can be wrong, but please tell us How did manage to enable it,unless you are using a x5x phone?
[Windows 10 Mobile] rajaganesan7:
How to Change Registry Keys

I'm using Lumia 638 4G , Its Support 4G Network , How to open Registry on the lumia 638 4g,

:confused: