It is difficult to fathom why on earth for some induced obsolescence people actually use those extra instructions after thumb.
Breaks all sorts of backward portability. Almost assuredly at any optimisation level, the v7 instructions can offer zero speedup.
Instead they should use CLANG so the binary doesn't change even if the CPU is changed to open source.
And hand optimise the underlying C virtual machine if at all. Or machine optimise that keeping the API intact.
And the 64-bit ecosystem is 100 times more expensive because scale has been achieved with the 5 dollar Allwinner board. For again zero speedups.
And the heap size of 256 mb is just wrong when 64mb has proven quick startup and run and cohabitation. Thus halving the effective cost of RAM.
Therefore proving once and for all, that there is an intentional induced obsolescence in all of these devices.
What can developers do, discard 64-bit, reduce heap to 64-bit, and hone in on the perfect set of compiler flags for eg Entware ( their v5 binaries as base not even their v7) to run on all Android. And ART.
Even the JVM flags standardised across all Android. Possibly investigate if the java native compiler can or is in ART so that the JVM is not used at all.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer? | Terms of Service