
iPhone 17 Pro and Pro Max Geekbench scores tipped
Apple's upcoming iPhone 17 series is due to be made official in September, and ahead of that today we have yet another rumor claiming that all four devices will have high refresh rate screens. That said, don't expect the vanilla iPhone 17's panel to be on par with those of the Pros - what's recently been rumored is that it won't be variable refresh rate since it won't get an LTPO OLED panel.
Aside from this, the leaker who goes by Digital Chat Station on Weibo has also presented us with the performance figures for the upcoming A19 Pro chip which will be powering the iPhone 17 Pro and Pro Max. It will allegedly get an over 4,000 single-core score and an over 10,000 multi-core score in Geekbench 6.
For reference, note that the A18 Pro in the iPhone 16 Pro Max scored 3,490 and 8,606 in our testing, respectively (and it had better performance than the iPhone 16 Pro). So, with that in mind, we're looking at an improvement of 15% in single-core performance and 17% in multi-core performance.
The A19 Pro will be made on TSMC's N3P process, expected to also be picked for the Qualcomm Snapdragon 8 Elite 2 and the MediaTek Dimensity 9500, which are both launching the same month as the A19 Pro, so the competition between these three will definitely be interesting to watch. Apple iPhone 16 Pro Max Apple iPhone 16 Pro
Source (in Chinese)

Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles


Phone Arena
42 minutes ago
- Phone Arena
If your favorite Android watch face disappears next year, this might be why
Google introduced WFF back in 2023 as a new way to design watch faces using XML templates. Since then, it has allowed both WFF and non-WFF designs to exist on the Play Store. But starting in early 2025, Google began tightening the rules. Developers could no longer publish new watch faces using the older AndroidX or Wearable Support Library (WSL), although updates were still allowed. That grace period is now coming to an end. Here's what will happen in January 2026: Users won't be able to install legacy watch faces from the Play Store. Developers won't be able to update existing legacy watch faces. Monetization features like one-time purchases, in-app items, and subscriptions will no longer be available for these older watch faces. Existing purchases will continue to work, but auto-renewals will stop. Examples of Wear OS watch faces using the Watch Face Format (WFF). | Image credit — Google Google says that any developers who want to keep their watch faces available must migrate them to the Watch Face Format before the deadline. This includes developers who use Watch Face Studio, who will need to update to version 1.8.7 or later when resubmitting. WFF brings some clear benefits. Because it's based on XML templates, it helps watch faces run more efficiently, uses less power, and keeps animations smoother. But it's not without downsides. Some users and developers feel the new format limits creative options, especially for more complex or interactive designs. Still, this change has been coming for a while. Google's goal is to make the watch face experience more consistent across devices, which could be helpful as Wear OS continues to expand. Compared to Apple's limited watch face options and Samsung's increasing focus on AI-based designs, Google is trying to strike a balance between openness and stability. That said, users who prefer older watch faces should install them before the cutoff. While already-installed designs will continue to work, they may not receive updates or support going forward, so — you have been warned. For some, this shift could mean saying goodbye to their favorite designs unless developers act in time, so time is of the essence.


GSM Arena
2 hours ago
- GSM Arena
Google will reduce the Pixel 6a's battery capacity with an upcoming update
Earlier this year, Google released a Battery Performance Program update for the Pixel 4a which cut the phone's battery life as a precautionary measure. The reason – Pixel 4a batteries were overheating and posing a fire hazard. Well, another Pixel a-series phone is getting similar treatment soon as the Pixel 6a will also get a battery voltage decrease to prevent it from overheating. There are several reports online of Pixel 6a units spontaneously catching fire while charging and Google is taking the precautionary route once again. The update will only affect Pixel 6a units with over 400 charging cycles. A string in the latest Android 16 QPR 1 beta release confirms these upcoming changes, and Google also issued an official statement. A subset of Pixel 6a phones will require a mandatory software update to reduce the risk of potential battery overheating. The update will enable battery management features that will reduce capacity and charging performance after the battery reaches 400 charge cycles. We'll contact impacted customers next month, with all the information they need to address the issue. – Google official statement In the Pixel 4a case, Google reduced the battery's maximum voltage down to 3.95V from the original 4.45V value. The result meant a 56% drop in charging capacity. The Pixel 6a will probably get similar treatment. Burnt Pixel 6a unit (images: AndroidAuthority) In the meantime, if you are a Pixel 6a user, you can check your battery health by going to Settings > Battery > Battery health. If the phone shows an alert, you should probably look into getting your phone's battery swapped, preferably at a licensed service center. Google is also offering free replacements for Pixel 7a units with swollen batteries. Via


Phone Arena
2 hours ago
- Phone Arena
Pixel 10 may be getting the assistant iPhone users always wanted Siri to be
As the launch of the Pixel 10 approaches, one of Google's rumored upcoming AI features has quietly changed names and revealed more about how it works. What was previously called "Pixel Sense" will now be known as "Magic Cue," according to a new report. Magic Cue is not a replacement for Gemini, but instead works alongside it in a more passive and context-aware way. While Gemini still requires you to trigger it through a prompt, Magic Cue is designed to quietly monitor your screen and suggest helpful information or actions based on what app you're using and what's happening on screen. For example, if someone asks for your flight number in a messaging app, Magic Cue can automatically pull that information from your Gmail and present it to you, saving you the step of looking it up yourself. It's a small feature, but one that could reduce friction during day-to-day use. According to the leak, Magic Cue uses recent screen activity, app usage, and certain data from your Google apps and account — including Gmail, Calendar, Keep, Tasks, Contacts, and Messages — to figure out what might be useful at the moment. All of this data is processed in what Google describes as a "secure, isolated environment." Users will also have control over which apps Magic Cue can access. Magic Cue reportedly highlights two main functions: Find info instantly: It brings up relevant information based on the app you're currently using. Finish tasks faster: It suggests links to other apps where you can complete related actions. The 'Magic Cue' feature splash screen. | Image credit — Mystic Leaks (Telegram) What's still unclear is exactly how Magic Cue will be triggered or what it will look like on screen. The assumption is that it will work in the background and appear automatically when needed, rather than requiring a prompt like Gemini. Google originally planned a "Pixie" assistant for Pixel devices, but that idea was reportedly dropped. Instead, Magic Cue appears to be part of a shift toward more ambient AI that works quietly and efficiently in the background. Compared to Apple's Siri or Samsung's Galaxy AI, Magic Cue could appeal to those who prefer fewer interactions and more timely assistance. And now that Gemini is fully integrated into the Pixel software, features like Magic Cue may give Pixel users a more seamless and proactive experience than what's currently offered by the competition.