
20

Development - [ROM] [11.0.0] [alioth/aliothin] ArrowOS 11.0 [OFFICIAL] [CLOSED]...
source link: https://forum.xda-developers.com/t/rom-11-0-0-alioth-aliothin-arrowos-11-0-official-closed.4279481/page-100#post-88056945
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Top Liked Posts

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
- You tell me
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
INSTALLATION PROCEDURE:
First installation (Clean flash):
You need adb/fastboot tools.
Download boot, vendor_boot and rom zip:
Reboot in fastboot. Flash arrowos recovery (boot.img and vendor_boot.img):
Reboot in ArrowOS Recovery:
Make format data (Factory reset -> Format data).
Flash ROM (Apply update -> Apply from ADB):
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):
__________________________________________________
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
First installation (Clean flash):
You need adb/fastboot tools.
Download boot, vendor_boot and rom zip:
Reboot in fastboot. Flash arrowos recovery (boot.img and vendor_boot.img):
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
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.
- - 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.
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
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!
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!
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.
Installation instruction: https://forum.xda-developers.com/t/...os-11-0-official-weekly.4279481/post-85045261
Download: https://arrowos.net/download/alioth
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK