Android 12 exposure: Google wants to abandon 32-bit support


Android 12 exposure: Google wants to abandon 32-bit support

Technical editor: Wang Zhizhi from the editorial department
SegmentFault has he reported the official account number: SegmentFault

Recently, the media exposed the x86 of Android s (sorted by alphabet, corresponding to Android 12 system)_ 64 emulator has stopped supporting 32-bit, which means that all applications and support libraries must be compatible with 64 bit security and protocol since Android s.

After implementing the 64 bit architecture on Android apps through the Google play store last year, Google seems to be following Apple’s footsteps and transitioning the very complex Android OS ecosystem to the 64 bit architecture.

However, this is a very important step to improve the efficiency, function, reliability and security of the entire Android OS ecosystem.

Forced transition to 64 bit has several advantages. Eliminating the compatibility layer of older 32-bit applications frees up a lot of ram. This will allow application developers and OEMs to provide better performance for smartphones. Although new smartphones have more than 4GB of ram, developing markets still have devices with less RAM.

In addition to ram, Android OS and support architecture will take up less space. Although the changes are small and will not have a significant impact, they are a waste of space, especially for large apks that do not use bundled software.

And the biggest improvement of all 64 bit Android will be improved security. 64 bit architecture is significantly more secure and reliable than 32-bit architecture.

In addition, SOC manufacturers like arm will certainly welcome this step, because the company’s new cortex-a65 is not supported by aarch32 isa when it leaves the factory.

Google said it had converted all applications to 64 bit and ensured that the app ecosystem was fully operational when Android s was launched. Experts pointed out that at present, all functions except some media codecs should work normally. This is mainly because the simulation platform does not support the new codec2 standard, but lags behind OMX (the latter is the old 32-bit media component).

Codec2, by the way, is also 32-bit. In short, there is still a lot of work to do to ensure that all media formats play properly on all 64 bit Android.

Android 12 exposure: Google wants to abandon 32-bit support