Skip to content
yom-chadashPublic

About

Run Android apps on Windows as native processes — no emulator, no VM

Resources

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

Gesher Logo

Gesher

Run Android apps on Windows as native Windows processes — no emulator, no virtual machine.

Gesher (Hebrew: bridge) is to Android what Wine is to Windows: a compatibility layer. Double-click an .apk, and the app runs in an ordinary window, at native speed, with no hidden VM and no Android image to boot.

Release: v0.1.0 — Native execution of Android applications on Windows with ART JIT, HWUI/Direct3D acceleration, WASAPI audio, Camera/Location subsystems, microG GMS stubs, ARM64-to-x64 binary translation, and seamless desktop integration. See the architecture overview.

How it works

Instead of rewriting Android, Gesher compiles the Android Open Source Project's own runtime and framework for Windows and replaces only the layers that talk to the Linux kernel:

 .apk ─► APK loader       manifest, resources, dex, native libs
         ART (with JIT)   Android's own Java runtime, ported to Windows
         framework.jar    the real Android framework
           └ system services re-implemented in-process
         HWUI + Skia      → OpenGL ES → ANGLE → Direct3D 11
         native .so       ELF loader + bionic on Win32 (+ arm64 translation)
         integration      windows, input, IME, clipboard, files, notifications

Full design: docs/architecture.md.

The November 16 performance follow-up adds measured audio, path, WebView, camera, framework-build and dashboard-row improvements, with independent QA and Windows/ART checks.

The November 16 performance audit records subsequent allocation, polling, camera, graphics, logging and desktop improvements, independent QA, actual Windows/ART checks and remaining limits.

The earlier runtime performance audit maps execution paths and records measured allocation, file-I/O and archive-scan reductions, frame-cache lifetime repairs, regression coverage and remaining work.

Compatibility

The November 16 runtime contract audit maps all tracked paths, records SDK/service/JNI review queues, and repairs socket, DNS, activity, binding, media lifetime and Bluetooth contracts with independent QA, reproducible evidence and explicit remaining Windows gates.

The November 14 contract audit maps every tracked path, refreshes the SDK and service/JNI review queues, and repairs pthread clocks, location completion, NSD values, media callbacks and Windows mouse-capture cancellation with independent QA and mandatory CI gates.

The Android/Windows contract audit maps every repository file, records SDK36 gap candidates, and repairs ELF lookup, memory advice, media ownership, audio negotiation, task snapshots and services. It includes independent regression controls, Windows gates and remaining gaps.

The lifecycle contract audit maps the runtime, records a fresh SDK inventory, and repairs network callbacks, message-port ownership, timers and media lifetimes with independent QA.

Android compatibility is partial. Apps can still fail on missing module APIs, native imports or backend behavior. The earlier compatibility audit records concrete crash-contract repairs, regression coverage and substantial remaining work; a successful build or symbol lookup alone does not prove that an arbitrary APK will run correctly.

The compatibility follow-up adds a repository map, exhaustive SDK gap lists, and focused service, filesystem and media repairs with independent regression controls and Windows gates. The earlier deep audit builds on that work with network and Wi-Fi data contracts, event-loop fairness, audio-state and native-window repairs, and a fresh combined SDK inventory that separates structural gaps from demonstrated failures.

Principles

  • No VM, no emulator. One Windows process per app.
  • Light. Nothing runs when no app is open.
  • No store. Gesher opens .apk files the user already has.
  • Respects the host. Networking and TLS use Windows' own certificate store, so content filters and corporate proxies work unchanged.
  • CI does the heavy lifting. Every build and test runs on GitHub Actions; contributors don't need a powerful machine.

Building

Requirements: CMake 3.24+, Ninja, Python 3, git, and llvm-mingw (works on Linux and Windows hosts). CI does all of this on every push.

tools/fetch-aosp.sh                       # pinned AOSP sources + Gesher patches
cmake -S . -B out -G Ninja \
  -DCMAKE_TOOLCHAIN_FILE=cmake/toolchain-llvm-mingw.cmake \
  -DLLVM_MINGW=/path/to/llvm-mingw
ninja -C out

Outputs include:

  • dalvikvm.exe: The ported ART runtime with JIT compiler.
  • gesher-exec.exe: App process host and launcher.
  • installer/gesher-setup-*.exe: Complete Windows installer and shell integration.

Tests: tests/build-test-apps.sh out/test-apps (needs a JDK), then tests/windows/run-tests.ps1 on Windows.

Updates

The Gesher Control Center checks GitHub Releases for stable updates and can download and install a newer version. Automatic checks can be disabled; installing requires confirmation and preserves installed Android apps and their data. See updating Gesher for behavior, release packaging and tests.

License

Apache License 2.0, the same license as AOSP. See decision 0001.


בעברית

‏גשר מריץ אפליקציות אנדרואיד על Windows כתוכנות רגילות, בלי אמולטור ובלי מכונה וירטואלית. המטרה היא כלי קל שפותח קובצי ‎.apk בלחיצה כפולה ומכבד את הסינון שמותקן במחשב.

גרסה v0.1.0 כוללת מנוע ART עם JIT, האצת חומרה HWUI/Direct3D, סאונד WASAPI, תמיכת מצלמה ומיקום, שירותי microG GMS, תרגום ספריות ARM64, ושילוב מלא בשולחן העבודה של Windows.

About

Run Android apps on Windows as native processes — no emulator, no VM

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages