• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [ROM] [OFFICIAL] ArrowOS 11.0 [android-11.0][vayu/bhima]

Search This thread


Senior Member
Feb 17, 2008
There is some reason for weird CPU scaling in recent version. Kernel supports only the most effective frequencies, other are removed. See:

I don't know, how this frequency table influence idle battery drain, but maybe it is worth to check.
  • Like
Reactions: kd276


Senior Member
Jun 14, 2021
There is some reason for weird CPU scaling in recent version. Kernel supports only the most effective frequencies, other are removed. See:

I don't know, how this frequency table influence idle battery drain, but maybe it is worth to check.

Dunno about such tables, i can't understand them since i do not have enought knowledge.
As you said, someone should do a test regarding battery drain with the old and last build, if is really more efficient as the dev claim or not.

Apart this the last build worked very well, tried for few days without any real issue before i rollback. If all future builds will use this new scaling then it can't be helped, if it work as the dev intended of course.
Last edited:


Senior Member
Jun 14, 2021
Please note:
Next OFFICIAL will come with source compiled vendor so a clean flash is mandatory!
anyone, who is on community edition can dirty flash and receive OTA later on.

Thank you for the update.

Clean flash is, move the rom into the internal storage, flash via twrp and do a format data, and factory reset?
Or such operations should be done before and then install after the rom from an external source (usb-c pendrive or microSD)?

Just to be sure to no mess up.

Regarding the firmware i'm still on EEA (27 may 2021), there is no update atm for my region.


Senior Member
Jun 14, 2021
You dont need any official firmware for OSS vendor builds, that's the whole point of it - device can be community supported indefinitely after it was abandoned by the manufacturer because it's built from the scratch with everything open source.

Thank you, regarding the clean flash procedure i need to format data and factory reset before the rom flash or after?

New version 07 28 is up, OSS only, anyone tried it yet? Is safe without any bug? Scrolling is smooth? Scaling is the same as the previous one?
Last edited:


Sep 18, 2019
So was on latest community build based on oss vendor. On bhima
I wiped, then flashed 12.5.2 global firmware then flashed rom, and formatted data.

After booting into the rom while signing into Google, the app would just crash, I tried to do it after the initial setup, still crashes.

So I again clean flashed it, still no luck
So I installed PE+ now it signed in properly and the rom works fine.

Does anyone using bhima have this problem?? If yes what fix you found works
  • Like
Reactions: kd276


Senior Member
Jun 14, 2021
@Erbols1n Nope, i'm on EEA firmware and i never rollback to install this rom.

From some posts above seems there are some bugs and stability issues, better to wait a bit more.

@Shanta1111 Is PE+ any good? Have you a link of the rom you are using? I'm just curious to compare both.
Last edited:
Sep 8, 2008
Espirito Santo
After 3 weeks using Arrow OS, I have my veredict.

- Amazing Performance...This fast... really fast.
- clean, no bloatware, no waste, no garbage.
- battery is a miracle from technology, 2 or 3 days easily.

- OTA is huge...Is boring download 1 gb every week, reboot on recovery, update... I probably will give more time delay until updates.
- Magisk must be reinstalled every time after OTA update (I accept sugestion).

-GCAM natively on a rom must be a plus...

- I didn't found how to change the order of the famous "3 buttons on botton", but is just a mechanical memory I delay some days to change in my mind.
- I got some problem in some apps running at 120fps. When changed to 60fps works fine... I don't think this is a problem from Arrow...
- I really don't know if keep adaptative brightess will drain the battery, so, how I read some posts about this, I keep it off.
  • Like
Reactions: kd276 and Ferby02


Senior Member
Apr 6, 2012
after installing 23.7 update, flashed magisk again, but bootloop...
anyone else experiencing this?
dirty flash from arrow may version,
i get error message
unable to ope block device...
failed to mount /data
i install arrow again and it's back working
maybe i need clean flash? i thought it's not mandatory when upgrading
I installed V11 COMMUNITY-20210728 on the V12.5.1.0.RJUEUXM and this problem occurred in the setup phase:
  1. First window (connecting to network with sim) a window pops up, that chromium has crashed.
  2. Connecting to wifi works
  3. Clicking on skip in the "Restore from other device" the screen is black.
  • Like
