101–110 of 147 posts
Earlier quoted context omitted.
> They? This is my project, it is just me. "They" has been an acceptable default third-person singular pronoun since at least the 1400s. If there's something you'd prefer, it might be wise to list it on one of your user profile pages.
The comment was in direct response to me, but not addressed to me, so it was they as in "project members" (which there are none).
I went to the site and failed to understand what’s different from other Android distros to make the general claim of “support for EOL Android devices”. Isn’t it the same as LineageOS or whatever other distros you can find for each device at XDA? I thought I was going to find a site that found a way of running newer Android over the old one to not have to worry about drivers and such, but I found yet another distro wi…
Earlier quoted context omitted.
I run latest Android version on my 6 years old Pixel 1. The only reason it isn't provided by Google is that Google doesn't want to.
More like Qualcomm doesn't want to spend the money to do it. Google can't update the binary drivers and firmware that Qualcomm gives them. And Google only has so much leverage in order to get Qualcomm to provide updates to older hardware. Sure, Google could release newer Android versions (assuming they'll run under whatever last kernel version Qualcomm provided support for, which isn't always the case), or at least r…
1. The lockscreen bypass security flaw of last week is major compared to any flaw Qualcomm currently have.
2. Apple still updates devices hit with checkm8, so maybe security doesn't dictate everything for them. Not sure why it needs to for Google.
3. What does security has to do with getting Material You to my device? (to give just one example). Maybe the idea is that if a device is insecure, then it must get to the trash bin...? I hope not.
Earlier quoted context omitted.
The title states "Long-term support for end-of-life Android devices". This "long term support" does not extend beyond cherry picked AOSP security patches and does not address the security issues in the drivers of these devices.
But it does what it can. It patches the system, the kernels, adds many hardening features, provides updated browser engines, and removes the proprietary unpatchable components that it can. This is all well documented on the website, please read through it.
The name sure is pretentious.
I went to the site and failed to understand what’s different from other Android distros to make the general claim of “support for EOL Android devices”. Isn’t it the same as LineageOS or whatever other distros you can find for each device at XDA? I thought I was going to find a site that found a way of running newer Android over the old one to not have to worry about drivers and such, but I found yet another distro wi…
Yeah I was checking what support they advertised for my old nexus 5 and the recently retired oneplus X of my girlfriend. The nexus 5 is on 9.0, mostly working, the oneplus X isn't supported at all. That's not long-term support.
The support is in the form of all the added security features, the (system) updates, and kernel patches like this: https://gitlab.com/divested-mobile/divestos-build/-/blob/mas...
"the best os" / divestOS. The name sure is pretentious.
Earlier quoted context omitted.
But it does what it can. It patches the system, the kernels, adds many hardening features, provides updated browser engines, and removes the proprietary unpatchable components that it can. This is all well documented on the website, please read through it.
What would you suggest for using MicroG on a DOS-supported device? I see built-in support was removed in 18.1. Could just the DOS kernel be used with the official microg-lineageos on top?
You can get a fair bit of benefit from using the boot.img like you say, but it will only go so far.
While I wouldn't recommend it, there are flashable ZIP images of microG, but it'd be at the downsides noted here: https://divestos.org/index.php?page=faq#rootSupport