yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Even I have the same problem of can't boot Android 14
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
At the mercy of upstream (Google/LOS). For context, LOS18 was sunsetted this February.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I think there's something up with the AOSP/LOS source code. I find it weird that i can boot all the Google gsis up to the latest one. But all other gsi builds after 1-29 just hang on the Samsung bootloader screen, then infinitely reboot in the same way.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I know you aren't subbed so you might've missed some replies - a recap:

Given the date, I suspect it's a boot fix for S24 that's responsible, however as QPR2 came shortly after, and broke so many Samsung devices I know of, I feel test builds on top of QPR2 would be ineffective for isolating the issue. I'm open to making a one-off test build, once I see the QPR2 storm settles some.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You know wrong, i'm subbed to this thread and have been for months. Just because i dont post on XDA as much as i used to, doesnt mean i'm not still lurking and reading. I vaguely remember you offering a test build, and later retracting that offer. I read it but didnt reply. No opinion to publicly offer there, except that i never expected anything to come of it. Devs work during their free time and arent paid by XDA members, so there shouldnt be an expectation of anything. But on a personal level, if i tell someone i will do something, then i'll give it my best effort. If i'm not 100% sure i can follow through, then i wont offer. A guiding principle of mine is that someone's word is their bond, and they cant be trusted if they break it. But **** happens, things can change quickly, so i take that into consideration.

I'm kind of put off immediately trying Android 14/15 gsis anyway, due to the broken booting. The only fix in A14 gsis that interests me is that DualShock/DualSense controllers work, but dont work in A13 gsis. If i knew how, and had more time, i'd dig into finding the commits that make them work again, then backport to LOS20 in a personal build. Besides that, LOS20 is as close to perfect for me as it gets for a custom ROM. All other functionality i use seems to work as expected.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
since i migrated to lineage_arm64_bgN-userdebug 14 AP1A.240405.002.A1 eng.crossg.20240425.011459 test-keys no turnip driver is working on yuzu emulator, so i was wondering if there is any related issue. any idea @AndyYan ?

