yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Hi, I'm bootlooping. What's causing it?

ro.system.flac.frame_rate = false
third.party.apps.frame_rate = 60/90
ro.amdroid.active.frame_rate = 60/90
net.tcp.buffersize.default = 4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi = 4096,87380,256960,4096,163 84,256960
ro.ril.hsxpa = 2
ro.ril.gprsclass = 10
ro.ril.hsdpa.category = 10
persist.cust.tel.eons = 1
ro.config.hw_fast_dormancy = 1
ro.ril.enable.dtm = 1
ro.ril.enable.a53 = 1
ro.ril.enable.5g.prefix = 1
ro.ril.hep = 1
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
pm.sleep_mode=1
ro.ril.disable.power.collapse = 0
ro.ril.fast.dormancy.rule = 0
ro.ril.power_collapse = 1
ro.battery.saving.mode = enable
system.performance_reduce = false
ro.android.performance.tuning = 1
ro.automate.performance = enable

Using your Lineage-TD 20.
[Treble-Enabled Device Development A/AB ROMS] JohnTheFarm3r:
Andy can remotely read your device's issue, he found it. Just wait for the fix. *rolls eyes*
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
On XDA it's just the two I've replied above; I think there were one or two from CoolAPK (local) as well, but I haven't read them in time, and now that the message history is gone, I can't check what they were...

Pasting a bunch of random props but not an actual logcat...?
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
If I wanted sarcasm, I'd look in the mirror. You do you, tho......
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Thing is, doesn't matter if it's 1 edit to build.prop or a load - it always bootloops. I tried it last night. Added one line to my build.prop which was to keep the launcher in my memory and it bootlooped.....

Also, I can't get a "logcat" if it's not booting or y'know..... I don't have TWRP etc installed. Your GSI's are broken.
[Treble-Enabled Device Development A/AB ROMS] JohnTheFarm3r:
Instead of posting logs, you're asking what's wrong from the dev just like that. Jokes on you.
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
How am I meant to post logs when I can't boot? Jokes on you.
[Treble-Enabled Device Development A/AB ROMS] JohnTheFarm3r:
You think you can only take logs while you're booted into the ROM?

OK lmao
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
I don't get why you're being sarcastic.....

If I knew how to get logs on a device that isn't booting, I would've posted them already.

Sad life you have trolling XDA and putting others down because "you know it all" lol go touch grass.

Enjoy being ignored I guess.

I mean, if you can't help or have anything useful to say, why reply? makes no sense.

I'm right, I can't get logs if I can't boot and I don't have a custom recovery.

JOKER!

Glad I ignored you now. :D :D
[Treble-Enabled Device Development A/AB ROMS] JohnTheFarm3r:
Dev asked for the same exact thing from you. Not sure what makes you think that anyone is "trolling" here.
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Anyway, Andy Yan - if you could explain how to get logs on a device that doesn't boot with an edited build.prop or how I can get logs without a custom recovery, I'm all ears!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
0. Yes, broken. I can't guarantee modifications made on top of my images would work, and I'm not obligated to support such.

1. Although I can tell these props are custom, I can't reliably guess what you did with them. You could've made it clear that you added these props to build.prop and then got a bootloop.

2. ADB is enabled by default and without authentication (for this kind of situation), connect the device to a PC and "adb logcat" from there. ...unless you turned ADB off after boot?

3. Only "VNDKLite" builds are /system RW, and even then, subject to certain device-specific restrictions. Also consider disabling verity (vbmeta), if applicable.
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
I didn't disable ADB. I have VBMETA disabled already.

Logcat will work when it's not booting? Because it gets to the Samsung logo and bootloops. lol

Sorry, new to all this. :D

And yes I'm using VNDKLITE.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Ah shoot, a splash loop (not making to bootanimation right?), I jumped to a conclusion too early myself.

I can pick up one of my remaining Sammy devices (which has TWRP) and see if I can replicate, but as it differs greatly from yours, don't keep hopes up high...
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Yeah no boot animation. Stops at the Samsung logo.

