What Zima Client Android 1.5.2 Beta Changes
Zima Client Android 1.5.2 Beta is a broad mobile-client update rather than a single feature patch. The community announcement describes a redesigned interface, Dark Mode, a rebuilt Photos workflow, expanded file operations, improved remote connections, multi-device management, NAS Profile, app management, sub-account sign-in, biometric login, and 29-language support.
For current download and platform context, use the official ZimaOS download page and the current Shop overview of Zima Client connectivity.
What to Test First
Because this is a beta build, the most useful test order is to validate the workflows that can affect access or data movement before cosmetic details. Start with sign-in, local discovery, remote connection, Photos sync destination, uploads and downloads, then verify device switching and app controls.
- Photos: confirm the selected source albums and destination folders before enabling mobile-data sync.
- Files: test upload, download, copy, move, rename and delete with non-critical files first.
- Remote access: compare LAN, Remote ID, Direct IP and VPN behavior while switching networks.
- Multi-device: verify that cached file lists, apps and NAS Profile data stay attached to the correct server.
Beta-Specific Issues Reported by Community Testers
The thread includes useful early feedback. One tester reported that manual language selection did not behave as expected, while another reported stable LAN and remote connections, working photo upload and file browsing, but also noticed live-metric refresh behavior and sign-in persistence. A later reply reported frequent crashes during remote connections and concerns about photo timestamp preservation. These are community observations, not guarantees that every device will reproduce the same behavior.
Android's own guidance on secure biometric flows is available in the Android biometric authentication documentation. For beta testing distribution, Google's official Play testing workflow is described in the Google Play testing documentation.
How to Join the Android Beta
- Join the ZimaOS Android Google Group used by the beta program.
- Open the Google Play beta testing link with the same Google account.
- Install or update Zima Client from Google Play.
- After updating, confirm the app version before reporting a bug.
If you are evaluating Zima Client as part of a broader personal-cloud workflow, the current Zima Client smart connector guide explains how mobile access fits with desktop and remote workflows.
How to Report a Useful Beta Issue
A reproducible report should include the phone model, Android version, ZimaOS version, connection method, exact steps, screenshots or screen recordings, and the visible error message. Also state whether the issue occurs on LAN, remote access, or both. This distinction helps separate a mobile UI bug from a path-selection or network problem.
FAQ
Should I use the beta on my only production phone?
Use caution. The community announcement explicitly labels this build as Beta, so instability is possible. Keep a stable access path to your ZimaOS device before relying on the beta for essential file access or backups.
Does biometric login replace the ZimaOS account?
No. Biometric login is a local sign-in convenience on the Android device; it does not remove the underlying account and authorization model.
Where can I check the current Zima ecosystem rather than the beta snapshot?
Use the current ZimaOS page and Shop device-connectivity page rather than assuming every beta item remains unchanged after release.
