• 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
OTA update is booting into twrp to install the update also, so there is no difference between the two methods.

I see, then is a bug on the rom itself no matter the method, well, no problem.

Maybe the fact i have delay on notifications can be also related to this since i didn't have this ussue before, now that i think about it.

Confirm, the scaling with the previous version working properly.

Screenshot_20210724-075006.pngScreenshot_20210724-075037.png
 
Last edited:

0b4

Senior Member
May 8, 2012
117
41
I see, then is a bug on the rom itself no matter the method, well, no problem.

Maybe the fact i have delay on notifications can be also related to this since i didn't have this ussue before, now that i think about it.

Confirm, the scaling with the previous version working properly.

View attachment 5369403View attachment 5369401
I can confirm too. Dirty flashing back the previous version in TWRP and wipeing cache and dalvik, everything works fine. Scaling issue is gone too.
 
  • Like
Reactions: kd276

Jaftdroid

Member
Apr 6, 2021
22
8
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.

Hello,

Updated to the last version and still seeing battery estimates when I drop down QS (eg: 1d & 7h).
 

kd276

Senior Member
Jun 14, 2021
317
63
Hello,

Updated to the last version and still seeing battery estimates when I drop down QS (eg: 1d & 7h).

This work as intended, but there is no way to change this when you swipe down the quick settings, there is not an option.

Last version of this rom is bugged, see above, it drain your battery since scaling governor do not work properly, you should downgrade to the previous one till the devs fix it.
 

Jaftdroid

Member
Apr 6, 2021
22
8
This work as intended, but there is no way to change this when you swipe down the quick settings, there is not an option.

Last version of this rom is bugged, see above, it drain your battery since scaling governor do not work properly, you should downgrade to the previous one till the devs fix it.

