yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] GroovyG:
Sorry for the double post, but this may be of interest to many:

As noted above, 120Hz works amazingly in this ROM. So well even that I lowered the refresh rate to 90Hz because I really can't see a difference between 90Hz and 120Hz at all and it uses a lot less battery, the difference from 60Hz to 90Hz is very notable though.

So, after scrolling everywhere was super smooth without any lags or jank, I still noticed it when scrolling in the browser (I use Brave). It happens in all chromium based browsers, but strangely not in Firefox - there everything is smooth as silk. After some research I found a simple setting in chrome://flags called Android SurfaceControl - see screenshot below. Disable that, and 90 or 120Hz scrolling is also super smooth in chromium based browsers.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] asylor:
Thanks for your hard work! Just want to inform you that the LineageOS 20 GSI Light version (2023 June ver) works fine on POCO F5, from phone calls/SMS to WIFI/mobile data, bluetooth everything works (I tried the TD version first but phone calls and bluetooth earbud had no sound/tested with alternate audio setting but still failed so I switched to Light).
[Treble-Enabled Device Development A/AB ROMS] pvdeejay:
Hello,

Can you please kindly point me to the description of individual variants provided?

I'd like to get a rom rootable with magisk with MicroG instead of gapps.

Am I looking for secure vanilla or is there a better variant for me?

Edit: I've found out variants are described at the source forge site along with the downloads. I was looking for these here in the forums. That's my mistake and I apologize.

Downloading lineage-20.0-20230715-UNOFFICIAL-gsi_arm64_vS.img.xz.

Greetings

P
[Treble-Enabled Device Development A/AB ROMS] bedencic:
im having problems with 5G network,

and with dual sim switching on/off, doesn't work

on Galaxy A33 5G
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Removed
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with August security patches. [Insert obligatory backup-and-test warning here]

I've been inactive around online discussions due to day job - here's hoping it doesn't hinder my progress on U when it drops.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
It seems that somewhere in the 0813 build introduces an issue where certain (but not all) apps can't utilize a VPN connection. Connecting through a hotspot with the same backing VPN works fine, so this is most likely a fault of the build, not the VPN. Non-VPN usecases seem unaffected.

I've temporarily reverted the entire string of changes that have been tested to cause this, and uploaded new builds dated 0814. However, if you've already flashed 0813 builds, even after dirty-flashing 0814, you might not immediately see restored network access. A few things you can do at this point:

