Develop Bugs

Tethering not working , Global Rom 9.5.6.0

I have the Xiaomi Redmi Note 5 Global Version, ROM oreo 8.1.0, Global ROM 9.5.6.0
Tethering (4G hotspot) does not work.
Does anyone else have this problem??
{
"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"
}

What do you mean by doesn"t work ? You can turn it on, but there is no internet access or it won't turn on at all, or what ?
Sent from my WHYRED global

4G works but cannot be shared with the hotspot.
Hot spot turns on. You can connect another mobile phone to the hotspot by wifi but no internet connection.

Just did a speed test on Nexus 7 2013 connected to my Redmi Note 5 global (WI-FI_by_MikiGry). Everything seems fine...
http://cloud.tapatalk.com/s/5b01fcef1f6d1/1526856485498.jpg?
http://cloud.tapatalk.com/s/5b01fce...-05-21-00-45-21-694_com.android.settings.png?
http://cloud.tapatalk.com/s/5b01fd2...-05-18-23-02-23-504_com.android.settings.png?
Sorry for posting pics like that. Tapatalk doesn't want to post the normally for some reason :/
Sent from my WHYRED global

MikiGry said:
Just did a speed test on Nexus 7 2013 connected to my Redmi Note 5 global (WI-FI_by_MikiGry). Everything seems fine...
http://cloud.tapatalk.com/s/5b01fcef1f6d1/1526856485498.jpg?
http://cloud.tapatalk.com/s/5b01fce...-05-21-00-45-21-694_com.android.settings.png?
http://cloud.tapatalk.com/s/5b01fd2...-05-18-23-02-23-504_com.android.settings.png?
Sorry for posting pics like that. Tapatalk doesn't want to post the normally for some reason :/
Sent from my WHYRED global
Click to expand...
Click to collapse
Yes, everything the same as mine, very strange.
Maybe some setting that I need to change.....

I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"

Thanks a lot
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks to your method, I solved this issue.
My setting is also null.

Same issue after checking.
Hope they release a patch for it, don't fancy mucking about doing ADB stuff but will if I have to

meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks for your suggestions, I changed the settings as indicated and did the ADB and changed the value to "0" (it was "null").
But still no luck, tethering (hot spot) still not working.

Maybe if I flash a different ROM ? (EU weekly or RR?)

Hi,
Me too, tethering doesn't share Internet connection, but only when SIM is in slot 1.
If a put the SIM card in slot 2, everything works fine.
However, if I use another carrier SIM card in slot 1, tethering works as expected...

Tried both sim slots with one sim, then 2 sims, no joy.... No tethering... wifi connects but no internet...

meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
settings put global tether_dun_required 0
"
Click to expand...
Click to collapse
So I follwed the steps but when I try to execute the upper command to set this parameter I get an Android "android.permission.WRITE_SECURE_SETTINGS" denied error.... I enabled USB debugging and I´m successfully connected to the WHYRED device via ADB.
Any tips to solve this?

I also used the commande "settings put global tether_dun_required 0" and hotspot is now working as expected.
Envoyé de mon Redmi Note 5 en utilisant Tapatalk

Kusie said:
So I follwed the steps but when I try to execute the upper command to set this parameter I get an Android "android.permission.WRITE_SECURE_SETTINGS" denied error.... I enabled USB debugging and I´m successfully connected to the WHYRED device via ADB.
Any tips to solve this?
Click to expand...
Click to collapse
You need to also enable "USB Debugging (Security settings)" in additional to just "USB debugging". It is located in Developer options next to "install via USB" toggle.
To enable it you must be logged into your Mi account. You can log out later, and the setting will keep its value. While you're there you might also consider enabling "installing apps over USB" which also requires you to be logged in.
And yes, the fix indeed works.

Thank you, will try and hope it works.

meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse
Thanks a lot! I just register here to thank you!!! Worked in Xiaomi Redmi Note 5 Global Version 4GB 64GB

Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:
meroupow said:
I had the same issue and changed a setting (tether_dun_required to 0) using ADB. Now it is working as it should have.
Got that from another forum:
"
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
"
Click to expand...
Click to collapse

