One handed mode disappeared - Huawei Mate 20 Lite Questions & Answers

One handed mode disappeared - Huawei Mate 20 Lite Questions & Answers

Thread Closed Per OP Request
I used to use one handed mode. However, I recently realized that I was unable to activate it no more. When I check accessibilty settings, I can't see 'one handed' mode while it must be there (see attachement).
Is it also the same for anyone else or only for me?

Can someone please paste the output of
Code:
adb shell pm list packages
on their default system?
I suspect that I might be removed an/some app(s) and would reinstall the associated one to get that option back.
Thanks in advance.

Related

[Plugin] Remote Adb Shell

Hi everyone!
I just created my first Tasker plug-in. This plug-in enables you to send an adb shell command to any other device on the network that has adb over wifi enabled. I for example use it to turn my androidtv on or off by sending it the command "input keyevent POWER". You can also open specific activities in apps for example or simulate touch input.
Please read the description before using it and don't hesitate to leave feedback/bug reports/tips! This is my first app ever published so I still have a lot to learn.
You can download it for free from the play store:
https://play.google.com/store/apps/details?id=com.ADBPlugin
Edit: It's now also available on XDA Labs! You can find it here

First update is live!
This includes proper (cat)logs and Tasker errors if something went wrong, so if you run in any problems, you can now tell me . It also plays a lot nicer with the Tasker timeout system.

@Humpie
Thanks for this plugin. I allready made a project for my sony android tv. Start apps and controll media play.
But to make the plugin better I have some featur requests:
It would be nice to be able to work with tasker variables. e.g input text "%mytext".
Another feature reqest would be to get a output variable for commands with output like adb shell pm list packages.

MartelKombat said:
@Humpie
Thanks for this plugin. I allready made a project for my sony android tv. Start apps and controll media play.
But to make the plugin better I have some featur requests:
It would be nice to be able to work with tasker variables. e.g input text "%mytext".
Another feature reqest would be to get a output variable for commands with output like adb shell pm list packages.
Click to expand...
Click to collapse
Thanks for the tips! Will definitely add variable support and I'll also have a look at output variables. They are visible in the logs already, but not yet to tasker.

Why can't we use the built-in code Acton in Tasker? Is there a difference?

loogielv said:
Why can't we use the built-in code Acton in Tasker? Is there a difference?
Click to expand...
Click to collapse
In fact there is, since android 4.something google removed adb from android devices, so you can't perform adb commands from your phone, well aside from my plugin that is.
There would however be no difference if your remote device did have Tasker and you programmed it so that a certain action does something with code. However, you would have to figure out a way to contact that device etc...

