rikkaapps / shizuku Goto Github PK

View Code? Open in Web Editor NEW

8.4K 8.4K 489.0 38.07 MB

Using system APIs directly with adb/root privileges from normal apps through a Java process started with app_process.

License: Apache License 2.0

Java 32.16% CMake 0.53% C 0.42% Shell 0.66% C++ 9.42% Kotlin 56.81%

shizuku's People

Contributors

Stargazers

Watchers

Forkers

ryanfu haruue vaginessa haozi5205 livecso scatiger arhamdan heruoxin snowyferret xdk168 leonzhouh vu1seek gyyfifafans lihenggui tsdl2018 starrom xdcs100 prife rucamedia chuyuanlinzi xyz12810 michaellee2019 morphemic420 eagle518 ljxinternet eligiant kr328 republicsong neoblackxt malow005 knbs1 themaximumjuandchavezprop anang2019 wojtek8668 dstmath crackercat yy540a shuaiyinoo learder freemanzyq liu1352183717 whitemike889 lukumavs mbobo24 colorpenboy littleboybiggun chenjiancheng hoking007 cylee0909 furkorn60 wasif1122 fenglimima mac4androidx bitcloudson d4rken niuwadiandian lfyg goofwear ledudu lgslegend zhangshu345 anysou 019369 xinruonicole pinro3 xiangyutian demonxjj fahmyhamzan emrah2435 xfxphil adavenport27 pangaoxin oseas22 ricardo816 valbracamonte2-gmail-com surfndez netstu faiiev libertycost 992939 alejagapatrick kloida httpsgithu yhtsnda torywilson87 unjaster jackevill sx5486510 brandycooklyn topys001 willyt103 tek-god tchigher rockystevejobs geekhuyang qinlicang charlottefallices forksource tiger7456 abalam1980

shizuku's Issues

pm disable之后的应用无法通过shizuku调用package service启用

您好，最近开发一款冻结类APP，支持root与shizuku冻结应用，发现当应用被通过pm disable停用后，通过shizuku远程调用package service操作应用都会失败，代码如下

fun disableApp(pkgName:String):Boolean{
            val data=SystemServiceHelper.obtainParcel("package","android.content.pm.IPackageManager","setApplicationEnabledSetting")
            val reply=Parcel.obtain()
            data.writeString(pkgName)
            data.writeInt(3)
            try{
                ShizukuService.transactRemote(data,reply,0)
                reply.readException()
            }catch (e:Exception){
                Log.e("Shizuku",e.toString())
                return false
            }finally {
                data.recycle()
                reply.recycle()
            }
            return true
        }

他在正常情况工作良好，root模式使用了命令行的service指令去远程调用该服务，同样工作良好。但是当应用被pm disable一次之后，shizuku调用时会出现以下错误：

java.lang.SecurityException: Shell cannot change component state for com.coolapk.market/null to 3

报错信息与shell下未获取root权限时执行调用指令相类似：

$ pm disable com.coolapk.market
Security exception: Shell cannot change component state for com.coolapk.market/null to 2

即使应用被pm disable，root模式下通过命令行service指令调用同样的远程调用是可以继续修改应用停用状态的。但通过shizuku会出现错误。
安卓7的模拟器与安卓9的实体机同样出现了这个问题。
这个问题不影响程序主要执行流程，但比较好奇产生原因，希望作者能够解答，十分感激！

Android 11 adb 启动失败

Pixel2 rpp1.200123.016
shizuku 3.5.0.r323.f399ca4

