yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Installed the lineage-20.0-20230622-UNOFFICIAL-arm64_bgN-vndklite.img on my Sony Xperia 10 III (XQ-BT52) as well as the previous builds following this procedure:

Restore Magisk app

adb reboot bootloader

fastboot reboot fastboot

fastboot flash system lineage-20.0-20230622-UNOFFICIAL-arm64_bgN-vndklite.img

"Reboot system now"

Hide Magisk app again

But now some things on the device are not right at all.

The launcher app "Tab" (com.android.launcher3) hangs when I go to "Settings".

Shouldn't this be named "Trebuchet"?..

The icon for "Settings" (com.android.settings) is no longer a gear, but now the icon with the white Android head on a green background. Also, the app is now named "Loggar-Dat" in the app drawer.

When the app info is called from the context menu of an item, the background is transparent and simply overlays the previously displayed screen.

In the settings, some menu items are listed with completely wrong names. For example, the menu item that normally calls "System" -> "Backup" is now named "Restart" and shows a red icon instead of the cloud icon for backup.

What went wrong here and how can this be fixed?

"Clear Cache and Clear Data" for com.android.launcher3 and com.android.settings had unfortunately not brought any improvement.

Also not a reboot of the system as well as a renewed flashing after the described procedure.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
In addition some screenhots which shows the problems I mentioned.

The first one is the menu "Settings" -> "System" -> "Backup" which is here named "Restart". You can also see that the other menu items are named incorrectly.

The second is the app info for the Settings app, which is called up via the context menu and is here titled "Store logg...".

In the third screenshot, the app info is scrolled down a bit further so that you can see that it is actually still the app "com.android.settings".

If you open the app, you can actually access the settings.

I really hope someone can help me and explain how I can fix the error.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
This LOS20 is running perfectly on my Lenovo TB X505F.

At the moment, it is on security patch May 2023.

lineage-20.0-20230507-UNOFFICIAL-arm64_bgN.img.xz

I have also installed DeltaMagisk.

In developer-option, there is a point "DSU Loader" which is showing 2 Updates.

Is this something I should install, or something which I should never install in AndyYan's LOS images?

Now, LOS20 with security Patch June 2023 was released.

What is the correct way to update my Installation?

Is there anything I have to look for regarding Magisk?

Thanks
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
I think I have come a step further in the meantime.

I used adb shell pm list packages -f to display the locations of the apps com.android.launcher3 and com.android.settings.

From these paths, I then pulled the associated APKs like adb pull on my computer and then reinstalled using adb install.

The Settings app icon is now correct again and the Trebuchet settings can also be accessed again.

Some of the menu items in Settings -> System are now also correct again. Among them are the developer options, "Multiple users" and backup.

However, the items Buttons, System profiles and Status bar are still incorrectly labeled or have the wrong icon.

Possibly there are other errors that I had not noticed before.

Now the questions arise:

How can I correct the remaining errors?

Which system apps do I have to reinstall?

Or is there maybe a way to use a script do reinstall all system apps via adb without the need to manually pull each one of them?

How did the error occur and how can I avoid it in the future?

I have a second, identical device here that I would also like to update.

Since the cause and the complete solution for the problems have not yet been found, I will have to leave the smartphone on the old status.
[Treble-Enabled Device Development A/AB ROMS] djgje:
Hello everyone,

just a quick question, I've installed this GSI ROM on my device, but now I would like to know the best way to apply updates.

I would like to keep my data and just proceed with the update via, I guess, recovery menu?

Thanks in advance for your help regarding this,

Regards,

Jerome
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Reminder: although I check into XDA a few times a day, often I don't have time, condition (e.g. suitable test device), or simply am not in the mood to reply to posts. I also tend to silently skip posts that I can't provide a satisfactory answer for (lack of info on your side, or lack of skill on my side).

This really does sound bad, however I wasn't able to replicate on a test device by clean flashing it, and that device has special issues with dirty flashing anything so I can't test that immediately - will get back to you about it later.

