yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
baseball game MLB 9 innings 22 doesnt work on my Cubot king kong mini2 and xiaomi redmi 8a for the rest everything works as far as i could see om a A64 gsi
[Treble-Enabled Device Development A/AB ROMS] tosiaczus:
I have broken screen and I'm trying to enable sound and turn off alarms and shut down the phone.

Can anyone share screenshot of

clock app pages first page and alarms list

volume control

and power menu
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
use something like https://github.com/Genymobile/scrcpy
[Treble-Enabled Device Development A/AB ROMS] lord_stoner:
Thanks Andy for the good work.

I have one question : Why is the Call recording missing in the Lineage Phone (Dialer)? How can it be fixed or started?
[Treble-Enabled Device Development A/AB ROMS] emperor_N:
Successfully booted this GSI on my Infinix S4 (X626B).

Specs:

Helio P22

6/64 Variant

Originally runs pie (stock)

I used the arm64 bvS build from June 2022.

Flashed Nikgapps Core for Android 12.1

Everything works and the battery life has heavily improved. I'm now getting a 7 - 8h SOT on a 4000mAh battery. WTF 😳

Observed bugs: Calls were mute at some point. But can fix by going to phh settings>ims>install mtk ims apk for pie vendors. (Problem stopped)

Can't set alarm manually except by summoning Google Assistant to do it. (Any suggestion pls?) Thanks!

Camera quality is same as stock.

It charges insanely fast too.

There's the occasional stutter here and there but nothing serious (maybe its just me, I have a keen eye for detail) lol 🧐

No restarts, reboot or anything odd.

Hotspot, Bluetooth (Calls too), RIL, Fingerprints and all the basics.

And yeah also I observed that if you attempt setting a wallpaper of high resolution, it fails but can be fixed by reducing photo resolution.

BTW this is my second day with this GSI.

I hope this information helps those of us with a mediatek chip.

For a genetic system image, its quite stable.

I'll report more findings.

Thank you @AndyYan & @phhusson for this work.
[Treble-Enabled Device Development A/AB ROMS] jamadz15:
I installed this rom on my moto G8, and is working fine the only issue I've got is no sound on messenger calling, as in the normal calling as in the video calling anyone else having that issue, any way to solve it
[Treble-Enabled Device Development A/AB ROMS] autokoise:
Hi, in my experience GSI is (probably) always without in build sounds, at all.....you just download some ringtone/notification jingle from browser, from Zedge for example, and set it as ringtone or notification sound.
[Treble-Enabled Device Development A/AB ROMS] jamadz15:
Actually, that's not the issue I meant, when I'm making a messenger calling there's no audio on the phone nor on the speaker
[Treble-Enabled Device Development A/AB ROMS] 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?
[Treble-Enabled Device Development A/AB ROMS] :
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. :unsure:
[Treble-Enabled Device Development A/AB ROMS] 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)?
[Treble-Enabled Device Development A/AB ROMS] 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
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] :
Isn't it clear?

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

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.
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Andy perhaps you can add eremitein patch to support dynamic root
[Treble-Enabled Device Development A/AB ROMS] MPK99:
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.
[Treble-Enabled Device Development A/AB ROMS] :
Waste of bandwidth?
[Treble-Enabled Device Development A/AB ROMS] MPK99:
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.
[Treble-Enabled Device Development A/AB ROMS] 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:

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.

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'm pretty sure there had been more than one user in the past who voiced their objection to *Z citing its issues...
[Treble-Enabled Device Development A/AB ROMS] MPK99:
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.

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
[Treble-Enabled Device Development A/AB ROMS] 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.

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...
[Treble-Enabled Device Development A/AB ROMS] SeventhRaven:
Any news on A13 builds for this? Apologies if I missed a post, haven't seen anything in the OP.
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
There is an early alpha on Telegram. Search under GSI's Trebble project.
[Treble-Enabled Device Development A/AB ROMS] SeventhRaven:
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.
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] vewu101:
bit of a weird question but does the pixelify module work on the gsi?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
hey there. i am currently in a bit bad situation. i cannot use telegram since it is banned here. (why). i heard lineage os 20 builds are over at telegram. even if its that early i would like to test it but i have no idea how to get em. since every gsi i try has animation or bugs/lags and samsung own stock firmware for my device has a critical bug.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The result of the SU poll has been locked in, and *N took the majority this time. Nonetheless, I'll give "building both" a go to see if it's still unacceptably impactful as of now.

Once again reminding you that *N builds still aren't guaranteed to pass SafetyNet - you might still need Securize for that, or simply go Magisk+modules if applicable.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I'll update you guys on LOS20 and in general A13 as well, and you might not like it.