info: start.sh begin
info: source dex path is /storage/emulated/0/Android/data/moe.shizuku.privileged.api/files/server-v6.dex
info: dex path is /data/local/tmp/shizuku/server-v6.dex
info: starter begin
info: killing old process...
info: killed 7259 (shizuku_server)
info: starting server v3...
info: process forked, pid=16089
info: checking shizuku_server start...
info: checking shizuku_server stability...
info: checking shizuku_server stability...
info: checking shizuku_server stability...
info: shizuku_server started.
--- crash start ---
[command] logcat -b crash -t '02-21 11:52:44.000' -d
--- crash end ---
--- shizuku start ---
[command] logcat -b main -t '02-21 11:52:44.000' -d -s ShizukuServer ShizukuServerV3 ShizukuManager
--------- beginning of main
02-21 11:52:45.916 16090 16090 I ShizukuServerV3: server v3
02-21 11:52:45.916 16090 16090 I ShizukuServerV3: using token from arg
02-21 11:52:46.051 16090 16103 D ShizukuServerV3: onUidActive: uid=10196
02-21 11:52:46.052 16090 16103 D ShizukuServerV3: onActive: uid=10196, packages=rikka.appops
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: failed send binder to user app rikka.appops in user 0
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: java.lang.NoSuchMethodError: android.content.IContentProvider#call
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.v.a(Unknown Source:55)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.q.h(:10)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.n.a(:11)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.n$c.onUidActive(:2)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at android.app.IUidObserver$Stub.onTransact(IUidObserver.java:155)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.c.onTransact(Unknown Source:0)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at android.os.Binder.execTransactInternal(Binder.java:1126)
02-21 11:52:46.069 16090 16103 E ShizukuServerV3: 	at android.os.Binder.execTransact(Binder.java:1090)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: failed send binder to user app rikka.appops in user 0
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: java.lang.NoSuchMethodError: android.content.IContentProvider#call
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.v.a(Unknown Source:55)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.h(:10)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.g(Unknown Source:41)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.d(:1)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.m.run(Unknown Source:2)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at android.os.Handler.handleCallback(Handler.java:907)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at android.os.Handler.dispatchMessage(Handler.java:99)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at android.os.Looper.loop(Looper.java:216)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.e(:2)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.Starter.main(:7)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
02-21 11:52:46.069 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:396)
02-21 11:52:46.077 16090 16090 E ShizukuServerV3: provider is null cn.wq.myandroidtools.shizuku 0
02-21 11:52:46.106 16090 16103 D ShizukuServerV3: onProcessDied: pid=14079, uid=10064
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: failed send binder to user app com.catchingnow.icebox in user 0
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: java.lang.NoSuchMethodError: android.content.IContentProvider#call
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.v.a(Unknown Source:55)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.h(:10)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.g(Unknown Source:41)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.d(:1)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.m.run(Unknown Source:2)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at android.os.Handler.handleCallback(Handler.java:907)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at android.os.Handler.dispatchMessage(Handler.java:99)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at android.os.Looper.loop(Looper.java:216)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.e(:2)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.Starter.main(:7)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
02-21 11:52:46.403 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:396)
02-21 11:52:46.469 16090 16103 D ShizukuServerV3: onUidActive: uid=10222
02-21 11:52:46.470 16090 16103 D ShizukuServerV3: onActive: uid=10222, packages=moe.shizuku.privileged.api
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: failed send binder to user app moe.shizuku.privileged.api in user 0
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: java.lang.NoSuchMethodError: android.content.IContentProvider#call
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.v.a(Unknown Source:55)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.q.h(:10)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.n.a(:9)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.n$c.onUidActive(:2)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at android.app.IUidObserver$Stub.onTransact(IUidObserver.java:155)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at moe.shizuku.server.c.onTransact(Unknown Source:0)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at android.os.Binder.execTransactInternal(Binder.java:1126)
02-21 11:52:46.509 16090 16103 E ShizukuServerV3: 	at android.os.Binder.execTransact(Binder.java:1090)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: failed send binder to user app moe.shizuku.privileged.api in user 0
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: java.lang.NoSuchMethodError: android.content.IContentProvider#call
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.v.a(Unknown Source:55)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.h(:10)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.d(:3)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.m.run(Unknown Source:2)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at android.os.Handler.handleCallback(Handler.java:907)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at android.os.Handler.dispatchMessage(Handler.java:99)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at android.os.Looper.loop(Looper.java:216)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.q.e(:2)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at moe.shizuku.server.Starter.main(:7)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
02-21 11:52:46.509 16090 16090 E ShizukuServerV3: 	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:396)
02-21 11:52:46.526 16090 16103 D ShizukuServerV3: onProcessDied: pid=15365, uid=1110133
02-21 11:52:46.526 16090 16103 D ShizukuServerV3: onProcessDied: pid=15094, uid=1110115
02-21 11:52:46.546 16090 16247 D ShizukuServerV3: onProcessDied: pid=12643, uid=1110120
02-21 11:52:47.254 16090 16247 D ShizukuServerV3: onProcessDied: pid=12398, uid=10173
02-21 11:52:47.280 16090 16247 D ShizukuServerV3: onProcessDied: pid=15479, uid=10148
--- shizuku end ---
info: shizuku_starter exit with 0

Shizuko Manager Tasker Task

