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
Tell AURA the outcome, for example “Install Facebook”. It keeps working until Android verifies the app is installed. An explicit install request authorises that free Install action; purchases and subscriptions remain separately gated.
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. Qwen itself is stateless between planner turns; this tree is the memory.
Action Tree files
Export this file to review or send for debugging. Import/Replace restores a reviewed tree. Reset removes learned routes/habits but keeps AURA’s built-in Android skills. A local backup is created before import/reset.
Debug exports now include a bounded Decision / Prompt Audit showing the user prompt, screen/app context, planner snapshot, model output and executed actions. Vault values, sessions, notifications and voiceprints remain excluded.
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.
Action Tree Map
Green roots are pre-trained Android skills. App screens and verified routes grow automatically as AURA learns.
Route details
Tree quality
Checks for state-capture races and suspicious unverified routes before they can influence AURA.
Decision / Prompt Audit
Shows why AURA chose a route. Useful when exporting the Action Tree for debugging.
Recent events
Persistent Android + adaptive AI
Checking hands-free runtime…
AURA uses independent lanes for speech, reasoning, Android semantics, input and the live display. A failure in one lane should degrade gracefully rather than taking the whole assistant down.
Android emulator
Repair restarts the same persistent AVD only when needed. Performance mode reduces animation overhead and prefers hardware-accelerated emulator settings. 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.
Google Play + Android storage
Normal repair keeps your Google account and installed apps. Deep repair resets only Play Store and Download Manager state; it never clears Google Play Services/account data.
Local AI
Python owns the persistent context and control loop. Qwen receives a fresh, bounded state snapshot for each planner turn and keeps no conversation history between turns; model weights stay warm only for speed.
Gemini coordinator · lightweight local fallback
With Cloud preferred selected, AURA keeps deterministic Android controls local but uses Gemini as the active planner for novel/multi-step work. Passwords, vault values and editable-field contents are redacted. Screenshot pixels leave the machine only when Gemini screen vision is separately enabled.
Voice
Speech recognition and spoken readback are core access features. Speaker familiarity is an optional background-speaker filter; it is not required for voice control and a false value there does not mean speech is broken.
Runtime Doctor
Deep checks test ADB, Android boot/display, screen streaming, the companion bridge and an actual structured Qwen response.
Install AURA as a web app
Install the full AURA interface to your home screen/desktop for a standalone app window, microphone access and one-tap launch. Android control still stays on your own AURA server.
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.