Second update! The Plugin now has Tasker variable support!
(enjoy @MartelKombat btw I'm still thinking about how to implement your other request!)

I doont understand. I can type the code, but i do have to remove the "adb sell" part of the code but it's good to go… is that not what this plugin does?

Humpie said:
Thanks for the tips! Will definitely add variable support and I'll also have a look at output variables. They are visible in the logs already, but not yet to tasker.
Click to expand...
Click to collapse
Humpie said:
Second update! The Plugin now has Tasker variable support!
(enjoy @MartelKombat btw I'm still thinking about how to implement your other request!)
Click to expand...
Click to collapse
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!

How to run root commands on an unrooted device with this plugin
I just wanted to share how I use this plugin, just to give others an example of what this nice plugin is capable of.
Recently, I bought a new device and for now, I have no intention of rooting it. Coming from a rooted OnePlus One, this means some of my Tasker profiles do not work as expected anymore and I have to find workarounds.
On LineageOS (and CyanogenMod before that), we have the option to display left/right cursor arrows in the navigation bar when typing text. I always loved this feature, since placing the cursor in the right position by tapping will always be a hit&miss game. Since my new device (S7 Edge) has no onscreen navigation bar, I was searching for a replacement solution to move the cursor. I came up with the idea that it would be quite handy to use the volume buttons for this. So, the idea was the following:
IF the keyboard is shown THEN use the volume keys to move the cursor (and suppress any volume changes, if possible).
It took me a while to figure out how to determine whether the keyboard is out (solution: install another keyboard and intercept the "change input method" notification as a trigger). Suppressing the volume keys' usual behaviour was easy (AutoInput -> Key Suppress) but the final step turned out to be quite difficult: How to move the cursor?
After doing some extensive research, I always came to the same point: "not possible without root". Damn.
But then, this plugin came in. The keyword "remote" in its name might suggest that you can use this plugin only to act from one device to another, but that's not true. Actually, you can use this plugin to run adb commands on the same device.
What does that mean? It means that you can run an adb shell command like "adb shell input keyevent xy" on your phone WITHOUT ROOT. In my case, I can run "input keyevent 21" and "input keyevent 22" to move the cursor. So, how can we do that?
Prerequisites:
Connect your device via ADB to a PC (google it if you don't know how) and run the command "adb tcpip 5555". That's it, you can disconnect your device now.
Then in Tasker, create an action with this plugin and type in the following:
IP Address: localhost
Port: 5555
ADB Shell Command: input keyevent POWER
Hit the play button to test this action. If you've done everything right, your screen will turn off.
Congrats, you just executed a command on an unrooted device which usually requires root privileges!
Important:
The only downside is, the tcpip setting does not survive a reboot, so you have to set the port 5555 again via PC after rebooting the device.
I hope I explained the important part well enough. If that's not the case, don't hesitate to quote me and I'll answer here.

digitalpig82 said:
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!
Click to expand...
Click to collapse
I'm sorry for my absence, really busy with school etc. (honestly, I also completely forgot, I hope you can forgive me). I'll try to look into it soon (this week or the next) and see how far I get. I really like that you like my plugin! I just found out myself last week that I can let unrooted phones send shell commands to themselves using my plugin, so I'm glad to see you found it out as well! (I used it for snapchat to simulate volume key presses, which is also possible without root indeed: https://www.reddit.com/r/tasker/comments/699sav/project_share_handsfree_snapchat_picture_and/ It also works for other camera apps that require you to hold the button to film, like whatsapp etc)
Edit: I hope it pleases you to hear that today I started working on it again. I already have the responses bundled in a list in Java, now I just need to parse them to Tasker

loogielv said:
I doont understand. I can type the code, but i do have to remove the "adb sell" part of the code but it's good to go… is that not what this plugin does?
Click to expand...
Click to collapse
Yes, you have to remove the "adb shell" part since all my plugin does is access the adb shell part. This means commands like adb pull etc won't work, that requires a different type of connection, that for now I can't achieve with Tasker. But running any remote shell command should be fine (like how you would run it if you were directly running the commands from a terminal on your phone)

digitalpig82 said:
I just wanted to share how I use this plugin, just to give others an example of what this nice plugin is capable of.
Recently, I bought a new device and for now, I have no intention of rooting it. Coming from a rooted OnePlus One, this means some of my Tasker profiles do not work as expected anymore and I have to find workarounds.
On LineageOS (and CyanogenMod before that), we have the option to display left/right cursor arrows in the navigation bar when typing text. I always loved this feature, since placing the cursor in the right position by tapping will always be a hit&miss game. Since my new device (S7 Edge) has no onscreen navigation bar, I was searching for a replacement solution to move the cursor. I came up with the idea that it would be quite handy to use the volume buttons for this. So, the idea was the following:
IF the keyboard is shown THEN use the volume keys to move the cursor (and suppress any volume changes, if possible).
It took me a while to figure out how to determine whether the keyboard is out (solution: install another keyboard and intercept the "change input method" notification as a trigger). Suppressing the volume keys' usual behaviour was easy (AutoInput -> Key Suppress) but the final step turned out to be quite difficult: How to move the cursor?
After doing some extensive research, I always came to the same point: "not possible without root". Damn.
But then, this plugin came in. The keyword "remote" in its name might suggest that you can use this plugin only to act from one device to another, but that's not true. Actually, you can use this plugin to run adb commands on the same device.
What does that mean? It means that you can run an adb shell command like "adb shell input keyevent xy" on your phone WITHOUT ROOT. In my case, I can run "input keyevent 21" and "input keyevent 22" to move the cursor. So, how can we do that?
Prerequisites:
Connect your device via ADB to a PC (google it if you don't know how) and run the command "adb tcpip 5555". That's it, you can disconnect your device now.
Then in Tasker, create an action with this plugin and type in the following:
IP Address: localhost
Port: 5555
ADB Shell Command: input keyevent POWER
Hit the play button to test this action. If you've done everything right, your screen will turn off.
Congrats, you just executed a command on an unrooted device which usually requires root privileges!
Important:
The only downside is, the tcpip setting does not survive a reboot, so you have to set the port 5555 again via PC after rebooting the device.
I hope I explained the important part well enough. If that's not the case, don't hesitate to quote me and I'll answer here.
Click to expand...
Click to collapse
So...is it possible to create a version of the plugin that runs locally and doesn't disappear on a reboot?

kenkiller said:
So...is it possible to create a version of the plugin that runs locally and doesn't disappear on a reboot?
Click to expand...
Click to collapse
I would like to be able to create such a think but I don't think Google would allow it since it's a big security flaw to have adb opened to the world at all time without notifying the user. Some devices however have a debug over wifi function hidden in the developer options (like the nvidia shield android tv), there you can just enable it and it will probably survive a reboot.
However what I would advise to do if this option is not available, is to create a .bat file on your desktop containing "adb tcpip 5555". That way after a reboot you can just plug in your phone, click the bat file and be done!

Humpie said:
I would like to be able to create such a think but I don't think Google would allow it since it's a big security flaw to have adb opened to the world at all time without notifying the user. Some devices however have a debug over wifi function hidden in the developer options (like the nvidia shield android tv), there you can just enable it and it will probably survive a reboot.
However what I would advise to do if this option is not available, is to create a .bat file on your desktop containing "adb tcpip 5555". That way after a reboot you can just plug in your phone, click the bat file and be done!
Click to expand...
Click to collapse
Hmm....But there's this custom nav bar app where it allows users to grant it adb shell permissions, and the permission survives over reboots. Auto tools and Securetask relies on the same process as well.
I guess what we're asking for is something that's not as encompassing as your plugin. Me, I just want to execute the power command without root in a way that respects smart lock, which is possible now with your app but doesn't survive a reboot, or with the custom nav bar app, which survives a reboot, but restricts me to using it in a tiny button on the nav bar, as the dev doesn't seem interested in exposing the commands to external usage.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
We discussed it in this part here....
https://forum.xda-developers.com/an...avigation-bar-customize-t3590967/post72212488

kenkiller said:
Hmm....But there's this custom nav bar app where it allows users to grant it adb shell permissions, and the permission survives over reboots. Auto tools and Securetask relies on the same process as well.
I guess what we're asking for is something that's not as encompassing as your plugin. Me, I just want to execute the power command without root in a way that respects smart lock, which is possible now with your app but doesn't survive a reboot, or with the custom nav bar app, which survives a reboot, but restricts me to using it in a tiny button on the nav bar, as the dev doesn't seem interested in exposing the commands to external usage.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
We discussed it in this part here....
https://forum.xda-developers.com/an...avigation-bar-customize-t3590967/post72212488
Click to expand...
Click to collapse
It seems this app uses specific android permissions to be able to send events etc. However my plugin has no direct access to the android system (only by using the adb bridge), so granting my plugin these permissions won't help. What however would help is if I could find a way to enable adb over wifi using only some permissions... I have no clue whether this is possible though as the app would have to call service.adb.tcp.port 5555 for itself and that needs root or an adb connection (so it still requires a laptop XD). I'm still trying though.

Humpie said:
It seems this app uses specific android permissions to be able to send events etc. However my plugin has no direct access to the android system (only by using the adb bridge), so granting my plugin these permissions won't help. What however would help is if I could find a way to enable adb over wifi using only some permissions... I have no clue whether this is possible though as the app would have to call service.adb.tcp.port 5555 for itself and that needs root or an adb connection (so it still requires a laptop XD). I'm still trying though.
Click to expand...
Click to collapse
No worries. It's just that it's so close yet so far, heheh.... I guess I'll have to reboot only when home.

kenkiller said:
No worries. It's just that it's so close yet so far, heheh.... I guess I'll have to reboot only when home.
Click to expand...
Click to collapse
I found out it is in fact possible to have wireless adb survive a reboot! However it requires a build.prop edit.
in \system\build.prop "service.adb.tcp.port=5555" needs to be added at the end of the file and then after a reboot adb over wifi will still be enabled (at least it was in my case).
The downside is that this modification can't be done via adb without root unless you have a custom recovery like TWRP and run adb while having that opened and /System/ mounted.
I'm trying to create a zip that modifies the build.prop how it should be modified, but I don't think it's possible to run it through a non-custom recovery...
Edit: I added my .bat file for modifying the build.prop adding that line. It uses an adb connection that requires more rights than what android allows when booted, but should probably work if you are able to access adb from recovery and you are of course booted in recovery mode (using recoveries like TWRP or even some stock manufacturer ones).

Update 4.3 is live!
As requested you can now access the output from the console directly in Tasker.
I tried to order everything neatly in a list, with each line in the console being an item in the list, but this does mean that the initial "device\sdcard $" et cetera get added as an item as well.
But since I didn't want to cut off anything important I just kept it that way. You can just modify the list in any way you want (AutoTools has some handy Array handling tools built in).
I also added some hints in the main screen just for fun.
If you run into any strange behaviour, bugs or have tips, please tell me!
digitalpig82 said:
Any news on the output variable? I have high hopes since you mentioned you already see the output in the logs...
Thanks a lot for this plugin! It makes an unrooted phone much easier to control!
Click to expand...
Click to collapse
Enjoy

Since most people are using my Plugin locally instead of remotely, I'm thinking of renaming it to just 'ADB Shell [Tasker]'. It would make it simpler when googling it. What do you think?

XZ1c not detected by ADB and questions about Immersive Fullscreen mode

I'm using the Minimal ADB and Fastboot program from this thread since it's easier for me to use https://forum.xda-developers.com/showthread.php?t=2317790
First two attached files are for my ADB question, the last three are about Immersion
I'm attempting to enable GSam Battery Monitor's extra stats like I did with my Z3c and my S6 Active, as well as
the Custom Nav Bar app for media controls in my navbar and eventually figuring out how to theme my phone using Andromeda. I believe I did everything correctly, but every time I type "adb devices" to see my phone it doesn't show as connected. My USB debugging is on. Maybe I have my drivers in the wrong folder for this to work? Worked fine when I had my Z3c and S6A.
Also related to using ADB, I want to know if it's fully possible to force Immersive full screen for all apps, including launchers, as there's a portion of the screen being taken away by a digital bezel, and as we saw with the 18:9 screen ratio trend in 2017, bezels are going out. There's a thread in the Pixel 2 XL forum asking if it's possible with Nova Launcher, which what I use, but it goes nowhere. I know that there's multiple apps in the Play store that can force your phone into Immersive mode as seen in my phone screenshots, but they leave an unsightly gap where the navbar used to be.

CMT 1412-4444 'Fours' said:
I'm using the Minimal ADB and Fastboot program from this thread since it's easier for me to use https://forum.xda-developers.com/showthread.php?t=2317790
First two attached files are for my ADB question, the last three are about Immersion
I'm attempting to enable GSam Battery Monitor's extra stats like I did with my Z3c and my S6 Active, as well as
the Custom Nav Bar app for media controls in my navbar and eventually figuring out how to theme my phone using Andromeda. I believe I did everything correctly, but every time I type "adb devices" to see my phone it doesn't show as connected. My USB debugging is on. Maybe I have my drivers in the wrong folder for this to work? Worked fine when I had my Z3c and S6A.
Also related to using ADB, I want to know if it's fully possible to force Immersive full screen for all apps, including launchers, as there's a portion of the screen being taken away by a digital bezel, and as we saw with the 18:9 screen ratio trend in 2017, bezels are going out. There's a thread in the Pixel 2 XL forum asking if it's possible with Nova Launcher, which what I use, but it goes nowhere. I know that there's multiple apps in the Play store that can force your phone into Immersive mode as seen in my phone screenshots, but they leave an unsightly gap where the navbar used to be.
Click to expand...
Click to collapse
You have installed ADB, but did you get the drivers specific to the mobile?
It is possible that drivers from a previous mobile are still on your machine and can interfere. Try from a different PC if you can.
System UI tuner has some options about making all applications immersive. But you do need to be able to run some ADB commands to get this to work.

Didgesteve said:
You have installed ADB, but did you get the drivers specific to the mobile?
It is possible that drivers from a previous mobile are still on your machine and can interfere. Try from a different PC if you can.
System UI tuner has some options about making all applications immersive. But you do need to be able to run some ADB commands to get this to work.
Click to expand...
Click to collapse
I have those drivers saved on my laptop, yes. Is there a specific place I'm supposed to save them to after unzipping them?

Update: figured it out. Used the guide on the full Android Developer site and it was a matter of getting the driver to actually update. Got the ADB command to work with GSam monitor but i cant get it to work with UI tuner :/ I'll just ask in the thread for it why despite typing "adb shell pm grant xyz.paphonb.systemuituner android.permission.WRITE_SECURE_SETTINGS" like the on-screen instructions say does nothing.
Edit: I'm dumb, I spelled a word wrong. Glorious full screen at last.

How To Disable Hisearch - Guide

Perform at your own risk! I am not responsible for your device!
I was trying to figure out how to disable Hisearch and found the package for it. I have successfully deleted it. Hisearch is no longer present when I swipe down on a blank space.
It does not seem to be having any adverse affect on my phone.
1) Download ADB
2) Enable USB Debugging on your device
3) Connect to computer and verify your device is listed with command "adb devices"
4) Type "adb Shell"
5) Type "pm list packages", this will show you all packages installed on phone.
6) Type "pm uninstall -k --user 0 com.huawei.search"
7) you should see the word "Sucess" pop up
8) enjoy having the utterly useless, ****ing annoying search gone!