Reactions: kd276

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I updated #2 with a possible solution for users facing ghost touch problems in their units, this has nothing to do with ArrowOS; this is something at HW or FW level, people are able to fix it while rolling back to or firmware (you will need to boot full MIUI rom for them to do their magic on partitions)
    Even if MIUI fixes it in the latest releases, we might not know how as they do not publish changes made to their kernel source rather publish the base/initial sources only
    anyways, read more at the FAQ section in #2
    Just to be clear, I never faced these issues as I unlocked on the 7th day and never went to MIUI again nor flashed any other firmware, more than 98% of the users also do not face it at a regular basis. I have a bhima 8/128gb variant (Indian vayu with no NFC)
    Good luck
    A new update will soon be released (08-09-2021) will include:

    - Update blobs from V12.5.4.0.RJUMIXM
    - Bring back and switch to AOSP WFD implementation
    - Import remaining Xiaomi init script changes
    - Fix Ambient Display crash on clean installs
    - Misc changes and improvements

    - Merged September security patches
    - Full source changelogs here: https://arrowos.net/changelog.php

    - Requires MIUI 12.5 firmware (any region), but if you face issues with the latest firmware you can use or above (Remember you need to boot to that specific MIUI version first for MIUI to do its magic on firmware partitions before moving back to ArrowOS)
    - These builds include custom source compiled vendor and ODM partitions
    - Misc changes and improvements
    - See full device changes at: https://github.com/ArrowOS-devices?q=vayu

    kubersharma001: UPI: [email protected]

    For helping me test new changes to some feedbacks, I am usually active in my chat, you can join it here: https://t.me/kubersharma001chat

    New update is available!


    - Merge latest CAF tag on kernel (LA.UM.9.1.r1-11100-SMxxx0.0)
    - Migrate to libperfmgr power aidl hal (pixel power hal)
    - Add NotchBar killer (Can be seen in cutout menu in developer settings)
    - Update Brazillian translations in device settings
    - Cleanup init rc files/scripts
    - Sync init rc files/scripts from CAF 9.1.r1-10900 SMxxx0.0 tag
    - Cleanup unneeded blobs
    - Add missing vintf entries
    - Remove duplicate, irrelevant references in init rc files
    - Introduce raise to wake gesture
    - Enforce all RRO for all resource overlays
    - Remove QTI perfd, I/O prefetcher blobs, props in favor of moving to libperfmgr
    - Decrease minimum brightness value
    - Update SE policy rules
    - Synchronise some props from stock MIUI
    - Enable idle_state mechanism
    - Fix Clear speaker footer text issues
    - Add a summary for clear speaker and Dirac preferences
    - Zram/swap improvements
    - Move remaining device-side RROs to vendor partition
    - Misc changes and improvements

    ^ This is not a full changelog, please check device repositories (https://github.com/ArrowOS-devices?q=vayu) and source changelogs (https://arrowos.net/changelog.php) for all the changes made from the last date of update.

    UPI: [email protected]

    Support chat: https://t.me/kubersharma001
    New update will include the following changes:
    - Enable AOSP Sim toggle
    - Minor refresh rate improvement
    - Fix SafetyNet issues for all users
    - Fix GoogleCamera mod video recording issue
    - Allow all 4 rotations
    - Misc changes and fixes

    PayPal: https://www.paypal.com/paypalme/kubersharma001
    UPI: [email protected]
    who is developer of this ROM? will u fix brightness problem at next update and when? if no pls inform, i will move to lineage or crdroid, lowest brightness on arrow is trash
    Developer of this ROM definitely is not paid by Xiaomi themselfs and is not obliged to spend his valuable time to improve / fix stuff on a ROM that is voluntarily maintained, yet he does. Instead, be thankful that OP still improves upon an AOSP based ROM which X3 Pro is not designed for originally. Please do not ask for ETAs. If you have any problem about the ROM itself, follow this guide by OP: https://blog.arrowos.net/how-to-report-a-bug/
  • 49

    ArrowOS for POCO X3 PRO (vayu|bhima)

    is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.

    Website: https://arrowos.net
    Telegram: Channel | TG Portal/Links
    Github: https://github.com/ArrowOS
    Code Review: review.arrowos.net
    E-mail: arrowos.contact
    PayPal: Donate to us
    Blog: blog.arrowos.net

    Checkout more documentation at (maintainership/contributing): Check this out

    1. Audio
    2. Bluetooth
    3. Camera
    4. Dt2w
    5. Display
    6. Torch
    7. Battery/Notification LED
    8. Sensors
    9. Radio, data. networks (2g,3g,4g+volte,vowifi etc)
    10. Refresh rates(120,90,60)
    11. Headset port, charging ports, etc
    12. GPS/Location
    13. Almost everything?
    • ArrowOS ships with source compiled vendor and odm partitions.​
    1. You tell us.​
    Be sure to include a log: check how to

    Click here to Download
    Tip: Select OEM -> Device, choose Arrow version, choose the build type: "GAPPS" or "VANILLA" to download.

    • Remove any fingerprint, PIN, or password in MIUI
    • Unlock the bootloader
    • Transfer ROM to internal storage
    • Install any suitable recovery
    • Flash ROM zip file
    • Do a data wipe in recovery (format data)
    • Reboot to the system, wait and enjoy
    • Download via OTA Updater and let it automatically install; OR
    • Download an update, transfer to internal/external storage (always check file sha256)
    • Flash ROM zip and reboot.
    Read our blog article/post about:
    * HOW-TO report a bug
    * GAPPS and VANILLA variants
    * Checking build integrity

    ROM Source: https://github.com/ArrowOS
    Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_xiaomi_vayu

    ROM Firmware Required: MIUI global or you can use any latest R firmware from your region as well (firmware only)
    Donate: https://www.paypal.me/kubersharma001
    UPI: [email protected]
    You can download ArrowOS Recovery if you like or use other 3rd party recoveries


    Tip: If you are new to custom ROMs, I would suggest taking a TWRP backup/partition backup (usually: persist, efs, firmware partitions, etc) saved in your cloud or computer.

    Q1: How can I update to a new update?
    A1: Flash ArrowOS recovery and download and install the update from the OTA Updater application OR Download from arrowos.net [codename: vayu] boot to TWRP and flash it; if you are using ArrowOS recovery, copy build zip to external storage (sdcard, USB otg etc) and install via "Apply system update option"
    If you are on PC, you can also use adb sideload while being on recovery

    Q2: Why is Mi8 (dipper)/walleye oreo or any other device's build fingerprint and desc props/values are used?
    : As most of the custom ROM users might be aware that SafetyNet cannot pass with devices own build fingerprint props due to the multiple checks or other aspects which is unknown, done by the OEM/Google which fails hence nowadays devices are generally spoofed with build fingerprint and description props of devices which passes CTS/SafetyNet like from a device with Android Oreo or Pre Android Oreo (walleye oreo; mi8 oreo, etc) or from latest Pixels (like redfin)
    This device as of now uses Mi8 (dipper) build fingerprint and description to pass SafetyNet!
    (In future release: It can change to Pixels or some other device too just to "Pass SafetyNet checks") hence don't consider this as some lame reason to spam or message about.

    Q3: Facing ghost touch issues on your device?
    This issue has been recognized by Xiaomi as a fault in their MIUI firmware, I am not yet sure if this is completely a hardware fault or just a firmware fault with specific variants
    I have an Indian 8/128 variant and I never faced such issues.
    Since Xiaomi does not release newer changes done to the kernel source, we are stuck with the initial R source release hence we don't know what changes they made to fix it on MIUI if they ever did
    But, some people have fixed ghost touch issues by :
    * Flashing MIUI full MIUI rom, booting to it, setup up everything (like registering the fingerprint, etc), and then moving to custom ROMs.

    [* Using 120hz? (not confirm but 2 users have suggested doing this has solved sluggish touch issues for them)]

    If this method works for you do not update firmware unless you are sure that will work
    This is not a global issue, only a limited number of people face it!
    Also, users have faced ghost touch issues on MIUI versions aswell, so this is not something custom from related! It is hardware/firmware level

    Do not report bugs with mods or custom kernels.

    You can chat with me on Telegram: https://t.me/kubersharma001chat
    Hey. just wanted to notify you all that I am going to remove the "Smart Charging" feature in future builds, Also I suggest using mods/ modules which simulate similar behavior as the smart charging feature IS NOT RECOMMENDED!

    A bunch of Xiaomi devices (at least vayu, surya etc for sure) (or lets say some QUALCOMM devices in general too) have somewhat buggy PMIC ( i.e Power Management IC) and facing the issue is rare in most scenarios (some can face it without using these features too) till you don't mess power_supply or anything related to PMIC mods or features like smart charging, idle state charging, those Magisk modules for smart charging like ACC or whatever can trigger the PMIC to bug out as well and in that case your battery will be drained, won't charge unless you reboot to bootloader till the time you can. If you don't do that and let it drain (which I remind you might be quicker than usual) it might just go DEAD.

    Ref: https://github.com/lybdroid/poco-x3-pro/issues/1

    Most people might not face the issue, but still, there is a chance, and let's not risk it. I would suggest avoiding draining your battery to 0.

    I am not saying the above-mentioned features or mods are bad or broken but there is a slight chance something bad can happen, so my removal of this feature on vayu is just a safe play till we know something better
    "Be safe than sorry"
    Fixes/Changes done for next build/update:
    - Yellow tint on screen
    - Lowers vibration intensity to a decent level
    - Force volume steps to 25 as some MIUI vendors are forcing this to insane 150 volume steps, yikes.
    - Fix Recents Overview sluggishness
    - Ship GCamGoPrebuilt instead of AOSP camera2
    - Other minor improvements and fixes.
    BTW, Incase anyone wasn't aware you can see last 24 hour active/installs statistics here:
    vayu is now under top10

    Changes for Next update:
    Fixed WFD showing green screen while casting to laptop