Couldn't run MiracleCast on fresh installed Alarm repo

[zedeg94]

Hello.

After fresh install of MiracleCast Alarm image to my RPi3 B https://github.com/albfan/miraclecast/wiki/raspberry-pi-3 I've faced an issue. Logs attached:
miraclecast.zip
Sometimes, Miracle won't start with "Could not read interface p2p-dev-wlan0 flags: No such device", sometimes it says infamous "Failed to create interface p2p-dev-wlan0: -16 (Device or resource busy)".
It's fresh install, I ensure that wpa_supplicant isn't running before starting miracle-wifid.
Nothing additional is installed, no additional configs made either.

Can you advise something?

I've also tried to install Miraclecast to latest Raspbian, and it've been able to start and connect to Android device.
(Yet it was unusable, stream is incredibly laggy, with 5secs of delay and slideshow instead of video, so after reading trough this repository instructions and issues, I've decided to install your pre-made image.)

Thank you.

[zedeg94]

I've played around for a bit more, I think some logs should help...

log2 - Running miracle wifid and sinkctl just after startup (miracle is not updated yet)
logs from journalctl, wifid, sinkctl
log2.tar.gz
log3 - Running miracle wifid and sinkctl after Yaourt (updated, no reboot inbetween this and log2)
logs from dbus, journalctl, wifid, sinkctl
log3.tar.gz
log4 - Running miracle wifid and sinkctl after startup (rebooted after log3)
logs from dbus, journalctl, wifid, sinkctl
log4.tar.gz

(Haven't read trough logs closely yet)

On fresh start I'm able to see Miracle on my Android, but when I try to connect - it results to timeout.
After that, Miracle won't appear on devices list and, interestingly enough, there's no wpa_supplicant/network.target/networkd.service running, or wlan0 listed on ifconfig result.

[albfan]

I see this many times. There must be something not cleaned after stop casting. But not sure what it is.

[zedeg94]

There must be something not cleaned after stop casting.

The main problem for me is not inability to reconnect. For now, at-least.
The main problem is inability to connect at all. Even when I try to connect after startup, it always results to Timeout.
(On my raspbian-attempt, I've been able to connect succesfuly and stream Video/Audio, yet with huge lag/stuttering)

[albfan]

I guess only with info from both side we can make some conclusion, probably devices now each other and do the pair in a different way.

Now there's --log-date-time so we can match pair traces and see why it refuses to connect.

I think when miraclecast is Group owner sometimes it fails to connect