danger/u/
This thread is permanently archived
LineageOS

| I ruined my previous phone with CyanogenMod, now I feel skeptical about doing it again. My 2016(?) phone is running fine atm, but apparently they upgraded SSL(?) and makes every android versions below 5.0 obsolete. Mine's 5.1 but is somehow affected due to COMODO certificate expiring or whatever.

Long story short, is Lineage OS decent or would I be better off getting a cheap android 9.0 phone?


| before i just stopped using phones i had stock AOSP it was rly nice and genuently made every phone i put it on run way better


| Stock Android is nice, but if you can't update to newer Android lineage is probably a good choice since free with some security improvements, but really you should just get a new phone soon


| specifically when you're that far back, you should definitely get a new phone

I'm 5 releases ahead of you and I'm sure that's not great for security or app compatibility


| >>679627 I dislike your mindset. Just getting a new phone is a crappy attitude, like seriously. Phones aren't exactly cheap, you know? And OP doesn't sound like he wants to spend money anyway. Long story short² - custom ROM like Lineage and you should be fine! I'm running a custom rom on my Nexus 10 tablet. Made in glorious 2012, still perfectly useable. Running Android 8.1 atm.


| >>679576
If you're going custom, Lineage is a safe bet, but there are ROMs that can be plenty better than LOS (i.e, those based off of AOSP). Sometimes LOS and LOS-based ROMs are the only choice though, and when that's the case it's just feature & maintainer differences that sets them apart.


| >>679794 >>679798
I wouldn't mind getting custom ROM if they don't have the tendency to break connectivities (wifi, bt, phone) or sensors and sometimes cause overheat. I haven't really done a proper research but from what I've found with my phone model it seems that wifi didn't work with LOS unless I first flash an older custom ROM that is 3 major versions behind which is a lot of work.


| >>679830
That being said I appreciate the push. I'll consider it on the note that if it bricks my phone then I'd at least have an excuse to spend on a new one.


| >>679830
What phone is this? Only phones with problematic SoCs tend to exhibit strange, awful issues (Exynos, Kirin...) or phones with device tree that is made with lots of reverse engineering (as with most Chinese Qualcomm devices).

Devices like the Nexus or devices with proper development support tend to have custom ROM with the same quality as the stock ROM (or worse, but not by a huge margin).


| >>679834
A Chinese Qualcomm device (oppo f1)

I can't name a SoC that you don't list as problematic lol. For a list that starts with "only" that seems to be a very inclusive list.

Anyway I'm gonna attempt bricking my phone. Gonna be fun.


| progress update,

lineageOS won't boot, I think I'm retarted

on the bright side, apparently there exist an official AOSP build for my phone. it's 6.0 but it's working and I just gotta live with it for now.

now the reason that I was retarted is that I think I was supposed to flash this official AOSP first, but for now I don't feel like trying again (battery status seems to be broken on LOS according to several people)


| I mean, it might not be Pie, but it's AOSP!! it's fresh and clean looking!! I'm so excited :D


| >>679794 well ideally phone manufactures would support their phones longer but this is Android we're talking about, even Apple does better than some phones in this space


| >>1fe961 what the shit, you can load a custom rom on your oppo? damn gg man. Fuck vivo, man, i cant find any roms for this mfer v7+


| >>679895
It depends on your phone's development support and how willing your OEMs are at giving you the source codes needed to build one. I don't trust Chinese brands (and hell, even Samsung) with doing this, and custom ROMs (and even custom kernels) support is scarce for them.


| >>679895
technically it's official rom, but you know what, actually getting official aosp rom is even sicker so yeah, fuck vivo. but wait, oppo dropped the aosp project in 2017 so fuck oppo too.

>>679903
what phone brands do you reckon has decent development support? aside from google that is.


| >>679863
I should retract the 'Chinese Qualcomm' part here, but the list of 'good' and aftermarket-ready phones is such a small list that it's difficult to not be inclusive.

