Android
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]
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
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.
-
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.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
For me the biggest difference between 60 and 85 Hz on a CRT was that one gave me a massive headache and nausea within a few hours, and the other didn't.
Modern displays work differently though, especially LCDs which only really flicker if the backlight flickers. CRTs only display a small sliver of the image at any given time, while the rest is black or fading away until the next frame is drawn.
(Though I do see a big difference between 60 and 85 fps these days; 85-95 is where I start to find FPS games to not feel downright choppy, but there's still a big, big difference between 95 and 165.)
Higher refresh rates make a bigger difference when physically larger portions of the screen are changing at once, and when there's fast movement on the screen. That's why it has a more noticeable effect on FPS games, where the entire screen changes when you move the mouse, and when you want to quickly move your aim to specific points. It's much more noticeable on a large display than it is on a phone screen, for example.
Yes, indeed. But I find it very, very noticeable when just moving the mouse pointer too. Looks horrible on a 60 Hz screen.
The most important thing I think is movement speed. Extremely slow movements would look the same at 10 fps as 1000 fps (think a movement of 10 pixels per second, for example), while large movements look choppy at lower framerates. That's also (part of) why it's more important to have a high framerate in Quake/Unreal Tournament-style games than it is in e.g. first person puzzle games, latency being the other big one.