PIE vibrate on connected call app - Google Pixel 2 XL Questions & Answers

Does anybody has working application for "vibrate on connected call" on Android Pie?
In Oreo I used VibCall but on Pie ot doesn't work. I tried a couple different apps but no one works.

https://play.google.com/store/apps/details?id=com.robin.huangwei.vibrate250&hl=en
This works if you follow the instructions and grant the permission via adb shell

badchip said:
https://play.google.com/store/apps/details?id=com.robin.huangwei.vibrate250&hl=en
This works if you follow the instructions and grant the permission via adb shell
Click to expand...
Click to collapse
Testen on Google Pixel 2 - Android Pie - grant the permission via adb shell, restart, but not working

Is there another app? or another option to do that?

I use "call vibrator - no root" and it's work.
But, it do about 1s pause after call is answered. Samsung has build in function and it do not do any pause

Related

Add notifications to Shield

Must have your Shield rooted
apps needed installed
-AppOps
-Settings Editor
-Snowball
-Heads Up Notifications
-terminal emulator
Install the 5 above apps.
Grant settings editor WRITE_SECURE_SETTINGS permission in terminal
-su
-pm Grant by4a.setedit22 android/.permission WRITE_SECURE_SETTINGS
Add Snowball and Heads Up listeners to active listeners
-go to secure table in Settings Editor
-choose "enabled_notification_listeners" and choose editor value
-replace all text with "com.snowball.app/.nsprocess.NotificationService:codes.simen.l50notifications/.NotificationListenerService"
Grant draw over apps permission to snowball and Heads Up in AppOps
-for each app change "this app can appear over top of other apps" to allow
Now open Heads up and snowball and run through the setups.
You should now get notifications.
I've been wanting this for Soo long and now I have no pc to root ??
Slayerkodi said:
I've been wanting this for Soo long and now I have no pc to root
Click to expand...
Click to collapse
I just did it without root, just needed to not use appops.
so you need
-settings editor
-terminal emulator
-heads up
install settings editor and terminal editor
open terminal and put in"pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS"
install heads up
-go to secure table in Settings Editor
-choose "enabled_notification_listeners" and choose editor value
-replace all text with "codes.simen.l50notifications/.NotificationListenerService"
open terminal and put in "pm grant codes.simen.l50notifications android.permission.SYSTEM_ALERT_WINDOW"
let me know how that works
Quick question before I try this, is there a way to turn off notifications? Like say I don't want notifications from specific apps - how do I stop this if there is no way to turn off notifications from within the app??
Tbh I only want notifications coming from one app only if poss
Slayerkodi said:
Quick question before I try this, is there a way to turn off notifications? Like say I don't want notifications from specific apps - how do I stop this if there is no way to turn off notifications from within the app??
Tbh I only want notifications coming from one app only if poss
Click to expand...
Click to collapse
just turn off the notification toggle in settings apps for the app you want notifications disabled.
Settings editor is a Xposed module - Xposed requires root! So no go unfortunately
Slayerkodi said:
Settings editor is a Xposed module - Xposed requires root! So no go unfortunately
Click to expand...
Click to collapse
It's in the shields play store
Slayerkodi said:
Settings editor is a Xposed module - Xposed requires root! So no go unfortunately
Click to expand...
Click to collapse
It's in the shields play store
Ok so I just attempted this and it seems to fail at the first step https://m.imgur.com/a/vOLLfRc
Slayerkodi said:
Ok so I just attempted this and it seems to fail at the first step https://m.imgur.com/a/vOLLfRc
Click to expand...
Click to collapse
Try turning on USB debugging
Wildheart said:
Try turning on USB debugging
Click to expand...
Click to collapse
USB debugging is on already
Slayerkodi said:
USB debugging is on already
Click to expand...
Click to collapse
Next thing I would get you to do that is to say the command.
What do you mean?
Wildheart said:
Try turning on USB debugging
Click to expand...
Click to collapse
Wildheart said:
Next thing I would get you to do that is to say the command.
Click to expand...
Click to collapse
USB debugging is already in, what do you mean by say the command?
Wildheart are you there?
Would love to have had this to work
Can anyone else help with this?
can you adb into your shield?
No pc or root, I have been using termux recently to upload music to Google play music as there's no way to do this with Android atm, which is working fine. I tried your code again the other day using termux, seems like your code you asked me to enter needed a few spaces in places for it to recognize the command but I still got an error, I'll upload a screenshot later on when I'm at home
Try using "ADB Shellkit" to enter the commands, I've tried it and you need at least ADB access to follow this walkthrough without root.

