How tytydraco/ladb works
Project type and purpose
• This is a single-module Android application (“app” folder) written in Kotlin, implementing MVVM and packing a full ADB server via JNI for on-device Local ADB over wireless debugging.
• Purpose: let users run ADB shell commands locally (without USB) by leveraging Android’s Wireless ADB Debugging feature.
File structure
• Top-level files: build scripts (build.gradle, settings.gradle), gradle wrapper.
• app/src/main/java/com/draco/ladb:
• views: Activities (Main, Bookmarks, Help)
• fragments: HelpPreferenceFragment
• recyclers: adapter for bookmark list
• viewmodels: MainActivityViewModel, BookmarksActivityViewModel (MVVM)
• services: QSTile.kt (Android Quick Settings TileService)
• utils: ADB.kt (wrapper around native ADB operations)
• app/src/main/jniLibs: prebuilt ADB server binaries for arm64, armeabi-v7a, x86, x86_64.
• app/src/main/res: layouts, menus, drawables, XML configs, themes.
Key insights from README
• Bundles ADB server inside app libraries.
• Communicates locally via loopback socket using wireless debugging pairing.
• No external backend or cloud dependencies.
• Incompatible with Shizuku; uses standard Android APIs only.
Main components
a. UI Layer
• MainActivity, BookmarksActivity, HelpActivity
• RecyclerView + BookmarksRecyclerAdapter
b. ViewModel Layer (MVVM)
• MainActivityViewModel, BookmarksActivityViewModel
c. Service Layer
• QSTile (Android TileService for quick access)
d. Native ADB Server
• JNI libraries (arm64-v8a, armeabi-v7a, x86, x86_64)
e. Utility Layer
• ADB.kt: launches ADB server process, issues shell commands
f. Android OS / Network
• Wireless Debugging subsystem (pairing dialog, loopback TCP/IP)
g. Data stores (optional)
• SharedPreferences or Room (not explicit here, but bookmarks likely in SharedPreferences via ViewModel).
Relationships and data flows
• User taps UI → Activity
• Activity binds to ViewModel → invokes methods
• ViewModel calls ADB.kt → starts ADB server process via JNI libs
• ADB server listens on local TCP port → communicates via Android’s network stack
• Responses flow back through ADB.kt → ViewModel → UI updates
• QSTile service can launch pairing/activity flows
• Bookmarks stored/retrieved via ViewModel → persistent storage (SharedPreferences)
Architectural patterns / design principles
• MVVM: activities/fragments observe ViewModels
• Separation of concerns: UI vs business logic vs native code
• JNI boundary: native ADB server binary invoked from Kotlin
• Android Jetpack components: ViewModel, Lifecycle
Summary
• MVVM separation and JNI boundary.