What you need to know
- Apple's first iOS 16 beta came out on Monday.
- It includes a leak about a major iPhone 14 Pro upgrade.
- Multiple references can be found to an 'always-on display'.
Apple's rumored always-on display for iPhone 14 Pro appears to have been leaked by Apple in the first iOS 16 beta.
9to5Mac says it has found "multiple" references to an always-on display:
The report says multiple references to the feature can be found in Springboard and within components of the lock screen, which got a major update with iOS 16.
This all means that the iPhone 14 Pro is likely to get the always-on display we've been waiting for. The feature will likely require a lower variable refresh rate of just 1Hz, as predicted by Ross Young last month.
The iPhone 14 Pro is also expected to feature a hole-punch display instead of a notch and a new A-series chip, as well as all the major software advancements announced by Apple this week. iOS 16 delivers huge lock screen changes and improvements to Maps, SharePlay, and more.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple. Follow him on Twitter @stephenwarwick9
During the keynote, the attention to the Lock Screen told me always on was likely. Makes sense
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.