Database Info

Android Lollipop (AOSP builds)

This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3.
What I would like to be discussed in this thread is the stability of the different Android Lollipop roms. Since most of the devs have not made a seperate thread for their (at this stage alpha) builds of Lollipop. I would like to collect the experiences of the users from these alpha's.
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept. The unofficial thread for Slayer's rom: http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support. Now on preview 2: http://forum.xda-developers.com/showpost.php?p=56934897&postcount=6046
Zion: also just an initial build (I think). Also no statements regarding support. The build from ZION: http://forum.xda-developers.com/showpost.php?p=56900235&postcount=542
I would like the structure of the posts in this thread to be:
Device: hlte/hltespr/hltetmo/hltevzw/hlteatt/hltexx/hlteusc/hltevan
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.

I can't even get temasek's build to boot.

speedyjay said:
I can't even get temasek's build to boot.
Click to expand...
Click to collapse
Booted and with LTE.

temasek said:
Booted and with LTE.
Click to expand...
Click to collapse
Share and share alike my good friend?? Lol

I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port

Miniprepumen said:
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Click to expand...
Click to collapse
Port? It's built from source and not a port.
PREVIEW 2 is up.

temasek said:
Port? It's built from source and not a port.
PREVIEW 2 is up.
Click to expand...
Click to collapse
Sorry mistake
Downloading !!

Miniprepumen said:
Sorry mistake
Downloading !!
Click to expand...
Click to collapse
It's a preview so don't get so excited.

temasek said:
It's a preview so don't get so excited.
Click to expand...
Click to collapse
Works very well, LTE works normal, wifi too, I can do calls without any problem, and very very smooth and fast.
Problems for now: There are apps that not work, but very very good job. Thanks really
Edit: camera not works.

Wait where is zion's build? How's google now on all these builds? On Slayer's it's broken / causes reboots

My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance

PlutoDelic said:
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
Click to expand...
Click to collapse
Preview 2?

Tema prev 2 fixes the touch button wake for me. But WiFi + Google now still cases reboot. Google now hotword doesn't seem to work which it does on slayer. All camera apps fc. And the home button still doesn't wake the device. Aside from those it seems near perfect. Thanks a ton!
Sent from my SM-N9005 using XDA Premium HD app

temasek said:
Preview 2?
Click to expand...
Click to collapse
Actually no my friend, i just read it 10 minutes ago and am downloading as i write.
I did not want to spam around and used this thread exactly for expressing opinions, as i know both roms are early stage builds and none of the devs should be bombarded with requests anyway.
Will report back.

I just need spotify working them I'm happy as Larry lol

temasek said:
Preview 2?
Click to expand...
Click to collapse
One hell of a ROM at the moment, havent had a single crash and loaded loads of apps that used to crash in nearly all Lollipop builds. Too bad your ROM doesnt have the flashlight in the notification drawer, was very useful.

Right I must be blind. I can only find the ROM thread that is a cyanogenmod 12 PORT.
Can't even find any other Lollipop ROM!
can someone share the links please?
Hope their compatible with the international Note 3

Suggestion
hom.hom said:
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3......
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept.
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support.
Zion: also just an initial build (I think). Also no statements regarding support.
I would like the structure of the posts in this thread to be:
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
Click to expand...
Click to collapse
We can assume there will be a ton of reports here of what is working and what isn't (probably duplicates or even 5 times the same report as we saw in Unnofficial CM12 Port from Jamal's thread...). I would advise everyone to post phone info after every report. Because there is a confusion of what is working on which model.... You might wanna add this to OP so people can actually see since my post will be long forgotten after pages and pages of comments.
Plus you might add link to Jamal's thread and download links for Zion and Temasek's ROM... Not everyone has those since they are buried in an ocean of posts over at Jamall's thread. @AndroidInsanity here they are:
1. @jamal2367 thread
http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
2. @ZION959 cm 12 unofficial
https://s.basketbuild.com/devs/Zion959/L/HLTE/
3. @temasek Build
http://d-h.st/users/temasek/?fld_id=41330#files
SM-N9005 (would be an example, so people know what phone is about. I know some have details listed in signature but not everyone).

and as always noone cares about exynos note 3...

ereneren564 said:
and as always noone cares about exynos note 3...
Click to expand...
Click to collapse
And rightfully so, if you buy an exynos device you should know that developers do not support these devices. Because the documentation of exynos chips is practically non existent. I am sorry, but with regard to custom aosp roms and devices with exynos chip consider this an expensive lesson. For support for these devices complain to Samsung.

Interest check: LineageOS 13.0 nightlies for Mi 4c

