# Shizuku Shizuku is an Android application and API that lets apps use system APIs with root or ADB shell identity. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## January 2021 round-up DevFeed: [January 2021 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-02-02T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [USB](), [Android](), [Shizuku](), [Kernel](), [Linux]() Tags: [adb](), [android](), [kernel](), [linux](), [mobile](), [render](), [usb](), [user-interfaces]() ### AI overview The January 2021 Mobile NixOS round-up reports merged project changes, including USB gadget modes, target disk mode for selected devices, broader ADB support on Android-based devices, DRM rendering support during early boot, and a libinput input driver. ### Source excerpt This update is the fourteenth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the month 18 pull requests were merged. Buckle-up, this month there's a lot to say. Go go all USB gadget modes A couple changes this month are related to USB gadget mode. This is the name of the feature allowing a device (your cellphone) to be used as a USB device on your computer. Target disk mode This is not a fresh feature, the implementation pull request was opened in March 2020. Once a device is booted with this example system, the device's internal storage is made available over USB, as if it was a USB mass storage device. The feature is limited to select devices, as it can be easily misused. The pine64-pinephone and asus-dumo devices are configured for this feature. It is limited as the block device to export has to be configured on a per-device basis. A further reason is the following: Warning Target disk mode should not be used to export the full drive of Android-based devices as it becomes trivial to brick a device. Some of their partitions should not be touched. This is because for most Android-based devices, part of their basic firmware needed for booting is found on the main block device. Erasing or modifying the wrong partition would be like erasing the BIOS from your computer. Broader ADB support Time was taken to understand why ADB didn't work on newer Android-based devices. It was initially suspected that the ADB daemon was incompatible with GadgetFS and FunctionFS. It was much more trivial. The FunctionFS feature of the kernel needed the daemon to be started at a specific moment during the configuration, rather than at any time after. With the fixes in #290 any device with GadgetFS can use ADB. This means inspecting newer Android-based devices is easier, as it will most likely work if the device boots with