hi there I been able to get wifi calling and volte working on my non branded HTC u11+ and 12+ dual sim
https://forum.xda-developers.com/u12-plus/how-to/wi-fi-calling-volte-t3867267
Wish this was found last year... Good to finally know that this can be done.
Vodafone CH & Sunrise CH
Confirm working for Swisscom (22801) & Sunrise (22802)...well done!
:good:
Thank you for all your help. I finally managed to get VoLTE and VoWIFI working on my U11+ European DualSIM.
But it seems that the modifications described here are necessary (at least some of them) but they are definitely not sufficient,
at least for every European carrier. In my case they were not, for Orange Romania, the settings were enabled but the radio would not
register with the network for VoLTE and VoWIFI.
What I needed to do were the changes described for the OnePlus recent phones, with the PDC tool and the Qualcomm drivers.
I found in /vendor/mbn/mcfg/... the *.mbn specific files for many carriers, and mine Orange RO.
Took the mbn file from there and activated it in the PDC tool in usb diag mode (search for this in the OnePlus forums).
Then I just edited HTC__034.xml (my CID) for just these parameters:
" <item name="carrier_volte_available_bool" type="boolean">true</item>
<item name="carrier_wfc_ims_available_bool" type="boolean">true</item>
<item name="carrier_htc_volte_reg_icon_bool" type="boolean">true</item>"
, last one is optional if you want the VoLTE icon, but it's kinda big, only the first 2 are actual enabling functionality.
Then after reboot everything worked perfectly.
Related
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code •#0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
bump
bump, come on people someone must have some info
have you tried *#2263# ??
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
esjames said:
have you tried *#2263# ??
Click to expand...
Click to collapse
that is for the snapdragon version, i have the international exynos version and the *#2683662# code used to work but after the update it now says unsupported
bluheart said:
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
Click to expand...
Click to collapse
possibly yes, im not sure which soc the indian version has whether its snapdragon or exynos but if its exynos then seems samsung have disbaled it after a recent update for whatever reason
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Bryan48765 said:
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Click to expand...
Click to collapse
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
With regards to the CSC's, i can only comment on the XEU CSC which is part of the OXM multi csc and the one my phone is on and on that it says not supported for the code.
I haven't checked on root, don't really want to root my device
hamzahshakeel said:
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
Click to expand...
Click to collapse
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Bryan48765 said:
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Click to expand...
Click to collapse
i tried the logcat using the filters you provided (i.e. RILS, RILD etc) and yes it does bring back logs relating to those services however its not enough, all it outlines is when i type the code and monitor the logs subsequnt to the typing of the code the log just shows it trying to open the process associated with the menu, it doesnt show what it tries to do in between me sending the code and the response coming back so comparing that with a working code log will bring back nothing of note
however having said that i did try the full system wide log which was a bit teidous given it logs everything so going through it and pinpointing the relevant piece of log was a bit hard, i will attempt to log again using my s8+ and another samsung phone for which the same code works on and then post it here
try install phone info . this programm has all codes inside
Guys, the same in brazil. Since the begining of the year I've tried to activate 256QAM+MIMO 4x4 in my sumsung galaxy s8 using *#2683662# and by now it doen't work as return the message "not supported". Do you guys has reached some progress on it?
Seems they changed something inside the CP (modem.bin) and disabled the code. Flashing back the AQF7 - CP file will get back the code, but don't know the effect.
Yes I also noticed this a couple months back and made my own thread on it. So far there has been no progress except to flash a previous older update
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
no_name_no said:
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
Click to expand...
Click to collapse
Ive tried this but not work
Enviado desde mi SM-G935F mediante Tapatalk
hamzahshakeel said:
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code #0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
Click to expand...
Click to collapse
Unfortunately starting with Android v8.x.x (Oreo), test codes sent to the RilServiceModeApp via android_secret_code://<code> even by root are being denied.
If the test menu *#2263# or *#2683662# or *#2766338378# doesn't work with your current sim card, then try the following.
Find a couple of other active or inactive sim cards (can be another local carrier or from abroad), let the phone reboot and reconfigure its CSC while on the blue bootup screen, then try the code again, since test codes are CSC specific. It's a hit and miss affair, so be persistent.
If your phone is rooted, you can try these methods one at a time.
After each step, reboot the phone and try the test codes *#2263# or *#2683662# or *#2766338378#.
1. Using Shortcut Master (free version) from the PlayStore, tap on the menu, Secret Code Explorer, scroll down to 2263 or 2683662 or 2766338378 (or Menu > Search for "band"), tap on Launch0.
2. On combination firmware edit the file /efs/carrier/HiddenMenu and /efs/FactoryApp/keystr to be "ON", which will persists even after flashing back to stock firmware.
3. Copy the <CSC>_keystrings.dat from system/etc to root/etc and set permissions to 0744.
4. Try replacing the /system/priv-app/ModemServiceMode/ModemServiceMode.apk=com.sec.android.RilServiceModeApp from a previous Android version which had the codes working, and set the permissions to 0744.
5. Flash an earlier radio (CP) which had the codes working, if the current bootloader allows it to be downgraded.
This last method works on all Samsung models/firmwares without root, but requires a special test cable, which is only available for micro-USB ports at this time.
If you can find a similar cable with a USB-C connector, then it should work just fine. By the way, using an micro to C adapter does not work.
The following is only for phones with a micro-USB port, nonetheless it makes an interesting way to enable the hidden test menus.
You can actually enable most test codes (including RIL test codes which fail to execute on Oreo of newer even while rooted, such as *#2263# band change, *#2683662 lab test mode, and *#2766338378# engineering test menu, etc) on pretty much any model/firmware/region by simply plugging in a test cable into the phone (the other end doesn't have to be plugged in anywhere, it's just the built in resistor which enables test mode/FactoryMode).
It's important to follow the next steps exactly in this order: Open the dialer, exit the dialer with the Back key (not the Home button!), reopen the dialer and now it should accept most test codes.
These cheap test cables can be found on Ebay or AliExpress, just search for "Samsung 523K uart cable" or "Samsung 619K uart cable". Some come as a combo where you can simply switch the resistor values via a switch, but you must try both values, since only one or the other will work on certain models/firmwares/regions.
I've been using this method successfully for many years (currently on my Samsung S7 with the latest 2019 firmware), unfortunately these test cables are only available for micro-USB connectors, so it won't work on the newer USB-C phones even with an adapter (because it doesn't extend the resistor lines, only the data lines). If anyone finds a solution for USB-C, please post a message here.
I got the OnePlus 6 in India, but I live in the US. Is there any way for me to change the device region to match? Apparently there are some differences in functionality between the two (notably double-tap to launch camera not working). I am rooted and have Magisk installed.
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!
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
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?