yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] uschipower:
Thanks for fast reply.

I am not sure what you mean. Should I use

lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img ?

And what about GAPPS? They are not included, right?

Another question:

How do I switch GSI-Image, in my case from your

lineage-20.0-20230324-UNOFFICIAL-arm64_bvN-vndklite.img

to

lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img

Simply flash "system" with TWRP doesnt work.

Device doesnt boot

It also doesnt boot after formating data.

edit:

i used this guide https://xdaforums.com/t/android-s-gsi-system-as-root-on-on-smart-tab-m10-tb-x605f.4400689/ to install lineage-20.0-20230324-UNOFFICIAL-arm64_bvN-vndklite.img
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
ok thanks bro , I gotta do the comand in fastboot mode ?
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
i have root , so can i do the shell command trought TERMUX APP ?
[Treble-Enabled Device Development A/AB ROMS] ttritium:
Nothing.

I made it from a terminal on my PC but maybe with Termux it's possible, try.
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
when i put in terminal

adb shell settings put global restricted_networking_mode 0

I GET THIS

adb server is out of date. killing...

* daemon started succesfully *

in termux says not adb command found

i have usd debug active , im doing domething wrong ?
[Treble-Enabled Device Development A/AB ROMS] ttritium:
Try : adb devices (to see if you device is detected)

After if detected : adb shell settings put global restricted_networking_mode 0

And maybe try with a newer version of adb if "out of date"

I think in termux app, adb command isn't necessary because your already in the phone. ADB is for communication from PC to phone.

Try just : settings put global restricted_networking_mode 0
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
settings put global restricted_networking_mode 0
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
i can do this from terminal in phone fastboot mode ?
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
it recognizes in terminal pc , adb devices ok ,but when i put comand and hit enter , it just dont say nothing , no ok , no error, it just bring me down the line again ,
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
I FIXED :) so simple , just gotta run the comand in terminal from computer , and with the phone on in the lineage gsi ,
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
now i see google is not allowed cause phone is not activated , but i know how to solve that easilly :) Now im gonna be able to test your lineage 13 yey ....thank a lot ANDY for your great job and helpfull guidenneess :)
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
... so funny, people are not used to use command-line anymore :-).
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
"I FIXED :) so simple , just gotta run the comand in terminal from computer , and with the phone on in the lineage gsi ,"

... was too late :). But your internet access is working now?

Greets

Kurt
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
yeah well everything seems to work ok now , awesome rom gsi
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
i solved it , im using it now on Poco X3 Gt , thanks Andy for his help
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Tried lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-vndklite-secure.img with my Sony Xperia 10 III (latest Firmware).

Everything I tried worked fine so far.

