8000 newer Windows versions disconnect after 2-3 secounds · Issue #83 · homeworkc/lazycast · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

newer Windows versions disconnect after 2-3 secounds #83

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.

Sign up for GitHub

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

Jump to bottom
Open
KoehIl180151 opened this issue Apr 15, 2021 · 10 comments
Open

newer Windows versions disconnect after 2-3 secounds #83

KoehIl180151 opened this issue Apr 15, 2021 · 10 comments

Comments

@KoehIl180151
Copy link

Hi, I installed your programm on my pi 3 b+ today.
On a laptop with an older WIndows version everything works fine but on an up-to-date version (I tried multiple devices) the feed works fine for 2-3 secounds but then it freezes and crashes.
I tried changing all kinds of setting and did troubleshooting for a few hours now but nothing helps.
When crashing it shows recv timeout.
@homeworkc
Copy link
Owner

I will look into it but it may take a (long) while.
"recv timeout" means that the Raspberry Pi does not receive any wifi packet for an extended period of time. This usually indicates the problem with the wifi p2p connection. It could be that Windows change some logic of wifi p2p connections. (For example, switching channels.) It also could be that Windows adds some new wifi display features and somehow causes problems. (For example, switching to other video encoding schemes.)
One way to debug is using Wireshark both on the Windows side and on the Raspberry Pi side. A more comprehensive method to debug is to use a third device with its wifi card set to the monitor mode and with the Rx filter set to accept any frames. (E.g., another Raspberry Pi 3 with Kali Linux.)

@trixrahbit
Copy link
trixrahbit commented Sep 19, 2021 •
edited
Loading

I have the same issue on a pi4 with newer Windows. Will try to debug in the future if needed. Would love to see this working again.
image

@Jaroslav-Dvorak
Copy link

I have two laptops. One of them works flawlessly. And the other disconnects after few seconds. I have no idea why.
But I have noticed that in Wireshark is shown protocol of packets UDP on working laptop and MPEG TS or MPEG PES on disconnecting laptop.
I bought Microsoft Wireless Display Adapter and both laptops work. And in Wireshark is on both protocol UDP.
I spend a lot of time finding the problem - comparing source code from Miraclecast project with lazycast and so on..
Unfortunately I did not find the solution :-(

@JpTiger JpTiger mentioned this issue Apr 3, 2022
Open
@JpTiger
Copy link
JpTiger commented Apr 3, 2022

Also having this issue with a new Windows 11 laptop. My old Win 10 laptop from 2014 works with Lazycast just fine. Happy to provide debugging info if helpful.

@hj0707
Copy link
hj0707 commented Apr 9, 2022

I have the same issue with raspberry Pi 3B + & windows10 21H1, even use network cable ,seems not wifi problem

@Jhgallas
Copy link

Same, on 3B and Windows 11

@Jhgallas
Copy link
Jhgallas commented Apr 15, 2022 •
edited
Loading

Same, on 3B and Windows 11

I have had success however with a different machine, with a 720p display (also on 11). However the resolution of my main pc does not appear to be what was causing problems - after testing different resolutions of the lazycast display (painfully, in the 2-3 seconds of connection), as well as the resolution of my surface book, nothing changed, i get the same recv timeout

I did try to change to player 2 in the config file, wich immediately spits out some error codes:

[rtp @ 0xb1a9d0] max delay reached. need to consume packet
[rtp @ 0xb1a9d0] RTP: missed 57 packets
[rtp @ 0xb1a9d0] PES packet size mismatch
[h264 @ 0xb1f2c0] sps_id 0 out of range
[h264 @ 0xb1f2c0] SPS unavailable in decode_picture_timing
[h264 @ 0xb1f2c0] non-existing PPS 0 referenced
[h264 @ 0xb1f2c0] sps_id 0 out of range
[h264 @ 0xb1f2c0] SPS unavailable in decode_picture_timing
[h264 @ 0xb1f2c0] non-existing PPS 0 referenced
[h264 @ 0xb1f2c0] decode_slice_header error
[h264 @ 0xb1f2c0] no frame!
[h264 @ 0xb1f2c0] error while decoding MB 55 29, bytestream -30
[h264 @ 0xb1f2c0] concealing 1609 DC, 1609 AC, 1609 MV errors in I frame
[rtp @ 0xb1a9d0] max delay reached. need to consume packet
[rtp @ 0xb1a9d0] RTP: missed 222 packets
[rtp @ 0xb1a9d0] PES packet size mismatch

These are just the more visible ones, if it helps anyone, i can dump out the whole log

Amusingly enough, however, after doing this it displays a completely frozen cast of my laptop screen until terminated

@debritde
Copy link

Hi, i am also facing this problem with Windows 11.
Did anyone found a solution?

@homeworkc
Copy link
Owner

Try using win10debug.sh instead of all.sh and see if it helps. (win10debug.sh isn't very polished but it seems to at least keep the connection open.) Somehow newer Windows versions have some weird behaviors.

@homeworkc
Copy link
Owner

Also please report the WiFi card model if you have connection issues. I've found a new Qualcomm card having difficulty to establish a connection in mixed 802.11ax environments. In such case, it might be beneficial to lock the wireless mode (on the Windows side) to 802.11n.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@JpTiger @trixrahbit @homeworkc @debritde @KoehIl180151 @hj0707 @Jaroslav-Dvorak @Jhgallas
0