[GSI][12] LineageOS 19.x GSI (A64B/64B)

[Novhytha]

why i cant pass safetynet even its securized?
i was changed ro.control_privapp_permissions to enforce but it cant helped

but i can pass safetynet in phh gsi,
any way to fix safetynet in this gsi?

 

[Deleted member 12251071]

does anyone have a memory leak in surfaceflinger?

I have also a memory leak in "system_server", i must restart my phone everyday to mitigate this issue

Same here.

But there's a fix for this issue:

Fix memory leak on "Try to fallback mCallingSid to getpidcon" by diogotcorreia · Pull Request #4 · phhusson/platform_frameworks_native

Also fixes styling to stay consistent with the rest of the file. Fixes issue phhusson/treble_experimentations#2410 Commit 53b95fc introduced this memory leak.

github.com

cc @AndyYan

It looks like next builds will be LineageOS 20.

 

[nisfta]

I installed the GSI via DSU loader, but there is no MAC randomization (even with 'Wi-Fi non-persistent MAC randomization' turned on). Will randomization work if I flash the GSI the proper way (through recovery)?

 

[Virteal]

Hello, after flashing Lineage OS 19.1 20220912 arm64_bgS on my Doogee S68Pro my sim is not working. When I tried version 18.1 a long time ago, I couldn't make calls, only receive calls. In version 17.1 everything always worked for me without any problem. Do you have any solution? I wouldn't mind if, for example, the bluetooth didn't work, but if the sim doesn't work, it's a big problem especially with a mobile phone. Thanks

 

[MPK99]

@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.

 

[Deleted member 12251071]

@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.

Isn't it clear?

From https://github.com/AndyCGYan/lineage_build_unified

Note: VNDKLite and Secure targets are generated from built images instead of source-built - refer to sas-creator.

Generate secure targets isn't difficult and only take a few minutes.

Also,
GSI is not a device-specific custom ROM.
Users should not assume that this rom is perfect.
We (users) need to create overlays and/or make changes and we need to test it.
For that we (users) need root and the ability to remount partitions.

 

[AltairFR]

Andy perhaps you can add eremitein patch to support dynamic root

 

[MPK99]

Isn't it clear?

From https://github.com/AndyCGYan/lineage_build_unified

I know about sas creator mate. My point isn't about difficulty. I myself created overlays that got merged in vendor before.
I wanna know what made Andy decide to ship only bvS/bgS bydefault (on his sourceforge).
SU from bvS/bgS is simply unusable & has no applicable advantage to any user. Manually flashing Magisk is currently a root standard & works perfectly on non root builds out of the box (I know Magisk discussion isn't preferred in GSI threads. But it's truth)
For every update, one wouldn't always execute sas creator, it's already another step overhead on top of installation. bvN will ease that, is all what I'm saying.
Every other GSI dev provides non root builds, except Andy, which seemd so strange.

 

[Deleted member 12251071]

SU from bvS/bgS is simply unusable & has no applicable advantage to any user. Manually flashing Magisk is currently a root standard & works perfectly on non root builds out of the box (I know Magisk discussion isn't preferred in GSI threads. But it's truth)

Just ignore that.

Every other GSI dev provides non root builds, except Andy, which seemd so strange.

Waste of bandwidth?

 

[MPK99]

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.
It ain't that hard for a single dev to spare couple more builds to upload. Caz thousands of users gonna save their time by not sas creating non root builds on every update.
You're literally saving thousands of collective minutes of all users by just uploading couple more builds.
It's not a waste of bandwidth, right now it's a waste of time.

 

[AndyYan]

@MPK99 Building *N is a community concensus (vote) made back in A10 days. You made some good points, so I'm opening a vote once again, however I should also rebut some of them:

SU from bvS/bgS is simply unusable & has no applicable advantage to any user.

• It's /system-based and therefore works unconditionally even on devices that don't play well with Magisk (notably, Samsung).
• It's simple and "just works", like any pre-Magisk-era root manager. Pushing files, running root commands from apps (not just adb shell), etc. Call me an old timer, but I don't need Magisk modules.
• It also serves to enhance debugging or recovering from bootloop situations, though this is admittedly less of a user advantage.

It ain't that hard for a single dev to spare couple more builds to upload.

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.

Andy perhaps you can add eremitein patch to support dynamic root

I'm pretty sure there had been more than one user in the past who voiced their objection to *Z citing its issues...

 

[MPK99]

@MPK99 Building *N is a community concensus (vote) made back in A10 days. You made some good points, so I'm opening a vote once again, however I should also rebut some of them:

Tq for considering this mate.

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.

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.

Call me an old timer, but I don't need Magisk modules

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

 

[AndyYan]

XDA doesn't seem to allow creating a new poll over the existing, so here it is hosted off-site: SU poll (2022)

I doubt that I actually have thousands of active users, let alone who checks XDA, but hey, let's hear it! It'll be open for roughly a week from now.

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.

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.

I work and play on a single laptop that has respectable specs but (by nature) limited expansion - no HDD slot, both SSD slots occupied. Heck, I now rely on a small external SSD over USB to contain occasional non-current sources such as TWRP. Maybe A14 will break this fragile storage balance again and force me to migrate to a bigger SSD...

 

[SeventhRaven]

Any news on A13 builds for this? Apologies if I missed a post, haven't seen anything in the OP.

 

[mikefnz]

Any news on A13 builds for this? Apologies if I missed a post, haven't seen anything in the OP.

 

[mikefnz]

There is an early alpha on Telegram. Search under GSI's Trebble project.

 

[SeventhRaven]

There is an early alpha on Telegram. Search under GSI's Trebble project.

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
Thanks for the information, though. Suppose that means it's not that much longer.

 

[Dragorius]

First thanks to the great work. I flashed a a600f with the GSI, new Vendor and new Kernel. It is running fine. But I cannot pass any saftynet checks and of course not the google play certification. I tried a lot. Shortly also with Magisk, safetynet fix, MagiskHidePropsConf (with original fingerprint from the a600f) and busybox it will not pass basic and cts check. I tried to remove the prebuild SU but without success. So for me it will be interest to get a lineage-19.1-2022xxyy-UNOFFICIAL-a64_bgN-vndklite (or bvN) version to test, if the problem will be the buildin SU or something else.

 

[ChristianWS]

Using this on Redmi Note 10, working pretty good, but...

Double tap to wake isn't working, and I can't seem to find it, is it normal? I thought LOS had this option as long as it was supported by the firmware, is there a difference because it is GSI?

Another thing is that the device fingerprint is on the power button. I know LineageOS has an option to disable wake and unlock but again, I didn't find it.

 

[Crrrr]

Hello, I tried to do a clean install of your LineageOS 19.x GSI on my Samsung A20e, but it did not boot in the system after instalantion. It is weird, as I remember than one of your earlier versions worked just fine and the previous LineageOS 18.x GSI works fines as well.

Am I missing something?

PS: Samsung did a recent firmware update regarding their Knox.