ARKTOR Android
Turn an Android phone or tablet into a controlled ARKTOR endpoint. Today the device works through the ARKTOR workstation or local server path for chat, vision and approved device actions. The longer-term direction is a direct, policy-controlled connection to compatible frontier or local intelligence.
Who this product is for
Users and prototypes that need an AI endpoint on Android with persistent interaction, vision and controlled device capabilities under normal Android permissions.
The decision moment
The AI needs to operate where the phone, tablet or Android-class endpoint is, while platform consent and device boundaries must remain visible.
One Android product line, with the intelligence hosted where it fits.
Today ARKTOR Android uses the existing workstation or customer-local server path to reach the model and ARKTOR control layer. That already makes phones, tablets and Android-class endpoints useful as mobile interfaces and execution points. Direct connection to compatible frontier or local intelligence is a future product direction, not a current release claim.
What users can already do
- Create, open, switch and rename persistent chats
- Change supported models without losing the active conversation context
- Send images through a real vision workflow with preview and persistence
- Use approved Android capabilities and receive human-readable results
- Keep DE, EN or system-language preference across the tested lifecycle
Phone and automotive endpoints have both been exercised
The stable phone workbench baseline is 0.8.7. The retained reference proof used a physical 2019 Android phone. A separate Android 13 automotive/AI-TBox endpoint has also been physically tested.
Continue after a mobile-network reconnect.
See the evidence-backed scenario: Continue an Android AI workflow after mobile-network reconnect →
0.8.9 passed the Automotive Workbench E2E path over independent LTE.
The physical Android 13 automotive endpoint passed transport, reconnect, fresh Chat and a read-only device-tool workflow while retaining the expected ARKTOR identity.
Evidence boundary: this proves the tested ARKTOR app and Workbench path, not vehicle telemetry, CAN, ECU or safety-critical control.
Advanced prototype, not a general Android release.
- 0.8.7 remains the phone-workbench reference; 0.8.9 is the accepted automotive E2E baseline
- Broader Android-device coverage and public onboarding are still release work
- Android permission, consent, sandbox and lock-screen boundaries remain authoritative
Transport recovery and application recovery are different claims.
Read the physical 0.8.8 lesson and the practical guide to separating transport failures from application failures.
Physically validated Android product workbench with accepted 0.8.9 automotive Workbench E2E proof. Not yet offered as a general public Android release.