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

71–80 of 260 posts

Re: LineageOS 19

#71

Post by jeroenhd »

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.

Re: LineageOS 19

#72

Post by zozbot234 »

KronisLV wrote: post #70

This is pretty cool to see! Still really odd that i couldn't just take any ROM and install it on my current phone from a slightly less popular manufacturer: https://www.ulefone.com/ Of course, phones don't work as regular desktop computers do for some reason, though i really enjoy being able to just throw Debian/Ubuntu/Rocky/Alma (or some of the BSDs as well, though support varies) at some pile of x86 consumer hardwa…

Most recent hardware should "vaguely work" using GSI images.

Re: LineageOS 19

#73

Post by raelmebrand »

andrecarini wrote: post #51

Unfortunately it seems LineageOS isn't available for most (if not all) common budget/mid-range phones in my country. Does anyone here have experience in porting AOSP/LineageOS to an unsupported device? Any suggested materials and resources? I have the spare time to give it a go on getting it for my Samsung model, but no idea where to start.

Please try https://github.com/phhusson/treble_experimentations/wiki for recent devices (Android oreo and later). GSI is fine; of course not everything is perfect. Also google XDA GSI forums for specific advice

Re: LineageOS 19

#74

Post by hedora »

jeroenhd wrote: post #62
tmoravec wrote: post #41

I'm curious how secure LineageOS is. It doesn't seem to have the resources of Apple/Google to respond to vulnerabilities. I haven't even found anything on this topic at their website. Googling "lineageos security response policy" haven't found anything useful, either. How does it compare to flagship Samsungs/Pixels/iPhones? Is it usable in, say, corporate settings that do have some security standards in the vein of "…

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 worried about the lag between Android security patches (and vendor blobs, which GrapheneOS gets direct with android updates, from what I can tell) and custom ROM updates.

You're much more likely to get hit by some Samsung zero day that impacts 100M active devices than something targeting a custom ROM.

(All of this is assuming you're a boring target, which most people are.)

Anyway, the main deciding factor for me between the two operating systems was device support.

Re: LineageOS 19

#75

Post by ajot »

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.

Re: LineageOS 19

#76

Post by BenjiWiebe »

jeroenhd wrote: post #68
Tistron wrote: post #32

I used to run lineage, but every time there was a major version upgrade I had to reinstall, which was annoying. So I reverted to stock OS. Has that changed? Can it upgrade between major versions now?

I've always done upgrades and they usually worked, but updating across Android versions is quite painful. You need to be wary not to accidentally keep old versions of GApps and any other system modifications installed, and not all system services migrate that easily. At some point, a transitionary .zip was published to help users upgrade between versions. However, I'm pretty sure their official policy is still that y…

Unless the major upgrade is Fedora, then it works great and is well supported to update in place for many years. The one major issue I had once was my fault because a force rebooted in the middle of the install. Still got it working though.

Re: LineageOS 19

#77

Post by tmoravec »

jeroenhd wrote: post #62
tmoravec wrote: post #41

I'm curious how secure LineageOS is. It doesn't seem to have the resources of Apple/Google to respond to vulnerabilities. I haven't even found anything on this topic at their website. Googling "lineageos security response policy" haven't found anything useful, either. How does it compare to flagship Samsungs/Pixels/iPhones? Is it usable in, say, corporate settings that do have some security standards in the vein of "…

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…

Thanks for the comprehensive post! The weekly updates in particular sound good.

Re: LineageOS 19

#78

Post by raelmebrand »

tmoravec wrote: post #41

I'm curious how secure LineageOS is. It doesn't seem to have the resources of Apple/Google to respond to vulnerabilities. I haven't even found anything on this topic at their website. Googling "lineageos security response policy" haven't found anything useful, either. How does it compare to flagship Samsungs/Pixels/iPhones? Is it usable in, say, corporate settings that do have some security standards in the vein of "…

Security is a bit different for different people. If you want to do browsing minimising ads/spying from rubbish lineage is there. Also one can block minimise data, improve battery life by avoiding playstore

> corporate settings that do ha

Use a dedicated phone

Re: LineageOS 19

#79

Post by zozbot234 »

BenjiWiebe wrote: post #76
jeroenhd wrote: post #68

Earlier quoted context omitted.

I've always done upgrades and they usually worked, but updating across Android versions is quite painful. You need to be wary not to accidentally keep old versions of GApps and any other system modifications installed, and not all system services migrate that easily. At some point, a transitionary .zip was published to help users upgrade between versions. However, I'm pretty sure their official policy is still that y…

Unless the major upgrade is Fedora, then it works great and is well supported to update in place for many years. The one major issue I had once was my fault because a force rebooted in the middle of the install. Still got it working though.

Debian Stable also has a very well documented upgrade workflow.

Re: LineageOS 19

#80

Post by cxr »

nfriedly wrote: post #46
skellera wrote: post #28

Earlier quoted context omitted.

Is that really their policy? Unlocked until it needs to be fixed? Seems like that’s worse than just locking it down in the first place.

It was never a publicly stated policy and, anecdotally, they seem to have stopped doing it on newer phones. But one person escalated to a manager (because the first-level support staff didn't understand the difference between carrier unlocking and bootloader unlocking), and the manager stated that it was their policy. And, yeah, I agree that it's probably the worst of all situations. If I'd have known that a google r…

Are you in the US? It doesn't solve the issue that you now have to deal with, but if you paid for the "repair" service, I'd have considered cancelling the payment through my bank.
Post reply on HN