yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] veekay:
I edited my custom vendor to remove that line - no difference. Still so odd considering this device has no notch.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Baffling indeed... Run "grep -r -e config_mainBuiltInDisplayCutout /vendor" (or /product, /system) to look for any traces in weird places?
[Treble-Enabled Device Development A/AB ROMS] veekay:
Doesn't show up anywhere else, at least in the overlay I made. Could be another weird Samsung thing, like so many other issues.

In your custom build, can anything from that be moved over to other builds or is the custom part baked in too deep?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Digging into your forum posts, I see you have a Tab S6, and also see your demo screenshot in the AOSP thread. The cutoff clock (a Google bug, also dealt with in my private build) and off-center navbar buttons further reinforce my idea that it's not some weird offset (e.g. wm overscan) but likely a "notch". Can you look for the keyword "cutout" in logcat? I remember that DisplayManagerService would log things related to it.

The "feature" is (the removal of) a piece of code unfortunately. In future builds I might be able to make it controllable by a system prop.
[Treble-Enabled Device Development A/AB ROMS] veekay:
Tab S4, but almost the same thing.

So just take a logcat and look for that keyword?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Yes, cutout (if any) should be among the data DisplayManagerService reports about the display.
[Treble-Enabled Device Development A/AB ROMS] veekay:
DisplayManagerService: Display device added: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1600 x 2560, modeId 1, defaultModeId 1, supportedModes [{id=1, width=1600, height=2560, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities android.view.Display$HdrCapabilities@89c77d83, density 360, 286.449 x 286.197 dpi, appVsyncOff 1000000, presDeadline 16666666, cutout DisplayCutout{insets=Rect(0, 96 - 0, 0) boundingRect={Bounds=[Rect(0, 0 - 0, 0), Rect(1470, 0 - 1600, 96), Rect(0, 0 - 0, 0), Rect(0, 0 - 0, 0)]}}, touch INTERNAL, rotation 0, type BUILT_IN, address {port=0}, state UNKNOWN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}

That?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
cutout DisplayCutout ... Rect(1470, 0 - 1600, 96)

Yes. Your device reports a cutout bounded by a rectangle of size 130x96, which corresponds to the size of black strip you mentioned earlier.

Since you already offered plenty of info that point to its existence yet we haven't been able to pinpoint it, I'll consult an expert on overlay...

EDIT: Please show the output of "cmd overlay list".
[Treble-Enabled Device Development A/AB ROMS] cjprostar:
Can i flash with Android 10 (twrp display only super partition)
[Treble-Enabled Device Development A/AB ROMS] klausb65:
Is there another way to flash this img file? I always get the message <waiting for device> I've updatet all the drivers but noting works.

Laptop: Windows 10

Phone: Doogee X95 Android 10 go Edition
[Treble-Enabled Device Development A/AB ROMS] arko7123:
are you in fastbootd with fastboot reboot fastboot?

this bat solved for me

https://xdaforums.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
[Treble-Enabled Device Development A/AB ROMS] axelagustinc:
Can you give me the address of the file to modify the sound values? I hear it very under my speaker and I can't find the route. :(
[Treble-Enabled Device Development A/AB ROMS] klausb65:
Thanks for your help, flash is now working but I get an error

Failed Remote: This partition dosen't exist

Any solution for this error?
[Treble-Enabled Device Development A/AB ROMS] HSE172233:
Stucked at bootanimation in mobiistar C1 Shine Plz devlopers help me out.....
[Treble-Enabled Device Development A/AB ROMS] Mike Frayner:
Hi, I'm trying to install this on a moto g6 using TWRP. However, TWRP only gives me the option to install .zip files, and the ones in sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ are img.xz . Is there a way to install these using TWRP, or will I have to use a different method? I'm using twrp-3.4.0-0-ali
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Via fastbootd (or make your own super if you're a Samsung owner like I am).

At least tell us what command you used?

Sounds like you have some catching up to do with GSIs. Extract the .xz for the actual GSI image (.img), and in TWRP there's an "Install Image" button.
[Treble-Enabled Device Development A/AB ROMS] klausb65:
Hi Andy

I'm using the fastboot flash system command

do you need more information?

Thanks

Klaus

Edit: This is an Android 10 ge Edition, I need the low_memory parmeter set to false hope this works on your build

other question: Is it necessary to flash first the vbmeta.img file?
[Treble-Enabled Device Development A/AB ROMS] HSE172233:
Anyone has volte fix for this rom
[Treble-Enabled Device Development A/AB ROMS] Dildoman:
Is the8s ROM support overclocking , CPU, kernel etc?
[Treble-Enabled Device Development A/AB ROMS] HSE172233:
VoLTE Not working please help....?????
[Treble-Enabled Device Development A/AB ROMS] downhere:
Just use Search for VoLTE and LineageOS or AOSP.

It's been asked and answered plenty of times.
[Treble-Enabled Device Development A/AB ROMS] stark1296:
Hey [MENTION=4467696]AndyYan[/MENTION] thanks for this, running really great, just one weird issue - it starts to lag on my A51 (Exynos 9611) as soon as I select a custom configuration in live display, though it goes back to normal after moving back to default colour values. Not just lineage, I face this on all GSIs with live display.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Try the build.prop mod mentioned in OP - I had an Exynos 7904 (close to 9610 series) device before with the same issue and that did it.
[Treble-Enabled Device Development A/AB ROMS] ColdTriple:
Hi, everyone. First post here.

Clearly this is a significant project and I salute everyone who has done the work necessary to make this happen. Considering that you’re working against Google, more or less, it’s quite an accomplishment.

My situation is pretty simple, really. I have a Blu C5L (unlocked) and I would like to purge it of all proprietary Google code and use it mostly as an ordinary phone with messaging plus the option to side-load selected apps.

As I understand it, this means that I should install a custom recovery type, flash this generic distro, and never install the “gapps” package. Will I be able to do this for this device?

---------- Post added at 03:33 PM ---------- Previous post was at 03:09 PM ----------

Additionally, is there a straightforward way to take a complete and restorable backup, ideally with adb, dd, or tar?
[Treble-Enabled Device Development A/AB ROMS] Rohlfee37:
Hey, I am unable to mount/extract the .img file neither on Linux of Windows. I need the arm64_bvS's boot.img in order to patch it with Magisk. Any suggestions?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
GSI = Generic System Image - no boot, no vendor. Grab your stock boot image somehow (e.g. after flashing and booting this GSI, using built-in SU and dd).
[Treble-Enabled Device Development A/AB ROMS] nift4:
Depends - as this is based on phh-treble it should work relatively good but not everything will problably work.

You just use the custom recovery program to backup, it creates an bit-perfect .img file via the GUI.
[Treble-Enabled Device Development A/AB ROMS] HSE172233:
Can you provide me the link. Plzzz...
[Treble-Enabled Device Development A/AB ROMS] eremitein:
https://t.me/phhtreble/381476
[Treble-Enabled Device Development A/AB ROMS] shenery:
Can anyone point me in the direction of a twpr for the Nokia 2.3 TA-1206.

I would like to install this rom along with nanodroid.

If anyone can give me any pointers that would be great. Also can I unlock bootloader with ADB?

Kind regards

Steven
[Treble-Enabled Device Development A/AB ROMS] Yeslam7:
Hi dose this rom work with my phone is meizu note 8 unlocked bootloder and rooted
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
https://github.com/phhusson/treble_experimentations/wiki
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
A preview of what's to come...
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
Cool!

I'm ready to try :D
[Treble-Enabled Device Development A/AB ROMS] ogghi:
Any chance those GSIs would run on a Huawei Mediapad T2 10.0 Pro? Has Cortex-A53 which is Arm64 if I'm right...

Just managed to find one over here..could be used as display for home-assistant or so :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Too old, no Treble for you.
[Treble-Enabled Device Development A/AB ROMS] Legion495:
Hai everyone!

So my view here.

Got a BV9800 works good needed to resize the filesystem to get some gapps going.

As far as I can tell everything is okay except that open camera sees the 3 separate cams but that is okay.

On the BV9500 oh boi I fiddle around with it. As I wrote this it actually bootet lol.

I am still unclear what is up with it. Probably need to boot into the OS before adding any packages?

I skipped "modified" magisk by re-adding the boot img.

My steps currently are.

Systemimg

Resize the partition

Gapps+Magisk

I got a bootloop and reflashed the stock boot.img basically voiding that modified magisk.

I am not 100% I still try around but that modified magisk seems flakey on my end as far as I can tell.

Yes Aonly on BV9500. Works like a charm on AB.
[Treble-Enabled Device Development A/AB ROMS] HSE172233:
Modified Magisk not working on Mobiistar C1 Shine Plz help
[Treble-Enabled Device Development A/AB ROMS] Legion495:
I have to add my BV9500 now even refused the Stock ROM with SP Flash so probably was the phone to beginn with.

Had some issue with it. I was about to try the latest Magisk just to check. Either way only count on Magisk for AB release unless you are certain it will work.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Oct. security patch is here... Except technically we already have it, see explanation here. I'll still build a batch as usual, but I'm working on and testing some details of LOS18 as we speak, and that's of higher priority.
[Treble-Enabled Device Development A/AB ROMS] veekay:
Just wanted to follow up and was curious if your expert had any ideas?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Nothing yet (I myself am unsure if that command would even reveal the problem), will update you if there's anything new.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
First test build of LOS18 uploaded to SF, only for ARM64 AB non-VNDKLite for now (my metered 4G can't handle more).

This is a preview and NOT ready for daily use - LOS is still rapidly merging features, PHH is busy working on the GSI side of stuff, and Google in their yearly fashion has again broken a bunch of stuff with Android 11 (grrr), including things as crucial as device overlays.

It has been said many times, but for a new Android version, you're even more strongly advised to try PHH's AOSP first and identify/report issues there. On the other hand, even if you don't own a device of compatible arch, you can still try an AOSP build of your arch and get an idea of what's broken for your device at this stage.
[Treble-Enabled Device Development A/AB ROMS] PoochyX:
GSI has come a long way....

([emoji88]Omni Rom[emoji88])
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
:eek:

Despite the fact that the link has already been given, I will answer - look at my screenshot carefully again.

Into the lower left corner of the yellow frame.

:cool:
[Treble-Enabled Device Development A/AB ROMS] Abaddon:
Would this work with the Oneplus 7 (GUACAMOLE) Eg; camera, RIL, FOD?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Builders' stuff for LOS 17 has been uploaded to GitHub. Again, not the cleanest code, use only as a reference.
[Treble-Enabled Device Development A/AB ROMS] vimal0212:
Thank you brother.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
[MENTION=4467696]AndyYan[/MENTION]

Thanks so much. I ordered a Pixel 4 xl last week and when it arrives i will try this GSI.

And thanks that you provide builds without gapps and microG support.
[Treble-Enabled Device Development A/AB ROMS] champ784:
Probably a stupid question, but this should work on a tablet that's GSI compatible, correct?
[Treble-Enabled Device Development A/AB ROMS] Dr. Mario:
LineageOS 17.0 GSI image works great on Google Pixel (too bad the development on Google Pixel have been almost entirely abandoned, only very few new ROM, and TWRP may probably never be updated, but GSI really gave my phone another shot, and I actually like Android 10 OS).

Thanks for the Android 10 GSI.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Did you need to disable dm-verity for the boot or wasn't it needed?

I asking because i have a new pixel 4 xl and want to install the GSI tomorrow.
[Treble-Enabled Device Development A/AB ROMS] Dr. Mario:
For original Google Pixel, it's not necessary (boots just fine here), although for newer Pixel 4, I would say it's needed because of additional onboard security.
[Treble-Enabled Device Development A/AB ROMS] MrHomebrew:
I noticed only 2 out of 4 speakers are working on the Galaxy tab A 10.5.

Do we have a fix for quad speakers anywhere?

There are two speakers on the top and bottom and only the bottom are working.
[Treble-Enabled Device Development A/AB ROMS] popeye2468:
Can this be installed on the Galaxy tab a 10.1 2017 model please?
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Hi,

Can somebody explain shortly the naming system of the imgs?

I don't understand it really. I have a pixel 4 xl so i need arm64 ab and i want the vanilla version from the rom.

So which file must i download?

Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
This one - lineage-17.0-20191117-UNOFFICIAL-treble_arm64_bvN.img.xz
[Treble-Enabled Device Development A/AB ROMS] surfer30:
Nordicus, which version is for arm64_a ?
[Treble-Enabled Device Development A/AB ROMS] dhacke:
[MENTION=4467696]AndyYan[/MENTION]

I flashed the GSI (arm64_bvN) on my pixel 4 xl and it boots. Mostly basic functions work (and to my surprise camera too) but i have one big problem:

The process "android.process.media" is very unstable and almost not useable.

It crashes every time when i want to open the gallery or the camera wants to save a photo.

The same thing happens when i open the file manager.

And i can't get a usb file transfer connection to my Linux PC. The phone gets mounted when i toggle the option 'file transfer' but then it throws me out as soon as i want to access it via my linux pc.

NFC file transfer itself works but the phone can't save the file. I guess these two problems occur too because of the crashing process.

So it's nearly impossible to take files on my phone. Any idea how to workaround it? If not i can make adb logs so that it can be fixed as quickly as possible.

Update:

I tested the original GSI from phhusson on which this LOS 17 GSI is based. And there the process doesn't crash and i can move files from PC to phone.

And no gallery crashes, too. So it seems that the problems are related to the LOS 17 GSI.

I can make some logs tomorrow evening for fixing.

After that i will change to phhussons GSI as daily as long as the problem in this GSI Rom remains.
[Treble-Enabled Device Development A/AB ROMS] reynard1:
same problem
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
Next one :cowboy:

https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download

ps when installing this ROM on my Z17S, there are no active SIM cards...
[Treble-Enabled Device Development A/AB ROMS] MrHomebrew:
What is the best tool for unpacking, nodding and repacking a gsi img
[Treble-Enabled Device Development A/AB ROMS] Hawkiinz:
Nice rom !

But I've some lags with my MI 9 SE.
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Boots fine on LOS17.1 Q vendor. All work but RIL. XT1962-1, River
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Judging from your other reply in the AOSP thread, you get RIL there?
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Yes, but that's using stock Q vendor. AOSP 300F won't even boot on LOS17.1 vendor. Have not tried LOS18 on Stock Q vendor as need PC to fastboot install stock
[Treble-Enabled Device Development A/AB ROMS] adek89:
when I try to upload a package of gapps I get a message in twrp with error 70. I did a full wipe and still the same error. galaxy a8 2018 design treble
[Treble-Enabled Device Development A/AB ROMS] AmyClaraRose:
Did you resize system partition after flashing gsi
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
Tried LOS 18, manage to boot it to desktop on Wayne... So far can't seem to get Magisk to install both on AOSP R and LOS 18 GSI.
[Treble-Enabled Device Development A/AB ROMS] adek89:
No. How to get this ?

---------- Post added at 11:25 AM ---------- Previous post was at 10:53 AM ----------

@AndyYan

do you plan to make an 'official' los 16 ( android 10 ) for samsung galaxy a8 2018? you did for a3, a5, a7 and a8 2018 awaits XD. ?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The time to say goodbye to Magisk is nigh... Under the current situation of GSI and Magisk accusing each other of incompatibility, this seems a dead end.

LOS won't have an official GSI (probably never) due to the amount of hacks needed - it won't fulfill their strict charter on every device. BTW, LOS16 is Pie not 10.
[Treble-Enabled Device Development A/AB ROMS] adek89:
and I could have been wrong :), in the sense that I meant whether there would be a total fate of 17, not as a trable under a8 2018 :) and when I manage to flash gapps, the system does not boot. goes back to twrp after reset
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
I'll need some time to get used to the world without it. Anyway... Thanks for the new build!
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Does phone calls work for you? Who's your provider?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
To people who tried the LOS18 test build and got a bootloop, if you can grab a logcat, please provide it along with device name and vendor version - out of the 3 devices I've tested on, one has such a problem, and I have identified a cause specific to LOS, but I'm unsure if it's a quirk of this one device or common to a vendor version.

Also, dunno who tipped the test build to XDA Portal, a bit too early but thanks nonetheless.
[Treble-Enabled Device Development A/AB ROMS] adek89:
Fingerprint error

fter flash the system and gapps, when I want to add a fingerprint, I get a message that 'the screen lock method has already been changed' and when I try to add a fingerprint, it crashes me from the settings. ..
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I hate to sound like a broken record, but...

...you repeated your issue without proving it's unique to here. The fact that you're using a custom vendor only makes things worse - if you find out that the bug is common to PHH-based R, you can only ask the author to fix it.

For device-specific ROMs, ask someone who actually owns the device. Also, I wouldn't have relied on GSIs so heavily if I knew how to do device bringups...
[Treble-Enabled Device Development A/AB ROMS] bubba1601:
There's no TWRP for the lower end Nokia's, and so far there's no bootloader unlock either so you won't be able to Install anything.

Sorry

(I have UK Nokia 2.3)
[Treble-Enabled Device Development A/AB ROMS] KtownJeff:
[MENTION=4467696]AndyYan[/MENTION]

Moto G7 plus xt-1965 boots test build 18 on moto 10 vendor/firmware lake-user 10 QPWS30.61-21-14 a5a6c release-keysM636_13.45.02.60R

Everything works no patches or Gapps/mods installed
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
No SIM card. Just a phone I have lying around to try out.
[Treble-Enabled Device Development A/AB ROMS] HueyT:
RIL works on stock Q vendor
[Treble-Enabled Device Development A/AB ROMS] AyHenry:
Is it for all project treble device with compatible architecture or device specific?

Cos I want to flash it on my infinix note 5. I don't know if it's supported cos v17.1 works on it
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with October security patches... not really (see previous explanation). [Insert obligatory backup-and-test warning here]

Per suggestion, now using a more secure MicroG patch - MicroG users out there, please evaluate if this tightened security affects your usecases.
[Treble-Enabled Device Development A/AB ROMS] NisseGurra:
Latest Lineage installed nicely on my S20 G9810, mtp and auto brightness broken as always but rest seems fine, even 120fps runs
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
For all compatible devices, though not all of them would boot.
[Treble-Enabled Device Development A/AB ROMS] TyDyeXDA:
How do I know if I download the avS or bvS version?

edit: nevermind, I figured it out
[Treble-Enabled Device Development A/AB ROMS] rafik25:
Hello LOS 18 boot ok on pixel 4XL
[Treble-Enabled Device Development A/AB ROMS] Rush:
That's to be expected on Google's own devices

But good to know
[Treble-Enabled Device Development A/AB ROMS] :
OnePlus 8 with R vendor cannot boot, stuck at full white screen after unlocked bootloader warning. Phh AOSP boots good though.
[Treble-Enabled Device Development A/AB ROMS] SirRGB:
On Pixel 1st gen it is a little harder to boot GSI.
[Treble-Enabled Device Development A/AB ROMS] Rush:
Well, yea, but that probably due to Google having added treble with an update rather than release
[Treble-Enabled Device Development A/AB ROMS] SirRGB:
Yes, but I also have an OnePlus 5 and I think you can flash a GSI on that much easier. OP5 also came with Android 7 out of the box.
[Treble-Enabled Device Development A/AB ROMS] Rush:
I think OnePlus decided to use AOnly though

Google probably opted for A/B for the sake of staying faithful to what they made
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
You might benefit from a fix I made for Reno3 Pro R vendor a few days ago, given how close OPPO/OnePlus are these days. Try the next build when it comes.
[Treble-Enabled Device Development A/AB ROMS] Legion495:
I have a stupid question but I cannot find any infos.

So this is a img file for the system. I used to flash a zip for updates on official builds with TWRP.

I was wondering is it okay to flash this system.img over the previous one to update. Does this affect Gapps and such?

Or do I need to go clean System if I want to update this unofficial build?

Am I fine flashing over the old System?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If you're on a device-specific (non-GSI) ROM, I advise staying that way. Although it is possible to shift to GSI without wiping data (I did it on my K20P back when I was unsure which way to go), unexpected stuff might happen.

And unlike ds ROMs, flashing GSIs doesn't trigger addon.d, so take care of your /system mods yourself.
[Treble-Enabled Device Development A/AB ROMS] Legion495:
GEZUS (aha moment here)

They seem to generate just fine

In fact addon.d already has

50-lineage.sh

70-gapps.sh

99-magisk.sh

I seem to have made a huge mistake!

How the hell did I get a A/B to even start? xD I probably mixed my img files up...

Uh. Will be back and update this post accordingly. I think this BV9800 is a A only device
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
addon.d is there but I don't think it gets triggered.

Also note that the "AB" moniker in GSIs is not the same thing as physically having AB partitions.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
use Treble Info app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck