yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Yesterday I wanted to boot into custom recovery while the device (Samsung Galaxy A50) was still running LOS 20. So, I pressed volume down & power key until it shut off. Then, I pressed volume up & power key until TWRP showed up. After verifying some stuff I booted back into system and my phone was resetted!!! It was literally starting with the welcome screen of LOS. Then, I also verified whether maybe the data was still there...nothing...all gone. So, is this a normal behavior of LOS? Pressing these two buttons will erase the phone??
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Has nothing to do with Lineage.

You obviously did something wrong during your initial setup. I'm guessing it was something in TWRP....you were pretty vague on what exact steps you performed
[Treble-Enabled Device Development A/AB ROMS] thurblunt:
Hi,

I got success on installing the GSI on my Moto G20 but with a little bug.

I got a bug where all videos play with weird colors.

Everything that is not static got this bug. It happens even with the camera.

I tried changing the colors settings but no success.

See the screenshots attatched.

Besides that the GSI works fine. Really good.

*** Screenshots 1 and 2 are on the YouTube home page (that auto playing videos)

and screenshot 3 is the actual video.
[Treble-Enabled Device Development A/AB ROMS] brgroover:
Hi! Any way to enable the in-display fingerprint reader? Or is this impossible on GSI ROM's? I have a Motorola Edge+ (2020). No 5G available either.
[Treble-Enabled Device Development A/AB ROMS] twolitrepinto:
Good to know.

I'm looking to install this on my S20 (Exynos) but looking for some feedback first.

For signature spoofing, try installing Lsposed and FakeGapps module.

Works for me on LOS 19.1 and BeyondRom 6.1 which is A13 based. I use MicroG also.
[Treble-Enabled Device Development A/AB ROMS] Sage:
just letting you know this works great on Tab S6. Only issue i found is the Samsung Keyboard Touchpad doesnt respect the rotate. So works fine in Portrait though in Landscape it Up is Right and Down is Left etc... Any thoughts on a fix would be appreciated.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I had the same experience when using the S-Pen. As far as I remember, it went away by flashing the March update. Maybe setting the property to use the spen pointer instead of the mouse pointer resolves the issue? Idk but worth a try! See here

Edit: hopefully link works now
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Both of my devices are back on this gsi now. I was on stock for a few weeks, to upgrade firmware and do some tests. Which just reinforced that stock isn't worth it in the long run, gsi roms are the way forward for long term support.
[Treble-Enabled Device Development A/AB ROMS] Sage:
That link isn't working for me?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Same. I get this:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: i'm wondering if your gsi has a patch that blocks the fallback to hardware attestation, for SafetyNet purposes, on devices that support attestation?

For reference/context:

https://xdaforums.com/t/app-microg-...of-google-play-services.3217616/post-88332379

https://xdaforums.com/t/app-microg-...of-google-play-services.3217616/post-88332997

If it doesn't, would you consider adding such a patch?
[Treble-Enabled Device Development A/AB ROMS] Kenaz Rune:
I'm using a Samsung Galaxy Tab 2019 (SM-T510), which is A64. I've been using the vanilla version and installing MicroG. There is one ROM on the XDA Dev forum for this device that now uses your GSI with GAPPS, so your effort is still very much appreciated.
[Treble-Enabled Device Development A/AB ROMS] Kenaz Rune:
I am catching up on the forum, and this interests me. I'm reluctant to try it on my tablet because I don't know if it is safe and Trojan free. Can you tell us about this software? If I decide to install it, the best I can do is tell you if I get the same problem.
[Treble-Enabled Device Development A/AB ROMS] newboihere:
Hello @AndyYan , thank you for your work!

I am trying to use your ROM in a mediatek device with EROFS (Poco M4 pro 5g).

I manage to re-pack a super.img from the original stock image (MIUI13) and flash it from fastboot. The system works but I have no mac address, no bluetoth and no NFC.

restricted_networking_mode is set to 1 as you explained, so I change it to 0 but does not solve it (even after rebooting is changed to 0 but no conexions).

