If the setup steps aren't followed correctly, HoppyShare may get stuck in a "half-installed" state. A common problem is when HoppyShare doesn't relocate itself from the downloads directory. The fastest fix is to completely remove it and reinstall fresh.
~/.local/share/keyrings/
. If it is locked, delete and recreate the keyring.%LOCALAPPDATA%\HoppyShare\HoppyShare.exe
.~/Library/Application Support/HoppyShare/HoppyShare
.~/.local/bin/hoppyshare
.~/.config/autostart/
.No. If you visit hoppyshare.com/add-device/mobile
on your phone, a device will be added—but the mobile setup won't complete from the browser. The process only works when it's started inside the Android app.
Not yet—iOS is coming soon. For now, only the Android app is supported for mobile devices.
BLE implementation on android is still a work in progress.
Hoppyshare is not aware of the type of device that is registered. Thus, while the web gui shows all the settings for an Android device, the mobile app itself only listens for the following settings:
While the windows implementation of BLE can receive messages from other devices, it cannot send messages. It is also a bit buggy and may take a while to discover peers.
Clients must have the following installed:
After installing, ensure it is running:
gnome-keyring-daemon --start --components=secrets
Set required environment variables (GNOME_KEYRING_CONTROL) or alternatively try dbus-launch
Optionally, test storing:
secret-tool store --label="test" application test
Then retreiving the key:
secret-tool lookup application test
For Wayland:
wl-clipboard
For X11:
xClip