Development Havoc-OS 4.x [ Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] [ OFFICIAL ]

[IronGFL]

Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.​

Has a refined Material Design 2 UI crafted by @SKULSHADY.​

Many useful features that provide a smooth premium experience.​

Just flash and enjoy...​

https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6​

Founder & Lead Developer:​

SKULSHADY (Anushek Prasal)​

​

DevOPS & Scaling: (meee )​

Irongfly (Sukeerat Singh Goindi)​

​

​

​

If you like our work and would like to support this project then please consider donating.​

PayPal: https://www.paypal.me/ANUSHEK​

UPI: anushekprasal@okhdfcbank​

ROM: https://download.havoc-os.com​

About Us: https://havoc-os.com​

Recovery: https://twrp.me​

Magisk: https://github.com/topjohnwu/Magisk/releases​

Telegram Support Group: https://t.me/havocofficial​

Telegram Announcements Channel: https://t.me/Havoc_OS​

Code Review: https://review.havoc-os.com​

Device:​

Alioth/Alioth (IN)​

LineageOS (https://github.com/LineageOS)​

Crdroid (https://github.com/crdroidandroid)​

Pixel Experience (https://github.com/PixelExperience)​

And all the other Developers, Testers, Donators and Users.​

https://github.com/Havoc-OS​

https://github.com/Havoc-Devices​

​

Device Side :

GitHub - SukeeratSG/device_xiaomi_sm8250-common: A device tree for sm8250 trees

A device tree for sm8250 trees. Contribute to SukeeratSG/device_xiaomi_sm8250-common development by creating an account on GitHub.

github.com

GitHub - SukeeratSG/device_xiaomi_alioth: A device tree for alioth(in) F3/Mi11x/K40

A device tree for alioth(in) F3/Mi11x/K40. Contribute to SukeeratSG/device_xiaomi_alioth development by creating an account on GitHub.

github.com

Kernel :

GitHub - SukeeratSG/kernel_xiaomi_alioth: Kernel Tree for Alioth ( F3/Mi11x/K40 )

Kernel Tree for Alioth ( F3/Mi11x/K40 ). Contribute to SukeeratSG/kernel_xiaomi_alioth development by creating an account on GitHub.

github.com

Vendor Trees

GitHub - SukeeratSG/vendor_xiaomi_SM8250-common: Vendor Repo for SM8250 Devices

Vendor Repo for SM8250 Devices. Contribute to SukeeratSG/vendor_xiaomi_SM8250-common development by creating an account on GitHub.

github.com

GitHub - SukeeratSG/vendor_xiaomi_alioth: Vendor tree for alioth(in) F3/K40/Mi11x

Vendor tree for alioth(in) F3/K40/Mi11x. Contribute to SukeeratSG/vendor_xiaomi_alioth development by creating an account on GitHub.

github.com

 

[IronGFL]

4.9
Changelog : https://github.com/SukeeratSG/dump-public/blob/iron/Announcements/havoc-4.9.md
download: havoc-os.com/device#alioth

 

[J33VA]

This is one of the few custom roms that supported aliothIN out of the box with Official tag. It runs smoothly without any major hiccups with its Initial build. Kudos to the dev. hope to see more refinements made in the device side changes.

 

[CRNO]

wow wow wow look who is here !! this is the best rom on performance !thank you very much

 

[Y0191]

Thanks for the ROM, it's smooth and fast af, but unfortunately has the same issues as 90% aosp roms for alioth.
1. Auto-brightness works with a huge delay when you take the phone out of the pocket in a bright sunny place. Screen is at minimal brightness for about 3-4 seconds. Plus the maximum brightness doesn't seem to be as high as on MIUI-based ROMs, and even the auto-brightness seems to be set for lower values all over the scale.
2. NFC only works for GPay, for any other app (when approaching a transport or bank card) the NFC module starts turning on and off on its own, like in a loop.
3. Headphones do not work via 3,5mm-to-usb. ROM recognizes it and opens the in-built Moto equalizer, but no sound at all.

I also tried flashing the boot.img and vendor_boot.img from Arrow OS ROM (it has 2 and 3 issues working). This solved the headphones issue, but the NFC did not start working.

Waiting patiently for the devs to solve these problems, thank you in advance.

 

[IronGFL]

Thanks for the ROM, it's smooth and fast af, but unfortunately has the same issues as 90% aosp roms for alioth.
1. Auto-brightness works with a huge delay when you take the phone out of the pocket in a bright sunny place. Screen is at minimal brightness for about 3-4 seconds. Plus the maximum brightness doesn't seem to be as high as on MIUI-based ROMs, and even the auto-brightness seems to be set for lower values all over the scale.
2. NFC only works for GPay, for any other app (when approaching a transport or bank card) the NFC module starts turning on and off on its own, like in a loop.
3. Headphones do not work via 3,5mm-to-usb. ROM recognizes it and opens the in-built Moto equalizer, but no sound at all.

I also tried flashing the boot.img and vendor_boot.img from Arrow OS ROM (it has 2 and 3 issues working). This solved the headphones issue, but the NFC did not start working.

Waiting patiently for the devs to solve these problems, thank you in advance.

Hi arrow os has it's trees private until the fix is open source i cannot implement in any of my work

 

[IronGFL]

This is one of the few custom roms that supported aliothIN out of the box with Official tag. It runs smoothly without any major hiccups with its Initial build. Kudos to the dev. hope to see more refinements made in the device side changes.

Yeah thanks

 

[Y0191]

Hi arrow os has it's trees private until the fix is open source i cannot implement in any of my work

Oh I did not know that, but anyway thank you, Havoc still combines a big variety of settings and great stability, very rare among custom ROMs)

 

[bleibeidl]

The additional UI options and ambient features are indeed nice.
I'll stay with Arrow for now and keep this one on my watchlist.

 

[orko95]

Bluetooth connectivity sucks

 

[Oneironaut84]

helloo.. I press run and the console closes. any idea?

 

[Robert314]

The additional UI options and ambient features are indeed nice.
I'll stay with Arrow for now and keep this one on my watchlist.

Explain. I find it perfectly fine

helloo.. I press run and the console closes. any idea?

Sounds like a Windows driver issue. Open a terminal and type fastboot devices. The majority of the ROM flashing is done once it's flashed boot and vendor_boot and rebooted into fastbootd. This is usually where people have driver issues

 

[esszett]

I'm quite happy with the phone and Havoc so far.

Not sooo happy with the Kernel yet. Although, I like the standby drain, but it looks like the active drain is way higher than with Quantic Kernel. Furthermore the adaptive charging does not work at all.

The last time charging was more than 5 days ago. The battery is now at 14 %. SOT: more than 10 hours. Nice

 

[ggtony233]

This is a great rom, but why can't it enter doze mode, so that the standby power consumption is quite exaggerated, how to solve this problem?

 

[esszett]

This is a great rom, but why can't it enter doze mode, so that the standby power consumption is quite exaggerated, how to solve this problem?

Did you flash Quantic Kernel?
If yes: Flash back to Havoc Kernel.
If not: Try to find out which (system) apps prevent sleep mode / keep the device awake. For example, with BetterBatteryStats.

On my device deep doze works like a charme...

 

[IronGFL]

This is a great rom, but why can't it enter doze mode, so that the standby power consumption is quite exaggerated, how to solve this problem?

It does.
Please uninstall any custom kernels or magisk mods or any mods

 

[esszett]

When I get a call, the earpiece doesn't work (it's completely muted). I can't hear the person I'm talking to. Only when I turn the loudspeaker on and off again does it work.

When I initiate the call, everything's fine...

Can someone confirm this behaviour?

 

[esszett]

I faced another 2 issues:

1. After I charged the phone for the 2nd time without rebooting, the kernel seems to have a problem because it keeps the device awake. 11 h after full load the kernel kept the device awake for more than 7 h. After these 11 h, the battery level dropped to 79%, with only 1 h SOT. A single app was allowed to stay active in the background (foobar2000). Exactly 4 things appear in the overview of the "app suckers" that kept the phone awake: Kernel (7h), foobar2000 (1h), Android System (6min), Phone services (1 second). I don't understand what's going on here.

2. The other problem is the proximity sensor. If I don't lock the phone manually when I'm talking to someone, my ear is constantly "operating" the phone. However, I don't think this was a Havoc-only problem, but affected all OS, right?

 

[Gr1mw00d]

When I get a call, the earpiece doesn't work (it's completely muted). I can't hear the person I'm talking to. Only when I turn the loudspeaker on and off again does it work.

When I initiate the call, everything's fine...

Can someone confirm this behaviour?

it happens to me too on crDroid with AOSP caller.. maybe its an issue with that caller

 

[Robert314]

it happens to me too on crDroid with AOSP caller.. maybe its an issue with that caller

Yeah we're having problems with that on AICP. It's either the dialer or the device tree not working properly with AOSP dialer. Google dialer or another dialer should work though