yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] m0byn:
So, I was able to isolate the problem somehow. It is definitely related to using the S-Pen. If I just use the tablet without the pen everything works fine and no issue of restarting when putting the tablet to sleep. However, as soon as I do just one little thing with the S-Pen (it is enough that it shows the pointer and recognizes the S-Pen without even touching the display), the next time the tablet is put to sleep, LineageOS somehow crashes and restarts.

I am thankful for any tips on how to solve this issue since the S-Pen is indeed a core feature of the tablet for me!

I am happy to provide any more details to figure out whats the problem, be it logs or anything else.

@AndyYan would it be possible for you to have a look at this?

EDIT: S-Pen issue disappeared with March update!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Definitely weird to see this report. Will have to test for myself on both of my Samsung devices, they both have pens (a phone and a tablet).

Is your pen the kind that wirelessly charges? Or it doesn't need to be charged periodically? On my tablet, it automatically magnetizes to a location on the rear of the device, and wirelessly charges as long as it's placed there. I have a case on my tab, but it has a cutout slot on the back to fit the pen.

On my Note, it just slides into a slot in the bottom left of the phone, and charges as long as it's there. So it fits INTO the phone, rather than ONTO it, like the tab.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I totally agree that it is weird. Looking foward to your tests.

My tablet is a Samsung Galaxy Tab S6 and it is exactly this type of pen. However, I am pretty sure that the pen itself does not HAVE to be charged. For example, I tried the pen of my Samsung Galaxy Tab S4 tablet, which does not even have a battery, and it shows the exact same behavior while writing, but also with restarting lineage. To the best of my knowledge, the charging of the pen is only necessary to use some special Samsung features related to the pen when using OneUI.
[Treble-Enabled Device Development A/AB ROMS] IronDwarf:
What gapps are compatible ?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
The GApps that are included will be 100% compatible with the gsi. For 3rd party GApps, the LOS dev team only recommends MindTheGApps. Better to go with what's included, since you would have to flash MTG separately.
[Treble-Enabled Device Development A/AB ROMS] IronDwarf:
I am a little confused, I installed your latest release and runs great but no she apps installed. I tried several different yeah but none would install
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
It's NOT my release...I was merely responding to your post.
[Treble-Enabled Device Development A/AB ROMS] IronDwarf:
Sorry about that. I installed the latest release and it doesn't have any gapps
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Then install the one that has GApps. You can flash the MindTheGApps zip onto the vanilla vndklite version, I've tried it, it does work. But I couldn't get OK google/hey Google voice commands to work.
[Treble-Enabled Device Development A/AB ROMS] IronDwarf:
Thanks i will do that
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
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.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@AnonVendetta Thanks for voluntarily taking care of Qs while I'm gone :)

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. I don't plan to get a Tab S* or any productivity-oriented tablet in the near future, so I won't work on improving this just yet. Note to others: if you notice another AOSP-based ROM with a better solution, do notify me.

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.

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

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

Sounds like your device has an ill-defined overlay - the "center" option is only removed when there's a center cutout defined.

Trust's notif can be disabled, after which it shouldn't affect daily usage.

Encryption is a vendor-specific thing, and by now all modern devices default to enabled. Most vendors are now also read-only (EROFS and such), so you can't even change the fstab to disable that.

Logcat me the crash, I'll check for the obvious.

BTW, I own a Sammy Note10 5G, which happens to be my only device on TD-based (the rest are all on "Light"). It doesn't crash like you described.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Andy, if you could only have one device/OS for a year which would you rather, TDBased or 'Light'?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
"Light" any day, unless someone f's with me and intentionally gave me a legacy device or a Sammy.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
I have a VNDKLite enabled phone (Moto G Power 2021). Is that what you're talking about when you say Known but will not implement/fix:

Compatibility with legacy (pre-A10) devices, A-only, VNDKLite? Screenshot of Treble Info attached
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
No, it says "full" and doesn't have a slash across the icon. VNDKLite is a way legacy concept from Oreo.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Maybe that's one of the reasons there are no roms for it.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I don't mind giving up the generic mouse pointer for a pen pointer.

I'm wondering if you know of some way to query the charge level #/status (charging/not charging)? Not necessarily with a GUI, perhaps terminal commands or something? I know that the pen charges when it's "docked" to the back of tab/inside phone, it's easy to deduce this, since when it's not working, or barely working, it's either battery low or dead. And after a time of docking it, i can usually use it again within 15-20 mins. At some level, GSIs recognize the pen because they're charging it, but I wish I knew of a way to be sure.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
My devices supports all of the options shown in your screenshot, except "seamless upgrades". For some reason, Samsung is just too damn stubborn to adopt true A/B slots on their devices. In the same vein, they also refused to implement adoptable storage, despite it common amongst other manufacturers.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I always just thought that vndklite meant system (or root, whatever you prefer) is RW.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Nope, sorry, although I am kinda curious (how the pen would report back its status).

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.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
"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 seems very plausible. Would you be interested in adjusting the coordinates? I would help out to find the correct ones the best I can.

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

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

Create new page · phhusson/treble_experimentations Wiki

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

github.com
[Treble-Enabled Device Development A/AB ROMS] wojtekojtek:
but I have it ro in vndklite :<
[Treble-Enabled Device Development A/AB ROMS] Kenaz Rune:
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
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
With root access, remount it (the system or whatever) partition as RW. Then you can make changes.
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
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 ! o_O

- of course: data was formated before flashing -
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
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.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I will try that with the next update! Thank you!

EDIT: it works like a charm! Thank you for including this!

Yes, I compared across devices.
[Treble-Enabled Device Development A/AB ROMS] 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_*
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
...?

