this post was submitted on 14 Jul 2024
486 points (96.9% liked)
linuxmemes
20880 readers
2 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've never experienced that. Also Android is OpenJDK based and the applications in Android work well and the system is well optimized
Yep, I also don't fully agree on that one. I'm typing this on a degoogled Android phone with quite a bit stronger hardware than the iPhone SE that my workplace provides, e.g. octacore rather than hexacore, 8GB vs. 3GB RAM.
And yet, you guessed it, my Android phone feels quite a bit laggier. Scrolling on the screen has a noticeable delay. Typing on the touchscreen doesn't feel great on the iPhone either, because the screen is tiny, but at least it doesn't feel like I'm typing via SSH.
That has to be because the code is better optimized for the hardware in case of iPhone and less so which language it was written in.
Why? I certainly expect that to be a factor, but I've gone through several generations of Android devices and I have never seen it without the GC-typical micro-stutters.
I've never experienced that and I am running a several year old phone
I have experienced the delayed scrolling, mostly on cheaper phones.
But that's mostly because i'm used to phones having 120+hz screens now, going back to a 60hz screen does feel a bit sluggish, which is especially noticeable on a phone where you're physically touching the thing. I think it might also have something to do with the cheaper touch matrixes, which may have a lower polling rate as well.