Start shizuku server with tasker task
Runs command:adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh

Useful for fire tv/android tv

Requires adb debugging enabled
No other device required than
fire tv supports it

Requires tasker app
https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm
Requires ADB Shell [Tasker] Plugin
https://play.google.com/store/apps/details?id=com.ADBPlugin

Shizuku Manager Tasker Task
Import in tasker app
Than start the task
https://mega.nz/#!KSxFCK4I!10jEs6Qy-RQMo9qxu4g37N5m-qSPLLvVH_4irTqxGu4

Legacy not working

Cant tap

Huawei mate20 Pro android 10 kind regards

Is it possible to add device owner mode?

I think it would be more appropriate to set up the device owner directly to solve the problem permanently if other software can be licensed.

This could be an option if it works in principle.

Shizuku V3 doesn't work on Android Pie, but on Lollipop

Sorry for penetrating your inbox first.

This is an older issue I had with Shizuku. I sometimes try it on a Lollipop and sometimes on a Pie phone. I thought the issue was fixed because it worked on L after adding MultiProcessHelper.initialize(main), but I will get the same exception as the one in the original issue if I try to run a shell Command on Pie. I get this exception when I try to invoke transactRemote.

sony xperia xzp问题

您好，
我是美版xzp，8.0系统，未root，每次运行adb命令后，shizuku manager显示server已经正常运行，但是每次一拔下usb线，server就没了，请问这是正常吗？
谢谢。

Installing app via Shizuku not possible?

I try to install an apk via Shizuku.
ShizukuPackageManagerV27.installPackageAsUser throws an ShizukuRemoteException: No interface method installPackageAsUser. ShizukuPackageManagerV27.getPackageInstaller() returns an IPackageInstaller which isn't recogniced by my ide. Reflection doesn't work also.

So what are the intended uses of the methods ShizukuPackageManagerV27.getPackageInstaller, ShizukuPackageManagerV27.installPackageAsUser?
And how can I get the Interfaces working?

[request] kitkat support

Rikka，可不可以使用网络adb调试开启shizuku服务呢

这样就可以不输入命令了

拔开usb后adb即刻失效

三星S10, 更新系统至补丁日期9月1日，成功使用Adb后拔开usb后过一会无效或息屏后再点亮屏幕即刻无效，无法在仅充电时使用usb调试模式

使用需要传 IBinder 的 API NPE

Parcel 无法传递 Binder，看 Server 里面是直接从 Parcel read 出来的，然后就是 null，再传给系统 API，之后就 NPE 了。建议对于传给 Shizuku Binder 这类情况直接在 Shizuku Server new 出来一个 Binder 即可。

Support system plugin mode

AppOps supports System plugin as a Working Mode, which can be installed with root privilege or flashing. But Shizuku Manager is not supporting this. I want to use this feature because I will be able to run shizuku server anytime without root permission if Shizuku supports this.

Crash after restart service (in root mode)

XiaoMi 6
MIUI 9 Stable 9.6.3 (Android Oreo)
Allowed root permission in magisk.

It happened after some recent updates (It worked fine before).

在已经ROOT的设备上，能不能设置成自动启动shizuku server？

执行start.sh 后出现提示Permission denied

设备：小米 MIX2S

系统： MIUI 10 9.7.11 开发版安卓版本 9 安全补丁程序级别：2019-06-1

电脑上的 ADB 版本：Android Debug Bridge version 1.0.41 Version 29.0.1-5644136

运行 Shizuku 启动命令时，终端的输出:
PS C:\Users\NamelessMidNight> adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh

info: start.sh begin chcon: '/data/local/tmp/shizuku_starter' to u:object_r:shell_data_file:s0: Permission denied fatal: can't access null, please open Shizuku Manager and try again. info: shizuku_starter exit with non-zero value 1

请问是不是因为小米对系统的自定义将部分机制破坏了所以没用办法使用也做不到修复？先谢谢了

Add portable GUI client for PC (use WebUSB?)

It'd be nice n easy to have a PC GUI client.

关于 ShizukuService#newProcess deprecated 的疑问

今天看到 API 4.0.0 中将 ShizukuService#newProcess 方法标记为 depreacted，并推荐使用 binder 交互。但是我的应用需要使用 adb am 指令而并非 pm 指令，可以用 binder 拿到 ActivityManager 吗？

Linux adb 开启问题