Manually double-check and make sure [App info - Mobile data & Wi-Fi - Allow network access] has been flipped on, both for the app you want to use and for the VPN (if that's provided by another app). If you have too many apps installed, this might not be for you...

Turn off Restricted Networking Mode entirely by following post #9.

Try this ADB shell one-liner command that populates the allow list with all app UIDs. Requires a rooted shell (*N can turn it in in Dev options). Note that this is unverified security-wise.

settings put global uids_allowed_on_restricted_networks "$(cut -d ' ' -F 2 < /data/system/packages.list | sort -n -u | tr '\n' ';')"
[Treble-Enabled Device Development A/AB ROMS] voidflame:
Screen randomly freezes on Xiaomi 13 Pro when I am using Chrome. Disabling "Adreno Graphics Driver" app worked previously but after I wiped it doesn't work.
[Treble-Enabled Device Development A/AB ROMS] asylor:
Is it normal that this ROM cannot use 4G connection? I tried to put the SIM card in my old phone (poco f1 lineageos 19) it can show LTE, but in new phone (poco f5 lineage os 20 light) it is always 3G/EDGE/H/H+ even I had changed the prefered setting to LTE in SIM card setting. Currently using the 2023-08-14 version, tried both SIM slot one and slot two then restart it is the same.
[Treble-Enabled Device Development A/AB ROMS] voidflame:
My Xiaomi 13 Pro too, and the 4636 doesn't work. I must use Network Signal Guru to get it to work. But VoNR doesn't work.
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
My moto g100 and Redmi 9T just work fine with 4G/4G+ without any special configuration...
[Treble-Enabled Device Development A/AB ROMS] asylor:
(Solved, see #288)

Thanks for the star code 4636 /Network Signal Guru hints. I still fail to use 4G in latest version of the rom but found something.

Main Issue: Network setting page when selecting "Allow 2G" with Preferred network type as 3G or LTE with have value "GSM/WDCMA preferred" in 4636 page, without checking "Allow 2G" will have "WCDMA only". However "LTE" value in network setting page won't change anything in 4636. Status bar icon displays EDGE/3G/H/H+ and network type HSPA.

For the same sim card in my old phone (lineage 19) the value was "GSM/WCDMA/LTE(PRL)" (should be 2G/3G/4G with roaming not enabled but still show PRL), where the network speed was much faster and more stable due to local 4G coverage. So it rules out the SIM card or ISP issue. The icon shown in status bar is 4G/LTE and 4636 page shows data network type is LTE.

No matter what values I change in 4636 page it will automatically roll back to "GSM/WDCMA preferred" or "WCDMA only" which is set by the network setting page.

Tried some apps (Network Signal Guru/Force LTE 4G/5G) either they request root permission (my rom is non root) or they said rom is not compatible (the rom stored the configuration to somewhere no one knows?).

Here comes the interesting part. I can use root adb I can set settings value with command "settings put global [key] [value]". Somehow "preferred_network_mode" is not the right value.

I even dump the whole configuration of global/system/secure by something like "settings list global > setting1.txt" then use the diff command to compare the settings of "GSM/WDCMA preferred" or "WCDMA only" but the values did not change. So I guess it may be storing its value somewhere else. Also in theory as the phone has dual sim with DSDS mode enabled, so there should be two preferred network mode values one for each card, which can be shown in 4636 page. (the value in old my phone was "preferred_network_mode=22,22" but obviously not working in lineages 20 light, and the 22 value is not "GSM/WCDMA/LTE(PRL)" from the list I can find on the internet, guess it varies in different versions of Android?). I also tried "pm clear com.android.providers.telephony" to reset sim card cache, set preferred LTE first then registered, it still uses 3G no matter what.

If someone knows the value for setting the preferred network mode for dual sim phone please tell me.

Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] ULTRA90:
can anyone help me install the right rom on galaxy s23 ultra s918b??
[Treble-Enabled Device Development A/AB ROMS] JW10233:
I don't quite understand why phh's ota renders Magisk unusable. Don't GSI updates only modify the system image? Can't you just install the ota via phh's ota and then flash magisk to the inactive slot?
[Treble-Enabled Device Development A/AB ROMS] JW10233:
I would recommend you to stay on One UI but I would root it to to do my modifications. At the time of writing this, there are no device specific roms to try, but you can still install any GSI that works for you. You can test these on your device using dsu sideloader. If you install a custom rom or a GSI that is not One UI based, you cannot install the stock camera app which makes your camera much worse.
[Treble-Enabled Device Development A/AB ROMS] ULTRA90:
yes I know what I'm getting thanks but I would like to know do not install the rom via recovery?
[Treble-Enabled Device Development A/AB ROMS] asylor:
I found the solution finally. In simple words somehow the phone cached somewhere the preferred network type, and even "pm clear com.android.providers.telephony" won't work (the SIM card page the custom name of SIM card is gone, it registered again like new SIM card but still failed to change preferred network type).

So I simply search around for how to delete settings. The trick is to delete all WIFI, bluetooth and mobile settings with the "Reset Wi-Fi, mobile & Bluetooth" option. At the end I still don't know how Android 13 stored the value (adb export settings look the same) or why WIFI and Bluetooth matter, as least this can clear the "2G/3G only" issue. And now I have my LTE back.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Cheers, Andy. Just installed Aug version. Had bit of flailing... Had an older version next to new version of .imgs and accidentally tried to flash an older version than I had. Ended up revanilla-izing then doing properly. Works great. Much appreciated.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sorry about the lack of interactions and activity in general lately. In July I've shifted to a new role in my day job that requires significantly more involvement, and while it hasn't fully exhausted me (yet), it does mean that I come home / head into the weekend with much less energy for things I usually do. Over the past month I preferred to spend that energy on recreation/relaxation, critical (and few) ROM stuff, and communicating with closer friends. Not a burnout from doing ROM stuff (what PHH faced), but still a burnout slowly happening nonetheless.

There's no platform-side security patch this month, so to many it would be a less than meaningful update. There's an impactful change from @Jeik to support Xiaomi's FOD/UDFPS, which I feel I should properly test on my side before rolling out (esp. on Light), but I don't have the energy and device to at the moment.

For reasons above, I've decided that I'm skipping this month's update to LOS20 Light/TD. Thank you for reading through and understanding.
[Treble-Enabled Device Development A/AB ROMS] PTuT:
Thanks for letting us know and all the best in your new role and let it not drain you out.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with October security patches. [Insert obligatory backup-and-test warning here]

A few days ago, on the release day of Android 14, I gathered the energy I could and made an early TD-based AOSP build. That was about the most effort I can spare nowadays in a short burst, and now after another tiring week, I'm back to low power...

This update still doesn't have @Jeik 's Xiaomi's FOD/UDFPS change built-in, as the whole thing seems non-trivial t understand and merge, I'd rather take it slow and safe. If you're a Xiaomi user and would really like to use that (esp. after experiencing it on other TD-based GSIs), I suggest waiting for a TD-based LOS update instead.

The VPN issue mentioned in #278 hasn't been resolved, but meanwhile for the specific affected VPN app (Clash), a workaround had been found, so the firewall feature has been re-enabled.

As for LOS21, in my current state, I can't quite keep up with the rapidly changing upstream sources, and would rather like to wait for it to stabilize a bit, perhaps next month. LOS20 will also enter low-effort maintenance mode by then (oh isn't it already now? sigh).
[Treble-Enabled Device Development A/AB ROMS] Heeni:
It may sound a little cheesy, but I'd like to say thanks for everything you do. I have your GSI ROM on a tablet which would otherwise be sitting in a corner doing nothing.
[Treble-Enabled Device Development A/AB ROMS] PTuT:
When will lineage-20-td be updated similarly as light version? Thanks.

