Android Environment
Install, launch and sign in
Apps live inside the persistent Android emulator. AURA can search Google Play, learn each app, and reuse saved routes later.
Find an Android app
AURA opens the Play Store inside the emulator. Pressing Install is treated as a consequential action and needs confirmation when done by voice.
Secure sign-in vault
On Windows, values are encrypted with DPAPI and never sent to Qwen. AURA only sees slot names such as username or password.
Installed apps
Launch directly or tell AURA what you want done.
AURA’s persistent state tree
This is the fast layer in front of Qwen: live variables, notifications, app screens, learned transitions and reusable routes.
Priority context
Live variables
Connected app state trees
Each app remembers screens, learned actions and reusable routes. New layouts create new branches instead of overwriting working knowledge.
Learned action graph
Recent events
Persistent Android + local AI
Android emulator
Repair cold-boots the same persistent AVD with a stable renderer and wakes the virtual display. It does not use -wipe-data.
AURA Android Companion
The companion provides AccessibilityNodeInfo trees, semantic text entry and notifications over an Android-loopback server reached only through ADB forwarding.
Local AI
The context index handles known state first. Qwen is used mainly for novel intent or changed app screens; structured-output repair prevents malformed model text becoming Android actions.
Voice
Speaker familiarity helps ignore background speakers. Acoustic delivery cues can tune interaction pacing, but AURA does not infer emotions from a voice.
Runtime Doctor
Deep checks test ADB, Android boot/display, screen streaming, the companion bridge and an actual structured Qwen response.
Remote portal safety
Hugo OS should expose only HTTPS through its reverse proxy. The emulator, ADB, Ollama and companion ports remain loopback/local and are never forwarded directly to the internet.