Our great sponsors
-
hardened_malloc
Hardened allocator designed for modern systems. It has integration into Android's Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-based platforms. It will gain more portability / integration over time.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Shizuku
Using system APIs directly with adb/root privileges from normal apps through a Java process started with app_process.
-
termux-app
Termux - a terminal emulator application for Android OS extendible by variety of packages.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
VirtualXposed
A simple app to use Xposed without root, unlock the bootloader or modify system image, etc.
A little glimpse from the future (not really, it's already here): With Android 13 KVM is a platform requirement (for pKVM) so it'll be possible to run custom "ROM"s as VMs without root access (and use Magisk, KernelSU etc whatever "root" stuff in that VM, not on the host OS).
Demand properly made devices that can re-lock the bootloader with a 3rd party ROM installed, like in the case with Pixel devices & the 3rd party GrapheneOS; if the stock system isn't promised to be updated forever.
Then there's the fact that starting with Android 11 it's no longer necessary to first use ADB over USB to initiate ADB over network so, anybody can start ADB on the device itself, use apps like Shizuku, LSPatch (rootless Xposed), LADB, Termux (apt install adb) etc, automate the ADB commands (via Tasker, let's say) on system boot-up and so on (to let's say, disable the shitty OEM/carrier app packages etc).
Then there's the fact that starting with Android 11 it's no longer necessary to first use ADB over USB to initiate ADB over network so, anybody can start ADB on the device itself, use apps like Shizuku, LSPatch (rootless Xposed), LADB, Termux (apt install adb) etc, automate the ADB commands (via Tasker, let's say) on system boot-up and so on (to let's say, disable the shitty OEM/carrier app packages etc).
Then there's the fact that starting with Android 11 it's no longer necessary to first use ADB over USB to initiate ADB over network so, anybody can start ADB on the device itself, use apps like Shizuku, LSPatch (rootless Xposed), LADB, Termux (apt install adb) etc, automate the ADB commands (via Tasker, let's say) on system boot-up and so on (to let's say, disable the shitty OEM/carrier app packages etc).
Then there's the fact that starting with Android 11 it's no longer necessary to first use ADB over USB to initiate ADB over network so, anybody can start ADB on the device itself, use apps like Shizuku, LSPatch (rootless Xposed), LADB, Termux (apt install adb) etc, automate the ADB commands (via Tasker, let's say) on system boot-up and so on (to let's say, disable the shitty OEM/carrier app packages etc).
Then there's the fact that starting with Android 11 it's no longer necessary to first use ADB over USB to initiate ADB over network so, anybody can start ADB on the device itself, use apps like Shizuku, LSPatch (rootless Xposed), LADB, Termux (apt install adb) etc, automate the ADB commands (via Tasker, let's say) on system boot-up and so on (to let's say, disable the shitty OEM/carrier app packages etc).