Mirror and control Android devices from Windows, macOS, or Linux. FreeControl adds saved devices, wireless pairing, visual scrcpy settings, and per-device options. Free and open source under MIT.
Replies
Best
Maker
📌
Hi Product Hunt, I'm the developer of FreeControl.
FreeControl gives Android mirroring a desktop interface for the parts around the session: choosing a device, keeping its settings, pairing over Wi-Fi, and checking output when something goes wrong. scrcpy does the actual mirroring and control.
You can start with one set of global options, then give a particular device different settings. Those overrides can be switched off without losing them. The interface also keeps the scrcpy option names visible, so using the GUI doesn't mean losing track of the underlying tool.
It's free and MIT-licensed, with Windows, Linux, and macOS builds. You still need to enable debugging on your Android device. scrcpy and adb are downloaded separately from inside the app, or you can use an existing runtime directory. macOS builds are not notarized and may need first-launch approval.
I'd be interested in feedback on the first connection: is it clear how to get from opening the app to seeing your device?
Replies
Hi Product Hunt, I'm the developer of FreeControl.
FreeControl gives Android mirroring a desktop interface for the parts around the session: choosing a device, keeping its settings, pairing over Wi-Fi, and checking output when something goes wrong. scrcpy does the actual mirroring and control.
You can start with one set of global options, then give a particular device different settings. Those overrides can be switched off without losing them. The interface also keeps the scrcpy option names visible, so using the GUI doesn't mean losing track of the underlying tool.
It's free and MIT-licensed, with Windows, Linux, and macOS builds. You still need to enable debugging on your Android device. scrcpy and adb are downloaded separately from inside the app, or you can use an existing runtime directory. macOS builds are not notarized and may need first-launch approval.
I'd be interested in feedback on the first connection: is it clear how to get from opening the app to seeing your device?