But Android Auto didn't connect with my car with USB.
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
yes fully working .... wifi and 5g networks
[Treble-Enabled Device Development A/AB ROMS] Jimmy Glex:
HEY ALL , i want PERFORMANCE AND GOOD GRAPHICS and now i have this question , in phh setiings says DESABLE HW OVERLAYS eats more cpu and battery , and in DEVELOPERS OPTIONS says , DESABLE HW OVERLAYS always use GPU for screen compositing , THIS IS CONFUSING ME A LOT , should i tick this option on ?
[Treble-Enabled Device Development A/AB ROMS] zyhk:
It depends on you. When I used Android 10, the overlay switch affected the percentage of deep sleep very much, say from 90% to 40% (I don't know recent results). But you could get a little bit quicker response.
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Finally it booted on my OnePlus nord 100 phone, thank you very much guys.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
Hello all..

I have a question that can be related to the previous question..

So I have a working LineageOS 20 on my phone (Poco M4 Pro 4G) which is also rooted with Magisk.

Now I wanted to install Gapps, but it seems the only way to do it is to use a custom recovery (TWRP).

The problem is that TWRP seems to not exist for my device and unofficial TWRP are stated to be only compatible with Android 11 (on my device the latest stock ROM is under Android 12)..

Do I need to rollback to a previous version of Lineage OS under Android 11 (or even using an older stock ROM) in order to have a working TWRP?

Isn't there another way to install a custom recovery?

I guess that in any caseif I succeed to have a working TWRP, I'll need to start over Magisk and Lineage OS installation, right?

Or maybe is there a way to just install the Gapps without using a recovery?

It seems the distribution preferred by LineageOS is MindTheGapps https://www.xda-developers.com/download-google-apps-gapps/
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Someone who hasn't heard of Magisk, what a rare sight these days...

There's a pre-GAPPS'd variant (*_gN).
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
I did installed that one: lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img which I belied should be one with Gapps, eight?

But it seems that all in all, among the Gapps, there's only Google, Play Store and Voice Search.

So I thought that I still needed to install MindTheGapps (or any other gapps distrib) in order to have a little more..
[Treble-Enabled Device Development A/AB ROMS] uschipower:
you misunderstood me

I know Magisk, and also DeltaMagisk

You wrote "Root with Magisk. Yes these do support Magisk out of the box, usually no need to do Securize or weird stuff."

I am not sure if you meant to use

lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img

which shall include SU, and Magisk-App is only the app which control su (you wrote "S: *Built* with PHH Superuser (app needed)"

or

if I should use Magisk normally on

lineage-20.0-20230324-UNOFFICIAL-arm64_bvN-vndklite.img

and patch boot-partition.

I have tested to patch boot in arm64_bvN-vndklite.img. This seems that this doent work.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The integrated one is already MTG. Download the "heavier" apps straight from Play Store, no reason to further blow up the size of the images (which already prevents some older devices from flashing).

You want both Magisk and GAPPS, so pair it with a *_gN image.

Unfortunately, if Magisk doesn't want to work with GSIs on your device, then none of us are really in a position to help you (the author is kinda anti-GSI). *_gS is also not an option, since PHH-SU is known to disturb SN.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
What ist SN?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
SafetyNet. Here I didn't precisely refer to it, I meant that having PHH-SU might fail some verification from el Goog and prevent you from logging in and such.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
@AndyYan

Because I was asked in another thread, does your *.img change/modify/add something on boot partition?

Which partitions are affected/changed when flashing your *.img?

Thanks.

@ all

have anybody rooted his device with one of AndyYan's *N-*.img (= Images without integrated PHH Superuser) successfully with Official Magisk or MagiskDelta?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Ya, I got Magisk. I'm running lineage-20.0-20230322-UNOFFICIAL-gsi_arm64_gN and just flashed it right after I flashed that using a patch previously generated through it's app.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Only /system.

I see you're asking around whether other GSIs support Magisk better. This is quite device-specific, and even if people report success with all sorts of other devices, yours might not necessarily do.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
Which device do you have?

Did you use the Magsik app to modify a boot-Image-File which you you have flashed then.

Or did you use Recovery to patch installed boot-partition directly?

If using boot-File, where have you taken from the file? From latest stock-rom?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Using a Moto G Power 2021. Ya. Used boot file from stock rom with the Magisik app.
[Treble-Enabled Device Development A/AB ROMS] stephengodwin895@gmail.co:
howfo I fix this color error
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i see nothing wrong. It might be happening on your physical display but not on screenhots. Try taking picture of the screen from another device.
[Treble-Enabled Device Development A/AB ROMS] tangy912:
Tried but there doesn't seems to be any files in both framework-res.apk and the vendor's framework-res that can fix it.

So, what should I do?
[Treble-Enabled Device Development A/AB ROMS] sso003:
Big thanks @AndyYan . I'm using this GSI as my daily driver on a Lenovo Legion Y70 and it works great. I truly appreciate your contribution to this community.
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
Hello everybody..

I tried to install the Live Wallpapers from here https://xdaforums.com/t/port-app-6-0-google-pixel-2-3-4-a-5-6-live-wallpapers-27-07-2022.3481640/

On different GSI ROMs (tries with Elixir and also PE - even if those are already in the phone) they just works.

On this version of Lineage OS, the Wallpaper app keeps crashing..

Does anyone know if there's a workaround?

I found that https://gitlab.com/LineageOS/issues/android/-/issues/5371 but it doesn't work in my case..
[Treble-Enabled Device Development A/AB ROMS] wojtekojtek:
Okay

I have now system rw

but

1) how to chnge bootanimation? there's no /system/media folder...

2) how to make /vendor rw?