Thanks for warning me man. I'll do it. I'm anyways thinking to go back to the stock MIUI (or xiaomi.eu's MIUI) just for a while.

Thanks again.
 

kd276

Senior Member
Jun 14, 2021
317
63
Thanks for warning me man. I'll do it. I'm anyways thinking to go back to the stock MIUI (or xiaomi.eu's MIUI) just for a while.

Thanks again.
MIUI is too heavy and fancy for me, will never come back from Android stock, prefer simplicity and performance, but xiaomi.eu build is indeed a good compromise if you like MIUI and is more customizable.
 

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.

edit
After several test, the issue of not receiving notifications while the screen is off is that the system appear to freeze the stock apps. It go into a hybernation/doze mode that completely kill the apps notifications. Notifications of sms arrive istantly if the screen is not off.

The laughtable thing is that the app messages have the battery optimization/doze greyed out, i can't change it because there are no options to do so.

Wondering if the zipped magisk module to disable the doze at every boot i found here in the Oneplus forum can be of some help, but i read it can case boot loop. >_>
 
Last edited:

punpun1

Member
Feb 8, 2018
6
1
Hello,

I am running latest official ArrowOS (2021-07-23) and encountered a very specific problem regarding games that have LAN server hosting.
For example in Minecraft, I can join LAN worlds hosted on other devices just fine. However if I open the world myself, I can't join from other devices, because it is not visible.
This worked on MIUI just fine, and I can confirm it is not an issue regarding my network, because I can host on other devices.

I know this is not a significant problem and it doesn't impact all (if any) ArrowOS users, but I would be grateful if you could take a look.

Here's the logcat (I specifically ran Minecraft and entered a world, which should have started LAN hosting):

EDIT:
I am also running Magisk with no modules, but I don't think it would impact outbound network connections.

EDIT 2:
I have switched back to previous official because of CPU scaling issue, but this LAN connection issue is still present.
 
Last edited:
  • Like
Reactions: Hani El Pakistani

kd276

Senior Member
Jun 14, 2021
317
63
Hello, want to reinstall from scratch the rom and erase all my personal settings, factory reset and wiping data/dalvik/cache have no effect, my settings still back at the next reboot. Need to do /formata data or the /system folder have a different name?
 
Last edited:

0b4

Senior Member
May 8, 2012
117
41
Hello, want to reinstall from scratch the rom and erase all my personal settings, factory reset and wiping data/dalvik/cache have no effect, my settings still back at the next reboot. Need to do /formata data or the /system folder have a different name?
Wipe/format data (type yes) - Isn't it what you are looking for? I don't know if this will format the entire internal storage, so I don't know how can you flash the zip after this. Maybe have an otg flashdrive with the necessary files, just in case.
 
  • Like
Reactions: kd276

kd276

Senior Member
Jun 14, 2021
317
63
Wipe/format data (type yes) - Isn't it what you are looking for? I don't know if this will format the entire internal storage, so I don't know how can you flash the zip after this. Maybe have an otg flashdrive with the necessary files, just in case.

Yes, thank you, the correct command is format data, and yes, it format internal storage too (sdcard). ArrowOS is untouched but resetted to default settings.

Believe that format data wipe the OS too, but was not the case, just a hard reset, that what i was looking for.

Unfortunately this doens't solve the sms delay issue i have when the phone is in sleep mode, seems a problem with doze in all android phones from android 6.x, more or less android devs never cared to solve such annoying bug.

Is /metadata the /system folder? Because i didn't found it so i'm guessing here.

Anyway, i read elsewhere that disabling doze is possible via adb and can solve the freezing apps :
Code:
adb shell dumpsys deviceidle disable

However such command should be performed everytime at boot, is frustrating.

There is a script or a command that can automatically do this command everytime the device boot into the os? Would be more practical to have.
 
Last edited:

0b4

Senior Member
May 8, 2012
117
41
Yes, thank you, the correct command is format data, and yes, it format internal storage too (sdcard). ArrowOS is untouched but resetted to default settings.

Believe that format data wipe the OS too, but was not the case, just a hard reset, that what i was looking for.

Unfortunately this doens't solve the sms delay issue i have when the phone is in sleep mode, seems a problem with doze in all android phones from android 6.x, more or less android devs never cared to solve such annoying bug.

Is /metadata the /system folder? Because i didn't found it so i'm guessing here.

Anyway, i read elsewhere that disabling doze is possible via adb and can solve the freezing apps :
Code:
adb shell dumpsys deviceidle disable

However such command should be performed everytime at boot, is frustrating.

There is a script or a command that can automatically do this command everytime the device boot into the os? Would be more practical to have.
If you have an otg flash drive, place the arrow os rom on it, and in twrp choose the button wipe, and then format data, then install the rom from the flash drive, and at the end wipe cache and dalvik. BTW I don't have the sms notification delay that you are talking about. It works fine for me.
 

kd276

Senior Member
Jun 14, 2021
317
63
If you have an otg flash drive, place the arrow os rom on it, and in twrp choose the button wipe, and then format data, then install the rom from the flash drive, and at the end wipe cache and dalvik. BTW I don't have the sms notification delay that you are talking about. It works fine for me.

For otg flash drive you mean a usb-c pen drive? Unfortunately i do not have it but i will buy one since seems pretty usefull, but can a normal microSD card work too? I can buy both for later use.

Not everyone suffer from this bug, is random, have you maybe disabled battery optimization? Anyway i'm using vanilla version so i don't have playstore, but i doubt it matter, this issue happens only when the phone is in standby mode.
 
Last edited:

0b4

Senior Member
May 8, 2012
117
41
For otg flash drive you mean a usb-c pen drive? Unfortunately i do not have it but i will buy one since seems pretty usefull, but can a normal microSD card work too? I can buy both for later use.

Not everyone suffer from this bug, is random, have you maybe disabled battery optimization? Anyway i'm using vanilla version so i don't have playstore, but i doubt it matter, this issue happens only when the phone is in standby mode.
Yes, usb-c pendrive or a regular pendrive with an usb-c otg adapter. Both works.
I disabled battery optimization for some instant messaging app, but not for messages, and still, my sms messages are arriving in stand by mode too.
 

kd276

Senior Member
Jun 14, 2021
317
63
Yes, usb-c pendrive or a regular pendrive with an usb-c otg adapter. Both works.
I disabled battery optimization for some instant messaging app, but not for messages, and still, my sms messages are arriving in stand by mode too.

The problem is, in vanilla you can't optimize some system apps, in case of massages this option is greyed out. I'm thinking of install the gapps apk version.
 

Top Liked Posts

  • 2
    Hi guys one question I have I'm currently on the Gapps version of arrow and I would like to flash the non Gapps version. Can I dirty flash it with no issues or do I need to do a clean flash
    You should clean flash when switching from Gapps ver. to vanilla ver.
  • 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