Now the interesting thing: I flash back the original super partition from stock and still no mac, no bluetooth but NFC works.

After a clean "flash all" with XiaoMiFlash the phone recovers all the connections.

Do you think something from your ROM might be affecting other partitions out of super?

(I also installed TWRP and Magisk, the source of the problem could be one of them)

Thank you for your time!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Restricted networking mode? Are you talking about a crossed out globe icon that appears in the status bar sometimes? Because I'm getting that with microg and play store, they are unable to access internet, and therefore can't work. I can't even log in.

@AndyYan: Do you know what this user is referring to? And this icon I'm seeing? I just want to know how to make it f off so my apps work correctly. I have never seen this icon in the Phh AOSP gsis, sounds like another "feature" that the LOS devs crammed in without asking the users or giving an obvious toggle for it.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Inc'd in both Light and TD.

...why? Just flash it like any other device. Stock being EROFS doesn't mean you can't flash/boot EXT4 images.

That corresponds to the toggle [App info - Mobile data & Wi-Fi - Allow network access], but it shouldn't be turned off by default for anything.
[Treble-Enabled Device Development A/AB ROMS] newboihere:
Sorry, I should have give more context:

at comment #3, Andy said:

Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

But it seems that apart from that bug, there is something else not going well in my case. Might be the flashing process or the ROM setup process or Magisk or TWRP, for example.

I was thinking that, as the process through Mi Flash restore the conectivities properly, I could just change the stock super.img there for my modified super.img with LineageOS. Of course it gives CRC error, so I need to create a new sparse crc list. Is it a stupid idea?

Would be better to first try to find where is the missing information and just patch it afterwards?

On which partitions could be useful information about the wifi and bluetooth setup?

I am also going to do a dump of the vendor and product partitions before and after losing conectivity, to see if the problem is there (but as I said, the stock super.img does not fix the problem, so the damage must be outside of the super partition)

Thank you in any case for your time! :)
[Treble-Enabled Device Development A/AB ROMS] newboihere:
fastbootD cannot manipulate the partitions. I do not remember the exact quote, something like unable to write partition table or unable to mount... I can try again and tell you the exact issue. Also by TWRP it was unable to mount some partitions, maybe system_root or something like that...

Spoiler content hidden.

The idea of repacking the super was from here:

https://xdaforums.com/t/guide-unive...ons-inside-super-read-writable-again.4483933/
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sounds like your TWRP has a bad fastbootd impl.

Here with GSIs we don't really need to rely on custom recoveries. Just return to stock fully, flash only the GSI via stock fastbootd, and see what happens?
[Treble-Enabled Device Development A/AB ROMS] newboihere:
Same issue. I will try reboot to system and again to fastbootD and try again.

Spoiler content hidden.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Stock fastbootd? It sounds quite impossible to me, as OEM-internal xTS testing definitely involves flashing Google GSIs and by extension a working fastbootd.
[Treble-Enabled Device Development A/AB ROMS] newboihere:
I have new information: after the previous test (trying to flash from TWRP and stock versions of fastbootD) even if in every case the flash failed for not being able to re-size system_a, I have already lost the conectivity (mac address, etc).

any suggestion what could I try next?
[Treble-Enabled Device Development A/AB ROMS] newboihere:
I am just a beginner, no idea about it, but I suppose that if there are several threads about people figuring out how to repack their super images for being able to flash custom ROMs, there must be a reason.

In any case it seems that this issue is not related to the ROM itself but to the Xiaomi implementation of their phones or even a specific issue of my device. If you want I can try to find help in other threads instead of here (any suggestions?)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The only OEM where repacking super was necessary is Samsung, but that became obsolete after PHH found out how to patch stock recovery to enable fastbootd. Some people also repack super for convenience, e.g. bundling together vendor tweaks for their releases. I don't know of another compelling reason to do this rather involved move.

