OTA Server for LineageOS
Go to file
Steven Polley fb5b9864d9
continuous-integration/drone/push Build is passing Details
continuous-integration/drone Build is passing Details
Update README.md
2023-09-11 17:38:31 +00:00
public initial commit 2023-06-03 23:07:55 -06:00
.drone.yml fix typos 2023-06-03 23:13:51 -06:00
.gitignore go mod and .gitignore 2023-06-03 23:10:29 -06:00
Dockerfile fix typos 2023-06-03 23:13:51 -06:00
README.md Update README.md 2023-09-11 17:38:31 +00:00
go.mod go mod and .gitignore 2023-06-03 23:10:29 -06:00
main.go Add configurable baseURL (required for multi-device support) 2023-08-21 19:47:49 -06:00
ota-logo.jpg add logo 2023-06-09 17:04:15 -06:00
processFiles.go fix string formatting bug causing mangled id's 2023-07-10 18:08:34 -06:00


Build Status


A highly-scalable and lightweight OTA Server for LineageOS. The OTA server supports a single device model (eg: Google Pixel), if you intend to have OTA's available for a variety of device models, just create an additional OTA server instance for each device.

alt text

docker compose example

The service listens on port 8080 by default. Mount the output directory for the builds of the device you wish to serve to the /out folder. Also, mount a persistent public directory which will be served publicly. The public folder can be shared across multiple OTA server instances if you wish.

version: '3.8'

    image: registry.deadbeef.codes/lineageos-ota-server:latest
    restart: always
      - "8080"
      - /data/android/lineage/out/target/product/sunfish:/out
      - /data/android/public/sunfish:/public

How to point device to OTA server

The recommended way is to include the configuration inside your build of the ROM. We do this by by including the URL as a system build.prop by doing the following:

Create new file /data/android/lineage/vendor/lineage/build/core/deadbeef-ota.mk

Edit (create if not exist) /data/android/lineage/vendor/extra/product.mk

# Include deadbeef.codes OTA server