在 Linux 下使用 transfer data 模式连接手机，执行命令，启动 server 后，拔掉数据线，服务停止。（在 Linux 下连接手机无法使用 charge only 模式调试）

尝试使用

adb tcpip 5555

也没有效果

The problem of using the Shizuku

Samsung note 9
magisk
MiPushFramework伪装小米

Shizuku 安装器错误:

设备: Xiaomi SM-N9600 | MIUI | Android 8.1.0 | Install Lion-Root 2.91

java.lang.RuntimeException: Command: pm install-write -S 2702065 93877727 0.apk
Exit code: -1
Out:

=============
Err:

<!> SAI ShizukuShell Java exception: java.lang.RuntimeException: java.lang.RuntimeException: android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died
at b.c.a.c.d.b.a(:9)
at b.c.a.c.c.d.a(:26)
at b.c.a.c.c.a.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.RuntimeException: android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died
at d.a.a.a.getOutputStream(Unknown Source:17)
at b.c.a.c.d.b.a(:7)
... 5 more
Caused by: android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:777)
at d.a.b.a$a$a.e(Unknown Source:17)
at d.a.a.a.getOutputStream(Unknown Source:6)
... 6 more

at b.c.a.c.c.d.a(:27)
at b.c.a.c.c.a.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

[咨询]您好，我想请教一个问题

就是如何使用 Tasker 直接启动 Shizuku Server？
目前我的想法是用“发送意图”（中文翻译，我不知道英文原文是什么）来调起，但是我需要一个 Activity，操作类型和 Data（若有），如果可以的话请您告知，烦请回复~
EDIT: 举个例子，这是调起特定 APP 的应用管理页面的 intent

System > Intent:
       Action: android.settings.APPLICATION_DETAILS_SETTINGS
       Data:   package:com.yourpackage.name
       Target: Activity

不是 issue 的 issue

shizuku 权限显示错误

设备：LG G5
系统：Android 7.0
shizuku 版本：3.5.0.r323
如图，shizuku 权限显示为权限名，而不是正常的中文。
此问题在某次更新后出现。（好像是最近的一次更新）

三星 S9 已启动的服务会自动关闭

谷歌搜了一下没找到答案，我用的是 Android Pie，三星默认连接电脑是 MTP 模式，直接输入命令可以开启，但大概过两天两夜再打开就是没有运行，手机没重启，app 是 Play 上的最新版本。

App takes up all of space

A critical bug appeared after using it the previous day. It looks like it used up all my available storage space, probably due to logging although I don't see any setting for logging in the app itself.

Using Shizuku Manager version 2.0.0 on Android 6.0 with root capability

MI 9 Android Q 上的关闭 Shizuku 授权闪退问题。

你好，最近着手开发一个应用引入了 Shizuku。引入后试着关闭 Shizuku Manager (3.4.5) 中的授权，程序会直接闪退。尝试关闭App Ops，冰箱也有同样问题。系统版本MIUI 10 9.8.22 Android Q。崩溃日志如下。

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.lbe.security.miui/com.android.packageinstaller.permission.ui.GrantPermissionsActivity}: android.content.res.Resources$NotFoundException: String resource ID #0x7f100026
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3304)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3443)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2040)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7520)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
Caused by: android.content.res.Resources$NotFoundException: String resource ID #0x7f100026
at android.content.res.Resources.getText(Resources.java:379)
at android.content.res.MiuiResources.getText(MiuiResources.java:97)
at android.widget.TextView.setText(TextView.java:6376)
at com.android.packageinstaller.permission.ui.GrantPermissionsDefaultViewHandler.updateDescription(Unknown Source:61)
at com.android.packageinstaller.permission.ui.GrantPermissionsDefaultViewHandler.updateAll(Unknown Source:0)
at com.android.packageinstaller.permission.ui.GrantPermissionsDefaultViewHandler.updateUi(Unknown Source:29)
at com.android.packageinstaller.permission.ui.GrantPermissionsActivity.showNextPermissionGroupGrantRequest(Unknown Source:436)
at com.android.packageinstaller.permission.ui.GrantPermissionsActivity.onCreate(Unknown Source:535)
at android.app.Activity.performCreate(Activity.java:7880)
at android.app.Activity.performCreate(Activity.java:7869)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1300)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3279)
... 11 more

能否将shizuku设为设备管理员？

rt，不用每次重启都要再次给权限

adb激活

C:\Users\xx>adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
sh: /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh: No such file or directory

problem internet connect