Do you need root access for this to work?

junkyhlm said:
Do you need root access for this to work?
Click to expand...
Click to collapse
No.

Thank You !!!!!!!! Works like a charm

Is this the same. Settings app. Smart assistance, hitouch, toggle off.
This may be wrong. Was thinking of something else.

It's a different thing, Hisearch is incredibly irritating. Will be trying this soon, as I've been looking for a way to disable it. Thanks for posting OP.

After a few days still no issues from deleting Hisearch. I will say it's safe to get rid of.

I can confirm this worked great for me too, thank goodness as it was driving me mad. Stock launcher is actually OK, except for this.
Would this work for other Huawei apps? If so, maybe we should get together a list of "safe to remove" apps?

Is there a way to extract a program somewhere in case its removal does have a negative impact? I would be willing to start removing some of the bloat but I'm a little worried that I remove something the rest of the system relies on

panrix said:
Is there a way to extract a program somewhere in case its removal does have a negative impact? I would be willing to start removing some of the bloat but I'm a little worried that I remove something the rest of the system relies on
Click to expand...
Click to collapse
You can make a back-up and then restore. Or a factory reset will re-install everything.

This is awesome. Thank you.
A quick and painless way that anyone can use to get rid of this annoying non-feature.
Thank you very much for the clear instructions...
Let's hope an update doesn't re-install it!

