Lineage OS

Probably it is full of bugs..we have to wait at least 1 year to have a decent ROM.

>>58619628
Out of curiosity, CM13 did came with root access. How do you do it in Lineage? And no, Nexus 4 still does not have official build.

>>58619669
Flash supersu through TPRW (or whatever the fuck it's called)

>>58619663
their are literally using the CM codebase, it cannot be in worse state CM was when it was discontinued.

>>58619705
Hmm, but CM doesn't have that, it manages root access through Settings, like an application permission.

>>58619669
>not building it yourself

>>58619742
I don't know how :(

>>58619749
http://wiki.lineageos.org/mako_build.html

>>58619709
I know that but with new cpus (10 nm) it will be full of bugs..lineage OS is perfect for old smartphone not officially supported anymore but I don't think is very smart to change stock ROM in a new smartphone with lineage-one..

>>58619735
It's literally what everyone did before they baked it into the OS, and on all non-CMs.

It takes less than a minute as long as you've got TWRP installed which you should have already

They haven't released any builds for the moto x pure yet, but they've confirmed that it will be one of the devices getting nougat builds.

I'll probably flash as soon as they release.

>>58619709
The development didn't even stopped, there is a shit fucking ton of new commits every day.
I am currently using without any hassle on oneplus one and oneplus 3.

>>58619628
Are there even any official builds/releases yet?

>>58619793
>perfect
I don't know if I would call it that.
Android has always been a bad system.
It is the least bad system we currently have, but it is not even damn near acceptable.
1. you have compile stuff yourself, do the testing yourself and fix the OS yourself.
2. you cannot do the testing and compiling from the phone, so it will take a long time to do so.
3. It doesn't work for all phones, so if you do it for one phone, it will not work on other phones.

All this leads to a lot of wasted time and effort.
To make matters worse, the lifespan of phones are so low that making the OS compatible with a single phone is not a huge progress.
That phone is obsolete just a year, maybe two at most.

Lets compare this to the gnu/linux OS on the desktop.
There we can fix problems on the system we are using, while we are using it.
We can use the work of others, and speed up process by using build servers, so we don't have to compile everything.

It is like you only have the options of using red star and linux from scratch.
It is a joke.

>>58620309
>3. It doesn't work for all phones, so if you do it for one phone, it will not work on other phones.
fucking this, why can't smartphones be like normal computer where you install the OS you want and support/updates are offered by the OS's maintainer?

welp, building just failed with some out-of-memory error

File: unnamed.png (59KB, 300x300px) Image search: [Google]

59KB, 300x300px

>>58619628
>ripping off the nextcloud logo

File: og.jpg (39KB, 500x353px) Image search: [Google]

39KB, 500x353px

>>58620419
>ripping off the nextcloud logo ripping off the olympic games logo

>>58620309
I feel exactly the same, Android is the least shit mobile OS but it is still a fucking stinking pile of dogshit.
The day I will see an alternative I will jump ship immediately but I fear that that day will never come.

>>58620396
Mainly because if intel are a bunch of jew nigger Arm producers are way fucking worse.
Binary blobs riddled with bugs that will never be fixed, locking people to use a single kernel version, locked bootloader, 6 months of software support, etc.
We should really vote with our wallet and stop buying that shit.

>>58619628
Tried it yesterday, too broken for daily use, but I'm going to check it out again in a while

>>58620624
Where did you get the image from?

>>58620309
>>58620396
>>58620479
It's not like it's the OS's fault that you need a specific build for every different device. Developers can't do anything about the current (shitty) state ARM.

>>58620961
there https://download.lineageos.org/
or maybe he built one himself

>>58621038
Oh, so they have actually added some devices to that tab. Thanks.

>>58621008
>https://download.lineageos.org/
The OS shit anyway, 60 GB of source code just to compile a ~1 GB of binary files is fucking insane.

>>58621008
>Developers can't do anything about the current (shitty) state ARM.
You solve it by making a better structure.
Android is designed to be a single blob that cannot be changed.
This is a bad design when it comes to an OS.
When most of the drivers are proprietary, you would expect that you could at least get the binaries and run those from within the system to get access to special camera drivers and stuff like that.
>It's not like it's the OS's fault that you need a specific build for every different device.
Yes it is.

yeah i am using it and its shit

I don't have a computer powerful enough to build this

>>58619628
Gonna switch to it whenever my moto g4 plus stop receiving updates.

File: oc.jpg (12KB, 200x200px) Image search: [Google]

12KB, 200x200px

>>58620419
>>58620443
hi

>>58622173
As I'm also using a Moto G4 Plus I had to do a double-take after reading this, because apparently Nougat has already rolled out since ages ago, but my phone is still stuck on Marshmallow, and no updates are detected when searching manually. What gives?

>>58622388
>>58622173
G4 plus here, I gave up waiting for the official update and got the last cm build (12/24) before hearing about lineage.

>>58621314
>You solve it by making a better structure

Software developers cannot do anything about ARM SoC manufacturers producing stuff that require blobs to run, which locks these chips so a certain kernel version since software support on ARM is a fucking joke.

>Yes it is.

Good luck building a ROM that can run on devices which require vastly different blobs and kernels.

>>58622698
about that, how hard is to port a rom like this one to another device? where can I read something about it?

>>58622944
>how hard is to port a rom like this one to another device

It shouldn't be that hard if you are familiar with development and can actually find the required driver/blobs for your device.

http://archive.is/em0UZ

>>58622388
>>58622485
there is a nightly that was built today for you guys

https://download.lineageos.org/athene

>>58620297
I thought that they weren't bothering with releases anymore, just nightly snapshots. Cause you know devs, they love being bleeding edge and don't understand why those silly users want to install something that works and then leave it alone.

>>58620248
Are there any official downloads or do you compiled it yourself?

>>58623773
there were good reasons to do that, the fact that you believe they were stable is one of them.
Differently from desktop os there isn't a real update system on android, so to patch some ugly bug or security issue you have to update all the thing.
In others words android is never stable.

File: Screenshot_20170123-141042.png (162KB, 1080x1920px) Image search: [Google]

162KB, 1080x1920px

>>58619628
dirty flashed my hammerhead with 14.1 caf last week. so far totally stable and more responsive than I thought it was going to be.

>>58623929
I have a script compile it for me every night, I don't like downloading archives from xda or any other skiddies and curry infested places.
Your best best if you don't want compile it yourself is to get it from: https://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850
This gook is the official maintainer for oneplus 3, you can see his commit on github/gerrit.

>>58623986
>>58624016
Thenks anon, I will try these.

>>58624016
I've read that installing maven and gradle may speed up the building process, is that true?

>>58624045
*thanks

Custom ROMs degrade your security compared to stock because you are not getting Android security updates and are putting your trust in Indians doing it for free. The only ROM which actually brings an improvement in security is CopperheadOS with its privacy defaults, exploit mitigations and attack surface reduction.
>>58619793
Your point about newer phones stands, but the manufacturing process makes ZERO difference.
>>58624052
No.

>>58624052
I honestly don't know.
One thing I learned -the hard way- is that the following two environmental variables are a risk you don't wanna take:

export USE_CCACHE=1
prebuilts/misc/linux-x86/ccache/ccache -M 50G

While even google suggest to set them I find it not a very good idea because if for some reason the compilation process produces a non working binary it will be cached and used for the next build.
Always run

make clobber

before compiling and don't cache anything.

>>58624104
The fuck are you up to? lineageos/cm get android security patch, 5 jannuary 2017 is currently used.

>>58622009
Just leave it running overnight for a couple of weeks.

>>58624161
>The fuck are you up to? lineageos/cm get android security patch, 5 jannuary 2017 is currently used.
Friendly reminder that Motorola only does quarterly security patches, ie. 4 per year
Any curryOS is better security wise than the stock rom Motorola has, unless the curry has fucked around and left all kind of retarded settings/commits or abandoned his rom for 3+ months

>>58619628
already running an unofficial build, just waiting on an official build for my M8,

>>58624191
tl;dr; use lineage and not some shit downloaded from XDA and you are far more safe than with the custom ROM preinstalled with the phone

>>58619669
Linage dropped built in root for some reason. Use SuperSu now.

>>58624492
or you could wait a day and download the official su zip from lineageos

>>58624492
Probably due to the nowadays much more widespread use of SafetyNet

File: 1482691979897.jpg (171KB, 800x600px) Image search: [Google]

171KB, 800x600px

>>58619628
>Samsung section is just Galaxy S III variants

Fuck me for buying a phone made in the last 4 years. I want my S7 edge support.

>>58624492
It's not a bad idea to not include root by default.
Certain apps don't run if they find the phone is rooted.

>no screens in the thread
>look up their site
>nothing their either
>youtube Lineage OS
>every video is by some indian

fucking pass.

>>58624771
The fuck do you think it looks like? Google CM screenshots you retard.

>>58624785
I think some people are able to distinguish an os from another only from the UI

>>58624815
I wanna see the guy who does that with the fucking identical looking homescreens/appdrawers from CM14.1 and Lineage 14.1.

>>58624161
Hobbyist Indians do not have security as a priority, and they most likely don't know too much about security either.
>>58624275
Except for Nexuses/Pixels, and most likely popular models from the big manufacturers (apart from Motorola, apparently). Custom ROMs other than CopperheadOS invariably give you decreased security.
>>58624492
SuperSU is proprietary. I wouldn't trust it as the gatekeeper for the capability that can wreck your phone and widens your attack surface MASSIVELY.

>>58624887
>Except for Nexuses/Pixels, and most likely popular models from the big manufacturers (apart from Motorola, apparently). Custom ROMs other than CopperheadOS invariably give you decreased security.

why? you said that you don't get the android security updates, but that just not true

>>58624550
Stop buying Samsung. It's like you want to be cucked.

My Wileyfox Swift was made in the last year, and supports LineageOS. Same for my friend's Redmi Note 3, and my brother's OnePlus One.

>>58624104
Security is a meme distraction since it's cool to not have privacy.

>>58625090
why is samsung so bad?
>shit software
>shit support
>sometimes shit hardware
>exploding phones
>exploding washing machines
>crashing koreans's governments

>>58624911
Do you trust Lineage developers, amateurs with little to no security knowledge to be able to harden the operating system? I certainly don't trust them. Doesn't matter if you get Android security rollups, if you opened up a security hole that isn't covered by the bulletin it doesn't matter.
Here's another thing: CyanogenMod and most likely Lineage don't do any signature verification and don't enforce checking the hash of the update package leaving users open to malware being bundled with the package they downloaded that masqueraded as the official package thanks to MITM, or Lineage server compromise.
>58625186
fuck off!

when the hamburger goes to me the finland for hemorrhoids and 45 rrmmmmmmmdd sudo burger

>>58624887
That's just not true.
For example CM got security fix for stagefright way way before every official ROM from manufacturers.

>>58619896
Moto X Pure runs better on stock rom though. The best roms were based or just altered stock roms. The community for the device is horrible. OnePlus is the new Nexus post Nexus 4. Community puts out decent roms and is more robust. The OPO for example still has some of the best roms. Doesn't hurt that the device still runs like a fresh set of titties.

>>58625343
That was before Google's initiative for universal security rollups necessitated by Stagefright. Still, the base operating system has far less scrutiny than Google takes or manufacturers take.

>>58625278
You can always use AOSP, or copperheadOS if you have the right phone.
They do signature verification and mitm can happen on any phone.
Just use a dumb phone so you don't have to worry about mitm/compromised servers.

>>58625278
>Do you trust Lineage developers, amateurs with little to no security knowledge to be able to harden the operating system?
not amateurs, and why do you think they have no security knowledge?

>Doesn't matter if you get Android security rollups, if you opened up a security hole that isn't covered by the bulletin it doesn't matter.
according to this logic, every fork is bad

>Here's another thing: CyanogenMod and most likely Lineage don't do any signature verification and don't enforce checking the hash of the update package leaving users open to malware being bundled with the package they downloaded that masqueraded as the official package thanks to MITM, or Lineage server compromise.
again not true:
http://lineageos.org/Update-and-Build-Prep/
>Our official builds will all be signed with a private key for authentication and signature permission control

> This will not break, prevent or stop any ‘unofficial’ builds.
> Key verification info can be found on the wiki Verifying Build Authenticity page

>>58625401
And you still have to wait for _Samsung_ to bake the update and ship an update to you.
Good luck with that.

>>58625414
>not amateurs
Where's the income? Vast majority of CM devs are Indians.
Yes, almost every ROM gives you a net loss in security.
Pleased to have been proven wrong on Lineage signature verification.
>>58625433
Point still stands on security competence.

>>58625278
Literally everything is this post is easily falsified bullshit.

0/10 troll harder

Waiting for klte.

>>58625562
0/10 post. Present an actual argument rather than relying on your assumptions that fucking Indian hobbyists are infallible.

>>58622296
>abstract iconography of dev balls over a night table, were they leave them before going to work or doing anything
pottery

>>58625598
Stop replying to this fucking retard.

>>58625524
It's open source, everyone can co tribute and there are core developers check what other people pull, it's like any other open source project.

>>58625524
Lineage is a community driven opensource project, this doesn't mean the developers working on it are incompetent.
And I suppose some of the devs may be indian, so what? the 20th director of darpa was indian too. Do you have any proof of bad code or practice in their code?

>58625620
>ideology man.jpeg
>>58625625
>>58625680
Sorry, the key word was hobbyist.

>>58625524
Android and iOS are just one big hole, doesn't matter if the OS is "secure" because the software will have vulns.
In fact there is only one that tries to set it's goal on security first and that is CopperheadOS.

File: 20170123_184251.jpg (3MB, 4608x2592px) Image search: [Google]

3MB, 4608x2592px

Booting up for the first time :')


Sorry for sjitty pic. Taken on my old phone

>>58624016
Thanks man, its working perfectly

Any reason why I should switch from Resurrection Remix? It's so comfy

>there's people ITT who believe in the (((enterprise))) """"security"""" model
topfuckingkek

>>58626020
How's it treating you? Just installed on my OnePlus and seems to be working great so far.

I only have a ecot computer and android tablet . I want to use the ecot computer but every thing is blocked . I was looking for a way around this so i could eventually reset the os completely and it work like a normal computer. It been hard as ,right clicking is blocked, installing need admin passcode,cmd is blocked . I was thinking that the only way i may be able to get into this would be if i boot of a thumb drive , which doesnt seemed to be blocked as far as i can tell . All i have is a android tablet to do it on tho . And i cant physcially plug the usb into this tablet. Is it possible to do it threw the tablet then plug the usb and tablet into the computer and transfer it to the usb ? Its kinda a long shot but only option i really see .If anyone could help or suggest somewhere i could ask for help ,that would be great . Also if there are any other ways you could think of going about this feel free to give input. I have tried normal ways such as safe mode ... ect. The os is windows 7 pro, and the tower says thinkcentre intel pentuium ,think centra sn mjd11250

>>58626873
It's pretty decent. I really want root back though

alright, just installed it on my moto x pure.

Install was fast and I flashed superuser 2.79 along with opengapps pico and everything worked.

Too early to tell how the battery is, but assuming that the doze on the go feature works properly I'm expecting a pretty noticeable increase in battery life.
DPI switcher is nice though.

>>58622944
In my experience the main problem is the lack of decent documentation. It'd already be a huge step forward if someone just made a blog post describing porting to a particular device.

>>58619628
>no Nexus 5 support
Yeah, I know the phone is old. But I was hoping that they carried over the official builds for the device.

Guess I'll have to flash PureNexus again.

>>58619628

I'm on CM14.1 with my trusty Galaxy S III and I certainly will.

>>58630091
Nexus 5 is coming, just wait a few days.

>>58628925
I completely agree with you, the biggest problem of the whole android community is the lack of decently written and maintained guides.

>>58624550

Just go to S7 Edge development on XDA an download the Lineage or resurrection remix, dumb frogposter.

>>58619749
Why does your gender matter?

File: 8718dae404aaee8671c5ce57c302721d9df58b61aa332ae768adc34bb1573e77.jpg (33KB, 281x473px) Image search: [Google]

33KB, 281x473px

No HTC m7 support yet. No guide to build it either.

File: Screenshot_20170124-105044.png (75KB, 720x1280px) Image search: [Google]

75KB, 720x1280px

>>58619628
I do anon but it is first custom rom maded for my phone and it still needs a lot of work. Dev is very good at what he does because huawei didn't shared source code and he writes thinhs by himself

>>58630695
shit nigga time to upgrade, I couldn't even find a decent rom for marshmallow (that was stable, all of them were fast but almost none of them stable unless it was some rom that was insanely different from stock) and stuck with stock rom 5.1.1 with some tweaks here and there, said fuck it and moved over to a moto g4+ until I picked up a htc 10

>>58631150
I would like to upgrade hardware but I can't afford doing so at the moment. The m7 works just okay enough to justify no upgrade as well.

>>58630675
s/he wants anon's dicks (beware, it's probably a trap)

