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

Development [ROM] [11.0.0] [alioth/aliothin] ArrowOS 11.0 [OFFICIAL] [MONTHLY]

Search This thread

mocmocmoc

Member
Jan 24, 2011
40
16
Xiaomi Poco F3
I did a clean flash and then got updates. And charged my phone multiple times to 100% and used it till 0. No custom kernel.
That is weird. Maybe it's some kinda cache problem. Some MIUI user have this issue where phone will drain battery even when screen is off and eats up 25% overnight. Well at least you fixed your problem, kinda..

I can confirm this. Battery life is definitively worse than on MIUI stock. I could do at least 2 days without needing a charge, with Arrow I need to charge each day. And I'm not a heavy user at all, most of the time it's on standby.
Usually if there is such drastic battery consumption difference (6+ hours) like the other guy, there is something else that is wrong and not the ROM. Do you have a battery log of some kind?
 

Romu_GSI

Member
Aug 16, 2009
8
6
In previous builds I had a good active drain but a bad idle drain, like 1% or more, yesterday I clean flash this last update and charge battery to 100% and for now goes fine the idle drain (0.5%/0.6%) so I hope the new kernel helps with that, I'm sure it improves it a lot
 

wasthewad

Member
Nov 22, 2016
29
4
OnePlus 5T
Xiaomi Poco F3
That is weird. Maybe it's some kinda cache problem. Some MIUI user have this issue where phone will drain battery even when screen is off and eats up 25% overnight. Well at least you fixed your problem, kinda..


Usually if there is such drastic battery consumption difference (6+ hours) like the other guy, there is something else that is wrong and not the ROM. Do you have a battery log of some kind?
I didn't take screen shots but I verified battery drain overnight and it was around 5%. Didn't notice anything unusual with normal usage.
 

NTClarity

New member
Jul 20, 2021
4
3
Xiaomi Poco F3
What might cause the bad battery performance with arrow os in my case?
wasthewad , I might not be the person you're expecting but instead I just want to mention that my situation is similar to yours . I get around 5hrs & 30mins of SOT (6hrs max) , which I believe , it's kinda bad for my usage(mostly browsing , zero gaming).Battery drain is around 5% at night ( idle for 10hrs) . I came from stock miui and I can say that I haven't seen any difference regarding battery performance between those two roms. I have also seen many people getting a great amount of SOT(around 8-10hrs) in arrow , but it seems impossible for me and for others to reach these numbers. All of us who experience these issues would be grateful for any type of assistance , which will eventually lead to fixing most of the problems. Thanks in advance.

P.S. : Sorry if my grammar isn't correct , English is not my native language.
 

dzo

Senior Recognized Developer
Apr 3, 2008
2,487
5,085
Auckland
I noticed that the new kernel doesn't have my doze brightness patch so the aod will use lots of power.
Here's a boot image with that patch applied, it's also patched by magisk for root.

extract boot.img.signed from the zip and flash from fastboot with:

fastboot flash boot boot.img.signed
 

Attachments

  • boot.zip
    28.6 MB · Views: 24
Last edited:

mocmocmoc

Member
Jan 24, 2011
40
16
Xiaomi Poco F3
I have always had problems with the proximity sensor. Especially in calls. Do you know if it has a solution?
No real fix, it's a "you're holding it wrong™" scenario. Proximity sensor is facing upwards on top of phone together with ir. Try to point the top of the phone towards your head when answering calls and don't block the top when on video calls. That is all you can do.
vs2mOw7.jpg
 

palaych

Recognized Developer
Apr 11, 2017
568
2,761
Russia
I noticed that the new kernel doesn't have my doze brightness patch so the aod will use lots of power.
Here's a boot image with that patch applied, it's also patched by magisk for root.

extract boot.img.signed from the zip and flash from fastboot with:

fastboot flash boot boot.img.signed
Ye, forgot add because testing new solution.
 

angelogtc

Member
Apr 3, 2018
5
2
No hay una solución real, es un escenario de "lo estás sosteniendo mal ™". El sensor de proximidad está orientado hacia arriba en la parte superior del teléfono junto con ir. Intente apuntar la parte superior del teléfono hacia su cabeza cuando conteste llamadas y no bloquee la parte superior cuando esté en videollamadas. Eso es todo lo que puedes hacer.
vs2mOw7.jpg
: pag
Esto es algo muy básico que ya tenía en mente.
 

angelogtc

Member
Apr 3, 2018
5
2
No tomé capturas de pantalla, pero verifiqué el agotamiento de la batería durante la noche y fue alrededor del 5%. No noté nada inusual con el uso normal.
También creo que la batería dura menos de lo que debería.
Con el teléfono anterior, el Poco f1 podía durar hasta 2,5 días al inicio de su uso, con el f3 solo 1,5 días.
 

duydong

Member
Sep 5, 2014
29
6
I try 2 times with 2 kernel from 10.08 patch and 18.08 patch. The results are too different
The kernel from 10.08 is better. I know benchmark means nothing but i feel the 10.08 patch is smoother
 

Attachments

  • Screenshot_20210819-195107.png
    Screenshot_20210819-195107.png
    99 KB · Views: 98
  • Like
