Isn't it clear?@AndyYan Is there any explanation for why you only ship bvS/bgS ? Why not N ?
Why only pre-rooted builds which has no user functionality advantage ?
No one shouldn't be supposed to ship pre-rooted ROMs & GSIs. Root is a choice that has to be taken by users themselves. bvN/bgN builds give users chance to flash magisk upon their will. Pre-rooted builds slow that process down & give issues to newcomers. It's also against user's security.
I know about sas creator mate. My point isn't about difficulty. I myself created overlays that got merged in vendor before.Isn't it clear?
Waste of bandwidth?
That isn't ignorable. Magisk would still use su binary in the backend instead of it's own (which is the reason it shows conflict). Both binaries are completely different, even though they provide same usecase.
My ~400KB/s upload bandwidth would disagree, and I can't negotiate that due to where I live.
I'm pretty sure there had been more than one user in the past who voiced their objection to *Z citing its issues...
Tq for considering this mate.
Haven't thought of your specs btw. I had the same issues when I was building stuff for some devices. There are some large repositories that are common on all Android releases. They need to get symlinked. And ccache doesn't need to be on SSDs. Affordable way is to use hard drives, since read speeds are almost the same when data is stored sequentially.My ~400KB/s upload bandwidth would disagree, and I can't negotiate that due to where I live.
Likewise, my 1TB SSD juggling A12, A13 LOS, A13 AOSP sources plus their ccache would like to catch a breath. I don't request or live on donations, but I also lack an incentive to expand my storage further.
I can understand you andy, but as we know, that majority of the users are just lazy, so they prefer Magisk over any other script/procedure/solution...XD
I've tried the "--reference" feature of repo command back when I built both GSI and device-specific in separate workspaces - they used the exact same sources and it should've saved me almost all the space, but in the end the saving wasn't large enough as anticipated, and it got annoying to maintain when I wanted to move or delete one of them. I assume it'd get even messy if I cross-reference/symlink between Android versions or AOSP/LOS.
If it's so early that it's still only shared on Telegram (which I don't use), then that's probably still too early. haha
I have no mobile data/telephony problems on Israel. I think it is safe to try for you.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.