run-as Package ‘a.b.c’ is unknown – Galaxy S4 Jellybean or Android 4.3

by

Found success by adding this to the activity:

private void startGdbServer() {   
    try {
        new ProcessBuilder()
        .command(getFilesDir().getParent() + "/lib/gdbserver", "tcp:5039", "--attach" ,"" + android.os.Process.myPid())
        .redirectErrorStream(true)
        .start();
    } catch (IOException e) {
        Log.e(TAG, "IOException failed to start gdbserver");
    }
}

Then I wrapped startGdbServer in an Android service and updating the ndk-gdb script to start the server instead of the run-as command.

Here’s the manifest addition:

<service android:enabled="true" android:name="com.apportable.activity.GdbServerService"
    android:label="@string/app_name" android:icon="@drawable/icon">
    <intent-filter >
        <action android:name="apportable.FoundationTests.GdbServerService" />
    </intent-filter>
</service>

Here are the relevant ndk-gdb changes (in python):

    remote_gdbserver="/data/data/" + env['APPLICATION_IDENTIFIER'] + '/lib/gdbserver'

    print "Attaching to pid " + pid
    # Android 4.2 requires the --user 0 option. Earlier versions cannot have it

    results = env.Execute([env['ADB'], 'shell', 'am'])
    if "--user" in results:
        user_option = "--user 0"
    else:
        user_option = ""

    adb.AsyncShell(env, 'am startservice ' + user_option + ' -a ' + env['APPLICATION_IDENTIFIER'] + '.GdbServerService --es gdbserver_name ' + remote_gdbserver + ' --ei gdbserver_port ' + str(env['ANDROID_REMOTE_DEBUG_PORT']))

    # HACK: magic number. ensure the gdb server is actually up and running
    time.sleep(2)  # 1 is usually enough, but not always, like after reboot or with heavy system load

    adb.Forward(env, env['ANDROID_LOCAL_DEBUG_PORT'], env['ANDROID_REMOTE_DEBUG_PORT'])

    adb.Pull(env, process_path, '/system/bin/app_process')

    setup_path=""" + setup_path + '"'

    if env['CGDB'] is not None:
        cmd = [env['CGDB'], '-d', env['GDB'], '--', '-x', setup_path]
    else:
        cmd = [env['GDB'], '-x', setup_path]

    env.RunCommand(cmd)

More Related Contents:

  1. How to get ndk-gdb working on Android?
  2. How to use JNI bitmap operations for helping to avoid OOM when using large images? [closed]
  3. define LOCAL_SRC_FILES in ndk{} DSL
  4. Android 4.3 Bluetooth Low Energy unstable
  5. System.loadLibrary(…) couldn’t find native library in my case
  6. How to make Android apps which support both 32-bit and 64-bit architecture?
  7. Android NDK: dlopen failed
  8. Android NDK linking
  9. Calling native method twice of third party library in an Activity causes the Android application to close down
  10. Using FFmpeg with Android-NDK
  11. Android NDK C++ JNI (no implementation found for native…)
  12. How to find the Android version name programmatically?
  13. How to get the battery level after connect to the BLE device?
  14. Write file to location other than SDcard using Android NDK?
  15. Set Build path in Eclipse for ndk program
  16. How to package native commandline application in apk?
  17. Rotating a bitmap using JNI & NDK
  18. Android OpenGL ES 2.0 emulator
  19. How to compile C into an executable binary file and run it in Android from Android Shell?
  20. Official “Boost library” Support for Android and iOS? [closed]
  21. NDK – How to use a generated .so library in another project
  22. How to access resource with dynamic name in my case?
  23. How to Find memory leaks from native code in android
  24. Why is redirecting stdout/stderr on android not working?
  25. Debugging Android NDK C/C++ code in Eclipse – breakpoints are not hit
  26. After update android studio could not create parent directory for lock file
  27. Why do some Android phones cause our app to throw an java.lang.UnsatisfiedLinkError?
  28. Cross compiling static C hello world for Android using arm-linux-gnueabi-gcc
  29. Power-Off or Restart an android device via Code/Program?
  30. Loading shared libs that depend on other shared libs

Leave a Comment