Attached: 1 image
Wait, 20 *milliseconds*? Either their kernel scheduler config is completely out of whack, or ARM/Qualcomm really screwed this one up.
Apple cores can boost to max in around 50 *micro* seconds. 20 milliseconds is just broken. That's more than one frame, and that's how you get janky UI response and dropped frames. I hope this was a config issue and these cores/designs really don't take 20ms to increase clocks (I could see that with a really bad regulator/power delivery system...)
From: https://chipsandcheese.com/2023/08/11/arms-cortex-a710-winning-by-default/
I don’t define anything, there are Java standards which define source code, binary code and runtime behaviour compatibility. That makes it possible to run Java apps on non-Oracle JVMs, use non-Oracle tools, etc. Android doesn’t have anything Java outside of source code. And even Java source code is not 100% compatible. It’s just not Java at all and never was. You can’t even use many open source Java libraries on Android because they are not Android compatible at the source level.
I don’t define anything, there are Java standards which define source code, binary code and runtime behaviour compatibility. That makes it possible to run Java apps on non-Oracle JVMs, use non-Oracle tools, etc. Android doesn’t have anything Java outside of source code. And even Java source code is not 100% compatible. It’s just not Java at all and never was. You can’t even use many open source Java libraries on Android because they are not Android compatible at the source level.