I modified android phone hdmi output properties using ADB commands below
adb shell setprop persist.demo.rotationlock false
adb shell setprop persist.demo.singledisplay true
In order to see the change,
I will have to do either one of the following.
turn off phone screen, then turn on phone screen.
restart the phone or tv
unplug the phone to monitor, then plug the phone to monitor.
What I want:
Is there any command to do a quick reload/reset/refresh phone screen or video output connection? so I don't have to do any of the above to see the change.
Any help is appreciated
To "turn off phone screen, then turn on phone screen":
adb shell input keyevent 26
Run the above command twice.
26 is the keyevent code for power button.
To "restart phone":
adb reboot
I am playing around with the Android doze mode in my app and just wants to examine my apps behavior in doze mode.
My application enqueues some tasks in a job scheduler while in doze mode. I want to check if any event, that wakes up the device, triggers the jobs that my app had put in the job scheduler while in doze.
I programmatically put the device in doze mode by firing the below commands-
adb shell dumpsys battery unplug
adb shell dumpsys deviceidle enable
adb shell dumpsys deviceidle force-idle
I also tried the other set of commands to put it in the doze mode
adb shell dumpsys deviceidle step deep
The above commands put the device in deep idle mode and I check for it with the command-
adb shell dumpsys deviceidle get deep
output: IDLE
But even if I give a phone call, which turns the device screen on and vibrates the device, the device status doesn't change. The above command continuous to give me IDLE status.
Question:
Can I emulate the scenario where I put the device in doze(by firing some commands) and then the device would move out of doze by some events that are stated by the android doc (moving it, turning on the screen, or connecting a charger).
EDIT
My observations after doing a lot of research-
When we program a device to go in the deep idle mode, the device doesn't come out of doze mode unless explicitly done using the command-
adb shell dumpsys deviceidle disable
So, even if you a send a text message or call the device which would cause
- the device screen to turn on
- the device to vibrate
but because if is programmatically set to idle mode, it continuous to remain in the same state.
I believe the problem is that you are using force-idle.
When you do that the device enters IDLE mode until you "unforce" it with:
adb shell dumpsys deviceidle unforce
You can check for alternative ways of entering IDLE mode from adb in the docs or in other question, like here:
How to shift device in Doze Mode (Android Preview M / Marshmallow)?
Problem description:
Each time wen I connect USB cable between PC and my mobile phone the battery automatically is charged. I want to use ADB protocol but I don't want to charge my battery during ADB connection. Is it possible to to turn off this charging? And ofcourse how can I do this?
Environment:
Mobile phone with Android os 4 and higher
I need only mention that my referential device working on android 5 so there is no /sys/class/power_supply/battery/force_usb_charging file
BEWARE: adb shell dumpsys battery unplug only MOCKS the battery status. I checked with a current indicator on my usb cable and this does not change the amount of flowing current at all so the battery is still charging.
It only changes what applications think about the state, so for example google play would not start updating if you have configured that it can only update when charging...
Changing the value of a file like /sys/devices/battery.XX/power_supply/battery/hv_charger_set to 0 does really work but its a different file for every device. For example, for my yotaphone 2 with a snapdragon 805 there is a file: /sys/devices/qpnp-charger-14/power_supply/battery/charging_enabled
So you could make a script that you can use in tasker(if you have root):
echo $1 > /sys/devices/qpnp-charger-14/power_supply/battery/charging_enabled
if you write that to an executable file /data/setcharging.sh then you could call the script like /data/setcharging.sh 0 to disable or
/data/setcharging.sh 1 to enable.
This works, I checked with my current metering usb cable, but it does not show that it works in the battery status icon. So you could use a combination of this and adb shell dumpsys battery unplug / reset to make it look better, but the problem is that then apps like tasker don't know whether you have ac power or not, so you can not put triggers for that when you've set it to unplugged...
One more thing, I also tested what it does in recovery (twrp) and during boot. And it turns out that during boot and in recovery, the charging just works. So its not like your device will end up dead if you forget to turn on charging again. You can always charge it in recovery mode and then boot up and change the value again (or change it while in recovery if your recovery gives access to adb).
Lastly, there are apps on the play store that are made exactly for this, but I would recommend getting such a current indicating usb-cable and checking if they really do what they say and are not just mocking.
You can make the system think it is not loading th battery using
adb shell dumpsys battery unplug
Refer to this good article :
https://stanfy.com/blog/android-shell-part-1-mocking-battery-status/
Try this for rooted device:
To enable battery Charging:
adb shell dumpsys battery set ac 1
adb shell dumpsys battery set usb 1
adb shell dumpsys battery set wireless 1
To disable battery Charging:
adb shell dumpsys battery set ac 0
adb shell dumpsys battery set usb 0
adb shell dumpsys battery set wireless 0
Probably it can be done via (root privileges):
/sys/devices/battery.XX/power_supply/battery/hv_charger_set
0 - Disable USB Charging
1 - Enable USB Charging
if android os version is more than 6 use unplug and reset to revert back.
adb shell dumpsys battery unplug
adb shell dumpsys battery reset
Copied from perfetto.dev
On rooted phones the power management IC driver allows to disconnect the USB charging while keeping the USB data link active. This feature is SoC-specific, is undocumented and not exposed through any HAL. For instance on a Pixel 2 this can be achieved running, as root: echo 1 > /sys/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-02/800f000.qcom,spmi:qcom,pmi8998#2:qcom,qpnp-smb2/power_supply/battery/input_suspend. Note that in most devices the kernel USB driver holds a wakelock to keep the USB data link active, so the device will never fully suspend even when turning the screen off.
I need to unlock my screen using adb, and wait-for-device exits way too early(when the device is booting up), and screen unlock fails. Is there a way to detect that the home screen, so I can fire screen unlock then?
This is the command I am using to unlock screen -
adb wait-for-device shell input keyevent 82
I send debug commands via adb in windows to my rooted android device.
command is in a loop:
adb shell input tap 200 200
but it seems there is a second or fewer delay in each command to run in device.
is there any way to send commands on device without delay or decrease it?
Note: I used tasker and result was same as adb in windows.
There is no delay "between" the commands. It just takes about a second (depending on the device) to run the input command.