I'll see if I can install TWRP and see what's going on.

The only GSI that doesn't bootloop with an edited build.prop is the CrDroid GSI.
[Treble-Enabled Device Development A/AB ROMS] yahmabr0:
Hi Andy Yan. Just a follow up post:

It's still bootlooping when I copy over to /system/ as root but there's something weird happening; when I go into TWRP's file manager and look at /system/ there's 4 folders there and no build.prop!

I tried copying over a build.prop to /system/ with TWRP's file manager but it doesn't have any effect...

Did you have any luck with your Samsung device?
[Treble-Enabled Device Development A/AB ROMS] ivanmara:
Hello. I try to use this los20 gsi image on my device. Booting is successful. But I have problems with brightness and wired headphones. I want to change some vendor specific files. How can I unpack and repack this image on a linux machine. Are there instructions?

ps:

simg2img lineage-20.0-20231116-UNOFFICIAL-arm64_bgN.img system.img.ext
Invalid sparse file format at header magic
Failed to read sparse file
[Treble-Enabled Device Development A/AB ROMS] drnightshadow:
This is OT... Go to android mod/Dev section.. use android kitchen for linux
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
In case you haven't tracked my recent status here, I'm currently being hammered hard by my day job, and only spend minimal time/effort in ROMs and XDA...

VNDKLite images are read-write.

GSIs don't contain many vendor-specific files though, and even if you're sure modding files is the way to go, there are often simpler ways of doing it (on-device file manager, Magisk module, etc.).
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Here's an LOS21 TD-based test build.

It's intentionally built in "personal" flavor, to avoid being daily driven prematurely. I only know it boots on one of my devices, no time/energy to dive deeper.

However, it's GAPPS'd, so the eager can check if GAPPS/SN are working alright for them.

I've blindly picked lots of unmerged stuff, so expect platform features to be (half-)broken. For the same reason, I can't provide patches and picklist yet, as it's still a fast moving target.
[Treble-Enabled Device Development A/AB ROMS] Dr.Akk:
Hello! There is a tablet with a helio g99 processor, android 12. It has a standard orientation - portrait, but I would like it to be landscape. So far, I've only found something that can be edited PhoneWindowManager.java but I have no experience in editing and compiling code. I would really like to use the LOS20 bvN vndklite assembly in landscape orientation. Can you help me?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
A phone that isnt capable of rotating from portrait to landscape? Never heard that one before. Try the auto rotate toggle in display settings. And JSYK, not all apps will rotate. Android generally lets apps set the screen orientation when they're in the foreground. It just depends on how they're written. There are root/Xposed modules that can override this behavior, but this can have unintended effects, like an app looking weird or not displaying correctly.

There are also non root apps on the Play Store that can force a certain orientation for certain apps. But again, unintended effects are likely, so you'll have to test per app.
[Treble-Enabled Device Development A/AB ROMS] Dr.Akk:
I'm sorry, I may have expressed myself incorrectly. I don't need to force rotation of all applications. I need to change the standard orientation of the tablet from portrait to landscape. When auto-rotation is enabled, sometimes the display turns at the wrong moment. When auto-rotation is turned off, when I launch the application in portrait orientation, when I close it, the tablet remains in portrait orientation, and I would like the desktop to be constantly in landscape orientation when auto-rotation is turned off. There were no such problems on my old tablet with a standard landscape orientation. I would like to ask you to build a los 20 bvN vndklite version with the modified PhoneWindowManager.java .
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Sorry, but I cant build you anything, and wouldnt even if i could. I'm not the maintainer of this LOS GSI, you should tag @AndyYan if you want a request.

speaking of running this GSI on a tablet, I'm currently running it on my Samsung Tab S7+, which has a 12.4" screen. It does default to portrait mode, but auto rotate has always worked as expected so far. Not sure why you're having such issues, but it's probably hardware specific. I cant do anything to help you.
[Treble-Enabled Device Development A/AB ROMS] Dr.Akk:
Thanks for the answer! I will be waiting for @AndyYan
[Treble-Enabled Device Development A/AB ROMS] uschipower:
just a question:

