soobujmiah
CVServices
Background map focus: London

04 — Featured Work

Selected projects with CI and device evidence.

012024–26

LAI

Bangla-first local AI + consent-driven automation

Source-only Android runtime for private on-device LLM inference and Accessibility-gated automation. CPU inference device-validated; GPU/NPU in qualification.

Evidence: Real arm64 llama.cpp CPU inference, 12–20 tok/s decode, KV-prefix reuse. Root-cause diagnosis of an Adreno Vulkan driver crash that shaped a fail-closed CPU-default architecture.

Kotlinllama.cppVulkanAccessibilityShizukuGGUF
022024–26

GGEN

Android-first creative & document studio

Flutter/Dart foundation for professional vector, raster, document, and PDF work. Documentation-first architecture with pure-Dart core and SHA-256 state integrity.

Evidence: 143 pure-Dart unit tests, 353 widget/controller tests. Validated on a physical device round after round.

FlutterDartDocument GenerationVector Graphics
032023–26

ADT

Native ARM64 Android development toolchain

Explore ↗

Builds Android SDK build-tools and platform-tools from AOSP source for Linux ARM64/glibc. SHA-256-verified offline release artifacts.

Evidence: Full ARM64 native APK pipeline validated end-to-end on Snapdragon 8s Gen 4: source → APK → sign → install → JNI load → run.

AOSPARM64Build ToolsCross-compilation
042023–26

Ternux

No-root Debian/Xfce Linux desktop on Android

Explore ↗

Installs a real Debian ARM64 userspace, Xfce4 desktop, Termux:X11 display, PulseAudio bridge, and Zink/Turnip GPU route — one command, no root.

Evidence: Zink/Turnip renderer confirmed on Adreno 825: glmark2 score 140 (OpenGL 4.6), with a documented compatibility fallback route. Blender 4.3.2 launched, but its own report still named device type SOFTWARE — only the viewport OpenGL path through Zink/Turnip is proven, not Cycles GPU rendering.

DebianVulkanTurnipZinkAdrenoPRoot
Now building — P0 release trackSongjogBengali-first business and institution operations app. Owner Edition: fast daily entry, local SQLite records, auditable corrections instead of destructive deletes.94 tests green on CI · export/diagnostics device-validated on the Redmi Turbo 4 ProFollow the build ↗
One physical Android device

ADT and Ternux are two halves of the same Android/ARM64 workflow.

One physical Android device, two complementary toolchains. ADT turns it into an Android development workstation — build, sign, install, debug. Ternux turns it into a Linux ARM64 desktop — Debian, Xfce4, GPU acceleration. Neither needs a conventional PC, and both are maintained as independent repositories with their own documentation and evidence.

ADTAndroid development layer

Native aarch64 build-tools and platform-tools from AOSP source: build, sign, install and inspect real APKs from the phone itself.

Explore ↗Code ↗
TernuxLinux desktop layer

A real Debian ARM64 userspace with an Xfce4 desktop and an explicit graphics route, installed on the same device with no root.

Explore ↗Code ↗

Verified: Both toolchains were validated on the same physical device — a Redmi Turbo 4 Pro running Termux and PRoot Debian. Ternux installs that Debian desktop; ADT runs inside it and produced, signed and installed a real APK end to end.

Not yet proven: Joint automation, shared build orchestration and a GPU-assisted build path are not yet in place. Each project is validated on its own evidence rather than on a combined pipeline.