They intentionally block casting from your Pixel phone to a TV, unless you use Chromecast. Google is terrible when it comes to casting.
Also disabled DisplayPort over USB-C on all Pixel phones to force you to buy a Chromecast.
Which really fucked me over last month when my Pixel 7 Pro’s screen died and I had no way of accessing the phone’s data, since I hadn’t allowed developer mode on any of my PCs yet
[This comment has been deleted by an automated system]
Mildly off topic but years ago I bought a cheap Microsoft Miracast receiver. Tried using it some dozen times with various phones and with my PC and it never worked. HOWEVER this month I got a new phone and NOW it works with that phone, lol (the device itself hasn’t been updated, and both my current and previous phones are Sony). Guessing it’s some compatibility thing in the Linux drivers shipped on the phone. But weird that no other device of mine has been able to cast to it before, including some Windows computers.
What we need is a Miracast 2 which does the Chromecast thing of offering a remote controlled browser engine, but open.
I have a TV with Android TV and casting stopped working, and found out Google requires signing into the TV with an account now? I didn’t feel like doing that so started using airplay which TV supports too.
That would be pretty neat. But I think they should get connected calling and messaging between phone and tablet in there. Apple does it, Samsung does it, the web app doesn’t cut it.
Edit: and immediately after posting this, I found this
I would think this would be a huge boon for reverse engineers to potentially come up with a self hosted cast compatible interface. Much more opportunity for looking under the hood in this configuration.
This has already been done over wireless ADB and more if you just want mirroring. For content aware casting we essentially just have DLNA derivatives and nothing better.
