[ROM][6.0.1] LineageOS 13.0

[osm0sis]

Sorry I didn't know that such a modification is already available. But your solution is really great! Two questions: Do your mod persist a /system wipe? And in which location do I have to save my pngs that the script can find it?

You supply the location as an argument on the command-line, so wherever, but /sdcard would be logical. Yes, the modifications are to the bootloader's sbl partition, so they survive a full wipe, and also for that reason should be done with care. I've made every precaution I could in my scripting to prevent a corrupt bootloader, but recognize that the potential is there and you make such mods at your own risk.

It does not survive a bootloader flash, naturally, and coexists nicely with RePIT. It also requires JPEGs because that's what Google/Samsung used. Closely read and follow my instructions in my linked logohack posts in that thread to know how to properly prepare the images to be used in the script.

 

[Childe89]

Hello, I´m not using this phone much anymore, just as backup device, but flashed newest nightly and It´s nice to see this device is still supported And how much RAM was made available since the first Lollipop builds
Everything I tried worked in last nightly, except minor problem in Camera - switching between main and front cameras closes Camera app, so you have to reopen app after each switch - but I suppose It´s RAM allocation issue, and more free ram is worth it But might be on my side also, because my device performance is suffering by very slow eMMC (famous V3U00M) and fstrim just makes it a bit better, so It´s usable (that´s also the reason I switched to different device)

 

[LeoHart]

Can someone explain me, why I get an error 4 in TWRP if I flash the su(arm).zip from the LineageOS page?

 

[Android-Andi]

Can someone explain me, why I get an error 4 in TWRP if I flash the su(arm).zip from the LineageOS page?

Lineage Team knows about it and had it fixed, idk why they never made it public. I compiled one from source myself, link in OP.

 

[MrFlashGame]

Hey folks,
I've found another bug in the newest LOS nightly: If I hear music and turn the display off and turn it on again and want to take a photo over the lockscreen while the music still runs the music stucks and I have to jump over to the next song to fix this bug. I hope this gets fixed soon even it's a small bug.

Greetings, Nils

 

[nailyk]

IIRC someone here recently bought a maguro to dev on it.
Can this person share me his github/gerrit account?
I would like to start working on 14.1 for maguro with the actual dev community.
Thanks in advance.

 

[Android-Andi]

@nailyk github.com/andi34 , but i don't think lineage and roms based on lineage are the best places for non QCOM devices anymore. Things changed a lot within last years... It happens quite more often you need to fix bugs introduced by CAF which aren't ifdefed properly... And if you find the broken bits you will have a lot of fun explaining what and why you are fixing it before it get merged (if it ever gets merged). Atm i think UA is the best place to work on.

 

[nailyk]

@nailyk github.com/andi34 , but i don't think lineage and roms based on lineage are the best places for non QCOM devices anymore. Things changed a lot within last years... It happens quite more often you need to fix bugs introduced by CAF which aren't ifdefed properly... And if you find the broken bits you will have a lot of fun explaining what and why you are fixing it before it get merged (if it ever gets merged). Atm i think UA is the best place to work on.

Thanks!
UA?
I recently talk with the SII maintainer. They have some pending changes (maybe merged now) for our/their soc and they are running 14.1 onto it. (cannot find the gerrit link right now)
I have big hope it will works.
Also I still have this link: https://zeelogkang.blogspot.fr/ where there are some 14.1 builds

 

[Android-Andi]

UA = Unlegacy Android.

