this post was submitted on 22 Feb 2025
36 points (95.0% liked)

Android

18283 readers
276 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: [email protected]


💡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: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬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 [email protected].

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].

  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 2 years ago
MODERATORS
top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 12 points 5 days ago (4 children)

Why would you take a screenshot of a photo?

[–] [email protected] 3 points 4 days ago* (last edited 4 days ago)

I for one welcome any progress for HDR in software. It's still woefully behind on pretty much every platform. This is display technology invented 22 years ago that still doesn't work properly in a million different cases. Actually smartphones have some of the best implementations for HDR right now, for some reason.

[–] [email protected] 7 points 5 days ago* (last edited 5 days ago)

This is mainly for HDR video lol. And other content like HDR Android games if they exist...? Why tf would you take one of your own photos 😭

Also I assume this would be useful if you want to take a screenshot of an HDR photo on apps like Instagram where you can't send the actual photo itself or don't want to link someone to Zuck's all-knowing algorithms.

[–] [email protected] 1 points 3 days ago* (last edited 3 days ago)

In case the website wouldn’t let you save it. I don’t think the Instagram app allows you to save posted photos, for example.

[–] Albbi 1 points 5 days ago
[–] [email protected] 7 points 5 days ago (1 children)

It’s unclear why Google stuck with PNG for HDR screenshots instead of a format supported by Ultra HDR such as JPEG.

Because for good lossless HDR you've got a grand total of 2 options, PNG and JPEG XL. And Google don't want people to know of yet another use case for JXL.

[–] [email protected] 2 points 5 days ago (2 children)

Google don't want people to know of yet another use case for JXL.

Why's that?

[–] [email protected] 2 points 3 days ago

They really want to promote their AVIF format, and supporting JXL would hinder that (Since JXL is a much nicer upgrade path from JPEG/PNG than AVIF is)

Like you can transparently go from JPEG to JXL and back with no loss, which isn't possible with AVIF. And PNG to JXL gives you a smaller file, while it's usually the opposite with AVIF (Unless you get lucky, as lossless AVIF can be beaten by a BMP in a ZIP file). There's also the issue of speed, AVIF is slow to encode compared to other formats (And while hardware decoding is possible, it's also geared towards video, so the quality is often lacking, and can sometimes be slower than plain software encoding)

[–] [email protected] 1 points 4 days ago (1 children)

I'm not sure Google even knows. They killed it off in Chrome

[–] [email protected] 1 points 4 days ago (2 children)

Ironic, knowing that Google Research created it (together with Cloudinary).

[–] [email protected] 2 points 3 days ago* (last edited 3 days ago)

That’s actually quite common in large companies, just recently I read this story:

Back then, there was close to zero collaboration between divisions at Microsoft […] In late 2013, my team was building Skype for Web, which we positioned as a competitor to Google Hangouts. We had a problem, though: in order to start a video or voice call, users needed to download a plugin which contained the required video codecs. We noticed Google Hangouts did the same on Internet Explorer and Firefox, but not on Chrome because the plugin was bundled with the browser for a frictionless experience. […] My team decided we had to offer the same frictionless experience on Microsoft’s latest browser, Edge, which was in development at the time. […] the team politely and firmly rejected bundling our plugin into the new Microsoft browser. The reason? Their KPI was to minimize the download size of the browser, and helping us would not help them reach that goal.

[–] [email protected] 1 points 4 days ago

Makes sense