microsoft / microsoft/onnxruntime

[Mobile] Will provide supported 16KB-page-size prebuilt Android .so in the future?

Open
#21,837 13 comments 0 reactions 0 assignees View on GitHub
contributions welcome feature request platform:mobile
Dominant language
C++
Stars
21.9k
Forks
4.2k
Avg merge
4d 11h
Merged PRs (30d)
184

Description

### Describe the issue

With Android A15 introducing a beta requirement for shared libraries to support a 16KB page size on ARM64 devices
W

source: [(https://source.android.com/docs/core/architecture/16kb-page-size/16kb)](https://source.android.com/docs/core/architecture/16kb-page-size/16kb)

We’re keen to ensure our project remains compatible with this and future Android versions, including A16.
Our current prebuilt .so files follow the older page size specifications
which might cause compatibility or performance concerns.

### To reproduce

Use the existing prebuilt .so file on an Android A15 device or emulator.
Check for failures in the VTS elf_alignment_test related to the 16KB page size.

### Urgency

Maybe Urgent

As the Android A15 adoption grows, addressing this could become more pressing. We would appreciate guidance on whether there are plans to provide a prebuilt .so file that meets the 16KB page size requirement or any recommended steps we can take to ensure continued compatibility.

### Platform

Android

### OS Version

15

### ONNX Runtime Installation

Released Package

### Compiler Version (if 'Built from Source')

prebuild

### Package Name (if 'Released Package')

onnxruntime-android

### ONNX Runtime Version or Commit ID

version 1.16.1

### ONNX Runtime API

C++/C

### Architecture

ARM64

### Execution Provider

Default CPU, NNAPI

### Execution Provider Library Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the onnxruntime-android released package and its prebuilt ARM64 .so on an Android 15 device or emulator. Check the existing artifact against VTS elf_alignment_test and determine whether the project has a path for producing a 16KB-page-size-compatible library. Done means the compatibility question has a documented answer and the supported artifact or required steps are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
build-system, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.