ARKTOR Android
ARKTOR Android brings the operational AI experience to Android devices: persistent chat, vision, model choice and controlled device capabilities, while Android permissions and human approvals remain part of the product instead of being hidden behind the demo.
One Android product line, not a phone-brand demo.
ARKTOR Android is designed around Android itself. Phone, tablet and automotive-class Android endpoints can use the same product direction while each device keeps its own permissions, hardware limits and transport requirements. Individual test devices are evidence, not the brand.
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 reference physical proof used a Huawei P30 Pro. It is test hardware, not the ARKTOR Android product identity. A separate Android 13 automotive/AI-TBox endpoint has also been physically tested.
Evidence boundary: app and display operation do not imply CAN, ECU or safety-critical vehicle-control authority.
0.8.8 restored the intended remote Android path over independent LTE.
The latest physical automotive acceptance proved the Android endpoint online over its independent mobile-data connection with the expected ARKTOR identity and local capability set. That closes the transport regression discovered during testing.
Still open: a separate chat/model/backend UI issue seen after transport recovery has not yet been root-caused. Transport proof and chat-workflow proof remain separate claims.
Advanced prototype, not a general Android release.
- The 0.8.7 phone workbench remains the protected UI/UX reference while 0.8.8 carries the accepted automotive transport recovery
- Broader Android-device coverage and public onboarding are still release work
- The automotive chat/model path still needs independent closure after the transport fix
- Android permission, consent, sandbox and lock-screen boundaries remain authoritative
Physically validated Android product workbench and automotive transport proof. Not yet offered as a general public Android release.