[GSI][13] LineageOS 20 TrebleDroid-based

[AndyYan]

I'm wondering if you know of some way to query the charge level #/status (charging/not charging)?

Nope, sorry, although I am kinda curious (how the pen would report back its status).

I always just thought that vndklite meant system (or root, whatever you prefer) is RW.

This is actually a side effect of mounting the image and adding VNDKLite support. TD-based is built with EXT4 shared blocks enabled, but to mount/modify the image, it has to be unshared; "Light" on the other hand is simply unshared to begin with.

 

[m0byn]

1. On my builds, "setprop persist.ui.spen.pointer true" should replace the pointer with Sammy's original blue dot, but that also replaces the mouse pointer, not sure if that's a price you're willing to pay.

"my builds" refers to the "light" version? I actually installed the TD version since in the "light" forum you mentioned the better support of TD for Samsung devices.
How can I set "setprop persist.ui.spen.pointer true" ? My device is not rooted.

1. Unsurprisingly this device has FOD. I only inherited the FOD solution from PHH/TD, never took a look at it, so I'm not entirely sure what could be wrong either - a crude guess would be wrongly reported FOD X/Y coords, esp. under landscape.

This seems very plausible. Would you be interested in adjusting the coordinates? I would help out to find the correct ones the best I can.

1. I've heard from a Tab S7 user that it worked for him (in fact he was the one who pointed out that the above pointer replacement also affecting mouse).

Ok, I will try to flash my Tab S4 then.

1. Perhaps one of the audio options in Treble settings might help?

I do not think so. Maybe someone else figured out a correct setting? @AnonVendetta you maybe?

One last point: the "light" version installed on my Samsung Galaxy A50 actually has auto-brightness implemented. The TD version installed on my Samsung Galaxy Tab S6 does not have this option. Is it somehow possible to implement it in the TD version/for the Tab S6? @AnonVendetta mentioned that his Samsung tablet neither shows the option of auto-brightness.

 

[Kenaz Rune]

Just wanted to mention as an alternative that MicroG works fine on the vanilla versions, if you just need working Play Store and basic Google apps compatibility. Lighter installed footprint/space used, and probably less usage of system resources.

You can just install MicroG Installer Revived as a Magisk module, will work on vndklite and non-vndklite versions. Or you can manually push its' files directly into the system partition, but you'll need root access and a vndklite variant.

You can get SafetyNet to pass with MicroG too, alongside enabling securize/spoof system properties. You might also need an extra Magisk module or 2. It was passing for me when I last tested.

This is the way.

I have a Galaxy Tab SM-T510, and it's becoming almost useless with GAPPS installed. Play services takes over 800M of RAM. It's still viable with MicroG. I'm hoping some soon to be released tablet will work with GSI or get custom ROMs, as this one is quite rickety.

 

[rw_on_xda]

ping @Kenaz Rune

care to post:
1. what ROM *exactly' do you have installed ?
and
2. how exactly did you install the GSI ROM's ?
and
3. what stock ROM was on the device before ?

Why ?
I got boot loop's with GSI Rom's (greater than Android 12) on my SM-T510

last working: AOSP 12.1 v416
installed as described here:

Samsung Galaxy Tab A 10.1 (2019)

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

 

[wojtekojtek]

You don't patch it. Use the vndklite versions.

On the technical side of things, you could remove the shared_blocks filesystem attribute from the img. You would just need to use a tool that removes that attribute and repacks the image without it. But why go through all that effort, when using vndklite is much easier?

but I have it ro in vndklite :<

 

[Kenaz Rune]

ping @Kenaz Rune

care to post:
1. what ROM *exactly' do you have installed ?
and
2. how exactly did you install the GSI ROM's ?
and
3. what stock ROM was on the device before ?

Why ?
I got boot loop's with GSI Rom's (greater than Android 12) on my SM-T510

last working: AOSP 12.1 v416
installed as described here:

Samsung Galaxy Tab A 10.1 (2019)

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

Gladly. First, for a long time, I used Magendanz' ROMS. Most recently, his LineageOS 19.1, which uses Andy's GSI with GAPPS. The key thing here is that he's been updating the rest of the firmware as Samsung releases it. If you're still on stock, that might be part of the problem.


I suggest you start with his version, then flash the GSI yourself onto system when updates are available here. When he releases a new update, flash his build to get all the tweaks and fixes for the other parts of the system. At this point, it's mostly about getting the security fixes from Samsung, which happens quarterly at best.


I just flashed Andy's Android 13 February release yesterday and it's working well. I just noticed recently that Minecraft is now working with MicroG. Some MicroG update in the last 4 months must have made that possible.


One more important point that burned me early on. The T510 uses the "a64" variety, not "ARM64". You will bootloop if you choose the wrong one.


1: lineage-20.0-20230218-UNOFFICIAL-a64_bvN

2: TWRP flash image to system partition

3: LineageOS 19.1

 

[AnonVendetta]

but I have it ro in vndklite :<

With root access, remount it (the system or whatever) partition as RW. Then you can make changes.

 

[rw_on_xda]

...

One more important point that burned me early on. The T510 uses the "a64" variety, not "ARM64". You will bootloop if you choose the wrong one.
....

quiet clear, I used the Treble Info, what turned out:
- system-arm32_binder64_ab
- VNDK Version 30.0 supported

My attempt was with *a64_bvS-vndklite*, maybe that was my mistake.

very curious, cause I was flawless running system-squeak-arm32_binder64-vndklite-vanilla (based on Android 12.1)

my stock is 5CWA1 (of course with @Magendanz last TWRP)

+++ EDIT +++
tried lineage-20.0-20230218-UNOFFICIAL-a64_bvN

NO chance !
LOS logo is spinning since 10 minutes !
- of course: data was formated before flashing -

 