3) how to DisableForcedEncryption?
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Does it already work for you? I tried it on my Samsung Galaxy A50 on the March bvN variant and it shows the exact same behavior!

EDIT: this is the logcat

Edit: @AndyYan is there a way to know if the mentioned fix is included in the current version of LOS? The Samsung A50 shows the exact same behavior as described in the quoted post!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Make your own measurements, although there doesn't seem to be many writeups on it. I should probably sum up how I do overlays into a post some time...

1) /system/product/media

2) Most likely you don't, esp. if it's EROFS on many newer devices.

3) Again, most likely you don't, as fstab is in /vendor and consequently RO.
[Treble-Enabled Device Development A/AB ROMS] AfiqAffandi:
Thank you @AndyYan for latest build lineage-20.0-20230325-UNOFFICIAL-a64_bgN google is working properly so far.
[Treble-Enabled Device Development A/AB ROMS] myrmidon132:
Hi, working great so far on Samsung S20 FE (Snapdragon).

Using lineage-20.0-20230324-UNOFFICIAL-arm64_bvN-vndklite.img .

Just one 'issue' (not really but it's easy to have sometimes to stop some apps from complaining), is there a way to enable signature spoofing?

I've got microg installed, working fine, however it is reporting the "System has signature spoofing support' (checkbox is checked) but the 'System grants signature spoofing permission' is unchecked. Is there a way to enable signature spoofing permission?

Thanks for the great work!
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Did you test your devices with the pen?
[Treble-Enabled Device Development A/AB ROMS] tangy912:
Use Link2SD or /system/app mover or any similar app that does the same thing to move the app into system. This should fix the issue.
[Treble-Enabled Device Development A/AB ROMS] tangy912:
Someone told me that I should make a custom overlay to fix the issue. But, I haven't found any Youtube tutorial or written tutorial about it.

You should make one so that people with the similar issue will be able to fix it.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I didn't, and wont be able to for awhile. I'm back on the stock firmware, no gsi, for now. Perhaps in a few more days I will install a gsi again. Been busy with lots of stuff outside tinkering with Android.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
There's your cue...figure it out yourself, make a tutorial, publish it.
[Treble-Enabled Device Development A/AB ROMS] Sage:
just got one of your builds running on my Tab S6! Thank you so much!
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Unfortunately, I am not 100% sure what you mean by setting an appropriate density...
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Could this post be helpful not to repeat any work?

Maybe you could quickly look over it and let us know if that is still the way to go? Or even include it in OP such that everyone knows from the beginning :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Both tablet UI (taskbar) and two-pane are enabled on sufficiently small (albeit different) display sizes. I don't think the setting in Settings - Display size and text would go that low though, so instead one either set a large enough Smallest width in Developer options, or a small enough density via ADB.

This mainly outlines getting values from stock, but sometimes stock provides no or dummy values (they can store values in other partitions or under entirely different keys).
[Treble-Enabled Device Development A/AB ROMS] wojtekojtek:
1) thanks!!

[Edit] - I can rename boitanimation.zip, but I can't copy my bootanimation in media folder.... Help

2) I don't have erofs, I have a samsung device (a137f). I must edit /vendor or atleast repack vendor.img.... really.. because I must DFE to make twrp working... I tried DFE zips, they aren't working.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I am currently trying to flash this GSI on my Samsung Galaxy Tab S4 (gts4lte), but am not succeeding.

I managed to install TWRP (unfortunately only the WIFI version is available, but others say it works for the LTE version as well). Afterwards, I wiped the usual stuff and tried several different procedures

Flash GSI, then dm - verity disabler (as explained in a different forum by a guy who got LOS 17 running) => stuck at bootanimation of lineage