UPDATE: TD was also updated ... Appreciate.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Updated Oct version few days ago. Working great. As soon as I get a dozen Fabergé eggs 1 is yours.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with November security patches. [Insert obligatory backup-and-test warning here]

Finally got some breathing room from day job - just began taking a look at LOS21. It might still take a good while though.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I overestimated "A13 QPR4", so here's an LOS21 "Light" test build.

As with previous instances, it's intentionally built GAPPS-less and in "personal" flavor, to avoid being daily driven prematurely. Heck, even I have only tested it on 2 sidekick devices so far...

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.

TD-based is also nearly ready, but a test build will be offered at a later date, perhaps next week?

LOS20 "Light" will be retired when 21 is deemed ready - after all, "Light" is all about shaking off legacy burden.
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
THX for your great work!

I won't blame anything 'cause it's just the test build and it's your personal build.

But just an FYI, I flashed it on my moto g30, and it boots fine. But once its screen has locked, the screen won't come back anymore (system is working normally, but the screen is blacked out 'till rebooted).

Well, I think this is my device specific issue 'cause the same thing happens with ponces's AOSP A14 build too (though most of A13 GSIs work pretty fine).

Anyway, I'll wait for your official(?) build.

Thank you so much indeed!
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I put this on my Lenovo X505F and was pleasantly surprised. No bootlooping or other strangeness. Admittedly, I don't use this tablet for much, but so far, everything has behaved well.

Many thanks!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with December security patches. [Insert obligatory backup-and-test warning here]

