PojavLauncher's 32-bit support

Most of you, Android users, who are reading this now, won't be bothered by this documentation, but for the poor souls who have a 32-bit device, let's press L F to pay respects to them.

ARM transitioned into the modern arm64/aarch64 architecture, which significantly improved utilization and stability compared to its widely used predecessor, arm/aarch32, while also maintaining compatibility using code blocks for parity between both architectures.

We won't get into much detail regarding it, but if you'd like to learn more about it have a read of this documentary about the ARM platform. (opens new window)

You may encounter issues while using PojavLauncher on 32-bit devices. Here's a list of things that are known to be problematic:

RAM Allocation

Real 32-bit devices (32-bit hardware and firmware), can't allocate more than 768MB of RAM to PojavLauncher. This CAN'T be changed even if the device has extra RAM to spare.

• Examples of real 32-bit SoCs: Qualcomm Snapdragon 801, 800, 600, 400, S4, S3, S2, S1, etc.

64-bit devices limited to 32-bit firmware can't allocate more than ~1000MB of RAM. As said earlier, this CAN'T be changed.

• Examples of 64-bit SoCs limited to 32-bit firmware: MediaTek Helio G37, G35, G25, P35, P25, P23, P22, etc.

Performance

Due to 32-bit's processing speed limit, Minecraft's performance is always compromised. Even with optimization mods installed, you may receive big stutters even on the lowest settings. Decreasing RAM Allocation may help performance in some scenarios.

Compatibility

As of snapshot 24w14a (opens new window), Minecraft has officially dropped support for the 32-Bit architecture, ultimately meaning if you own a 32-Bit device you will NOT be able to run Minecraft 1.20.5+ on said device.