I still can't quite believe a fully stock configuration would error out with "Failed to write partition table", as that means the super itself is configured wrongly even in stock. Please forget all about repacking, rooting and Magisk for now, return to the latest stock base with MiFlash + fastboot package, and flash only the GSI via stock fastbootd.
[Treble-Enabled Device Development A/AB ROMS] newboihere:
I have being doing that this morning. Everything clean and fresh with MiFlash, enter in MIUI13 to check that there is mac (and unlock USB debuging) and from there to fastbootD and same error. At least now going back to MIUI the mac is still fine, that makes me think that losing the mac was an issue with TWRP or Magisk (could that be possible?)

The only thing that could different in my phone compared to the "original" phone is that I modified GPT with gdisk to increase 500Mb the super partition reducing userdata partition, but it does not seem that MiFlash complains about it (it could detect it or even fail because the scatter file on the original stock rom used by MiFlash does not match with my phone GPT).

By now I have a working MIUI13 and no way to flash any GSI.

Should I try DSU loader to see if the GSI ROM works properly as a temporal system?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
One thing to note is that, at least on LOS, WiFi/BT MAC only shows when they're turned on, otherwise they're marked "unavailable".

????????????

And I think we found why your fastbootd is acting up - a size mismatch with what was pre-configured (in kernel I think?).

Yeah sure.
[Treble-Enabled Device Development A/AB ROMS] newboihere:
At MIUI13 <I have observed that> it shows the mac even when wifi is turned off, but bluetooth only when it is on.

Then anyone with a modified partition table would potentially have the same issue... it sounds more feasible to me that Xiaomi found a new painful way to obstruct custom roms in the new EROFS devices.

Nevertheless my options would be to revert to the original partition table (and, even if it works, I would have no space for custom ROMS with GAPPS) or to find a way to succesfully repack the super partition.

By now I will check your room by DSU load and try to ask other people with the same phone if they have similar issues.

Thank you for your time!
[Treble-Enabled Device Development A/AB ROMS] newboihere:
Something is not fine in my phone... DSU fails. Both using the native way (inside of development options) and using the "DSU Sideloader" app

Anyways, do not worry, this is going far from the topic of this thread, I will try to post somewhere else to have more advise and suggestions...
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Xiaomi don't suppose people go as far as modifying partitions...

I figured space constraint would be why you did it in the first place - you should've asked upfront. Removing stock system_ext and/or product from fastbootd is enough, like so:

fastboot delete-logical-partition system_ext
fastboot create-logical-partition system_ext 0

(If this device has AB partitions, add appropriate suffix)
[Treble-Enabled Device Development A/AB ROMS] newboihere:
I tried removing those, but still it was not enough, or maybe once there was enough space the error was the current one and I did't realised, we will never now ^^

In any case, in my current situation, maybe the best/simplest option would be to find a way to patch/restore the connections after flashing the super partition with LOS. Do you think it would be easy to find the lost information and copy it back to the right location?

Any idea how can I find the missing information or what am I looking for?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Without even knowing for sure you flashed the image correctly, this is a situation equal to using an unofficial vendor, and I can't provide you further help.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with April security patches and in sync with TD 20230417. [Insert obligatory backup-and-test warning here]

All modern Xiaomi/Redmi devices should be able to see high refresh rates now (if supported), without having to spoof properties globally.
[Treble-Enabled Device Development A/AB ROMS] fabioken:
Can I update from build lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img.xz to the new build without loosing my data?
[Treble-Enabled Device Development A/AB ROMS] mawa54:
hi,

just installed lineage-20.0-20230418-UNOFFICIAL-a64_bgN.img on my ulefone note 6t. wlan is ok. but browser and google play failed with ERR_NAME_NOT_RESOLVED. "adb shell" followed by "curl https://google.com/" is ok. it seems that the apps have no right to access the network ??

same with lineage-20.0-20230418-UNOFFICIAL-a64_bvS.img .

but no problem with system-td-arm32_binder64-ab-vanilla.img from android_13.0.0_r41 ci-20230417. and no problem with lineage-19.1-20230418-UNOFFICIAL-a64_bgN.img . any hint?

thanx

martin
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Take some time to read OP and #2...?
[Treble-Enabled Device Development A/AB ROMS] m0byn:
@AndyYan do you provide any other way of donating? I wanted to donate via the given PayPal link in OP, but would have to pay fees of 4€. I am from Europe.

