Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LineageOS 19

lineageos.org

Post reply on HN
Print view View original

181–190 of 260 posts

Re: LineageOS 19

#181

Post by snvzz »

jeroenhd wrote: post #71
shimonabi wrote: post #57

I tried Lineage on my Xiaomi 10T Pro a while back, but some of the apps I use the most (NFC pay/credit card double verification for online shopping, gasoline payment with a QR-code) just don't work with it, so I had to revert to a stock ROM. The developers seem to have a whitelist of acceptable Android versions.

This could be a Safetynet issue, which you can fix by rooting your phone and installing Magisk + the necessary module. It's not a perfect fix (Magisk can't make GPay work) but it works most of the time for me. My bank is fine with me running a rooted phone, so I can't tell you for sure if it'll fix your situation.

Alternatively, https://lineage.microg.org/ discussed elsewhere in this thread seems to fare better by default.

Re: LineageOS 19

#182

Post by EFruit »

Their IRC setup is profoundly disappointing. Joining their channel redirects unregistered users to a designated quarantine room that blocks all messages.

Why on earth do I need to manage YET ANOTHER account just to ask a question, get a response, and leave?

Re: LineageOS 19

#183

Post by lufte »

captn3m0 wrote: post #135

PSA: LineageOS 17.1 is no longer getting official builds, even though it has some of the recent security updates committed. So if can't upgrade immediately to 18.1, you can do a build yourselves to get the security patches. https://endoflife.date/lineageos

Good tip. My device doesn't have any official build newer than 17.1 so I may need to start building my own images.

Re: LineageOS 19

#184

Post by kbenson »

colordrops wrote: post #159
user_7832 wrote: post #155

Earlier quoted context omitted.

Partly that, but also a lot of/all of Google Services Framework is proprietary Google code. Other implementations reverse-engineer and modify it afaik. Google probably doesn't go after them because they're small, but LOS is the largest such organization and would be an easy target if Google were to sue. And also, even if it's technically legal, it's such lawsuits/slappsuits can entirely bring down an organization as…

Is this your speculation or is that their stated reasoning?

Nobody is talking about stated reasons, the question is what grounds Google would have to object on if they chose to. That means it's speculation.

Re: LineageOS 19

#185

Post by ajvs »

pja wrote: post #94
deng wrote: post #82

I just switched to LineageOS 18 w/ MicroG and oh my lord is this stuff still complicated. I'm fairly familiar with this stuff and yet still it took me many hours to set everything up correctly. To be clear, this is not the fault of LineageOS, this is simply the state of the FOSS Android environment and the fact that Google has no interest in supporting this setup whatsoever, to put it mildly. Not only is it complicat…

You could just run an unrooted LineageOS? What exactly are you getting out of a rooted phone that you couldn’t get with a straight LineageOS install?

AccA, Titanium Backup, Acet's Call Recorder Magisk module, etc.

Re: LineageOS 19

#186

Post by lberrymage »

hedora wrote: post #74
jeroenhd wrote: post #62

Earlier quoted context omitted.

LineageOS relies on the open source kernels and pre-existing vendor blobs to run. Qualcom drivers and such won't receive any patches, the best you can hope for is that the driver blobs are extracted by the device maintainer and put into the next build. As for the Android stack itself, LineageOS follow the upstream Android branches very closely where it can. Most vulnerabilities in that stack will probably be shared a…

GrapheneOS is able to support relocking the bootloader, but only works on Pixel devices (the bootloader lock is one of the main reasons they only work with Pixels). I personally think the booloader lock is of dubious value. It protects against physical attacks against the device (evil maid attacks). That's very low in the list of threats I worry about. (Though I am using GrapheneOS, and am happy with it.) I'd be more…

Locking the bootloader (to enable verified boot) isn't only a protection against physical attacks. It also ensures that any deep OS exploit that occurs is not persistent since the base OS is cryptographically verified on boot. This is really important to the security model, because otherwise you have no reliable way to protect against persistent exploits or verify that you're running a genuine release of the OS you think you are.

Re: LineageOS 19

#187

Post by ajvs »

ajot wrote: post #75

If you are reading this, thank you for backporting to kernel 4.4! My phone is only a year and a half old. I'll just wait for the OpenGapps to have at least an unofficial 12.0 version to upgrade, so I can keep using the minimal Gapps required and not bloat my phone with crap I'll never use like Gmail or Youtube.

MindTheGapps is a decent alternative that supports Android 12.

Re: LineageOS 19

#188

Post by Zak »

pja wrote: post #94
deng wrote: post #82

I just switched to LineageOS 18 w/ MicroG and oh my lord is this stuff still complicated. I'm fairly familiar with this stuff and yet still it took me many hours to set everything up correctly. To be clear, this is not the fault of LineageOS, this is simply the state of the FOSS Android environment and the fact that Google has no interest in supporting this setup whatsoever, to put it mildly. Not only is it complicat…

You could just run an unrooted LineageOS? What exactly are you getting out of a rooted phone that you couldn’t get with a straight LineageOS install?

I'll add to the list: Advanced Charge Controller, and the ACCA GUI app for it.

This provides fine-grained control over battery charging if the kernel/device have the required features. The user can set limits on current, voltage, and percentage, as well as pause charging when the battery gets too hot. These settings can be saved into profiles selectable with a tap or on a schedule.

Limiting charge speed/capacity can significantly extend the service life of the battery.

Re: LineageOS 19

#189

Post by LukeShu »

m3adow wrote: post #40
karteum wrote: post #10

I wish that LineageOS could accept the "signature spoofing" patch that is needed for microg (possibly with a toggle switch that would be "off" by default), so that we could avoid the need for the less-frequently-updated https://lineage.microg.org/ and properly install apps from Play Store without the Google Service Framework (that essentially give root access to Google on your smartphone). (and actually I also wish t…

Having the sandboxed Google Play services would be wonderful. I'm currently using LineageOS with microG and Aurora store, but quite a lot of apps do not properly run with microG. Having some kind of fallback alternative in a second user or even better a work profile would be great.

FYI, GrapheneOS supports sandboxed Google Play services.

Re: LineageOS 19

#190

Post by lberrymage »

zekica wrote: post #106
aaaaaaaaata wrote: post #55

Earlier quoted context omitted.

Lineage actively and knowingly break the Android Security Model in order to achieve widespread compatibility and reduce e-waste. Security is not their top competency, nor mission. Check out the pages on GrapheneOS.org, definitely seems they're who you're after.

Lineage doesn't "break" android security model. It works around OEMs that don't support installing your own keys in the bootloader. Otherwise, security model works the same as any other android. LineageOS's first priority isn't security - it's freedom. Graphene and CalyxOS have security as the first priority - but have only a couple of phones on their support list and they deprecate old devices as soon as they stop r…

Yes it does. They ship userdebug builds as production releases, pretend to support devices past their vendor EOL (which is impossible since Lineage can't provide security updates for firmware etc.), ship the F-Droid Privileged Extension (which uses an incorrect approach to implementing unattended updates), don't support locking the bootloader to enable verified boot on many supported devices, etc..
Post reply on HN