does these images of LOS 20 from AndyYan include any tools to pass Google's safetynet?

I am using LOS 20 from andyYan on 2 lenovo tablets, together with magisk delta.

The Universal SafetyNetFix says that you need to have a valid cts profile.

It seems that that it this is not included in the this safetynet fix.

To do this, you can use MagiskHide Props Config but this tool is

a) very old

b) deprecated

You can further read that many Custom Roms include that feature.

So what about AndyYan's Roms`?

Hot do I get a valid safetynet attestion?

Thanks.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Answer to 1st question is no, there are no "tools" included to pass SN, except the securize/spoof properties toggle in Settings > Treble settings. Not sure what kind of "tool" you're expecting/hoping for, but any such tool is likely to need to make use of root/Magisk.

I too use Magisk Delta, and the modded USNF by @Displax (you can find it on his GitHub). I use MicroG on LOS and my SN is passing fine. Although you're probably using official Google services. I have never used MagiskHide Props Config.

For valid SN attestation, it helps if the ROM is patched to support passing SN without falling back to hardware attestation. This LOS gsi is patched so that this is possible, and I'd imagine that most other gsis are too. With stock firmwares, it's a different story, OEMs would never incorporate such patches into their firmwares.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
I think this setting-feature is exactly what kdrag0n wrote under "ROM integration", right?

How do I find out which services I do use?

Thanks for explanation. It's good to know that.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you have to ask the question of which services you use, it is most definitely official Google Play Services in your case. MicroG generally isn't something that one would install by accident/without knowing it. And it has very few users in comparison.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
I am always using the latest image from here:

Andy Yan's personal builds // GSI - Browse /lineage-20-td at SourceForge.net

sourceforge.net

I use arm64_bgN.img.xz

as explanation, AndyYan wrote at sourceforce: "g: With regular GAPPS"

well, this can mean "Regular Google-Apps", but there are also "Open GApps" --> https://opengapps.org/

So i cannot answer which services I am using.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Try not to get too hung up over exact wording. You have official Google Play Services, as opposed to MicroG. It doesn't matter whether the GApps are bundled in the ROM, OpenGApps, MindTheGapps, etc. All those other providers just repackage Play Services in a flashable/installable format. In the end the result is pretty much the same.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I flashed the latest build some days ago on my Samsung Galaxy Tab S6. Until before, I was able to get the blue dot instead of the mouse pointer when using the spen by "adb root" and then "setprop persist.ui.spen.pointer true". Unfortunately, it does not work anymore. I did it right now and the pointer is still the mouse pointer. Verifying whether the value is still correct after a reboot with getprop.persist.ui.spen.pointer says true.

Do you have any hints? The mouse pointer is not suitable for taking notes and it used to work!
[Treble-Enabled Device Development A/AB ROMS] uschipower:
sorry for the stupid question, but what is the use case for this?

what can a "normal user" do with this option?