After I installed shizuku, All internet connection app show "49年" in system notification like the attached pic. I tried uninstall, but can't fix.

没有权限执行 Script

如下日志，在小米盒子 4 （MIUI 国内版、Android M、网络 ADB）的情况下无法执行，确认 2000 uid，且无权访问 /data。

shell@transformers:/data $ id -u                                               
2000
shell@transformers:/data $ ls
opendir failed, Permission denied
shell@transformers:/data $ /data/user/0/moe.shizuku.privileged.api/files/start.sh
/system/bin/sh: /data/user/0/moe.shizuku.privileged.api/files/start.sh: can't execute: Permission denied

你们 MIUI 你们 MIUI 你们 MIUI

server v3 crash

Device: HTC U11 (Japan)
Android 8.0 without root

log:

D:\Tools\platform-tools>adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
info: start.sh begin
chcon: '/data/local/tmp/shizuku_starter' to u:object_r:shell_data_file:s0: Permission denied
info: path is /storage/emulated/0/Android/data/moe.shizuku.privileged.api/files/server-v3.dex
info: path-legacy is /storage/emulated/0/Android/data/moe.shizuku.privileged.api/files/server-legacy-v32-api26.dex
info: path is /data/local/tmp/shizuku/server-v3.dex
info: path-legacy is /data/local/tmp/shizuku/server-legacy-v32-api26.dex
info: starter begin
info: killing old process...
info: killed 20131 (shizuku_server_legacy)
info: starting server v3...
info: process forked, pid=20933
info: checking shizuku_server start...
warn: timeout but can't get pid of shizuku_server.
--- crash start ---
[command] logcat -b crash -t '03-27 22:19:52.000' -d
03-27 22:19:52.950 20934 20934 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
03-27 22:19:52.950 20934 20934 E AndroidRuntime: java.lang.SecurityException: Permission Denial: registerUidObserver from pid=20934, uid=2000 requires android.permission.PACKAGE_USAGE_STATS
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:1960)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:1906)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at android.app.IActivityManager$Stub$Proxy.registerUidObserver(IActivityManager.java:9128)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at moe.shizuku.server.api.Api.registerUidObserver(Api.java:110)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at moe.shizuku.server.BinderSender.register(BinderSender.java:119)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at moe.shizuku.server.ShizukuService.<init>(ShizukuService.java:52)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at moe.shizuku.server.Starter.main(Starter.java:109)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
03-27 22:19:52.950 20934 20934 E AndroidRuntime:        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:284)
03-27 22:19:52.951 20934 20934 E AndroidRuntime: Error reporting crash
03-27 22:19:52.951 20934 20934 E AndroidRuntime: java.lang.RuntimeException: Bad file descriptor
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at android.os.BinderProxy.transactNative(Native Method)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at android.os.BinderProxy.transact(Binder.java:756)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at android.app.IActivityManager$Stub$Proxy.handleApplicationCrash(IActivityManager.java:4345)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$KillApplicationHandler.uncaughtException(RuntimeInit.java:115)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1063)
03-27 22:19:52.951 20934 20934 E AndroidRuntime:        at java.lang.Thread.dispatchUncaughtException(Thread.java:1953)
--- crash end ---
--- shizuku start ---
[command] logcat -b main -t '03-27 22:19:52.000' -d -s ShizukuServer ShizukuServerV3 ShizukuManager
03-27 22:19:52.940 20934 20934 I ShizukuServerV3: server v3
03-27 22:19:52.940 20934 20934 I ShizukuServerV3: using token from arg
--- shizuku end ---
info: shizuku_starter exit with non-zero value 7

AndroidP 息屏状态错误

无法在息屏状态开启 ADB，报错如下

