What is the difference between Odd Solutions builds and official LineageOS?
There are a few major difference
These builds have full GMS included as applicable (some legacy devices need a trimmed down version), so you don’t need to flash GApps!
LineageOS 16.0 builds have Pixel goodies as well as reverse-engineered SystemUIGoogle and SettingsGoogle implementations. LineageOS 17.1 builds just have the Pixel goodies.
These builds are signed with Odd Solutions dev-keys as opposed to LineageOS’s release-keys.
Many of the devices supported here don’t fully comply to charter, but are functional enough for daily use, and some can’t support specific functions on official LineageOS, but can unofficially, so please read the noted on your device’s specific page here.
No warranty is impled or provided on any of this, consider these builds as testing builds at all time.
Installing LineageOS zips in Recovery results in “Error 7”
The most common reasons for this error are:
You are trying to install a build for a different device. You need to make sure you download the zip for the correct device *and* variant
You are attempting to migrate from an unofficial build to official LineageOS. A full data wipe is needed if you are coming from something other than an official build of LineageOS.
Your vendor/modem/bootloader is too old (or maybe too new). Flash the correct stock image for your device, before wiping data and attempting to install LineageOS again. This information should be listed on the device’s wiki page.
Your recovery is outdated. Flash the newest available version of the recommended recovery image for your device.
If your error still persists after confirming these are not causing your issue, post on your devices relevant XDA thread and provide a recovery log.
My device is officially supported, but there’s no zips for it on the download page. Where are they?
Be patient. Devices are slowly being built throughout the week. Maintainers have busy lives, and sometimes an issue is holding it back. Please do not ask for ETAs.
My device is not officially supported, but I’d really like to give LineageOS a try. Can you support my device?
All devices are maintained by open source contributors - sorry, we don’t take device requests. If you would like to bring-up LineageOS for a device, and can meet some basic standards, we’ll happily look into making it official.
If you have a working device tree/kernel, and would like to submit it for official builds, please contact firstname.lastname@example.org with links to them. Please note - your device must have full hardware support (i.e., every peripheral works) and must be stable.
A build for my device disappeared? Where’d it go?
Occasionally a build is broken. If this happens, we remove it until the next build cycle. It is also possible the device is no longer in the official build roster and its old builds are being purged, or that the version it supported is no longer supported. You can check your device’s wiki page to confirm support status.
Where can I find the last build for xxx device before support was dropped/its LineageOS version was deprecated?
In short, you can’t. We don’t keep building, or keep builds around for any version older than 2 Android versions (e.g. when 18.1 builds started, 16.0 builds stopped and the builds were slowly removed, while 17.1 builds continued). We don’t keep old builds around for a multitude of reasons, the largest being that we won’t keep old, insecure, potentially broken builds around. Additionally, we don’t have the server space (or the space on mirrors) to do so.
Some devices pass their bootloader unlock status and verity status to android’s kernel during boot. We don’t purposefully remove those flags, as it isn’t our place to lie about security features. There’s also a blog post about this topic, which explains our reasons further.
Will you enable signature spoofing?
Once again, it isn’t our place to lie about security features. No.
Where does the updater app store the downloaded zip?
Mirrors? Why don’t you use torrents? Or IPFS? Or carrier pigeons?
This question isn’t new. To list a few reasons:
A majority of builds are downloaded on mobile devices via our updater. Mobile devices have limited bandwidth and monthly quotas.
Bandwidth is plentiful for open source projects. We have roughly 100gbit available to us.
We occasionally need to remove a build because of a device-breaking bug. This is much harder, or impossible, to accomplish with torrents.
We currently keep the last 4 builds per device. Older builds do not have the latest security patches.
The top 5 devices account for 50% of our users. 95% of our builds do not have enough users to justify torrents.
Pigeons are slow and stupid. They also tend to be hit by vehicles and make a delicious treat for predators. We could send your build via pigeon, but chances are very slim it would make it to you.