When I try to activate miracast / screen cast, it dos not work and often a message appears: “Wfd Service keeps stopping”, the TV shows a symbol that the device is connecting, and the screen cast icon appears on the Android device, but the connection does not happen. Some time later the symbol on TV disappears and the screen cast icon disappears at another time.
With /e/OS-T (A13) it worked very good. Even videos and sound were casted.
Since the update to /e/OS-U (A14) it shows up the described behavior.
I wonder why this bug doesn’t bother anyone else. It is pretty comfortable to share your screen with others. In our office we have lots of smart boards with miracast.
Is it an /e/OS or a LinageOS problem?
Who can help to debug?
I noticed this too and would really like Screencast to work again as i have to connect with hdmi for now.
I thought about opening an issue on this but as noone else seemed to miss it, i didnt want to bother the team and only mentioned it in the release feedback threads a few times.
I am experiencing the exact same problem. the Wfd service crashes when using Wireless Display on my tv. I have tried to force stop Wdf service, restart and every possible light tinkering, but nothing works. The Wfd service crash regardless of what I do. I hope it will be fixed in the next update because having degoogled and want to avoid using Chromecast (which works btw from VLC), from my /e/os/ FP4. Please fix this as soon as possible, because everything else is working as intended and I am very happy with /e/os/ but not being able to Miracast/Wireless display is truly a big one.
A stacktrace can help. There are 3-4 miracast issues in the /e/ backlog, 2 about FP3 (config xml disables casting atm - but the xml setting isn’t meaningful in the end), 1 about FP5. Many more over at lineage.
It’s mostly about the proprietary library blobs compatibility.
For the FP4 you want to look at what’s happening in version branches that are being worked on: https://review.lineageos.org/q/project:LineageOS/android_device_fairphone_FP4+wfd → looks to me as proprietary-files.txt were kept updated, but there was breakage, thus a shim was introduced in A15+ - not sure if A14 is completely declared broken.
When lineage moves on, it seldomly maintains an older version branch if for the device a newer exists. I’d just test lineage in A15 (22.2) and A14 (21.0) - and if it works, make sure the device development branch in /e/ has parity
Edit: found out that “Web Video Caster” on phone + “Web Video Caster Receiver” on the device you want to stream to, will make it possible to stream videos (and even with subtitles!)
if you leave the wifi-display constraint behind, there are alternatives. I think the constraint makes sense if all there is in a moment is an older tv OS that can do miracast but nothing else.
That said - for Android(TV), newer WebOS (5.0) or just regular OSes - the FUTO people work on FCast and a video player that utilizes the protocol for sending.