sailfish:/ $ sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh                                                                                                                             
info: start.sh begin
info: starter begin
info: old shizuku_server found, killing
info: dex path is /storage/emulated/0/Android/data/moe.shizuku.privileged.api/files/server-27-v30.dex
info: process forked, pid=19315
info: checking shizuku_server start...
info: checking shizuku_server stability...
info: checking shizuku_server stability...
info: checking shizuku_server stability...
info: shizuku_server started.
--- crash start ---
[command] logcat -b crash -t '07-23 12:14:12.000' -d
07-23 12:14:12.886 17572 17572 E AndroidRuntime: FATAL EXCEPTION: main
07-23 12:14:12.886 17572 17572 E AndroidRuntime: Process: moe.shizuku.privileged.api, PID: 17572
07-23 12:14:12.886 17572 17572 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {moe.shizuku.privileged.api/moe.shizuku.manager.MainActivity}: java.lang.IllegalStateException: Not allowed to start service Intent { act=moe.shizuku.manager.service.action.AUTH cmp=moe.shizuku.privileged.api/moe.shizuku.manager.service.WorkService }: app is in background uid UidRecord{fda9a97 u0a220 TPSL bg:+4m3s845ms idle procs:1 seq(0,0,0)}
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3784)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:193)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6669)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { act=moe.shizuku.manager.service.action.AUTH cmp=moe.shizuku.privileged.api/moe.shizuku.manager.service.WorkService }: app is in background uid UidRecord{fda9a97 u0a220 TPSL bg:+4m3s845ms idle procs:1 seq(0,0,0)}
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ContextImpl.startService(ContextImpl.java:1532)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.content.ContextWrapper.startService(ContextWrapper.java:664)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at moe.shizuku.manager.service.WorkService.startAuth(Unknown Source:12)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at moe.shizuku.manager.MainActivity.check(Unknown Source:0)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at moe.shizuku.manager.MainActivity.onResume(Unknown Source:3)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.Activity.performResume(Activity.java:7292)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776)
07-23 12:14:12.886 17572 17572 E AndroidRuntime: 	... 11 more
--- crash end ---
--- shizuku start ---
[command] logcat -b main -t '07-23 12:14:12.000' -d -s ShizukuServer ShizukuManager
07-23 12:14:12.746 19316 19316 W ShizukuServer: unsupported system (28) detected, some API may not work
07-23 12:14:12.812 19316 19316 I ShizukuServer: uid: 2000
07-23 12:14:12.812 19316 19316 I ShizukuServer: api version: 28
07-23 12:14:12.812 19316 19316 I ShizukuServer: device: sailfish
07-23 12:14:12.812 19316 19316 I ShizukuServer: start version: 30 token: 7a7afaa6-c29f-4144-af0a-0d370abe6bbb
07-23 12:14:12.855 19316 19316 I ShizukuServer: send token to manager app in user 0
--- shizuku end ---
info: shizuku_starter exit with 0

亮屏状态成功开启 ADB 后，息屏重亮后服务失效

还是我使用姿势有误？

[feature request] restart server without computer

If the server started then crashed, will it be possible for user to do the following things:

first time after reboot phone, run adb tcpip to start adb over network
then run commands to start shizuku server
then it crashed
user back to shizukumgr app, click start button to start server via pre-started network adb?

If some one relies on shizuku for ice box, then he is outside without computer, the system itself however killed the shizuku server, then this feature will help user to get quick access back to apps in icebox again.

just like the brevent do.

shizuku 开启后无法工作

手机型号blackberry priv
系统6.0
在用adb 启动shizuku server后(running version 32) 日志如下
info: start.sh begin info: starter begin info: no old shizuku_server found. info: dex path is /storage/emulated/0/Android/data/moe.shizuku.privileged.api/files/server-23-v32.dex info: process forked, pid=5846 info: checking shizuku_server start... info: checking shizuku_server stability... info: checking shizuku_server stability... info: checking shizuku_server stability... info: shizuku_server started. --- crash start --- [command] logcat -b crash -t '03-16 19:00:06.000' -d --- crash end --- --- shizuku start --- [command] logcat -b main -t '03-16 19:00:06.000' -d -s ShizukuServer ShizukuManager 03-16 19:00:07.579 5847 5847 I ShizukuServer: uid: 2000 03-16 19:00:07.580 5847 5847 I ShizukuServer: api version: 23 03-16 19:00:07.580 5847 5847 I ShizukuServer: device: venice 03-16 19:00:07.580 5847 5847 I ShizukuServer: start version: 32 token: 717e5a8d-33b6-4939-a4b2-c8a736df2270 03-16 19:00:07.641 5847 5847 I ShizukuServer: send token to manager app in user 0 03-16 19:00:07.799 5900 5900 I ShizukuManager: token update: 717e5a8d-33b6-4939-a4b2-c8a736df2270 --- shizuku end --- info: shizuku_starter exit with 0
使用my android tools 时显示 shizuku authorization failed
使用 blocker 会报错
n

小黑屋，icebox 也必须要adb后才能使用

Add virtual joystick for fire/android tv

Adding a virtual joystick
for android/fire tv support

