this post was submitted on 21 Aug 2023
43 points (97.8% liked)

Android

16911 readers
64 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 1 year ago
MODERATORS
 

Android Authority: 3DMark's benchmarking suite has launched its first ray tracing test and we've run it on a bunch of phones

top 13 comments
sorted by: hot top controversial new old
[–] [email protected] 16 points 10 months ago (4 children)

This is not a feature that a device with limited available power to consume needs. It's just dumb.

[–] [email protected] 6 points 10 months ago (1 children)

I disagree. I use my old phone exclusively as a gaming device. If it needs power, I plug it in. The better graphics it can handle, the better

[–] [email protected] 5 points 10 months ago (1 children)

So you believe it needs it as a standard feature even though gaming phones that it's more appropriate for are a thing?

[–] [email protected] 3 points 10 months ago (1 children)

I think it should be a standard feature that game developers are able to take advantage of if they would like to.

I don't think you are going to accidentally stumble upon any mobile games that have raytracing anytime soon and wonder why your battery is draining

[–] [email protected] 3 points 10 months ago (1 children)

Looking forward to those unskippable ray traced ads. πŸ‘

[–] [email protected] 3 points 10 months ago
[–] [email protected] 3 points 10 months ago (1 children)

I completely disagree.

We are doing rasterization on mobile devices, running shaders, running neural networks... why exactly is ray tracing the only feature left out?

In fact, the tendency is for 3D graphics to replace rasterization with path tracing entirely. It's a much better way of creating graphics.

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

The only argument you can really have is about die space. If fixed function hardware is on die for ray tracing.

The chip could be cheaper or have a larger rasterization GPU block, AV1 encode block etc etc

[–] [email protected] 0 points 10 months ago (1 children)

I'm willing to bet the engineers behind Qualcomm are aware of the challenges with die size.

[–] [email protected] 2 points 10 months ago

Of course. But it's still an absolute physical trade off. There is only so much die space and power budget or cost. They will have traded something off.

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago)

This is not a feature that a device with limited available power to consume needs.

I don't disagree, but I'm not sure that that is the long-run game.

I think that many of us consider Android to be a supplemental platform to a "heavyweight" computing platform, like Linux, MacOS, or Windows.

My understanding is that an increasing number of younger people don't know how to use those platforms. Just a smartphone platform.

And I see attempts to shift towards heavier-weight Android devices.

It may be that the aim here is to move towards larger Android devices.

[–] [email protected] 1 points 10 months ago

I don't think we'll be using dedicated hardware for these work loads for very long.

FPGAs will likely phone several tasks such as encryption, ray tracing, ml, etc.

That said I would very much like raytracing in my phone as it is the lowest barrier of entry for VR/AR which could benefit from raytracing.

[–] [email protected] 9 points 10 months ago

Awesome, a high end graphics feature that brings even the biggest dGPU to its knees just got better on a mobile phone with a 6” screen and tiny battery. That 8 minutes of playing before the battery dies sure will look fancy!