thanks for explanation
[Treble-Enabled Device Development A/AB ROMS] m0byn:
One was able to replace the mouse pointer with the blue dot pointer when using a pen on Samsung tablets.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
My screenshot is from Phh AOSP Android 14 gsi (haven't been on LOS in a few months), but maybe this LOS has it. it gives a pen pointer dot, but it's white, not blue. and depending on where I hover the pen, I still get a hand pointer (hand with index finger extended), kind of like on older versions of Windows.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
PERFECT! Honestly, I just did not know that this setting exists. Probably it was added some time ago. Thank you very much!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you're interested in having better SPen functionality than what you'll get on any gsi, try this method (I'm sure I'm the 1st one to try it on a Samsung, and was really surprised when it worked). It will let you run a gsi and the stock ROM at the same time.:

[GUIDE][A10/A11] Flashing and booting GSI on Galaxy Tab S7+

/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...

xdaforums.com

I don't know if it works for others, on other Samsung devices, no one has ever given me any feedback. But I suspect it will, if the steps are followed as I've listed them.

To get an idea of which stock firmware you need to extract system.img from, just go to /vendor/build.prop, open it, look for the line that has "ro.vendor.build.fingerprint". For me personally the value reads as:

ro.vendor.build.fingerprint=samsung/c2qksw/c2q:11/RP1A.200720.012/N986NKSU2HWE8:user/release-keys

Which means I need to use the stock firmware ending with HWE8. You can get the firmware you need from samfw.com, or any other site that hosts Samsung firmwares.

If you're willing to try that method, and have any questions, just PM me. If it works for you, maybe you can share it on the Tab S6 subforum. And don't forget that you will need enough free internal storage space to run the Samsung ROM via DSU Sideloader, so check that before trying.

Sorry in advance for the totally off topic non-LOS plug.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I am very happy with running the GSI as my daily driver, so I will not try this out. I don't want to risk setting up everything again as right now it is perfect. However, thank you very much for all the help you've given me already in the past and now 😃
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you follow the instructions, you won't need to set up the gsi again. Just skip to the part of extracting system.img from the firmware zip.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I vaguely remember there's a system prop for that, that even some OEMs use. Perhaps some searching would get you there.

For when you absolutely don't want any root detected (*N), but still need to occasionally run some rooted shell commands like "settings put secure", "setprop", etc.

Other builders over at TD saw more universal need for this alternative pointer, and moved it to TD-global scope, enhancing it while they were at it. I myself seldom get to use a pen, let alone the S-Pen tabs, so let's thank them for it.
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
always on display not working on xiaomi redmi note 11, double tap not working also. i tried TD, arrowOS, LOS GSI the same result.
[Treble-Enabled Device Development A/AB ROMS] djshakilexe:
Sir, I think you forgot to post Changelog of December LOS20 GSI.​
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
Just wait and don't blatantly ask for it in bold letters. The developers do their work for free in their free time. Update will come when it comes. Thanks!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
What a PRICK. You should be banned from XDA for having that kind of attitude. So many XDA devs drop out of development because of unthankful "gimme, gimme, gimme" people like you. You're like a kid shouting when he/she doesn't get what they want.

I'm reporting your post and I hope everyone else here does too. Although I'm sure staff will do nothing besides edit it, at best. I'd drop the banhammer on you if I could.
[Treble-Enabled Device Development A/AB ROMS] BIGWORM:
People, don't do this. Please understand devs are here on XDA and provide in their free time. Either wait patiently, or pull repos and compile for yourself.

Thank you.
[Treble-Enabled Device Development A/AB ROMS] djshakilexe:
Not expecting someone will take simple word this negatively and make it a big deal. I meant no rudeness. Usually you post changelog, I thought you forgot to post for latest one.
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
For people who are too lazy to scroll and read. Please!

[QUARTERLY][GSI][13] LineageOS 20 TrebleDroid-based

LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...

xdaforums.com
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I only write down what I feel I should let you know, plus I almost always exclude platform-side updates (certainly I don't have the patience to flip through LOS Gerrit each month).

By now LOS20 is more than a year old, and I'll soon put it into low-effort maintenance mode, so you can basically expect only security patch mentioned from here on out.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
@AndyYan just a short question regarding LOS on the Samsung Galaxy Tab S6: in my experience, only the bottom two speakers work. However, in the respective sub-forum one experienced all 4 speakers working. After investigating it further, it was clear that 4 speakers only work while using Musicolet or Lineage OS Music Player and otherwise only two speakers work.

Furthermore, one has to turn on the following settings:

Qualcomm features -> use alternate audio policy

Samsung features -> use alternate audio policy

Samsung features -> enable stereo audio mode

Since the speakers are working with the LineageOS Music Player, I thought it might be an easy fix making it work with Spotify as well. Am I right in this regard and would you mind taking a look at it, or is the conclusion I am drawing incorrect?

If you need any logs/testing or whatever I am very willing to help in any way I can.

Thank you very much for all your wonderful work!!
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
How did you manage to install this GSI?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you have twrp, use the blockdev and dd commands. If you have fastboot or fastbootd, use that instead. Or you can dump your device's super partition, unpack it, replace system.img with the gsi (extract then rename to system.img), repack super.img, flash it with whatever tool works for your device.

I personally use blockdev/dd from within TWRP, because it lets me flash gsis without needing to connect my devices to laptop.

In my use cases:

TWRP:

blockdev --setrw <PathToSystemBlock>

dd if=<PathToImgFile> of=<PathToSystemBlock> bs=4096

My system block is /dev/block/dm-0, yours may be different. And you should omit the < and>. If you're not reckless, and write to the correct partition, then dd is perfectly safe.

Fastboot/fastbootd:

fastboot flash-logical-partition system <PathToGsiImgFileOnPC>

You need to install your device drivers on the PC. And Google's adb/fastboot/USB drivers.

For repacking your super.img, that's a bit more complex, so I won't list details here. But you will need Linux. I have yet to find a working super.img unpack/repack method that works exclusively in Windows. And Linux is the superior OS anyway, IMO.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
I tried to flash it via fastbootd command (fastboot flash system <img>) but I always got stuck on a bootloop on this device and I don't know why because I always do the steps correctly, is your decive the same as mine?
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Does my command have any difference between the command you suggested for fastboot? Do I need to fastboot -w after flashing?
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
And it got wrong... "fastboot: usage: unknown command flash-logical-partition"
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
"Fastboot flash-logical-partition" is definitely a valid command. But you have to append it with the name of the logical partition you're overwriting, which in this case is "system".

So:

fastboot flash-logical-partition system <PathToGsiImg>

fastboot: self explanatory

flash-logical-partition: tells fastboot you're writing to a logical partition

system: name of the logical partition you're writing to

PathToGsiImgFile: the local path on your PC where the Img file is located.

I don't know what fastboot -w does, so I won't advise for or against it.

Perhaps your vbmeta isnt neutralized, that can stop a gsi from booting, even if otherwise flashed successfully. This is your 1st time on a gsi? You need to disable your vbmeta's verified boot, then flash the modified vbmeta, in addition to the ROM Img.

The only other thing I can think of is, maybe you don't have a super partition on your device, which will make flash-logical-partition not valid in your case.

Last possibility: You were running stock ROM before flashing the gsi img, and forgot to format/wipe your data partition after flashing. You can't boot the gsi with stock firmware contents in the data partition, it must be clean. Having dirty data is a conflict that will prevent going from stock to a gsi.

My devices are Tab S7 Plus and Note 20 Ultra, I have successfully flashed and booted this LOS gsi on both of them. But I used the blockdev/dd method in TWRP, not fastboot.

And just to be sure: your bootloader is unlocked? This is required to run any gsi.

If you are sure you have correctly flashed the gsi with the command as I've listed it, then I suspect that your vbmeta is to blame for the bootloop. It's not hard to patch and flash it, so do that first, and flash the gsi img alongside it. Then report your results. And, after you have flashed a modified vbmeta, you will have to erase/factory reset your device (data and cache partitions). But you will probably have to do that anyway for the gsi to boot.

So first try:

1. Flashing gsi img, formatting data partition, attempt to boot

2. If stuck, next step is to patch vbmeta and flash it, flash gsi img again, format data partition, try to boot
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
If it is a valid command, it's not working here and Idk why :unsure:

And yes, I'm on Stock ROM precisely because I can't flash a GSI ROM on my device... sadly

How exactly I patch vbmeta?

I have TWRP, but it's not decrypted, so I believe it's useless, I cannot do anything with /data (https://xdaforums.com/t/recovery-a14-teamwin-recovery-project-for-galaxy-a14-4g-exynos-850.4635006/)