- Feb 15, 2014
Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.@Tomoms
For some reason after flashing the 3/11 build, there is an update available for the same build. Same size too. Updating doesnt change anything. It goes through the whole process but the build stays the same and the same update is available again. The updater is showing 2/17 as the current build. Weird.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.
Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.Has anyone tried the dual speaker mod on lineage 20? Need to know before going forward with it.