Although a test build has already been done (see above), LOS21 release will be deferred to at least next month. By then, I reckon most LOS picks would've been merged, and QPR1 would've come out too.
[Treble-Enabled Device Development A/AB ROMS] anotherphonker:
i am getting no certificate error, and when i'm enable safetynet fix it looping as you said. what should I do?
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
LOS20 GSI works fine with com.android.art.capex and com.android.runtime.apex from Android 14. Why did I do it? Just because.
[Treble-Enabled Device Development A/AB ROMS] anotherphonker:
i am in android 13.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with January security patches. [Insert obligatory backup-and-test warning here]

We don't have a holiday season around Christmas / new year here; quite the opposite, the end of a year usually means the toughest work and the most urgent deadlines. The more I work overtime and code, the less I want to even read any code for ROMs at home - the scale almost tipped over by the end of December.

The bright side is I finally got to catch a breather to adjust my patches some more, but I still don't have enough time yet to migrate my daily device to A14 (to better test it). Moreover, even by now, LOS21 still has lots of unmerged stuff, and needs a carefully maintained picklist to get going.

I'll still try to make a thread-worthy release within this month, but with what I can devote to ROMs nowadays, don't expect a daily driver out of it.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Installed. Working fine on Moto G Power (2021) that never will have a sim card.
[Treble-Enabled Device Development A/AB ROMS] AcnapyxoB:
I installed the last few lineage-20.0-arm64_bvN, including lineage-20.0-20240112-UNOFFICIAL-arm64_bvN.img.xz

on a Motorola Defy 2021, everything (except NFC and FM Radio) is working very well.

The phone is super fast and responsive. No single reboot or other problems.

Thanks!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Now that the successor is out, if nothing goes seriously wrong there, LOS20 "Light" will be discontinued after a short grace period (one month perhaps).
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I've been running the test version of LOS21 "Light" on my Lenovo X505F tablet and I've been very happy with it.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
the last two releases have annoying bug: the Alarm Clock hangs when setting an alarm time. Anyone can check and confirm?

app id com.android.deskclock, I have an ANR report.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with February security patches. [Insert obligatory backup-and-test warning here]

Likely the last of LOS20 "Light".
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Cannot replicate, set one on a fresh DSU installation just fine.

This thread is near EOL anyway, if it still happens on 21 (likely, the clock app is the same), let's move it there?
[Treble-Enabled Device Development A/AB ROMS] Electrix C:
AHelp, what happens to me is that it won't let me log in due to security problems, the device is not certified, what could it be?
[Treble-Enabled Device Development A/AB ROMS] Ayron_Oliveira:
Hi @AndyYan. There will be any a64 variant of LineageOS 20?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
overlay issue. find a overlay for your device then push it to /vendor/overlay/
[Treble-Enabled Device Development A/AB ROMS] kernel_t4sk:
thx i will try to fix
[Treble-Enabled Device Development A/AB ROMS] AppleExpl01t:
Posting for my interest in Google apps
[Treble-Enabled Device Development A/AB ROMS] aldiandrew:
Cant wait for gapps version
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
I flash it on my OnePlus nord 100 and it won't boot, it returns to fastboot mode, I am wandering why
[Treble-Enabled Device Development A/AB ROMS] nisfta:
Can I dirty flash from Lineage GSI 19.1?
[Treble-Enabled Device Development A/AB ROMS] varadinum:
Sorry, I would like to install this but I don't know how a gsi rom works. Can this be used as a daily driver? Do you always get an update? Many Thanks.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
maybe for some devices yes. No builds with gapps are availible tho. so if you use google playstore, discover, youtube etc. then dont go for this. Some stuff can still work with microg. wait for gapps build. For me i aint using LOS 20 yet since Andy is still working on those new patches and the patches aren't suitable for my devices. it boots just fine super smooth. but audio settings greyed out for me and most of the samsung features i will not be able to get back since andy has already said hes not going to bother with samsung oddities in the first post. so rip.
[Treble-Enabled Device Development A/AB ROMS] varadinum:
that was very detailed. Thanks a lot for this
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
your welcome
[Treble-Enabled Device Development A/AB ROMS] nisfta:
What Samsung features don't work?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
everything tbh. only feature that is here is alternative backlight scale. but andy could include more patches in the next build. and 90Hz
[Treble-Enabled Device Development A/AB ROMS] YoShake:
I gave a shot with this on my moto G Pro / Stylus, and seems to work blazing fast.

