Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Good to see. This is something that should've been communicated to developers before the iPhones came out, not after, so that apps could be updated before the phones came out (like every other iPhone launch).

Let's hope they push updates fast.
Give Apple a little time, it is out since Friday and 99% of users who order it has not yet received. It not like you can’t use the product, like many new features it needs dev to implement it.. but give devs and Apple time, tho is like free whining. This attitude is absolutely wrong.
 
  • Like
Reactions: SFjohn
This is pretty ill-informed. The rather extensive documentation on this feature shows they didn’t just make it up last night. The way it works is well-reasoned and very-well explained in the developer documentation. And the support is already in the operating system - it just requires developers to opt in by editing their plist file (which is not source code). The software works fine will AirPods Pro and Apple Watch, it uses the headlining feature to its full potential (promotion is NOT “120Hz at all times” but “variable speed to increase battery life to double the old phones“), its own software already runs at 120Hz when appropriate, and it will have no affect whatsoever on the battery scores.
I was talking about Siri not being able to control ANC and Transparency modes of AirPods Pro and "iPhone Storage Almost Full" bugs. I thought there was also something about the Aple Watch but I can't find it. Maybe I misremembered.
About the plist - if that was the plan all along why not notify the developers in advance, especially if that's something that wasn't required for iPads?
 
So all the battery life reviews we have seen had 120hz disabled most of the time? How convenient.
Sure, except in all Apple apps including Safari, in video playback apps like Netflix, in games using Metal or third party frameworks on top of Metal, etc.
 
I was talking about Siri not being able to control ANC and Transparency modes of AirPods Pro and "iPhone Storage Almost Full" bugs. I thought there was also something about the Aple Watch but I can't find it. Maybe I misremembered.
About the plist - if that was the plan all along why not notify the developers in advance, especially if that's something that wasn't required for iPads?

If they had notified the developers in advance, the developers would have known that this feature was coming to iPhone, and it would have blown apple’s ”surprise.” They could’ve let the developers know about it right after the product announcement 2 weeks ago, but the developers couldn’t do anything about it until the new Xcode and sdks became available anyway (last week). So you are quibbling about a couple of days.
 
You also don’t get a setting to always run the CPU at full speed. Pointing this out by iOS 15 seems a little quaint to me.
Those are completely unrelated things entirely. I don't care if the CPU is running at full speed while I'm using the phone. Seeing the screen be at a consistently fluid 120 Hz, like I have on Android, something that you are looking at to interact with the phone 100% of the time, is far more important. That is such a silly comparison I don't even know where to begin.
 
  • Like
Reactions: willchris
Those are completely unrelated things entirely. I don't care if the CPU is running at full speed while I'm using the phone. Seeing the screen be at a consistently fluid 120 Hz, like I have on Android, something that you are looking at to interact with the phone 100% of the time, is far more important. That is such a silly comparison I don't even know where to begin.
Love my 13 PM. Reading this site in Safari the phone gets really hot. Anyone else notice this
 
  • Like
Reactions: Bandaman
If they had notified the developers in advance, the developers would have known that this feature was coming to iPhone, and it would have blown apple’s ”surprise.” They could’ve let the developers know about it right after the product announcement 2 weeks ago, but the developers couldn’t do anything about it until the new Xcode and sdks became available anyway (last week). So you are quibbling about a couple of days.
Of course I am. Unlike many people on this site I care about the customers way more than I do about Apple. There is no excuse for not providing your customers with the best possible experience, especially when you keep going on and on about how much you care about them. Apple make great products but iOS 15 is quite a mess.
 
  • Haha
  • Angry
Reactions: Krizoitz and cmaier
Of course I am. Unlike many people on this site I care about the customers way more than I do about Apple. There is no excuse for not providing your customers with the best possible experience, especially when you keep going on and on about how much you care about them. Apple make great products but iOS 15 is quite a mess.
There are literally apps already on the AppStore that support this. It’s been less than 24 hours. How, exactly, have customers been harmed?
 
As usual there is a conspiracy theory attached to all of this: Apple deliberately withheld this feature from developer apps until battery benchmarks had been done by reviewers.

Surely there’s the possibility that battery life using 3rd party apps will actually get better once developers start using this feature as their apps won’t be running at a constant 60hz?
 
  • Like
Reactions: cmaier
Glad to see Apple being proactive on this but you would think this is something they could and should have relayed to Developers once they started accepting iOS 15 apps last week.
I wasn't interested in the problem, but I saw real developers figure it out with existing documentation right away.
 
There are literally apps already on the AppStore that support this. It’s been less than 24 hours. How, exactly, have customers been harmed?
Who said anything about anyone being harmed? Not providing people with the best possible experience doesn't equate to harming them. Why the need to blindly defend Apple? It's not some minority owned indie company operated from the sole developer's kitchen. They are a multi billion dollar company that can absolutely afford the brain power and testing needed for a software release with all the announced features present and functional on day one. I guess when you think of your customers as potential criminals and psychopaths you don't really have to care about their comfort that much...
 
