yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] MPK99:
ROFL. That would then be a noob question isn't it?

Yes. It's a toggle. And I've tried it fairly on all sort of applications, even the gyroscope testing too.

Currently I'm on another AOSP fork (crDroid by Nazim) & I don't have this issue. And probably the 2nd one too.

These issues occured on both light & td variants. I don't think this is device specific caz other phh GSIs don't have these 2 issues.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Usually if you have a bug that's on LOS TD but not on

TD AOSP 13

, then I suggest it's really interesting for Andy. Plz discuss in TD thread with the proper diagnistics.

Hope I understood you right.
[Treble-Enabled Device Development A/AB ROMS] jmfindorff:
Interesting, auto-rotate works on my phone (Samsung A33 5G), so I'm not sure what the issue would be then.
[Treble-Enabled Device Development A/AB ROMS] tripin@:
BT issue with 20.0 build (light and td) :

It connects but sound comes out from mobile, not BT speaker.

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.
[Treble-Enabled Device Development A/AB ROMS] nat:
I have switched from TD to Light on my moto g60 few days ago and so far it's awesome! I legit can't spot ANY bugs.

On TD I had weird bug when I had to reboot few times before bootanimation appeared otherwise the screen would blink and systemui would crash constantly. Also, a2dp offloading simply didn't work - now it does.

I have VNDK 30 btw.
[Treble-Enabled Device Development A/AB ROMS] jmfindorff:
I can't seem to get USB audio to work, even with alternative audio jack detection enabled. I'm on a Samsung Galaxy A33 if that helps. I know it's not the USB port itself since USB audio worked in another GSI rom as well as the stock rom.

Edit: I just noticed that in connected devices, when I plug in a USB aux cable, it thinks the cable is charging the device, when it clearly isn't.
[Treble-Enabled Device Development A/AB ROMS] nat:
Try disabling A2DP offload through developer settings, not treble settings and rebooting. That's what I had to do on TD.
[Treble-Enabled Device Development A/AB ROMS] tripin@:
I have tried without success on TD or light, I don't remember.

I will check again with light. Thanks
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Sadly, still it won't boot on my OnePlus nord 100
[Treble-Enabled Device Development A/AB ROMS] HUN_Gyuszi:
I would like to say a very big thank and hats of for the excellent work. I installed lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_gN-secure.img on my Moto Defy 2021 and 99% features are working out of the box. The running speed and smoothness is superior and much better than the original Moto EU software, let alone it does not have all the vendor crap, and also Moto left the device at Android 11, now I have 13. Awesome!

I had to fiddle around a bit to make SMS work (Treble fixes, IMS download, toggle VoLTE and a reboot). VoWiFi works, not sure about VoLTE.

Apart from this, everything works as expected, including safetynet totally passing with Magisk and safetynet fix.
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
ok, the actual difference is this:

android/13-gsi/system/core$ git log --oneline

2939aa404 (HEAD -> patched) FDE is dead. Fallback FDE to no encryption, and FDE+FBE to FBE

cdaf78dd5 fs_mgr: Keep allowing encryptable fstab flag

even if this is "light" version, you should consider adding these patches to allow several devices to boot.

Edit: actually, these are the only two patches, needed to boot "stock" android-13 gsi on my lenovo x606fa (coming with android 10).
[Treble-Enabled Device Development A/AB ROMS] hugolight:
Hy

wich GSI Build can i flash on a Gigaset GS5 (MediaTek Helio G85) Device...........

Thanks
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Kudos for building on your side to isolate the issue.

