This is some bs. If AOSP development is made less publicly accessible it does NOT " simplify things for developers" but rather it hinders it for de-googled privacy respecting ROMs and their device ports. The need for continued and ramped up efforts developing alternative mobile OS's, like Ubuntu […] - ThreadSky

About ThreadSky

TotalSonic.mastodon.social.ap.brid.gy • 12 days ago

This is some bs. If AOSP development is made less publicly accessible it does NOT " simplify things for developers" but rather it hinders it for de-googled privacy respecting ROMs and their device ports. The need for continued and ramped up efforts developing alternative mobile OS's, like Ubuntu […]

Comments

val.packett.cool•11 days ago

@TotalSonic eh, how much do custom ROM devs even follow "real-time" WIP on the AOSP dev branch? seems like they've moooostly been reacting to tagged releases

mxk.hachyderm.io.ap.brid.gy•11 days ago

@valpackett @TotalSonic yes. And that's why this changes very little.
The parts that still happend in the open always were incomplete.
The development of a new lineageOS release really just kicked of, when Google released the new AOSP version and the same will be true going forward.
The only way […]

TotalSonic.mastodon.social.ap.brid.gy•11 days ago

@valpackett - but yes, most ROM devs don't start working on a new release until it the AOSP base is fully released by Google. Still, this could potentially delay future releases, as well as effect development of newer Halium versions too. Guess we'll see

TotalSonic.mastodon.social.ap.brid.gy•11 days ago

@valpackett - fwiw, for certain devices in certain ROM's, I have received new versions and security updates long before the OEM actually ever provided them for that device. I've noticed that as Google has made developing and supporting Android Custom ROM's more difficult over the past few years […]

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply