I have an Android(7) phone [also fine if you can provide a solution for Android 10] and a Linux pc. By enabling USB debugging and using the terminal of my pc, I am able to read the notifications of my phone using the command:

shell dumpsys notification --noredact

Now, there are some notifications in Android in which we can interact with the app directly from the notification. For example, in a WhatsApp notification, there are usually two buttons: *Reply* & *Mark as read*. On YouTube, there are options like *Play, Turn off, Watch later*. In the output of the above command, these options are visible in the following form:

actions={
         "Reply" -> PendingIntent{6becf48: PendingIntentRecord{87b8050 com.whatsapp startService (whitelist: +30s0ms)}}
         "Mark as read" -> PendingIntent{c1661e1: PendingIntentRecord{b8e3249 com.whatsapp startService (whitelist: +30s0ms)}}
      }

I have two questions: 1. Can we interact with these options from adb shell? For example, is there any command like

shell  'Message to be sent in WhatsApp with reply option'

which will send the text as a reply in WhatsApp without opening the app? 2. Is it possible to swipe the notifications using any ADB command? (Not the

shell input swipe x0 y0 x1 y1

, it requires to unlock the phone each time) Thank you in advance! **Edit:** Here is what I found that may be relevant to this question. I think that I have to somehow launch the specific intent linked to the mentioned PendingIntent id (in this case

or

) Using the command

shell dumpsys activity intents > output.txt

and then searching for

in

.txt

, I found the name of the intent. It was as follows:

* PendingIntentRecord{87b8050 com.whatsapp startService (whitelist: +30s0ms)}
    uid=10104 packageName=com.whatsapp type=startService flags=0x0
    requestIntent=act=com.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE dat=content://com.whatsapp.provider.contact/contacts/2256 cmp=com.whatsapp/.notification.DirectReplyService (has extras)
    whitelistDuration=+30s0ms

Now I think that it may be possible to launch the intent

.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE

using

shell am

command, and passing the intent id and message as some parameters. (Just like we can launch WhatsApp from adb with

command, it should be possible to launch the pendingIntent also.) **Edit 2:** Using this command:

adb shell am startservice -a com.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE -d content://com.whatsapp.provider.contact/contacts/2256 -n com.whatsapp/.notification.DirectReplyService --es 'com.whatsapp.Intent.EXTRA_TEXT' 'Hi. Okay.'

The output was as follows:

