Live data from Hacker News

LineageOS 19

lineageos.org

41–50 of 260 posts

Re: LineageOS 19

#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 "two years old iPhone OK, six years old Android not"?

Re: LineageOS 19

#42

I'm still pissed at Google for locking the bootloader on my Pixel 2. I bought the phone unlocked directly from Google, specifically so that I could install a custom ROM once Google stopped supporting it. But I sent the phone in to repair a broken USB port, and apparently it was Google's policy to send back a phone with a locked bootloader any time you get a repair. I can't even get a response from Google's support ab…

You can’t unlock it? I got back a locked phone when I got mine repaired but I could unlock it just like I did with the one I sent them.

Re: LineageOS 19

#43
It is said to have removed of iptables in favor of eBPF. Won't we loose compatibility with AFWall+? Will there be a relevant alternative? I consider it important to choose which apps can access the Internet and when.

Re: LineageOS 19

#44
post #22

Earlier quoted context omitted.

In addition to the official wiki, or running queries on the yml data yourself (it's published under the lineage OS Github account), you can also check these two third party tools: https://lineageosdevices.com/ https://lineageos-device-finder.org/lineageos-device-configu...

> it's published under the lineage OS Github account What I found there was a list of model codenames like "redfin" rather than "Google Pixel 5". Now I've already found the list I wanted, however. Thank you anyway.

The list I meant is here:

https://github.com/LineageOS/lineage_wiki/tree/master/_data/...

It contains the full model name in the yml data.

Re: LineageOS 19

#45
post #7

It's nice to see that Lineage OS is still a prominent alternative OS. Back when I couldn't afford new smartphones, it would allow me to keep years old devices on relatively new software (these were the CyanogenMod days). Using it opened my eyes to tinkering and the possibility of a de-googled digital life. It's a shame that due to the ongoing 3G shutdown, people won't be able to keep old devices working.

You can still use old devices with WiFi. If you need phone service you can configure a VoIP provider. You lose the cell network but it's still a phone. Some would even say you'd regain privacy this way.

I have tried this in the past with Google Voice. It's just too inconvenient to not be able to make calls when I'm not near a wifi. I've learned that's the #1 feature I value in a phone.

Re: LineageOS 19

#46

I'm still pissed at Google for locking the bootloader on my Pixel 2. I bought the phone unlocked directly from Google, specifically so that I could install a custom ROM once Google stopped supporting it. But I sent the phone in to repair a broken USB port, and apparently it was Google's policy to send back a phone with a locked bootloader any time you get a repair. I can't even get a response from Google's support ab…

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 repair would cut the phone's lifespan in half, I'd have just done the repair myself, or else hired someone local to do it.

Re: LineageOS 19

#47
post #42

I'm still pissed at Google for locking the bootloader on my Pixel 2. I bought the phone unlocked directly from Google, specifically so that I could install a custom ROM once Google stopped supporting it. But I sent the phone in to repair a broken USB port, and apparently it was Google's policy to send back a phone with a locked bootloader any time you get a repair. I can't even get a response from Google's support ab…

You can’t unlock it? I got back a locked phone when I got mine repaired but I could unlock it just like I did with the one I sent them.

Yes. Was yours a Pixel 2?

I'm not the only one to experience this issue, see https://support.google.com/pixelphone/thread/14920605/google... and https://issuetracker.google.com/issues/73217322 and https://issuetracker.google.com/issues/68897739

Re: LineageOS 19

#48
post #42

Earlier quoted context omitted.

You can’t unlock it? I got back a locked phone when I got mine repaired but I could unlock it just like I did with the one I sent them.

Yes. Was yours a Pixel 2? I'm not the only one to experience this issue, see https://support.google.com/pixelphone/thread/14920605/google... and https://issuetracker.google.com/issues/73217322 and https://issuetracker.google.com/issues/68897739

I see. Mine was a 2 XL. Probably not the same exactly

Re: LineageOS 19

#49
post #5

I love Lineage and used it as my main phone OS but since my carrier required in February for VoLTE to work, I can’t receive or make phone calls anymore.

You may have to call your carrier and have them change some things. I had trouble with AT&T a couple times, but then they had me turn off the phone, sent some data to it, then turn it back on. All good now.

Re: LineageOS 19

#50

It is said to have removed of iptables in favor of eBPF. Won't we loose compatibility with AFWall+? Will there be a relevant alternative? I consider it important to choose which apps can access the Internet and when.

It appears so, for now. Apps can be updated to support IPTables to eBPF wrappers, though; you'll have to see if the developer(s) behind AFWall+ will be able to get that to work. This isn't just a LineageOS issue, it should also cause problems for anyone running any other form of Android 12.
Post reply on HN