Handset: Xperia 10+ i3883
Carrier: T-Mobile
Build: lineage_mermaid-userdebug 11 RQ3A.210705.001 eng.root.20210729.214831 dev-keys
Everything on the menu seems to indicate VoLTE is enabled, it also shows it as enabled when I use the # key combination from the dialer to get into the phone maintenance menu.
Right now it shows LTE+ as I am posting this message...
...but the minute I make or receive a phone call it drops to 3G or H+.
Any ideas?
Couldn't seem to resolve this, so for now I used Emma to install stock android 9 and then rooted that with TWRP + Magisk and started deleting bloatware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------[Test Platform]----------
[ Device ]
----| Motorola Moto Edge + XT2061-3 (Global)
[ Carrier ]
----| Verizon Wireless USA
[ Stock Firmware ]
----| BURTON_RETAIL_11_RPBS31.Q1-19-19-14-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[ GSI Firmware ]
----| LineageOS 18.X (Android 11)
----------[Features]----------
*** This only pertains to the test platform used, no other GSI was tested
[ Working ]
----| LTE Data
----| CDMA Voice
----| Text
----| WiFi
----| Bluetooth
----| Camera
[ Not Working ]
----| Display over USB-C *** This may not be present in any custom rom for any phone, cannot verify
----| VoLTE
[ Not Tested ]
----| Fingerprint Sensor
----| VoWiFi
----| Tethering
----------[Important Information]----------
Android 11 on this device uses a dynamic partition for various partitions called super. The only way to access system is through fastbootd
VZW (Verizon Wireless) stock firmware version confirmed working on XT2061-3, albeit without mmWave 5G (due to [this]). Using this stock was not tested with GSI, but will more than likely work.
----------[Sources of Information]----------
[How to flash GSIs on devices with dynamic super partition]
[[Tutorial] Magisk on GSI on devices with dynamic partition]
----------[Prerequisites]----------
Moto Edge + XT2061-3 *** Verizon's XT2061-1 will NOT work
Unlocked Bootloader [found here]
Stock Android 11 Firmware [found here] *** If unsure which version, use same as test platform.
Latest platform-tools [found here]
TWRP [found here] or [mirror here] *** mirror uses 7zip archive dropping size to 21.1MB from 49.2MB
GSI AB arm64 Android 11 image [found here]
----------[Guide]----------
[ Flash Stock Firmware ]
1---| Boot device into the bootloader (Volume & Power)
2---| Connect to PC
3---| Extract firmware package
4---| open flashfile.xml
5---| Execute the commands as listed in flashfile.xml by using one of the orders below
5a-------| fastboot operation var (ie fastboot getvar max-sparse-size)
5b-------| fastboot operation partition filename (ie fastboot flash partition gpt.bin)
6---| When flashing vbmeta, use this command
7--------| fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8---| Reboot to bootloader from bootloader menu
[ Prepare Data ]
1---| Boot into TWRP, do not flash
1a-------| fastboot boot twrp-3.4.0-0-burton-beta1.img
2---| If menu comes up about enter password, just hit cancel
3---| Click Wipe, Format Data, yes
4---| Click Wipe, slide to factory reset
[ Boot into fastbootd ]
1---| Boot device into bootloader (Volume Down & Power) or select reboot into bootloader from TWRP
2---| Use fastboot to boot into fastbootd
2a-------| fastboot reboot fastboot
[ Flash GSI Image ]
1---| With fastbootd we can flash directly the system partition
1a-------| fastboot flash system gsi.img
2---| Reboot and your device should be booting the GSI
[ Installing Magisk ]
1---| Extract boot.img from stock firmware archive
2---| Copy boot.img to phone
3---| Install magisk.apk from github
4---| Open Magisk, click Install, select from file, choose boot.img
5---| Copy patched magiskboot.img from Downloads to your pc
6---| Reboot into bootloader
7---| Flash magiskboot.img
7a-------| fastboot flash boot magiskboot.img
----------[Notes]----------
If you have any problems, please refer to the links posted in [Sources of Information]. Those are the guides I used. Although they include some steps omitted in this guide, they may be relevant for you.
----------[Thanks]----------
Thanks to [kusti420] for providing information about the super partition and how to flash GSIs.
----------[Feedback]----------
I have provided this guide to get feedback about which GSIs work and what features in those GSIs work. If you follow this guide, please report back what was working and any steps different from this guide that you had to take. Thanks!
i ran into trouble with this. the firmware you have and lineage your using is now outdated but i tried with both your version and the updated ones and 18.x version of lineage does seem to detect my sim card and the new one lineage 19 detects it but i get the error from verizon that my phone cant be authenticated for calls but everything else works. i notice when im running updated stock, the sim card reads fine and service works normally but before when i had it running older stock firmware (android 10) i got the same thing. everything would work but calls. then when i updated the stock firmware, everything worked. so im not sure what im missing here when trying to follow your direction for getting this installed but maybe you know whats going on since your a verizon user using the global variant. please write me back when you get this. thanks a bunch
bjf189 said:
i ran into trouble with this. the firmware you have and lineage your using is now outdated but i tried with both your version and the updated ones and 18.x version of lineage does seem to detect my sim card and the new one lineage 19 detects it but i get the error from verizon that my phone cant be authenticated for calls but everything else works. i notice when im running updated stock, the sim card reads fine and service works normally but before when i had it running older stock firmware (android 10) i got the same thing. everything would work but calls. then when i updated the stock firmware, everything worked. so im not sure what im missing here when trying to follow your direction for getting this installed but maybe you know whats going on since your a verizon user using the global variant. please write me back when you get this. thanks a bunch
Click to expand...
Click to collapse
Well I only had the phone as a test for getting mmWave 5G on the global variant, which isn't possible due to a proprietary solder pattern on the board, but I no longer use this phone.
What I would recommend for you is to flash the NON-HLOS.bin from the stock firmware that worked for you without a problem. It's the modem firmware and it could cause problems like that. I didn't have any issue with my sim card, calls worked fine over CDMA and I could get text messages and LTE data worked.
I have never even seen the error that says the phone can't be authenticated for calls. Is it coming from a verizon app or is it an android error? I would also suggest to make sure the correct APN is being used, should be VZWINTERNET. I had an issue with an older motorola where it would for some reason randomly switch to some other VZW APN that was wrong.
I didn't do thorough testing of this, I just wanted to get the baseline for getting custom roms running, but I didn't encounter anything like what you're going through. Considering you had this problem on a certain stock firmware version, my best guess is the modem firmware. I did flash the VZW firmware on the phone and that worked as well, maybe you should try flashing that modem firmware? I didn't have issues, but I can't 100% recommend it because VZW expects the QTM 5G modules to be present, which it isn't. I don't know if this could cause hardware issues. Other than that, the phones are 100% identical.
Sorry I didn't get back to you sooner, XDA's "stay logged in" checkbox does not seem to work correctly and this website is a hassle to navigate.
Knuxyl said:
Well I only had the phone as a test for getting mmWave 5G on the global variant, which isn't possible due to a proprietary solder pattern on the board, but I no longer use this phone.
What I would recommend for you is to flash the NON-HLOS.bin from the stock firmware that worked for you without a problem. It's the modem firmware and it could cause problems like that. I didn't have any issue with my sim card, calls worked fine over CDMA and I could get text messages and LTE data worked.
I have never even seen the error that says the phone can't be authenticated for calls. Is it coming from a verizon app or is it an android error? I would also suggest to make sure the correct APN is being used, should be VZWINTERNET. I had an issue with an older motorola where it would for some reason randomly switch to some other VZW APN that was wrong.
I didn't do thorough testing of this, I just wanted to get the baseline for getting custom roms running, but I didn't encounter anything like what you're going through. Considering you had this problem on a certain stock firmware version, my best guess is the modem firmware. I did flash the VZW firmware on the phone and that worked as well, maybe you should try flashing that modem firmware? I didn't have issues, but I can't 100% recommend it because VZW expects the QTM 5G modules to be present, which it isn't. I don't know if this could cause hardware issues. Other than that, the phones are 100% identical.
Sorry I didn't get back to you sooner, XDA's "stay logged in" checkbox does not seem to work correctly and this website is a hassle to navigate.
Click to expand...
Click to collapse
I'll try flashing the Verizon modem when I can. Recently, my service randomly died and I turned on airplane mode to restore service but the unable to authenticate for calls happened again when it worked fine before. I had to restart the phone to get calls working again. No idea what it was about. As for the apn, I was going to transfer the apn over from my s21 plus but it seems the verizon sim already sets the apn automatically to where it's not able to be changed. It's all greyed out. I noticed that I also got the unable to authenticate for calls before I updated the firmware. I bought the phone used and it was behind in updates. When I updated to the second most recent update, I noticed calls started to work. I haven't updated to latest since installing magisk with root broke the Ota update. I could update with a pc easy but I haven't since the things listed here are now out of date so trying to stay with the firmwares listed here. Lastly for 5G, i checked the bands the phone supports before buying it and I believe it matched one or two bands with 5G and I do get 5G in few areas. It also supports most LTE bands that Verizon gives. I didn't see any cdma support, only GSM but from my understanding GSM and CDMA is an older thing when it came to 2g or 3g. What I've gathered is if voice can be done through LTE then calls would work. So just a tip on the testing and things I've come across so far
I just noticed in the thread that voice over LTE doesnt work. I wonder if that's my issue? However I see CDMA voice is working so says the thread here. It's confusing at this point
bjf189 said:
I just noticed in the thread that voice over LTE doesnt work. I wonder if that's my issue? However I see CDMA voice is working so says the thread here. It's confusing at this point
Click to expand...
Click to collapse
Ok I remember now when I was trying to enable VoLTE the calls just wouldn't work. I didn't get an error though. You have to turn off VoLTE for it to work again. This is in Settings/Network & Internet/Mobile Network/Advanced Calling.
The developer of the lineageos gsi was aware of this issue and tried to fix it but I guess it only applies to whatever phone he was testing with.
As long as the APN says VZWINTERNET you should be fine. Trying to flash over another APN isn't worth the effort and can cause more problems than it could fix, the values are correct as long as the right APN is being selected.
CDMA is Verizons standard calling radio technology, was also used by Sprint. CDMA is being phased out though to be replaced by LTE entirely. I don't know when this will happen. If you check the GSMArena link in the first post you will see all the bands listed on this phone, and it does support CDMA, which is why calling works without VoLTE.
Considering you were having problems on the stock firmware, it seems like your issue is more than just VoLTE not working, because what you explained is not a typical issue, and no matter what stock firmware you were on, VoLTE and CDMA calling both should've worked out of the box. I would test to make sure your Verizon account even has VoLTE support first because that seems to be the only reason for error messages popping up like you had. Although this doesn't really matter though because this method does not support VoLTE from what I tested.
Knuxyl said:
Ok I remember now when I was trying to enable VoLTE the calls just wouldn't work. I didn't get an error though. You have to turn off VoLTE for it to work again. This is in Settings/Network & Internet/Mobile Network/Advanced Calling.
The developer of the lineageos gsi was aware of this issue and tried to fix it but I guess it only applies to whatever phone he was testing with.
As long as the APN says VZWINTERNET you should be fine. Trying to flash over another APN isn't worth the effort and can cause more problems than it could fix, the values are correct as long as the right APN is being selected.
CDMA is Verizons standard calling radio technology, was also used by Sprint. CDMA is being phased out though to be replaced by LTE entirely. I don't know when this will happen. If you check the GSMArena link in the first post you will see all the bands listed on this phone, and it does support CDMA, which is why calling works without VoLTE.
Considering you were having problems on the stock firmware, it seems like your issue is more than just VoLTE not working, because what you explained is not a typical issue, and no matter what stock firmware you were on, VoLTE and CDMA calling both should've worked out of the box. I would test to make sure your Verizon account even has VoLTE support first because that seems to be the only reason for error messages popping up like you had. Although this doesn't really matter though because this method does not support VoLTE from what I tested.
Click to expand...
Click to collapse
Well I will do more testing here shortly. I noticed that on lineage 18.x (Android 11) I get a missing Sim card error when a Sim card is present. Then with latest lineage 19, I get no sim error except the calling authentication error. I have Verizon firmware with the modem now so I'll try testing lineage again with the Verizon modem to see how it plays out.
UPDATE: i tried both lineage 18.x and 19 that have android 11 and 12 in them. still have the same result of phone not able to be authenticated even after flashing verizon modem. ive even tried other gsi roms and ether ended in a bootloop or an error saying petition was too small. it seems that the apn for verizon becomes greyed out and changes the apn settings itself from the sim card. ive even tried using the latest stock update with the gsi and same results. (had to pay a site for the firmware since the newest update is exclusive?) at this point, ive decided using a gsi on this phone with verizon service a bust. so ive decided to stick with stock with root and magisk.
on a side note, i noticed the newer updates have provisioning apps installed on the stock firmware for carriers. not sure if that makes much of a difference but im done messing with it.
First of all thanks Knuxyl for your guide, it helped me to install a GSI ROM n my Edge+, I found really good images but in the end all the images I tried had the same issue... "bluetooth devices connects but transfer no audio", I dont think this is a ROM issue, because I tested 6 android 10 custom ROMS and 3 android 11 with the same result, so I wonder if you dont have this same issue or you manage to solve it.
Im using crdroid v313+211013 and BT wont connect to anything unless I disable A2DP hardware offload inside developer options, with this option enable, the phone pairs with devices but transfer no sound also most of audio codecs are not selctable, they are disabled (grau color), if I enable gabeldorsche stack, the phone is unable to pair with devices. Please if anyone have this issue or suggestion let me know. Have a great day.
@Knuxyl - Thanks for putting this guide together.
@ifritknight - Indeed, I also couldn't get bluetooth to work. I got bootloop with Havoc and LOS 19. LOS 18 worked well.
hi , thank you , there are upgrade?
Well this platform isn't widely supported. I wrote the guide just to get us a foot in the door. The problems with VoLTE, sim, and Bluetooth are more than likely an improper implementation of the new oem partition stuff Google started enforcing, which started with Project Treble.
I did request the source for the kernel for global retail and verizon variants like a year ago. They finally released them within the past month on their github, so maybe a lineage developer could take a peek and possibly officially support this phone. This phone is too good to not support, but the display over usb c would take some effort.
Here are the links
Verizon
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2
github.com
Retail
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11
github.com
Hello friends, I use the device and it does not show me VOLTE, I solved it with the magisk module, it activates the buttons to activate the service and then I select the company profile using the PDC program (it is the same as the volte and vowifi activation of the oneplus 6)
The problem I have is that the change is not permanent, when I restart the cell phone the unwanted profile returns without VOLTE.
Delete the Oversea-Commercial_DS profile but even after reboot the changes are not permanent.
What can you recommend me to solve the problem of activating VOLTE in unsupported countries (which do not have a factory profile)
I clarify to activate I followed the tutorial here
[Guide] VoLTE + VoWiFi working for German carriers
[UPDATE] Updated QPST version + new how to Exciting news, jamal2367 from https://jamal2367.com has developed a way to get VoLTE + VoWifi working for many countries + carriers. If you are on Vodafone and you are having problems with...
forum.xda-developers.com
I have the exact same issue , it reverts back after reboot
I have a nord n10 that i got from tmobile that has unlocked bootloader and is running android 13 gsi the evolutionx version. No matter what gsi I flash it only has an option between 3g and lte, but lte does not work. It shows that its currently on tmobile edge where only messages and calling works. Anyone know a fix to make the lte work?
Did you try that: go into Settings, Phh Treble Settings, IMS features,Install IMS APK for Qualcomm vendor, Reboot the device, Go back to IMS features and request IMS network, and Create IMS APN.
what do I do once I create ims apn.
SupreethChinta06 said:
what do I do once I create ims apn.
Click to expand...
Click to collapse
Go Internet settings/operator settings and enable VoLTE.