Shizuku

34 downloads

Uploaded by

erex2499

Version

13.2.0.r954.f03f071 (build 954)  37 version(s)

Shizuku versions

13.5.4.r1079.bd847ed8-dev (build 1079)

2430 downloads

13.5.4.r1066.48a534b (build 1066)

184 downloads

13.5.4.r1064.1278b9f (build 1064)

107 downloads

13.5.4.r1062.c02de15 (build 1062)

223 downloads

13.5.5.r1055.adeaf2d (build 1055)

114 downloads

13.5.4.r1050.adeaf2d (build 1050)

2231 downloads

13.5.4.r1049.0e53409 (build 1049)

223 downloads

13.5.3.r1040.1fc3a2d (build 1040)

409 downloads

13.5.3.r1036.fff3f87 (build 1036)

323 downloads

13.5.2.r1028.2bbf671 (build 1028)

45 downloads

13.5.2.r1028.2bbf671 (build 1028)

157 downloads

13.5.1.r1025.ebb2a30 (build 1025)

231 downloads

13.5.0.r1021.28fd25d (build 1021)

109 downloads

13.3.0.r993.5392b9d (build 993)

309 downloads

13.2.1.r968.9b59737 (build 968)

121 downloads

13.2.1.r965.5c29283 (build 965)

94 downloads

13.2.1.r962.48f1ece (build 962)

88 downloads

13.2.1.r958.5f9516b (build 958)

48 downloads

13.2.1.r958.5f9516b (build 958)

15 downloads

13.2.0.r954.f03f071 (build 954)

34 downloads

13.0.0.r952.27c15f5 (build 952)

24 downloads

13.0.0.r949.377dd96 (build 949)

42 downloads

13.0.0.r941.258a69b (build 941)

61 downloads

13.0.0.r934.787870b (build 934)

18 downloads

13.0.0.r931.cb4b93e (build 931)

72 downloads

13.0.0.r924.9e7381b (build 924)

119 downloads

12.14.0.r919.5fb3401 (build 919)

51 downloads

12.14.0.r914.e88de6a (build 914)

16 downloads

12.12.0.r885.287b4eb (build 885)

58 downloads

12.10.0.r868.704048a (build 868)

68 downloads

12.8.1.r813.97acd55 (build 813)

27 downloads

12.8.1.r813.97acd55 (build 813)

34 downloads

12.8.0.r808.7d4ac78 (build 808)

18 downloads

12.6.2.r790.907776f (build 790)

53 downloads

12.6.0.r762.6812764 (build 762)

41 downloads

12.5.0.r756.c13ed7d (build 756)

10 downloads

12.4.3.r713.e5d22d5 (build 713)

70 downloads

Close

Size

3.4 MiB

Publish Date

2023-02-02

Category

Tools

Package

moe.shizuku.privileged.api

Minimum OS

Android 6.0

SHA1

eeec4bced9b5330e540587969b4be8bbc53076e4

Description

When developing applications that require root, the most common method is to run some commands in the su shell. For example, the application uses the command: pm enable/disable to enable/disable components. This method has very big drawbacks: Extremely slow (creation of multiple processes). Requires word processing (very unreliable). The ability is limited by the commands available, even if adb has sufficient rights to run the application, but be aware that if you refuse to run it through ADB, then root privileges will be required. Shizuku uses a completely different way. The most important feature that Shizuku provides is to be a sort of intermediary that takes requests from an application, sends them to the system server, and sends back the results. For an application, this is almost identical to using the system APIs directly. But it's much faster because it connects directly to the system. Several apps are already using Shizuku. If you want to integrate it into yours, check out the developer guide. There is also a manual for users. And also, I would like to recall the fact of how much it is needed and is given priority by some software, such as the popular installer of APKS files - SAI, DarQ, SkyDroid, and in general, in many other programs. A complete alternative to root-rights! ◇ Reference Information ◇ When developing applications that require root, the most common method is to run some commands in the su shell. For example, there is an application that uses the pm enable/disable command to enable/disable components. This method has very big drawbacks: Extremely slow (creation of multiple processes). Requires word processing (Very unreliable) Capability is limited by available commands Even if ADB has sufficient permissions, root privileges are required to run the application. Shizuku uses a completely different way. See detailed description below. User manual and download https://shizuku.rikka.app/ How does Shizuku work? First, we need to talk about how the application uses system APIs. For example, if an application wants to get installed applications, we all know that we should use PackageManager#getInstalledPackages(). It's actually an inter-process communication (IPC) process between the application process and the system server process, it's just that the Android framework has done the inner work for us. Android uses a binder to perform this type of IPC. Binder allows the server side to know the uid and pid of the client side so that the system server can check if the application has permission to perform the operation. Typically, if there is a "manager" (eg PackageManager) for applications that they can use, there should be a "service" (eg PackageManagerService) in the system's server process. We can simply assume that if an application has a "service" binder, then it can interact with the "service". When the application process starts, it receives system service binders. Shizuku recommends that users first run the process, the Shizuku server, as root or ADB. When the app starts, the binding to the Shizuku server will also be sent to the app. The most important feature that Shizuku provides is to be a sort of intermediary that takes requests from an application, sends them to the system server, and sends the results back. You can see the transactRemote method in the class: rikka.shizuku.server.ShizukuService and also in the class: moe.shizuku.api.ShizukuBinderWrapper. So we've reached our goal of using higher resolution system APIs. And for an application, this is almost identical to using the system APIs directly. □ API and sample □ https://github.com/RikkaApps/Shizuku-API Upgrading to v11 Existing applications continue to work, of course. Tutorial for dummies who don't understand how to use Shizuku: https://github.com/RikkaApps/Shizuku-API#migration-guide-for-existing-applications-use-shizuku-pre-v11 ♤ ATTENTION, NOW LIMITATIONS ARE ABSOLUTELY FOR EVERYONE ♤ You are NOT allowed to use the image files listed below in any way (other than to display Shizuku itself). manager/src/main/res/mipmap-hdpi/ic_launcher.png manager/src/main/res/mipmap-hdpi/ic_launcher_background.png manager/src/main/res/mipmap-hdpi/ic_launcher_foreground.png manager/src/main /res/mipmap-xhdpi/ic_launcher.png manager/src/main/res/mipmap-xhdpi/ic_launcher_background.png manager/src/main/res/mipmap-xhdpi/ic_launcher_foreground.png manager/src/main/res/mipmap- xxhdpi/ic_launcher.png manager/src/main/res/mipmap-xxhdpi/ic_launcher_background.png manager/src/main/res/mipmap-xxhdpi/ic_launcher_foreground.png manager/src/main/res/mipmap-xxxhdpi/ic_launcher.png manager/src/main/res/mipmap-xxxhdpi/ic_launcher_background.png manager/src/main/res/mipmap-xxxhdpi/ic_launcher_foreground.png -something else) in any stores (IBNLT Google Play Store, etc.). Open source: https://github.com/RikkaApps/Shizuku All questions about bugs/bugs/side issues/and many other things you can ask and discuss here: https://github.com/RikkaApps/Shizuku/issues List of all Shizuku changes/releases: https://github.com/RikkaApps/Shizuku/releases Official website of the developer: https://shizuku.rikka.app/