Starting service: Intent { act=com.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE dat=content://com.whatsapp.provider.contact/contacts/2256 cmp=com.whatsapp/.notification.DirectReplyService (has extras) }
Error: Requires permission not exported from uid 10104

I'm trying to use my phone less. I've managed successfully to remove apps via adb. My question is if it's possible to have apps disable/remove via their package names over adb, and then reinstated on the device at certain times of the day. So for say the hours 9am to 5pm Chrome app would be completely removed and not on the device, then after 5 it's there again. I'm not wanting app timers or the app being disabled but app icon still visible. I'm after the full removal followed later in the day by it's full revival. Thanks :)

I am using Lineageos 17.1 on the FP3 (the phone is not rooted). I do know my screen pattern code (it is a 6x6 pattern), but I am not able to enter it correctly, because I disabled that the pattern is shown and that the sequence is visible. In the recovery mode I can enable adb and I tried to delete the file adb shell rm /data/system/gesture.key which worked in the past, but now this file does not exist anymore on Lineageos 17.1. ADB unfortunately does not work when the screen is locked. Is there another way to bypass the screen pattern? Doing a factory reset is the last option I want to do. Making the pattern visible should be enough in principle.

I've tried everything I could find on the internet (mostly on *StackOverflow*). These I've already tried without result: 1. [*Page not found - Stack Overflow*](https://stackoverflow.com/questions/51082608/is-it-possible-to-authorize-adb-on-my-android-phone-with-a-broken-screen) 2. [shell - How to solve ADB device unauthorized in Android ADB host device? - Stack Overflow](https://stackoverflow.com/questions/26213954/how-to-solve-adb-device-unauthorized-in-android-adb-host-device) 3. [android - running adb devices showing unauthorized device? - Stack Overflow](https://stackoverflow.com/questions/25236960/running-adb-devices-showing-unauthorized-device) **Both screen AND touch are broken so I can't see nor touch a thing.** (So the OTG mouse option can't be used in my case.) The device is a *Huawei Ascend P7 L10, Lollipop 5.1.1.* - It's rooted. - It has TWRP recovery. - USB Debugging is enabled. - I'm using the latest ADB version, updated from Android Studio. I entered recovery mode, done adb push adbkey.pub /data/misc/adb/adb_keys and rebooted, after reboot adb keeps saying devices isn't authorized. I entered recovery checked if the file copied on the device was still the same as the one in the *.android* folder, and it was the same key. If anybody has any idea I'm all ears. Thanks in advance.

I had a Sony Xperia z5 compact for about 2 weeks until I smashed the screen. I have searched online to find some help to recover my photos and videos taken with the device. I didn't have any cloud set up so I cant get them from there. OTG cable has to be turned on EVERY TIME from the settings on the Z5, it seems the Z3 was plug and play good to go OTG, but not the Z5. The screen is unresponsive and barely visible and it has a passcode lock (as fingerprint function is locked, and wont reset after a soft reset). I have until the end of the week to return the phone to my carrier and would like to get the data from it before i send it back. I have no knowledge of scripting ADB or how i can activate usb debugging with a damaged screen. Is there a script I can download as a zip and paste to the root of an external SD card which can transfer or duplicate the files from the internal to external storage? or a zip that can activate usb debugging?

My phone is currently stuck in a boot loop. I tried using minimal adb and fastboot but I can't seem to do it. I have also read in some forums that usb debugging should be enabled and the phone should be rooted. Is there a way to use adb commands without enabling the usb debugging('coz I can't). I tried all the choices in the recovery mode except the factory reset. Can somebody help me? I really need to recover the memos that I have saved. I have a Samsung galaxy V duos.

## The issue I needed to push a folder to my phone and I just ran the following command which always worked fine:

adb push ~/some_folder sdcard/some_folder

For some reason however it just didn't respond and stayed quiet in the terminal. After a while my system started lagging, then I looked at the RAM usage and was shocked when saw that 30GB of RAM was allocated. After looking back at the terminal, it also showed >Exception occured ... std::bad_alloc. It also didn't respond to my Ctrl+C, so I crashed the terminal which freed the memory. To make the final test I ran the following two commands to exclude the possibility of folder being to large

mkdir test
adb push ~/test sdcard/

Yet the result were the same. ## Pc Info 1. OS: Arch Linux 6.16.3-arch1-1 2. ADB: comes from package android-tools-35.0.2-17 from arch linux repository. ## Phone Info 1. Make: Xiaomi 2. Model: POCO X6 Pro 5G 3. Android version: 15 AP3A.240905.015.A2 ## Some additional info 1. Never experienced something like this before, Always was fine with pushing/pulling any file, including folders. 2. My adb also sometimes just freezes without responding (but without any else negative effect i listed above) on pushing regular files, but reconnecting the USB helps (for folders it doesn't) Anyone else experienced the same issue? Would be glad for any help!

**TL;DR:** On-device, we can navigate to *Settings › Apps,* and for each app separately can call up details on storage used: by the app itself, by its data, by its cache. Is it possible to obtain those details from the command line, ideally via ADB – and ***without having root access?*** **In detail:** I've already searched the web, but found no information on this. I've already tried walking the package list (pm list packages), obtaining the path to the APK file (adb shell pm path $pkgname | awk -F':' '{print $2}'), and getting the file size of that (adb shell stat $path | grep Size) – but that has a series of disadvantages: * it only gives me the size of the APK (for updated system apps, only of the latest update) * even if scripted, it takes ~2s per app to obtain even that. As today's devices already ship with far more than 100 system apps, it would take "ages" even if only a few user apps were installed (almost 6 minutes on an almost virgin Wiko Sunny 3 where I just tried that) * details on data and cache are completely missing Ideally, Android has already somewhere collected those details; it doesn't take that long via the GUI. Maybe there's some database one could query ***without having root privileges*** – or some XML to parse, or some shell command I missed? **PS:** if you know about a root-only solution, that'd be "better than nothing". Please indicate that in a comment then so I can come back and ask you to make that an answer if there are no non-root solutions.

I accidentally removed /system/bin/toolbox on my Android 5.1.1 tablet. Right now I have temporarily replaced it by a busybox binary I had at hand, so the system is somewhat usable but not completely functional (e.g. no network connection). I have tried to pull the toolbox binary from other devices I have, but those are either Android 4 or Android 6, so it didn't work due to unresolved linker symbols. Is there a place where I can get a binary for a specific Android version? Or is there a place on my device where a backup is kept?

My Pixel 8 recently stopped displaying anything, And the touchscreen has stopped working. I've thus been using ScrCpy to recover data(I have my computer set as always authorized), However, Upon restart, I've discovered I'm unable to enter my pattern through ScrCpy. I attempted to use ADB locksettings clear to regain access, However, Upon use, My phone vibrated for a long period of time, And will no longer connect to ADB. Has ADB activated a security feature I was unaware of? Is there any way to regain access? My phone is on a google account I have access to, If that's needed.

Many Android device manufacturers have their own custom skins | Brand | Shell (Skins) | | -------------------------------- | ------------------------------- | | Xiaomi | MIUI, from October 2023 HyperOS | | Huawei | EMUI (Emotion UI) | | Honor | MagicOS | | Oppo | ColorOS | | OnePlus | OxygenOS | | Realme | Realme UI | | Samsung | One UI | | Tecno | HiOS | | Infinix | XOS | | HTC | HTC Sense | | Meizu | Flyme | | Google, Motorola, Sony and Nokia | Pure Android (AOSP) | Is it possible to get this information via adb? I tried adb shell getprop, but I don't see anything that indicates it yet, I have the One UI shell because I have a Samsung Galaxy A14 smartphone connected.

My phone is an unrooted Samsung Galaxy S7 Edge running Oreo 8.0. Yesterday when removing bloatware from my phone, I accidentally uninstalled a system app using the adb command: pm uninstall -k --user 0 I suspect the culprit to be com.sec.factory.camera, as since that unfortunate event, the camera app crashes every time I try to launch it. I tried reinstalling it using either of these two commands pm install com.sec.factory.camera pm install --user 0 com.sec.factory.camera but they returned a "can't open non-file" error message. I tried as well downloading the APK on my phone and installing it from Android, but at the end of the installation process, I got a "not installed application" message. How to reinstall an uninstalled system app through ADB?

I've been playing with some ADB settings put commands on one of my WearOS watches (Galaxy Watch 7, WearOS 5, OneUI 6), to customize things a bit beyond what the settings app usually allows, and I've come across an odd issue: I wear my watches on the inside of my wrist and prefer them oriented vertically (90° from stock setting, WearOS's "landscape" orientation internally). I have been able to use ADB to rotate the whole system to this 90° angle, and it's great. However, when the ambient mode for Always On Display kicks in, while the rotation is preserved for a moment when the screen first dims, after about two seconds, the AOD ambient screen returns to stock 0° ("portrait") orientation. As soon as I tap the screen to wake the device from ambient mode, the rotation returns to 90°, and gestures (swipe up for app tray, down for QS, etc.) are all oriented to that 90° rotation even when the screen is in ambient mode. I know it is not the watch face itself, because I have tried multiple and they all do this, but the issue is not present when using the stock 180° rotation mode (it will not flip back to 0° when ambient). While reading about the issue, I found some people discussing performing a similar trick on WearOS 3, and they stated the AOD/ambient mode *stayed* rotated at 90°... I am not sure if this is something specific to Samsung OneUI versions of WearOS, so I did a little digging with adb shell pm list packages and it seems like Samsung's implementation of AOD/ambient is named com.samsung.android.watch.watchface.perpetual. <-- This was a watch face, disregard. The AOD/Ambient service is still being provided by the AmbientLifecycleObserver on Samsung devices. Is anyone aware of what might be causing this glitch, or does anyone by chance know of a way (ADB or otherwise) to force an individual-specific app to a particular orientation so I can try resolving this? If native methods won't work, does anyone have any thoughts about the potential to mod this APK to change its default orientation in its properties?

> adb shell sh-4.1$ su Permission denied I have rooted my phone successfully. I know this because I'm able to install apps on SD card and I have a program called SD Maid that is able to operate with root permissions.

There is a .xapk file in APKPure and here is the corresponding app on Play Store . I can install it using Play Store. But other approaches of installing this app fail (SAI_v4.5 and other installers), and about 20MB (the size of the .xapk file) is lost after installation failure. I got the error > INSTALL_FAILED_ABORTED: User rejected permissions when installing split APKs (.xapk) on my Oppo Reno4 SE 5G running Android 12. # example commands to install split apks pm install-create pm install-write 18911812 base.apk /data/local/tmp/base.apk pm install-write 18911812 split_1.apk /data/local/tmp/split_1.apk pm install-write 18911812 split_1.apk /data/local/tmp/split_1.apk pm install-commit I tried to install it using ADB, and although pm install-commit returns with a Success message, the app is not fully installed. When using ADB, "Verify app over USB" is turned off. I noticed this error when installing split APKs using a custom app installer from storage. But now I found this error also occurs when installing a normal .apk file (I didn't notice this because I am using Android's default package installer). However, .apk could be installed successfully (at least it seems like it). How to solve this?

I have tried to access the voice command on the Talkback menu. I have tried to use adb/fastboot. All o no avail Outlast 5g

Looking for an ADB copypasta to jack my bluetooth call audio all the way up to maximum on my Galaxy ao2s. Android 12. When my media audio is high enough to cave in my head, I can barely hear my calls. All the settings are stock and all the way up, recent factory data reset. Samsung techsupport, of course, had "limited success" is helping me. I've gone through every setting in the UI and the developer options to no avail. The odd thing is that the call volume is perfectly adequate over speaker or without a headset, but plug in a BT headset - ANY BT headset - and the problem resurfaces. Crystal clear media, straining to hear my son who can help lost ships find their way to shore.

Within location services on Android 13 devices, there are several services such as Google Location Accuracy. [](https://i.sstatic.net/mURlQ.png) I have taken a snapshot of secure, global and system settings before and after enabling this setting, but there is no change, which leads me to believe that we can't change it via settings. I have tried the solutions mentioned here https://android.stackexchange.com/questions/40147/enable-location-services-via-adb-or-shell But these just seem to affect the location setting and not Google Location Accuracy. Is there a way from ADB to enable/disable this?

It happened when Google Play was automatically updating apps. I guess, something went wrong and the phone suddenly restarted and was not able to turn on again. It always gets stuck on "Starting apps" screen and then restarts again (bootloop). I figured out, that if I can delete the app causing bootloop it should be just fine. However, I don't know how I could do it.

My phone is nexus 4 running Android Marshmallow. Also, I have a custom recovery (cwm 6.0.4.7). So, I tried to connect through adb to the phone in recovery mode and delete the app, however, I can't use any adb command, because "device unauthorized". I assume, as soon as I can get access through adb, I can delete the app.

After surfing many forums for the past several hours I couldn't able to find any solution which preserves data the phone has. Any ideas how I can delete/fix the app without loosing any data? (nexus 4 doesn't have SD card slot). Thanks. P.S. wipe cache partition didn't help.

The menu appears to have been hidden on the more recent Android releases — currently on Android 14 the only per-app toggle the users are given is 'allow background usage' (app info → app battery usage). On my Oneplus 8T device the OS is actively stopping some apps designed to be running on the background at all times, such as Shizuku . On AOSP-based ROMs three settings used to be available for each app, the most permissive being 'unrestricted'. SystemUI Tuner didn't expose the menu. --- Using ADB is an acceptable answer as well.