how do I trigger an Android Intent from outside Alien-Dalvik?

asked 2014-04-12 02:45:25 +0200

dsilveira
7805 ●77 ●110 ●101

updated 2015-02-18 05:23:26 +0200

foss4ever
13056 ●97 ●134 ●141

Can someone give me some pointers on how to go about doing this?

I tried the solution from the selected answer from this: http://stackoverflow.com/questions/4567904/how-to-start-an-application-using-android-adb-tools

but it didn't work, it kept saying: /opt/alien/system/bin/am: line 6: exec: app_process: not found

Anyone have any clue?

EDIT 1:

this is what's in /opt/alien/system/bin/am:

# Script to start "am" on the device, which has a very rudimentary
# shell.
#
base=$ANDROID_ROOT
export CLASSPATH=$base/framework/am.jar
exec app_process $base/bin com.android.commands.am.Am "$@"

This is the command I used (I know it's just a start intent, no action flag to trigger the intent, but before this works, the action won't either):

(I have aptoide v5 installed, and this same command (without the full path) works on an android that I got with the same version of aptoide installed)

/opt/alien/system/bin/am start -n cm.aptoide.pt/cm.aptoide.pt.Start

EDIT 2:

thanks to @tingo, I got a little bit further, by modifying the am script adding the full path to app_process, so am looks like this now: this is what's in /opt/alien/system/bin/am:

# Script to start "am" on the device, which has a very rudimentary
# shell.
#
base=$ANDROID_ROOT
export CLASSPATH=$base/framework/am.jar
exec /opt/alien/system/bin/app_process $base/bin com.android.commands.am.Am "$@"

The thing is that now it does not start the Aptoide (like it did on Android), but instead, returns Segmentation Fault on the console, and that's it.

Any thoughts?

I feel I'm getting closer, but still, just, can't reach my goal :P