How is VoLTE implemented in Android nowadays? - General Questions and Answers

Hello,
I used iOS the last years but want to switch back to Android/customs roms. A few years ago, when VoLTE started to become available, I remember that it generally only worked on android when the phone had the carrier firmware.
A few days ago, I tried an unlocked phone with a non carrier firmware with my sim card, and volte and vowifi worked immediately. I cannot find any information how this is implemented nowadays. Is there any relation with Google carrier services? Or do modem basebands include these settings? Where is this information stored and does volte and vowifi on newer android systems "just work" as long as the carrier supports it? I'm just curious how it works, and if LineageOS for example does support it.
Thank you!

Related

Travel Sim use changes with PIE update?

Currently on Oreo...
I recall reading somewhere a change has been implemented in Pie with respect to Travel Sim use; it is now necessary to re-flash a new rom before new travel sim card can be used in a different country, is that correct?
Anyone know what the process is with respect to getting a pie flashed phone working with a new destination country sim card?

Sony Xperia 5 Wi-Fi Calling and VoLTE???

Hi.
I've been looking for posts related to this theme, but unfortunately I haven't found anything concrete.
If I dial the code *#*#‪4636‬#*#* It turns out that Wi-Fi Calling and VoLTE are turned off and cannot be activated.
I mention, that the operator supports these services, because before, on previous phones, it worked perfectly.
Is there another possibility of activation?
I'm particularly interested in Wi-Fi Calling.
I really want to stay on stock, no custom rom.
I'd be totally grateful if you could help me.
Thank you in advance.
Anybody?
Fairly certain it needs to be provisioned by the carrier
hatryan said:
Hi.
I've been looking for posts related to this theme, but unfortunately I haven't found anything concrete.
If I dial the code *#*#‪4636‬#*#* It turns out that Wi-Fi Calling and VoLTE are turned off and cannot be activated.
I mention, that the operator supports these services, because before, on previous phones, it worked perfectly.
Is there another possibility of activation?
I'm particularly interested in Wi-Fi Calling.
I really want to stay on stock, no custom rom.
I'd be totally grateful if you could help me.
Thank you in advance.
Click to expand...
Click to collapse
I'm also interested in Volte. Have you had a way to enable it? Quite a rude awakening for me that the phone doesn't readily come with the Sync toggle and the Volte option. I used to use all those and more, on the Samsung Note 10. Xperia 5 is a downgrade for me.
jackpotbox said:
I'm also interested in Volte. Have you had a way to enable it? Quite a rude awakening for me that the phone doesn't readily come with the Sync toggle and the Volte option. I used to use all those and more, on the Samsung Note 10. Xperia 5 is a downgrade for me.
Click to expand...
Click to collapse
I have VOLTE (and WiFi calling)... It's a network provision: it's not a phone setting if it's not available from your network.
kboya said:
I have VOLTE (and WiFi calling)... It's a network provision: it's not a phone setting if it's not available from your network.
Click to expand...
Click to collapse
I had Volte on Samsung Note 10 with the same sim I use in Xperia 5. Just baffled why it isn't available on my phone but I suspect its a regional firmware related issue.
How to Enable Volte and 5G Without Permanent Root on Xperia 5 III and 1 III
First of all, Thanks to @johndaniel, @htcmage, @gorEisberg @Forbesii @morphvale @arjun_m4 for sharing all the information and files required for this guide. FIRST THING FIRST: Data is priceless. Always backup before you modify your phone...
forum.xda-developers.com

CalyxOS - Pixel 4a - network issues