Alternative Keyboard / Language Firestick 4k

I checked the forums and couldn't find that this was answered. I got a Firestick 4k and want to change the on screen keyboard / language to something other than supported languages (yes I see where you can go in settings to change).
I sideloaded a keyboard app that I use on other android devices but it doesn't seem to do anything with the firestick and and an external keyboard - it's not bringing up the custom keyboard app.
Any suggestions?
smeagolheart said:
I checked the forums and couldn't find that this was answered. I got a Firestick 4k and want to change the on screen keyboard / language to something other than supported languages (yes I see where you can go in settings to change).
I sideloaded a keyboard app that I use on other android devices but it doesn't seem to do anything with the firestick and and an external keyboard - it's not bringing up the custom keyboard app.
Any suggestions?
Click to expand...
Click to collapse
there are 2 options:
1st you need to activate and set new KeyBoard via adb:
Code:
ime list
Here is the example list of installed keyboards, look at 1st line with keyboard ID:
mantis:/ $ ime list
com.amazon.tv.ime/.FireTVIME:
mId=com.amazon.tv.ime/.FireTVIME mSettingsActivityName=null mSupportsSwitchingToNextInputMethod=true
mIsDefaultResId=0x0
Service:
...
org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService:
mId=org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService mSettingsActivityName=null mSupportsSwitchingToNextInputMethod=false
mIsDefaultResId=0x0
Service:
...
Click to expand...
Click to collapse
next enable desired one and set it default:
Code:
ime enable org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
Code:
ime set org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
thats it.
2nd option is install Buttons Remapper apk and define there any key press to show Choose Keyboard dialogue. You'll can switch between keyboards from UI.
I have installed the LeanKey Keyboard_v4.3.39 on my 4k Firststick and tried to open it (in case something had to be started for this process to work)
If i type in
"ime list"
That only lists the default keyboard for me.
If i type in:
ime enable org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
i get the error "Unknown ID com.amazon.tv.ime/.FireTVIME
have you tested this yourself on a 4K firestick?
Intenti0n said:
have you tested this yourself on a 4K firestick?
Click to expand...
Click to collapse
Yes, I used both on FireTV 4K before, but "ime" part was tested on previous OS release (probably 6.2.6.3).
There is still option to enable it without root by writing secure settings, you can use companion app for it: FireTVjack.
You must grant this app permission to write secure settings via adb:
Code:
adb shell
pm grant com.amazon.fireh1jack android.permission.WRITE_SECURE_SETTINGS
pm grant com.amazon.fireh1jack android.permission.CHANGE_CONFIGURATION
pm grant com.amazon.fireh1jack android.permission.SYSTEM_ALERT_WINDOW
and reboot. It will activate LeanKey Keyboard on boot. It also have language switch for RU/UK/DE/EN language.
tsynik said:
there are 2 options:
1st you need to activate and set new KeyBoard via adb:
Code:
ime list
Here is the example list of installed keyboards, look at 1st line with keyboard ID:
next enable desired one and set it default:
Code:
ime enable org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
Code:
ime set org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
thats it.
2nd option is install Buttons Remapper apk and define there any key press to show Choose Keyboard dialogue. You'll can switch between keyboards from UI.
Click to expand...
Click to collapse
tsynik said:
Yes, I used both on FireTV 4K before, but "ime" part was tested on previous OS release (probably 6.2.6.3).
There is still option to enable it without root by writing secure settings, you can use companion app for it: FireTVjack.
You must grant this app permission to write secure settings via adb:
Code:
adb shell
pm grant com.amazon.fireh1jack android.permission.WRITE_SECURE_SETTINGS
pm grant com.amazon.fireh1jack android.permission.CHANGE_CONFIGURATION
pm grant com.amazon.fireh1jack android.permission.SYSTEM_ALERT_WINDOW
and reboot. It will activate LeanKey Keyboard on boot. It also have language switch for RU/UK/DE/EN language.
Click to expand...
Click to collapse
Thanks and this works on a default 4K firestick without any unlocking / rooting?
I only ask as I can see you mention fireh1jack in another thread that is for firesticks with an unlocked bootloader.
Intenti0n said:
Thanks and this works on a default 4K firestick without any unlocking / rooting?
Click to expand...
Click to collapse
Yes, this tool works on stock unrooted firesticks also. But you need to grant needed permissions to it via adb.
We don't need FireTVjack on rooted devices at all
tsynik said:
Yes, this tool works on stock unrooted firesticks also. But you need to grant needed permissions to it via adb.
We don't need FireTVjack on rooted devices at all
Click to expand...
Click to collapse
I just tried this on a clean 4k firestick.
Installed FireTVJack
connected via ADB and ran these 3 commands:
pm grant com.amazon.fireh1jack android.permission.WRITE_SECURE_SETTINGS
pm grant com.amazon.fireh1jack android.permission.CHANGE_CONFIGURATION
pm grant com.amazon.fireh1jack android.permission.SYSTEM_ALERT_WINDOW
all commands accepted without error.
If i start the FireTVJack app, it asks me to select a launcher.
If I reboot the device, the default keyboard doesn't change.
If i click on the LeanKeyboard Pro - nothing happens.
have i missed a step?
thanks
Intenti0n said:
If I reboot the device, the default keyboard doesn't change.
Click to expand...
Click to collapse
Strange.
Intenti0n said:
If i click on the LeanKeyboard Pro - nothing happens.
Click to expand...
Click to collapse
That's expected behaviour - that shortcut for Keyboard settings activity which doesn't exist on FireTV
Intenti0n said:
have i missed a step?
thanks
Click to expand...
Click to collapse
Nope. Only thing needed to add/switch keyboard is to write its component to secure settings. On unrooted FireTV, user can't write those settings, but programs with granted WRITE_SECURE_SETTINGS perms can. In h1jack there is OnBootComplete receiver which looks for exact packages and add them to settings if exist.
Code:
("org.liskovsoft.leankeykeyboard.pro", "com.google.leanback.ime.LeanbackImeService");
("com.example.semitop7.FireTVStyle", ".FireTVStyleIME");
It worked on unrooted 6.2.6.5 without issues. Why it doesn't work for you on 6.2.6.6? I don't know, and can't test because my 4K rooted and LeanKeyKeyboard Pro works fine. Does your version match (it must have id - org.liskovsoft.leankeykeyboard.pro and 4.3.30 version)?
P.S. What output you have with that command on adb:
Code:
settings list secure|grep input
tsynik said:
Strange.
That's expected behaviour - that shortcut for Keyboard settings activity which doesn't exist on FireTV
Nope. Only thing needed to add/switch keyboard is to write its component to secure settings. On unrooted FireTV, user can't write those settings, but programs with granted WRITE_SECURE_SETTINGS perms can. In h1jack there is OnBootComplete receiver which looks for exact packages and add them to settings if exist.
Code:
("org.liskovsoft.leankeykeyboard.pro", "com.google.leanback.ime.LeanbackImeService");
("com.example.semitop7.FireTVStyle", ".FireTVStyleIME");
It worked on unrooted 6.2.6.5 without issues. Why it doesn't work for you on 6.2.6.6? I don't know, and can't test because my 4K rooted and LeanKeyKeyboard Pro works fine. Does your version match (it must have id - org.liskovsoft.leankeykeyboard.pro and 4.3.30 version)?
P.S. What output you have with that command on adb:
Code:
settings list secure|grep input
Click to expand...
Click to collapse
I am on 6.2.6.8 FireOS.
I noticed you mentioned leankeyboard 4.3.30. I was running 4.3.29.
I removed that and installed 4.3.30, rebooted and now when I run the command
settings list secure|grep input
I get:
default_input_method=org.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
enabled_input_methods=com.amazon.tv.ime/.FireTVIMErg.liskovsoft.leankeykeyboard.pro/com.google.leanback.ime.LeanbackImeService
input_methods_subtype_history=com.amazon.tv.ime/.FireTVIME;1802354156
selected_input_method_subtype=-1
Many thanks for your time!.
I really was hoping for a voice input key with this custom keyboard, so I could use my voice to input text in 3rd party apps. Would there be any possibility of that?
Intenti0n said:
I really was hoping for a voice input key with this custom keyboard, so I could use my voice to input text in 3rd party apps. Would there be any possibility of that?
Click to expand...
Click to collapse
You can try different keyboards with voice options, but probably most of them rely on Google Search itself. Even with Google Search installed I can switch to it with keyboard chooser, but voice input doesn't work for that apk version. Maybe others will work somehow.
tsynik said:
You can try different keyboards with voice options, but probably most of them rely on Google Search itself. Even with Google Search installed I can switch to it with keyboard chooser, but voice input doesn't work for that apk version. Maybe others will work somehow.
Click to expand...
Click to collapse
even if I install another keyboard apk....
How will I give that permission ? as you said the FireTVjack has " OnBootComplete receiver which looks for exact packages" . - but that wont contain the custom package name for a random keyboard apk that I would try ?
Intenti0n said:
even if I install another keyboard apk....
How will I give that permission ? as you said the FireTVjack has " OnBootComplete receiver which looks for exact packages" . - but that wont contain the custom package name for a random keyboard apk that I would try ?
Click to expand...
Click to collapse
You can install apk which can edit settings (Settings Database Editor for example), grant needed permission to it and use it's UI to edit settings db directly.
I cannot get to LeanKey Keyboard to appear on IME list.
Fire TV Stick 4k, FireOS 6.2.6.8.
FireTVJack installed, all permissions granted,rebooted many times
Installed LeanKey 4.3.30 and 4.3.39
Any thoughts?
crzsotona said:
I cannot get to LeanKey Keyboard to appear on IME list.
Fire TV Stick 4k, FireOS 6.2.6.8.
FireTVJack installed, all permissions granted,rebooted many times
Installed LeanKey 4.3.30 and 4.3.39
Any thoughts?
Click to expand...
Click to collapse
Try this release: https://github.com/yuliskov/LeanKeyKeyboard/releases
Also, which fireh1jack version do you have? (one which enables leankey keyboard on boot must have com.amazon.fireh1jack package id)
org.liskovsoft.androidtv.rukeyboard/com.liskovsoft.leankeyboard.keyboard.leanback.ime.LeanbackImeService
This is leankey package name on my Fire Stick I was successful in activating on my stick.