I would like so much to use a nongms GSI as daily. But none of those I've tried were compiled with support for motorola, thus they lack moto gestures.

Once a man shakes the phone, he enjoys having flashligt launched right away. Seems a but odd but they support rotating gesture, so could anyone point me to a guide or just say if it's even possible to add all moto gestures on my own, without compiling source?
[Treble-Enabled Device Development A/AB ROMS] 3mel:
I changed one setting... alternative audio policy... and some apps went screwy (namely Vanced) and I rebooted into a never ending boot up.

it's not a bootloop, it just repeats the first part of the animation without end.

my phone is a SM-G781B an international S20FE 5G

I had to wipe data to get back in... a dangerous setting for Samsung owners!

wired headphones via USB-C adaptor don't seem to be able to work on this build for me.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If I don't see a T partner GMS repo up this week (which perfectly slots into the build system), I'll experiment with MindTheGapps, I heard other builders have used it with success. Securize will be implemented together (it has to, no good having a GAPPS'd build that doesn't even have a chance to pass SN).

And um, it may sound apathetic, but Samsung users please just go try something else, one of the TrebleDroid-based ones, see how TD serves you. I already have TD-based built once, just haven't got time to polish it.

Don't dirty-flash on ROM or version shift. And in case of the upcoming TD-based LOS20, I'd advise against dirty-flashing from "light" to that too.

Again, these are only for Qualcomm devices.

Perhaps I should just remove/hide that category altogether otherwise...

Refresh rate should already work, and perhaps better than in past PHH-based GSIs.

More patches on Samsung, eh, probably not here...

LineageOS has their own MotoActions implementation, but whether that could be introduced without device-specific dependencies or breaking other devices - the "generic" premise in GSIs - has to be experimented.

I remember that, it was on PHH-based too.

If you have root (*S or Magisk), turn it off during that bootloop with:

su
setprop persist.sys.treble.caf.audio_policy false
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
yeah 90Hz is fine. I was talking about everything else that would fix some of the issues like alternate way to detect headsets that was in the phh gsi. it fixed my broken headphone port. and double tap to wake.. that was in the samsung section. the one in misc doesnt work. but yeah. thanks.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
treble droid based ones most of them have broken bt audio which is essential for me. toggling the force ad2p offload doesnt do anything. i dont even know where to go now. My device own stock firmware has extreme bugs so i aint going back to it.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Can you give me a list of Samsung-specific features you personally found effective? See if they were trivial to add.

Heard about that, yeah I need to test that on my TD-based too, one of the builders said it just mysteriously breaks for him despite that he supposedly included everything.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
the features that i really use are

1. Double tap to wake

2. Enable Extended Brightness range (i think this one is already in there)

3. Enable access to all cameras (for a app called freedcam allowing me to use all of the cameras again)

4. Set flash light signal strength (tbh i have seen apps that does this maybe i could use those if you dont include these.)

oh wierd. bluetooth app was just crashing the popup appeared for a micro second then goes away and bluetooth restarts itself. this happens when my headsets connect and play some audio. if my headsets do nothing and still be connected nothing happens.
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
For the gapps you can use MindTheGapps repo
[Treble-Enabled Device Development A/AB ROMS] varadinum:
A build gapps would be really appreciated. thanks mate
[Treble-Enabled Device Development A/AB ROMS] 3mel:
I did it again... this time I was experimenting and not intending to reboot but the phone chose for me after a few minutes. can't use su command without the system running that I know of.

that is the only major drawback for me, USB C adaptors for headphones not being recognised / supported. this is my first time going google free and I like it.
[Treble-Enabled Device Development A/AB ROMS] jacomail95:
Any plans to support a64 A devices?