Will give this a go later. Thanks OP ??

One question to someone who already uninstalled HiSearch.
When you go to the camera, is there still the possibility to scan things (regognizing Brands, or scanning QR-Codes)?
Or is this also gone with this package?

the_real_fosgate said:
One question to someone who already uninstalled HiSearch.
When you go to the camera, is there still the possibility to scan things (regognizing Brands, or scanning QR-Codes)?
Or is this also gone with this package?
Click to expand...
Click to collapse
Still there. That is a separate package. Hivision vs Hisearch

Worked perfectly for me . Finally able to use scrollable widgets again...
THANKS

Really appreciate this. Can this method be used for disabling other stock apps, like the music app? Like half the time I start up my car, the bluetooth opens the stock app instead of Blackplayer EX (which I have designated as the default)

Just a note if someone wants to use scrollable widgets but also likes to flick down for app search. If you get used to starting your scroll with a small upward movement then it doesn't trigger hisearch to open.
(Just a tip in case anyone wants to keep search)

Slapyou said:
Really appreciate this. Can this method be used for disabling other stock apps, like the music app? Like half the time I start up my car, the bluetooth opens the stock app instead of Blackplayer EX (which I have designated as the default)
Click to expand...
Click to collapse
Yes. Just a matter of deleting the right package. Backup before trying ^^

