[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] ayunatsume:
Upgraded from HavocOS 2.0 (jan2019) to HavocOS 2.9. Didnt do 3.0 as I think Android 10 is still too untested. Some of my findings may be old for you who update regularly though but good for those who are like me who jump only when significant changes are made and versions are close to final (e.g. last pie build w/o xiaomi modules to last pie build with xiaomi modules)

Here's my findings:

+Everything looks better and camera support is better.

+GPS is more sensible now

+Bluetooth appears to pair faster and consistently.

+YouTube no longer randomly flickers when using multi window.

+Mobile Data has a bit lower latency.

+OS boots faster and starts showing boot animation faster.

+Google assistant shows faster. Same gapps flashed.

+Battery drain seems to be longer but mobile data web browsing no longer drains it as fast as 2.0.

~ I liked the older mobile signal and battery level icons (bars look more readable). I like how more compact they are though. End of the day its just cosmetic so no biggie.

-Miracast now get device stuck in black screen after resuming from sleep after it goes to sleep from a full screen video (Netflix and YouTube). I now simply learn not to put phone to sleep.

- WiFi tethering seems to be less stable or just as problematic. 2.0 made it so that sometimes I cant connect especially when charging and eventually data wouldnt work even if client PC says it is connected to WiFi. Traceroute suggests phone wont forward packets from phone to ISP. Requires restart of phone to fix. 2.9 now always lets me connect, but there comes a time when phone periodically wont pass packets to ISP. Reconnecting to hotspot works for a while and requires a restart to fully fix until it happens again. I just make it a habit now to restart phone before I tether to keep things consistent.

Just my 2 cents. Thanks dev for giving me a stable daily driver phone :)

I was actually happy enough with 2.0 with its choppy portrait mode camera until Magisk stopped working after an update and thought I borked the kernel so I thought I might as well update ;)

Here's a toast for a good nice Android Pie run :D Excited for when Android 10 becomes just as stable :D

For the popcorn scene before this post:

Man, you can't expect a corporate-level personal support of everything in a custom rom in XDA. Your questions were fine until you just started complaining (which had a bad accusing tone) which is the only problem since it sounds like you want us or the dev to be your personal Xiaomi-certified technician. We're all just like you trying to make things work. Its understood here that you can piece things together yourself (hence why you're hacking your phone without official support from manufacturer) and devs are just making it possible by spending their unpaid hobby time fixing bugs and building code. Latest version is not always ready. Experiment if you must with different builds in the github repo. This phone is always fully recoverable with qualcomm's dload and emergency firehose protocols. If you want the latest major android version, then help the devs by trying to fix yourself so they can implement a fix for the next build. If you want the fastest release, trebelize your phone and use GSIs. Logcat if you can (is it still called that? My last phones were pretty much gingerbread to Lollipop).

Expect a slow upclimb Hill when major android versions are to be run in a phone that doesn't have official firmware with the same android version. Expect even more hackier hacks that you have to flash with Magisk to make things work. Android 10 will be ready for stable and daily driver status when it comes. Meanwhile, enjoy Android 9 Pie or help fix Android 10 in this rom or the others. The way things happen now is way easier than the older hacking days of getting ICS or jelly bean to run in a gingerbread phone full of security like Sony's TA partition or some bootloader unlock protection that requires shorting two motherboard pins to defeat. This is how most of XDA Android Development thread works.

Android phones don't work like Windows computers where generic drivers, driver models, backward-compatbility shims, class drivers, and an advanced HAL exists. Hopefully, Project Treble puts android closer to that level of universal runnability across different hardware combinations. Hopefully future hackable phones are like that, eh? ;)

On the note of making Android 10 work, have you considered trying to force flash your downloaded ROM somehow? Or flashing another Android 10 rom before HavocOS 3.0? Back then with such errors, I used to flash a future android build's kernel first before trying to CWM-flash a new build. Pretty much like prepping your phone for the next android version. Assuming you really got a build meant or usable for our model. But there might still be teething problems with initial builds with Android 10 so we'll have to wait if you want the safe easy route.

Would you look at that, now I have 4 cents!

Thanks again dev looking forward to the next build.