yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Perhaps I'll try again later. Your gsi is still installed as a DSU, I still haven't discarded yet. But the notification to boot into it is now gone because I swiped it away. And it doesnt return after rebooting. Any way to make it appear again? Or otherwise trigger booting the DSU ROM with a command?

Does Samsung build their kernels with pstore enabled? Because mine is just the stock kernel, boot.img patched with Magisk Delta. I haven't felt that there is a need to run a custom kernel. There aren't any for my specific models that I'm aware of, since the Korean versions of the Note 20 Ultra/Tab S7+ are the rarest models and have the least users. I would need to compile myself. I've given that a go before on some older devices, the results were mostly bad. I don't have much experience with kernel compiling.

Edit: pstore appears to be enabled in their kernels on my devices. Checking the directory (while booted into Android) reveals 2 files.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I just installed the gsi again via DSU. I'm attaching a zipped copy of the log I found in twrp. It was the only file I found in that directory, and it may or may not have relevant info. It could be twrp's kernel log.

Edit: I believe it's the right log, because it says this at the end of the file:

[ 6.409328] [0: init: 1] reboot: Restarting system with command 'recovery'

[ 6.409349] [0: inip: 1] Going down for restart now

[ 6.409361] [0: init: 1 (sec_debugset_upload_magic) 0

[ 6.409371] [0: init: 1] sec_debug:sec_debug_set_qc_dload_mabic() on=0

[ 6.409498] [0: init: 1] set_dload_mode <0> ( ffffff800880b760 )

[ 6.409939] [0 inht: 1] PM0: PON:41 ON:80 POFF:02 O:80 F1:40 F2:00 S3:00

[ 4.409939 [0: in)t: 1] @m2: PON:20 ON:80 POFF:01 O:80 F1:00 F2208 S3:00

[ 6*409839] [0: )nit: 1U PM4: PON:20 ON:80 POFF:01 O:80 F1:00 F2:08 S3:00

[ 6.410682] [0: i.it: 1] (sec_debug_update_restart_reason) reboot cmd : recovery

Rebooting into TWRP is what happened on all the times I tried.
[Treble-Enabled Device Development A/AB ROMS] Glowez_:
Hello, I don't know if there already is a solution for this but after searching for some days i still can't fix my problem so I'm asking here, does anyone know why bluetooth headphones on my redmi note 10s connects succesfully but the sound is played on the phone speakers? Thanks
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Try this.

https://xdaforums.com/search/53595549/?q=bluetooth&t=post&c[thread]=4517345&o=relevance
[Treble-Enabled Device Development A/AB ROMS] Glowez_:
well i tried all i could find but nothing worked
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
yeah we can. is working great on my old lavender awaken os a14 :), but not on my halo lineage os a14 ):
[Treble-Enabled Device Development A/AB ROMS] sso003:
Just updated to the 2024-01-12 build; lineage-20.0-20240112-UNOFFICIAL-arm64_bgN on a Lenovo Legion Y70.

As far as I can tell, everything is working as expected aside from previously known issues, no regressions.

Not working: 5G (known GSI issue), auto-brightness (known device specific issue).

Thanks again @AndyYan. I've been daily driving your GSI builds for almost a year now.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
buddy do you know if it's safe to dirty flash over 20-20230622-UNOFFICIAL-arm64_bgN?

or better yet: do you have ways to test a ds4 controller on it?
[Treble-Enabled Device Development A/AB ROMS] sso003:
I only ever dirty flash.

adb reboot fastboot

fastboot flash system system.img

reboot

badabing badaboom. No issues.

As for a DS4 controller, sorry, I don't have a DS4 to play around with.
[Treble-Enabled Device Development A/AB ROMS] sso003:
Maybe this?

https://www.reddit.com/r/AndroidGaming/comments/32p33c
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
sadly no. that thread refers to remapping an already working ds4 controller.

i want that so bad. some said a14 got dat already fixed. did you ever tried some a14 on your halo?
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
hey thanks for that. just dirty flashed 20240112 over 20230622 with no dramas.