Reactions: Asoroka

relies

Member
Mar 5, 2014
26
6
33
São Paulo
Xiaomi Poco X3 Pro
My proximity sensor seems completely off on last update, was working "fine" on the previous one. Tested it in phone call and also on sensor test from play store. Any work around ?

Aside from that, just awesome ROM, my favorite by far.
 

Belerefontis

Member
Mar 6, 2009
24
3
Athens
Xiaomi Poco F3
Have the same problem, starts dialling in my pocket via emergency call in lock screen


Try Advanced Charging Controller App (on Fdroid), a GUI version of ACC. Very powerful and customizable. Set min/max charge %, and set max temperature so charging will be throttled to maintain said temperature. Expert user can also set manual voltage/current. A real battery maintainer, an essential app.

33 watt rapid charging is present in ArrowOs. 0%-100% in 55 minutes
You should also mention that in order to utilize the Advanced Charging Controller App, you need to be root.
 

arifqur

Senior Member
Nov 12, 2005
3,698
1,111
Tried to install on Locked Mi 11X (Indian) for the first time.
After stuck for 3 hours on unable to detect device in fastboot mode, I got to know that I have to wait 168 hours to unlock my device. Waiting is so boring man.
In order to pass time and not get bored i would recommend reading up on the howto guides on xda and other places before attempting to flash anything
 

AmmoChin

Member
May 23, 2020
11
1
Screenshot_20210820-023626.png

I've flashed @dzo 's boot.img. then turn on aod and left it for some hours. And this is what happened. With burning temp of 48 °C.

However I did left it while turning on the portable wifi hotspot on. But no one was using the wifi. So I don't think that was the cause.
 

-GREY

Senior Member

