Related
http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )
These are very good news
I already see my Hero running CM 7
:happy face:
Excellent News Lets see who get's their GingerBread ROM out first
Sweet, if the hero really will be supported!
Cooooooooooooooool man very nice go go go go gooooooooooooooogle
Tchuup-tchuup! Hotness train is leaving the stations
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...
Good news
Sent from my HTC Hero
C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress
I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.
Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?
That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project
Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero
I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...
Especially the repo syncing... that just takes ages ;
krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!
Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents
I already saw a lot of kernel developers here, each of them posting their own version.
I don't think that "download sources / fix them / apply patches" by every one of them is ok.
If all could focus on a single source-tree and fix / apply patches to that we would get to a stable/improved version a lot faster.
I can provide a linux machine for the developers interested by this project.
Hardware: 2 x Xeon X7550, 16GB RAM (can be extended to about 60GB), 300GB of storage (can be extended) - RAID6, FC dedicated storage.
Example:
$ time make ARCH=arm clean
[...]
real 0m2.479s
user 0m0.953s
sys 0m1.151s
$ time make -j32 ARCH=arm CROSS_COMPILE=arm-eabi-
[...]
real 1m4.720s
user 19m11.694s
sys 3m23.190s
Click to expand...
Click to collapse
Software:
Slackware 64bit 13.37, gcc 4.5.2, gcc-arm 4.6.1
OS can be changed if you have good enough arguments.
SSH access, no root.
If any developer is interested by an account, pm me with the desired username.
Have fun!
Ok, if no one is interested, I have to start this alone...
BETA
First release - ALiCE Kernel - with patches/tweaks from eternity/franco/bricked kernels and some of my own. Everything seems to work on my HOX.
- Sweep2wake included
- modules built in kernel, no need to flash anything else but boot.img
Attached:
zImage - for including into your own boot.img
boot.img - InsertCoin 5.3.0 boot.img with this kernel.
DELETED ATTACHMENTS - Kernel was virtually unusable.
You can use zImage injector ( http://forum.xda-developers.com/showthread.php?t=1647398 ) to update your own boot.img
I like the idea of this collaboration of kernels.
And I like how the modules are integrated into the kernel.
I'll be testing this out more tomorrow with a battery test for a work day
Keep up the good work
EDIT:
3G Does not work.
As in it shows 3G/H on the top, but no network connectivity.
WiFi does however work.
Great
I'm not a kernel dev, but this seems like a good idea.
Kernel devs working together to create a solid/stable base kernel.
If they want to add specifics they can always release one aside of this.
Also good to integrate modules into boot.img
Keep up the good work.
+1
Good idea, and go on
Good work.
Well I build kernel in 1 minute on i7 920 @4.2 ghz, no need for you machine ;-)
But common git would be nice.. I have zero time to maintain a kernel for HOX
Sent from my HTC One X
It will be nice if we can have a common github repository for the OneX sense kernel with all the patch applies by the devs.
AliceXES, do you have a git link of your repo ?
Because I currently compiling the franco's repo with some config tweek for my own need. And I would like to compiling yours just for testing.
Anyways, thanks for starting your project
Please send me your twitter account it's for helping you
The biggest problems ain't hosting or building times, just version-control. A common Git would be nice, although it seems most changes get picked by eachothers at github.
What about a GitHub organisation? You can have free ones where everyone is admin if you leave the source open. But then that requires a certain level of trust I suppose, heh.
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
AliceXES said:
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
Click to expand...
Click to collapse
Sad happenings. Hopefully it'll be fixed soon so you'll be back on track!
1: 3G problem indeed lies in the modules (linked to one of the binary baseband module)
2: getting collaborators won't be easy; many (apart from a select few) of today's "chefs" (dare not call them devs) prefer to act alone, get the credits, instead of working together, where the progress would've been much faster. This has been discussed too many a time on xda.
It is so much easier to rip someone's work & claim it as your own... Which is why many a dev resorted to "protecting" their roms (for example, from dumping).
Another reason why not many would like to join you, is that then it would come apparent that they don't have any real skills, since they won't be contributing any patches. ;]
Why compare ROMs with Kernels though? Maybe I'm unique at this, I don't know but, I never really cared about moving files around at ROM level or building AOSP ROMs. I prefer the kernel-space just a bit more
If people are afraid that their commits get stolen (which unintently happened just a few days ago, it seems) they should sign-off it properly.
Ányway I'm always interested in collaborating. Atm I'm just foring Franco's kernel and fixing a few compiling warnings.. I think what we really need is one main-maintainer which holds the master-branch, then the rest of our bunch just can push commits to him for reviewing. Who this lad is going to be, is also a tricky one.
I don't think I will have any success with this project
I started my own kernel thread (here: http://forum.xda-developers.com/showthread.php?t=1662781 ), sorry.
Anyway, the invitation is still open.
Hello guys,
Then again, this was probably answered before, but my question is asked from a different focus, so bear with me.
I'm interested in getting involved in AOKP ROM development mostly because of three things:
1) I want to avoid huge downloads on such a slow connection, every time a change I want is made. (Details on that latter).
2) I want to make custom stuff at the source level.
3) I want to contribute for starts in fixing issues, then if time and connection speed allows, bigger stuff.
I'm not sure on how the AOKP team handles this, and I wanted one of you guys to provide some guidance in this.
I'm fairly proficient with Java, Android and Github myself.
Also wanted to mention that since I do have a painfully slow connection I'm performing the initial setup stage at some friend's worksplace, so it would be nice if it were a place where I can find instructions for everything I'd need while offline / on low conn (such as android repo setup, external dependencies, etc).
That's pretty much it, how to get involved with AOKP development, from the technical and philosophical sides.
Any pointers?
If you are interested in building LineageOS for Bonito or Sargo you can use my script on Github to compile for either device. The script I link in this post will build my daily driver ROM. To consider running this script you will need the following:
- A PC running Ubuntu 18.04 or a distro based off Ubuntu 18.04 (I use ZorinOS)
- This PC needs at least 8gb RAM, a quad core processor and 300GB of available space on a drive (preferably SSD)
- Patience
* These are the instructions for running the script:
Open a terminal and run the following commands
git clone https://github.com/stevn4127/scripts
(This clones my scripts to a directory called scripts)
cd scripts
(This navigates you to the scripts directory)
bash lineage.sh
(This runs the script)
You will need to enter your root password to update the OS and install build tools. You may also need to run the following command with your Github credentials following the text:
git config --global user.email
git config --global user.name
Here is a direct link to my scripts repository on Github:
https://github.com/stevn4127/scripts
Join my Telegram chat for help: NugTowers HQ
Test builds and a ton of OT. We are mainly Pixel/Pixel 3a users but everyone is welcome! Just don't be a POS Please... No nudity. DONT be a pervert. (Mod Edit: Certain descriptions removed)
https://t.me/nugtowers
Good Luck!
Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)
PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project; primarily due to the VoLTE and VoWifi support it shares with Bliss 12.x. Yes; I know that T-Mobile is kicking phones that don't support VoLTE and VoWifi off their network; however, that won't apply to any phone that runs AOSP - as VoLTE is par for the course for any phone that runs a recent AOSP firmware (Pie or later in practically all cases; in the case of Lineage, as far back as Oreo). I changed tower providers because T-Mobile doesn't care what firmware you run on your phone. (Since then, it turns out that my infusion center (and my current cardiologist - which is in the same building) are in a hole in the UnCarrier's tower network - which makes hotspot support - and therefore VoLTE and VoWifi support - all the MORE critical.)
Click to expand...
Click to collapse
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!
blksith0 said:
Google may be trying to kill custom development, but we have developers like you to thank for continuing to help advance this field. Keep at it!
Click to expand...
Click to collapse
I am not a developer. This is just my hobby. Lol. Thank you though. I'll be doing this stuff for as long as it's still possible. Long live the custom community!
PGHammer said:
Since I cloned your scripts, I have added Lineage to my "skinny build box" project;
Click to expand...
Click to collapse
Is this skinny build box project available?
tvoneicken said:
Is this skinny build box project available?
Click to expand...
Click to collapse
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.
A followup
PGHammer said:
The skinny build-box project is designed to be as low a specification that can build a standard-spec AOSP-based ROM.
My target is a two-core PC with 8 GB of ROM and 250 GB of storage space used - as either a virtual machine OR a WSL2-bsed spec.
The very reasons FOR the skinniness is so the PC used for it can be doing other things while build operations are going on - which is also why I am concentrating heavily on WSL2-based specs - because it has such operating in mind.
As opposed to most build-boxes - which have lots of both storage and cores - I'm going the other way - with as few cores and storage as can be gotten away with - to keep costs for builders down (hence "skinny") - not every builder is rich.
Once I get things ironed out, I will, naturally, publish exactly HOW "skinny" the final spec is - and I'll do so publicly ALA Nathan Chancellor.
Click to expand...
Click to collapse
I'm still shooting for the two-core target; however, as a backup, I'm doing a slightly-beefier four-core version based on the stebomurkn scripts - for the honest reason that I find them personally extremely useful.
CPU - Intel Core i5 (Socket 1151 or later)
Motherboard - any H or Z chipset that can take the same
RAM - 16 GB
HDD - 4 TB or larger
SSD - optional
GPU - optional
I'm doing a rebuild of my current system based on this spec. While my current system is G3258-based, I actually have a bigger budget than I did when I built "Baby Beastie" - my current '58 PC. The GPU will be the same GTX 1050Ti that drives "Baby Beastie" currently, as I have no need to upgrade it based on my gaming drivers. The HDD will be larger, because pricing for such has dropped dramatically. The PSU - like the GPU - is carryover (Corsair CX550M) - why replace what isn't broke? Same with the case - a full-size ATX. An SSD is an option - as my gaming needs don't require one. (My motherboard choices support both traditional SSDs and the M.2 sorts.) I'm still trying to stay under $1000USD - and I'll be purchasing everything via Amazon.com - which I did with "Baby Beastie".
ADDENDUM - Can you use both stebomurkn's scripts AND the scripts referenced in Nathan Chancellor's AOSP build guide? Absolutely - you simply need two script directories - ~/scripts and ~/scripts2; they can be in either order. (The reason why you need two directories is that you can't simply add them to the existing ~/scripts directory because it's not empty - hence you need a new place to put them - ~/scripts2.)
ADDENDUM - the core of the "skinny box" has been acquired - and it's the platter drive.
First off - why a platter drive? Platter drives are not pricey, and have gobs of capacity; further, thanks to onboard cache, they need not be snails. In my case, I went with the midrange Seagate 4 TB Barracuda Compute - which has been on sale at Amazon (AKA "Smiley's") for a mere $80USD (Prime). The Compute series is in three ranges - 2.5-inch for portables - 3.5-inch for desktops - and Compute Pro for workstations. The Compute I chose - for that $80USD - is from the 3.5-inch formfactor desktop range - which makes it physically no larger than the 1 TB previous-generation Barracuda it replaced, despite the four times larger storage capacity AND fifty percent faster (according to Windows 10) I/O performance - so much for making snap judgements! You don't need speed from a build box storage medium; what you DO need, though, is capaciousness - and 4 TB is plenty.
With the new core acquired, next came moving the data from the old drive to the new. Normally, I would use old-friend Acronis True Image; however, it has grown unwieldy in its age - so I wound up replacing it with Macrium Reflect 7. It has all the features that the older version of Acronis did - operates natively in Windows - and costs nothing.
Once you have the old data moved to the new home, re-sync your repos - remember, you have a LOT more space than you used to! (If you had a 1 TB (or smaller) platter drive, you may find yourself KICKING yourself, thinking "I was that silly in terms of lack of storage space?" Not exactly fun. Don't overeat - but don't skimp, either.)
Due to issues starting a new thread with a new post, I am making this one here; could someone with the proper access move it where it should go once I am finished? The subject involves running GSI (Generic System Image) ROMs on the Pixel 3a.
Why would anyone do so? The reasons are - unfortunately - twofold; it is getting harder and harder to find - or build, in fact - ROMs based on Android 10 and later for THE utility-infielder phone for Android 10 - the Pixel 3a. The second I have uncovered in my own running of Android 10-based GSI Havoc OS 3.8 for the past week - it is, in fact, better than the purpose-built Havoc ROM for the same hardware based on the same code - which makes not a lick of sense, but there it is.
There are two differences - Pixel Launcher is missing; instead, it uses Havoc's Shady Launcher - also, it cannot use Google Camera. Still, that is, in fact, all.
Now comes the $0.64 USD (sixty-four cents in US dollars) question - how does it run, and especially compared to purpose-built? Here's the scary part - for the most part, it actually runs BETTER than purpose-built based on the same code. The display is better. The performance is also better for the most part. As I said earlier, it makes not a lick of sense for "generic" to be better than "name-brand" - even when it comes to ROMs - yet here it is.
I have run it for the last week, and am STILL running it; either tomorrow or Monday, I will replace it with Havoc OS v. 4.1 (also GSI) for additional thrashing.
My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.
stebomurkn420 said:
My BlissROM script is up to date if anyone is interested in building for this device still. I will be updating my Lineage script in the following days to make this thread relevant.
Click to expand...
Click to collapse
Hi, I've tried to build Bliss using your script, and it failed at Building Kernel Image (Image.lz4) :-(
Most likely I'm the problem - I have no clue how android and Linux works nor any clue what scripts do and how they work, but since everything seemed to be working fine for a couple of hours, I hope it wasn't me (=fixable) this time. I can provide you with the log, just let me know where can I find it... Thank You!
ADDENDUM/FOLLOWUP - Can this be used with Windows 11? Yes - and with no changes whatever.
I wanted to GTFO Google and (ONE) single ROM has been developed for this phone on XDA without Gapps and it's not even maintained any more. I tried out Lineage with Micro G and I was pretty happy. I asked if anyone here would be interested in GrapheneOS and got no reply. I built it for myself and was happier with the spoofing in Lineage so I went back. But that brings me to the OP question...I guess I just don't understand why anyone would build a custom ROM that allows Google to spy on you completely unchecked. I thought I must have been insane since literally nobody here seemed to agree. Then I found this write up......I immediately decided to post it. Not because I want to piss people off. Not because I'm unappreciative. But because WTF ARE WE DOING??Why are we even running custom ROMS? Xposed came out and Google screwed us with SafetyNet. Then you had Substratum that got checked from Google but it's being "allowed" right now even though they tried to patch it out. Then Magisk comes and Google buys him out. This has always been a "cat vs mouse" game until recently. Now it's just a "cat vs customizable cat" game. Did we lose? Or is it that people would rather trade their privacy for convenience? The direction we are headed as a community is allowing Google to slowly close off and become Apple pt2 and nobody seems to mind much. But this is XDA! How will it exist without people caring about this?Here is part of the write up that applies specifically to the OnePlus7T. Hopefully I'm not alone. Hopefully we can get this train back off the tracks where it belongs. Barreling through the unknown in defiance of these huge entities trying to control you. Link is at the bottom of the write up.crDroidLineageOS-based custom ROM designed to increase performance and reliability over stock Android for your device while also attempting to bring many of the best features existing today, according to their intro & how I think its grammar should be.
Personal remarks: A very good heavyweight ROM (and the best Limbo ROM at the moment), burdened with a soydev website (at least there's no BlockAdBlock unlike Arrow) & lack of Vanilla/GApps enforcement in a way similar to Bootleggers - no Vanilla/GApps branding
Advantages:
Per-app data restriction (Pie, A10, A11)
Signature spoofing (A10 & A11: no toggle)
Inbuilt App Lock
Disadvantages:
No signature spoofing (Pie-only; forgiven & redacted starting with A10, 12/4/2020 build)
If you look at the official site, there's a screenshot that shows this feature, on a toggle. Should have been available at Settings > crDroid Settings > Miscellaneous; but it's not there.
Tested the 12/4/2020 build & found out that microG support is enabled without toggle. This anti-feature is redacted.
Poco X3(N) only (confirmed on 23/3/2021 build) - USB debugging enables itself on boot (redacted per 22/4/2021 7.5 build)
28/4/2021 Update : With inbuilt vendor on 22/4/2021 7.5 X3N build, USB debugging no longer self-enables on boot (it's enabled at 1st boot, but can be disabled without enabling itself on subsequent boots). Welp, guess it's like the F1's Pie era all over again, where most builds (especially userdebug ones) enable USB debugging on boot until developers starts to include vendor partition in their builds.
Poco F1 (A11) : No force encryption
No Vanilla/GApps enforcement, in addition to lack of Vanilla/GApps labeling
List of GApps-infested builds :
OnePlus 7T & 7T "Pro"
Not having an active TWRP development for a device does not excuse the maintainers for releasing GApps-only releases, unless they also make a Vanilla variant. And, since there is an active TWRP development, there shouldn't be any more reason to tolerate a lack of Vanilla build (other than the maintainer being too lazy / unwilling to develop a Vanilla build, in which case per should be replaced).
Poco F3 (switched to Vanilla builds as of 9/7/2021 builds, but still listed for reference)
Redmi K20 / Mi 9T (davinci) (Vanilla build available on GDrive, FWIW.)
OnePlus 9 "Pro"
When its non-"Pro" (the vanilla OnePlus 9) variant gets a Vanilla build (despite a lack of functional TWRP for either) there is no excuse to be lazy & provide GApps-only builds
Custom ROM List
Definitely. Yaap microG by John Galt is very good also. Omni microG is also good
I read through your entire post and while most of the things you have said could be attributed to a subjective basis depending on person to person basis but the overall idea has a couple of inconveniences that I would like to add some insight of my own and would like to explain without sounding too brash
This is just my own personal impression that I have witnessed being part of the greater Android ecosystem in general starting from the early days to where we are now
In my opinion, the lack of interest by developers that originally gave their time and effort into working hard and fixing things has generally not kept up with the pace of Google's development efforts to curb these "hacks". The cat and mouse game what the post you quoted said is nearly at an end. I think Google is winning with everything in broader terms and despite the conveniences offered by microG and custom roms using that implementation, it doesn't come close to what Google offers.
The hassle of finding workarounds to make even the basic of functionality to work on Android requires time and effort which as I have already said earlier, it's something no one can commit to these days. The "enthusiast" aspect of custom rom development has really taken a dive over the past few years as manufacturers generally offer good enough functionality (at least for my use case as I am heavily reliant on my phone for work and general personal use) and Android has come a long way since the early days.
All of what I said boils down to the cost of convenience vs concern for issues that are really issues for a specialist segment of users within the entire community. People de-google their phones to focus on privacy and prevent data mining from these data hungry corporations and I for one for wish I could have something that would decrease my overreliance on Google's services but it is just not possible as the majority of people just use their phones and expect things to work just like that. So, the long lived idea of if it ain't broke, don't fix it plays very well into this. The trouble is generally not worth the inconveniences that come with it. Lack of interest of users therefore means lack of options and thus a lack of development.
Here's my 2 cents
I think for devs or hobby-coders who do this for free, time is more valuable than the luxury of "privacy" (which doesn't really exist if you're using any form of social media, like XDA).
Things changed. Android is more polished now than the Nexus days.