sadly ds4 remains the same. rain of logs of no success acknowledging ds4.
[Treble-Enabled Device Development A/AB ROMS] kluknawa235:
I Try lineage 20-slim on mediatek Helio A22. Must use adb shell command to correct work wifi and mobile data.

after this rom works good.

On google play say device is not certicated. but here just device registration google via ID and after this all works normally.

thanks for your work
[Treble-Enabled Device Development A/AB ROMS] Mr. Hase:
can you give me a step by step instruction for adb shell commands? :)
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Any idea how to enable haptic feedback (vibration) when pressing navigation buttons? Same GSI on Unihertz Jelly 2 has haptic, new Jelly Star not.

And something more: Why is this the only GSI that boots up on my new Jelly Star (Mediatek Helio G99). On the older one (Jelly 2, Mediatek Helio P60) much more GSI roms boot up. Maybe someone knows the techncal details?
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Ok if noone answers how can i find out the changes done btw.

lineage-20.0-20231116-UNOFFICIAL-arm64_bgN.img <-> lineage-20.0-20231214-UNOFFICIAL-arm64_bgN.img

?

With lineage-20.0-20231214-UNOFFICIAL-arm64_bgN.img it startet wordking on my phone.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Same issue here, but different model.

@myballgotkicked Your command didn't worked.

@AnonVendetta Hey buddy, did you have any idea how to fix this problem?
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Have you fixed it? Same model here.
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
sure problem was custom kernel.
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Sorry, should've read.

Great work btw! Flashed on a Tab A7 Lite. Might even flash on a Mi Pad 6/Poco X5. :D
[Treble-Enabled Device Development A/AB ROMS] ttritium:
I have a Jelly Star too, and unfortunetely don't know why only AndyYan's LineageOS works on our phone.

Just a thing if you try to know what is special with its GSI. 20230815, 20231116, 20231214 and 20240112 vanilla releases work, only 20231017 and before august (vanilla too) ones don't work. Maybe you can find an answer here or here.

Other point, I tried to investigate the question and found a way to boot TD's A14 releases and AndyYan's LOS A14 testing release, you can find it here, if it can help you.
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Thank you very much. The guy seems to have EXACTLY the same issue like me/us.
[Treble-Enabled Device Development A/AB ROMS] ttritium:
Nothing.

The answer is maybe more here.

You can also find another GSi that boots natively here.
[Treble-Enabled Device Development A/AB ROMS] 吃兔兔打豆豆:
I have a smartison Nut pro2 phone.

The phone's official firmware is stuck with Android 7. Fortunately, there are developers who have made Android 11 support treble rom, based on pe. Unfortunately, using the GSI system image of lineage, it will get stuck in the boot animation and cannot successfully enter the system.

The log file cannot be obtained because the system cannot be accessed.

Can you teach me how to solve the problem of getting stuck in lineage animation or can you teach me how to get logs to solve this problem

Thanks a million
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Does Face unlock work on this release? Can't test it myself right now. :-(
[Treble-Enabled Device Development A/AB ROMS] Ajaybabu07:
Please provide core gapps inbuilt with it i dont have working twrp request to dev

Built a gapp based gsi give at least playstore
[Treble-Enabled Device Development A/AB ROMS] ttritium:
Sorry no.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I have DualShock 4 (PS4), DualSense 5 (PS5), and Xbox One controllers. On the latest LOS 20 builds, DS5 and XBOne works, not sure about DS4. But the last time I tested DS4 with this GSI, it didn't work. That was about 4 months ago, just before I bought a PS5 Slim.

I also commented on it in a GitHub bug report that someone else opened.

All of my controllers are original controllers, not 3rd party controllers.