File: Screenshot_20170124-135825.png (165KB, 1440x2560px) Image search: [Google]

165KB, 1440x2560px

Installed it last night because I wanted to try f2fs. AMA

>>58631652
did you wipe or just flashed it over the old rom?

>>58631947
You can flash it over CM14.1

>>58631947
Clean flashed. Changing to f2fs requires a format anyway.

>>58632144
and are you happy with f2fs?

File: 20170124_143127.png (30KB, 637x283px) Image search: [Google]

30KB, 637x283px

shit keep failing, any tip?

>>58632167
Can't say yet. I ran androbench before and after changing and the results were the same. I haven't noticed any difference in normal usage either. My old nexus 5 felt noticeably snappier when I switched to f2fs.

>>58632316
I suspect it could be failing because jack does not have enough RAM.
Specify the amount of memory to allocate with "-Xmx4096m" instead of "-Xmx4G" you are currently using.
New version of jack switched from gigabyte to megabyte for the Xmx option.

>>58632981
thanks, I will try to do that

>>58619628
Does the Z3 compact have one yet?

>>58619705
Are we seriously stuck with supersu instead of something open source now?

>>58633532
Just compile lineageos by yourself and set this environmental variable

export WITH_SU=true

>>58619628
>No support for Xperia Z2/Z5
Dropped