NO ROOT/Enable Native Call Recording/Working Even After REBOOT

I have OnePlus 7T Pro with STOCK 10.0.4.HD01AA Global version NOT ROOTED!!!
How to enable Native Call Recording,that WILL working even REBOOT:
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time :laugh:
11.100% TESTED AND FULLY WORKING!!!
Confirm, it works. Activated after restart. Good quality recordings. Thanks.
Sadly the google drive file doenst exist anymore on the server ?
Please fix.
Thanks!
zat0x said:
Sadly the google drive file doenst exist anymore on the server ?
Please fix.
Click to expand...
Click to collapse
Done.
Worked also for me... Thanks !
Hi. tried on 7T also and it work. Vers. 10.0.6 HD65AA model HD1900
fail
(('adb' is not recognized as an internal or external command,
operable program or batch file.))
please help !!
Works on my OnePlus 7T PRO HD 1910 , Oxygen OS 10.0.4.HD01AA. Thanks and keep up the good work !
Do you have to utilize the Joneplus app? Or is there a way to manually enable?
Just follow the instructions carefully.
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/d....joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/att...7&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time
11.100% TESTED AND FULLY WORKING!!!
ivo777 said:
I have OnePlus 7T Pro with STOCK 10.0.4.HD01AA Global version NOT ROOTED!!!
How to enable Native Call Recording,that WILL working even REBOOT:
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time :laugh:
11.100% TESTED AND FULLY WORKING!!!
Click to expand...
Click to collapse
Made on OnePlus 7T Pro Maclaren and working.
Thank you.
many thanks, it works in my 7T 1900
AFTER REBOOT - JUST TURN ON call recording IN JONEPLUS APP
All,
It works fine on HD1913
Thanks
All works as it should
HD1913
Sent from my OnePlus 7T Pro using Tapatalk
Great work,thanksssss
Sent from my HD1913 using Tapatalk
Do not survive a reboot I'm afraid. Needs to be toggled manually on each boot. [OxygenOS 10.0.5.HD01AA]
tal_sarid said:
Do not survive a reboot I'm afraid. Needs to be toggled manually on each boot. [OxygenOS 10.0.5.HD01AA]
Click to expand...
Click to collapse
Not in my case, it automatically starts after booting and unlocking the phone.
Oxygen 10.0.5.HD01BA
without Joneplus app and if youf dont reboot
adb shell settings put global op_voice_recording_supported_by_mcc 1
Click to expand...
Click to collapse
Does the phone update later without any problems after applying this guide?
OTA updated already 3 times with joneplus installed without problems.