Want a way to enable
virtual mouse or joystick
Integrated inside shizuku

App Cloner has this feature
https://appcloner.app
Under android tv & wear os options:
Joystick pointer
Control touch-only apps through a cross-hair pointer using your D-pad. Press the center key to trigger clicks, long-press to show / hide the cross-hair pointer.

问题

请问一下我有一个app想接入您的shizuku manager，但我没有在您的github上找到帮助文档，能不能给我一份呢。

现在的shizuku可以获得permission.UPDATE.APP.OPS.STATUE吗?

谢谢您

TODO

use different dex for different API version
try ServiceManager.addService for root mode
add all APIs

The system is possibly kept waked up with shizuku

I recently observed the device(7.1.2) kept waked up which seems to be caused by shizuku(0.2.5).

Though I could not find any concrete evidence for now, there is still some clues:

1, The issue occurred after using shizuku as the privileged action proxy for your AppOps wrapper app.
On another device running the same Android version and same AppOps wrapper without shizuku, the issue does not occur.

The version 0.1.99 is involved in this case:
https://play.google.com/store/apps/details?id=rikka.appops

2, The issue(on the first device) disappears after a reboot, but some time(around a day) later, it occurs again.

3, I used the wakelock detector to gather statistics about wakelock duration of each app.
When it happened, the device did not sleep at all after screen off for hours(suggesting partial wakelock was hold by some owner), however I could not observe any app that was responsible for the long wakelock.

Usually the wakelock issue is due to play service's NLP(network location provider) components when there is a connectivity issue, and more importantly can be observed by such tools as "an app has been holding a wakelock for a very long time "

Note:
The wakelock tool app used:
https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot

Me

[code] sorry for ask how to write a binder to shizuku

sorry for the stupid question.

i viewed the sample, then not known for those lines, i don't know how to write a binder and write it on which class or package, my app have mutilple packages named..

Shizuku/sample/src/main/java/moe/shizuku/sample/MainActivity.java

Line 52 in 75b84e9

 sendBroadcast(new Intent("moe.shizuku.sample.TEST").setPackage(getPackageName())); 

and

Shizuku/sample/src/main/java/moe/shizuku/sample/SampleApplication.java

Line 58 in 75b84e9

 Log.d("ShizukuSample", "initialize " + ShizukuMultiProcessHelper.initialize(this, !getProcessName().endsWith(":test"))); 

and

Shizuku/sample/src/main/AndroidManifest.xml

Lines 29 to 35 in 75b84e9

 <receiver android:name=".MultiProcessTestReceiver" 

 android:exported="false" 

 android:process=":test"> 

 <intent-filter> 

 <action android:name="moe.shizuku.sample.TEST"/> 

 </intent-filter> 

 </receiver>

if bothered, just close this.

java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder moe.shizuku.server.IShizukuService.asBinder()' on a null object reference

I just called my ShizukuService.transactRemote(data, reply, 0), and I got this message. Shizuku is running and I have got the permission.

E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #3
    Process: de.unknown.appmanager, PID: 30878
    java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder moe.shizuku.server.IShizukuService.asBinder()' on a null object reference
        at moe.shizuku.api.ShizukuService.transactRemote(ShizukuService.java:42)
        at de.unknown.appmanager.ShizukuApi.deletePackage(ShizukuApi.kt:26)
        at de.unknown.appmanager.appmanagers.ShizukuAppManager$uninstallPackage$1.run(ShizukuAppManager.kt:76)
        at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)

Add an actual License to the repo

Ref: Aefyr/SAI#43 (comment)

/LE: It appears here: https://github.com/RikkaApps/Shizuku/blob/master/publish.gradle#L6 but is that for the whole repo?

Persistent Notifications to keep Shizuku Alive

Dear @RikkaW,
Shizuku is a phenomenal app for free and I have been greatly benefited...Using two shizuku assisted apps such as icebox and app ops in Samsung galaxy a50 android pie stock rom unrooted. With shizuku versionVersion 3.4.5.r288.726cd9a ... I have been facing a problem...Shizuku is getting killed even after making it "not optimised" in settings and disabling power saver mode...I did check out tips that were given in the website to make to persist without reboot....
So could there be persistent notification service that would keep the service alive ...or background service?
Thanks in advance....

Is it possible to start Shizuku Server using a similar technique?

not working on lineage os 14.1

java.lang.NullPointerException: can't find transaction code of getInstalledPackages in android.content.pm.IPackageManager$Stub

