Trying to execute procrank from cmd promt, but not working - android

I'm trying to get memory info which is allocated by my specific application using "adb shell procrank".
But when i'm trying to execute the procrank command from cmd promt its giving me error like "/system/bin/sh: procrank: not found".
I cant guess what it means!
Thanks in advance.


Procrank is not installed on all devices, you will have to use the following command: "adb shell dumpsys meminfo", it won't give you the memory usage per app, but its an alternative.

Related

How to Disable FRP using ADB Sideload?

my issue is pretty much in the title.
I have been trying to remove the FRP of a samsung Flip 3.
I set up ADB, downloaded the CLI tools with the right version. (I am not using Android Studio)
Can anyone help
Thank you in advance :))
When I try to execute any command in the ADB CLI it returns error: closed .
This happened when I tried to execute these commands:
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
adb shell content insert --uri content://settings/secure --bind
It happens with pretty much every command that I tried. I think it's due to the "sideload" mode of the phone when I execute adb devices .
I overall need any way of removing the FRP, maybe my best shot would be if I could enable USB Debugging from the recovery screen.

nohangup using ADB shell

I am trying to do a logcat to a file using adb shell by following command -
adb shell "nohup logcat -f /storage/sdcard0/myLog.txt -v time &"
If I do a ps | grep logcat, I don't see the logcat command. Even I tried to see nohup command, but it is not there. So somehow above command does not work.
However if I perform the command in 2 steps it works fine -
adb shell
nohup logcat -f /storage/sdcard0/myLog.txt -v time &
I can see the process using ps and logcat continues to record to the file even if I disconnect adb shell. Now I would like the first command to work, since I am using python scripts to issue commands via ADB. It is possible to change the python scripts, however I would like to know if I am doing anything wrong in issuing the first command and if it is possible to make it work.

try
adb logcat
not
adb shell logcat

How to get ADB logs using eggPlant automation tool

Can anyone tell me how can we get adb logs using eggPlant automation tool.Actually i want to have adb logs for my device when running eggPlant scripts.
Please help me out in this situation.

Actually, the previous answer is incorrect as adb command support does exist in eggPlant. There are ways to get adb logs in eggPlant. Here's how:
adb logcat is the command that enables getting adb logs. (Warning: This will print a ton of info!)
You need a way to execute adb logcat within eggPlant. This is accomplished using the shell command
On some systems (I am using eggPlant for Windows) you need to dump the output of the shell command to a file and then read the file back into a variable.

I guess there is no such command or something else.eggPlant identifies only object or script to execute the command.

How can I crash/kill a running app

I would like to crash my Android app by using command-line ADB tool during my app is running, is it possible to do? and how ?
(Basically, I want to test if my app persist the necessary informations when it is crashed. So, I would like to demo this by crash my app by some command-line tool, like ADB.)
***** Update ********
In other words, how to kill my app process by using ADB tool?

kill probably won't work.
adb shell am force-stop <your.app.package>

adb shell kill <PID>
Try the below command in abd shell.

You can kill your app from the shell:
adb -s YOURDEVICEID shell
top // find your app pid
kill -p YOUR_APP_PID

I can easily kill my app from Eclipse DDMS. Just stop the process , e.g. stop "com.my.app"

You can actually trigger a crash via the "crash" param to adb shell am
adb shell am crash <package name>
This is an obscure option but can be confirmed when emulator is running via: adb shell am help
Details: reference
crash [--user <USER_ID>] <PACKAGE|PID>
Induce a VM crash in the specified package or process
Wish this was easier to find I cannot find the original source where I found it but should be more obviously listed on docs page vs only shown when connected am help menu...
https://developer.android.com/studio/command-line/adb#am

App crashing at runtime is nothing but an Occurance of Exception, The place after which you want to crash your app, write a logic which causes for an Exception.

The best way to crash your app is to add an Exception to your package.
Like division by 0 - add it to your app code.

I don't know if you've got the answer yet. The answer is pretty much the same as #bas but instead of using , you need to you the package name
adb shell am force-stop <package name>
you can get the package name by using this command
adb shell pm list package -3
-3 means all 3rd party apps that are installed in device.

Android Native Heap Inspection DDMS

I'm having trouble getting the native heap information from my HTC
Magic running Android 2.2.1.
I've configured the standalone DDMS setting "native=true" and used the
commands:
adb shell setprop libc.debug.malloc 1
adb shell stop
adb shell start
However, when I try to check if the property is set correctly by issueing the command:
adb shell ls
I get the following log message:
"/system/bin/sh: Missing module /system/lib/libc_malloc_debug_leak.so required for malloc debug level 1"
Can someone help me with getting the native heap allocations?
Thanks,
Ove Danner

I'm using this on a Xoom : http://code.google.com/p/honeycomb-sdk-united-base/source/browse/trunk/system/lib/?r=8
Download the raw file using "save as"and then
adb remount
adb push libc_malloc_debug_leak.so /system/lib/libc_malloc_debug_leak.so
You already have root so the adb remount and pushing to /system/lib should work for you.
You can "probably" also build that library by building Android from source. But this was quicker for me.

Categories

Resources