DSU Loader (not to be confused with DSU Sideloader) just lists Google-provided images, these are not at all usable.

Simple, flash the update like how you flashed the first, just don't wipe anything.

w.r.t. Magisk, unlike device-specific ROMs, here updating only ever touches /system and shouldn't affect anything.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Since the apps that showed the described errors after the update were all system apps, and I had performed the flash process as usual, my supposition was that the error could be in the image.

Unfortunately, I have absolutely no idea what kind of error could lead to such an error pattern.

Maybe the info that a reinstall of the apps in question could at least partially fix the error can help track down the cause of the problem.

Thank You for that.

I'm perfectly willing to post a logcat or something similar, as long as it helps troubleshooting.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Have you verified that you have a correct download in the first place? SF offers hashes.

This month I initially uploaded corrupted Light builds, but someone was quick to point out, and I double-checked the hashes of both Light and TD between local build output and uploaded.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Thats a good point.

So I just downloaded the packed file again and checked if the checksum of the finished download matches the one from SF.

Then I unpacked the archive and compared the checksum of the originally downloaded .img file with the new one.

Again, both matched.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@psychofaktory Unable to replicate, 0507 dirty flash to 0622, same arm64_bgN-vndklite variant as you picked, on (I believe) the only test device that can boot vndklite that I still have.

Normally I would suggest replacing APKs, but as you clearly know the drill and has already done that, I don't have any more ideas other than just wiping and starting over...
[Treble-Enabled Device Development A/AB ROMS] Rumplestilzken:
I recently repo sync'd and my device/phh/treble has changed, even though the repo seems to not have been touched. The files i relied on ($(call inherit-product, device/phh/treble/lineage_arm64_bvN.mk) for instance) are no longer accessible. Any idea?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This file is generated at build time.
[Treble-Enabled Device Development A/AB ROMS] Rumplestilzken:
Thanks!
[Treble-Enabled Device Development A/AB ROMS] insestito:
Someone with this ROM using It on a Xiaomi 12T Pro?
[Treble-Enabled Device Development A/AB ROMS] Jonny:
@AndyYan apologies for the direct ping but there have been some reports of alarms not working for the current TD builds (no idea on light).

The solution is to add uname: 1 below set_tid_address: 1 of system/system_ext/apex/com.android.media/etc/seccomp_policy/mediaextractor.policy

So the last few lines of that file looks like:

set_tid_address: 1

uname: 1

@include /apex/com.android.media/etc/seccomp_policy/crash_dump.arm64.policy
@include /apex/com.android.media/etc/seccomp_policy/code_coverage.arm64.policy

Instead of:

set_tid_address: 1

@include /apex/com.android.media/etc/seccomp_policy/crash_dump.arm64.policy
@include /apex/com.android.media/etc/seccomp_policy/code_coverage.arm64.policy

Unfortunately, I am a bit unsure of where to add a patch for this at the moment but at least this gives the solution. This was what I managed to get by analysing logs and diffing the AOSP TD builds to Lineage TD builds
[Treble-Enabled Device Development A/AB ROMS] jianjin9987:
如何修复电话没声音How to fix phone no sound
[Treble-Enabled Device Development A/AB ROMS] Jonny:
I think the post above fixes it
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Attached are variants with the alarm/sound fix as of 03/06/2023 (UK date - this is the correct date format US viewers :p)
[Treble-Enabled Device Development A/AB ROMS] user2332:
I'm interested too.

Has anyone tried it?

Experience?
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Further to this it looks like a patch has already been created for TD, just not ported over correctly/missed to the Lineage builds - platform_frameworks_av 0027-Allow-uname-syscall-in-all-seccomp-This-is-needed-be.patch in TD.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I see. PHH and I thought dropping this patch (alongside one in fwb) would be no problem; I'll raise this with him.
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Apparently not! 🙂 Certainly on the devices I own (which all happen to be mediatek devices, no idea if this has anything to do with it) alarms and choosing alarm sounds do not work without this patch.
[Treble-Enabled Device Development A/AB ROMS] insestito:
Not yet. If you install it tell me...
[Treble-Enabled Device Development A/AB ROMS] tellko53:
Hello. I have problem with camera flash. When taking picture in a dark room, the flash is initiated, but it blinks, meaning flashlight turns on, then turns off, then turns on again, picture is taken, but the picture is black. Is there a fix for this please? I tried different camera apps, always same problem. Was working fine on stock rom.

