This is the first list of supported devices that will get the A16 community build
Devices can be added or removed from this list based on the status of the build.
In case builds fail for the devices we would attempt to rebuilt them. Devices for which we cannot make builds in A16 will continue to receive the next lower OS level build which works for it. Users will be updated about those devices.
All of these builds are to be flashed manually. Take a backup before proceeding. Installation guides will be updated for the A16 builds.
Official builds for devices will be announced separately. Official OS upgrade builds are delivered OTA and require more development effort.
The list of new devices coming with /e/OS A16 and being added to the supported device list is available here
Thank you for the list, @Manoj .
It should be mentioned that some older devices with Linux/Android kernel 4.4.x or 4.9.x may not receive Android 16 in the near future, see the corresponding article on the LineageOS blog:
Googleās increased reliance on newer eBPF features has made supporting devices with older Linux kernels increasingly difficult. Android 16 āQPR0ā ārequires Linux 5.4 and above, and at the time of writing, the necessary features have only been properly backported as far back as 4.14.
Unfortunately, LineageOS 22.2 still supports many devices running 4.4 and 4.9. As of now, no complete backports of the required features exist for these kernels. The silver lining is that, unlike the massive device loss we saw moving off LineageOS 18.1, these versions could be salvaged if someone were to take on the work of adapting the backports. If you do succeed, please reach out to devrel(at)lineageos.org, weād be happy to review it!
Weāre currently targeting only shipping kernels that have 1:1 eBPF backports to make them feature equivalent to Linux 5.4 from here on out to avoid compatibility issues.
From the list that was initially shared the following devices failed to build on A16 community. We will try to build them in the next iteration and release along with v3.7 in about a months time.
I see, Thanks @Manoj ā¦ there seems to be a misunderstanding I got that far of course and skimmed through the installation guide. From your āInstallation guides will be updated for the A16 builds.ā I was expecting a new section or something specififcally for that upgrade and I did not see thatā¦
So āflash manually.ā means ānormalā installation process, right?
(I wonder if a dirty upgrade via sideload or via ālocal updateā is possible at manageable risk)
The installation guides are always updated for the latest version of the build we share. We do not have installation guides for different OS version.
Flash manually means the build has to be downloaded from the link given in the installation guide and installed following the steps given in the guide.
The A16 build will not show up in the device installer as the updater app blocks OS upgrade builds.
The alternate is for official builds which get OTA OS upgraded. For example a device if on the official A14 build will be upgraded by downloading the build OTA (over the air). No need to manually download on a PC and then install following the guide.
I did a dirty upgrade through sideload from 12-13 without issues. I think Iām gonna try though local update for the A16 update. I plan to replace my iffy USB port first though, just in case I need to reinstall.
very interested on your plan to update to A16 from previous version, using ālocal updateā option.
if you do so, please share your experience, it will be very appreciated.
Yes, no issues or anything alike.
I did previous upgrades dirty as well via sideload and never had any issues (never did huge version jumps) ālocal updateā is very straightforward and quick and less fumbling than āsideloadā, I see no difference besides that.
I was just hesitant in the first place because there was so much wave about the A16 upgrade and announcement of manual flashing being required and referring to official procedure and so on.
Does not mean hereās no risk or that it will work that way for any device and version jump, but for me sideload worked before and everytime I tried on my samsung devices and my pixel 4a without any flaws so far.
(My routine includes backups of important apps settings or content before and clearing cache of all apps after every update or upgrade)
just to confirm everything was o.k. with ālocal updateā from USB-flash tu upgrade from e3.6-A15 to e3.6-A16, on my Sony Xperia 10 IV.
thanx for advices.
I got that far of course and skimmed through the installation guide. From your āInstallation guides will be updated for the A16 builds.ā I was expecting a new section or something specififcally for that upgrade and I did not see thatā¦