[Galaxy S III General] Chainfire:
Please note I do not follow this thread. If you want any chance of me seeing your post, you need to "mention" me ( [MENTION=631273]Chainfire[/MENTION] )

OpenDelta is still really really young and no doubt there'll be some more issues down the line.

Also, I see a lot of people around being annoyed by having to reflash SuperSU every update... You guys know there's an option in SuperSU settings to create a backup script, right? Once you've done that, the internal backup tool present in pretty much all major custom ROMs (CM, AOKP, PA, Omni, etc) will preserve SuperSU for you.

Frequency checker? It's designed to not get "in your way" with checking. You can disable checks completely by setting the "Networks" to "nothing".

Changelogs will eventually come. Changelog server for Omni has only just come online, and since that isn't really open, an intermediate solution needs to be found to pull changelogs into the updater without making it unusable for other non-Omni ROMs.

Starting tomorrow (so you'll have to have the 20131208 nightly flashed already for this to work), you can drop ZIPs in /sdcard/OpenDelta/FlashAfterUpdate folder (the correct folder will automatically be created for you once you are on 08 or newer and force a check for updates, so you know its the right folder) and they will all be automatically flashed after the update is performed. So just drop your kernel ZIP in that folder as soon as it exists. For the update from 08 to 09 you should not have to do anything manually anymore.

OpenDelta is only tested against TWRP, Omni's official recovery of choice. There is some code in OpenDelta to cope with CWM, but is (a) untested and (b) known to break if you run an "official" CWM (installed by ROM Manager, downloaded from the CWM website, etc - those are intentionally crippled in the scripting department by it's author). There will not be a work-around for this. If you must run CWM, use a version like PhilZ (which still isn't tested against, but much more likely to work) which has no such crippling.

The updater does *not* *only* download big files. It downloads deltas if possible (and if the collection of deltas is smaller than downloading the full zip, if you have not updated for a while). But for deltas to be possible it needs a starting point. A + B = C. If you don't have A, you can't make C. Initially, it'll try to locate the ZIP for the current flash on your storage (internal only) and use that as a base, but if it can't find that, the first time the update is used, it will have to download the full update ZIP. It saves that so it can be the starting point for the *next* update, though. So it is not at all strange that the first time you use it it downloads a full-sized ZIP.

It uses deltas to reconstruct a full flashable ZIP that is content-equivalent to downloading a full nightly release. It is not a delta of any files on your system (though that would essentially be the same thing) - it is merely a delta of the downloads. As such the result is exactly the same as if you'd download a full nightly ZIP and flash that. If you look through the OpenDelta folder on your storage, it is also normal to only find one big ZIP file (while the updater isn't actively working), regardless of whether deltas have been used or not.