HaKeNdoR

This is expected if they kept the same N4 node and raised the frequency. Giving that A17 is using TSMC N3E node with raised frequency, this is odd. Or this is -maybe- the silicon lottery due to immature production? Or thermal conductivity of titanium to blame? Effectively keeping the heat inside. This could be really bad for the battery. They don't like the heat.

Google should have just spread Android features to 2, 3 years instead of as soon as possible, to match feature set of iOS. Then most Android would be getting easy 10 years of support. But then again most Android phone manufacturers selling a device, Apple is selling services and side products. Giving the die size of A16 SOC and quality hardware, Apple probably giving you their phones at cost and keeping them up to date so you can buy their other products.

Yes. But I think most importantly, Samsung can spin out budget phones and actually sell it. No one's buying cheap Apple product. Currently mostly it is a status symbol... as most-if-not-all high end phones. Don't get me wrong, great devices but we all know what kind of personalities mostly go for Apple stuff.

https://imgur.com/a/h8jkiS2 Amazing they still not able to pass SD8G2 in GPU, even per watt (...oof). Giving they used 3nm processing for these SOCs, I expected at least a little lead. Maybe a software optimization issue?

When I see someone mentioning geekbench multicore score, I just roll my eyes. Compare to other multicore benchmarks like Cinebench, Blender and most gaming bench they are way off in terms of real life performance. It looks like they bench for multicore for separate threads. You know one thread/job for one core and not one job for more than one core. This is great for mobile devices because this shared processing/tasks is a huge power draw so when it is possible using single core for processing/tasks is a huge power saver. I looks to me Geekbench always favored mobile devices and going to stay that way.