Matrix Home Recommended
Matrix is a minority writing community, we advocate sharing real product experience, practical experience and thinking. From time to time, we will select the highest-quality articles from Matrix, showing the most authentic experiences and opinions from users.
The article represents the author’s personal opinion, only minor revisions to the title and layout are made by the minority.
In the traditional concept of many people, if you want to do something beyond the user-level permissions on your mobile phone, generally speaking, you cannot bypass the operations such as unlocking the Bootloader, flashing Magisk and obtaining root permissions.
The same is true for me – Magisk’s previous turmoil made me start to re-examine the use of Magisk itself, and during that time, I used the European version of OneUI to get a very good custom experience without flashing Magisk, These experiences have made me drift away from Magisk, which was once a “must-have” for gaming.
Instead, there is another open source project that does not require root and has a lower threshold, and is also the protagonist of today’s article: Shizuku .
How to start Shizuku
Similar to Magisk, we can also understand Shizuku as another “bridge” that interacts with the system and achieves customized requirements.
Although it comes from Chinese developers, its name has gradually become well known to foreign developers and users in recent years. Its best part, in the words of the developers, is that it interacts directly with the system server, providing a more efficient system-level interface for some applications that require higher privileges, and can be turned on with only adb debugging without Bootloader. Unlock, flash into Magisk and other “hard core” operations.
In other words, compared to the traditional root permission method, Shizuku executes faster, has a lower threshold for getting started, and does not ask users for root permissions that are higher than the actual needs. In my opinion, it is a more suitable tossing method for players and users.
After Android 11, our mobile phones actually have the ability to “debug themselves”. A feature called “Wireless Debugging” is hidden in the “Developer Options”. As long as the device is connected to a Wi-Fi network, it can “doll” by itself through ADB wireless debugging, without the need for an external computer or other USB devices .
Taking Shizuku as an example, after downloading and installing Shizuku from the Google Play Store, the method of completing the configuration without root is similar to the Repainter application we introduced before:
- Make sure your phone has “Developer Options” turned on;
- In Shizuku, select “Start via Wireless Debugging”, then click the “Pair” button to jump to the developer options;
- At this point, we need to find the “USB debugging/wireless debugging” function in the developer options. After enabling wireless debugging, select “Pairing devices using pairing code”;
- At this time, Shizuku will prompt the detection of the pairing code by means of a pop-up notification. Enter the pairing code provided by the developer option and click Send to complete the pairing.
After that, every time the device restarts or Shizuku fails, we can restart Shizuku through the same process. It is worth mentioning that although it sounds troublesome, the wireless debugging pairing state can be saved, so we only need to restart each time. Wireless ADB debugging is enough, and the pairing process can be omitted.
In addition, here is a little trick to quickly turn on wireless debugging: some options in the developer options can be put into the shortcut panel, including “wireless debugging”, “turn off the sensor”, etc., which can be found in the developer options Check the “Quick Settings Developer Tile”.
Tips: Similar wireless debugging authorizations above are also applicable to applications such as black threshold.
What can it do for you?
After completing the above steps and successfully running the Shizuku process, we can use it to help third-party applications obtain higher permissions – but this is only a vague intention. What specific needs can this “higher permissions” solve? Woolen cloth?
Here we might as well give a few examples.
Disable app
Involving applications:
On Android, the application can be in a “disabled” or “frozen” state with the help of the application manager. In this state, the application will not have any activity, achieving a similar “uninstall” effect, and can be activated at any time. This function is very suitable for low-frequency scenarios such as takeout, shopping, ticket booking, fitness, etc. You can also deactivate Feishu and WeChat with one click on weekends like me. The deactivated apps will not be able to push notifications normally, so the phone is lighter , life is more clean.
Shizuku can provide API support for tools such as refrigerators, black houses, and hail, and it is faster and more efficient than the traditional root method that requires tools to continuously issue commands and process text one by one to obtain execution results – even if your device is rooted , the Shizuku method is also recommended.
As for the tools themselves, these three tools have their own merits: the refrigerator is an old brand, and the functions are relatively complete: it supports the quick call out of the refrigerator drawer in the form of a voice assistant, and also supports the application of tab freezing; Hail is a free open source application, and it is already suitable for use. With Matrial You Design, it is more transparent and trendy.
All three models support the automatic freezing function, and the two models with in-app purchase payment also support free trials.
App Ops Permission Management
Involving applications:
- App Ops
- permission dog
In recent years, the permission management function has often been linked to the privacy protection feature of the mobile phone system. However, when manufacturers emphasize this function, they have not made this function more usable. Requirements such as batch setting and template application are still rarely taken care of. Needless to say, many subdivided and unpopular permissions are not open for users to set. Apps like App Ops are, in my opinion, a complement and enhancement. Through them, we can exhaust all possibilities of the rights management function.
It also requires Shizuku to escalate privileges before it can be used. As mentioned above, the execution efficiency is slightly better than that of root mode.
Related reading: Running through iOS 14 and Android 11 on Permission Management: App Ops 4.0 Getting Started Guide
This application mainly introduces App Ops, which comes from the same developer as Shizuku. It not only has permission templates, permission backup and restore, and batch setting functions, but also provides a clipboard monitor similar to iOS in the case of permanent background. With the two permissions of “read clipboard content” and “modify clipboard content”, the privacy protection of the clipboard can even be more in place than iOS .
“Automatically apply templates for new applications” can make permission settings more lazy and friendly, and let me worry as little as possible while setting permissions. After one configuration, I rarely open App Ops manually. In general, in App Ops, setting permissions is not a fight between the user and the system, but more like letting the user declare their will and letting the system implement it.
In addition, a permission setting that is particularly commonly used in App Ops and is worth setting as a template to be applied in batches to domestic “cancer apps” is: “Strictly restrict running in the background”. Whether it is Android 9 or Android 13, the system will constrain the background behavior of applications more.
Silent/Batch Install Apps
Involving applications:
- Aurora Store
- Swift Backup
- R installer
- SAI
Because side-loading applications are allowed (that is, users are allowed to install application packages by themselves), in addition to the Play Store and the official application store provided by the manufacturer, there are also third-party application stores with their own characteristics such as Aurora Store, F-Droid, FFUpdater and so on. storehouse.
It is a pity that these “third-party” stores are not old enough, and they are still distributing installation packages in essence. Therefore, when installing applications, the process of manually installing one application is inevitable. When there are many applications that need to be installed at one time, the steps will be more complicated and require us to pay attention and operate at all times.
Shizuku can provide higher “silent installation” permissions, but this requires the application itself to adapt and access Shizuku. After obtaining the silent installation permission, the application itself can be responsible for batch downloading, which makes “quick batch installation of applications” a reality.
Taking the backup tool Swift Backup, which has been introduced many times by the minority, although application data cannot be accessed in non-root mode, it is much more convenient to batch transfer all third-party applications installed on one phone to another phone. , Meituan, Hema, Taobao and other service applications are just a simple login for me to use immediately. In addition, Swift Backup also supports installation of Play Store’s .aab format of app bundles.
Be bold: If you directly replace the system’s Package installer and install the package parser, and give Shizuku permission, can it take effect globally and silently install any application package? Domestic developers have also noticed this solution and developed R installer, an application that silently installs applications. For Bank of China users, using R installer can also avoid various psoriasis advertisements of the system’s own application installer.
Change the system theme color of Android 12
- Repainter
Thanks to the introduction of the new design language Material You, Android 12 finally allows users to choose theme colors at the system level. The emergence of the system interface also means the possibility of hacking. @Danny Lin , an independent developer who has deeply explored the system interface since the Android 12 beta version, also took this as an opportunity to develop a more general tool: Repainter, which provides traditional The root way as well as the Shizuku way.
For a more detailed introduction and experience, please refer to the previous articles of the minority:
Forced dark theme by app
The dark theme has been promoted since Android 10, and it has been two or three years today, and most applications have completed the adaptation of the dark theme. If there are still some “thorns” that are unwilling to adapt, you can try to enable the “Force Dark Mode” option in the developer options to achieve the effect through intelligent inversion. The fly in the ointment is that when this option is turned on, it will take effect in all applications. Can it be more refined and only take effect for some applications?
DarQ is a tool that can use the Shizuku API to force dark mode by application, and it is also useful for applications like DevCheck that use dark themes as a payment point. And DarQ also supports determining whether to force a dark theme by geographic location or time zone.
Epilogue
It should be noted that Shizuku and Magisk are not alternatives to each other. The latter is more hard-core and more demanding for users, and of course it can achieve more functions. The former only uses the debugging function that comes with the system to complete the rights and can be called by third-party applications. If the two are used together, Shizuku does not have to re-authorize after each restart, and also reduces the possibility of third-party applications abusing root privileges, which is a more perfect solution.
> Download Minority 2.0 client , follow Minority Official Account, and unlock a new reading experience 
> Practical and easy-to-use genuine software , presented to you by the minority 
This article is reproduced from: https://sspai.com/post/73294
This site is for inclusion only, and the copyright belongs to the original author.