Time is the most killer for me atm, still need to replace my LG G4 asap because i lost all my data twice in a short time (known official problem with bootloop on that phone... And it'll be back sooner or later...) and still need to find a part time job.

On lineage it took a while to bring the common omap4 hw repo almost inline with the stuff our omap4 team brought to us... And still it's missing tuna support in some parts which makes maintaining unneeded complicated.

Another killer on official Lineage for tuna: i am quite sure they won't accept unified builds

 

[Android-Andi]

@nailyk btw i think you mean the exynos4 Galaxy S2 (i9100)? The omap Galaxy S2 (i9100g) isn't worked on anymore afaik, at least no one actively working together with us and i haven't heared from that device since kitkat/ beginn of lollipop (?).

 

[Deleted member 2044343]

...

Another killer on official Lineage for tuna: i am quite sure they won't accept unified builds

I don't think unified would be a problem for Lineage, for example LineageOS for OnePlus 3 and 3t is a unified build for both too

 

[nailyk]

I don't think unified would be a problem for Lineage, for example LineageOS for OnePlus 3 and 3t is a unified build for both too

@nailyk btw i think you mean the exynos4 Galaxy S2 (i9100)? The omap Galaxy S2 (i9100g) isn't worked on anymore afaik, at least no one actively working together with us and i haven't heared from that device since kitkat/ beginn of lollipop (?).

UA = Unlegacy Android.

Time is the most killer for me atm, still need to replace my LG G4 asap because i lost all my data twice in a short time (known official problem with bootloop on that phone... And it'll be back sooner or later...) and still need to find a part time job.

On lineage it took a while to bring the common omap4 hw repo almost inline with the stuff our omap4 team brought to us... And still it's missing tuna support in some parts which makes maintaining unneeded complicated.

Another killer on official Lineage for tuna: i am quite sure they won't accept unified builds

Thanks for the anwsers.
Yes unified trees are good. We^wThey are bringinup shinano (xperia z2,z3 and variant) with a 'unified' tree and the official is on the go.
Yes I would say the 'g' one, because, afaik, it is the same soc as us.
I remember seeing that huge framework commit, with some #ifdef tuna. Into the comment they said everything is fine but didnot test maguro.
I will try to highlight the old maintainer ( @doriandiaconu ) on irc, maybe he can share me the link again.
Will start looking at all of this the coming week.

Also I think 14.1 will be good as many 'low-ram-device' users (~1Go) report smoothest device on N than M.
Am really not an expert so will try to paste what I find here.

 

[____Mdd]

@nailyk @Android-Andi
You can also talk to "Motorola Droid Razr" community.. they got RR-N and AICP and Lineage as well.. that also has omap4430..
See here: https://xdaforums.com/droid-razr/development

On my another device, Moto G4 plus, that's also unified and has official support from most of ROMs, you can give it a try.. best of luck..:good:

 

[bamtan2]

I would like to start working on 14.1 for maguro with the actual dev community.
Thanks in advance.

Thank you for this nailyk! We have had many good and generous developers come through this community, and it is crucial that we all welcome new developers who will take the place of those who have departed!

In my experience CM12.1 is the most stable and performant recent version of android for this device. I believe this is because it received the most attention from the largest group of developers for the longest period of time. It would be a real achievement for someone to bring UA or LOS14 up to the same quality standard.

 

[nailyk]

Thank you for this nailyk! We have had many good and generous developers come through this community, and it is crucial that we all welcome new developers who will take the place of those who have departed!

In my experience CM12.1 is the most stable and performant recent version of android for this device. I believe this is because it received the most attention from the largest group of developers for the longest period of time. It would be a real achievement for someone to bring UA or LOS14 up to the same quality standard.

Thanks for your encouragements.
I know am not skilled enough to make something as good as the 12.1 but will do my test to help the devs.
AFAIK there is another N rom for maguro, maybe it can help us.

 

[____Mdd]

AFAIK there is another N rom for maguro, maybe it can help us.

Yes there is but for tuna (unified), DU, SAOSP and Pure Nexus.. they are based on AOSP (UA) , by yuuji, he post on google+ , read here: https://xdaforums.com/showpost.php?p=69354816&postcount=16

Slim7 by android-andy also..

 

[guest4711]

Yes there is but for tuna (unified), DU, SAOSP and Pure Nexus.. they are based on AOSP (UA) , by yuuji, he post on google+ , read here: https://xdaforums.com/showpost.php?p=69354816&postcount=16
Slim7 by android-andy also..

And LineageOS 14.1 unofficial (unified), see
http://zeelogkang.blogspot.com

 

[Android-Andi]

Let's leave this here as it's a topic here and there now:

https://www.lineageos.org/Safetynet/

 

[Android-Andi]

AnyKernel for maguro, toro and toroplus attached. Adresses the following CVE & LVT:

• CVE-2016-9794
• CVE-2016-9793
• CVE-2016-9754
• CVE-2016-8655
• CVE-2016-7915
• CVE-2016-7911
• CVE-2016-7910
• CVE-2016-6786-CVE-2016-6787
• CVE-2016-6136
• CVE-2016-2184
• CVE-2016-1583
• CVE-2016-10208
• CVE-2016-10088
• CVE-2016-10044
• CVE-2015-8966
• CVE-2015-8963
• CVE-2015-8962
• CVE-2015-8019
• CVE-2015-8019
• CVE-2014-9420
• LVT-2017-0001
• LVT-2017-0002

The LVT commits are an workaround/fix for an Lineage SU vulnerability because it is not fixed in su source yet.

Attached AnyKernel should work on all roms from 4.4 up to 7.1 (only kitkat has an own kernel config and that's why there's an seperate zip attached) - it is not specific for LineageOS.

All mentioned CVE and LVT commits can be found on LineageOS gerrit.

 

[guest4711]

Attached AnyKernel should work on all roms from 4.4 up to 7.1 (only kitkat has an own kernel config and that's why there's an seperate zip attached) - it is not specific for LineageOS.

Thank you Andi. I'm just testing your kernel on LOS 14.1 and it's looking good so far... :good::good: