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

161–170 of 260 posts

Re: LineageOS 19

#161

Post by SahAssar »

user_7832 wrote: post #155
dTal wrote: post #149

Earlier quoted context omitted.

Perhaps I'm not understanding the issue - what legal standing does Google have to object? "Terms of service violation"?

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…

microg replicates the API but contains no actual google code, right? Isn't that exactly what google argued was completely legal when they were sued by oracle over replicating the java API?

Re: LineageOS 19

#162

Post by mishafb »

colordrops wrote: post #160
m3adow wrote: post #40

Earlier quoted context omitted.

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.

What apps dont run for you? Everything is working fine for me. Are you also using Magisk with the DenyList enabled?

There's a payment app that detects the installation source is not google play store, and I haven't found a way to use it

Re: LineageOS 19

#163

Post by nobodywasishere »

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…

> Still really odd that i couldn't just take any ROM and install it on my current phone

This is because ARM uses device trees to know what hardware's on the device, versus x86 which discovers it at boot. Every rom has to be specifically built for that exact device model.

Re: LineageOS 19

#164

Post by woleium »

ttarr wrote: post #121
nfriedly wrote: post #52

Earlier quoted context omitted.

It was not branded as a Verizon model, but it seems to have the Verizon behavior of carrier unlocked, bootloader locked (and not unlockable). Based on anecdotes like yours, I believe Google stopped doing it after the Pixel 2, but that doesn't help me.

I don't think they stopped, my Pixel 3 XL is locked also in the same manner.

you can contact them and they will replace it with an unlocked one

Re: LineageOS 19

#165

Post by daqhris »

uneekname wrote: post #83
nfriedly wrote: post #24

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…

The same thing happened to me, and I wrote an angry blog post about it[0] It is not OK for Google to lock me out of a phone that I own! LineageOS (running on a different device) has changed the game for me. It has been a smoother, more accessible Android experience, and I'm so grateful to the developers who make it happen. [0] https://jacobhall.net/2022/01/29/000177

Unrelated to the topic we're discussing, I just wanted to say that your website is super cool. Its design is so simple and appealing to my minimalist taste (and I noticed that it's open-sourced). Fantastic job!

Re: LineageOS 19

#166

Post by woleium »

skellera wrote: post #28
nfriedly wrote: post #24

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.

I doubt it is intentional. I heard they'll fix it if you contact them

Re: LineageOS 19

#167

Post by zozbot234 »

chasil wrote: post #151
uneekname wrote: post #83

Earlier quoted context omitted.

The same thing happened to me, and I wrote an angry blog post about it[0] It is not OK for Google to lock me out of a phone that I own! LineageOS (running on a different device) has changed the game for me. It has been a smoother, more accessible Android experience, and I'm so grateful to the developers who make it happen. [0] https://jacobhall.net/2022/01/29/000177

Unfortunately, Lineage has abandoned a large number of previously-supported devices, so this latest version will be met with some dismay. The primary reason is the loss of iptables, and the older kernels that do not support eBPF. U.S. carriers are also moving to VoLTE, and this is not supported on any Samsung devices at all. AT&T has already made the move, and published a list of allowed devices. It's sad to see them…

> Unfortunately, Lineage has abandoned a large number of previously-supported devices, so this latest version will be met with some dismay.

> The primary reason is the loss of iptables, and the older kernels that do not support eBPF.

It's worth noting that the pmOS folks are working on mainline kernel support for older devices. This is not always easy, since e.g. some devices are only supported via non-free kernel or userspace blobs. But good quality hardware might regain support at some point. If you have devices that are going unsupported because of this issue, you might want to experiment with porting them to a mainline kernel by following the instructions on the pmOS wiki.

Re: LineageOS 19

#168

Post by orangepurple »

afavour wrote: post #132
FrenchAmerican wrote: post #125

Earlier quoted context omitted.

How do you manage the battery? I would be afraid of a fire after x years being on all the time. Note that I have no specific knowledge on the subject ; it's quite possibly a fear without any reasonable ground. But I had a cheap speaker that I used with a Chromecast audio to listening to podcasts ; I left it always on and... I came back just in time one night, the speaker was producing a large dark smoke. I almost put…

Another reason why non removable batteries are crap. I have an old Nexus phone kicking around, if I were to repurpose it I’d just remove the battery and power it via USB. But you can’t do that with newer devices.

I wish there was an ability to replace smartphone batteries with a capacitor bank. Dashcam users have had these battery problems since Day 1. The solution is to replace batteries with capacitors. They are far more durable and can tolerate heating well.

Re: LineageOS 19

#169

Post by nfriedly »

Congrats, and thank you to everyone involved in LineageOS!

I can't use it right now, but I have many fond memories of LineageOS (and CyanogenMod before that), and I look forward to using it again in the future!

Re: LineageOS 19

#170

Post by [deleted] »

nfriedly wrote: post #24

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…

[deleted]
Post reply on HN