Phone model: Cubot Pocket 2022
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I believe the LOS camera app ("Aperture") has a 4th flash-always-on mode that combats just this.
[Treble-Enabled Device Development A/AB ROMS] insestito:
Something for fix sms on Xiaomi? (12T pro)
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Have you tried "Install IMS APK for Qualcomm vendor" in the PHH Treble Settings under "IMS features"?
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Any plans to support Substratum Lite in the future? Regular Substratum works partly, but it's been deprecated
[Treble-Enabled Device Development A/AB ROMS] Rumplestilzken:
Now i'm getting

FAILED: ninja: out/soong/build.ninja:31009641: unexpected NUL byte

18:41:40 ninja failed with: exit status 1

out/soong/.intermediates/frameworks/native/libs/gui/libgui_aidl_static/android_arm_armv8-a_cortex-a53_static/gen/aidl/android/gui/

This is the line in the ninja build file. All the others seem to be files and end in $. This one is a folder and does not end in $. I tried to look at the contents of the folder, but it doesn't seem to exist.

All i did was repo sync and these issues started to occur. I have since pulled down the repo from scratch. If i can't fix them, i can't get the new release out when the next security patch comes. Any suggestions would be appreciated.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: it seems that the 6-22 build has broken Bluetooth functionality with PlayStation 4 controllers. I can pair it but no game will recognize it, including emulators that it was working with on the 5-7 build, like AetherSX2. Has a commit been made that would affect this in some way?

Can someone else try and verify? Just test with any free game app that is known to support controllers.

I can't test with a comparable controller like Xbox One, since I dont own that console.
[Treble-Enabled Device Development A/AB ROMS] insestito:
Yep, it not work for me... (sms)
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
IMS is only for VoLTE, it wouldn't have any effect on text messages. The "v" in "VoLTE" means "voice".
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
I had the same problem.

Regardless of the VoLTE status, I could not send SMS. Receiving was possible and also sending via RCS.

The problem was fixed by installing the IMS APK.

Therefore, there must also be a relationship to text messages here.

In addition, the menu items for VoLTE and wifi calling were added to the settings when the APK was installed.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I can't relate, since texts (plain SMS) have always worked for me on gsis, whereas VoLTE has never worked regardless of the gsi I use. And the IMS apk does nothing for me, I didn't see a change after.
[Treble-Enabled Device Development A/AB ROMS] insestito:
This problem is almost on Xiaomi i think...
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
There's this bug whereby if an app stops responding, the dialog keeps popping up over and over even after the apps resumes normally, how to fix it?
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
you can add this line to prop file or with magisk module

ro.hw_timeout_multiplier=3
[Treble-Enabled Device Development A/AB ROMS] tellko53:
Hello. I noticed something weird. I used my phone all day today, the battery dropped from 80% to 40%, but in "Battery Usage Settings" apps usage show only 1% each. Did i mess up some settings or what could be the cause of this?

Edit: Nvm. I know where was problem now. Battery stats reset after reboot.
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Incorrect, IMS is for all communications, calls, SMS, VoLTE etc...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Then why do my texts/calls/data work fine, even though VoLTE has never worked for me on a gsi? I mean, once i make/receive a call, the call works, but data completely drops until the call is over. On stock firmware, VoLTE does indeed work for me, just not on gsis.
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Ah yes, the great argument of "because this works for me, it must work for everyone else"... wake up. This doesn't apply in GSI world, even on the same vendor and/or SOC. Take a look in /system/bin/rw-system.sh for some literal device-specific workarounds to get things working.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I wasn't making an argument, so no need to be a sarcastic smartass. I was LITERALLY just asking you a question, nothing more. And no, my line of thinking isn't "because this works for me, it must work for everyone else". I'm not ignorant, I know better than that.

