Skip to main content

August 27, 2026

Omnissa Horizon Client for Android Release Notes

Horizon Client for Android 2606 | 24 AUG 2026

With Horizon Client for Android, users can connect to and use remote desktops and published applications using an Android phone or tablet. Horizon Client for Android also supports Samsung Dex and Zebra devices.

IMPORTANT NOTICE: Changes to Support Lifecycle Dates

Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.

Note: The support policy for versions before 2606 remains unchanged.

MilestonePrevious PolicyPolicy from 2606 Onwards
EOA / EOGSGA + 36 monthsGA + 18 months
EOTGEOGS + 12 monthsEOGS + 12 months (unchanged)

What's New

Horizon Client for Android 2606 is released along with Horizon 8 2606.

  • Blast Networking - Open SSL 3.5 Upgrade

    Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

  • Updated Protocol for Client Connections

    Blast is now the only supported protocol for client connections. PCoIP is no longer available as a selectable protocol in the Horizon Client UI (Desktop and Mobile). Command-line options that previously accepted a protocol value (-appProtocol, -defaultProtocol) are retained for backward compatibility, but now only accept Blast. When PCoIP is specified, a message displays directing you to reconnect using Blast. PCoIP remains supported on Horizon Agents for zero client connections at this time.

Before You Begin

  • Horizon Client for Android is supported with the following deployment types:

    • Horizon 8 version 2006 and later

    • Horizon Cloud in Microsoft Azure

    • Horizon Cloud Service - next-gen

  • Horizon Client for Android requires the Android 14, 15, or 16 operating systems.

  • When you install Horizon Client for Android, you are prompted to let the app read phone status and identity. This prompt relates to the RSA soft-token integration feature. The prompt is requesting permission to read the state of the phone. This permission does not allow the app to make a phone call or send a message. You can safely grant this permission.

  • Install and upgrade Horizon Client for Android just as you do any other Android app. For example, you can get the latest version of the app from Google Play or the Amazon Appstore for Android. For a link to the Horizon Client app in one of these stores, go to the Horizon Client Downloads page.

Resolved Issues

There are no resolved issues in this release.

Known Issues

The following sections describe known issues related to the operation and performance of Horizon Client for Android.

For known issues specific to the use of Horizon Client in a Horizon Cloud Service - next-gen environment, see the Horizon Cloud Service - next-gen Release Notes.

  • Android Dex multi-monitor mode does not work

    Applications are unable to display windows on both the Device screen and the Dex screen at the same time. This occurs on all Android 14 phones with the latest updates.

    Workaround: None.

  • User input displays on suggestion bar of keyboard when using Horizon Screen Keyboard to enter letters or numbers in the password input box of the Windows Lock screen.

    Workaround: There are two ways to address this issue.

    • Disable Predictive Text on mobile device settings, or
    • Switch to Direct Touch mode and enable Windows Native Touch Gestures in Client Settings. Wait for the Windows keyboard to automatically pop up and then use the Windows keyboard for password input.

  • When the Samsung DeX “New” view mode is selected, the Android taskbar will only display the Horizon client main window.

    When this problem occurs no remote session window displays on the taskbar. Any minimized session windows cannot be restored and are therefore inaccessible.

    Workaround: None.

  • On certain Android devices, when you use the client drive redirection feature to copy, rename, or create files on a redirected external SD card, you receive the error "You need permission to perform this action."

    This problem occurs if the Android device prevents third-party apps from getting automatic permission to put files on an external SD card.

    Workaround: None.

  • If you use a NAT64 network that is shared from a macOS 10.14 or later system, internet access is not available on an Android device and Horizon Client for Android cannot connect to a server.

    Workaround: Use an earlier macOS version to share the NAT64 network, for example, use macOS version 10.11.6.

  • When you connect to a remote desktop with the High Quality Mode option enabled, if you change the resolution from the Auto-fit resolution option to another resolution in the Horizon Client settings, and then change the resolution back to the Auto-fit resolution option, Horizon Client uses the wrong resolution.

    Workaround: Log off and reconnect to the remote desktop.

  • When you use the Horizon Blast display protocol to connect to a remote desktop or published application with a non-English input method, you might not be able to enter certain symbols.

    Workaround: Use the local input buffer, or connect to the remote desktop or published application with the PCoIP display protocol.

  • On some Android devices, certain keys introduce white spaces when you connect to a remote desktop and input text with Horizon Client.

    Workaround: Turn off predictive text for the keyboard in the Android Settings app.

  • The Unity Touch sidebar cannot show changes in the All Programs menu for new software that you install during that same session.

    Workaround: To see items for new software that you recently installed, disconnect from the desktop and then connect again.

  • Because an Android device does not have a persistent ID, the device's MAC address is used to generate an ID for the license. If a device's MAC address cannot be detected, its SIM is used instead. If neither the MAC address nor SIM can be detected, a random ID is generated for the device. In certain circumstances, this process can result in multiple licenses being issued to the same device.

    Workaround: An administrator can remove the inactive licenses.

Documentation

Horizon Client for Android documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs

For details on Omnissa's localization strategy, see Announcing Omnissa Localization Support.

Support Contact Information

To receive support and learn more about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and via Cloud Services Portal, see KB 6000005.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…