OTA v2

[Gelbpunkt]

• New client, not based on weird PE one
• Allow flashing any version in the history (would mean changing format)
• Changelog text (markdown rendering?)
• toggle between wifi and mobile data downloads

[Diniboy1123]

maybe consider:

• detect connectivity changes and pause/resume download on network drop/connection
• use sha256 file to validate
• custom mirror support
• when pre-release is selected, pull from both origins
• show a label next to the latest release
• clean flash required arg

[Gelbpunkt]

My current idea for OTA format would be having a single JSON file per device (yes, since maaaybe we can support other devices with the same SOC by Xiaomi), it would look like this, with new releases being added at the top:

{
    "device": "davinci",
    "device_full": "Mi 9T/Redmi K20",
    "maintainers": [
        {
            "main": true,
            "github": "Diniboy1123",
            "name": "Mary Johanna"
        },
        {
            "main": true,
            "github": "Gelbpunkt",
            "name": "Jens Reidel"
        },
        {
            "main": false,
            "github": "SomeDude",
            "name": "Some Developer"
        }
    ],
    "website": "https://github.com/DavinciCodeOS",
    "news": "https://t.me/DavinciCodeOS_Support",
    "releases": [
        {
            "version": "12.2",
            "type": "alpha",
            "needs_clean": true,
            "timestamp": 1649101502,
            "filename": "DavinciCodeOS_davinci-12.2-20220404-2147-OFFICIAL.zip",
            "size": 9999999,
            "download": "SOME_URL_YOU_KNOW",
            "sha256": "SOME_HASH_YOU_KNOW"
        },
        {
            "version": "12.1",
            "type": "beta",
            "needs_clean": false,
            "timestamp": 1649101501,
            "filename": "DavinciCodeOS_davinci-12.1-20220404-2146-OFFICIAL.zip",
            "size": 9999999,
            "download": "SOME_URL_YOU_KNOW",
            "sha256": "SOME_HASH_YOU_KNOW"
        },
        {
            "version": "12.1",
            "type": "stable",
            "needs_clean": false,
            "timestamp": 1649101500,
            "filename": "DavinciCodeOS_davinci-12.1-20220404-2145-OFFICIAL.zip",
            "size": 1824286089,
            "download": "https://github.com/DavinciCodeOS/Cathedra/releases/download/vergion/DavinciCodeOS_davinci-12.1-20220404-2145-OFFICIAL.zip",
            "sha256": "eb48a64ba6d12235db655e01883cacb791eceac31f2299e4f016e19678ce41bf"
        }
    ]
}

TODO: Changelog inline or as a link? TODO: Mirror support won't work with direct URLs, unless we make mirrors point to other davinci.json files? Thoughts?

[Diniboy1123]

I would use a link for the sha256 so it would be pulled and extracted from a file. Otherwise I like the proposal.

Changelog as link please.

I thought about mirror support with custom jsons hosted by 3rd parties too. The link could be specified in the updater.

[Gelbpunkt]

I'd say changelog as a link is good, yes. Means one file per release, but that's okay. We could use https://github.com/noties/Markwon to render markdown changelogs in the app.