I don't own an XBox One, and never have, I only use that controller for playing PC games. I've always been a Sony loyalist when it comes to the console wars, and have been ever since the original PS released in the mid 90s.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
hey mate are you dirty flashin andy yan's latest lineage-21 release atop of lineage-20?
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
ok then hey @AndyYan you call it safe to try your los21 dirty flashing atop of los 20?
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
Same question clean install better for LOS 21 or just an update - dirty flashing?
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
based on recent releases i was expecting more activity here, which suggests that there is another place where andy is more active. anyone confirms that?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Am I the only one with a bootloop? Note 20 Ultra 5g on the latest stock Android 13 firmware. The LOS 21 2-1 build just tries to boot, then loops back to my primary LOS Android 13 gsi. The same thing happens with Phh's Android 14 1-30 build. I used DSU Sideloader to install. I'm not going to bother flashing "for real", because in my previous experience, if a DSU ROM bootloops then the results will be the same for a native install.

Other Android 14 gsis have previously worked on this device, but texting hasnt worked (always the same "error code 0, failed to send", regardless of gsi tried). This is the only reason I can't move from 13 to 14, because I need texting working on my primary phone. I just wanted to try again to see if anything had change, but can't test further due to the bootloops.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
so, you post presented me dsu sideloader. i tried it, and managed to boot los 21 without issues. and ds4 joypad is working flawlessly on it! good findings! ty @AnonVendetta! now i just need to backup my current stuff so i can dirtyflash los21 over los20 and try the luck.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
just dirty flashed los21 over los20 and got things working so far.
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
Cheers mate I just did it, dirty flashed on my Lenovo tablet, everything works fine but Bluetooth...is Bluetooth working at yours?
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
yeah is working perfectly. maybe a reset network settings should do for you?
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
What's your tablet or mobile phone? Mine is TABLET LENOVO TAB M10 PLUS TB-X606F
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
lenovo legion y70
[Treble-Enabled Device Development A/AB ROMS] sso003:
Haven't tried yet. It's my daily driver so I'm a bit hesitant to go from L20 to L21 by dirty flash. And it's a lot of work to re-setup all my apps and whatnot from a clean install. I haven't made the jump yet.
[Treble-Enabled Device Development A/AB ROMS] hanichl:
Flawlessly installed Android 21 over 20 fromTWRP, (dirty flash ). Afterwards cleaning Cache and dalvik-cache.

Starting and running Like a Charm :)
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
Actually i did it and worked flawlessly! @hanichl above succeeded too!

Something i realized: while TWRP i've got can't handle huge USB devices but Orangefox can, Orangefox i've got can't handle this flashing, but TWRP can.

I had to go for orangefox to backup boot/data/super to a huge usb device, then return to twrp before flashing.

if someone has a twrp version capable to format and use usb properly let me know.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with February security patches. [Insert obligatory backup-and-test warning here]

On Chinese New Year vacation and away from most of my devices, the testing I could do was even more limited than usual - exercise extra caution.
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
I don't have haptic feedback on my hardware buttons. Can it be fixed? (Device Jelly Star)
[Treble-Enabled Device Development A/AB ROMS] seyren00:
Hi, I installed the gsi in my poco x3 gt, but the only thing I can't fix is that I can do calls in VOLTE but can't receive them (3g and 2g works good, only volte not working).
[Treble-Enabled Device Development A/AB ROMS] juanes10201:
I installed the rom and I noticed it is signed with public keys. Can this be a security risk using the precompiled roms uploaded to sourceforge?
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
anyone successful installed/upgraded to L21 on an Samsung SM-T510 ?
[Treble-Enabled Device Development A/AB ROMS] Valfore:
Hi!

i freshly installed LOS 20 on my A14 5G, it boots but as soon as i apply Play Integrity Fix Module with Magisk 27.0, some apps like Gmail and Wallet will instantly crash, this also happens with LOS 21 and Kitsune Mask, not really sure why, it seems like a problem exclusive with LineageOS too since i was able to get it to work with Pixel OS 13 GSI, any ideas?
[Treble-Enabled Device Development A/AB ROMS] Eula13:
try turning on spoof system properties in treble settings, reboot and reinstall those apps.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Nowhere actually, I'm just as inactive on TG (heck I didn't even create my own group), and GitHub is basically code/push-only.

Do you have haptics at all (e.g. long-press power, notifications)? If yes, it should be fixable with a device overlay that rewrites the haptics pattern for keypresses, although I've never written that part myself.

It can be, but then again most unofficial device-specific builds are pubkeys too.