Nicelysedated said:
Perform at your own risk! I am not responsible for your device!
I was trying to figure out how to disable Hisearch and found the package for it. I have successfully deleted it. Hisearch is no longer present when I swipe down on a blank space.
It does not seem to be having any adverse affect on my phone.
1) Download ADB
2) Enable USB Debugging on your device
3) Connect to computer and verify your device is listed with command "adb devices"
4) Type "adb Shell"
5) Type "pm list packages", this will show you all packages installed on phone.
6) Type "pm uninstall -k --user 0 com.huawei.search"
7) you should see the word "Sucess" pop up
8) enjoy having the utterly useless, ****ing annoying search gone!
Click to expand...
Click to collapse
Worked a treat, many many many thanks!

Worked for me ? thanks for sharing.
On another note has anyone successfully removed any of the other items on the package list without any dramas?

Video/Live wallapaers?

Is there any way to use live wallpaper or video wallpaper on the home screen?

did a search of the settings menu and nothing came up but I've debloated a little bit so it's not conclusive. if you search settings and get nothing yourself I'd say we don't have it.

3mel said:
did a search of the settings menu and nothing came up but I've debloated a little bit so it's not conclusive. if you search settings and get nothing yourself I'd say we don't have it.
Click to expand...
Click to collapse
so we don't have it. how you debloated? getting better performance after it?