Hi all,
Over the past few months I have been building CyanogenMod (now LineageOS) 13.0 for my personal use. It's based off Kumajaya's sources and was roughly parallel to emfox's builds. I'm doing this because I'm dissatisfied with the stability and reliability of existing ROMs. (I can't claim that mine is any better, however it does put me in a position to debug the issues.)
This is an interest check. I am considering publishing my nightlies for people to download. I know that everyone will give a blanket "yes" to the question "should I publish my nightlies for people to download?". So instead I would like to ask:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
(Long time reader, first time poster!)

This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man

philipnzw said:
This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man
Click to expand...
Click to collapse
I second this! More roms/more activity keeps this device alive longer too

1. Your development wil keep this device alive longer.
2.(maybe) attract other dev/team to build rom for this device.
3.it will make your rom better,by sharing and let many people using it, will helps you find problem faster and improve it.
so yes!

Always useful to have more I have an Aqua (mi4s) and the rom scene is very poor :/ a few Libra roms do support it but in recent months even the SD card support has gone making for quite a sad outlook for the device. If there were someone building nightlies, it would be ace as from time to time you might be able to dip into the aqua stuff too and we'd all appreciate that
Whatever you decide, it's a nice thing to even consider doing for the community. You have my thanks

honestly i think Marshmallow is waste of time, most of the people are interested only in newest Android and i don't see much interest since we have official nougat ROMs from Mokee, AICP and Resurrection remix
if you want to do something different there is Nougat AOSP ROM missing, blobs from Xiaomi are already available, Nexus 5X as well, so...

more roms, more options. i want my mi4c looks better than Nexus 5X

terence.tan said:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
Click to expand...
Click to collapse
It really depends on what you would have to offer. The available CM13 (or are we calling them LO13 now?) ROMs are TeamSuperluminal's and Emfox's builds which are really not actively maintained anymore, although they are pretty damn stable. Except of course the few bugs that seem to go unfixed -- the touchscreen bug, which appears to be really complicated to fix without newer Xiaomi's kernel sources, the 2% battery bug which is present in TeamSuperluminal's builds and isn't a gamebreaker, and the way the SoC uses its cores in most of the ROMs based on Kumajaya's kernel sources (always active big cores) which results in lower battery life.
If you solved some of these problems, expect users to flock to your ROM. If not, I wouldn't bother, since you'll just be flooded with requests for fixing stuff that isn't broken in the first place. In fact, expect the second even if you deliver on the first.
I don't maintain any ROMs so I'm not one to give advice, but it seems to me it's a lot of work, and that you're paid with criticism and demands for more of your time. Get in contact with a ROM author and ask them for advice on this

Thanks for the thoughts.
As far as I can figure, there are 3 things people want:
Features/being on the cutting edge
Performance
Stability/reliability
We want all 3 but unfortunately it is a trade-off. In particular it takes special effort to achieve stability when combined with the other 2.
The CM14.1 builds satisfy the people who want to live on the cutting edge. The Xceed ROM is built for speed for those who think that Snapdragon 808 should perform like the top-tier chipset that it is
But out of all the ROMs I've tried (haven't tried the CM14.1 builds yet but have tried most of the others) I've had the following stability problems:
Screen freezes, requiring reboot
Sleeps of death
Random reboots in the middle of the night (waking up at 3 a.m. to find my phone clicking at me on the "decrypt your device" screen)
Stuttering or hangups
OpenGL-based games crashing
And that's not including the well-publicised touchscreen and battery problems.
So my personal strategy is:
Marshmallow build. Sorry for those who want Nougat, but I don't consider it stable enough (yet). Plus, all the proprietary MIUI vendor blobs from Xiaomi are targeted at Android L, and getting them working on Android M is hard enough already...
For the kernel, track CAF closely. Probably take their Android N release on the assumption that it's stable
Use as few proprietary blobs as possible; build from CAF source where available. This is what most developers are doing already
Use the most recent proprietary MIUI vendor blobs from Xiaomi, on the assumption that they've been buillding this version of MIUI on Android L for such a long time that it's stable
Avoid importing proprietary blobs from other devices (Nexus 5X, Moto X Pure etc.) where possible for licensing reasons. I don't intend to try and make this an offical LineageOS build, but this might be important for whoever attempts in future...
All this is difficult and @ketut.kumajaya and friends put in some impressive hacks to get it to work in the first place. I can't promise that I can build on this! But if I ever get to a stage where it's fit for consumption, I'll publish something...

in my opinion this will be great for development on Libra devices, i think Nougat rom with clean source will be great for user like me sir. For now iam using RR Nougat and for me its stable for daily use, if we can make Libra official for Lineage it can open other rom change to get official build too. Best luck for you sir and cant wait for your contribution

