Related
I have an Android 6.0 px5 head unit which has the lock screen settings disabled in rom. I tried Google's Android Device Manager to lock the unit remotely, and it just gave me a "lock" screen that can be easily bypassed. Problem is, this screen pops up at ever boot, as soon as Google Play services connects to wifi, and it's just plain annoying.
I've researched this and tried a number of things. Because there are no lock settings, the normal way to resolve this, enter the password on the locked device, won't work. I've tried a number of adb solutions (I am rooted on device), including removing the gesture.key file, issuing commands to the settings.db and locksettings.db databases, setting
Code:
ro.secure=0
in default.prop, and issuing the unlock keyevent ("
Code:
input keyevent 82
"). Nothing works. The only thing I have been able to do is create a script that removes the lock screen from the current window (
Code:
dumpsys window | grep mFocusedWindow
) -- but it still stays in the status bar and comes back every boot.
My question is: Does anyone know how I can programatically, from the Linux command line, issue a command back to ADM that either sends an "unlock" code or sends the password it's expecting or somehow responds in the way it needs in order for it to stop trying to lock my device at every boot?
Im trying to use Tasker app, but it needs to enabled on "Accessibility" android config
The problem is my Accessibility cannot be accessed because a long time when i removed some lg g2 bloatwares but i removed some wrong system apps
So.. can i enable Tasker on accessibility using ADB?
Any tip?
Thanks!
Please any tip?
Hello. Just for references, as it is one of the first results shown in DuckDuckGo, this worked for me:
Code:
adb shell settings put secure enabled_accessibility_services packagname/servicename
Source: https://stackoverflow.com/a/38939299
Hi Guys,
A lot of us are getting new devices that are not yet supported by developers or will never be supported and rooting new devices now a days is getting harder, that's why methods requiring no root are essential.
I was pointed to by @EMJI79 to the original thread of this method by @luisshnyder. Great thanks to both of them. :good:
Requirements:
* ADB and Fastboot installed on PC or Mac.
Instructions:
Type without quotations in CMD or Windows PoweShell(use ".\"before command in PowerShell):
"adb shell wm overscan 0,0,0,-202"
Notes:
1. Make sure to use an alternative navigation app before doing this.
2. To change the height change the values between (0 to -210)see what suits your screen best(for me it was -202).
3. The effect sticks after reboot.
4. To return to normal type without quotations: "adb shell wm overscan 0,0,0,0"
5. This works on all Android versions Oreo and before, it also works on many devices.
6. There are minor bugs stated by the original thread so check them out if you have any, i haven't encountered any yet except you wouldn't be able to see the camera & voice shortcuts in the lock screen.
Finally it's best to combine this with hiding the status bar too, so type afterwards without quotations:
"adb shell settings put global policy_control immersive.status=*"
-If you want to customize on per app basis follow my other guide.
Good Luck!
I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?
Thank you so much for sharing this, I've been searching for a way to completely hide the navbar without Root. Now Gesture Control can actually be used as intended. ?
My gesture non root setup I wish Google will implement.
Rashad83 said:
I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?
Click to expand...
Click to collapse
is there any command that enables the navbar on navbar disabled devices?
zohaibahd said:
is there any command that enables the navbar on navbar disabled devices?
Click to expand...
Click to collapse
Use this app https://play.google.com/store/apps/details?id=tw.com.daxia.virtualsoftkeys
For Redmi S2
adb shell wm overscan 0,0,0,-82
ishtiaqe22 said:
For Redmi S2
adb shell wm overscan 0,0,0,-82
Click to expand...
Click to collapse
Im also on redmi s2 running lineage os and 0,0,0,-97 works better for me
is there a way to do the same thing as : "adb shell wm overscan 0,0,0,-202" but for the status bar.
this worked great for my nav bar- but i dont wnt to completely remove the status bar, just move it up a little.
thanks for the respond.
Dear @Rashad83 and other Contributors!
Thank your for this little summary thread, I hope I am not necrobumping right now. I just wanted you to know, that this method is still working flawlessly. My settings for the Umidigi S5 Pro (Android 10): ,,wm overscan 0,0,0,-48"
have anyone tried this on umidigi bison?
infelizmente esse comando não funciona no galaxy s20 android 13
no meu s8 android 10
funciona bem
Oneplus has started to put Google Dialer along with its new android updates. Although, Google Dialer has many functionalities but, it misses out the native call recording of Oneplus Dialer (without the annoying announcement of calls being recorded of the GOOGLE DIALER).
I tried searching all over the internet but could not get Here is the process of activating native call recording in Oneplus 9R.
Install native Oneplus dailer (you can download from the below link)
https://drive.google.com/file/d/1T4UhfxsmFytd8MTBYN7vZZeVWe8yFAvJ/view
(from https://forum.xda-developers.com/t/...th-call-recording-in-oneplus-8t-nord.4189165/)
Activate USB Debugging on your phone from the developer options.
Go to SETTINGS
ABOUT PHONE
tap few times on BUILD NUMBER before activating DEVELOPER OPTIONS
go back to SETTINGS
go to SYSTEM
DEVELOPER OPTIONS
and activate USB DEBUGGING
Install joneplus tools from Playstore
https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en&gl=US
Download Platform tools for android in WINDOWS
USE ADB instruction method from the PLATFORM TOOLS FOLDER
Check if you can find your phone or not
./adb devices
it should show the phone as listed.
after finding your phone as listed, type the following instruction
./adb shell settings put global op_voice_recording_supported_by_mcc 1
This will activate the native call recording feature of ONEPLUS DIALER.
However, the call recorder will be deactivated once you change the sim card or restart your phone. So, you need to install JONEPLUS TOOLS app from GOOGLE PLAYSTORE which will activate the call recording automatically every time you reboot your phone.
You need to provide the permission to joneplus tools by using ADB instruction
./adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
This will allow joneplus tools to automatically restart and activate the call recording every time the phone reboots. Finally, you will have call recording feature in your beloved ONEPLUS 9R.
Is there any method with root other than the axet call recorder & skvalex?
Thanks in advance.
It's weird, I'm getting the recording option right after installing the dialer apk without performing any adb command or installing any joneplus tool. It's staying Even after reboots, I'm on oos 11.2.LE28DA factory firmware, I'm not rooted and bootloader is locked.. it's weird..
Thanks a lot btw.. pretty useful for me..
Hi there,
OnePlus 9R is one of the most recent devices prior to the OnePlus 10 Pro that just received its global release.
Same thing there, comes with Google Dialer stock. The above apps work on that phone too, but jOnePlus Tools does not install, and the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 does not execute.
I made a post similar to yours on that forum, with the difference we are stuck without understanding why.
Could you please help us understand why this command does not work on our phones as compared to the Oneplus 9R?
It would help that community a lot.
Here's a link to my post:
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...
forum.xda-developers.com
Thanks a lot in advance
Edit: Found a working solution. All I need now is to understand how to write a Tasker task to automate the adb command upon each reboot. This is what jOnePlus Tools normally took care of, but since we can't install it on that device..
Finally i found a method to record call on realme gt 2 pro global gdpr version, who is persistent at boot. No root, no bootloader unlock.
Step one : install setedit from play store and add op_voice_recording_supported_by_mcc with 1 value to global settings. You have to give Setedit write secure rights with adb
Step two : install phone apk below.
That's it. Start Google dialer and make a call. Still works after reboot.
Not working : automatic call recorder, you have to press record button when you're in call.
Notice: if you don't see record button in Google dialer , is normal, just press back button to see realme dialer.
This should work on all color os 3 device.
Recorded call are in internal memory / music/ recordings/ call recordings folder.
ENJOY !!
No working... No see
Which apk needs to be installed for step two?
NVM I figured it out
Not working, it has changed the dialer but instead of recording button I have a "contacts" button and when I press it nothing happens.
Please uninstall phone from installed apps and install again.
criszz said:
Please uninstall phone from installed apps and install again.
Click to expand...
Click to collapse
Same, tried also to reboot but nothing
No permission to add a new line in Global Table
RazvanelTM said:
No permission to add a new line in Global Table
Click to expand...
Click to collapse
Same here, I've added the option in the system table maybe that's why it is not working
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
criszz said:
Yes, you must provide write secure rights for setedit with adb to edit in global.
Updated first post with that.
Click to expand...
Click to collapse
How can do? Have any tutorials?
manu81cba said:
How can do? Have any tutorials?
Click to expand...
Click to collapse
By default, for your protection, Android prevents you from modifying the SECURE and GLOBAL tables. If you have Android Jellybean or later, you can remove this protection from an ADB shell using the command "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS". On earlier versions, you can only remove this protection on a rooted device by installing SetEdit to the system partition.
All working flawless now I can confirm that
Not working when giving the permission in adb
RazvanelTM said:
Not working when giving the permission in adb
Click to expand...
Click to collapse
Try to activate first in the developers options this one: "Disable permission monitoring"
shootemdown371 said:
Try to activate first in the developers options this one: "Disable permission monitoring"
Click to expand...
Click to collapse
It worked, thanks!
Now it's confirmed to work and we must think how to enable automatically record for all calls. People who said not working without knowing, please edit your post.
In setedit ...you know what need change for active the volte ?
Thank you very much it's working for me!
PS for those unfamiliar with SetEdit can also use this in adb after disabling permission monitoring:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Just must be applied after every restart ( that is what i read )
Nice post, thanks for sharing. Any solution for Xiaomi Redmi Note 10S, Global ROM MI?
Also working on the regular gt2