Good idea about checking rw-system.sh though, I'll have a look.
[Treble-Enabled Device Development A/AB ROMS] stanley321:
Thank you for this GSI ROM, this is working great for my Pad 5 Pro 12.4
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
Bluetooth do not hear sound, also during the call does not go speaker or microphone Samsung A6. in version LOS 19. 18 all functional. I installed android_13.0.0_r63 CI-20230706 TD and there was nothing I could do. My phone stuck in Orange Recovery-no recovery, no Odin Mode, nothing could be done. thanks a lot @phhusson . The battery can't be removed and before my phone turns off, recovery picture would burn OLED. That was the first phone I bricked.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
This is not Andy's or PHH fault, you should have confirmed that the A6 supports A13 and/or the GSI build wasn't too big for the smaller system partition your device has

It's been years since any Android device has included a removeable battery. You need to wait for the device to drain completely before trying again if it is truly bricked. If not, then you can just restart, reboot into fastboot and try again
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
It happened to me on this rom https://github.com/TrebleDroid/treble_experimentations/releases The phone didn't want to boot into either Recovery or Odinmode, and the computer didn't recognize it, so there was no other option. But it happened only after I deleted the system in Recovery, so there must be some fatal error. man, I know how to get into recovery and odin mode, I rooted hundreds of phones, Then the only option is to let the phone discharge, but the A6 has an OLED display and the stuck Orange Recovery logo would be burned there, because the display is OLED technology. LOS2O and another roms use this port, but it is full of bugs. damn.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
If you've rooted hundreds of phones (really?), then you'd know that deleting the system partition and not flashing anything afterwards or doing proper wipes would lead to a bricked device

I'm not sure what you're talking about with OLED and recovery burn in logo, but that has nothing to do with the state that you're in now.

So again, wait till the battery is fully discharged and confirm that A13 builds are compatible with your device. If not, stick with LOS 18 or 19
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
Because the phone only booted into Recovery IMG. There was no bootlop no option, but only the image of the squirrel (Orange Recovery) remained. How do you want to do something when your phone isn't responding? You don't have recovery and you don't have Odin Mode. Samsung does not boot like a Pixel. Even though I knew exactly the key combinations for recovery and odin mode, I only got to the picture of a squirrel. WITH NO OPTIONS. stuck on this.That squirrel would burn beautifully there.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
So then boot or flash the IMG file for Orangefox to fix it so you can get back into that recovery and then have more options to get back up and running. But I'm gonna stop now since this is going way OT
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
no key combination for forced reboot? Like holding vol- and power?

It's impossible to break device by flashing system partition, so you have no one to blame except yourself
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
no nothing. only reboot to stuck image recovery with no options.

volume down and power reboot to stuck image

volume down and power reboot than volume up reboot to stuck image

every options go to stuck image. I couldn't believe it.

before that i installed this rom. after that i went to recovery. wipe data, cache, system. and reboot to recovery. booom.....I knew exactly what I was doing, I think so. So I decided to open the phone and broke the display. Now I have to use my iPhone before I get a new Pixel.
[Treble-Enabled Device Development A/AB ROMS] DarkestSpawn:
Is the SM8550 fix implemented in your 20230622 builds, or will we wait for your version based off of the 20230706 TD build?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This is a carrier thing - some chose to sever 2G/3G to save resources, and run calls/SMS/etc. on LTE. One of the Chinese carriers (CT) doing so is what spurred me to look into VoLTE on QCOM AIDL last year...

Yeah I hate that, I wish this proprietary sh_t never existed, or Google could at least add VoLTE to their xTS-on-GSI testing, so that something this basic wouldn't fail on GSIs. Likewise for FOD/UDFPS.