Signing and migrating keys with GSIs haven't been documented, and I lack the incentive to explore.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
I see that Lineage team usually implement that trough the "settings put global lid_behavior 1" magic. This doesn't work on the LOS GSI so it seems to miss something inside.
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Yes, haptics work in general, but not with the touch hardware keys. If anyone knows how to create that "overlay" please get in touch with me. Thx.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I saw from mail notif that you said it works on Peter's image - I know he owns a Jelly Star himself, that's why. He takes a similar approach to "Light" though (backwards - he inspired my "Light"), so there's probably an overlay or fix in his sources that's not pushed to TD.
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
I think i found it. This should be the fix that Peter created:

android_device_peter_gsi

android_device_peter_gsi

gitea.angry.im

Now how can we migrate this to your ROM @AndyYan?
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
Yes, me !

dirty flashed on 20
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Seeing this comment angers me. Your device is older than both of mine (Tab S7 Plus and Note 20 Ultra), and yet you can boot LOS 21, whereas for me no Android 14 gsi newer than mid January 2024 will boot. I have no idea why, and I'm starting to not give a f about testing new gsis or reporting bugs/inability to boot. It's a crapshoot if you ask me. I even temporarily went back to stock Samsung ROMs for a few weeks, only to become gradually more and more pissed about the spyware/bloatware that never seemed to stop running.

I've had no issues booting any android 13 gsis, including the latest LOS 20, or phh's A13 gsis. Some older A14 gsis also worked, but texting didn't work. And then in January I suddenly found that newer releases wouldn't boot anymore.

At this point I'm more inclined to distance myself from further participation on XDA, or getting involved in Android development discussions. It's all very disillusioning. Although I suppose that some more recent negative events have made me more bitter and less willing to explore or contribute. I'm very tempted to settle for LOS 20 in the long run and throw in the towel. I had it running very smoothly and relatively bug-free, about as close to stock stability that i've ever gotten from any gsi. There's lots of other things I'd rather be putting my time into. As it is I don't log into XDA very often, or even come here to read what others are saying.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with March security patches. [Insert obligatory backup-and-test warning here]

LOS upstream merged their own way of allowing signature spoofing, see Gerrit for details; most TD-based GSIs will gradually switch to using this one, though with the debuggable requirement removed. For those who are using MicroG for the intended purpose, it should be a seamless transition, and perhaps even allow you to install MG as a user app.