I've deleted about half the stuff I want to so far. I used ADB shell commands and a package list posted by b1kerdude in his Samsung game optimiser thread.
it's hard to tell but I do feel it's a little tiny bit nicer now.

3mel said:
I've deleted about half the stuff I want to so far. I used ADB shell commands and a package list posted by b1kerdude in his Samsung game optimiser thread.
it's hard to tell but I do it's a little tiny bit nicer now.
Click to expand...
Click to collapse
Can you provide link to the thread?

S20FE (Snapdragon) (SM-G781B): Force remove GameOptimizationService howto -
For anyone that has been struggling to remove this damn app (com.samsung.android.game.gos), I found the solution (atleast for me on my S20FE (G781B). It goes without saying you WILL need root enabled on your device for this method! Fair warning...
forum.xda-developers.com
he has a list of apps under the spoiler button...
also here's a list provided by FedoraMaster420Blaze via reddit
One UI Debloat List - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com

How To Guide Enable Native Call Recording + OP Stock Dialer on OnePlus 10 Pro

Hi guys,
Just upgraded from OP7T to OP10 Pro as a European user.
Call recording functionality does not come with the device here.
Had native call recording enabled on my OP7T through jOnePlus Tools and the likes.
Jtools Oneplus does not install on our device.
Don't want to give up this very important functionality.
I'm sure there's a bunch of peeps here just like me.
To be clear, I haven't succeeded yet and I'm not a developer.
Hoping someone smarter than me can appreciate what a wonderful breakthrough it would be to make this work on the OP10 Pro.
I made some progress and have some clues which I'll share in summary below:
OP10 Pro comes with Google Dialer, not OnePlus dialer.
Google dialer natively either prohibits call recording or when succesfully enabled transmits a voice message to the other party disclosing the call is being recorded.
Enabled developer options by tapping build number 7 times in software version details (About Phone section in Settings)
In Developer Options: enabled USB debugging & OEM unlocking
jOnePlus Tools app (Play Store) does not install on our device.
Dev replied to a review in Play Store he discontinued further development of the app.
Following page lists what adb shell commands need to be executed to enable native call recording:
Enable Call Recorder on any OnePlus Device [Android 12]
In this comprehensive guide, we will show various methods (both root and non-root) to to enable Call Recorder on OnePlus devices.
www.droidwin.com
Commands on the previous page do not execute, but come back with an error stating "android.permission.GRANT_RUNTIME_PERMISSIONS" must preceed.
"pm grant <android app package name> android.permission.GRANT_RUNTIME_PERMISSIONS" is useless if there's no particular app available you want to do the writing
A YouTube video pointed to the following page providing links to download oos12 working OnePlus Dialer & Contacts app along with instructions to change the default dialer app:
Oneplus Stock Dialer for Oneplus Smartphones running OxygenOS 12
Oneplus Stock Dialer for Oneplus Smartphones running OxygenOS 12. Join Techibee Telegram Channel Join Now WhatsApp Group Join Now Along with the launch of Oneplus 8T, Oneplus started to Include a few google applications like Google Dialer & Google Messaging app as default communication...
techibee.in
The apps work as advertised albeit there's a floating balloon from the Google Dialer appearing overlayed on the OP Dialer when in a call.
After installation, settings of these apps still do not show the option for call recording in the settings options list
I vaguely remember there's a file, that I think needs root access to get to, that can be opened as a text file, in which you can change how your device interprets the region your device is used in, that afterward allows for the otherwise hidden native call recording function to be revealed. But it's been too long since I performed such an operation and can't even remember the name of this file. Maybe the way I explained it triggers someone's understanding here. I'm wondering if this could be a lead to a remaining thing to do to get that call recording function activated.
I fiddled a bit with different ways of writing the cmd adb commands, by for example using the app package names of the installed OP dialer and contacts apps within a pm grant command, but I'm too dumb to get it right, so no luck with that.
Hoping a smarter person here is willing to give it a go and make history
Cheers and godspeed !

Have you tried SKVALEX call recording app? Not sure if it works on Android 12 though. It needs root/magisk to work.

Macke93 said:
Have you tried SKVALEX call recording app? Not sure if it works on Android 12 though. It needs root/magisk to work.
Click to expand...
Click to collapse
Thank you for the suggestion. I am mainly interested in re-acquiring native call recording functionality. I was also informed that Android 12 indeed does not permit any third party call recording apps to function properly. Asides from that, a non-root method is what I pursue as primary objective. But thank you for suggesting, I appreciate it

Got my OP10Pro today too, waiting to see if someone comes up with turning recording on! Such a great feature, would be a waste to miss it!

So for those interested in knowing what the error in adb is that comes back:
Exception occurred while executing 'put':
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2663)
at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:1635)
at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:1589)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:591)
at android.content.ContentProvider.call(ContentProvider.java:2473)
at android.content.ContentProvider$Transport.call(ContentProvider.java:521)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:382)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:278)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:50)
at android.os.Binder.shellCommand(Binder.java:970)
at android.os.Binder.onTransact(Binder.java:854)
at android.os.Binder.execTransactInternal(Binder.java:1226)
at android.os.Binder.execTransact(Binder.java:1163)

Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot

