rquickshare-x is a fork of the original rquickshare project.
This fork currently adds:
- Windows support (builds + installers)
- Dark mode
- Live transfer speed meter
- ETA during transfers
The goal is to provide a practical open-source NearbyShare-compatible desktop app while continuing to improve usability and cross-platform support.
You simply have to download the latest release.
Important notes:
- The minimum GLIBC version supported is included in the pkg name.
- You can check yours with
ldd --version.
- You can check yours with
- RQuickShare was distributed with two versions (main & legacy) up until v0.11.5:
- Legacy is for compatibility with older Ubuntu versions: here.
- Main is for future support of newer versions of Ubuntu.
Simply install the .dmg.
Note that you may have to first allow the app to install under Settings > Privacy & Security > Security (you should see a dialog asking for permission)
Install the .msi or .exe package from the latest release and run it.
RQuickShare requires one of the following libraries to be installed:
libayatana-appindicatorlibappindicator3
The files should (in theory) install those dependencies by themselves, but if this is not the case you may have to install those manually.
sudo dpkg -i rquickshare-x_${VERSION}.debsudo dpkg -i rquickshare-x_${VERSION}.debsudo rpm -i rquickshare-x-${VERSION}.rpmsudo dnf install rquickshare-x-${VERSION}.rpmAppImage is a little different. There's no installation needed, you simply have to give it the executable permission (+x on a chmod) to run it.
chmod +x rquickshare-x_${VERSION}.AppImageYou can then either double click on it, or run it from the cmd line:
./rquickshare-x_${VERSION}.AppImageUnofficial Installation Methods
For Arch Linux, you can install it from the AUR by using an AUR helper like yay:
yay -S rquickshare-xAvailable here: NixOS
A nix-shell will temporarily modify your $PATH environment variable. This can be used to try a piece of software before deciding to permanently install it.
$ nix-shell -p rquickshare-x- Wi-Fi LAN only. Your devices need to be on the same network for this app to work.
Make sure both your devices are on the same WiFi network. mDNS communication should be allowed on the network; this may not be the case if you're on a public network (coffee shops, airports, etc.).
For some reason, Android doesn't broadcast its mDNS service all the time, even when in "Everyone" mode.
The first solution (implemented in RQuickShare for Linux) is to broadcast a bluetooth advertisement so that Android will then make its mDNS available. Of course, for this you need to have bluetooth on your laptop/desktop. If you don't have that, continue reading.
As a workaround, you can use the "Files" app on your Android device and go to the "Nearby Share" tab (if it's not present, continue reading).
A second workaround is to download a Shortcut maker (see here) to create a shortcut to the particular intent:
-
Method A:
- Activity:
com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity
- Activity:
-
Method B:
- Action:
com.google.android.gms.RECEIVE_NEARBY - Mime type:
*/*
- Action:
Note: Samsung did something shady with Quick Share, so the above workaround may not work. Unfortunately, there's no alternative at the moment. Sorry.
TLDR: This is normal if you're just using bluetooth (as explained in the previous point).
Android will see that your laptop/desktop is trying to share a file and will reveal itself. But for some reason, Android will de-register its service from time to time and will only then be revealed again once it detects the bluetooth message again.
Make sure the app is really closed by running:
ps aux | grep rquickshare-xIf you see that the process is still running, it's because the app is not closed. This may be an intended behavior: when closing the window, the app won't stop and instead is still running and accessible via the system tray icon. However, if your distribution doesn't support/hasn't enabled this, it may be an issue for you.
If you want to really close the app when clicking on the close button, you can change that inside the app by clicking on the three dots and then "Stop app on close".
In this case, you may want to configure a static port to allow it in your firewall. You can do so by modifying the config file as follow:
# linux
vim ./.local/share/dev.mandre.rquicksharex/.settings.json
# mac
vim Library/Application\ Support/dev.mandre.rquicksharex/.settings.json
# windows (PowerShell)
notepad "$env:APPDATA\dev.mandre.rquicksharex\.settings.json"
# to be sure
find $HOME -name ".settings.json"Warning
The json must stay valid after your modification; for example, if "port" is the last item of the JSON it must not have a comma after it, otherwise the config will be reset.
{
...existing_config...,
"port": 12345
}By default the port is random (the OS will decide).
This happens for some users running Linux + NVIDIA cards.
The workaround is to start RQuickShare-x with an env variable defined as follows:
env WEBKIT_DISABLE_COMPOSITING_MODE=1 rquickshare-xAlternatively, you may try the legacy variant.
rquickshare-x is still in development (WIP). Support currently targets Linux, macOS and Windows. Keep in mind that the design may change between versions, so flexibility is key.
- Added Windows support (build + installers)
- Added dark mode
- Added live speed meter during file transfer
- Added ETA while transferring files
- Added fork-specific release/CI workflow updates
Got feedback or suggestions? We'd love to hear them! Feel free to open an issue and share your thoughts.
This project wouldn't exist without those amazing open-source project:
- https://github.com/grishka/NearDrop
- https://github.com/vicr123/QNearbyShare
- https://github.com/Martichou/rquickshare
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.