-
Notifications
You must be signed in to change notification settings - Fork 417
- My setup didn't work, how can I send info about my system? Log for support
- What dependencies are required for ubuntu? Ubuntu requirements
- Is my hardware supported? Checking hardware
- How to run on a raspberry pi? raspberry pi instructions
- Failed to create interface p2p-dev-wlan0: -16 (Device or resource busy): bring down wifi interfaces
- Why bother, there's chromecast out there: Miracast vs Chromecast
- Is miraclecast compatible with Windows: [Microsoft OS support][microsoft-os-support]
Check it running res/test-hardware-capabilities.sh
$ sudo journalctl -f |& tee journal.log
$ sudo miracle-wifid --log-level trace |& tee wifid.log
$ sudo miracle-sinkctl --log-level trace --log-journal-level trace |& tee sink.log
add wifid.log, sink.log and journal.log to a zip and upload to a new or existing issue. Is handy to include exact command line used miracle-wifid --log-level trace miracle-sinkctl --log-level trace run 3 etc.
Security concerns: If you're afraid to upload your mac address on logs, add this filter before tee
sed 's/..:..:..:..:..:../00:00:00:00:00:00/g'
to hide your mac address.
To provide logs for dbus you can use
$ sudo dbus-monitor --system |& tee dbus.log
- ubuntu-restricted-extras
- gstreamer1.0
- libglib2.0-dev
- libreadline-dev
- libudev-dev
- libsystemd-dev
- libusb-dev
- build-essential
optional:
- git
- check
- cmake
See details on raspberry pi 3
Failed to create interface p2p-dev-wlan0: -16 (Device or resource busy)
Means that interface used by miraclecast is not ready to use. Normally that means that something (many times miraclecast) left a wireless interface configured without p2p
Check if something restarted normal wifi config. It's easy to detect because wpa_supplicant spawned by miracast has a control interface socket configured by '-C /run/miracle/wifi/...' and wpa_supplicant by network managers normally was a '-u' (dbus interface)
Depending on your system there will be a series of services and target that tries to reconfig wpa_supplicant if you just kill it:
$ sudo systemctl stop NetworkManager
$ sudo systemctl stop network
one of them should work. You can enable again after use miraclecast with:
$ sudo systemctl start NetworkManager
$ sudo systemctl start network
Many people see these technologies as similar but they are far from being the same, although the final result seems pretty similar.
Chromecast and other technologies (like AirPlay9 are based on have all the devices under same Wifi (i.e using an AP), while miracast is based on Wifi-Direct (No AP). This results in two devices communicating with the security level they decide two provide (maybe none at all), instead of allowing access to a local network to unknown devices. Miracast is too a battery drainer for this reason, as the need to keep communication working all the time
Windows support is still a WIP. You can find PR on #136. It is just a Q&D from reverse enginnering sessions from microsoft implementation. Is tested against Windows 10, but people reports it works with Microsoft wireless display adapter too. Feedback wellcome