I have a rooted device, and I noticed that the am command in adb cannot perform all its tasks since it does NOT have "signature" permission.
How do you suppose that happens?......... I noticed this behavior on other devices as well (rooted and non rooted)
On an emulator Am.jar seems to have this permission.
Is there any way I can modify the Am.jar (or the app_process that runs it) so that it would have the same signature as the systems'.
As I mentioned, my device is also rooted.
Thanks
Turns out, as @Chris mentioned, that the problem isn't signing permissions.
When running Am on the emulator it runs as a system process. On devices it doesn't.
If I run this command as root then all permissions are granted (even signature).