Flash patched boot.img to remove dm-verity, then GSI => stuck at bootanimation of lineage

Flash GSI, then dm-verity, then Magisk => stuck somewhere earlier, don't remember

Flash GSI and multidisabler.zip => same as only flashing GSI

Flash only GSI => reboots all the time not even proceeding to bootanimation of lineage.

These steps were repeated using the a64_bvN, arm64_bvN, and arm64_bvN-vndklite images.

The Treble Info app shows the following information:

Also, the Wiki has an article on how to install it on this device, although already from some time ago. Somewhere else, I read that from Android 10 onwards one should use the arm64_b images instead of the a-only. The only thing I did not do was flashing a custom kernel. However, I believe this is only done for disabling encryption. Please correct me if I am wrong.

So, could anyone help out? Did anyone experience a similar problem? Since it is stuck at the lineage bootanimation logo I suspect dm-verity and encryption do not play a role? Do you have any hints or ideas what I could try to make it work? Maybe LOS 19?

I am thankful for any hints or any information regarding this issue!

EDIT: if anyone faces the same problems see this post. Actually, as far as I can guess the reason causing all these problems is that FDE is used instead of FBE...but this is just a guess.
[Treble-Enabled Device Development A/AB ROMS] wojtekojtek:
edit edit:

I mounted system.img

but I need 10MB more space... and... what I can delete?
[Treble-Enabled Device Development A/AB ROMS] PalmerBE:
Hi, what alternative Gapp (OpenG, etc..) can be used with Lineage OS bvN Treble ?

With both 19.1 and 20 I get the error of the /system partition that cannot be resized.

Cheers
[Treble-Enabled Device Development A/AB ROMS] sso003:
The system partition is created with the EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS flag. It's basically read-only, can't resize, can't edit anything.

Your best bet is to go with the BgN version with Gapps built in.
[Treble-Enabled Device Development A/AB ROMS] PalmerBE:
Yes, but I would like to deGoogle my phone as much as possible.

I need only to pass the Safetynet and have the minimum of Google Service . No default app's

Should not be that one of the purpose of LineageOS :) ?

Jokes a part , can I manually de-Google BgN afterword with De-Bloater (for instance)?

Is there a list of the Google app/services included in the BgN so I know what to clean up reducing the risk of killing Lineage?
[Treble-Enabled Device Development A/AB ROMS] myrmidon132:
Thanks! Still a bit new to these android 'internals' (depends on your level of comfort with it I guess :)..)

However, if I use the /system/app mover or Link2SD, it complains about too few storage in the system-partition.

Checking it with some other app, indeed, the system-partition is almost full so no room to move the app to it.

Is there a safe way to enlarge the system-partition? If I boot into twrp and resize, I guess it should work? I've done it a couple of times on a Linux desktop but don't know how well Android behaves as a Linux system...

I'll try it later this week but maybe somebody has more experience with it?

EDIT: just saw the responses above about the system-partition being read-only, will have to find another way or just live with it I guess.
[Treble-Enabled Device Development A/AB ROMS] tangy912:
Well, Resizing the partition is kinda hard depending on what device you use.

But, an easy way of doing it is by flashing a gsi .img which is larger than the Lineage OS GSI .img using fastboot and then, flashing the Lineage OS GSI .img using TWRP.

This will leave some space because TWRP doesn't resize partition when flashing while Fastboot does.

Or, If you want, you can remove some system apps that isn't needed for the system to function.

And regarding the read-only system issue, use .imgs marked with VNDKLITE to make system rw.
[Treble-Enabled Device Development A/AB ROMS] myrmidon132:
Thanks for the thorough explanation, I'll try it out! I think I'm in luck regarding the read-only system issue, I (fully on purpose ofcourse...) took the vndklite image, so I'll first try removing some stuff.
[Treble-Enabled Device Development A/AB ROMS] tangy912:
You should also flash magisk to be able to modify system files.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
This just blew my mind....thought VNDKLITE builds were more for compatiblly and to be used with older versions of Android.

