Chainfire/librootjava

JDWP provider `internal` no longer exists on Android 11

Opened this issue · 0 comments

  • Device: Pixel 4 XL (coral)
  • Build: RQ2A.210305.006
  • App: zhanghai/MaterialFiles (debug build with Debugger.setEnabled(true))
  • Logcat:
    2021-03-06 14:21:59.278 31551-32696/me.zhanghai.android.files D/libsuperuser: [libsuperuser][C][SU+] #app_process=/system/bin/app_process64
    2021-03-06 14:21:59.278 31551-32696/me.zhanghai.android.files D/libsuperuser: [libsuperuser][C][SU+] NO_ADDR_COMPAT_LAYOUT_FIXUP=1 ANDROID_ROOT=/system LD_LIBRARY_PATH=/system/lib64:/system/lib64/drm:/system/lib64/hw:/vendor/lib64:/vendor/lib64/camera:/vendor/lib64/egl:/vendor/lib64/hw:/vendor/lib64/rfsa:/vendor/lib64/mediacas:/vendor/lib64/mediadrm:/vendor/lib64/soundfx:/system/bin:/librootjava CLASSPATH=/data/app/~~QsozZAvAA8hDNezkB64NSA==/me.zhanghai.android.files-ZZ6pIkMj1dFgTHtF5WiQEA==/base.apk /system/bin/app_process64 -Xcompiler-option --debuggable -XjdwpProvider:internal -XjdwpOptions:transport=dt_android_adb,suspend=n,server=y /system/bin --nice-name=me.zhanghai.android.files:root me.zhanghai.android.files.provider.root.RootFileService /data/app/~~QsozZAvAA8hDNezkB64NSA==/me.zhanghai.android.files-ZZ6pIkMj1dFgTHtF5WiQEA==/lib/arm64/libsyscalls.so /data/app/~~QsozZAvAA8hDNezkB64NSA==/me.zhanghai.android.files-ZZ6pIkMj1dFgTHtF5WiQEA==/lib/arm64/libselinux-jni.so
    2021-03-06 14:21:59.320 799-799/? D/AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
    2021-03-06 14:21:59.322 799-799/? I/AndroidRuntime: Using default boot image
    2021-03-06 14:21:59.322 799-799/? I/AndroidRuntime: Leaving lock profiling enabled
    2021-03-06 14:21:59.323 799-799/? I/vm-printf: not a valid jdwp provider: internal
    2021-03-06 14:21:59.323 799-799/? I/vm-printf: dalvikvm: [options] class [argument ...]
    2021-03-06 14:21:59.323 799-799/? I/vm-printf: The following standard options are supported:
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -classpath classpath (-cp classpath)
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -Dproperty=value
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -verbose:tag[,tag...] (currently valid tags: 'agents', 'class',
            'collector', 'compiler', 'deopt', 'dex', 'gc', 'heap', 'image',
            'interpreter', 'jdwp', 'jit', 'jni', 'monitor', 'oat', 'profiler',
            'signals', 'simulator', 'startup', 'systrace-locks',
            'third-party-jni', 'threads', 'verifier', 'verifier-debug')
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -showversion
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -help
    2021-03-06 14:21:59.323 799-799/? I/vm-printf:   -agentpath:library_path=options (Experimental feature, requires
            -Xexperimental:agent, some features might not be supported)
    ...
    2021-03-06 14:21:59.323 799-799/? I/AndroidRuntime: VM exiting with result code 1.
    2021-03-06 14:21:59.326 31551-32125/me.zhanghai.android.files D/libsuperuser: [libsuperuser][O][SU-] 39fc2349-84ee-405e-a2c8-1c496e9db0f9-0000000a 1
    2021-03-06 14:21:59.327 31551-32126/me.zhanghai.android.files D/libsuperuser: [libsuperuser][O][SU*] 39fc2349-84ee-405e-a2c8-1c496e9db0f9-0000000a
    

The JDWP provider internal no longer exists after aosp/1216803 and is causing the failure. Could you please take a look?