Given how small these changes are, I might still include them, but assuming you're on stock vendor, this device is quite an anomaly - FBE is mandatory since A10, and encryption way earlier...
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Boots just fine here, O.28 base, didn't even flash vbmeta...
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
actually, it is even just this...The device was released with android 9, just updated to 10.

} else if (StartsWith(flag, "forcefdeorfbe=")) {

ParseFileEncryption("aes-256-xts:aes-256-cts", entry);
[Treble-Enabled Device Development A/AB ROMS] BryanExcel:
Does anyone also get this error No Supported Camcorder Profile? Stock camera crashes when changing to video.
[Treble-Enabled Device Development A/AB ROMS] nat:
In the next build, could you please change sys.usb.config to something else than adb and also drop this patch https://github.com/AndyCGYan/lineag...ndor_lineage-Disable-ADB-authentication.patch ? I don't think it's a good idea to have USB debugging on after every reboot and also have it accessible without auth...

Also, it would be nice if the vanilla, "non secure" variant could come without phh superuser. imo it should simply resemble default lineageos as close as possible, without unnecessary addons.

edit: I see now that insecure adb is needed for compatibility with some devices. Maybe just disabling usb debugging on every boot would be a good compromise between having insecure adb and breaking compat :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sorry but this I'd firmly refuse. GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.

As you might have also seen, I've even removed the "secure ADB" part from the Securize process, as that doesn't work the same as building with ADB secure, and will cause ADB to be unavailable on every boot, requiring a re-toggle.

In the upcoming update I'll change Securize yet again, which will be controlled by a persist prop, and if enabling it causes a bootloop, resetting that prop via ADB will again be the way out.

If you need that security on your side, please add the "ro.adb.secure" prop to your own build.prop.

The upcoming change to Securize will unbind *N and "secure" again.
[Treble-Enabled Device Development A/AB ROMS] nat:
Okay, thanks! I will try doing this with magisk module then so it will nicely "survive" GSI updates.

Maybe adding a disclaimer about insecure adb to the first post would be a good idea? Most people definitely aren't aware that their lockscreen doesn't protect their data by default.

Keep up good work! It doesn't even feel like I'm running a GSI.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Fair, will add that to all 3 running threads when the next update comes.
[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 Treble-Droid based? ( 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] AndyYan:
To regular users, "Light" will have generally worse device support, but due to what's already mentioned in OP plus my favoritism towards it, will get updated easier and faster. I guess that's it? So yeah, I actually would like people to use TD-based, if that means one less not-so-elegant patch in "Light".

For some of the devices I use, see the forum signature. Nowadays I tend to choose form (aesthetics) over function (specs/value), so even though I can obviously afford a large fleet, I intentionally miss many popular ones like Redmi Notes.
[Treble-Enabled Device Development A/AB ROMS] Stan m:
Thanks a lot for your reply!

1) My device (redmi note 10 pro) is not a legacy device. So what would you recommend, light or Treble-Based?

2) Is this oss? Do I need to first flash some firmware? I am currently using ArrowOS 12 and TWRP. (I will use sd card to flash)

3) I think my device is arm64, with a/b, please correct me if I am wrong. But I dont understand vndklite. Should I use that or secure? ( I will not use gapps and I dont need safety net pass.)

Thank you!
[Treble-Enabled Device Development A/AB ROMS] nat:
1. Try light first, then trebledroid.

2. The whole idea of GSI is that there's no firmware in /system. You're supposed to use gsi with stock everything. You can use xiaomifirmwareupdater to get both latest stock firmware and /vendor

3. vndklite is for some legacy devices.
[Treble-Enabled Device Development A/AB ROMS] Stan m:
Thank you for your reply!

I know that gsi has more bugs than dedicated rom, but what about battery life? Is it similar or dedicated rom is better? Asking because I am confused, whether to use this rom or Arrowos 13 vanilla.

Thank you!
[Treble-Enabled Device Development A/AB ROMS] mioli104:
I have met BT audio problem on any version 13 treble project rom. BT audio stop working after few minutes. A2DP setting didn't fix that. Instead, the audio outputs from the speaker at the beginning. I have tried the new BT HAL settings but led to the same result. BT audio works fine on Android 12/L.

My device is realme Q2, any solutions?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with January security patches. [Insert obligatory backup-and-test warning here]

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.treble.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!

