luca020400

7 ms·

1.
by luca020400 9mo ago
Almost all device run on the initial android release (QPR0), and never shipped any of quarterly updates. Even less so using _main_ as a baseline so that point is moot. With android 16 introducing "mid releases" (QPR2), they expect
2.
by luca020400 10mo ago
> AIUI updates are less stringent and burdensome than initial certification That's true having dealt with some of it, nonetheless I haven't found that much of a difference due to having to use 3PL. There's more manual step
3.
by luca020400 10mo ago
I don't think that's a fair comparison. OEMs have quite a lot of extra steps before releasing any build to the public. They have to pass xTS, the set of test suites required before getting certified by Google, possibly carrier cer
4.
by luca020400 1y ago
^^
5.
by luca020400 1y ago
It isn't cell networks, no one ever on that side ever blocked Android forks. It's the implementation that OEMs used to support VoLTE isn't compatible with AOSP APIs. If it wasn't for Google here you'd never have VoL
6.
by luca020400 1y ago
As Lineage is concerned I found that a while ago and made https://review.lineageos.org/c/LineageOS/android_packages_mo... But no one bothered to test, and I had no way to verify so it's in a limbo for now :)
7.
by luca020400 3y ago
What stops you from uploading a fix? Now that I know about the issue I can do it myself, but... Regardless let me tell you that: AOSP fixed it for Android V!
8.
by luca020400 3y ago
Not entirely sure what configuration you're looking for, but the one supported in Android can be found here https://android.googlesource.com/platform/packages/modules/B... https://android.goog
9.
by luca020400 3y ago
Thanks for digging it up. Sometimes I can't comprehend how people come up with that stuff when it was already publicly explained how/why it happened :/
10.
by luca020400 3y ago
Pressure from Google? I myself removed that feature because the effort to have it was more of an hassle than anything else.
11.
by luca020400 3y ago
There's many of us :)
12.
by luca020400 3y ago
Android APIs are stable and an app will keep working until Google decides to bump the min SDK version in Android itself. The APIs a Google app uses are the same as any other app. Unless the app is privileged ( = can use system APIs ) there&
13.
by luca020400 3y ago
Supported => Supported by Google yes. I think you misread my comment, or I wasn't clear enough, I work on AOSP daily so I know very well what's in there :)
14.
by luca020400 3y ago
A lot of people still don't see how the operating system as a whole is open source, not having properly supported open source apps is not the best, but while we can make apps and/or update the aosp versions, we can't make an
15.
by luca020400 3y ago
You'll hear that it's been happening since years, and while a lot of us tried to upstream some of our enhancements/changes hardly any of them got accepted ( or anyone is actively working on those apps to review them properly
16.
by luca020400 3y ago
Their plan is to remove them altogether. Still those apps have not been maintained in years, that's the normal course of action for apps in AOSP.
17.
by luca020400 3y ago
Yep, everything you said is correct. The AMSS has control of the hardware, but there's different components, each implementing different functionality, they may be able to talk with each other using various IPC mechanism, and they do,
18.
by luca020400 3y ago
You have to manually strip the QCOM additions in the vendor side. It's just a matter of removing files, but I wouldn't expect to do it without some knowledge how the whole thing works in Android, without breaking GPS as a whole.
19.
by luca020400 3y ago
This operating system, know as firmware running in the DSP. That's the only sane way to have a working device that needs to handle signals. It's not hidden in any way, and the kernel/Android actively talks with it, configures
20.
by luca020400 3y ago
The download is done from the Android side. It's a privileged app ( a service in Android lang ) that once fetched sends the data to the modem, where GPS is actively implemented, and augmented by such extra data.
21.
by luca020400 3y ago
Leaving aside the opt-in/opt-out possibility. You can remove the services that download the extra GPS data, nothing stops you from doing that, aside making GPS unusable :)
22.
LineageOS 20(lineageos.org)
239 points by luca020400 4y ago|147 comments
23.
by luca020400 5y ago
Indeed, everyone works in its own way. Most on this scene started because people had obscene support by some OEM, so just for personal interest. But after a while you see the whole community behind it and you don't have much of a choic
24.
by luca020400 5y ago
I've been doing CyanogenMod for years, and since become a director at LineageOS. I've never heard anything akin to " malicious organization/project that's involved in spreading misinformation about GrapheneOS and ha
25.
by luca020400 5y ago
1) You can still block network via a native firewall ( it's in app settings ), currently the only issue is that network via VPN bypass the toggle. 3) Never heard of this happening, and I've heard a lot of stuff.
26.
by luca020400 5y ago
If you're rooted your security is way lower. Simple as that. Rooting can be used against you, it can lead to exploitation, and likely has been. Note: you can have secure boot without root and using your own Android build, such as Calyx
27.
by luca020400 5y ago
We cater the normal user. And what the hell? Root with verified boot? That's like having the most secure castle while leaving the door open for anyone, you can't have both worlds. Note: our root implementation was apparently affec
28.
by luca020400 5y ago
Privacy Guard) I was the one who purposely removed it. I spent days ( if not weeks ) trying to get it working properly ( read, it never worked properly and causes many issues we still have tickets for ) futhermore Google basically rewrote t
29.
by luca020400 5y ago
Guess I'll play a bit more on CalyxOS then. Feel free to hire me I guess. We are the base of course.
30.
by luca020400 5y ago
Director/Head Developer @ LinaegeOs here. Hi, sharing codebase when? :P

More ›