Macrumors mods and owners should really step up and do something about the constant Apple bashing on an
Apple-centric site. Too much is just too much, and they need to do something, or the site will just turn into an Apple hate club. And the hate is mostly stupid and unoriginal, mostly just pure hate and trolling.

The fact that they need to disable comments on LGBTQ-related news (like this one the other day) is indicative of this site's demographics and the general climate here.

Do they really want to associate with this?
Agree. And the worst part is they only give you like 5-10 dislike to counter the army of anti-apple trolls in the site. Macrumors is more like machate this days.
 

Attachments

  • 3695A178-C4B1-40FC-8985-FBDD87B88CA5.jpeg
    3695A178-C4B1-40FC-8985-FBDD87B88CA5.jpeg
    377.5 KB · Views: 59
I don’t think iPad pro’s proMotion is the same kind of variable refresh rate, right? That might require more testing, so they leave it as something the developer can enable once they confirm it works right.
According to Apple’s support document that they just published, the iPhone 13 Pro’s can run at twelve different refresh rates from 10Hz to 120Hz.

The iPad Pro’s can run at five different refresh rates from 24Hz to 120Hz.
 
Okay, so (1) if I'm on Safari browsing macrumors.com or forums macrumors.com then I am getting the 120Hz refresh rate when I scroll up and down the page, right? It appears to my sense of sight that it does feel noticeably smoother.

Also, (2) what are some websites that check and show you your screen refresh rates?

I don't like that https://www.testufo.com/refreshrate site because it keeps telling me I'm at 60Hz even when I scroll up and down through it. I know there were others.

EDIT: 120Hz is definitely on for scrolling websites on Safari. I turned Low Power Mode on, which I know limits the refresh rate to 60Hz, and scrolled. The difference is extremely noticeable.
Testufo stated a few years ago that their site incorrectly reports 60Hz on ProMotion iPad’s due to an inconsistency with their website and iOS. It’s something they haven’t been able to fix.

This inconsistency has now carried over to the iPhone 13 Pro.

The Testufo website only works accurately for Mac’s (out of the Apple devices) connected to 120Hz displays and higher.
 
  • Like
Reactions: Rafagon
Founder of TestUFO here.

Unfortunately, this is not TestUFO's fault.

Apple is currently in violation of compliance of the HTML 5.2 and HTML 5.3 specification, section 7.1.4.2. Since Apple forces Chrome to use the Safari engine, the restriction also applies to all web browsers installed on the 120 Hz iPads.

Currently, FireFox, Chrome, Opera, and Edge (74+) are all compliant and even works at 240 Hz



Until Apple fixes this, at least for plugged-in 120 Hz iPads, it is just not possible to run TestUFO at above 60 frames per second on Apple iPads.
Testufo’s response from 2019, here on MacRumors forums.
 
  • Like
Reactions: asdex
Those are completely unrelated things entirely.

No. Both are examples of dynamically adjusting a hardware feature to find the right balance between performance and battery life.

Seeing the screen be at a consistently fluid 120 Hz, like I have on Android,

I hate to break this to you, but as soon as Android makers find a good algorithm to dynamically throttle the frame rate, that’s what they’ll do.
 
No. Both are examples of dynamically adjusting a hardware feature to find the right balance between performance and battery life.



I hate to break this to you, but as soon as Android makers find a good algorithm to dynamically throttle the frame rate, that’s what they’ll do.
Android does have self-adjusting screen refresh rate but they also have the option to leave it maxed out. This isn't something magical or new. And again no, CPUs adjusting their speed, which has been a thing since the dawn of computers, has nothing to do with what I said.
 
Android does have self-adjusting screen refresh rate but they also have the option to leave it maxed out. This isn't something magical or new. And again no, CPUs adjusting their speed, which has been a thing since the dawn of computers, has nothing to do with what I said.
CPUs never used to adjust their speed dynamically, they went flat out all the time regardless of what you were doing.

Apple just doesn’t want you or doesnt see the need for you to leave the screen at 120hz all the time as it’ll dynamically adjust based on what you are doing. Take it or leave it.

Both the approach to dynamically adjusting the CPU speed and screen refresh rate are fundamentally the same concept.
 
  • Like
Reactions: Krizoitz
Android does have self-adjusting screen refresh rate but they also have the option to leave it maxed out.

I can't wait for the outcry when that option inevitably gets taken away once the algorithms are efficient enough. "But mah freedoms"

And again no, CPUs adjusting their speed, which has been a thing since the dawn of computers,

It's literally the same thing: a dynamic, high-frequency adjustment between performance and power draw. And no, dynamic frequency scaling wasn't in widespread use before Intel SpeedStep ca. 2005.

 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.