read it for 5 second, i mean it

read it for 5 second, i mean it

izumi

Notes Before Flashing

Please, explore the ROM and its features properly first before reporting random/basic stuff.

You won’t run into any serious problems if you spend just 5 seconds reading these notes.


Known Issue: Android/data / Storage Bug

This is already a common issue on Android 16, especially around QPR1/QPR2. It can happen randomly, and not every user will face it.

Yes, even I got this bug. But at this build, i didn't faced it at all tho.

The symptom is usually like this:

  • Apps cannot create folders inside Android/data or Android/media
  • Some apps behave weirdly because they cannot access internal storage properly
  • App data/download folders fail to generate
  • Some apps may look broken even though the ROM itself boots fine

From what I know, this issue is often related to broken /data behavior after using custom recoveries like TWRP, PBRP, OrangeFox, etc. It is not only happening on this ROM.

How to fix it?

You have two options:

  1. Flash the A16 Storage Fix module
  2. Flash the ROM properly / fix your data partition properly
    Here's the guide

If you hit this storage bug, try the fix above first before saying the ROM is broken.


Known Issues: ROM only works properly with Latest OrangeFox

This is most likely because this AxionOS release already includes a number of A17-related changes, such as decryption updates. It's not a big deal.

Fix: just use the latest OrangeFox.

If you're on an older OrangeFox or other recovery and run into bootloops or decryption failures, that's not a ROM bug. Please update your recovery before reporting issues.


Other Issues?

This build is released publicly, but please understand that it may still have random issues for some users.

If you find a real bug, report it properly with logs and clear steps to reproduce.

Do not just say “bug” without context.

If you install weird Magisk / KernelSU / performance / tweak modules and then something breaks, I probably cannot help.

Please test the ROM first in a clean state before adding random modules.

If the issue only happens after installing your modules, then it is not my problem.

Useful logs:

  • logcat
  • dmesg
  • ramoops / pstore if available

Without logs, I cannot magically fix it.






Report Page