tamilselvan9j said:
Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:[/QUOTE
I was wondering who could help me to enable tethering, someone mentioned ADB, can i have the link for that please
The mi suit doen't work neither wondershare tunes go
Click to expand...
Click to collapse

maksant said:
tamilselvan9j said:
Awesome bro.. Thank you so much really.. Was frustrated because of this issue.. Your help indeed solved the issue. Greatly appreciated.. :fingers-crossed::fingers-crossed::fingers-crossed:[/QUOTE
I was wondering who could help me to enable tethering, someone mentioned ADB, can i have the link for that please
The mi suit doen't work neither wondershare tunes go
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-hotspot-connecting-fix-t3796847
Click to expand...
Click to collapse

WiFi hotspot Sprint version

So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!

mariomtes said:
So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!
Click to expand...
Click to collapse
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?

Toni_RM said:
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?
Click to expand...
Click to collapse
Tried that. I get an error that says I can't edit that table

mariomtes said:
Tried that. I get an error that says I can't edit that table
Click to expand...
Click to collapse
Oh my bad i left out the most important part.
1. Install adb on your laptop (search it up)
2.On your phone go to settings, general, about phone, software info, find build number section and keep tapping until you are a developer
3. Go back to general and you'll now see developer options, turn developer options on and go down to usb debugging and turn it on.
4. Connect your phone to your laptop via USB (you will get a promt on your phone along the lines of "allow USB debugging?", click ok) and open up command terminal
5. Type "adb" and press enter
6. Type the command (without quotes) "adb devices". Your device should show up.
7. Type "adb shell" and press enter
8. Open up the settings database editor and go to global and scroll down to tether_dun_required. Click "edit value" and the shell command should pop up.
Type the shell command into adb shell and press enter
9. Go to the settings data base editor and go back to the tether_dun_required and click on change value. You'll notice that you are now able to change the value, change it to 0.
10. Enjoy your hotspot!
It seems like a lot of steps but it's not. The most "difficult" task will be installing adb.

Awesome. Got it to work now. Do you have to set it to 1 for the Ota updates or after each reset? Thanks again!

No, theres no need to set it back to "1". After you shut off your phone the setting value will turn back to a "1" and you hotspot wont work until you switch it back to "0". To save time you can buy the feature pack and you'll get access to settings guardian which will keep it at "0" at all times.

Unlocked AT&T e980 - Lost WiFi tethering with transfer to Mint Mobile - 4G LTE works

Unlocked AT&T e980 - Lost WiFi tethering with transfer to Mint Mobile - 4G LTE works
I thought members here might know if this solution I found for phones using KitKat might be my issue. Setting up the APN for Mint is trivial and know to be correct. Why no WiFi tethering for pc? Here is what I found but I do not want to implement this w/o gaining more confidence this will work...no desire to kill the phone. Mint tells me they do not block tethering. The e980 only offers WiFi and Bluetooth tethering. I do not see an option for USB tethering unless it is located in a unique place.
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
Any ideas?
Edit - Bluetooth tethering does not work either. I can connect a pc and the e980 via Bluetooth but enabling BT tethering on the e980 gives the same fault message.

RVC46 said:
I thought members here might know if this solution I found for phones using KitKat might be my issue. Setting up the APN for Mint is trivial and know to be correct. Why no WiFi tethering for pc? Here is what I found but I do not want to implement this w/o gaining more confidence this will work...no desire to kill the phone. Mint tells me they do not block tethering. The e980 only offers WiFi and Bluetooth tethering. I do not see an option for USB tethering unless it is located in a unique place.
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
Any ideas?
Edit - Bluetooth tethering does not work either. I can connect a pc and the e980 via Bluetooth but enabling BT tethering on the e980 gives the same fault message.
Click to expand...
Click to collapse
I think this is what you need to do? https://forum.xda-developers.com/showthread.php?t=2283615
Btw are you still using your LG att e980? Mine has sat in a drawer for 3 years since the screen stopped working. Not sure if it's rom or screen digitizer related? I bought it in 2014 I think & used it will March 2018 when I bought my T-mobile LG V20 & V30 phones. I'm trying to decide to fix it or toss it?

How To Guide [GUIDE] How to fix Quick Unlock bug on Android 12 (constant vibrate at lock screen, impossible to log in)

PROBLEM:​Under certain scenarios, enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
If your phone is in this state, here's three possible fixes:
Spoiler: Possible Solution #1
POSSIBLE SOLUTION #1:​
Thanks to Caligastia's post, here's another option to resolve.... (quoting from his post)[/B]
Just use the adb command...
Code:
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Spoiler: Possible Solution #2
POSSIBLE SOLUTION #2:​
Revert to settings_system.xml.fallback file. Do not follow this guide UNLESS your phone is in this vibrate over and over / impossible to login state.
Note: This only works if you have USB debugging enabled on your computer with root enabled. This will not work if you haven't performed adb shell as root before ( com.android.shell ). Doesn't hurt to try!
Boot up phone to system/normal mode.
Type the following in command prompt:
Code:
adb shell
su
ls /data/system/users/0/settings_system.xml
If it says:
Code:
/data/system/users/0/settings_system.xml
Then this fix should work! Otherwise, this probably won't work.
Finally, type...
Code:
mv /data/system/users/0/settings_system.xml /data/system/users/0/settings_system.xml.old
cp /data/system/users/0/settings_system.xml.fallback /data/system/users/0/settings_system.xml
reboot
Your phone will reboot and the issue should be fixed!
By applying this method you may lose a few recently changed system settings, but nothing major.
Spoiler: Possible Solution #3
POSSIBLE SOLUTION #3:​
Go to bootloader/fastboot mode on your phone.
Type
Code:
fastboot --set-active=a
fastboot reboot
if it doesn't boot right still, go back to bootloader/fastboot and type
Code:
fastboot --set-active=b
fastboot reboot

There are no settings on the 9Pro A12 called quick unlock. What are you referring to?

I'm referring to the setting called Quick Unlock.
Password and Security > Lock Screen Password.

But what this option do ? ( Quick unlock )

asheroto said:
PROBLEM:​Enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
DO NOT ENABLE QUICK UNLOCK!
Click to expand...
Click to collapse
On my LE2123 OnePlus 9 Pro I do not face this issue with quick unlock. I made a test now once and no issue. Just FYI. I an not rooted.

K1nsey6 said:
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
Click to expand...
Click to collapse
This option appears if you select Alphanumeric password, using the regular keyboard instead of number pad. Quick unlock will unlock your phone immediately once you enter the password without having to press the enter key.

Interesting, I have the LE2125 with alphanumeric enabled.
I edited the original post to say "Under certain scenarios".

I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?

blxyy said:
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
Unfortunately you have to allow the host (your computer), but you can't do that unless you can tap on the popup.
Can you get in with TWRP or anything else? If so you could edit the file that way. Otherwise, try booting to the other slot.
How to check the current slot:
How to Check if You're on Partition Slot A or Slot B? - KrispiTech
Android phones can now have an A and a B partition system for the OS and we can use this fastboot command to check and see which slot is currently active.
krispitech.com
How to change the active slot:
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com

I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
@bixyy
Just saw this, hope i'm not too late to help.
If adb shows "unauthorized" it just means that usb debugging permission was revoked between your phone and computer. here's what to do: (assuming you're on windows)
-Unplug your phone from pc. Disable Usb debugging and turn off "disable timeout"
-on your pc, go to C:/users/<username>/.android (it's a hidden folder) and delete adbkey.
-reboot both phone and pc to make sure it takes effect.
-plug your phone again, turn on usb debugging and you should get a new prompt to allow authorization.
adb devices should return your serial number now.

Added possible alternate solution

I ran into the same issue, OP was very helpful.
A bit more info here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password

Caligastia said:
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Thanks for that man! I updated the original post to include your solution and linked to your post for credits!

I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.

_147 said:
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
Click to expand...
Click to collapse
can you help me i cant seem to get adb to recognize my phone

Hi,
Is there any possible solution for us who don't have USB-Debugging enabled?
The goal is to not have to wipe the whole phone and loose all data.
Possible solution #1 fails: Wont work because USB debugging is disabled which prevents us from getting adb-shell and run the "
locksettings clear --old [PASSWORD]" command. When trying to figure out how to enable USB debugging from remote it seems to require some fastboot option which would wipe the phone.
Possible solution #2: Same - requires shell, and we cant enable usb debugging because of the bug
Possible solution #3: I can access fastboot but not run the specific commands:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
fastboot --set-active=a
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Unlocking boot to install TWRP and enable debugging to use ADB shell would wipe the phone as I understand it.
Any suggestions please?

Is your phone locked when you're doing that?

asheroto said:
Is your phone locked when you're doing that?
Click to expand...
Click to collapse
Developer options enabled
OEM bootloader unlock enabled
USB debugging enabled
Default USB Configuration file transfer
Non-TMO variant = boot to bootloader, then fastboot OEM unlock...wipes device. No other way. Unlock bootloader will wipe device period.

How To Guide Enable VoLTE and VoWifi on OOS 13 without root

Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet. (Edit 27/06/2023: new updated apk available here)
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings

Not works for me... I have the italian operator PosteMobile

Doesn't work for me... I tried to use a custom ROM so I could have VoWiFi, but I felt something was off. I got back to OOS13 on my OnePlus 8 Pro (IN2023) with AT&T and tried this method but no success...

omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh. You should see somewhat like "Shizuku is running" at your phone.
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Thank you! It worked on a LE2121 with Android 13!

Update:
I just updated to 13.1 and lost VoLTE. Re-did the steps and got it back.

Added an edit to step 5 in OP, as with 13.1 I had to uncheck "Disable permission monitoring" in developer settings).

It's not work. Oneplus 10 pro. Oxygen os 13.1

yasador said:
It's not work. Oneplus 10 pro. Oxygen os 13.1
Click to expand...
Click to collapse
Need to be more specific.....

Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please

momiloco said:
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
Click to expand...
Click to collapse
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.

omar302 said:
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
Click to expand...
Click to collapse
Thanks bro.
I tried like what you suggested but still the same error.
Managed to do it using wireless USB debugging. Much easier.
Thanks

omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?

kmahesh said:
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
Click to expand...
Click to collapse
I think you missed reading the first paragraph. It worked for me on my OnePlus 9 Pro on OOS 13 & 13.1. I am using a Tello (US) line which is basically T-Mobile and got VoWifi to work using these steps.

Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP

kmahesh said:
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
Click to expand...
Click to collapse
It seems that it doesn't work for all SIM cards. I also tried the same with a 1+ 7 Pro using another SIM and it did not work. Maybe I'll try with the Tello SIM on the 7 Pro just to test if it's an issue with the phone or SIM.

Thanks Omar for trying. All I am trying to find out (1) Is my phone the culprit (or) my T-Mobile is the culprit (2) Is there a solution (with or without rooting) to make this work for USA carriers?
Any help would be appreciated.
Thanks
Mahesh

Hello everybody. I have Oneplus 9R OOS 13.0 Android 13. I did everything according to the instructions using wifi debugging. The volte switch slider has become active. However, when making a call, the phone still falls into the H+, H or 3G network. I have 2 SIM cards installed, before starting the algorithm, I did not deactivate the second one. Could this be a problem? If so, what would you recommend to do in this case?
I tested SIM card 1 used for calls and the Internet in another device, Volte works on it.

Updated to LE2123_13.1.0.580(EX01) and off course lost VoWifi, however, repeating the steps re-enabled it.
Also found an updated Pixel IMS apk (link to download) that has more options when enabling VoLTE or VoWifi.