PHH has "retired" from intensive development, thus it's almost certain by now that there won't be A13 builds or patches directly from him. He still supports us builders (for now), so we formed a collective to forward-port his final patches and fix new breakages, but even our collective knowledge might not match his. The collective is still working on it, and I haven't tried making a (PHH-based) build with the current progress yet.

Meanwhile, I'm also experimenting with a new "light" approach - inspired by PeterCxy, I'm "starting over" from the AOSP generic target gsi_*, adding in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process. This is to make sure I understand most fixes I pick and make it easier for myself to keep up in the future. Many fixes are still from PHH's time-proven stash, but I don't think this can be appropriately called "PHH-based" anymore.

This "light" approach will likely not work on pre-A10 devices anymore (none of my legacy devices boot it), and won't work as well as PHH-based GSIs on many other devices (most obvious offender being Samsung). I deem certain bugs and buggy devices as unimportant or unworthy of my time, and will intentionally leave them unfixed. Yes, this approach is born "selfish".

The one LOS20 build shared in Telegram is an initial "light" build, and one that hasn't even reached my own daily-driver standard, so you guys definitely won't want it. When it's ready for myself, I'll make a separate thread about it.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i tried the gsi arrow os 13 with it based on your patches. so far there were alot of options missing. Anyways thanks for your amazing work
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
hey i am facing an issue on lineage os 19.1 where guestural animations are glitched. when i swipe home sometimes the animation bugs. it glitches. sometimes it does not. any idea on whats causing this. every android 12/12.1 rom has this issue.
[Treble-Enabled Device Development A/AB ROMS] a9381:
Can you share a link to this build? Thanks!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with October security patches. [Insert obligatory backup-and-test warning here]

Although the SU poll says people want *N, for this month, I generated Securized images instead. These should go just as far if not further than *N in removing SU and dealing with SN, and is easier on my build/upload time too. If this still doesn't work for your usecase, let me know, but I doubt I could do anything at that point.

Enabled call recording in the built-in dialer per request. Note that this feature is also controlled by region to conform with local laws, and I won't work around that.

State of A13 had been described above. For the "light" approach, I've reached my own daily-driver status yesterday, and I'll make it available after I actually test it on a device/environment that's equivalent to my current daily-driver. Don't pester me for a build.
[Treble-Enabled Device Development A/AB ROMS] NewXiaomiUser:
Hi,

first of all, thanks a lot for this wonderful GSI again.

I flashed successfully the "lineage-19.1-20220912-UNOFFICIAL-arm64_bgS" on my Redmi note 10 5g, and I'm using it since a 2 days now and I love it .....

But

- When in call, the volume is very low, the volume is already at the maximum and I barely can hear the other side.

- I applied the fixes for backlight (phh settings -> misc --> use linear brightness slider + force alternative backlight scale + allow settings brightness ...) and from time to time, the screen does not wake up when pressing the power button, in that case I either have to reboot the phone or use ADB to set the backlight intensity manually.

- I've tried to "build" a secure version using your procedure (https://github.com/AndyCGYan/sas-creator), and unfortunately, the resulting image is not working (using docker on windows), it goes into a Fastboot loop. Strange fact, the "s-secure.img" file is 3279048Kb where the original is 2817216Kb.

Looks like the VNDKLite images are not working on my device so I cannot try the latest "secure" from your repo

Thanks for your work
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
th

thankyou so much for your amazing work.
[Treble-Enabled Device Development A/AB ROMS] XDA_username00:
No issues to report on upgrading a Samsung S9+ previously running 20220912_arm64_bvS image. Not using this as a phone though, just BT/WiFi. Using the custom TWRP bootloader/recovery as a result of the unlocking process needed for this phone.

Only issue I observed with previous image was that sometimes the phone would get stuck in the low power state with the white circle and 100% in the middle. Had to force it into Download or Recovery mode in order for it to get a prompt for it to boot normally.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
why does this new release say its on Nov patch 2021
[Treble-Enabled Device Development A/AB ROMS] XDA_username00:
Where do you see that and which image? Mine says oct 11 2022 (20221011).
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i used the latest one bgs secure vndklite. i am sure it was the update one since sourceforge said it was uploaded 10 hrs ago.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Securize will use your vendor security patch date.
[Treble-Enabled Device Development A/AB ROMS] like427:
People Hi!

How to pass SafetyNet and hide apps, made all work to do this in Magisk (modules Shamiko, SafetyNet inside Zgysk etc), but any way it doesn't . Apps telling me that i have Root and so on (in any 19.1 VNDK bvS)?
[Treble-Enabled Device Development A/AB ROMS] spider1163:
On previous build (lineage-19.1-20220912-UNOFFICIAL-arm64_bgS-vndklite.img) :

I removed SU via Phh Settings (Misc > Securize)

Reboot