Installed CalyxOS on Pixel 4a. Very easy install.
Now have internet access through Wifi only. Can make phone calls (Sprint network) but no internet.
Anyone willing to help or redirect to source of CalyxOS support? Doesn't appear to be much online support.
Doesn't seem to be a lot of traffic on this forum.
In case anyone is interested, conclusion on Reddit forum is that my Sprint sim card may be the problem with CalyxOS. Wish I would have known this before suffering through the install and then return to stock.
All I am really trying to do is find an alternative to stock unrooted phone so I can better manage various things as I have done with all of my previous android phones. First attempt using rooted Android 11 was successful. Unfortunately both Adaway and Titanium BU failed to function. So now back to unlocked unrooted Android 11.
Also have the same phone and issue with trackphon.
@CarlInMO All Sprint users who don't automatically switch to T-Mobile are not currently able to use CalyxOS (or GrapheneOS or similar) until T-Mobile allows open network Pixel phones to use a service called TNX. TNX will allow Sprint phones to use T-Mobile SIMs or eSIMs.
You can read more here:
PSA: Does not work with Sprint ESIM : r/CalyxOS
Just wanted to let everyone know. I tried to activate it via the chat and it wouldn't even download the sim. Switched ba
teddit.net
asuh said:
@CarlInMO All Sprint users who don't automatically switch to T-Mobile are not currently able to use CalyxOS (or GrapheneOS or similar) until T-Mobile allows open network Pixel phones to use a service called TNX. TNX will allow Sprint phones to use T-Mobile SIMs or eSIMs.
You can read more here:
PSA: Does not work with Sprint ESIM : r/CalyxOS
Just wanted to let everyone know. I tried to activate it via the chat and it wouldn't even download the sim. Switched ba
teddit.net
Click to expand...
Click to collapse
I don't know what's going on but I've been having problems just trying to get signal once I put my metropcs card in my pixel 4a

Question Request for help to successfully activate VoLTE/VoWiFi in Australia