Android Studio Error

I was using the source code to see the sample,But not working in the AS 3.4.2
Error:

org.gradle.api.internal.tasks.compile.CompilationFailedException: Compilation failed; see the compiler error output for details.
	at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:52)
	at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:36)
	at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:100)
	at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:52)
	at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:38)
	at org.gradle.api.internal.tasks.compile.AnnotationProcessorDiscoveringCompiler.execute(AnnotationProcessorDiscoveringCompiler.java:51)
	at org.gradle.api.internal.tasks.compile.AnnotationProcessorDiscoveringCompiler.execute(AnnotationProcessorDiscoveringCompiler.java:37)
	at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:39)
	at org.gradle.api.internal.tasks.compile.incremental.IncrementalCompilerFactory$2.execute(IncrementalCompilerFactory.java:110)
	at org.gradle.api.internal.tasks.compile.incremental.IncrementalCompilerFactory$2.execute(IncrementalCompilerFactory.java:106)
	at org.gradle.api.internal.tasks.compile.incremental.IncrementalResultStoringCompiler.execute(IncrementalResultStoringCompiler.java:59)
	at org.gradle.api.internal.tasks.compile.incremental.IncrementalResultStoringCompiler.execute(IncrementalResultStoringCompiler.java:43)
	at org.gradle.api.internal.tasks.compile.CompileJavaBuildOperationReportingCompiler$2.call(CompileJavaBuildOperationReportingCompiler.java:59)
	at org.gradle.api.internal.tasks.compile.CompileJavaBuildOperationReportingCompiler$2.call(CompileJavaBuildOperationReportingCompiler.java:51)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:305)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
	at org.gradle.api.internal.tasks.compile.CompileJavaBuildOperationReportingCompiler.execute(CompileJavaBuildOperationReportingCompiler.java:51)
	at org.gradle.api.tasks.compile.JavaCompile.performCompilation(JavaCompile.java:154)
	at org.gradle.api.tasks.compile.JavaCompile.compile(JavaCompile.java:122)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
	at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:47)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:41)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:284)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:301)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:293)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:273)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:258)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$200(ExecuteActionsTaskExecuter.java:67)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:145)
	at org.gradle.internal.execution.impl.steps.ExecuteStep.execute(ExecuteStep.java:49)
	at org.gradle.internal.execution.impl.steps.CancelExecutionStep.execute(CancelExecutionStep.java:34)
	at org.gradle.internal.execution.impl.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:69)
	at org.gradle.internal.execution.impl.steps.TimeoutStep.execute(TimeoutStep.java:49)
	at org.gradle.internal.execution.impl.steps.CatchExceptionStep.execute(CatchExceptionStep.java:33)
	at org.gradle.internal.execution.impl.steps.CreateOutputsStep.execute(CreateOutputsStep.java:50)
	at org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute(SnapshotOutputStep.java:43)
	at org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute(SnapshotOutputStep.java:29)
	at org.gradle.internal.execution.impl.steps.CacheStep.executeWithoutCache(CacheStep.java:134)
	at org.gradle.internal.execution.impl.steps.CacheStep.lambda$execute$3(CacheStep.java:83)
	at java.util.Optional.orElseGet(Optional.java:267)
	at org.gradle.internal.execution.impl.steps.CacheStep.execute(CacheStep.java:82)
	at org.gradle.internal.execution.impl.steps.CacheStep.execute(CacheStep.java:36)
	at org.gradle.internal.execution.impl.steps.PrepareCachingStep.execute(PrepareCachingStep.java:33)
	at org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:38)
	at org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:23)
	at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:96)
	at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:89)
	at java.util.Optional.map(Optional.java:215)
	at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:52)
	at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:36)
	at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:34)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:91)
	at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:91)
	at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:119)
	at org.gradle.api.internal.tasks.execution.ResolvePreviousStateExecuter.execute(ResolvePreviousStateExecuter.java:43)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:93)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:45)
	at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:94)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:67)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:49)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:305)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:49)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:43)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:355)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:343)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:336)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:322)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:134)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:129)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:202)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:193)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:129)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)

Shizuku doesn't works after removing USB

Service stops running after I remove the USB.

	<receiver android:name=".MultiProcessTestReceiver"
	android:exported="false"
	android:process=":test">
	<intent-filter>
	<action android:name="moe.shizuku.sample.TEST"/>
	</intent-filter>
	</receiver>