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

LineageOS 22

lineageos.org

Post reply on HN
Print view View original

101–110 of 166 posts

Re: LineageOS 22

#101

Post by zozbot234 »

pimterry wrote: post #99

Love to see the ongoing progress here, but I'm really starting to worry that the growth of attestation on Android will make using custom ROMs like LineageOS impossible in future. Is there any way we can fight this? Feels like there must be some EU/US consumer rights or digital market legislation somewhere that could be used to more directly object to organizations like banks saying "your phone works just fine but we…

Just buy a separate low-cost device and use that only for your banking. It's a total non-issue, there are way more nefarious uses of SafetyNet/the attestation API's.

Re: LineageOS 22

#103

Post by cenamus »

sunaookami wrote: post #94
okanat wrote: post #83

Earlier quoted context omitted.

Whatsapp and Signal are fine. Random banking apps suck because their myopic and incompetent policies around custom OSes. Especially here in Germany where banks and even tech company management see internet as a magic, totally untrustworthy new curiosity. Combined with the overall extreme risk-averse society, basically none of the bank apps from big banks work with custom OSes. All require various levels of "hacking".…

Anecdote: I develop an app for a bank at my job in Germany and I was forced to implement root detection because of some annoying pentest. Everyone agreed that it was just security theater + checkbox compliance but it "had to be done"...

Even the apps that work for online banking, you can't use them for digital payments anymore. The old integrations worked fine but with Google Wallet even GrapheneOS isn't good enough

Re: LineageOS 22

#104

Post by wkat4242 »

zozbot234 wrote: post #101
pimterry wrote: post #99

Love to see the ongoing progress here, but I'm really starting to worry that the growth of attestation on Android will make using custom ROMs like LineageOS impossible in future. Is there any way we can fight this? Feels like there must be some EU/US consumer rights or digital market legislation somewhere that could be used to more directly object to organizations like banks saying "your phone works just fine but we…

Just buy a separate low-cost device and use that only for your banking. It's a total non-issue, there are way more nefarious uses of SafetyNet/the attestation API's.

The problem is you need banking stuff on the go more and more. Here in Spain for example people often pay friends with a service called bizum that works through the bank's app.

It's definitely not a non issue for me.

Re: LineageOS 22

#105

Post by homebrewer »

zozbot234 wrote: post #101
pimterry wrote: post #99

Love to see the ongoing progress here, but I'm really starting to worry that the growth of attestation on Android will make using custom ROMs like LineageOS impossible in future. Is there any way we can fight this? Feels like there must be some EU/US consumer rights or digital market legislation somewhere that could be used to more directly object to organizations like banks saying "your phone works just fine but we…

Just buy a separate low-cost device and use that only for your banking. It's a total non-issue, there are way more nefarious uses of SafetyNet/the attestation API's.

You'll have to change it often if you're worried about safety at all. Lineage has been keeping my phone alive for five years now, and although it only updates the upper layers and there are definitely unfixed vulns in the firmware, it's much better than if I'd used the stock OS that hasn't been updated since the beginning of 2020. Banks don't or won't understand this.

Re: LineageOS 22

#106

Post by 9cb14c1ec0 »

nubinetwork wrote: post #74
9cb14c1ec0 wrote: post #25

Earlier quoted context omitted.

> but it is an extra pain. I've bricked several Samsung devices trying to flash Lineage on them. It is important to follow the Lineage installation instructions very closely.

It used to be dirt easy, i remember my s5 was just "fastboot oem unlock" and flash the new image... Sure you'd lose knox, but nobody really uses it anyways... But from what lineage is saying, it seems Samsung made unlocking impossible on North American devices. I'm not sure what the law side of things is like for this, because I recall it being mandated that phones could be sim unlocked after contracts expire... some…

> it seems Samsung made unlocking impossible on North American devices.

It is possible to unlock them. It just takes about 20 steps and multiple reboots.

Re: LineageOS 22

#107

Post by gf000 »

zozbot234 wrote: post #62
t14000 wrote: post #61

> Android 15 introduced several complex changes under the hood... > Android’s move to trunk-based development, and the subsequent growth in size of Android’s QPRs (Quarterly Platform Releases) have made our job magnitudes harder! As a byproduct we must rebase our entire code-base every 3 months. > Sadly, Google also has a habit of introducing deprecations or outright removing code that older devices rely on with litt…

> Google trying new tactics to move Android from open-source to "source available, lol"? It seems to be the opposite - more of AOSP internal development moving out into the open. QPR's are getting more frequent releases than the old AOSP code-drops. (Tbh I do think that AOSP has always had way too much churn for a sensible system. A Linux phone should just work, and share as much of its codebase as possible with Linu…

Or maybe the Linux Desktop (used by a couple of people) should use more code from the android project (which is the biggest OS on the Earth)

The latter has sane sandboxing, proper IPC, an app lifecycle that makes sense for embedded devices (an app in the background should only ever take CPU time if it has an explicit service with permission for that) etc.

Re: LineageOS 22

#108

Post by pimterry »

zozbot234 wrote: post #101
pimterry wrote: post #99

Love to see the ongoing progress here, but I'm really starting to worry that the growth of attestation on Android will make using custom ROMs like LineageOS impossible in future. Is there any way we can fight this? Feels like there must be some EU/US consumer rights or digital market legislation somewhere that could be used to more directly object to organizations like banks saying "your phone works just fine but we…

Just buy a separate low-cost device and use that only for your banking. It's a total non-issue, there are way more nefarious uses of SafetyNet/the attestation API's.

It's not just banking. Though that's clearly the most inconvenient, I've heard stories of this in all sorts of contexts, and Google actively push it for _all_ apps in the play console etc now. Carrying two devices just to use basic things will work, but god that sounds annoying.

I'm curious though, what are the more nefarious uses you're concerned about?

Re: LineageOS 22

#109

Post by lufte »

nanna wrote: post #73

How's LineageOS with WhatsApp, Signal and random banking apps these days? Or let me put it another way: anyone running LineageOS but struggled to run any essential apps? (I don't care about games or whatever, I mean the apps you need to get around in life).

Whatsapp works even if you choose not to install Google Services. You can download the apk directly from https://www.whatsapp.com/download.

Re: LineageOS 22

#110

Post by gf000 »

timschmidt wrote: post #44
prosody wrote: post #42

Earlier quoted context omitted.

Isn’t that significantly on the Linux kernel not having stable driver ABIs?

I don't see how any choice the Linux developers make forces phone manufacturers to do anything. It's their choice to use Linux. They can abide by the license or not ship Linux. Not to mention that there are many more or less stable APIs within the kernel (which even has versioned API support in places) such as Video4Linux which manufacturers seem dead set against using.

They do abide by the license, but it's also their choice whether to maintain cheap firmware for n years old devices, that they may not even have the license to distribute in source form.

Nonetheless, android mostly solved the issue of the kernel's lack of stable interface via their HAL.

Post reply on HN