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

LineageOS Android Distribution

lineageos.org

Post reply on HN
Print view View original

91–100 of 104 posts

Re: LineageOS Android Distribution

#91

Post by anotherevan »

wazoox wrote: post #48
OJFord wrote: post #12

Earlier quoted context omitted.

The third OnePlus model is an old one now? I remember the first one coming out (and haven't kept track of how many there have been) but I honestly don't think I do anything that needs more than what the first one would give me. (I actually have a Motorola One, which is on the 'Android One' mostly-stock long-term upgrade committment, and was about £150 new 18mo ago? £100 phone or less would be plenty powerful enpugh,…

I still have my OnePlus One as a spare phone. I can confirm the only missing feature is a fingerprint reader. Photo and video quality are fine, power is more than necessary, battery lasts long enough...

I'm still using my OnePlus One as my phone. A fingerprint reader is really the only thing that tempts me to move.

Re: LineageOS Android Distribution

#92

Post by _0ffh »

dylz wrote: post #80
_0ffh wrote: post #11

Earlier quoted context omitted.

>HTC are well-known for providing locked-down devices I've been using HTC devices for ages, and so far every one of them was dead-simple to unlock: Just go to the HTC developer page and enter your phone ID, get unlock code and enter on phone, done! Naturally HTC will from there on out decline responsibility for bricked phones, but which company doesn't?

I've bought a handful of used HTC devices in the past. Only "real" HTC devices are go to dev page and unlock. If they've been through a carrier that isn't T-Mobile, it's very likely permanently not unlockable. Try entering a Verizon-issued HTC or Sprint-issued HTC on the page.

Yes, entirely possible (I wouldn't know, I'm not US based). When the carrier breaks the phone, is it the original manufacturer's fault though?

Re: LineageOS Android Distribution

#93

Post by dylz »

_0ffh wrote: post #92
dylz wrote: post #80

Earlier quoted context omitted.

I've bought a handful of used HTC devices in the past. Only "real" HTC devices are go to dev page and unlock. If they've been through a carrier that isn't T-Mobile, it's very likely permanently not unlockable. Try entering a Verizon-issued HTC or Sprint-issued HTC on the page.

Yes, entirely possible (I wouldn't know, I'm not US based). When the carrier breaks the phone, is it the original manufacturer's fault though?

The carrier's contract with the manufacturer or something explicitly demands that the manufacturer not unlock the bootloader.

Re: LineageOS Android Distribution

#94

Post by thaumasiotes »

lucideer wrote: post #84
thaumasiotes wrote: post #62

Earlier quoted context omitted.

> The fact that this is an accepted norm is another part of the problem. Why "naturally"? Some manufacturers (like Google, Fairphone, Motorola on a limited number of phones) don't void the warranty, but even if none did: why do you think this "naturally" an acceptable thing other than it being the norm? Because I want to be allowed to install software that will damage the phone. Holding the phone manufacturer respons…

> Holding the phone manufacturer responsible for code I wrote is not in fact a natural thing to do. I'm sorry but I'm really struggling to understand what you mean by this. What hardware should I be running the code I write on without fear of voiding the warranty. If it's the fact I wrote the code that constitutes voiding the warranty, exactly who's code should we be permitted to run on hardware we've purchased? Only…

You shouldn't be running the code you write on any hardware without fear of voiding the warranty. The point of a general-purpose computer is that the code you write might do anything at all. There is no warranty to cover that, and there shouldn't be. You should get over your desire for a warranty.

Re: LineageOS Android Distribution

#95

Post by bythckr »

I just wish that LineageOS just picks couple of devices that they can support. So, me as a "not highly technical" user can just buy that specific device. The current at https://download.lineageos.org/ where they list every device is confusing and hard to track which is the phone most are working on. Pick one and work on it. With enough people using it, hardware makers will have a strong case to sell device that is "Lineage OS compliant" even if it's shipped with Android.

Like how GrapheneOS has focused on Pixel 2 and Pixel 2 XL.

Re: LineageOS Android Distribution

#96

Post by as1mov »

bythckr wrote: post #95

I just wish that LineageOS just picks couple of devices that they can support. So, me as a "not highly technical" user can just buy that specific device. The current at https://download.lineageos.org/ where they list every device is confusing and hard to track which is the phone most are working on. Pick one and work on it. With enough people using it, hardware makers will have a strong case to sell device that is "L…

Oh for the love of god please no. Please don't narrow down the focus on 1 or 2 high end devices and neglect the rest just because a small percentage of people can't be arsed to read the documentation.

LineageOS is an hacker/enthusiast thing, it will always remain niche regardless of how easy to use you make it.

Re: LineageOS Android Distribution

#97

Post by qplex »

correct_horse wrote: post #70
xwvvvvwx wrote: post #46

iPhone user here. Increasingly curious about Android. If I installed LineageOS on a pixel3a, how much information would be going to google by default? How easy is it to avoid google altogether?

If you want to have a working phone, you need google apps (Google Maps, Google Play Services (used for many apps' notifications, location, analytics, etc.), Google Play Store, YouTube app). The Open Gapps project packages these nicely for use with LineageOS, but installation is janky (download a .zip file, install it using TWRP). note: despite being called "open", Open Gapps are proprietary, but packaged using open s…

Or you could just install F-Droid.

I agree that most people probably need Google Play because the apps they use aren't available anywhere else.

But then again most people probably don't have the skills to install LineageOS to begin with.

Re: LineageOS Android Distribution

#98

Post by Macha »

thaumasiotes wrote: post #94
lucideer wrote: post #84

Earlier quoted context omitted.

> Holding the phone manufacturer responsible for code I wrote is not in fact a natural thing to do. I'm sorry but I'm really struggling to understand what you mean by this. What hardware should I be running the code I write on without fear of voiding the warranty. If it's the fact I wrote the code that constitutes voiding the warranty, exactly who's code should we be permitted to run on hardware we've purchased? Only…

You shouldn't be running the code you write on any hardware without fear of voiding the warranty. The point of a general-purpose computer is that the code you write might do anything at all. There is no warranty to cover that, and there shouldn't be. You should get over your desire for a warranty.

Why is this acceptable for the computers that go in our pockets when its clearly not the case for those that go in our backpacks or datacenters?

Re: LineageOS Android Distribution

#99

Post by wazoox »

ivanfon wrote: post #87
wazoox wrote: post #53

Earlier quoted context omitted.

The main missing part is a good maps/Waze equivalent. I don't need anything else that's not available on F-Droid. Now I'm a GNU/Linux user of strict observance (depends only on Free Software!), so I probably don't have the same requirements as most.

Have you tried OsmAnd? (and if you have, what are your thoughts?)

I didn't try it, but what I'll miss the most is traffic information (I live in a very crowded area with huge traffic jams).

Re: LineageOS Android Distribution

#100

Post by Avamander »

StavrosK wrote: post #88
phh wrote: post #79

Earlier quoted context omitted.

Becauses the cost of doing a CI of Android is astronomical. (Especially for students) For my own ROM [1] I spent days and a hundred of euros optimizing the cost of building by trying various cloud providers (fwiw my current best spot is scaleway GP instance with 600GB local SSD). As of today, I'm still at 6€ per builds (For standard ROM devs, that should be cut down to 2€ I'd say). There is simply no way I can afford…

What's the expensive bit? Can't you rent a server and build on that?

Sure you can, for 20+€/mo if you want your builds take less than a day. That's still astronomical for the enthusiasts compared to struggling to build on their own PCs.
Post reply on HN