Realme X2 & Tasker

Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
bino_mat said:
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
Click to expand...
Click to collapse
Tasker is running fine on my X2 EU version. No problems up to now
Note4Addict said:
Tasker is running fine on my X2 EU version. No problems up to now
Click to expand...
Click to collapse
That is is interesting !! - 2 problems I encountered are
1.Tasker toasts are working only with in Tasker context - I mean if open the tasker and a do a flash message ,it flashes the message- But when on a normal working (Tasker is in background) - no toast message appears.
2.Even if I enable all of the permission,when Tasker tries to switch on the WIfi with in Tasker context as window popes out asking Tasker want to switch on Wifi - Allow or Prohibit -
If Tasker is in background,this window can't appear and nothing happens.
Finally ,I went to Developer options,Disabled the permission monitoring(last option) s- that this started working
Can you please confirm on these 2 points?
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Note4Addict said:
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Click to expand...
Click to collapse
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
bino_mat said:
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
Click to expand...
Click to collapse
Good news that Tasker works well in Color OS 7 which will get around March it seems. Regarding the initial ADB permission, I meant the message you get when you first install Tasker on a non-rooted device. In that case you need to execute a specific permission command via ADB to get Tasker up and running correctly.
What I meant with "Try if you can..." is that If you have the opportunity you may want to check if perhaps one of the new ADB wifi commands would be capable of setting wifi on and off despite permission monitor being active instead of disabled as we're doing now. Hope that will work so we can keep permission monitor active.
Guess ,it is more of Color OS issue , with the battery saved enabled,Tasker is missing the Alarm - I did a simple experiment of logging of BAttery level to a file in every 10 minutes.
If I look at the file now ,either the logging is not continuous or stopped after sleeping for one or hour or so !!! -- But this is not the case with MIUI - It's sharp on time with battery saver or not.
More importantly one thing I noticed is that when battery saver is on ,you can't lock the application in memory - Flip side , with battery saver on ,if I invoke recents and clear the memory ,evrything will be wiped and even when battery saver is off,the applications which you want to be in memory in normal condition will not be there!!!
Bluetooth problems with Android 10:
With my Realme X2 and Realme Ui 1.0 (Android 10) i can not start Bluetooth because my smartphone always asks with an popup for an permission ("Tasker needs the following permission: set Bluetooth on/off"). My desktop links give me the error code "action bluetooth failed".
How can i disable this popup asking for an permission? Or can i made tasker to click on yes itself?

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.

Categories

Resources