Flashed Magisk and safetynet-fix

From Magisk settings : hide the Magisk app, enable Zygisk & Enforce Denylist

Reboot

I just dirty flashed new build (lineage-19.1-20221011-UNOFFICIAL-arm64_bgS-vndklite-secure.img) and root is still hidden
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
tbh lineage os is the only gsi that passed safety net without me doing anything at all. even installing magisk passed safety net with no problems. all the others ones i had to hide the root from play services using shamiko. in this one it just passes S/N automatically.
[Treble-Enabled Device Development A/AB ROMS] nisfta:
How to make mac randomization work? There is no such option when connecting to WiFi network
[Treble-Enabled Device Development A/AB ROMS] XDA_username00:
Just wanted to report that this latest build still has the issue with low power state (Samsung S9+ using the bvS image). Leaving it unattended for a while, causes the phone to display the battery charge remaining in a white circle. The only resolution is to force it into Download or Recovery mode to get the menu option that allows a reboot. Power button alone does nothing. Remembering to power off at the end of the day of course mitigates this.
[Treble-Enabled Device Development A/AB ROMS] Dragorius:
Hello,

thanks for removing buildin SU. Here some information I got with the october rom:

Samsung A6 [A600FN]

Flash Orangefox 11.0 via Odin

Flash OrangeFox 11.1 via recovery

Format Data

Wipe Cache, Dalvic, Data, Vendor, System

Flash Rom lineage-19.1-20221011-UNOFFICIAL-a64_bgS-vndklite-secure as system

Flash Vendor a64

Flash H-Kernel as boot

Flash Magisk 25.2

Reboot System und setup System

Install Magisk apk, Modules Safetynet fix, MagiskHidePropsConfig and BusyBox

Setup Modules [Fingerprint Google Pixel 6 (12)]

Test SafetyNet with Yasnac --> Basic and CTS Pass!!!

Now only up to date security patches missing. Thanks for the great work.
[Treble-Enabled Device Development A/AB ROMS] MPK99:
What does bvS/bgS secure mean ? secure, or pre-rooted ? It's funny naming scheme btw...

Shouldn't it be bvN/bgN ?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
its all on the sourceforge page. if you didnt read
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Bruh. Andy's ignoring his own naming scheme that he wrote.

S in b*S refers to pre-rooted (comes with superuser). It cannot be secure, caz that would be b*N (non-rooted).
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The naming scheme is applied at build time. N is built non-rooted, while S is built rooted but post-processed to remove root, plus Securized (which N doesn't).
[Treble-Enabled Device Development A/AB ROMS] MPK99:
That's fine I guess. You gotta mention it in readme then.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Will do, I forgot to remove the "not offered here" part as well.
[Treble-Enabled Device Development A/AB ROMS] Hovenbeets:
My device have an A-only partition but there seems to be no variant for this. What variant should i select instead? My device supports system-as-root though.
[Treble-Enabled Device Development A/AB ROMS] Heeni:
Install Treble Info by Hackintosh5. That should tell you which version you need.

I suspect that with system-as-root you'll be able to run an a/b ROM.
[Treble-Enabled Device Development A/AB ROMS] Hovenbeets:
Thanks. I just installed treble info, it says that I should use A/B.
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I have a couple of tablets, which I'm pretty sure are A only, but Treble Info says they need A/B ROMs. They both run well with this Lineage ROM.
[Treble-Enabled Device Development A/AB ROMS] project_2501:
@AndyYan Is there a way to preserve the hardware flags set by the vendor and use the features with one of your GSI builds (such as VoLTE, USB DAC, etc. with build.props)?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
a A/B gsi should run fine. even my phone says it doesnt have seamless updates but it has SAR (system as root). i am using superior os 13 A/B as my daily driver
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Here's a byproduct of my work on LOS20 - working VoLTE/IMS on newer Qualcomm/MediaTek platforms! Tested personally on various devices of SM8450, SM8475, MT6893, MT6895, etc. And Motorola too - the currently available generic solution would hang on making a call.

This is a TrebleApp APK that contains changes to detect the above and install IMS APKs I've repacked for them. Install over the existing one, enable IMS settings as you would for any PHH-based GSIs, reboot and you should have it. If still nothing, try toggling VoLTE in SIM settings.

Should work on other PHH-based GSIs too.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
just tried the new LOS 20 light that popped up. it is super smooth. there seem to be more options in the treble settings. although audio settings are greyed out? maybe in future it will be working. super smooth. bluetooth worked (audio too).
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Much less settings compared to PHH's TrebleApp actually - like the preface of that thread said, I only picked what I need.

The 2 audio settings only apply to Qualcomm devices.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
oh okay. thanks for your amazing work againnn. hope to see more settings working soon. i use an MTK device maybe thats why.