Seems that incoming calls still run through the Google dialer and disables the call recording function again. Needed to execute the command again several times now, whilst I didn't perform any reboots throughout that time that could have invoked that otherwise.
Oberserved if it deactivated after an incoming call, once I noticed that this has happened before. Strangely, last incoming call that went through Google dialer didn't disable it. I may be completely wrong. Something else might be causing that deactivation. Maybe the system's automated security measures baked in are reverting it, idk.
I keep thinking about the build.prop file. I remember something was in there referring to how your device interprets the region it is used in. Supporting/unsupporting region sensitive functionalities. Like call recording..

This is really annoying.
I really liked OP stock dialler and contacts.
Hopefully there will be a way to bring it back without having to root the phone.

Just found this workaround...

No need to root or download all kind of developers apps, I uses on my oneplus 10 pro - oneplus call recorder app from the play store, it records - regular calls, skype, whatsapp, and more...

I tried to use OnePlus Call Recorder but It's renamed app Travis Call Recorder from same developer. The app works like most others, records only silence when using an external handsfree or headphones. the app doesn't replace the native call recorder. Recordings with using OnePlus dialer truly works from guide TechiBee.

Installing the previous version of Joneplus Tools from apkmirror works. Granted adb permissions to the app through LADB (read above) and it seems to work fine.
Also check Techibee's latest video if you want to learn how to properly handle the OP Dialer sometimes not being revealed as the primary Dialer on screen. He also explains how you can access the OP Dialer on incoming calls.
It's a welcome addition to the above advised steps for those who are not in Call Recording native activated regions (Europe, other?...)