Re: AOSP, I don't know why people would use AOSP, but it IS cleaner than OEM stocks. If you don't mind listing your installation steps for LOS, I think I can help you (with the limited knowledge I have with Oppo; I never held one aside from that CM-edition Oppo phone).


| >>679905
Naming a few: OnePlus, Pocophone, Xiaomi/Redmi (but only in the mid and higher ends; lower ends tend to be scrubbed with device tree issues), Moto, HTC to a degree, Sony (if they can fix their stupid DRM), ASUS (Qualcomm-only).

Most devices shipped with Android 8.0 have the ability to install custom ROMs through Project Treble, but these 'generic' images (as in, one-for-many images) tend to perform less optimally than specific images.


| Project Treble is also how most Treble-supported devices are able to run Android R (a pre-release, developer preview system) early, without being a Google phone.

But again, devices with ONLY Project Treble ROMs (see: Huawei, Samsung) tend to have ROMs with subpar performance and stability. This is because you can't tweak much of the device tree to perform 'just right' on the device, as the ROM has to account for many variations.


| You should eventually buy a new new phone anyway, since yours doesn't receive firmware security updates anymore. Also check out grapheneos


| >>679914
> Not that Oppo ever releases actual firmware updates with meaningful CVEs fixed anyway


| >>679907
I don't have any special reasons for using aosp. If anything, I hate oppo's default emoji probably. The main reason for me to upgrade was the SSL problem I mentioned which prevented specific apps from connecting to the internet, and now that I'm on Marshmallow these apps are working for now. So personally I'm not always interested in customization, only when I have practical reasons to.

Also I appreciate the offer, though I might not reattempt installing LOS soon. (1/2)


| Because of the glitchy battery status problem that I heard.

Though I don't mind listing my steps anyway. Basically I already had TWRP 3.2.3 installed a long time ago because I wanted root access (magisk). At this point I still have ColorOS. I simply did a wipe -> flash of the latest official LOS build for my phone, won't boot, then tried format -> flash, now TWRP said OS not found. Then I flashed Project Spectrum 0.2 and it works. (2/2)


| Maybe I should mention this as well since it's probably important: after flashing Project Spectrum TWRP is completely gone, or rather I can't boot into recovery anymore so there's that :p


| >>679917
I can't read, it was Project Spectrum 1.0 beta. My bad.

>>679914
I'm not security savvy so security isn't usually my main reason for buying a new phone (it's usually compatibility issue). This Project Treble thing >>f1ff1c mentioned sure sounds neat though.


| >>f1ff1c I only started diving into the workings of OEMs after a few months buying this thing (this is my first smartphone) definitely will be looking into longevity and custom rom support in my future pick, ill ride this thing till it dies

>>1fe961 fuck vivo (2)
It extra shitty too because Oneplus is basically oppo and vivo on a higher stage and theres roms everywhere for em


| >>679974
The main difference being OnePlus is WAY more open with their sources, giving developers over at XDA free phones to make sure custom ROMs and kernels are ready on day one (or week one) of the phone's launch.

But yes, they're all from the same parent company. They shill to a different audience.

Good luck on your future phones. Note that Google is kneecapping custom ROMs with SafetyNet nowadays. It's getting difficult to modify anything at all.


| >>679917
Have you tried older nightlies? I've never built anything for the device, so I don't know how the device sources are (stability-wise), but if it's in Nightly, there's usually an active maintainer looking out for issues (especially if it concerns the image not booting).

Re: TWRP, you can just reflash it back. There's a chance Spectrum wiped the recovery partition (seeing that it's the only way to also unlock the phone). Shouldn't harm you much.


| >>679984 Thanks for the tip man, I appreciate you


| >>680004
glhf Android is becoming more like a walled garden every release nowadays. Might as well enjoy the freedom while it lasts.

Total number of posts: 30, last modified on: Fri Jan 1 00:00:00 1594913560

This thread is permanently archived