Also implemented:

Override minimum brightness - @Captain_cookie_200

Override navbar availability - @pbgapski

Rejected:

FDE and unencrypted data - @DerTeufel1980 - given that yours is actually a legacy device, I recommend just using TD-based instead (I was hit by CoV last month and skipped an update; I'll update it in a few days). Thank you for understanding.

Although I don't quite deal with Samsung devices in "Light", I've fixed and tested exfat for Samsung/Sony here, and since it applies to more than Samsung, I'm leaving this one in.

Fixed an oversight that caused Settings to not have a search bar.

And finally, I've examined / received reports about 2 Snapdragon 8 Gen 2 (SM8550) devices which have a common bug of no call audio. This one's gonna take me a while to figure out (AIDL coding-wise), but since SM8550 isn't going international very soon, I won't rush it.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
thankyou so muchhhhhhh. your work is amazingg
[Treble-Enabled Device Development A/AB ROMS] Stan m:
Super urgent, need help!!

I am flashing and it says to select partition to flash image:

Boot

Dtbo

Persist

Recovery

Super (system system_ext product vendor)

would do I select??

I am using arm 64 vanilla.

If someone can help me, I would really appreciate it!

Thank you!

Edit: I think it is super. I will try and let you all know

Edit 2: i'm booting into fastboot. rip.

Edit 3: I dont think I can even go to recovery. Can someone help me? I have gnu/linux on my pc to fix it via adb
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If it shows super, your recovery can't handle flashing inside super, and you should use stock recovery for the job instead.

Alas, by forcefully flashing onto the entire super, you've destroyed it (containing vendor and such) and will have to reflash stock to recover. (And a warning on that - don't forget that you SHOULDN'T select "flash_all_and_lock"!)
[Treble-Enabled Device Development A/AB ROMS] Stan m:
@AndyYan flashed stock miui. Now when I go to fastboot, it just says fastboot. do i have to "sudo fastboot flash .img"?
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
USB adb security is lowered · Issue #2328 · phhusson/treble_experimentations

(Discussed in the chat but I wanted to trace it here) If adb debugging is on then anyone can connect to the device without any authorization. Android has mechanisms for it for quite some time.

github.com

also discussed in the Telegram chat with Phh and Andy
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Again and again: You should must know what you're doing. And you are the only one bearing the consequences.

Hint for you: fastbootd
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
...

I have loaded lineage-20.0-20230109-UNOFFICIAL-gsi_arm64_gN via DSU and have it running now. There are 2 points that I would like to highlight:

my f4 still does not show nav buttons; I have tried toggling the 'override navigation buttons' in treble settings, which was enabled by default, but it had no effect;

there is now a constant notification from google play stating that the device is not certified. I am not sure this is expected or not, but it was not there in the previous build.

Sound works, camera works, nfc does not. Dark mode with black option looks great :)
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
I don't know for sure but rebooting might help.
[Treble-Enabled Device Development A/AB ROMS] spider1163:
This sounds device and patch related
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
Me (moto g30) too....:unsure:
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Indeed that switch needs a re-toggle (most devices do have a navbar on first boot, so I coded it to default ON when it isn't set), plus a reboot, to come into effect.

The basis of this (again, inherited from PHH) is the ubiquitous "qemu.hw.mainkeys" prop which has very high priority in the framework and also shouldn't be touched by non-emulator vendors. If even that doesn't work, then your device has a really rogue vendor...

That's how non-Securized g* builds have always been, and why I made "integrally securized" earlier...

↓

If it keeps appearing even after Securizing, just silence it by long pressing, GAPPS will start to work regardless.
[Treble-Enabled Device Development A/AB ROMS] kousuke5555:
Hi

I was finally able to boot "Light" on my mediatek device.

It is xiaomi POCO M4 PRO 5G. MIUI 13 a12 vendor.

Even more surprising, I was able to receive incoming calls with volte. I installed ims s vendor.

I had an issue with android_13.0.0_r24 ci-20230104 and TD base and phh v416 with incoming calls not working. I've seen reports that other mediatek devices don't work either.

In "Light", VOLTE was used for outgoing calls and incoming calls.

However now I can't use incoming calls on my 3G system.

Outgoing calls are possible.

I did the following:

adb shell settings put global restricted_networking_mode 0

Can you fix it with TrebleDroid and td base?

Thank you for the development.
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
Oops, I've misread your tips:LOL:

Everything works fine now, sorry and thanks so much(y)
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I can confirm that it works after a reboot
[Treble-Enabled Device Development A/AB ROMS] HUN_Gyuszi:
Super thanks. I am on the previus release from Light with Defy 2021 and it is super awesome for daily driver.

The minimum brighness fix was needed for Moto Defy 2021 because in my car at night I could see nothing haha. How can we use that? There will be an option like in the Treble fixes screen?

What is the desired upgrade to keep settings and apps? Just do the same flash command I used for original install and do nothing else (like a dirty upgrade) ? Thank you.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
That option lowers the minimum brightness, perhaps not what you're after.

Yes, just flash, don't wipe, that's it.
[Treble-Enabled Device Development A/AB ROMS] HUN_Gyuszi:
Thanks for making it clear. Yes, my minimum brighness is too dark.
[Treble-Enabled Device Development A/AB ROMS] HUN_Gyuszi:
Hey @AndyYan

Just checked that here:

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

sourceforge.net

Your latest file is:

lineage-20.0-20230109-UNOFFICIAL-gsi_arm64_gN.img.xz

But, earlier I used:

lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_gN-secure.img

I see that you changed the securize method. As you write: "For users who are already on a gN build, be sure to toggle it on and reboot right after you update!"

So I should flash the new image, boot into it, do the toogle and reboot? Will I keep my safetynet status?

Sorry for the confused questions.. :(

Keep up the great work!
[Treble-Enabled Device Development A/AB ROMS] tavoc:
Hi,

I bought for my son a few months ago a Chuwi Hipad Plus with Android 11 (Mediatek). But it has constantly Wifi Problems, which I noticed yesterday. It drops all the time, and the vendor has no solution or fix or support.

Therefore I used your lineage-20.0-20230109-UNOFFICIAL-gsi_arm64_gN.img and disabled dm-verity

System boots and seems OK for kids apps, but the Wifi drops from time to time as well.

I have noticed, that my device on your GSI is using kernel 4.14 and before I keep digging deeper. GSI is using the original kernel of the vendor?

Is there any real chance that by using your or some other GSI the Wifi bug can be solved? Or is all in vain, because it is using the chuwi firmware?

Thx
[Treble-Enabled Device Development A/AB ROMS] HUN_Gyuszi:
To my understanding, GSI / Treble is all about seperating device specific parts (drivers, firmware) and the ROM itself. So if you use a GSI device and flash a GSI ROM, you are not modifying anything around parts related to the hardware. If the wifi driver / firmware is buggy, it will stay buggy no matter of your GSI updates. I would reflash factory software and return it to the seller.
[Treble-Enabled Device Development A/AB ROMS] dani993@freemail.hu:
Can you explain how you installed it? Is there any issues besides the wifi issue?
[Treble-Enabled Device Development A/AB ROMS] tavoc:
I unlocked the bootloader first in fastboot with:

fastboot flashing unlock

then I disabled verity with the original file from the androd11 vendor update

fastboot --disable-verity --disable-verification flash vbmeta C:\Users\Me\Downloads\ADB_AppControl_171\install\vbmeta.img

and last I installed the system with fastboot with this file

lineage-20.0-20230109-UNOFFICIAL-gsi_arm64_gN.img.xz

My son is using that as a kids profile for some games and school stuff. That works (but wifi is still bad). Besides of that I dont know, as the device is locked with familylink
[Treble-Enabled Device Development A/AB ROMS] dani993@freemail.hu:
I think I solved the wifi issue. Previously it was dropping like crazy, every 2-3 minutes. Now it's going 30 minutes without disconnecting. I didn't try with 5ghz tho.

I reflashed the original android 11 firmware with the help of a reddit thread, there is download link for the eu firmware, works great. Google chuwi hipad plus android 11 reddit
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
Hello,

First of all I would like to thank you for the nice work with Lineage. It has certainly been vital for thousands of devices.

I have flashed the latest version but have been having difficulties enabling the Securize option.

When I type adb root I get the following message:

restarting adbd as root

timeout expired while waiting for device

I already tried to turn on by TWRP Terminal but when I reboot the device the value of persist.sys.phh.securize returns to false :(
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Hello all,

I am new to the custom ROM scene - so please be gentle. However, thanks to @AndyYan I was able to install Lineage OS 20 on my Samsung Galaxy A50 and until now I am amazed by how smooth everything works! Thank you so much!

I do have one question, however, since I did not find any information about that. Does the Lineage OS 20 "light" version support encryption? When clicking on "ecnrypt smartphone", then nothing happens.

I would be really thankful for any information on that!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Hello, I prefer Samsung users to simply use TD-based instead, where Samsung oddities are better taken care of.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with February security patches. [Insert obligatory backup-and-test warning here]

Over the past month I've assisted @Cozzmy13 in getting IMS fully working on a Moto QCOM S device, but in a device-specific build - I might borrow the fix when I have more time. Also gotta work on SM8550...
[Treble-Enabled Device Development A/AB ROMS] Mrfunnysnake78:
Hello Andy,

Thank you for your GSI, I successfully flashed it on a Samsung A33. But I can't use 5 Ghz Wifi Hotspot, if I turn off the new setting "Maximise Compatibility" it will just ignore and fallback to 2.4Ghz constantly. Is there anything you can do to help with this issue ?

Thank you
[Treble-Enabled Device Development A/AB ROMS] 嘉然今天吃向晚:
Thank you for your work.

What is ’ ?
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Hello, first of all I am very satisfied and happy with this amazing operating system! Since I am new to the custom rom scene I do have two questions:

1.) How do I install the new February version if I have installed the January version? Do I have to wipe the whole system and reinstall using a backup or is there an easier method, e.g. without wiping the system?

2) I am planning to switch from the "light" version to the TD version since according to Andy Samsung oddities will be taken more care of in the TD version. What is the correct procedure to switch to the TD version? Do I have to wipe the whole system, install and then use a backup? Or is there an easier approach without wiping the system? Maybe @AndyYan could help out with this specific question?

Thank you so much in advance and keep up the good work! I am very happy with everything until now!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
By default, even when the hotspot host device has VPN activated, guests will connect "directly" without going through it. This option enables guests to also go through that VPN without the assistance of 3rd-party apps.

Just install, don't wipe.

I do recommend a wipe, but I think some people did dirty transition already. If you do decide to take the risk, most importantly you need Light/TD builds from the same month, so that the platform side (LOS itself) won't complain.
[Treble-Enabled Device Development A/AB ROMS] 嘉然今天吃向晚:
Sorry, what I want to ask is, why is there a single quotation mark?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Blame the upstream translation guy, this is an LOS feature, not my addition...
[Google Pixel 7 Pro] Schroeder09:
I am confused by Whitestone dome's description of "2-pack" for their pixel 7 pro tempered glass screen protectors. The description calls it a two pack, but says there is only one cover for the camera bar. That's not really a two pack. Is there something lost in translation here? Is there enough loca to install tempered glass screen protectors on two phones?

Does anyone actually have these in hand? Will They be compatible with the OtterBox defender series case? I've had very good luck with these cases thus far.
[Google Pixel 7 Pro] jshinn1:
Two Screen Protectors and one Camera Protector. 2 Pack is talking about the screen protector itself.