AOSP ROMs after Oreo launches?

i'm extremely grateful for all of the ROMs in the development section currently, but i'm kinda bummed there aren't more AOSP ROMs. i know only the developers have the definite answer to this question, but i'm curious to see what everyone else thinks. do you guys think we'll see an increase in ROM development (specifically AOSP) once Oreo officially launches?

IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..

tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.

miffymiffy said:
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.
Click to expand...
Click to collapse
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.

tomascus said:
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.
Click to expand...
Click to collapse
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS

amit_sen said:
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
Click to expand...
Click to collapse
As I said before in the slim thread, I don't have a dual sim device so it's broken and I can't fix. If you are a dev then I assume you have some skills to troubleshoot the issue.

Actually I don't know why we need this boring looking roms
The stock sense rom is perfect with ultra smooth performance
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Actually I wanna try
Miui rom ❤

tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I just flashed slimrom and it's pretty stable for me. I'd love to help out. What can I do?

Hi all, a quick thought that fits this topic, I think.
I was wondering if there is any chance we see the U11 Life Android One ROM ported to the U11, when the U11 Life will be out?
I'm asking because I saw this was the case for some Xiaomi devices:
https://forum.xda-developers.com/re...-androidone-7-9-21-xiaomi-redmi-note-t3691907
Thanks in advance !

Poco F1 Custom Roms

Hello guys,
we already are noticing how xiaomi is starting to lift her hand off our beloved Poco F1 to make us change device. but as users of this device,
we know this is very hard for most of us mostly because of budget reasons, and this device still has a lot of potential with SD845.
to counter xiaomi attempts, i am inviting you to write down suggestions of custom roms that you have used with some details like
how often the rom is getting updates, is it stable, does the devs keep fixing major bugs with updates, performance, battery life, bloatwares,
and why not suggest TWRP versions and kernels you are using.
i hope this thread gets some attention and let's keep using our beloved Poco F1.
peace.

I don't care about Xiaomi's MIUI updates anymore because custom roms are better, If you are new to custom roms I suggest you start with Lineage 17 as it is stable and smooth and It gets updates almost every month or less, If you want customizations you can try Pixel Experience Plus.
I've been using Awaken os based on Android 11 for three days now and I can recommend it also even though it's not fully stable.

Lineage is a solid choice for sure , arrow aint bad either ( very curious about the 11 build ) but for now i stick with CRdroid.
There are some very small minor issues there but compared to the mess of miui it's a laugh..

Honestly, they're all pretty lousy.
No offence to any Poco Devs here, we all know they do it for free, but just look at all the posts in Lineage OS recently - more and more bugs keep popping up.
They *are* weeklies, though - but we have no stable custom ROM's it seems because everyone just copies LOS DT and Devs don't have time to run CTS or VTS on their builds to make sure things actually work.
I think the key is to find a ROM that is being hand developed by someone who actually *uses* the ROM as their daily. Because right now it just seems like these are all blind builds or have only basic testing, e.g. "cool it boots, ready for release, bugs = you tell me" and they can't tackle all bugs because they're too busy or whatever.
Again, no disrespect intended - it just seems like many devs build ROM's for personal fun. And really I don't blame them, fixing stuff is generally way more boring than addin X trendy feature, right? [emoji14]
With that said, if you don't mind a pure AOSP experience with minimal mods, I've started work on an Android 11 GSI which I will be using *personally* and I intend to slowly add features over time. I will provide a custom modified vendor if I have to, to fix any GSI weirdness (despite that not being the direction Phh likes to go, Poco does some weird stuff of vendor last I checked which makes GSI's imperfect - but it's hopefully all things that I can fix). Note though that Magisk on Android 11 GSI's is not currently possible, though you can toggle root on/off with sooti's latest Dev work. My ultimate goal though is to make a ROM where I no longer need root, I'm personally exhausted with the SafetyNet vs Magisk arms race.
Sent from my POCOPHONE F1 using Tapatalk

So far I started with Pixel Experience, than switched for a year and few months with Lineage 16. Wich was good.
Now, I'm using Evolution X and very happy with it. The last firmware update was last september, so I recommend it.

iam using havoc for quiet some time, its got call recording, its pretty stable, got some issues with bluetooth(tws) connection and some very minor bugs. Havoc is my recommended rom.
The only feature i miss from miui ports roms is the dual statusbar.

Surya owner 6months. Looking for Clean/Fast/bug free ROM