I have android 12, on my oneplus joneplus doesn't work on this version any more. And as for the oneplus call recorder, it is available on play store, i have Chinese oneplus 10 pro version ne2210 with European rom ne2215. Its working and recording any call. For the old os i guess joneplus still works, it was working on my previous phone.
Who really wants it, i mean, you need to use adb with developer option to make it work.
But if thats the only option you have, so use it.
Another thing, on the new os, i dont have the phone app from oneplus, its google phone app so i dont think we can add the joneplus and the native call recorder unless you install the phone app from oneplus, but again, you will have to use adb and install updates for the new app by your own, and who knows if that will even work.

I think for you to download the app oneplus call recorder or joneplus, it depends on the os version and also maybe the region that you are in.

I found this link to the app https://www.google.com/amp/s/apkpremier.com/amp/com-travis-callrecorder-oneplus

shhuhs said:
I have android 12, on my oneplus joneplus doesn't work on this version any more. And as for the oneplus call recorder, it is available on play store, i have Chinese oneplus 10 pro version ne2210 with European rom ne2215. Its working and recording any call. For the old os i guess joneplus still works, it was working on my previous phone.
Who really wants it, i mean, you need to use adb with developer option to make it work.
But if thats the only option you have, so use it.
Another thing, on the new os, i dont have the phone app from oneplus, its google phone app so i dont think we can add the joneplus and the native call recorder unless you install the phone app from oneplus, but again, you will have to use adb and install updates for the new app by your own, and who knows if that will even work.
Click to expand...
Click to collapse
Thank you, but what you propose is completely different than what I've created this thread for.
The idea was to find a workable solution in obtaining native call recording inside OnePlus Dialer, whilst Joneplus Tools seemed to no longer install on android 12.
All these things have been RESOLVED and shared above to the extent that it is possible at this time of writing.
In my posts above I've shared links to where the OP Dialer can be downloaded along with a link on how to install it and make it default. I explained how to get the adb command to execute.
I provided a solution for adb OTG (LADB), given the adb command needs to be re-executed at times.
In my last post I also shared that the second to last version of Joneplus Tools DOES INSTALL on our device that comes with Android 12 pre-installed.

anarche_diver said:
Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot
Click to expand...
Click to collapse
anarche_diver said:
Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot
Click to expand...
Click to collapse
@anarche_diver Hello, thank you for the detailed post. I just switched from 7Pro to 10Pro (NE2213) as well and was looking to get native call recording. Firstly, you shouldn't be selling yourself short as you are definitely smart enough to have put in the efforts at the right places it seems, a special thanks for that
However, I am stuck at LADB. After I have plugged in the command (copy pasted from your post), it shows the following error. Could you maybe help me figure out what I did wrong ? Thanks in advance & below is a screenshot from LADB.
Edit : Please note that one way or another, I would love to get the native call recording feature. And I don't mind even if the voice announcement of call recording is issued

has anyone found a very good stock dialer for root my device?

Database Develop

welcome