Zima Client iOS v1.6.1 Release Notes

Zima Client iOS v1.6.1 is now available.

This update focuses on improving connection stability, file display, and app compatibility, along with fixes for several issues affecting everyday use.

:sparkles: What’s New

:one: Manual connections now support domains and custom ports
In addition to IP addresses, you can now connect using a domain name and specify a custom port, giving you more flexibility across different network environments.

:two: More stable device reconnection and switching
We’ve improved the device reconnection and switching process. Connections should now recover more reliably when switching between Wi-Fi, mobile networks, or other network environments.

:three: Improved file list display
We’ve optimized file list refresh and display behavior, fixing some cases where files might not appear correctly or the list status could become inconsistent.

:four: Improved app list and icon display
Compatibility across different ZimaOS versions has been improved, addressing issues where app lists or icons could occasionally display incorrectly.

:five: More fixes and improvements
We also fixed issues related to long-press file previews, login, and several UI details to improve overall stability and usability.

Download Link

Download the latest Zima Client and ZimaOS from our website:

Download ZimaOS and Zima Client

Questions or Feedback?

:e_mail: feedback@zimaos.com
:speech_balloon: Contact @Zima-777Spider

As always, thank you for your feedback and support. Please continue sharing your suggestions and reporting any issues on the forum. We’re listening!

Sincerely,
IceWhale Team

I tested Zima Client iOS 1.6.1 with my ZimaOS 1.6.2 system.

I can already confirm two improvements:

  • Web Links are working correctly now.

  • The previous folder display issue is fixed; I no longer see duplicate folders.

However, the reverse proxy issue is still not resolved.

When I configure my reverse proxy domain, the Zima Client automatically adds port 80 again, even though I enter only the domain without a port.

My reverse proxy uses standard HTTPS on port 443, so the automatically added :80 causes the connection to fail.

I will continue testing the other changes, but at this point the reverse proxy handling still does not work correctly for my setup.

1 Like

Can I confirm one detail: when you tested the reverse proxy connection, did you enter domain.com or https://domain.com in Zima Client?

I found an important detail.

When I enter the reverse proxy address using https://domain.com, the connection now works. I had not tested this exact format carefully before.

However, I have now encountered another problem.

When I open a Docker application that has its own reverse proxy configured, the Zima Client does not open the actual Docker application’s Web UI.

Instead, it opens the ZimaOS interface again.

So the connection to the reverse proxy itself works, but when I select a Docker application, the client appears to open the ZimaOS Web UI instead of the application’s configured Web UI.

The Docker application works correctly when I open its reverse proxy URL directly in a normal browser.

Could you please check how the Zima Client determines the Web UI URL when opening an application through a reverse proxy?

Could you please provide screenshots of the following two parts?

  1. The Docker settings page where you configured the reverse proxy.

  2. The mobile Profile page showing the domain information.

You can hide any sensitive or important information in the screenshots.

Also, I’d like to confirm: are the ZimaOS domain and the domain used by the Docker app two different domains?

Thanks for the screenshots and the detailed information! This issue will be fixed in next iOS version. :raising_hands:

1 Like

Video and Music Playback – External Player Support

I have another suggestion for improving the Zima Client’s media playback.

The built-in video player works for many files, but it cannot properly play the audio from some videos containing formats such as Dolby Digital or DTS.

I think there should be two possible solutions:

  1. Improve the built-in media player so that it supports more audio and video formats, including common surround-sound formats.

  2. Allow users to choose an external media player.

For example, when opening a video, there could be an option such as:

“Open with / Stream to…”

The Zima Client could then display the compatible media players installed on the iPhone or iPad, allowing the user to choose which player should handle the stream.

The same concept would be useful for music playback.

This would give users much more flexibility, especially because different media players support different codecs and audio formats.

Personally, I would prefer either a very capable built-in player or the option to select an external player. The important thing is that users should not be limited by the codecs supported by the Zima Client’s built-in player.

Please provide the following for targeted testing:

  • Original video file or an untranscoded sample

  • File extension, such as .mkv, .mp4, or .ts

  • Affected audio track number

  • Audio codec, such as AC-3, E-AC-3, TrueHD, DTS, or DTS-HD

  • Channel configuration, such as 5.1 or 7.1

  • Observed issue, such as no sound, distorted audio, or stuttering

Media Player Testing – MKV / Multichannel Audio and Orientation Issue

I have now tested the media player extensively with different video files and audio configurations.

I found a very clear pattern regarding multichannel audio:

MKV + 2-channel / stereo audio → works
MKV + 6-channel / 5.1 audio → does not work

I tested the same video with both 2-channel and 6-channel audio. The version with 2-channel audio works correctly, while the version with 6-channel / 5.1 audio does not.

I also tested multiple MKV files, and the same pattern appears consistently in my testing: 2-channel audio works, while 6-channel audio does not.

I found some additional issues as well:

Some MKV files play the audio but do not display the video correctly.
MPEG-4 files generally work correctly in my testing.

There is also a separate orientation-related issue shown in the screen recording I provided.

In portrait mode, I can access the audio/language selection normally.

However, when I switch to landscape mode, the player does not remain stable in the selected orientation. It keeps trying to switch between portrait and landscape, which makes it impossible to properly access and use the audio/language selection in landscape mode.

So the screen recording does not show that the audio selection itself is broken. It shows an orientation/UI issue that prevents the audio selection from being used properly in landscape mode.

The most consistent playback issue I found is still the difference between 2-channel and 6-channel / 5.1 audio: the same video works with stereo audio but not with 5.1 audio.

1 Like

We have recorded all the issues you reported and arranged fixes for them. Thank you very much for your thorough testing. Please verify in the next release!

Thank you for taking the time to review all the issues and for arranging fixes. I appreciate it. I will test them carefully again in the next release and report back with the results.

1 Like