Hello everyone.
I own the Surya Version of the X3 NFC for over 6months now. I am not satisfied with stock MIUI 12.0.8 and I am searching for a better ROM. Before writing what kind of ROM I am looking for, I ll write down some things about the past.
I was using for 3 years the Xiaomi Mi A1 using Pixel Experience custom rom and found to be the best overall for my needs. I tried also some clean AOSP Android Ones which were faster but had serious bugs. So Pixel Experience on my past Xiaomi mobile device was very balanced overall and was happy with it.
I see there is a thread for PE and PE plus for our X3 and I am reading these days the thread carefully.
What I am looking from a rom:
Less possible bugs,
Compatibility with security apps for banking financial purposes, authorization etc.
Lightweight in resources.
The cleaner the better for me. I am experienced and I can install everything myself including Magisk modules and stuff. I will stick with stock kernel or change to another one only if there is proof to be bug free and not messing with the device performance-compatibility-battery life.
Best camera app is a must but I am sure I will find a better one (google cam) than the stock I have right now. (feel free to make suggestions)
Right now I just made the Mi account and I am waiting the 168hours for the unlocking. So no hurry to find the best answers. I have 1 week to decide.
Do I flash the PE, PE plus or another rom?
Thanks so much for any opinions

Having had my Poco X3 since launch, I have now tried Xiaomi.eu (stock based), ArrowOS and am currently on Resurrection Remix,(v8.6.9, A10 based), and I'd advise you to stick to what you know best (the Pixel variants, some of which are quite well regarded) but also to not get your hopes very high.
From reading the forums for as much as long, my opinion is although the hardware specs are great, no custom ROM is completely without issues -- or maybe I'm just spoiled from past experiences, where I had no troubles worth mentioning setting up and using them as daily drivers.
Cameras on this device, for instance, are by itself a whole field of research.
If simplicity is what you seek, than most folks here will point you towards ArrowOS or LineageOS.

Thanks for the answer my friend. I am also reading the ArrowOS thread since I started searching for alternatives.
What would you think about ArrowOS disadvantages from the time you used it? Stock kernel or something else?
@pnin

From my usage, I had trouble setting up some rather basic options but, as it was a while ago, I don't have too clear a recollection.
Afterwards, ArrowOS switched to A11 firmware first and then an OSS vendor, which resulted in a seemingly never ending stream of complaints about upgrades, lack of features and degraded performance -- myself, I never experienced this because I had already moved on.

The migration to OSS vendor happened 2-4 years earlier than necessary, thats what (issues) you get when you do not wait for xiaomi to fix the issues and you try to fix them yourself.
I am still on the last non-OSS build cause of that untill they fix all the issues

iakoboss7 said:
The migration to OSS vendor happened 2-4 years earlier than necessary, thats what (issues) you get when you do not wait for xiaomi to fix the issues and you try to fix them yourself.
I am still on the last non-OSS build cause of that untill they fix all the issues
Click to expand...
Click to collapse
I'm using OSS vendor and have no problems.
Which issues are you talking about?

The ones reported on the ArrowOS thread.
Some users report worse performance and some issues here and there.
Also they seem to discontinue smart charging cause of an issue with it.
Personally i am on the latest non-OSS build cause:
A) i do not wish to format the phone and start from scratch again.
B) above reported issues.

@iakoboss7
Thanks for your reply. Can you please share your thoughts on what is not working on the non-OSS rom? I would like to know every detail if it is possible.
also I was unable to find the non-OSS build. where are these variants? I see only vanilla and gapps.

iakoboss7 said:
The ones reported on the ArrowOS thread.
Click to expand...
Click to collapse
There are no issues reported on the last pages of the ArrowOS thread.
iakoboss7 said:
Also they seem to discontinue smart charging cause of an issue with it.
Click to expand...
Click to collapse
You may as well flash the 20210608 OSS build and stick with it.
iakoboss7 said:
I do not wish to format the phone and start from scratch again.
Click to expand...
Click to collapse
That's something you will have to do anyway sooner or later. There is no way from non-OSS to a current build.
iakoboss7 said:
above reported issues.
Click to expand...
Click to collapse
Again, there are no reported issues. Please name the issue you have in mind or stop making false accusations

FYI, just now in the ArrowOS thread, atefbeldi and CherryFarmer8 complained of some serious problems with recent updates (cf. https://forum.xda-developers.com/posts/85337817 and following).

pnin said:
FYI, just now in the ArrowOS thread, atefbeldi and CherryFarmer8 complained of some serious problems with recent updates (cf. https://forum.xda-developers.com/posts/85337817 and following).
Click to expand...
Click to collapse
They are complaining about a problem with Magisk. atefbeldi specifically writes that the problem only occurs after installing Magisk. Without Magisk there is no issue