- dev/stable: the dev group are the test group until something gets a stable release. The recommendation holds true, but having used dev builds for 3 years, there’s rarely a bullet to catch. So: no hellfire. As /e/ delivery model for the App updates centers on the version-tagged Android branch, disruption in “dev” mostly comes from App updates or when firmware gets updated - not Android core components.
- Lineage has weekly builds. /e/ has (a bit less than) monthly builds - so it will lag. To manage expectations: users rightly lament the browser + webview update cadence in /e/. Efforts went into being quicker, but didn’t come to fruition yet. A major disadvantage is the delivery method for core Apps being the version-tagged device images. I’d checkout all major ROMs what fits your preference best.
As the pixel4a “flame” will stop getting firmware updates by Qualcomm, you’ll get ASB patchlevels for the Android core components in most ROMs, just on a different schedule, but all will be without firmware (modem, sensors…) fixes soon. /e/ will very likely build as long as Lineage will if not longer. - mostly correct as in Lineage has the device repositories: but for partner devices /e/ is selling they might have other channels
- Android 13 T is all test builds not yet public. When people return from holidays I’d expect dev releases in September - there’s a weekly development-updates post by Manoj to keep everyone updated
- good question - forum-search is a good start and manufacturer have a forum sub-category. Advice can be dated though when 2 years old.
2 Likes