[AndyYan]

"my builds" refers to the "light" version? I actually installed the TD version since in the "light" forum you mentioned the better support of TD for Samsung devices.
How can I set "setprop persist.ui.spen.pointer true" ? My device is not rooted.

This is a universally useful and non-intrusive (default OFF) mod, so I added it to TD as well.
LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.

One last point: the "light" version installed on my Samsung Galaxy A50 actually has auto-brightness implemented.

I just realized that you've been comparing across devices, i.e. you aren't controlling variables properly...

but I have it ro in vndklite :<

This might actually happen - I'm starting to observe it on some very recent OPlus (=OPPO+OnePlus+Realme) devices. Unfortunately I don't have a way out, nor am I really interested in checking "why" at the moment. Perhaps use Magisk for /system changes instead?

 

[AnonVendetta]

This is a universally useful and non-intrusive (default OFF) mod, so I added it to TD as well.
LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.

I just realized that you've been comparing across devices, i.e. you aren't controlling variables properly...

This might actually happen - I'm starting to observe it on some very recent OPlus (=OPPO+OnePlus+Realme) devices. Unfortunately I don't have a way out, nor am I really interested in checking "why" at the moment. Perhaps use Magisk for /system changes instead?

I think it's more likely that this user simply doesn't understand how to remount as RW. vndklite builds only means that it *CAN* be remounted as RW...but the default state is still RO. It's never failed for me.

Also, he may be trying to remount a partition that isn't covered within the scope of the gsi img, like vendor or product. If those are RO for whatever reason, and they can't be remounted as RW, then nothing will work no matter what is tried. Besides ext4 shared_blocks, there is also the infamous "f2fs RO" issue, which is an entirely different problem, but still can't be remounted RW regardless.

 

[m0byn]

This is a universally useful and non-intrusive (default OFF) mod, so I added it to TD as well.
LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.

I will try that with the next update! Thank you!
EDIT: it works like a charm! Thank you for including this!

I just realized that you've been comparing across devices, i.e. you aren't controlling variables properly...

Yes, I compared across devices.

 

[AndyYan]

Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]

As usual with "feature drops", things can change or break majorly.

Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too. Also pushed to TD upstream, so in case you don't like LOS, it's still coming to your favorite TD/-based GSI later.

Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.

Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.

Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.

And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:

rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*

 

[uluruman]

The dim backlight problem on Samsung A32 is still there. I presume the latest phh's vendor_hardware_overlays with the fixes from captaincookie200 were not included in this release. I've been waiting for this but alas... Too bad I can't include those myself, I have compiled the apks but no matter how I try the modified system.img is causing the bootloop. I still can't figure out why. It seems that the absence of "shared blocks" is not the cause, so I think I have to return to experimenting with VB signatures, may be that's the cause.

 

[AndyYan]

I presume the latest phh's vendor_hardware_overlays with the fixes from captaincookie200 were not included in this release. I've been waiting for this but alas...

...?

Commits · TrebleDroid/vendor_hardware_overlay

This includes hardware-specific overlays for Treble ROM - Commits · TrebleDroid/vendor_hardware_overlay

github.com

 

[AndyYan]

@tangy912 reminded me that, since the beginning of LOS20, I've been using arm64 GAPPS on A64G* builds (when I should be using arm). It took 2+ months for it to be found out - I guess A64* just don't have that many users nowadays? Anyway, I've uploaded new A64GN builds that supposedly now contain arm GAPPS. I haven't had an A64 device in years, so it's entirely up to you to try out.

 

[uluruman]

...?

Commits · TrebleDroid/vendor_hardware_overlay

This includes hardware-specific overlays for Treble ROM - Commits · TrebleDroid/vendor_hardware_overlay

github.com

Oh. I didn't know where to look. So that means captaincookie200's overlays didn't fix it. Too bad.

 

[Captain_cookie_200]

The dim backlight problem on Samsung A32 is still there. I presume the latest phh's vendor_hardware_overlays with the fixes from captaincookie200 were not included in this release. I've been waiting for this but alas... Too bad I can't include those myself, I have compiled the apks but no matter how I try the modified system.img is causing the bootloop. I still can't figure out why. It seems that the absence of "shared blocks" is not the cause, so I think I have to return to experimenting with VB signatures, may be that's the cause.

to fix brightness go to phh settings > samsung features > enable extended brightness range

phh settings > misc > use alternative backlight scale


phh settings > misc > allow setting brightness to the lowest

and reboot




i myself switched to march lineage td. works great on ondemand and my own custom built kernel on the latest one ui 5.1 firmware

 

[sanjibukai]

Hello everybody,

I successfully installed this ROM on my Poco M4 Pro (MTK processor) which has an AMOLED display, but I'm not able to make the Always On Display working on the device.

Is it something I'm missing or is it just that this ROM is not compatible with my phone?

 

[AndyYan]

I successfully installed this ROM on my Poco M4 Pro (MTK processor) which has an AMOLED display, but I'm not able to make the Always On Display working on the device.

Although someone made an overlay for your device, he neither enabled doze nor defined proper brightness/position for it.
I'd say don't bother, AOD on GSIs are often unoptimized and can drain battery pretty fast.

 

[sanjibukai]

Although someone made an overlay for your device, he neither enabled doze nor defined proper brightness/position for it.
I'd say don't bother, AOD on GSIs are often unoptimized and can drain battery pretty fast.

An overlay?
I guess I just learned something.. So do I need to search for an "overlay"?

In one side, I really need AoD as I'm using it as a clock on my desk. So I somehow just want to just go back to stock MIUI ROM)
But on the other side, now I found MIUI so bloated and slow and most importantly on recent ROMs it's impossible to have full screen gestures with a third party app - which is a bummer as well)

I'm so sad and stuck