Viewing a single comment thread. View all comments

kailron t1_iuhwglz wrote

I went from s21 to 14 pro, here are some issues i’ve experienced: 1)many animations on iOS aren’t configured for 120hz and run at about 90hz, which makes smoothness worse compared to android’s 120hz. 2)I prefer Samsungs/androids implementation of notification+control center 3) can’t map flashlight to double/triple clicking power button(I know many people love to bind camera to it as well). 4) no longpress number row in default keyboard

Wonder if these things are also part of your experience, don’t view me as a hater tho, there are reasons why I switched and they satisfy me, but I would give a lot to get features that I mentioned, especially given how easy they are to implement from the coding standpoint

22

tomj1991 OP t1_iuja9st wrote

I think the biggest thing I miss is being able to double press the power button for the camera. Apart from that and what I already mentioned Im not finding anything else.

5

StillChillBuster t1_iujq8x2 wrote

I miss this from my android as well

You have two options. One, add a camera widget to your control center (control center is the menu you get when swiping down from the top right of the phone). You can add it by going to settings > control center and adding camera

The other option is to make a shortcut that opens the camera app, and then use the back tap feature (settings > accessibility > touch > scroll down to back tap) and set a double or triple tap to run that shortcut

2

Venilix t1_iui0yuv wrote

Would you have an example where this is visible? I haven’t even seem the general difference, having used iphone since iphone 2G to now iphone 13 pro. I more experience it as an overall improvement of speed by the cpu. Wondering where I can see it in the display Hz

3

kailron t1_iuimkah wrote

The scroll is primarily the issue here, almost all other animations are solid smoothness. General scroll in every first party app, such as settings, iMessage, photos, mail, safari, etc jumps to about 80-90hz. Pretty much all 3rd party apps that use the same default scroll api also don’t reach 120hz. Lastly, switching between home screen pages isn’t 120hz. Here are some apps that do, somehow, use 120hz scroll: telegram, Amazon, chrome. If you wanna see comparison to how it should be in 1st party apps, turn on screen recording and try scrolling while the screen is being recorded, that forces 120hz everywhere. See if you can spot a difference. Also, without turning on screen recording, see if you can spot a difference scrolling through a google search in safari vs chrome

−2

djbuu t1_iuiupi0 wrote

I followed this test and noticed absolutely no difference whatsoever. Tried a few times over a few apps.

Curious, how are you arriving at this hz conclusion?

7

roastpork123 t1_iujdj96 wrote

Here’s a comparison between iPad and iPhone 120Hz: https://www.youtube.com/watch?v=cFvS883E9GY

2

djbuu t1_iuji8i0 wrote

Thank you. Very helpful. That said, I still don’t know if I’d ever notice this or feel strongly about it unless I was side by side scrolling with an iPad Pro. I stand by my other statements that most people won’t notice this or even care if they did.

2

roastpork123 t1_iujinnn wrote

True. Most people won’t notice it. And they’ll notice if they go back to 60Hz that their screen is better. But for me, I notice that the 120Hz is not really peaking at 120Hz and mostly capped at around 90Hz. Again, not too much of a big deal but it’s good to know. And it’s unfortunate considering this was iPhone 13 Pro’s main selling point.

3

kailron t1_iujbohw wrote

People who use high refresh a lot develop an eye for it, refresh rate is directly correlated with the perception of smoothness, you can tell when the animation feels half way between classic age old 60hz iPhone and what a true 120hz should feel, that’s where the number 80-90hz comes from. These findings are confirmed by a ton of other people mentioning 80-90hz since that’s what it feels like to people who can actually tell. Apparently, many people can’t tell the difference and that’s primarily what lets apple get away with it

−1

djbuu t1_iujbum9 wrote

So this isn’t science. This is your eye. And it’s something 99% of users will never notice or care about. Good to know

3

kailron t1_iujdbm5 wrote

Blaming it on “my” eye is just a cope argument. We will never know the true statistic but I would argue it’s not 99%, and the percent would be even lower if people we let to experience what it should actually feel like. There are various videos online with people using external cameras to compare hz on iphone vs android, one of them even has an approximate calculated value of a scroll of 80hz. And most importantly, a ton of people keep repeating the words “it feels like a 80-90hz screen” over and over

1

djbuu t1_iujdn8j wrote

Not blaming it on your eye. Just saying this isn’t science. Either way again 99% of people will never notice this. This is the nittiest pick I’ve seen in awhile

2

kailron t1_iujffob wrote

You have no idea how much of a serious issue this is, this is a universe away from being nit picky, you just can’t see it, not everyone can. Also, “this isn’t science” is a crappy argument in this case, science doesn’t just magically contradict observation. The only thing that’s not science here is your 99% number. There are people claiming iOS default scroll currently tops off at 80hz max since Xcode has 1, 10, 60, 80, 120hz as defined accessible options for iPhone animations, and apple chose 80 for default scroll api on iPhone. Contrast this to an iPad pro, which only has 10, 60, 120, so apple just gives 120. So far this reasoning is the most likely theory, the only reason why I’m using the word theory is because I’m not an iOS dev and I can’t confirm these findings myself

−4

djbuu t1_iujhogj wrote

It not being science is a great argument. Why? Because any semblance of a scientific method here would prove a problem. Instead? I only have your eye to trust on a problem so “serious” that this is the first time I’ve ever heard of it and your own “test” can’t even show an average user (me) a demonstrable difference. Honestly I was all ready to thank you for pointing it out and then be constantly ever so slightly irked that I wasn’t getting premium smoothness. Instead here I am, pointing out your unproven “eye” is severely lacking in concrete repeatable demonstration.

1

kailron t1_iujix68 wrote

Well, sorry mate, you’re just gonna have to trust my “eye” then. If you actually followed my tests and still can’t see it, then you just can’t see it. From my online observations there are plenty of people who can see it and are disappointed, but there are also plenty of people who can’t see it just Iike you.

−1

aleksevv t1_iuiql4r wrote

Probably, you can use accebility features to map the flashlight.

2

kailron t1_iuiqwxp wrote

I tried double/triple back tap and rage-turned it off after a couple of days due to how it works like every third time, it astonishes me how you can’t map triple power button click to it instead

3

aleksevv t1_iuirz9i wrote

Never used accessibility, but sucks to hear it works this way.

Sthg so simple should be possible.

1

kailron t1_iuisonm wrote

“Something so simple should be possible” is the general state of mind when u swap android to iphone

3

Flex973 t1_iujcsvs wrote

Download Google keyboard for iOS

2

kailron t1_iujdv0o wrote

I tried gboard and couple others, their aestetics suck compared to default iOS keyboard, also I dislike how I can’t reduce the activation time for number row

4

_nocontest t1_iuk2kwi wrote

For the flashlight use this- Settings > Accessibility > Touch > Back Tap > Double Tap : Torch

2

kailron t1_iuk4nr2 wrote

Already replied to another guy suggesting back tap, I used it for 2 days and rage-disabled it after experiencing that it’s dogshit and works like every third time, it’s also prone to accidental activation

2