back to home

iiordanov / remote-desktop-clients

VNC, RDP, SPICE, and oVirt/RHEV/Proxmox Clients for Android and Blackberry 10

2,403 stars
590 forks
162 issues
JavaCKotlin

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing iiordanov/remote-desktop-clients in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/iiordanov/remote-desktop-clients)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Intro This is the source code for bVNC, aRDP, aSPICE and Opaque, four remote desktop clients for Android. Please see the LICENSE file for information on how the source is licensed. Android App Store Links bVNC is a VNC client. It's released as a donation version at bVNC Pro, and as a free version at bVNC and IzzyOnDroid aRDP is a RDP client. It's released as a donation version at, aRDP Pro and as a free version at aRDP and IzzyOnDroid aSPICE is a SPICE Protocol client. It's available as a donation version at aSPICE Pro, and as a free version at aSPICE Opaque is an oVirt, RHEV, and Proxmox client available at Opaque The donation versions are also available on Amazon App Store at bVNC, aRDP, aSPICE, Opaque. Apple App Store Links bVNC Pro is available at bVNC Pro. aRDP is available at aRDP Pro aSPICE Pro is available at aSPICE Pro. Find bVNC Pro, aRDP Pro, and aSPICE Pro for MacOS and iOS source code here Links to Pro APKs You can always get the latest Pro versions by supporting us as a Patreon member and keeping your membership active! bVNC Pro aRDP Pro aSPICE Pro Opaque Releases You can find all free Android APK files here Building There are different ways to build the applications depending on OS and whether you are using pre-built libraries, or building them from scratch. On Linux and WSL2 These instructions should work on Ubuntu 18.04, 20.04, and Windows Subsystem for Linux 2. Builds are likely to also work on MacOS, feedback is welcome. Pick one of I-a, I-b, or I-c below, then move onto II. I-a With Prebuilt Libraries Building the projects with pre-built dependencies. ./download-prebuilt-dependencies.sh ./bVNC/prepare_project.sh --skip-build libs nopath I-b From Scratch with Docker Make sure you're running the commands below from the root of the project. Ensure ANDROID_SDK is set to the path to your SDK. I-c From Scratch Building from scratch and working in Android Studio. • Install some packages. On Ubuntu: apt install gnome-common gobject-introspection nasm gtk-doc-tools python-is-python3 • On Linux, install Android Studio • Install Android SDK from Tools -> SDK Tools • Install Android SDK command-line tools and CMake from the SDK Tools tab • Ensure that the path to ANDROID_SDK is ${HOME}/Android/Sdk/ and correct below if necessary • To build the projects • If building a non-custom client, set PROJECT to libs. For a custom VNC client, set PROJECT to a string that stars with Custom and contains Vnc, i.e. (see III below for details). • Set the environment variables ANDROID_SDK to your SDK installation. The scripts will install the NDK automatically. • Example: export PROJECT=libs # or CustomSomethingOrOther export ANDROID_SDK=${HOME}/Android/Sdk export PATH=$PATH:${ANDROID_SDK}/platform-tools/ export PATH=$PATH:${ANDROID_SDK}/tools • Accept all licenses (repeat if you see an error during build) ${ANDROID_SDK}/cmdline-tools/bin/sdkmanager --licenses • Then, run the build script which takes hours to run. E.g.: ./bVNC/prepare_project.sh $PROJECT $ANDROID_SDK • Switch to Android Studio, select the launch configuration you want to run, and run it on an emulator or device. • If using an emulator, choose x86_64 as the architecture to avoid "has text relocations" errors loading gstreamer on Android. On Windows with Git Bash These instructions are for Windows without WSL2 installed. For now, only pre-build dependencies are supported in this configuration. • First download and install git from here • Then, start Git Bash, clone this project, cd into the project root directory and run: • Start Android Studio and open the project directory • Click File->Sync Project with Gradle Files • If Android Studio reports any missing android versions (such as , for instance), find and start SDK Manager and ensure any missing Android versions are installed. As of today, the required versions are , , and , but in future other versions will need to be installed if Android Studio shows an error. II Importing projects into Android Studio This should be as simple as selecting "Open an existing Android Studio project" on the Welcome screen, browsing to the remote-desktop-clients directory and selecting it. • One final tweak is necessary to the (external) freeRDPCore project before the project can build. Double-click "Gradle Scripts" on the left, and open build.gradle (Module freeRDPCore). Change minSdkVersion to 11. • Build -> Make Project should now work. Custom Certificate Authority You can add custom CAs for aSPICE and Opaque in remoteClientLib/certificate_authorities/. They will be merged with the ca-bundle.crt provided to the app to validate your self-signed server certs if you have any. Generating Keyboard Layouts for aSPICE and Opaque The directory contains a utiliy that can be used to generate new layouts for the desktop clients. If you would like to add a layout, the best way to do so would be to create a file with the correct format in . Ideally, you should submit this file to the qemu project so everybody would be able to benefit from the new layout. III Building "Custom" VNC clients It is possible to programmatically build additional customized clients based on the VNC client contained in this project without altering any of the source code of the project. • Pick a unique identifier for your app. It will become part of the (application ID)[https://developer.android.com/studio/build/application-id] of the app. For example, say you pick YourVncClient. The application ID will be com.iiordanov.YourVncClient. • Place a configuration file in yaml format (note - with filename matching your resulting application ID) at • Use the file as a starting point. The numbers after each field are one of View.INVISIBLE or View.GONE and it controls whether the field is invisible or gone in the customized interface. • See [https://developer.android.com/reference/android/view/View.html#GONE] for the numeric value of View.GONE and [https://developer.android.com/ref…