Samsung TV Screen mirroring crashing after trying to use it with SecondScreen

[blueyed]

After trying out SecondScreen 2.9.2 with a Samsung UE55F8090SL 139,7 cm (55 Zoll) Full HD Smart-TV via its Screen Mirroring functionality, it does not work anymore without SecondScreen also.

I have used the default profile, using 1920x1080 with 240dpi (not sure if the DPI matches).

The crash happens right after the Screen Cast connection is established, and the TV just says the connection is ended ("Screen Mirroring wurde beendet" in German).
Android still displays the cast icon from the Wfd service for several seconds then.

It looks more like a bug with the TV than SecondScreen of course, but I wonder what might have caused this: is the TV in an unhappy state now after some unsupported DPI was tried on it? Wouldn't only the resolution matter after all?

And since this keeps happening after having uninstalled SecondScreen, and not having used autostart since the initial failure, I wonder if there is some state/setting changed in Android that might still cause it to crash like that.

I am using Android 10, and have tried it after rebooting both the phone and the TV.
I have not yet tested it with another phone/device, but it was working just before trying out SecondScreen, which I wanted to use for improving the mirroring experience.

[blueyed]

I have found that I can work around the issue by not using "Auto" for the advanced "Operating channel" Cast setting (to be enabled in developer settings, "Wireless display certification"). Using channel 1, 6, or 11 makes it work.
Using 36 does not work in some different way, and it says that it needs to disconnect from the main wifi there.
So the crash/issue appears to be with the Auto mode there then.
But it worked previously, and also still with another Android device, where SecondScreen has not been used.

[blueyed]

It's also notable that the TV did not show up in the main window (opened from the quick settings icon), but only when going to settings from there. It was just scanning there.
After having connected via a changed/manual channel the setting is back to Auto, and also the TV shows up in the main/initial window again, where it works from now, apparently also in Auto mode again.

Therefore likely some (advanced) setting in this regard was still changed/wrong after uninstalling SecondScreen maybe, which appears now to be fixed again.
Feel free to close the issue, but I would be happy to know what might have happened here, and even more if that was/is an actual bug in SecondScreen, that can / has been fixed.

[blueyed]

FWIW, after a reboot it still crashed now, but was available from the initial/main scanning screen. Going to settings and chosing an explicit channel could be used to work around it again.
It might be totally unrelated to SecondScreen, but pointers to settings that it changes and might have an impact here would be appreciated.