Related
If anyone wants to disable charging LED, here's an easy way via Tasker.
Note: notifications will not cause LED to blink while charging
State, power, power any
Enter task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
3. run shell as root, "chmod 444 /sys/class/leds/red/brightness"
Exit task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
Hi! Thanks for sharing. I am getting the following error:
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/Shell runBackground "chmod 644 /sys/class/leds/red/brigthness" root: true timeout: -1
23.21.58/Shell start process-thread ID 725
23.21.58/E add wait type Shell1 time 2147483647
23.21.58/E add wait type Shell1 done
23.21.58/E add wait task
23.21.58/E Error: 127
Am I doing something wrong?
Thanks!
Dj Telo said:
Hi! Thanks for sharing. I am getting the following error:
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/E Run Shell: ->
23.21.58/Shell runBackground "chmod 644 /sys/class/leds/red/brigthness" root: true timeout: -1
23.21.58/Shell start process-thread ID 725
23.21.58/E add wait type Shell1 time 2147483647
23.21.58/E add wait type Shell1 done
23.21.58/E add wait task
23.21.58/E Error: 127
Am I doing something wrong?
Thanks!
Click to expand...
Click to collapse
Does Tasker have root access? Check it in Magisk/superuser section.
_mysiak_ said:
Does Tasker have root access? Check it in Magisk/superuser section.
Click to expand...
Click to collapse
Yes it does. I can even execute other shell commands with root without problem. Is the command you are giving maybe only valid with Nougat and not Oreo?
Thanks!
Dj Telo said:
Yes it does. I can even execute other shell commands with root without problem. Is the command you are giving maybe only valid with Nougat and not Oreo?
Thanks!
Click to expand...
Click to collapse
Oups, my bad, sorry for the typo in the instructions. It has to be brigHTness, not brigTHness.
Will this work on the Mi A3 too?
And will the notification led still blink when not charging the phone?
Thank you
DBuffon said:
Will this work on the Mi A3 too?
And will the notification led still blink when not charging the phone?
Thank you
Click to expand...
Click to collapse
I don't have rooted A3 at hand, so can't try it. It might work, there is no harm in sending those commands over adb shell as root user. You will see the result immediately.
Sent from my Mi A1 using Tapatalk
_mysiak_ said:
I don't have rooted A3 at hand, so can't try it. It might work, there is no harm in sending those commands over adb shell as root user. You will see the result immediately.
Click to expand...
Click to collapse
Ok, I'll try but I don't understand the following:
_mysiak_ said:
State, power, power any
Enter task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
3. run shell as root, "chmod 444 /sys/class/leds/red/brightness"
Exit task:
1. run shell as root, "chmod 644 /sys/class/leds/red/brightness"
2. run shell as root, "echo 0 > /sys/class/leds/red/brightness"
Click to expand...
Click to collapse
Are the "Enter task" the code that should be run when the charging cable connects to the phone and the "Exit task" the one that runs when unplugging the cable?
I don't understand what this code does, and I don't want to mess up the led (that is: before I proceed, I want to know how to revert if things don't go as they should). Thank you.
DBuffon said:
Ok, I'll try but I don't understand the following:
Are the "Enter task" the code that should be run when the charging cable connects to the phone and the "Exit task" the one that runs when unplugging the cable?
I don't understand what this code does, and I don't want to mess up the led (that is: before I proceed, I want to know how to revert if things don't go as they should). Thank you.
Click to expand...
Click to collapse
Enter and exit tasks are for Tasker. If you want to try the commands from adb shell, enter those mentioned in "entry task" first and check if LED stopped glowing. To restore the original state enter commands from "exit task" (or just reboot the phone). Changes are not permanent.
Commands do the following - enable RW access to LED control, set intensity to 0%, disable RW access.
_mysiak_ said:
Enter and exit tasks are for Tasker. If you want to try the commands from adb shell, enter those mentioned in "entry task" first and check if LED stopped glowing. To restore the original state enter commands from "exit task" (or just reboot the phone). Changes are not permanent.
Commands do the following - enable RW access to LED control, set intensity to 0%, disable RW access.
Click to expand...
Click to collapse
Great, thanks for the information.
Unfortunately I can't issue the commands (sorry, I'm new to the adb shell):
Code:
[email protected]:~$ adb shell chmod 644 /sys/class/leds/red/brightness
chmod: /sys/class/leds/red/brightness: Permission denied
[email protected]:~$ adb root
adbd cannot run as root in production builds
DBuffon said:
Great, thanks for the information.
Unfortunately I can't issue the commands (sorry, I'm new to the adb shell):
Code:
[email protected]:~$ adb shell chmod 644 /sys/class/leds/red/brightness
chmod: /sys/class/leds/red/brightness: Permission denied
[email protected]:~$ adb root
adbd cannot run as root in production builds
Click to expand...
Click to collapse
adb shell
su
chmod ....
It works on the A3 too. Thanks!
In my mi A1, revengeos android 9, in enter task, 2th step go in error
d_borghi said:
In my mi A1, revengeos android 9, in enter task, 2th step go in error
Click to expand...
Click to collapse
What kind of error..?
_mysiak_ said:
What kind of error..?
Click to expand...
Click to collapse
Allego
d_borghi said:
Allego
Click to expand...
Click to collapse
Try to run that command from terminal on the phone (or via ADB) as root. Alternatively, store the error message in some variable in Tasker and display it, so we know why exactly does it fail. On my phone it still works fine (Mi A3 now).
how can i try by an emulator terminal app in my phone directly?
d_borghi said:
how can i try by an emulator terminal app in my phone directly?
Click to expand...
Click to collapse
Install and run for example this app https://play.google.com/store/apps/details?id=yarolegovich.materialterminal&hl=en
_mysiak_ said:
Install and run for example this app https://play.google.com/store/apps/details?id=yarolegovich.materialterminal&hl=en
Click to expand...
Click to collapse
Finally, I try the app.
By this terminal I receive no error, look at the screenshot.
Why tasker goes in error?
d_borghi said:
Finally, I try the app.
By this terminal I receive no error, look at the screenshot.
Why tasker goes in error?
Click to expand...
Click to collapse
Could you take a screenshot of the details in Tasker for that one task which gives you an error? Maybe you have a typo there.
Last month i installed Navigation Gestures app from and xda and granted it permission as in tutorial using adb and everything worked fine.
However from last few days i have been trying to use adb to grant extra permissions for greenify app (as required in non-rooted devices) for
following functions:
I connect my moto g5 via USB and enable Usb debugging then from adb folder opened Command prompt and entered following command to list device ie "adb devices" following is the response of adb:
Adb does not show my device :crying: last time it worked on first try when in was doing for Nav Gesture app.
What am i doing wrong plz tell why is this happening and any solution,
plz help as i don't wanna root my device as of now.
Below are the SS of the permissions i want to give and the adb error in pc
Thanxx in advance
Check in device manager (press Win+R, type "devmgmt.msc" and press Enter) if there's no exclamation mark of ADB device.
Andrej_SK said:
Check in device manager (press Win+R, type "devmgmt.msc" and press Enter) if there's no exclamation mark of ADB device.
Click to expand...
Click to collapse
Issue fixed it did showed an exclamation mark and google for it foumd how to manually install the driver and provide adb permission on phone and it worked. GRANTED GREENIFY PERMISSIONS. :laugh:
For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
bruceas said:
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
Click to expand...
Click to collapse
Thanks for the update, it seems to be related to the Windows regional settings on a PC (?). On my personal PC it works with double quotes ", on my work PC with single '. I've update the instructions.
Edit: if you split command into two, it works with double quotes as well
1. adb shell
2. settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
_mysiak_ said:
For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
Click to expand...
Click to collapse
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
arjo656 said:
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
Click to expand...
Click to collapse
https://www.xda-developers.com/quickly-install-adb/
https://www.xda-developers.com/what-is-adb/
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
arjo656 said:
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
Click to expand...
Click to collapse
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
_mysiak_ said:
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
Click to expand...
Click to collapse
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
arjo656 said:
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
Click to expand...
Click to collapse
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
WORKS!!!!!! :good:
thanks!!
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
Dont kill app, they will use more power when relaunching them, they use almost no power when in background.
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
No idea, I wasn't even aware of this button. As antoine62 said, it's totally useless. If you need to kill an app, just swipe it away from recent menu (or click on details and "force stop" if the app works with background service).
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
arjo656 said:
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
Click to expand...
Click to collapse
That button should not be really used at all, it just kills all cached apps. Stock Android is pretty good at memory management. There is really no point in force killing all the apps manually.
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
arjo656 said:
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
Click to expand...
Click to collapse
I don't have Android 10 yet and it seems that Google killed this feature (why oh why). I found this app which might help, give it a try and let us know. https://play.google.com/store/apps/details?id=nu.nav.bar
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
lowmanager said:
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Click to expand...
Click to collapse
Nope, Google removed the interface for navbar customization in Android 10. I just keep stock 2 buttons navbar and use "Edge gestures" app for one hand operation (it's even on sale right now, grab it while you can).
Phil_gloves said:
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
Click to expand...
Click to collapse
For 3 buttons navbar replace "contextual" with "recent". For example:
Code:
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
Edit: if you want to keep "contextual" button as well, this might work (can't test it as I'm on Android 10 already):
Code:
adb shell settings put secure sysui_nav_bar "contextual;space,recent;home;back,space"
I'm running on the 10.5.10.IN11BA build.
Just get a command shell to your OnePlus 8 Pro through adb, no need for the device to be rooted or anything.
Once you get there, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It will launch the FactoryMode app and get you directly to the manual camera test view.
Just press the bottom right icon until you get to the color filter.
I have no doubt there is easier and quicker ways to get the same result, maybe through an apk.
Edit:
As far as I know, this workaround could work on any OnePlus 8 Pro model.
Also, as pointed out by ster88, you also can take videos with the filter, which was not possible with the camera app.
I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.
sajjadhussaini said:
I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.
Click to expand...
Click to collapse
Sure !
To enable developper mode, go to "Settings > About phone" and tap the "Build number" until they tell you have developper mode enabled.
Then go to "Settings > System > Developper options" and under "Debugging" enable "USB Debugging" and "Wireless ADB Debugging".
Once that is done, on your computer, download the platform-tools, containing adb here :
Code:
https://developer.android.com/studio/releases/platform-tools
Once it is downloaded, go inside it with your command line.
If you are doing this wirelessly, get your phone IP address and type:
Code:
adb connect <your-phone-ip-address>
Then if it worked, to know what the transport id of our device is, type :
Code:
adb devices -l
Once you have the transport id, type this to get a shell to your phone:
Code:
adb -t <transport-id> shell
You can get more details on how adb works here:
Code:
https://developer.android.com/studio/command-line/adb
Then when you have access to the shell, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
If everything went fine, you should get access to the camera !
I could not use a terminal app to run the command, usually because the terminal app doesn't want to let the camera application to take over the view, or something like that, not sure.
The ideal would be to have a dedicated apk to run the command, at least for the time being.
Tried to launch using an app called Activity launcher and it didn't work.
play.google.com/store/apps/details?id=de.szalkowski.activitylauncher
imgur.com/a/BS9Wqzc
I'm not rooted, are you sure this works for non rooted devices? I'll try later with adb to see what happens.
Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
From what I understood, you need to run the command from an adb shell. You cannot run it from within the phone as far as I know.
You can still run it from adb and "lock" the application so it stays in the background.
And I tried with multiple Terminal apps, the command works with none of them (Termux, Terminal Emulator, Material Terminal, etc...)
Apparently, you have some rights on the adb command shell that you don't get as a simple user on the phone.
You man are genius. I found easy way also to keep it running if needed. After getting the camera test to run, you can lock the app so phone will not close it and always return to it. Thanks, finally I can enjoy my camera
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
lllsondowlll said:
Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
Did you get any solution for this ?
aishkumar said:
Did you get any solution for this ?
Click to expand...
Click to collapse
...
lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I've made a script that allows you to launch the Camera from your phone by just typing ./camera in Termux. No root needed. It can be found here: https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md
can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera
It works but not really required
It's working, but have few questions to myself.
1. Does it really needed?
Ans: No, you won't keep clicking pics of plastic material to see inside.
2. Is it handy?
Ans: yes, once opened you can pin/lock it in recent app and open whenever required.
It is just a IR camera and nothing wrong in it, I believe OP will enable it in future, because it really doesn't show through the clothes and even if you want to see for some black thin clothes, you need to go near.
So if you are thinking to click the nude people and go closure you will be slapped.
Few images I have taken.
babsvsphudi said:
can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera
Click to expand...
Click to collapse
https://youtu.be/iVQYu-CeN24
You can't hurt anything. Just follow the instructions.
lllsondowlll said:
You can't hurt anything. Just follow the instructions.
Click to expand...
Click to collapse
thanks man you are awesome love n respect for u brother
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.
pcningen said:
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.
Click to expand...
Click to collapse
I was able to resolve this issue by reinstalling factory mode. I apologize to you for a fuss over. Many thanks to the developers of this method.
Since I can't get termux to work for now, another idea if you want to have it accessible all the time(*), is to run this (beautiful) command with an adb shell from a computer and then lock the app so you can't accidentally close it.
After that you can always go back to it whenever you want it!
*App won't remain locked after reboot, obviously.
lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I wanna piggyback on this some, since this is similar to the process I just did.
So while this works for nonroot users (I didn't actually test the nonroot version myself), if you are rooted, AND using magisk, I personally install ADB and fastboot binaries from the repo from zackptg5(?) And then just told termux to run an elevated shell (su) and then pasted in the command linked in OP:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It then loaded the testmode camera app, and (xXx caused it to crash, I had to disable it but I don't know if it's a setting with my config) voila. It worked! Thank you.
Edit: I wanna say just running termux in root would solve the issue either way still, but, my point still is there.
Android 9 added a new feature which allows for the temporary rotation of the screen, with the press of a button would appear when the phone is put into landscape orientation. MIUI for some reason has decided to exclude it, we're at Android 11 and it still doesn't have it. I was wondering if Xiaomi.EU ROM has this feature, or would I have to go with a custom ROM?
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
reg66 said:
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
Click to expand...
Click to collapse
Cool, this could be a workaround for my issue, just enabling rotation in some apps. I'll try it out, thanks!
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
CharlieMHz said:
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
Click to expand...
Click to collapse
Ikr it's such a useful thing to have!
@pawelmiernik I just registered to say that you are a frigging legend, thank you so much!
Absolutely idiotic that they left out this option somewhere in the settings. Especially when you can reactivate the already implemented button with such a workaround. Ridiculous.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Thanks for this, would like to add that another way of having it persist is to use SetEdit and add show_rotation_suggestions 1 to the secure table. You'll need to give the SetEdit app permissions to write to the secure table. You can do it with root but if you're not rooted you can use adb, just be sure to enable "usb debugging (security settings)" as well.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Just to add on to this, for me, the settings stayed even after a restart, so I didn't need to run it again after reboot.
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Weslington9 said:
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Click to expand...
Click to collapse
How to turn on this feature, I am on miui13 but can't find it ?