Commits · TrebleDroid/vendor_hardware_overlay

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

github.com
[Treble-Enabled Device Development A/AB ROMS] 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.
[Treble-Enabled Device Development A/AB ROMS] uluruman:
Oh. I didn't know where to look. So that means captaincookie200's overlays didn't fix it. Too bad.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
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
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
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 :(
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Try this app, it should replace AOD if it's not available in Lineage. Don't be sad....

AOA: Always on Display - Apps on Google Play

Always on display with edge lighting, notifications, weather, music controls.

play.google.com
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
For desk clock purpose, Daydream (known as Screen saver now) is much more flexible; or, just pair your favorite app with LOS's Caffeine (never sleep) tile.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
not to mention aod on every gsi has tried is broken. the clock gets stuck and doesnt update.
[Treble-Enabled Device Development A/AB ROMS] tangy912:
I'm having a notch issue. The GSI is not detecting my device's notch. Any way to fix this?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Make an overlay.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
@AndyYan

When I need root and also GAPPS, which Image should I choose?

TrebleInfos says: arm64, vndklite

Device is ab-patched (TB-X605L)

I am asking because there is no

lineage-20.0-20230324-UNOFFICIAL-arm64_bgS-vndklite.img.xz

Thanks.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Root with Magisk. Yes these do support Magisk out of the box, usually no need to do Securize or weird stuff.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
Hello everybody...

I just noticed that on my device (Poco M4 Pro) with a freshly installed ROM, there is no internet despite Wifi is correctly connected and shows "Internet" as connected..

When I launch the browser, I get ERR_NAME_NOT_RESOLVED..

It seems it's a DNS issue..

I don't know how to change the DNS in the phone but I tried to go to a website by using its direct IP address but the page gets stuck in the loading state...

When I set the private DNS to adguard for example, it's also loading indefinitely..

Does it mean somehow my device is not working with LineageOS?

I tried many GSI ROMs and never had that issue..
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Hey. I'm using lineage-20.0-20230324-UNOFFICIAL-arm64_bgN-vndklite on a Moto G Power (2021).

couple things I've noticed:

- the powered off charging screen/logo is much simpler/basic than the previous lineage 19.1

-might be something up with the battery re: full charge saying I have one day instead of almost 2... I imagine I will do that thing where I drain it til it shuts down then power it up to full with the power off to see if that recalibrates anything.

Also, is there a way to put all status bar icons towards the right? Re: embedded camera on left

Also, is there any way to rescind vndkliteness so as to take advantage of your 'light' version?

PPPS: I should definitely not be attributed with the moniker 'Senior Member'. It implies that I'm something other than a technological clod, only maintaining a custom gsi because of the ability to cut and paste.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Gee people, read OP and #2...

I assume your stuff are going behind your front camera, the right way to rectify that would be to make an overlay.

VNDKLite is a way legacy concept from Oreo, I don't believe your device requires that variant (unless you show me a Treble Info screenshot?). That aside, people have reported that they were able to switch between "Light" and TD-based without wiping, although I wouldn't recommend so.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Don't really know what an overlay is, though its not really important.

Mostly I'm attracted to 'light' because of the exFAT thing. I've been told that it is, in the long run, gentler on the processor. And my goal with my device is technological endurance... as if I'll never have access to a pc again.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
TD here also has exFAT (ofc I'd (back)port that to all I'm maintaining).

Your screenshot proves that you don't need to run a VNDKLite variant; you might want it for /system read-write purpose.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
My bad and thank you!

In the meantime I flashed back LOS 19.. I'm going to flash again 20..

Quick question though on that post you say the following:

What do you mean by to upgrade to a new vendor?

Also, I read a little bit about VNDK, and it seems it's mostly related for older smartphones as you said..

But in my case my phone (Poco M4 Pro) is pretty recent and had Android 12 (so should not be relevant regarding VNDK) but I also have info about VNDK in Treble Info (VNDK version => 31.0 and VNDK Lite => Full linker namespace separation enabled).. So I usually go with the VNDKLite version but I did try both version for a given ROM (e.g. LOS 20) and I didn't notice something..

Do you think I go with the regular version or the VNDK version anyway?

Thank you.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
light has alot of stuff excluded. It was made for andy's own personal use. It excludes alot of fixes and patches. I cant daily drive it since i need some settings from phh settings which are not there in light. and they are essential for me. It depends on your usecase.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
I have the exact same output of Treble Info (minus mine says Version 31 for VNDK) so I got that I don't need the VNDK version..

Out of curiosity though, in which case we might want to have r/w permission for /system?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
I don't use a phone/data/sim card, and don't use bluetooth and don't buy or sell anything (re: security stuff). Ideally I'd not have my Android folder encrypted at all. My philosophy seems to be to have the optimal phone for endurance if 'the big one' comes...

wait... Which settings? Is the Alternate Headphone settings thing not there anymore?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Your device had A11 out of the box; a newer stock base with its updated kernel probably (A12) / definitely (A13) have already fixed that bug mentioned. When you wanna try that, flash stock and start over.

If you can't think up a usecase for /system RW, just use the regular version. You can switch when the need arises anyway.

/system RW is great for testing mods or changes that you want integrated later. When I write overlays for devices I appreciate being able to drop them in live, instead of having to repack or build a whole system image.

On the flipside "Light" will receive much more attention from me, be the first to get updates or fixes of my interest (e.g. the SM8550 in-call audio fix) each month. Just putting it out here so people don't simply dismiss it.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Wait. Doesn't 'rooting' automatically imply system r/w capability?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
No. Some system images are built with EXT4 shared blocks enabled, meaning they're inherently read-only. Surely you can "overlay" your modifications with Magisk, but that's a different mechanism.