I've a VoLTE/VoWiFi activated Telstra/Boost SIM that's confirmed to work fine with both stock-standard Moto G 5G Plus & iPhone 11 Pro Max, delivering those features in Australia.
Rog Phones in general & Rog phone 5 in particular are known to lack VoLTE/VoWiFi features with all of the Australian carriers. ASUS Zentalk forum has a few threads about it. (Of course, I too escalated it there for any official help, but none will be forthcoming anytime soon, from what I understand ). I'm genuinely in need of VoLTE at work due to terrible 3G but decent 4G there; and at home in need of VoWiFi due to terrible 3G but excellent WiFi backed by snappy fibre Internet connection.
My phone is an ASUS_I005DA model with build number WW_18.0840.2106.86. Neither "4G Calling" nor "Wi-Fi calling" settings are visible by default, but upon dialling "*#*#3642623344#*#*", those options become available. Though those features can be activated/toggled (and they stick around till the next reboot), they actually don't really make those features work (i.e., phone still drops down to 3G when making phone calls; similarly, calls simply don't go through WiFi, as is proven in airplane mode with WiFi on). This I understand is due to lack of .mbn files for the modem to support Australian carriers in general, Telstra in particular. (I gather that with previous Rog phone models, by injecting .mbn file(s) into the modem image, folks were able to get VoLTE and VoWiFi working in Australia.) I'm essentially looking for precise/tested/proven steps to accomplish just that but on Rog Phone 5.
This is where I've had it both boot loader unlocked & the system rooted with Magisk, in preparation for undertaking any and all such steps.
Has anybody been able to successfully access modem (i.e., Qualcomm Snapdragon X60 modem on Snapdragon 888 SoC found on this phone) from Windows or Linux systems for this sort of work? If yes, especially for Windows, what drivers did you use? (name, version info & where to download them from would greatly help) What additional software did you use on the Windows computer end (such as QPST) & on the phone end (such as QCOMDiagMode.apk & what version & from where was it sourced please?) etc. would be of great help.
A dumb question: Would it be at all possible to flash modem with updated image (incorporating the necessary .mbn file(s)) from within Android itself? Or Android itself doesn't have ADB to help with such tasks?? Just curious as I'm fine to work off either Windows or Linux end.
Thanks in advance for any useful guidance & direction.
The most likely answer would be to find how they made or picked the files with the 3 and try to make or find parallel 5 versions. The files should be compatible with fastboot (mbn is one of the extensions they use for firmware images).
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
It's also going to be an extremely experimental process, so the only tested and proven way will be to let someone else do it first. Hopefully you can find someone else in Australia with the same issue that is willing to put their device up for testing.
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
JazonX said:
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
Click to expand...
Click to collapse
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
twistedumbrella said:
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Click to expand...
Click to collapse
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
JazonX said:
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
Click to expand...
Click to collapse
AsusVoLTE/MainActivity.java at master · HomerSp/AsusVoLTE
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
It's literally running the setprop commands, but...
[MOD-ish] AsusVoLTE w/ Root Fix
This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated. I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's...
forum.xda-developers.com
Edit: moved to a separate thread, since it is not specific to this issue
I've had VoLTE show up on mine from day one with no problems, using Vodafone AU. I don't get VoWifi though - I don't know if that's dependent on your ISP. I use TPG for broadband at home.
That's great to hear! Thanks for your confirmation.
"Vodafone Wi-Fi Calling is not available to customers on prepaid plans" in Australia, according to this: https://www.vodafone.com.au/support/device/wi-fi-calling
Perhaps you're their prepaid user?
Hopefully, official VoLTE and VoWiFi support for Telstra and Optus isn't too far, seeing how unofficial community support isn't ready just yet.
Did you managed to find a way to write .mbn? In AsusRogPhone2 it was easy (via Diag mode, efstools etc, with A10 though), but in AsusRogPhone5 efstools freezes every time at port listening stage, so this methos it's a no go for now, for some unknown reason.
Vodafone in Australia has VOLTE and WIFI calling for Rog 5. I went from Vodafone (had Volte) to Telstra (Had literally nothing, had 10 support tickets with telstra that first month in regards to getting volte, wifi calling and reception issues) said screw it, went right back to Vodafone, and boom had both Wifi calling and VOLTE on the Rog 5. Plus my reception is god tier. Telstra only supports certain phones (literally like 2 series) and thats it. So yeah. Thats how I solved the VOLTE issue. Should have just stuck with Voda to begin with, but wanted to give Telstra a go. Never again. Garbage service.
Just to wrap-up my original request, as of Nov 2021 firmware update, thanks to ASUS incorporating necessary MBN file(s) for Telstra (and Optus too from what I've heard at other forums) in that firmware update, after dialling Enhanced-4G code, VoLTE and VoWiFi functionalities become available in Settings. Toggling those options does successfully activate both of those functionalities on Telstra network. According to what I've heard on Whirlpool, even Optus is now supported in the same way.
Alas, those settings don't stick over a reboot, so what procedure needs to be done after every reboot. Perhaps ASUS will make them stick in a future firmware update.
It's possible to make them stick across reboots on a rooted phone, using setprop tool.
Thanks

VoLTE/VoWiFi device model spoofing when device not allowed by carrier

Hi,
I've got several devices with VoLTE/VoWiFi capacity (like Xiaomi mi 9T Pro, OnePlus 8T, Xiaomi Mi 9 SE, Google Pixel 3...), but that are not supported by my carrier (Orange France). They only allow it for the devices on this list, according to tests they performed in their lab to ensure there aren't any issues to register them on their network :
https://reseaux.orange.fr/famille/appels-wifi
However, the other carriers in France I tested (SFR and Bouygues Télécom) are allowing these devices to have VoLTE/VoWiFi (I used both sim slots, and I have LTE data access on both. It's always the non-Orange SIM which can make LTE or Wifi calling).
Does someone know how to fake my device model in a carrier perspective ? I tried Device Faker plus and Android faker (on this thread : Android Faker) Xposed modules (on different LineageOS versions with Magisk installed and Riru/LSXposed loaded), but it's quite hasardous to make any random changes, without being sure which one could be effective to change.
Thank you in advance if someone has a solution !
Hi,
I'm sorry to answer so late but i just subscribe to orange, and i have a poco f3, i think this device isn't compatible with this carrier, and i want to know if you find a way to get it work.
Thank you
titou4488 said:
Hi,
I'm sorry to answer so late but i just subscribe to orange, and i have a poco f3, i think this device isn't compatible with this carrier, and i want to know if you find a way to get it work.
Thank you
Click to expand...
Click to collapse
If the carrier doesn't support the device, there is nothing you can do.
No, sorry, I didn't find anything. It seems all you can do is related to play store, and so on. I was able to fake my phone model to be able to install certificates from my company (for emails sync, through exchange), but that's it. It seems it's handled directly by the chipset, and you won't be able to change that within Android.
A year later, I'm on the same boat. Is there anything new around this?

Categories

Resources