• 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

kd276

Senior Member
Jun 14, 2021
317
63
Device Changelogs:
09/07/21:
- July security patches
- Fix issues with gamepad controllers
- Fix the "OK Google" voice trigger detection issue
14/07/21
- Improvements in the kernel source, upstream to latest CAF tag
- Manual Provisioning works now (Magically)
23/07/21
- Fix power-off charging anim issues
- Misc changes

Rom Changelogs:

This is the final official build which requires pre-installed manufacturer/OEM vendor and ODM partitions. OTA updates from this build will be blocked as a safeguard
After a while, when most who have transitioned to this update, I will release the official build with custom vendor and ODM partitions (compiled from source)
If you want to be the early adopters, you can flash the "community" variant from the website.

Donate(maintainer):
https://www.paypal.com/paypalme/kubersharma001 | [email protected]

ArrowOS CORE team needs your help! have a read at: https://t.me/ArrowOS/1957
We are upgrading our Infra servers as we recently lost one, help us to achieve the goal by donating here: http://paypal.me/TeamArrowOS

Thanks fo the update. Update succesfully via OTA/TWRP.

So from the next update the custom vendor will be included in the rom, i understand it right?

The firmware is unrelated and should be updated separately? Actually i have 12.5.1.0 (RJUEUXM), the last one.
 
Last edited:

kd276

Senior Member
Jun 14, 2021
317
63
Oh, this is quite good, good find, will try it. Thanks mate.

Two questions:

- Btw, you know why my device sometimes have notification with a delay? Expecially sms and the alarms, dialer and incoming calls works properly.

Maybe i should disable battery optimization since it freeze some apps in background? Or i need to give access to the messenger and clock unlimited data? This happens only with these two apps.

- There is also a way to reduce the display time of silenced notifications? I can disable them entirely but i prefer to reduce the timer.
For example when i use an app like root explorer a message that i'm using root permissions appear in a white window box at the bottom, and it go away only after 30 seconds, very annoying.
 
Last edited:

pl1992aw

Senior Member
Apr 5, 2019
1,040
633
Oh, this is quite good, good find, will try it. Thanks mate.

Two questions:

- Btw, you know why my device sometimes have notification with a delay? Expecially sms and the alarms, dialer and incoming calls works properly.

Maybe i should disable battery optimization since it freeze some apps in - background? Or i need to give access to the messenger and clock unlimited data? This happens only with these two apps.

Maybe you can try alter some settings in the battery section.
  • Turn off Battery Saver
  • Turn off Battery Manager
  • Thermal Profiles change to according profiles if exist
  • Turn off Do not disturb mode
Personally did not miss the alarm clock in GApps version, which uses Google clock and messenger for SMS.

- There is also a way to reduce the display time of silenced notifications? I can disable them entirely but i prefer to reduce the timer.
For example when i use an app like root explorer a message that i'm using root permissions appear in a white window box at the bottom, and it go away only after 30 seconds, very annoying.

That whitish window at the bottom is caused by Magisk if you are using Magisk.

Go into Magisk, press the shield icon at the bottom, choose the app you don't want to show and turn off the notification of it.

Not sure what setting to alter to reduce the timer. Personally disable it.
 
  • Like
Reactions: kd276

kd276

Senior Member
Jun 14, 2021
317
63
Maybe you can try alter some settings in the battery section.
  • Turn off Battery Saver
  • Turn off Battery Manager
  • Thermal Profiles change to according profiles if exist
  • Turn off Do not disturb mode
Personally did not miss the alarm clock in GApps version, which uses Google clock and messenger for SMS.

I did all this, i'm testing now, but about thermal profiles they are all settled in default mode, dunno what's the correct profile for every file.

I think that the issue can be caused by battery manager since is clearly say that is limit apps not often used.

That whitish window at the bottom is caused by Magisk if you are using Magisk.

Go into Magisk, press the shield icon at the bottom, choose the app you don't want to show and turn off the notification of it.

Not sure what setting to alter to reduce the timer. Personally disable it.

Yes, i can disable it via magisk, it have two options, "toast" and "disable", guess is the only way.

ps: Didn't notice before but magisk app appear to be not installed (N/D), need to install it too or don't matter?

Screenshot_20210723-172416.png

Anyway, thank you for all the info, very usefull.
 
Last edited:

kd276

Senior Member
Jun 14, 2021
317
63
OTA actually is a full ROM, it overwrites boot.img effectively removing Magisk. You have to root your phone again.

Are you sure? Anyway reinstalled and check with root checker and it said my device is rooted as expected like before.

Seems an option that only devs can add, regarding the display time of silenced notifications.
 
Last edited:

popej

Senior Member
Feb 17, 2008
98
24
www.gmaptool.eu
Just have noticed, that latest version of ROM has almost no CPU scaling. Minimal frequency for little CPU is about 1700MHz, for big is 1400Mhz. I have returned to version 20210709 and there is OK, little CPU goes down to 576MHz, big to 710/825Mhz.

I can't find any reason for these settings, looks like a bug, which will drain battery.
 

kd276