Also, would you mind quickly answering this question? I am trying to figure out whether the patches are already included, and FOD should work, or if they are not yet included. It is interesting since FOD works on my Samsung Tab S6 without any overlay (as far as I can tell), but it does not work on my Samsung A50 for which an overlay is included (as far as I can tell).
[Treble-Enabled Device Development A/AB ROMS] mawa54:
Now i get it. All good now. Many thanks.
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
it should do.

at least here it did yesterday
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I'm in China, so even going through PayPal (+ a proxy "bank") is convoluted and costly. I don't think there's another convenient way out...

It's okay not to, it's not like I really fix bugs anyway :P

I sync with TD patches, so if it's fixed there, it should here.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The post on the MTK no-internet issue (#9, over at "Light") has been updated with a more persistent fix, courtesy of @Rortiz2 .
[Treble-Enabled Device Development A/AB ROMS] syneoa:
Thanks @AndyYan for these builds, enjoying them on my Redmi Pad 10, I was a long time Cyanogen user and happy to continue with LineageOS again. :)
[Treble-Enabled Device Development A/AB ROMS] MerGr:
Thanks Andy Yan for the port, you breathed new life into my STG H10 (MT6737), but I have one problem as I can not receive calls at all ? any idea how I can fix it ?

EDIT : I'm using the latest LineageOS 19.1 A64-AB
[Treble-Enabled Device Development A/AB ROMS] m0byn:
On my Samsung device "Trust" is saying that the vendor image is outdated. Can I download the current Samsung firmware, extract it to get the vendor.img, and just flash this image using Odin without wiping data or anything else?
[Treble-Enabled Device Development A/AB ROMS] stephengodwin895@gmail.co:
That isn't how the color should be
[Treble-Enabled Device Development A/AB ROMS] stephengodwin895@gmail.co:
Color for 19.1
[Treble-Enabled Device Development A/AB ROMS] nabulsi08:
Hello. I like this ROM, especially for it's battery life. One single improvement should be done soon: The Camera. Some Custom ROMs now use inbuilt Anx Cam which I recommend for this ROM. OR even better would be Anx Camera Leica Software for more Features. I'd love to use my 108mp. I mean, that's including what I paid for... Other devices have 108mp too, so I hope that's done soon. Thanks for your effort.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I've encountered a Work Profile bug in LOS. But I think it is more widespread, since it also occurs in the latest Phh's AOSP builds.

Brief description:

After installing Shelter (a WP management app), it successfully creates the WP. I'm able to use it fine, clone apps into it, run them, no issues.

So, I disabled WP via the statusbar pulldown toggle. Then I deleted the WP from the accounts menu. Within 2 mins, the device (my Note 20 Ultra running the A13 builds) gets stuck in a soft bootloop that is essentially infinite. It kicks back to the LOS logo and never let's me in. Even after a hard reset, I still can't get in. The GSI is basically perma-soft-bricked, and I haven't found a fix other than to wipe the data partition. The same behavior occurs on the Phh AOSP gsis, it never lets me in again after deleting the profile. I'm certain that it has to do with the deletion of the profile, since it never crashes while actually using Shelter in WP mode.

I've duplicated this several times on both gsis, the behavior is 100% consistent each and every time. Even if I just create the profile, clone no apps into it/run no apps within it, then delete the profile, the result is a softbrick regardless.

Since this bug is common to both gsis, who should I report it to? The obvious solution is to never delete the profile once it's set up, but that's not really a solution, per se. I'd rather report this bug and have it crushed. Or at least a workaround that let's me boot the gsi again.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
On most devices fast charging would work. The only exception I've seen so far are some old OPlus devices (e.g. OnePlus 8 series).

Go through the IMS/VoLTE setup, then let's talk?

There's more to the base than just vendor, you know...

We've briefly talked about it in #291, but Samsung certainly belongs to the risky type there. A theoretical method I can think of is flashing the full firmware with Odin, but use HOME_CSC (which retains data), then without booting into stock, immediately do whatever complicated GSI flashing steps (e.g. flashing a patched recovery, then go fastbootd, blah blah).