UPD: no go. after tons of tests i`m rolling back. if anyoneis using this rom for switchemulation manage to use turnip drivers please let me know how it goes.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I installed micro g in this gsi but signature spoofing isn't working please help
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Sig spoofing works fine, MicroG is my preferred/go to. MicroG must be a priveleged system app or the spoofing wont work. Place MicroG GMS Core directory/apk into one of the following locations:

/system/priv-app

/system/product/priv-app

/system/system_ext/priv-app

Then it will work. Or you can use something like the MicroG Installer Revived Magisk module, which will handle everything for you. Spoofing wont work if the apk is installed as a regular user app, the ROM wont allow it to be granted spoofing perm.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@AnonVendetta If I install micro g revived module does all Google apps work fine with this rom just curious
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
As far as I know, most Google apps will work. Except apps like the Google app, that has never been fully functional with MicroG. From my experience, the Google Opinion Rewards app doesnt work either.

If you need better compatibility with Google apps, it's better for you to just flash something like MindTheGApps zip from TWRP. Or install one of @AndyYan's LOS builds that already have GApps. These are tagged as either BGN or BGS in the file name.

If you just need working Play Store but use very limited or no Google apps, MicroG should be fine for you.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
for some reason I don't want to use gapps builds so I tried opening YouTube but it keeps stopping is there a solution for that
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Last time i tested, YouTube app works fine with MicroG. But I dont use the official YT app that much. Check out NewPipe as an open source alternative.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Ok @AnonVendetta thanks for helping out 😁
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
hey @AnonVendetta are you testing latest td build (20240424)? i wanted to migrante so hard but got problems with vulkan. any experiente on that?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Yeah, that's the build I'm on. If you want to test Vulkan, flash the gsi and try installing a game like COD Warzone Mobile. If you're able to play then Vulkan is working, I'm pretty sure it uses that rather than OpenGL. There may be other ways to test, but I don't know about them. For me Vulkan seems to be working fine.

Or try Vulkan Android Test app from Play Store. Worked fine for me just now.
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
thx mate gonna try. btw there's a new rom build today!
[Treble-Enabled Device Development A/AB ROMS] livingligh1008:
anyone install on tab s6 wifi
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I didn't installed it on tab s6 but I can definitely say it will work
[Treble-Enabled Device Development A/AB ROMS] prazola:
Hi @AndyYan is this something you can address in the next build (ROM signing)?

15.9.9 Not passing device Integrity · Issue #331 · chiteroman/PlayIntegrityFix

Hello, After upgrading from 15.9.8 using chiron crdroid with Android 13, clearing data from google play services, play store and gms, and rebooting, the device is still not passing the device integ...

github.com
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Quoting another thread:

Most TD builders are still experimenting with signing.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@AndyYan can you implement face unlock option in your future builds if possible
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Has anyone tested the dynamic FPS option in Phh Treble settings? I know for a fact my phone supports both 60hz and 120hz. But I have never seen it hit 120hz no matter what I'm doing. I use the show refresh rate option in developer settings to confirm that it fluctuates between 40 to 60hz, but never higher.

I know that FPS and refresh rate aren't the same thing, but the the descriptions in Phh Treble are inaccurately labeled. I'm surprised that the devs either don't know there is a difference, or know but can't be bothered to use accurate descriptions.
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
If I look at the code, it is:

ro.surface_flinger.use_content_detection_for_refresh_rate

# useContentDetectionForRefreshRate indicates whether Scheduler should detect content FPS, and try
# to adjust the screen refresh rate based on that.
prop {
api_name: "use_content_detection_for_refresh_rate"
type: Boolean
scope: Public
access: Readonly
prop_name: "ro.surface_flinger.use_content_detection_for_refresh_rate"

If you want multiple refresh rates to work, read this:

Multiple Refresh Rate
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
I'm curious, with the release of the A14 QPR3 source code, will the case of devices with old kernels not booting happen again like with QPR2?

Edit: Looks like I posted in the wrong thread.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
What kernel version is in your device
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
4.14.186
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I have 4.9 kernel even I booted qpr2 so I think you can boot
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
Yup, it's fine since android_14.0.0_r37 ci-20240508

FYI I just tried the latest AOSP test build by ponces based on android-14.0.0_r50 (QPR3)

Github Artifacts

Can't boot (stuck on bootanimation and adb is not active so can't take logs).

But maybe because it's still testing and not all patches have been included. :coffee:
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Ok
[Treble-Enabled Device Development A/AB ROMS] _Pokey8680:
13 quarterly now? Damn...
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
anyone managed to MEET_DEVICE_INTEGRITY on this rom?

how could one reach that?
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
dead?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The build itself will have to be signed. I'm working on that, but over at LOS21 first.
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
sound is crackling (new clean install, Vanilla, when LOS starts, allready the greating sound is terrible

lineage-21.0-20240722-UNOFFICIAL-a64_bvN.img

Cubot Kingkong mini
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
If you aren't running LineageOS 20 on your phone, you are in the wrong place.

Use the Search function before posting. The appropriate forum for your device is here.
[Treble-Enabled Device Development A/AB ROMS] Glowez_:
oh sorry maybe i forgot to mention it, but i definitely am on lineageos 20 td
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Ah, okay, sorry about that. We have a lot of new users who post their questions in the wrong place so I assumed that's what you had done.

Are you able to switch the audio sink? While playing media, if you pull down the notification shade, there should be a button near whatever media you're playing that allows you to switch where the audio is going. Although, this should automatically happen when you connect to a Bluetooth device....
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've been tested positive for CoV and will pause activity until I fully recover. December updates to LOS19 and TD-based LOS20 will be skipped.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
At least you got it now, not back when it was really bad. I caught Omicron and was in the hospital a week for pneumonia, then again three weeks later for a pulmonary embolism. Now, it's basically the flu. Drink lots of water, take zinc and vitamin C, and get plenty of rest.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
And just when I thought we had this virus behind us. I've been lucky enough not to get it, but it has hospitalized and nearly killed 2 family members.
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
Look after yourself.
[Treble-Enabled Device Development A/AB ROMS] tripin@:
Same BT issue here with 20.0 build (light and td) :

Force disable A2DP offload is on

lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_vS.img.xz

lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_vN-secure.img.xz

lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img.xz

lineage-20.0-20221111-UNOFFICIAL-arm64_bvN-secure.img.xz

No BT issue with 19.1 builds

Devices : moto G9 guamp and moto G82 rhodep

Big fan of your work AndyYan, and Phh as well.

Hope you will feel better soon. Take care.
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I had it a couple of times. Have a safe recovery.
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
Hi, for me, adb is only starting to work, when the rom has booted up.

What's the reason for this?
[Treble-Enabled Device Development A/AB ROMS] Avraham Tsaban:
TD's github does not accept issues. Where should I report TD common gliches? On PHH's github?
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
Xiaomi Mi Pad 5 (nabu) boots up with all critical functions working :)
[Treble-Enabled Device Development A/AB ROMS] carliiiiiiiii:
Are you vaccinated? boosted?
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Does it matter? Is it any of your business? Let's keep discussions like this off XDA. Thanks
[Treble-Enabled Device Development A/AB ROMS] Matteo Gamba:
Installed on Motorola G52 rhode.

Everything seems to work fine, but wifi and mobile data doesn't really work, I can receive whatsapp messages but I can't install apps from fdroid/google play or browse the web (Mull browser). I thought this could be a Magisk problem, so I reflashed the stock boot.img and reinstalled the gsi but I still have those problem. I recently changed my device captive portal and dns, could this be related?

EDIT: nvm, I mistyped the captive portal URL so it didn't work lol, such a dumb mistake. everything works fine.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Very possibly. Try using default DNS settings, or setting your private DNS to something else. Magisk is unlikely to be the issue, because data problems like this are usually either related to a kernel issue (more specifically, the system interface with the kernel for data functions), or most likely an application layer issue such as inaccessible/incorrect DNS.
[Treble-Enabled Device Development A/AB ROMS] Matteo Gamba:
I'm currently using adguard DNS which works fine, the problem was with the captive portal, I'm very dumb and mistyped the server so it didn't work
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@AnonVendetta I got exfat to mount on the one Sammy I own. Haven't got to taking a look at your non-boot log yet, but one thing at a time...

EDIT: Can you let me know your build number, e.g. T975XXU2DVL1, and ideally CSC/region, e.g. XSA? So that I can dump and inspect its FW if needed without physically having the device.

And to everyone else, I'm back from CoV alright, thanks for your concerns.
[Treble-Enabled Device Development A/AB ROMS] silentrain94:
Hello dear friends,

I installed los 20 from andy yan in my lenovo device.I havent twrp in device.I flashed it with fastboot

Can i update los 20 old version to new with fastboot without delete anything?If i can can you say instruction?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'll let you know my firmware build # after I've upgraded it today. Samsung released a 2nd Android 13 firmware this month for both devices. Also, I can't remember if the log I gave you came from my Note 20 Ultra or Tab S7+. Although neither of the devices booted on the Nov11 TD build, so they likely would have produced similar logs.
[Treble-Enabled Device Development A/AB ROMS] VStephen:
Mt6761 Infinix X650B android 9 vendor ....

I was able to boot up the ROM everything works fine except for overlay light and some colour bug .. forcing HW overlay fixed it but not perfectly... Will be switching back to lineage is 19 for the meantime
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
any idea about this?

01-06 11:51:09.392 952 1078 W AidlConversion: legacy2aidl_audio_channel_mask_t_AudioChannelLayout: no AudioChannelLayout found for legacy input / voice audio_channel_mask_t value 0x3

01-06 11:51:09.392 952 1078 E AidlConversion: legacy2aidl_audio_channel_mask_t_bits_AudioChannelLayout_layout: legacy input audio_channel_mask_t 0x3 contains unrecognized bits 0x3

01-06 11:51:09.393 1238 1558 W AudioManager: updateAudioPortCache: listAudioPorts failed

audio seems to be fine though, but it is being spammed thousands of times (on aosp gsi as well...)
[Treble-Enabled Device Development A/AB ROMS] VStephen:
Can I dirty flash LOS 20 on LOS 19?
[Treble-Enabled Device Development A/AB ROMS] Stan m:
Hello,

Has anyone used this on redmi note 10 pro?

What is the difference between this and light version? ( For devices other than what AndyYan has.) (which device do they have anyway?)

Which one should I use for redmi note 10 pro?

Thank you!
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
The Lineage website has instructions for specific models but not sure if they would be applicable to this GSI.

I would clean install but have a read of this example (for Oneplus 7t but probably the same for other devices) https://wiki.lineageos.org/devices/hotdogb/upgrade

You may need to upgrade firmware first.

Do a thorough search on XDA &/or the web first.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
There seems to be massive Problems with GApps.

Besides the problems described above, it is also not possible to send SMS.

RCS messages via Google Messages work. However, SMS does not.

Hopefully @AndyYan can provide an update soon that fixes the problems.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with January security patches and in sync with TD 20230104. [Insert obligatory backup-and-test warning here]

During my CoV downtime, A13 QPR1 happened and TD-based had a lot of changes as well, which accumulated to this month and I had to update more patches than expected (way more than "Light" - lower maintenance is why I made that in the first place). I might've made oopsies along the way, so I don't feel quite confident about this batch, and you should exercise extra caution.

Some users have reported that securize bootloops their device, and the current "integrally securize" approach means they can't boot up even once. This month I've changed it yet again to "securize on-demand", which is similar to how you securize on PHH/TD-based (a toggle in Treble Settings), but reversible and doesn't require SU.

For new users who are unsure about whether securize might bootloop your device, please turn on USB Debugging and Rooted Debugging below it, and if/when you do hit a bootloop on the next boot, you'll have a rooted ADB shell available to you, from where you can toggle off manually:

adb root
adb shell setprop persist.sys.phh.securize false
adb reboot

For users who are already on a gN build, be sure to toggle it on and reboot right after you update!

Properly fixed exfat for Samsung/Sony, tested on the one Sammy I still own.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
That's good to know. Unfortunately if I can't securize then it's a no go, even if exFAT works. I'm not sure what you mean by "integrally securize", please clarify. Does this mean that your gsi is pre-securized, or not? Before the end of the month I'll get around to trying, got a lot going on RN.

What GApps package do you recommend? I've been using MicroG for awhile, but I'm starting to think that returning to GApps is more appropriate for me.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Yes, "integrally securize" was pre-securized, but that was last month; now I'm back to securizing on a toggle.

You can also try Magisk-based SN workarounds if you can get Magisk to work (I rarely succeed at Magisk on Sammys, but I don't rely on Magisk for anything so I didn't try hard enough).

Take your time. I'll be on Lunar New Year vacation soon, away from most of my devices for half a month, so our schedules kinda line up.

The GAPPS'd variant integrates MindTheGapps, which should be one of the best today. As stated in #2 though, I can't quite help you with GAPPS/SN...
[Treble-Enabled Device Development A/AB ROMS] leonardoncm:
It is working great on motorola motog52, snap680.

voLTE is working.

Problems: Headphone detection only.
[Treble-Enabled Device Development A/AB ROMS] orgler:
Hi,

I've tried lineage-20.0-20230115-UNOFFICIAL-a64_bgN on a SM-T510. I see two issues:

1) When I first have the lineage-19.1-20230112-UNOFFICIAL-a64_bgN, then do a factory reset and flash lineage-20.0-20230115-UNOFFICIAL-a64_bgN google apps keeps crashing. I don't see anything meaningful in the logs

2) When I do a "format data", then reboot recovery, copy lineage-20.0-20230115-UNOFFICIAL-a64_bgN to the latest twrp recovery and flash it, I run into a bootloop. Probably this is because of the encryption; but I see no way out of that. I can't run adb root / adb shell since it always runs into the bootloop and running the commands out of recovery does not work. how else can I set the value?

I tried to mount /vendor and modify /vendor/default.prop to have the securize=false line with no success/no change in behavior. I cannot mount /system (see (3)).

3) When I try to go for lineage-20.0-20230115-UNOFFICIAL-a64_bvN.img (as in (1) ) and then try to flash MindTheGapps-13.0.0-arm-20221025_095826 or MindTheGapps-13.0.0-arm64-20221025_100653 I get errors about "this is arm64 but the package is for arm64 (with the arm64) or "this is arm64 but the package is for arm" (with the 32bit gapps). When I try NikGapps-core-arm64-13-20220908-signed I get "not enough space. Any other idea for gapps on top of the vanilla build?

Probably this is related to my twrp not able to mount /system:

EXT4-fs (mmcblk0p25): couldn't mount RDWR because of unsupported optional features (4000)

(and the nikgapps being bad on handling this)

Any help would be highly appreciated.
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
this is the fix:

AUDIO_DEVICE_IN_BLUETOOTH_SCO_HEADSET: remove offending definitions... · DerTeufel/lineage_device_lenovo_x606fa@4f81a6a

01-16 20:14:46.994 551 551 W AidlConversion: legacy2aidl_audio_channel_mask_t_AudioChannelLayout: no AudioChannelLayout found for legacy input / voice audio_channel_mask_t value 0x3 01-16 20:14...

github.com
[Treble-Enabled Device Development A/AB ROMS] VStephen:
Use 32bit gapps
[Treble-Enabled Device Development A/AB ROMS] orgler:
Sorry, I had a typo in the error message. But I tried the 32bit mindthegapps as well with no success, I think this is since I'm not able to mount system in recovery, don't you think?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: Good news, the bgn variant boots on my Tab S7+. Not yet tested on the Note 20 Ultra, but I suspect it will boot there too. exFAT does also work. Magisk appears to work out of the box. Bad news...not sure yet.

Edit: I just toggled the "spoof system properties to on. After rebooting I can still get in. So far, so good, not seeing any obvious issues.

Edit #2: So far the only issue I'm seeing is hey google/OK google not working. I signed into play store, finished the setup wizard from the notification icon. Then I set the Google app as the default assist app. Afterwards I opened the google app and was able to set up the assistant. It even had me say hey google a few times, no issues. But after reopening the app and returning to the assistant settings, it now says it's not available for this language. I use US English, the rom's default. I'm sure it's not this gsi's fault, I experienced the same thing on Pixel Experience, as well as on A13 phh gsi with several GApps packages. It works on stock, wish I knew a fix for this.

Edit #3: it seems portrait mode is the default, especially on the lockscreen, and it doesn't rotate. That's fine on a phone, but not a tablet. Even with auto rotate enabled, the lockscreen insists on staying in portrait mode....Never mind, found the setting. I haven't noticed it on other gsis, it doesn't stand out.

Edit #4: Fingerprint enroll works, fingerprint unlock kind of works, but only in portrait mode. If I try to unlock in landscape mode, it just repeatedly insists "press firmly on the sensor". No matter how firmly I press, it doesn't want to unlock. Have tried with multiple fingers. The finger unlock icon appears just above the bottom edge of the screen, near the bottom left corner. So close that it's basically only a millimeter above my case. In portrait mode it appears centered at the bottom, but an inch or so higher up, so it's easy to press. I wish there were a way to move it away from screen edge so unlock would work even with cases.
[Treble-Enabled Device Development A/AB ROMS] Stan m:
how to flash this on redmi note 10 pro?

This device has super block. Roms that come with .zip file are flashed easily, but don't know how to flash image file as my device has super block.