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

Search This thread


Senior Member
Oct 7, 2007
Motorola Defy
Google Nexus 5
Sadly it is indeed deprecated, but you don't usually need all the security patches.
Last few final builds are quite stable and good to use for android 11 users.
Appreciate your confirmation, though we all keep our fingers crossed that someday you would push out an update when necessary, even if semi annual.
Thanks again for all the hardwork and keep up the good work.


Senior Member
Oct 18, 2012
Hi there! Is there any kind of archive versions of ArrowOS? The archive part of the official site contains just one or two last versions. I need more old.
May be some one holds it on HDD or in cloud?
Last edited:


New member
Feb 7, 2012
I cannot recommend this ROM. I've installed it on my new POCO X3 Pro and battery drain is insane. It's even draining with underclocked by 25%, battery saver, servicely and naptime. Quickcharge is also not working every time (seems to be random - tested different cables + chargers).


Senior Member
Jan 2, 2013
Did anyone manage to find a working Call Recorder for this specific ROM? I know it has one integrated, but I would like an independent solution.

If you know of one that works, please reply. Thank you.
Aug 10, 2017
Can someone please recomend a module or trick or tut to have this function "No Password After Boot" the function is to use fingerprint after a reboot instead of password


Senior Member
Jan 2, 2013
@kubersharma001 Any ideas why hardware lights service crashes on every boot? Is it a bug, or nothing I should worry about?


    42.7 KB · Views: 6


Senior Member
Jan 2, 2013
And does anyone have Whatsapp notification issues?

Also, this bug. 2 Android Adaptive Notifications options. Can anyone on AOS 11 confirm the same issue, please?


  • Screenshot_20220508-144713.png
    70.3 KB · Views: 33
Last edited:


New member
Apr 21, 2021
I have:
Upload to onedrive for you?


Senior Member
Mar 9, 2017
I have an issue: for some reason, the phone uses a lot of mobile data to perform "system updates".


I would like to know what exactly are those "system updates". I don't think it is updating new versions of the OS, since on under the Updater it doesn't show a newer version of the OS having being downloaded.

Auto-update Apps is disabled under the PlayStore, and updates are usually set to Wi-Fi only most of the time anyway. So I have no idea what kind of system updates ate over 3.5GB of data in a few days, but I know it isn't sustainable because I do not have that much data to burn (that is why I set my warning at 5GB). Thanks.


Senior Member
Oct 18, 2012
Forget it. I`ve already found those ROMs on sourceforge. They are some buggy, so still using the most stable january update.
  • Love
Reactions: NapsterAD


New member
Jun 6, 2022
I have:
Upload to onedrive for you?
Please upload and share us my friend , i lost that version , that was the last version on which i was able to play competitive scrims. Help please. Upload ASAP
Last edited:


New member
Jun 6, 2022
Forget it. I`ve already found those ROMs on sourceforge. They are some buggy, so still using the most stable january update.
Please upload and share the january 21 build, I tried to ping developer . he replied that he dont have the backup of it , Please Upload it ASAP. I am not able to play scrims.

Top Liked Posts

  • There are no posts matching your filters.
  • 66

    ArrowOS for POCO X3 PRO (vayu|bhima)

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

    Telegram: Channel | TG Portal/Links
    Code Review:
    PayPal: Donate to us

    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:
    Kernel Source:

    ROM Firmware Required: MIUI global or you can use any latest R firmware from your region as well (firmware only)
    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 [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:

    You can check out my blog post on pocox3pro:
    Why Encryption is important on Custom ROMs, have a read:
    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.


    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