Senior Member
Jun 14, 2021
317
63
Just have noticed, that latest version of ROM has almost no CPU scaling. Minimal frequency for little CPU is about 1700MHz, for big is 1400Mhz. I have returned to version 20210709 and there is OK, little CPU goes down to 576MHz, big to 710/825Mhz.

I can't find any reason for these settings, looks like a bug, which will drain battery.

Seems the case, but i don't know if it was bugged before or now since the frequencies are within the correct range.

Screenshot_20210723-201944.png
 
Last edited:

popej

Senior Member
Feb 17, 2008
98
24
www.gmaptool.eu
Minimum CPU frequency can't be corrected with kernel manager, since table of available frequencies is truncated and lower values are missing. Weird, previous version had table with frequencies as low as 300MHz for little CPU, while using limit 576Mhz.

@Jaftdroid: Latest ROM doesn't show estimation, only % of battery.
 

0b4

Senior Member
May 8, 2012
117
41
Minimum CPU frequency can't be corrected with kernel manager, since table of available frequencies is truncated and lower values are missing. Weird, previous version had table with frequencies as low as 300MHz for little CPU, while using limit 576Mhz.

@Jaftdroid: Latest ROM doesn't show estimation, only % of battery.
That's weird. I already noticing slightly worse barry life. In 10 minutes of light usage battery already dropped by 3 percent. Let's hope dev are watching the thread and can say something about it.
If I want to go back to previous version, can I flash it without any data loss? Can I dirty flash? What should I or have to wipe after install?
 
  • Like
Reactions: kd276

Lu5ck

Senior Member
Dec 18, 2013
103
27
Fortunately, I didn't do the OTA. I already know from experience on last OTA that arrowOS is really bad when come to it. Evidently, now is kernel bug. At this moment, I wouldn't recommend arrowOS as reliable daily driver, unless you intent to not OTA forever. :D

OTA actually is a full ROM, it overwrites boot.img effectively removing Magisk. You have to root your phone again.
when u flash a rom, it will look through its addon script folder and perform these script
the magisk script is in such folder and will automatically reinstall magisk after the rom is flashed
 
  • Like
Reactions: kd276

pl1992aw

Senior Member
Apr 5, 2019
1,040
633
ps: Didn't notice before but magisk app appear to be not installed (N/D), need to install it too or don't matter?

The app Magisk app is installed.

Ultima shows latest stable update by the author on internet. Turn on internet and open Magisk app, so Ultima will show something. (N/D) is probably abbreviation of No Data.

Installata is installed.
 
  • Like
Reactions: kd276

kd276

Senior Member
Jun 14, 2021
317
63
The app Magisk app is installed.

Ultima shows latest stable update by the author on internet. Turn on internet and open Magisk app, so Ultima will show something. (N/D) is probably abbreviation of No Data.

Installata is installed.
Thanks.

Guess i have to revert to the previous version since this one appears to be bugged. Will do via TWRP and wipe cache+dalvik classic method.

Fortunately, I didn't do the OTA. I already know from experience on last OTA that arrowOS is really bad when come to it. Evidently, now is kernel bug. At this moment, I wouldn't recommend arrowOS as reliable daily driver, unless you intent to not OTA forever. :D
I see, then is better to flash via twrp, anyone tried flashing the last version via twrp and not ota and see if it solve the scaling issue? Just wondering if is a permanent bug or OTA bug. Anyway i rollback too.
 
Last edited:

0b4

Senior Member
May 8, 2012
117
41
Good, then is better to flash via twrp, anyone tried flashing the last version via twrp and not ota and see if it solve the scaling issue? Just wondering if is a permanent bug or OTA bug.

OTA update is booting into twrp to install the update also, so there is no difference between the two methods.
 

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 12.0.4.0 or 12.0.6.0 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
    4
    A new update will soon be released (08-09-2021) will include:
    DEVICE

    - 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

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

    NOTE
    - Requires MIUI 12.5 firmware (any region), but if you face issues with the latest firmware you can use 12.0.4.0 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

    Donate:
    ArrowOS:
    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

    Thanks!
    4
    New update is available!

    Changelogs:

    - 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.

    Donate:
    UPI: [email protected]

    Support chat: https://t.me/kubersharma001
    3
    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

    Donate:
    PayPal: https://www.paypal.com/paypalme/kubersharma001
    UPI: [email protected]
    3
    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
    logo.png

    ArrowOS for POCO X3 PRO (vayu|bhima)

    ABOUT
    ArrowOS
    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

    WHAT WORKS?
    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?
    NOTE:
    • ArrowOS ships with source compiled vendor and odm partitions.​
    WHAT DOESN'T WORK ?
    1. You tell us.​
    Be sure to include a log: check how to

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

    Instructions
    FIRST INSTALL?:
    • 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
    FLASHING UPDATES?:
    • 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 12.5.2.0 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]
    14
    You can download ArrowOS Recovery if you like or use other 3rd party recoveries

    FAQ::

    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?
    A2
    : 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?
    A3:
    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 12.0.4.0/12.0.6.0 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 12.5.3.0+ 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
    12
    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!
    BECAUSE:

    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"
    11
    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.
    9
    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