Supposedly yes, but Jul update isn't far off anyway, might as well wait one. cc @Veiranx
[Treble-Enabled Device Development A/AB ROMS] DarkestSpawn:
I did end up trying via DSU both TD 20230622 arm64_bgN and light 20230621 arm64_gN and was not able to get the Radio Functioning on either version on NX729J (Redmagic 8 Pro+ with the SM8550 SoC). I installed IMS (Code Aurora via Treble setting) and set my APN settings. Data worked but I could not get IMS registration to work for receiving SMS/MMS. I can reboot it if you would like a Logcat, or I can wait and try again when a newer build comes out.
[Treble-Enabled Device Development A/AB ROMS] mouseracer:
Hello, @AndyYan!

It is with great enthusiasm that I am reporting that flashing the new version of the GSI has fixed the "setup crashing" bug for OnePlus Nord N10!

I am now finally able to use this great GSI!

Thanks again, Andy!
[Treble-Enabled Device Development A/AB ROMS] DarkestSpawn:
Interesting thing I just came across, when booting from Stock ROM to DSU, radio gets stuck on WCDMA and will never change even if I change it through Radio in phone testing or Network in Settings. When I boot back into Stock ROM it follows me there. Had to pull the SIM, flash modem image and it partial returns to normal. Still trying to get it back to normal
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
try app "Network Signal Guru"
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]

I just realized that I haven't included PHH-SU app in *S (while I did over at Light) - this has been corrected.

@Jonny - although I still very much doubt that the uname change is related to the alarm, adding it back is trivial, so now it's back.
[Treble-Enabled Device Development A/AB ROMS] Jonny:
Can confirm alarms are working with this set of builds, as for the patch itself... compare my images with yours using a diff tool, the only thing that stands out is the uname stuff, I've also done a/b testing with and without it as I explained privately so I can pretty confidently say that the alarm stuff is caused by that, why I have no idea but it does.
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
Video thumbnails are missing, how to fix?
[Treble-Enabled Device Development A/AB ROMS] sunny_moonasd:
good job
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
pixel 2xl not booting. I tried everything.

Reboot into fastboot mode.

Wipe your data partition: fastboot format:ext4 userdata

Clean cache and factory reset: fastboot -w

flash the GSI: fastboot flash system_a path/to/system.img

flash the GSI in other slot: fastboot flash system_b path/to/system.img

Test boot.

If it doesn't boot, download vbmeta for your device and flash in fastboot mode.

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

fastboot -w

it gets stuck on android logo.

Releases · TrebleDroid/treble_experimentations

Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations

github.com

system-td-arm64-ab-vndklite-vanilla.img.xz

can someone fix it?

update>

so I installed an older version of system-squeak-arm64-ab-floss.img, but my signal and wifi is not working.

With this version of system-squeak-arm64-ab-vndklite-vanilla-secure.img I have a signal, but again I do not sound, Too bad none of those versions are finished for the Pixel 2XL, The last one was tested on Android 8, So my question is what is the best current phone to flash GSI? phhusson
[Treble-Enabled Device Development A/AB ROMS] tellko53:
Hello. I have a question. What is this setting in developer options and why is it on for LineageOS? Also what exactly is it checking in the background?
[Treble-Enabled Device Development A/AB ROMS] zezinho7:
hi. great work!

installed the latest td lineage os 20 vN (vanilla and no root) to my Galaxy S22. Runs great (thx so much) with one big problem for me:

"CyberArk Mobile" App directly recognizes rooted device after starting it.

LOS is configured the same as on my op8pro, there it still works:

magisk zygisk + denylist

cyberark in shelter

any idea what i could check or which part of the rom could cause this.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Without getting into how this works along with your system, it's not LOS exclusive...it's been a part of Android for a long time
[Treble-Enabled Device Development A/AB ROMS] tellko53:
I know its not excluvise and that it has been around since oreo, still doesnt answer my question, what is it checking in the background... When i turn it off, it randomly turns itself back ON when i restart phone. Should i be worried?