LineageOS has added official support for the Samsung Galaxy S22 series, giving a 2022 flagship that Samsung has finished with a route to Android 16 and, eventually, Android 17. There is a catch that most of the coverage has skipped, and it is the one that decides whether this applies to your phone: the supported devices are the Exynos 2200 models only. The Snapdragon 8 Gen 1 versions sold in the United States are not on the list.
Which Galaxy S22 models LineageOS 23 actually supports
Checking the LineageOS wiki directly rather than the secondhand summaries, three device pages are live, and every one of them lists a Samsung Exynos 2200 as the chipset:
- Galaxy S22 — codename r0s, Exynos 2200, 8GB RAM, 6.1-inch 2340×1080 Dynamic AMOLED
- Galaxy S22+ — codename g0s, Exynos 2200, 8GB RAM
- Galaxy S22 Ultra — codename b0s, Exynos 2200, 8GB or 12GB RAM
The Snapdragon variants carry different codenames — r0q, g0q and b0q — and none of them appears anywhere in the LineageOS device index. Practically, that means most US Galaxy S22 owners are excluded, because the US got the Snapdragon build. Buyers in India, Europe and most other markets got the Exynos 2200 and are covered. If you are unsure which one you own, check the model number in Settings before you get invested.
Only one model has a build up so far
Support being “added” and a download existing are not the same thing. At the time of writing, LineageOS’s own build listings show a single nightly published for the Galaxy S22 Ultra — version 23.2, dated 16 August 2026 — while the S22 and S22+ pages are live with empty build lists. Nightlies for the other two should follow on the normal schedule, but if you go looking for a file today for a base S22, you may not find one yet.
Worth being precise about what this gets you today: LineageOS 23 is based on Android 16, which is the same Android version the S22 already runs under One UI 8. Flashing it now buys you a cleaner, Google-app-optional build and continued security patching after Samsung’s window closes — not a version bump. The version bump is the Android 17 build, and that has not been announced by the project. The expectation that one arrives in the coming months is the assumption of the outlets covering this, not a commitment from LineageOS.
The part Samsung’s abandonment does not make painless
The reason this story exists is that Samsung closed the door on the S22 series. The lineup was left off the One UI 8.5 roadmap and is excluded from One UI 9, and the S22 generation never got the seven-year software commitment that later Galaxy flagships did. A four-year-old phone with an Exynos 2200 and 8GB of RAM is nowhere near unusable, so an alternative path to current Android is genuinely valuable — this is exactly the kind of end-of-support cutoff where the community fills a gap the manufacturer left, much like the custom-ROM scene that depends on manufacturers publishing kernel source.
But be clear-eyed about the cost, because it is not small. LineageOS’s own device pages carry a blunt warning on all three models: an official method of unlocking the bootloader is not available, and while unofficial methods may exist, the project does not recommend or support them. An unlocked bootloader is required to install LineageOS. Each page also lists known quirks covering eSIM, IMS and device integrity — in plain terms, expect trouble with eSIM, with carrier calling features such as VoLTE and Wi-Fi calling, and with the Play Integrity checks that banking, payment and some streaming apps use to decide whether to run at all.
So the honest summary is that this is a real lifeline for a phone Samsung has written off, and it is a lifeline with conditions. If you use your S22 for banking and tap-to-pay on a carrier eSIM, the trade is a poor one. If it is a secondary device, or you are willing to work around those three quirks to keep getting patches and eventually reach Android 17, LineageOS 23 is now the best option you have — and it is more than Samsung is offering.
Sources: LineageOS wiki device pages and the project’s own build listings, checked directly; 9to5Google
