this post was submitted on 11 Aug 2023
33 points (97.1% liked)

Android

17390 readers
280 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: !android@lemdro.id


πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
top 7 comments
sorted by: hot top controversial new old
[–] KevonLooney@lemm.ee 20 points 1 year ago (3 children)

They intentionally block casting from your Pixel phone to a TV, unless you use Chromecast. Google is terrible when it comes to casting.

[–] gray@lemmy.boltwolf.net 13 points 1 year ago (1 children)

Also disabled DisplayPort over USB-C on all Pixel phones to force you to buy a Chromecast.

[–] Ramenator@feddit.de 5 points 1 year ago

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

[–] NightOwl@lemmy.one 6 points 1 year ago

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.

[–] skullgiver@popplesburger.hilciferous.nl 5 points 1 year ago (1 children)

On the one hand, they should've kept WiDi/Miracast in Android. It's included in almost every non-Google Android.

On the other hand, every other brand still includes it, and if you buy a Pixel, you probably either own something with a Chromecast in it or you run a custom ROM anyway. It's pretty terrible in my experience. Audio desync issues, several seconds of latency, the connection drops out every now and then, and every TV has their own magical recipe for allowing your phone to cast to them (so far I've seen popups, a pairing menu, and a special button you need to press before you can even start).

Samsung has their own proprietary extensions on top of Miracast/WiDi that make most devices list their TVs as compatible, but I've never seen a non-Samsung phone pair and cast successfully. Then there is the fact most phones just mirror the contents of the screen, leading to massive black bars around content.

Chromecast fixes all of the practical problems by a) not dealing with authentication at all beyond "should be on the same network" and b) running the applications on the Chromecast itself rather than making the phone transmit high-bandwidth video over WiFi Direct. I don't know how AirPlay does it, but I wouldn't be surprised if it uses the same concept.

[–] natanael@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

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.

[–] Jz5678910@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

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

https://lemm.ee/post/3931939