In my experience, Sony phones are great. The pain point is always buying them: they're unavailable in many market,s and their model naming conventions make no sense at all.
I thought about switching to Android for some time. And other than Samsung the 2nd option I got was Sony. And May be they were the only non-Chinese brand options since Google Pixel is not available in my area.
My biggest problem with Sony is with the 21:9 Aspect Ratio. I Just cant stand it. And 2nd being software update is still relatively poor.
It was probably factory overclocked for better cpu benchmarks on release. Now once all these release benchmarks are public, they can undo the overclock
Apple wouldn't take the PR hit from these overheating issues only to achieve higher scores on benchmarks that basically nobody factors into choosing a phone.
We also don't know yet if they're downclocking now or if there was some other issue; I'm eyeing the new USB-C charging since that was a real problem on earlier MBPs.
For the downvoters: there is precedent in this industry for this behavior. Samsung has been caught doing it, and I have vague recollections of HTC being caught as well although I can’t find a reference at the moment.
If you are asking for proof of this claim, you obviously won’t find it. But when there’s smoke…
There could also be many reasons besides this. If you want to point out Samsung and HTC having done this in the past, you can just say that. Honestly I'm a lot less surprised hearing that kind of news about those two, cause they don't have the same reputation to protect.
Or it could just be better thermal management, i.e. slower ramp up.
It could also be as simple as a bug causing the CPU to waste additional cycles in a specific set of circumstances, which would also partially explain the reports of excessive battery usage.
Considering that the iPhone 15 Pro is basically just "last years phone" in new clothes and with a bigger battery, i find it hard to believe that it would suddenly go from no overheating issues to massive issues.
> Considering that the iPhone 15 Pro is basically just "last years phone" in new clothes and with a bigger battery, i find it hard to believe that it would suddenly go from no overheating issues to massive issues.
>sell same phone as last year, but 10% faster
>same chip, just overclocked 10% more
>10% overclock causes phones to overheat
>push update to downclock 10%
>marketing and engineering teams high five each other
My iPhone 15 Pro Max hasn’t run hot since day one when it was downloading everything. Seems fine.
I am bugged though, about the changes on watchOS for switching watch faces. And everything seems harder — even starting workouts. Also requires additional steps to end a workout. It’s not better for me. Enough to hold off on getting the updated Ultra model.
If they made it harder to accidentally switch watch faces, I’m all in. I kept looking at my watch and finding the face had changed due to it being too easy to press it and change it. Make it so that you have to actually choose something. I finally had to delete all other faces so my preferred face was always there.
So does anyone know if Apple intentionally code hijacks popular apps to make them perform better on their phones yet?
There are a number of specific hacks in WebKit to make big websites work well, and I would have thought by now that Apple does some sort of coalescing or trampolining for the big names in tech and most popular apps.
Microsoft did similar work for Windows in the distant past. Not sure if they still do.
So the claim is that it would be easier to develop an entire binary hot-patching mechanism to apply reverse-engineered optimizations than to send an email to a colleague saying “this runs pretty hot, ask them to fix it”?
I was on iOS 17 beta, and saw, like almost every other beta tester, that their betas caused thermal issues that didn’t exist in iOS 16 on the same hardware. Our phones were just hot for no reason, and battery life tanked. It was the major complaint, and it hadn’t been fully addressed by the release candidate.
Apple doesn’t need to violate physical conservation laws; they just need to fix embarrassing regressions.
33 comments
[ 0.76 ms ] story [ 138 ms ] threadLooking at the Sony because it has all the top specs, including sdcard, headphone jack, no notch, headphone amp.
This was actually a widespread software issue, triggered by some apps. I've seen it happening in a last year iPhone 14 running Instagram.
So I would say that it is an iOS 17 issue, more than a hardware issue.
https://www.froresystems.com
My biggest problem with Sony is with the 21:9 Aspect Ratio. I Just cant stand it. And 2nd being software update is still relatively poor.
We also don't know yet if they're downclocking now or if there was some other issue; I'm eyeing the new USB-C charging since that was a real problem on earlier MBPs.
If you are asking for proof of this claim, you obviously won’t find it. But when there’s smoke…
(Also I didn't downvote cause I'm not about that)
Mine has only gotten faster after the patch? Any evidence to backup your claim?
https://imgur.com/a/SR1hoXo
It could also be as simple as a bug causing the CPU to waste additional cycles in a specific set of circumstances, which would also partially explain the reports of excessive battery usage.
Considering that the iPhone 15 Pro is basically just "last years phone" in new clothes and with a bigger battery, i find it hard to believe that it would suddenly go from no overheating issues to massive issues.
It's called modern software
New titanium casing could be an issue.
I am bugged though, about the changes on watchOS for switching watch faces. And everything seems harder — even starting workouts. Also requires additional steps to end a workout. It’s not better for me. Enough to hold off on getting the updated Ultra model.
There are a number of specific hacks in WebKit to make big websites work well, and I would have thought by now that Apple does some sort of coalescing or trampolining for the big names in tech and most popular apps.
Microsoft did similar work for Windows in the distant past. Not sure if they still do.
So yes. Also, this already happens with other software on Apple’s platforms. My question is does anyone know if they also do it with iOS native apps.
We know they do it on macOS.
Apple doesn’t need to violate physical conservation laws; they just need to fix embarrassing regressions.