Attachments

  • Screenshot_20210819-194440.png
    Screenshot_20210819-194440.png
    193.2 KB · Views: 85

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Update 2021-11-12

    Device changelog:
    • - rro_overlays: Drop TetheringOverlay
    • - Switch NXP NFC HAL (Now should read mifare card's and another tag's)
    • - Reserved vendor partition size
    • - Misc fixes and upstream changes.

    Kernel changelog:
    • - Merge branch android-4.19-stable android kernel common
    • - Merge CAF tag LA.UM.9.12.r1-13300-SMxx50.QSSI12.0
    • - Misc fixes and upstream changes.

    ROM changelog: https://arrowos.net/changelog.php

    Installation instruction: https://forum.xda-developers.com/t/...os-11-0-official-weekly.4279481/post-85045261

    Download: https://arrowos.net/download/alioth

    Note:
    - Recommend use with fw part MIUI V12.5.4.0 and newer (global/India/etc).


    P.S. My personal Telegram support chat: https://t.me/mipa_lab
    1
    is it possible to flash this rom with TRWP? ... does this rom have fixed the issue with calls, in speaker other people cannot hear me or hear me very low ... any feedback is appreciated...
    Check if u have Volte enabled. Can cause problems.
    1
    Have you found a solution? I have the same issue on my F3 with the current LineageOS nightly.
    Unfortunately not. This bug is still present...
    1
    Have you found a solution? I have the same issue on my F3 with the current LineageOS nightly.
    Not really a solution, but I found a workaround:
    If I change the Preferred network type to LTE/TDSCDMA/... instead of NR/LTE/TDSCDMA/... (this effectively disables 5G) the Choose network page works.
    1
    Hi, Can anyone confirm whether the MEMC feature works in this ROM?
    it is a miui only feature.not on aosp roms
  • 84
    logo.png

    ArrowOS

    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 | Chat
    Github: https://github.com/ArrowOS
    Code Review: review.arrowos.net
    E-mail: arrowos.contact
    PayPal: Donate to me
    Blog: blog.arrowos.net

    Installation instructions: Click here

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

    WHAT WORKS?
    • Almost everything

    WHAT DOESN'T WORK?
    • You tell me
    Be sure to include a log : check how to

    DOWNLOADS
    Click here to Download
    Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.
    Read our blog article/post about:
    * GAPPS and VANILLA variants
    * Checking build integrity

    XDA:DevDB Information
    ArrowOS 11.0, ROM for POCO F3 / Redmi K40 / Mi 11x

    Contributors
    palaych
    Source Code: https://github.com/ArrowOS
    Kernel Code: https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.x
    ROM Firmware Required: MIUI R
    Based On: AOSP
    55
    INSTALLATION PROCEDURE:

    First installation (Clean flash):


    You need adb/fastboot tools.
    Download boot, vendor_boot and rom zip:
    1. https://drive.google.com/file/d/1o-4T4hfEtxECIss-DVSSYAM1Kvy2iDN9/view?usp=sharing
    2. https://drive.google.com/file/d/1PgtI8bOV1yjmTZJ7euP6xDFzMszY6AXb/view?usp=sharing
    3. https://arrowos.net/download/alioth

    Reboot in fastboot. Flash boot and vendor_boot:

    fastboot flash boot_ab boot_alioth.img fastboot flash vendor_boot_ab vendor_boot_alioth.img

    Reboot in ArrowOS Recovery:

    fastboot reboot recovery

    Make format data (Factory reset -> Format data).

    Flash ROM (Apply update -> Apply from ADB):


    adb sideload name.zip

    Follow what show on device, should be ... Step 1/2 -> 2/2, then flashing ended, can reboot device in system. (In cmdline: If the process succeeds the output will stop at 47% and report `adb: failed to read command: Success`. In some cases it will report `adb: failed to read command: No error` which is also fine!")

    If you want install separate gapps on vanilla buildtype, after flash ROM:

    Advanced -> Reboot to recovery

    Flash gapps (Apply update -> Apply from ADB):


    adb sideload name.zip

    __________________________________________________

    Install Update (dirty flash):

    Go in Settings -> System -> Updater


    Downlad new build -> Install

    Device will automatically download, reboot into recovery and install a new build.

    _______________________________________________________


    Also you can use TWRP. Can find info in theme:
    CLICK HERE

    ___________________________________________________


    My official telegram group: CLICK HERE
    21
    Update 2021-09-11

    Device changelog:
    • - Remove qti telephony injection (Fix SIM-Switcher)
    • - sepolicy: Address denials
    • - rootdir: Disable sched_walt_rotate_big_tasks
    • - Build with Clang 13.0.1
    • - media: Sync configs with CAF
    • - audio: Sync configs with CAF
    • - proprietary-files: Restore all vibrator firmware
    • - proprietary-files: Unpin Display blobs
    • - Convert CarrierConfig overlays into RRO
    • - rro_overlays: {Wifi,Tethering}Overlay: Move to vendor
    • - Import full QTI Codec2 HAL and switch to Codec2 by default
    • - libinit: Switch to walleye oreo build fingerprint
    • - Misc fixes and upstream changes.

    Kernel changelog:
    • - Merge branch android-4.19-stable android kernel common
    • - Merge CAF tag "LA.UM.9.12.r1-12800.01-SMxx50.QSSI12.0"
    • - cpu-boost: Rework
    • - Misc fixes and upstream changes.

    ROM changelog: https://arrowos.net/changelog.php

    Installation instruction: https://forum.xda-developers.com/t/...os-11-0-official-weekly.4279481/post-85045261

    Download: https://arrowos.net/download/alioth

    Note:
    - Don't use fw 12.5.3.0 Global/India or China 12.5 Enhanced! (Use previous, example 12.5.2.0 Global)

    P.S. My personal Telegram support chat: https://t.me/mipa_lab
    19
    I've been using this ROM for a few weeks and it's great but I noticed a couple of things and have tried to fix them.

    The phone doesn't always go into full suspend mode because there's an misconfigured interrupt from the always on processor.
    This should fix it:
    https://github.com/dzo/android_kernel_xiaomi_alioth/commit/7ee79cda883ec09c69ba03d18d1be34291077442


    The display doesn't go into low power mode when the always on display is enabled. There's also a clock with the wrong name in the device tree.
    Here's a quick fix for both those things:
    https://github.com/dzo/android_kernel_xiaomi_alioth/commit/8ac729b52ea721a419b5dd7f21eaa829675b925b

    Attached is a zip containing a new boot.img and also a new dtbo.img, the dtbo isn't really necessary but I updated it to match the panel settings in the stock MIUI tree. In a dark room, the always on display might be quite bright but it's actually using less power than it used to.

    You can check the power usage with the display off by connecting adb over wifi and looking for lines like this in the kernel messages:

    <12>[ 309.495162] healthd: battery l=78 v=4129 t=31.5 h=2 st=3 c=40039 fc=4568000 cc=14 chg=

    It's the c= number that's important, this is the power consumption. With the display off it's about 17K, with the display in low power mode it's about 40K and without my fixes it was over 100K with AOD on.

    flash from fastboot (not recovery) with:

    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img

    This boot.img is patched with magisk, has root and should pass safetynet.

    You can also try the kernel out using:

    fastboot boot boot.img

    Unplug usb quickly after it says it's booting or it will just show a charging icon. This won't modify your system, just reboot to go back to the original kernel.

    All this should be quite stable but because the system wasn't previously going into suspend it might show up other bugs in some drivers. Use at your own risk!
    19
    Update 2021-07-24
    Device changelog:
    • - parts: Add High Touch Polling Rate support
    • - Update blobs to V12.5.2.0.RKHMIXM
    • - Update config DisplayCutout to MIUI V12.5.2.0
    • - Update QDCM calibration configs to MIUI V12.5.2.0 and switch smart_MC1 by default mode
    • - Update WCNSS config to MIUI V12.5.2.0
    • - Remove SmartCharging
    • - Add missed audio props
    • - overlay: Return COLOR_MODE_SATURATED
    • - Remove unused jars and libs
    • - Kernel: Update display panel configuration to MIUI V12.5.2.0
    • - Kernel: fixes for freq table
    • - Misc fixes and upstream changes.

    ROM changelog: https://arrowos.net/changelog.php

    Installation instruction: https://forum.xda-developers.com/t/...os-11-0-official-weekly.4279481/post-85045261

    Download: https://arrowos.net/download/alioth