just upgraded my #lineageos to get androids #security patch level for #november
take that as a #reminder to upgrade your phones, laptops, pcs, tvs, cars, microwaves... :)
@martin
I'd like too, but my Moto G5s is stuck at the june patches. No news from Motorola. And no LineageOS as well.
Never again a Motorola device.
@niebegegnet i know how that feels.. i've had a #shiftphone (to support a #startup) until recently and i've been extremely unsatisfied... i bought that in december 2016, and got a single #update in summer 2017 (that was patch level march 2017) - and that's it! the phone is not even 2 years old, but i needed to #trash it as it always felt painful to use it (with sooo many known #security issues...)
@niebegegnet
now i'm supper happy that a colleague sold me his used #oneplusone!
i will never again buy a #phone that is not supported by #linageos (or whatever it will be called by then...^^)
@martin My experience with a couple of phones showed that LineAgeOs/CyanogenMod firmware for that devices was far less stable than an older original firmware. :-(
No wonder: far less people work on the firmware testing systematically... So I trashed that phones anyway.
@yvolk
Really? So far I'm pretty #satisfied with the #linageos quality. I've had only 2 or 3 #issues in ~7 years...
But even if there may be some #feature not working perfectly, for me it feels ways better than plenty of #severe vulnerabilities...
So you have any other #suggestion? How do you live with that?
@martin I waited for months, hoping that one day an annoying problem (touch screen disfunction that occurred from time to time) will be solved. But after a year, when I gave the device to a grandmother, I realized that she won't be able to fix the problem each week... So I reverted firmware to the latest officially supported, and since that time I didn't hear from her that the device doesn't work.
Of course, problems with two old devices don't prove anything :-)
@yvolk a broken touch screen is indeed an issue you cannot accept.. did you report that issue? or did you check if it is already known?
@martin I decided that the problem was with compatibility between old vendor's driver and custom firmware. I hope that new Android system / kernel modular structure (which was introduced in #Android 9 only) will simplify reuse of old drivers in the newer Android system builds... See https://source.android.com/devices/architecture/kernel/modular-kernels
As a general tip, I think Nexus devices will get updates (from a vendor and from community) longer than others...