![[IMPORTANT] Android 16K Replace Information – Cocos Creator](https://i0.wp.com/forum.cocosengine.org/uploads/default/original/3X/c/9/c9a024cd3656916ac85bb3a01034f8075bc8f827.png?ssl=1 "[IMPORTANT] Android 16K Replace Information – Cocos Creator")
Good day builders,
To enhance the engine compatibility and efficiency on sure Android units (for instance terminals with ARM64 structure), we lately applied help for the Android 16KB reminiscence web page dimension function. The associated code modifications are prepared — we hereby invite you to combine and take a look at them to assist guarantee stability and reliability of this replace.
Core contents of this replace
- Engine core repository (
engine)
- Contents: Key code modifications that add help for Android 16KB web page dimension.
- Standing: Submitted as PR #18910 and awaiting merge and checks.
- Exterior dependency repository (
exterior)
- Contents: Primarily upgrades V8 model (11.8 → 12.7.140) to match the brand new function. See PR #499.
Different: keep away from package deal dimension enhance from V8 improve
Should you favor to not improve V8 (for instance to regulate package deal dimension), we offer alternate options:
- Engine code modifications: manually apply the code modifications referenced within the
enginePR #18999 to your engine model. - exterior V8 libraries: replace V8 libs (together with x64 and arm64) from the offered PR #501.
Key testing areas and requested suggestions
Please take a look at the next situations and report any points:
- Core regression testing: confirm primary engine functionalities on ARM64 Android units (particularly units utilizing 16KB web page dimension).
- Compatibility: test for any venture compatibility points earlier than and after the V8 improve.
- Efficiency: monitor modifications in startup time, reminiscence footprint, and JS execution efficiency.
- Stability: run long-duration checks to detect crashes or reminiscence leaks.
The best way to begin testing
- Get the code:
- Change to the repository department
v3.8.7-16kand construct from that department. - The
exteriorrepo makes use of massive information — please set up git-lfs earlier than downloading.
- Put together the atmosphere:
- [Strongly recommended] Improve your improvement atmosphere: replace Android Studio to 2024 or later to make sure the construct course of handles new dependencies and configurations.
- [Important] Clear native venture:
- If you have already got a constructed Android venture domestically, please BACK UP your venture’s
nativelisting (when you’ve got customized modifications). - DELETE the
nativelisting and associated construct caches (e.g.construct), then rebuild to make sure all native dependencies are accurately up to date.
- If you have already got a constructed Android venture domestically, please BACK UP your venture’s
For Cocos Creator 2.x customers
Cocos Creator 2.x customers please seek advice from the engine-native repo PR #4403 for validation. Throughout verification, make sure you use NDK 28 or newer.
Thanks for this discover.
Is that this repair applied over the v3.8.7 launch? In case sure, the one wanted step can be to do the engine replace?
it’s simply an instance for 3.8.7, comply with the PRs, it may very well be used for 3.6. and three.7.x as effectively
