Hi,
Can anyone confirm this feature is still supported on Android 12.
The guide to ADB command to activate feature is no longer available via the app.
Can anyone provide the instructions.
Many thanks,
Andy
Related
I bought this nice minicomputer - MK812 Mini PC Dual-Core Android Camera Mic BT 4.2.1 and I relied on the fact that since there is Android 4.2 installed, I can use switching users, but unfortunately this function is disabled. I need to get it to work.
Of course, I googled. This is what I've already tried:
http://www.pocketables.com/2013/03/how-to-enable-multiple-user-mode-on-cyanogenmod-10-1-and-some-other-android-4-2-2-roms.html
The problem is that this command pm get-max-users returns Unknown command get-max-users.
Furthermore, when I enter SetProp fw.max_users 8, it has no effect, even after a reboot. The command pm usernameyouwanthere create-user is also without effect.
http://forum.xda-developers.com/showthread.php?t=2187934
App - 4.2 Multiple users feature enabler
This app can't be installed by Google Play (apparently MK812 is not a compatible device). Since I couldn't get APK anywhere to download, I downloaded the source code and compiled it and generated APK. Unfortunately, can't be installed either.
I studied the source code and found out that even if i was able to get it installed, it wouldn't have worked anyway, because this app runs similar commands (as those above) instead of the user.
https://play.google.com/store/apps/details?id=fahrbot.apps.switchme
This could be a solution even for Android 4.0 and 4.1. It works, but switching takes too long, because it requires a reboot and this switching is not integrated into the system. So I do not want it.
Do you know of any other solution or anything what I could try?
I googled again, found this - http://forum.xda-developers.com/showpost.php?p=34362377&postcount=8
But setting fw.max_users=8 in /system/build.prop haven't helped either.
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
H0w4rd said:
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
Click to expand...
Click to collapse
try
"setprop fw.max_users 8"
Lower-Case setprop without the quotes.
Edit: I see, can you and are you willing to get the source, modify it, build it and flash it? I'm going to have to enable it for my phone so when I figure out what needs modifying I'll let u know.
Samsung Galaxy S7 on latest April Patch. Giving access to Greenify through this "https://greenify.uservoice.com/knowledgebase/articles/749142-how-to-grant-permissions-required-by-some-features" method is not working. I tried using different version of it starting from v2.9 to 3.3. The older ones give me a notification that I do not have root privileges, but the latest version don't.
Is this method still viable or just not working for me?
Also if this method is something that is endorsed by the developer shouldn't it be good to put a force check on it?
PS: Was working before updating to 3.2.2, by which I mean it didn't use to give me the "No root" notification.
PPS: Used to different machines with both CMD PowerShell to grant the adb access.
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..
I need advise on the following as I am doing mobile application security and testing.
I most of the time I use Burpsuite/Magisk/Objection/Frida for testing purpose
Some of the constraints I am facing;
1) How do I set a permanent alias to the phone itself
2) How do I issue remote command like adb shell "cd /" and show the responses as successful
3) What are some of the ways to bypass root detection and ssl pinning (I already know there is Magisk Denylist - but its not effective at times)
4) I am also involved in IOS related testing and such, is there a wall to post IOS related stuff here.
While I was working on IOS, I find that apt-get command is quite useful but it is not available on android phone, I want to have a lot of useful software in the phone like nano, which I installed using magisk etc.