I have a Samsung tablet which also has a small system partition. My problem with that is that I'm unable to flash any larger GSIs other than the most vanilla of Lineage OS builds. If I were to flash VNDKLITE based ones, would there be a chance that GSIs a tad bit larger may flash properly?
[Treble-Enabled Device Development A/AB ROMS] fabioken:
Very good images, I applied the lineage-20.0-20230324-UNOFFICIAL-arm64_bgN-vndklite.img on my Galaxy Tab A7 Lite SM-T220 and works very well nad fast, but I can't see the Auto Bright button, can you tell me how to?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
make an overlay for it.
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
Installed lineage-20.0-20230325-UNOFFICIAL-a64_bgN-vndklite.img.xz

and updating the previous lineage 19. The wired headphones aren't detected just like the previous GSIs, and video thumbnails are corrupted but they still play. No volte and otg support as in stock. Help
[Treble-Enabled Device Development A/AB ROMS] AfiqAffandi:
Tested on my Samsung Galaxy Tab A 10.1 2019 on rom lineage-20.0-20230325-UNOFFICIAL-a64_bgN-vndklite

Wired headphone detected and there is no problem with the sound.

Video thumbnails and OTG also got no problem.
[Treble-Enabled Device Development A/AB ROMS] fabioken:
I'm New in It, How I do ano overlay?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
How to create an overlay?

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

github.com

follow this guide
[Treble-Enabled Device Development A/AB ROMS] Nodus Cursorius:
I also own the Galaxy Tab A7 Lite SM-T220! The link provided by Captain_cookie_200 is a great place to learn but I found it had a few confusing steps.

One example where framework-res__auto_generated_rro_product.apk simply won't cut it: because it depends on previous framework APKs filling in the other Samsung details.

Order of execution seems to be:

super.img\system\system\framework\framework-res.apk

super.img\vendor\overlay\FrameworkResOverlay\FrameworkResOverlay.apk

super.img\vendor\overlay\FrameworkResOverlayExt\FrameworkResOverlayExt.apk

super.img\product\overlay\framework-res__auto_generated_rro_product.apk

I won't write a replacement tutorial but I will share the fruits of my own labor with you. In the specific case of automatic brightness/adaptive brightness the options are not overridden by the above frameworks 2, 3, or 4. So it's straight from 1.

We'll need to pull three values from Samsung's super.img\system\system\framework\framework-res.apk and add them to the existing overlay for gta7litewifi:

res\values\arrays.xml

<!--
enable autobrightness configuration option
[Samsung] super.img\system\system\framework\framework-res.apk
-->
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>6</item>
<item>6</item>
<item>6</item>
<item>11</item>
<item>79</item>
<item>95</item>
<item>141</item>
<item>183</item>
<item>200</item>
<item>219</item>
<item>255</item>
<item>255</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLevels">
<item>1</item>
<item>5</item>
<item>6</item>
<item>50</item>
<item>100</item>
<item>500</item>
<item>1500</item>
<item>3000</item>
<item>4999</item>
<item>5000</item>
<item>19999</item>
<item>20000</item>
</integer-array>

res\values\bools.xml

<!--
enable autobrightness configuration option
[Samsung] super.img\system\system\framework\framework-res.apk
-->
<bool name="config_automatic_brightness_available">true</bool>

I've attached a Magisk module that will install this overlay with the above changes, which replaces the gta7litewifi overlay from LineageOS 20 TrebleDroid but keeps the other default values. Uninstall the Magisk module to restore the default overlay.

I would pull request these changes to LineageOS 20 TrebleDroid's Github but this has been a bad brain week.
[Treble-Enabled Device Development A/AB ROMS] fabioken:
Thank you so much, installed here the overlay and works great, thanks to Captain_cookie_200 too, by answering the question
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
So, it's device bug?
[Treble-Enabled Device Development A/AB ROMS] raselmx:
Should I flash this on my mediatek helio device?
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
Maybe the bugs are because of deleting the product partition?
[Treble-Enabled Device Development A/AB ROMS] sanjibukai:
Anyone else having this problem?