Is it gud on Moto X 2014?

>>58635029
It's pretty much cyanogenmod, if that worked fine, and it most likely did, this will too.

>>58635161
I don't know the state of CyanogenMod on the Moto X 2014.
Been using the default ROM since I bought it, just thought of trying a custom to get 7.1.1.

But loosing the Active Display function is painful.

>>58635205
CM/Lineage have some Active Display functions, and if your phone has an AMOLED screen (I believe it does) they should work more or less the same as stock.

So, you can always try it. For that I advise that the first thing you learn before fiddling with any Android device is how to recover from total disaster (bootloop, unstable system, corrupted recovery or any other kind of soft bricks...) to a stock ROM. The XDA subforum for your phone should have all the info you need. If Pajeet can do it, so can you.

>>58635513
Thanks dude, I'll read about and maybe give it a try.

I'm waiting for the Nexus 6 build to be up. Last time I checked all that was there in the Google section was the 6P and 5X.

>>58632981
ok apparently i had to manually set $JAVA_HOME in my distro.
Now I keep getting out of memory errors, no matter if I use GB or MB, I also tried to lower that value but nothing, it keep eating all the available ram (~7 Gb)

>>58636621
What distro are you using?
Jewgle and all the pajets on XDA suggest ubuntu, I use Fedora and it works fine as well.
On an unrelated note, check that /tmp is not mounted on a tmpfs ramdisk because the build process stores some temporary files there, if there is not enough space left no errors are thrown but the zip will contain corrupted data.