I simply ignore all Trust warnings - in using GSI I've already thrown many stuff out of the window anyway.

AFAIK, unlocking full resolution is done by patching vendor camera libs, which is beyond the scope of a system image.

ANX Camera is Xiaomi-specific - certainly I'm not including that in a generic system image. Please mod whatever you wish on your own.

GSIs cover the basic, and often not even fully at that. It sounds you're looking for a more fleshed out experience, so I suggest using one of the device-specific ROMs your device already has. (I'm totally okay with losing users over this.)

Log me while it loops, please?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'm not really that experienced with getting logs on boot. I've only done it twice a few yrs ago, but forgot the commands. What is the syntax for telling adb to dump logs to a file? Which I can then upload here.

Also, since I have up to 2 mins-ish, within Android, between the deletion of the profile and the crash, then maybe a logcat within the OS would be useful too?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: So, I was just about to upload 2 log files......when i just now realized that my logs are from the latest Phh AOSP GSI, not yours. I had last encountered the issue on Phh and totally forgot to reflash LOS before asking about logs. Leave it to me to totally blank out on these kinds of small details. Since they're not from your GSI, i wont provide them.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
No big deal, if it's about the same issue, should be the same logs as well. I'll reproduce locally too.
[Treble-Enabled Device Development A/AB ROMS] nabulsi08:
Thanks for your response. Unfortunately the GCam didn't work well for me. I've tried many Ports. That's why I'd love the Anx Camera inbuilt like some other ROMs. The reason I want to leave MIUI is the Battery life. I've tested some GSIs and it was noticible better. In MIUI Android System takes almost 30 percent, Google Play Services 10 percent and Others (I don't know what is meant with Others) 35 percent. That's approximately. But I need a good Camera... Seems like I have to keep MIUI...

Thanks anyway.
[Treble-Enabled Device Development A/AB ROMS] jeff862:
does this work with samsung note pro 12.2 --p905?samsung tab s7+--T975?please help
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: now I have logs from your gsi. One was taken from within Android by Logcat Extreme Pro app, it only includes the main buffer. With this log, I started recording, then immediately installed Shelter and went through these steps:

1. Let Shelter set up the work profile

2. No need to do anything with Shelter after this, pull down the statusbar and disable WP from its' tile

3. Find accounts in Settings, tap on WP, then select the option to delete it

4. Wait up to 5 mins, if no crash/softbrick by then, you're probably fine. My crashes triggered within 2 mins max

The other log was taken while I was stuck on the LOS logo, with the following command ran from Windows 10 while connected via USB:

adb logcat -d -b main -b system -b events -v time > filename.txt

it includes the main, system, and events buffers. I didn't invoke "adb root" before running the command, although I am rooted with Magisk on the latest arm64 bvn vndklite build.

if you're going to test, maybe you might want to do so on a Samsung, as well as non-Samsung device. I'd also welcome tests from other users, if they're willing to risk a softbrick. If you have twrp and data partition isn't encrypted, make a backup of that partition and try. That way you have something to fall back on if you get the softbrick. I'd understand if others don't want to take the risk because they don't have the option of restoring a full backup.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Stop, just stop. I have already tried to help you in the Tab S7+ TWRP thread, but you just keep buggering. It's starting to get a bit annoying. Honestly, do you really think that someone here knows for sure whether this LOS will boot on your specific model? Sometimes, you just have to try for yourself. There are many great minds in the past/present that made well known discoveries, and it was all because they were willing to just take a chance and try without knowing for sure. Without those people humanity wouldn't be where it is today. You can't spend your entire life being mostly dependent on others to answer your questions. There's a time to ask if you're not sure, but you also need to be willing to test for yourself. It's how we learn.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Is there any GSI that has that built in? Again, ANX is Xiaomi/Redmi-specific, and I find it hard to believe that it appears on anything that's not tailored for these (i.e. their device-specific ROMs, where there can be other device-specific changes accompanying these cameras).