On the building side, a long overdue change is TrebleApp is now patched and built on the go. New builders no longer have to scratch their heads over a prebuilt that breaks almost every month.
[Treble-Enabled Device Development A/AB ROMS] sashavujacic:
Can not receive SMS on my Samsung A23.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I'm unable to boot almost all Android 14 gsis dated after January 29th. Including your LOS21 builds. The google official gsi A14 builds boot, but nothing else, I've tried them all. I've submitted a bug report on phh's github, with logs attached for last_kmesg which I found in /proc. @phhusson suggested I try to find a log in /sys/fs/pstore, but that directory is always empty when I check it in TWRP. I've followed his advice to put device in fridge (in a sealed ziploc bag, to prevent water from getting in), but no dice, that directory is always empty. Do you know what other log files I can submit for a not booting gsi? I know that you use a lot of the AOSP code in LOS, so its safe to assume that if his similarly dated gsis won't boot, then neither will your images.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've heard a speculation that it's a fix for S24 around that time that might've caused that. If you're okay with trying a one-off test build, I can make one with that reverted, but only after the QPR2 sh_tstorm settles (LOS just merged it so I can't easily go back :/).
[Treble-Enabled Device Development A/AB ROMS] I-am-Gaming:
@AndyYan everytime when I turn on my Lenovo Tab M8 it shows this message "This build was signed with public keys " . How can I disable this without disable notification?
[Treble-Enabled Device Development A/AB ROMS] kishin151:
samsung a05 mtk g85. Doesn't see the second SIM card. I installed different versions of los 20 firmware, it did not help. Upd. Maybe the card slot is dead
[Treble-Enabled Device Development A/AB ROMS] david7xw:
Open trust (the app in notification list), scroll down, turn off its notifications
[Treble-Enabled Device Development A/AB ROMS] pbonamy:
Hello, how you do that?
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
flashed

- Magendanz TWRP

- his LOS 19 or the other

- via TWRP without formating DATA Andy Yan's LOS20 to System

- via TWRP without formating DATA Andy Yan's LOS21to System
[Treble-Enabled Device Development A/AB ROMS] pbonamy:
Thanks
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
My comment #1042 seems outdated (as I'm currently got aware of)

take a look at:

[ROM][SM-T510][UNOFFICIAL] LineageOS 20.0 for Galaxy Tab A 10.1 (2019)

In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 20.0 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 20.0 GSI. It's very much a work...

xdaforums.com

- flash @Magendanz LOS 20 with TWRP (included) via Odin in one step !

- and if you want get rid of Google Apps see: Comment #12 and maybe #59 in the here provided link
[Treble-Enabled Device Development A/AB ROMS] luna00:
Does 5g work on this rom
[Treble-Enabled Device Development A/AB ROMS] kaazoo:
Hi, I faced the problem that receiving SMS didn't work after using this GSI combined with latest vendor firmware on Samsung Galaxy S20 FE 5G and wrote a small howto on how to extract the required files (libsec-ril.so and libsecril-client.so) from an older Samsung firmware version and got it working on my device: https://kernelpanik.net/fix-sms-reception-on-samsung-s20-fe-5g/

@ Andy Yan: Thanks for making this GSI!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
It seems we've faced the same issue, except my not receiving texts issue mostly happened on Android 14 gsis (both sending and receiving). I may try your solution later, but ATM there's no need to.

Edit: I'm about to test on my Tab S7 Plus. It is a 5g tablet and has a full voice line from my carrier. Months ago, texts stopped working on it, so I signed up for a cheap text line through an app. I found an older firmware dated May 2023, on samfw.com. I can't directly downgrade to it, due to an anti rollback provision introduced in the last few firmwares released after it. But I think that simply replacing those 2 files might work.

On my 2nd device, a Note 20 Ultra 5g, all stock firmware builds after N986NKSU2HWE8, have broken texting when running any gsi. So for now, I've just downgraded to that build, there is no anti rollback provision that would stop me from flashing older builds. I'm very tempted to upgrade it to latest build, flash a gsi, then replace those 2 files. I'm quite curious to see if it will work. But I can't just yet, due to needing texting working for work purposes. So it will have to wait until the weekend when I'm not working and can afford the downtime.

Edit #2: Tested and working on the tablet 100%, no noticeable downsides. Texts both send and receive successfully. Now I can finally cancel my sub. I didn't follow any of your steps as listed in your blog. I didn't even use a PC, all done on device only. But I did rename the original files and copy the new ones, followed by setting correct permissions and SELinux contexts. The tests were done after rebooting.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]

20 will move to quarterly from here on out.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Does this varient boot on kernel version 4.9
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
One of my devices has 4.19 stock kernel, which is only a bit higher than yours. It boots this LOS20 fine, but not LOS21. You have Samsung?

As with many other things on XDA, testing for yourself may be the only definitive way to get an answer. Try it and find out.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
hey @AndyYan and everyone how can i retrieve boot.img from yourrom.img.xz?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You cant. Gsi ROMs only provide a system image. Boot.img comes from your stock firmware, or from a custom kernel, if you've installed one.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@AndyYan how long does this gsi security patches supported
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
For as long as the gsi keeps getting updates, probably. Which @AndyYan has recently stated, will now be quarterly updates for LOS20. Presumably, the wider gsi community is shifting focus to Android 15. And LOS21 will become new focus for OP. That's just how Android seems to work, as soon as there is a new major milestone release, older Android versions get left behind. Which is fine for me, because LOS20 is very stable. I wont even bother trying LOS21 again until LOS22 hits, because i currently cant boot 21 anyway. I think that by letting some months pass before trying again, hopefully the booting issues will self-resolve. Clearly, 21 has issues for some devices. I also cant boot other Android 14 gsis released after January 29th, except Google's official gsi.