-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing raspberry pi 3 with miraclecast #100
Comments
must have something to do with #79 :( my rpi3 and so on.. I don't want to shutdown all interfaces just to bring miracast up.. This stuff is kind of hacky :P |
Did you test all the gst plugins are installed with: https://github.com/albfan/miraclecast/blob/master/res/test-viewer.sh I guess that is the problem |
I had everything installed. and tested with http://localhost:1991, when i am back home i send you some logs. |
My specs: |
I have an archarm with mate desktop (gtk2) vnc ssh and miraclecast ready to go. I'm planning to release it to community. Are you avaliable as beta tester. (It should work out of the box, but maybe other eyes see things I forgot) |
Yes, i would really like to be betatester .. and please send me your PayPal adress, i want to send 20€ to you for your support.. thank you |
Terrific! Here is the image Install with (check your sdcard dev with
More instructions on https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=46911 It must run out of the box I would use funds in research (I want to explore the touch screen for easy setup raspberry)
If this get traction, my intention is create an individual project to manage requirements and new features (avahi autodiscover, run as a systemd service, support for xbmc, airplay, dlna...) Instructions:At this time raspberry has an arch arm distro with mate desktop (gtk2). user: alarm it is added to sudoers. It has ssh and vnc enabled (first tries with creating systemd config services) from boot. You can see what net raspberry gets with: (See 192.168.0 depends on your net)
connect through ssh or vnc is a easy way to interact with raspberry pi at this time, but you can always plug raspberry to a monitor and operate with a usb keyboard and mouse. from that just run miracle-wifid and miracle-sinkctl as usual
and run the interface it detects pair your device and see the your screen on vnc, tv or whatever. If for whatever reason it doesn't work check if wlan0 is not up with
and if it does bring it down:
For package managing I have added yaourt (a package manager for AUR (Arch linux user repository)). After this great contribution postponed by me long time https://aur.archlinux.org/packages/miraclecast-git/ To update miraclecast you just need to do:
that uses my AUR repo https://aur.archlinux.org/packages/miraclecast/ which is tied to master branch (no edge updates or unstable) See yaourt is configured to don't ask anything http://kissmyarch.blogspot.com.es/2012/05/two-simple-yaourt-tips.html. |
so, i rested with the -uibc flag and it worked kind of.. |
Took the a while know kodi is the old good xbmc. It is an interesting option, feel free to ask anything here or in a new issue. Should be easy to do (when we know where to do it) Hint: miracast is a simple rtsp video stream |
I revive an old post about kodi and miracast http://forum.kodi.tv/showthread.php?tid=167455&pid=2389125#pid2389125 Let's see if people can provide some help about it. |
Wow, great news! Will this run on RPi 2 as well? I'm building Raspberry PI based infotainment add-on for VW stock navigation and i was searching for reliable Miracast solution for such a long time. I'm using https://github.com/codemonkeyricky/piracast at the moment, but it isn't as stable as i want it to be. I'm looking for more stable solution. Did i find it? :) |
Luckily enough, the image nowadays is based on arch arm for raspberry pi 2 https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3 so it should. Your requirements are interesting so if it works maybe you want to help in create systemd services for running from boot and ease the miraclecast control. If it didn't work we can create quickly an image for rpi2 |
Hello albfan, thanks for a quick entry. I cloned your image to a new SD card, but unfortunatelly it didn't boot at all. Not even the colour image on HDMI output at start. When i swapped files on FAT partition from my raspbian SD card, it boots, but i guess it's not a proper way to fix a problem. I've downloaded archlinux package for rpi2 (it's the same as for 3) and swapped files from FAT partition once again. It did'n work neither. Any help appreciated. |
Did you follow this steps on a vanilla arch arm image?:
Login as the default user alarm with the password alarm. If that works I guess my image should work too. But if it keeps failing, TIMTOWTDI, just installing a couple of packages and tweaking some files you will get it working. |
Hello. I didn't follow that, because your image (from google drive) contains whole disk and it's already partitioned. So i was only playing with FAT (boot) partition. Didn't touch second partition at all. OK i will start from clean archarm distro and see if this will work. Thanks. |
Yes. It's onky to check if a clean image works and see where's the problem. After my first install I had done a pacman uodate. Maybe that added some specific armv8 (rpi3) stuff (package uodates or new ones) and there's the incompatibility. As I told before, share a 7,4Gb image is not a solution at all. Downloading vanilla image and using fakeroot should be possible to configure a custom image for any embedded device from a few Kb script If your test is succesful, that will reveal the necessity for that approach. |
Wow, it's working ! Your disk image is allright. Only thing i was missing was an entry in config.txt file with kernel=kernel7.img . My observation (as text-console guy) is that you need to run 'sudo miracle-sinkctl' in gui mode. If you run this in text mode (eg. via ssh) gstreamer will not appear at all. Is this using RPi's hw-acceleration? I guess not. Maybe it would be possible to compile your project on raspbian? Modern raspbian images have systemd onboard and gstreamer with OpenMAX build in (or as a package). I will give it a try on the raspbian since i prefer debian-like systems. Anyways, great project! It's stable as i wanted. I was able to cycle connect-disconnect many times without any issue. When i was playing with piracast it was very hard to make a connection to it. It worked 50/50. Great 👍 |
Great contribution! https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=101122 I will update README.md about that (If you want provide a PR about that) About gstreamer, as gstreamer starts as a fork of miracle-wifid, it doesn't work on text mode. Some research is needed to fix that. Raspbian has an old systemd version and seems it doesn't work correctly. Keep an eye on it and don't hesitate to ask here about your progress |
Hi there! I admire you for what you have achieved! I have downloaded the image from google drive and installed it, but when I run "miracle-wifid" I get a warning that say: "wpa_supplicant or driver does not support P2P". Any help please? |
@WillemPi3 you need to shutdown existing wpa_supplicant. If it is present is used by miracle-wifid, and normally existing wpa_supplicant is not configured to support p2p_scanning.
should be enough. Anyway, check there's no wpa_supplicant running before starting
and kill it if it is present. There's a helper in res/ directory |
Thank you that helped! I've connected my Galaxy S6 to the Pi and it mirrored the screen for maybe 2 seconds and then miraclecast disconnected. I tried to restart the process but it couldn't kill the wpa or restart the connection. I've reinstalled the image and updated miraclecast with yaourt, tried to connect my phone again and this time it didn't even connect. Could it be my phone that is not supported? This was the output generated in Terminal: `[alarm@alarmpi res]$ sudo ./show_wpa.sh [sudo] password for alarm: [alarm@alarmpi res]$ sudo miracle-wifid & [1] 5193 [alarm@alarmpi res]$ sudo miracle-sinkctl [ADD] Link: 3 [miraclectl] # run 3 [ADD] Peer: ee:9b:f3:a5:d7:f5@3 [PROV] Peer: ee:9b:f3:a5:d7:f5@3 Type: pbc PIN: [GO NEG] Peer: ee:9b:f3:a5:d7:f5@3 Type: pbc PIN: [FAIL] Peer: ee:9b:f3:a5:d7:f5@3 Reason: unknown [miraclectl] # ERROR: supplicant: HUP on supplicant socket of wlan0 (supplicant_global_fn() in wifid-supplicant.c:2145) ERROR: supplicant: wpas (pid:5197) failed unexpectedly, relaunching after short grace period.. (supplicant_failed() in wifid-supplicant.c:2312) no longer waiting for peer [Phone] Galaxy S6 (ee:9b:f3:a5:d7:f5@3) ERROR: cannot change p2p-scanning state on link 3 to 1: Unknown object '/org/freedesktop/miracle/wifi/link/_33'. (ctl_link_set_p2p_scanning() in ctl-wifi.c:671) [REMOVE] Peer: ee:9b:f3:a5:d7:f5@3 no longer running on link 3 [REMOVE] Link: 3 ERROR: supplicant: wpas (pid:5214) failed again.. entering grace period, waiting 30s before relaunching (supplicant_failed() in wifid-supplicant.c:2316) WARNING: supplicant: wpa_supplicant or driver does not support P2P (supplicant_status_fn() in wifid-supplicant.c:1682) [ADD] Link: 3 [miraclectl] # run 3 now running on link 3 [miraclectl] # exit [miraclectl] # root 5217 5194 0 14:05 pts/0 00:00:00 /usr/bin/wpa_supplicant -c /run/miracle/wifi/wlan0-3.conf -C /run/miracle/wifi -i wlan0 -g /run/miracle/wifi/wlan0-3.global [alarm@alarmpi res]$ ./kill-wpa.sh [alarm@alarmpi res]$ ERROR: supplicant: wpas (pid:5217) failed unexpectedly, relaunching after short grace period.. (supplicant_failed() in wifid-supplicant.c:2312) WARNING: supplicant: wpa_supplicant or driver does not support P2P (supplicant_status_fn() in wifid-supplicant.c:1682) |
It fails on device handshaking, so the problem must be in device handshaking (miracle-wifid log) post it here. |
|
|
[alarm@alarmpi Desktop]$ sudo miracle-wifid --log-level trace TRACE: wpa: raw message: OK TRACE: wpa: raw message: p2p_device_address=ba:27:eb:12:c8:c6 DEBUG: supplicant: local p2p-address is: ba:27:eb:12:c8:c6 (supplicant_status_fn() in wifid-supplicant.c:1807) TRACE: wpa: raw message: OK TRACE: wpa: raw message: FAIL TRACE: wpa: raw message: OK DEBUG: link: link wlan0 started (link_supplicant_started() in wifid-link.c:277) sudo miracle-sinkctl DEBUG: supplicant: sent P2P_FIND to wpas on wlan0 (supplicant_p2p_start_scan() in wifid-supplicant.c:2020) DEBUG: supplicant: p2p-scanning now active on wlan0 (supplicant_p2p_find_fn() in wifid-supplicant.c:1901) TRACE: wpa: raw message: IFNAME=p2p-dev-wlan0 <3>CTRL-EVENT-SCAN-STARTED TRACE: wpa: raw message: <3>P2P-GO-NEG-SUCCESS role=client freq=2437 ht40=0 peer_dev=ee:9b:f3:a5:d7:f5 peer_iface=ee:9b:f3:a5:57:f5 wps_method=PBC TRACE: wpa: raw message: wifi_display=1 WARNING: supplicant: wpa_supplicant or driver does not support P2P (supplicant_status_fn() in wifid-supplicant.c:1682) DEBUG: link: link wlan0 started (link_supplicant_started() in wifid-link.c:277) DEBUG: supplicant: sent P2P_FIND to wpas on wlan0 (supplicant_p2p_start_scan() in wifid-supplicant.c:2020) WARNING: supplicant: P2P_FIND failed (supplicant_p2p_find_fn() in wifid-supplicant.c:1897) |
hello, good initiative. would love to know the current status of the project. specifically for rpi3 :) |
Hi @amit-handa. Look at https://github.com/albfan/miraclecast/wiki/raspberry-pi-3 on wiki faq. Feel free to open new issues if try yourself and get blocked |
I suggest to try again from master. There's a fix about wfd_video_formats. Closing by now until more input is provided |
First thing is, my Nexsu 5 is not finding the Miracast device, but my Windows 10 Laptop does..
Everything connects fine, but the screen is not showing can you help me quick? :) I am really sorry.. I did everything what was listed in the FAQ
The text was updated successfully, but these errors were encountered: