yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you have TWRP, use the dd or simg2img commands

Example:

blockdev --setrw /dev/block/dm-0

dd if=/path/to/img/file/here of=/dev/block/dm-0 bs=1m

Adjust dm-0 according to the location of your device's system partition, which is located within super. Be careful though, you could accidentally overwrite something important. dd blindly overwrites without confirmation, so you must be sure your typing is correct.

simg2img can be used if the gsi img is sparse rather than raw. But most come in raw format.

If you prefer flashable zips, google "gsi flasher", follow the instructions in the thread. It's universal, should work for any gsi.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I want to like this gsi, but I just can't. And right when I was getting used to nearly everything just working well. I've spent the last hour testing outgoing/incoming calls, they just don't work. Data and texts work, but not calls. I've tried in different locations in my city, places where I always get great signal. Whenever I try to call any #, it never rings, no dial tone, nothing. I've texted several friends to ask them to try calling me. After waiting a few mins, they all say they've called, but it never rings on my end.

Since this is critical functionality, I have to walk away. Even more critical than exFAT. If I had to call 911 for someone I know, and couldn't, that would be a potential disaster. Calling has worked on every gsi but this one. TBH, I rarely call anyone, so when I do, I expect it to just work. It seems LOS is just a different breed, I've encountered issues on it that don't happen elsewhere.

I'm sure people will just respond with "works here", and that's no help to me. I don't give a **** if it works for others, since it doesn't work FOR ME. I hate those kinds of responses, so ignorant.

Edit: half an hour later, calling works. On other gsis, I can't ever recall a time when calls didn't work, regardless of my location. It definitely seems much more unreliable/spotty on LOS.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Understand your concern and choice, life and safety first.

I can try spotting something obvious if you have logs (from when someone attempts to call you for example), but as with before, I can't guarantee you I'd be able to find out...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I doubt that would help. And just mins before I was about to flash PE, calls started working. Either way, still an hour of downtown. While it could be a carrier issue, none of that explains why data/texts remained working all along.
[Treble-Enabled Device Development A/AB ROMS] _Kuki_:
Hi there, it would appear that downloads for LOS19-20 are missing from sourceforge, is it a problem on my end or is someone else seeing the same thing?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Scared me too, but on second inspection, seems to be a site display issue, as the files are still there when viewed via FTP (for uploading). Many other people have filed this issue in SF support already, we just gotta wait.
[Treble-Enabled Device Development A/AB ROMS] _Kuki_:
Alright, thanks for clearing that up.
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
Here are some instructions: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-Note-10-Pro--Pro-Max
[Treble-Enabled Device Development A/AB ROMS] Stan m:
Wow! I'm extremely grateful!

Thanks!!
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
the manual dd method is neither safe not straightforward.

Better use fastbootD (which is mainly the part of a recovery).

Google would tell you can run it with "reboot fastboot" from an Android.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I disagree. dd is only unsafe for people that don't know what they're doing. I've been using it for years and have rarely made a mistake, except in the cases of typing errors. It's just a tool, if used wisely and correctly, nothing bad will happen. How do you think I flash all my GSIs?

I generally only use Samsung devices, which usually don't have a functional fastboot mode. So even if I wanted to recommend fasboot, it's not an option for me personally, and I have very little experience with it.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Nope. It's just you, I can see them fine.

LOS19 by AndyYan
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Seems they've resolved it by now, phew.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
Thank you to all the devs. This TD based release is the most stable for my Xperia 1 III (BC72). The camera is working and no high pitched audio issues in MS-Teams and VoIP. 'Alternate audio policy' option fixed VoIP and 'disable stereo support on VoIP' fixed MS-Teams for me.

With the light version, camera wasn't able to save images and freezes. Also, MS-Teams has high pitched audio even with 'alternate audio policy' toggled on.

I'm one happy camper now! Keep up the good work!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
The stock camera fully works for you? For me, trying to use the rear camera made the app crash, but front camera worked fine. I also tried a few 3rd party camera apps, all working 100%. So it's just the camera app bundled into LOS that has a problem.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
Under "light", neither stock nor Sony's Photo Pro camera worked. With TD, both stock and Sony have no issues using front/rear/wide angle. I haven't tried gcam yet.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Ok. I never tried light, only the "regular" TD version. The reason being, @AndyYan has stated that light are personal builds that are custom tailored to his needs. I don't want that, since what he considers optimal may not be good for everyone else.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
I have an issue where I can search for 'Local Terminal' in settings and click on the search result, but it is not available/missing when viewing Developer options. This has been an issue since I switched from LineageOS 19.x to 20.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Maybe the terminal app isn't present at all? That's the only thing I can think of. If it's not there, you can always use Termux or whatever.
[Treble-Enabled Device Development A/AB ROMS] MIcHiJK:
Hello, I would like to take this opportunity to thank you. I have repaired a Huawei P10 from a completely destroyed condition with cheap spare parts. I was a little disappointed at first, because the several system images ran poorly or not at all. At last I had installed Lineage OS 19. This stuttered and there were WLAN aborts. Now I have installed the Lineage OS 20 image and it runs flawlessly. The performance is good and there are no problems. I hope such projects will continue forever to give old devices a second life instead of throwing them away.

EDIT:

Huawei P10 still WIFI Disconnects after 2 Minutes turning screen off. Checked the logs and found this issue reported 3 years ago:

WiFi disconnects after the screen is turned off · Issue #27 · enesuzun2002/LineageOS-Releases

If I turn off the screen, the wifi connection will be disconnected after a few minutes. Not sure if always, but almost every time This is present in 2020-04-18 and 2020-01-21 Builds. I have SM-G925...

github.com

Working workaround:

Activate adb debugging as root in dev options and start adb as root on your pc:

$ abd root

$ adb shell

$ echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6

Then WIFI stays connected after you turn the screen off.

EDIT 2:

The workaround i mentioned is just temporary. It works till you reconnect to the WiFi or reboot. Disabling Ipv6 on your router makes it work but then some services might not work for you which rely on IPv6.

Since its TrebleDroid based i tried to install the TrebleDroid Android 13 GSI. In the TrebleDroid GSI the bug is also present. Its not a specific LineageOS problem.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Is it safe to upgrade from an existing installation (lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-vndklite-secure.img) to the new version (lineage-20.0-20230115-UNOFFICIAL-arm64_bgN-vndklite.img)?

I would update via fastboot flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bgN-vndklite.img.

Of course I would like to take over my existing data incl. the GApps and Magisk.

Would this be the right way?

Would there be any other steps necessary?
[Treble-Enabled Device Development A/AB ROMS] _Kuki_:
Just wanted to ask, in the Phh Settings there is an "icon pack" option, how do I exactly add packs to it? I downloaded one from Google play that didn't work. Do I have to flash them? I tried googling for an answer but couldn't find anything.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
You can dirty flash with fastboot and keep user data and apps intact. Obviously, don't wipe user data. Just unhide Magisk before you do so and rehide after you're done. When left hidden, you may end up with multiple instances.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Has anyone seen something like this? In the Frost app (an alternative Facebook client), I can't attach photos when sending messages, it just says "file chooser not found". Beforehand it was working fine, but never in LOS20.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Temporarily solved by switching to another unofficial app, Facebook Lite. It properly allows choosing photos. It must be an issue with Frost maybe not being updated for Android 13. Was working fine on all A12 GSIs.
[Treble-Enabled Device Development A/AB ROMS] zyhk:
Isn't this caused by wifi suspend optimizations?

Try

settings put global wifi_suspend_optimizations_enabled 0, and switch wifi off and on.
[Treble-Enabled Device Development A/AB ROMS] MIcHiJK:
Thank you for you reply. But sadly this isnt working. The only workaround is deactivating IPv6 right now. But its a bad workaround. Sadly this makes the phone unusable even if the rom is working great. This bug is also present in TrebleDroid which is used as base. The "light" approach isnt booting. I can provide logs but im not able to fix the cause by myself.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
@AndyYan , what if I want the functionality like this: https://github.com/LineageOS/android_packages_apps_FlipFlap ?

How it should be added?

Thanks.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Does anyone else have problems with sending SMS?

Sending messages via RCS is possible without any problems.

The reception works as well. Only sending is not possible.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Never had an issue sending texts on this gsi. Just with phone calls consistently not going through in a select few areas. Sounds like a carrier issue. I use the AOSP messaging app, not google's messaging app. Or QKSMS, my fave 3rd party messaging app. No issue with that either, although i'm not sure if it supports RCS.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Thanks for your report on your experience.

Had tried the Google Messages app and also the AOSP SMS app.

Google Carrier Services is also installed.

On an Xperia XA2 with LineageOS 19.1 I was able to send SMS with the same apps and the same SIM card at the same location without any problems.

Where could the error be here?

The ability to send SMS is very important for me.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'm just going to reiterate that it's probably a carrier issue. That would be my personal best guess. Have you checked your APN settings? Maybe they are incorrectly configured.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Yes, they are as recommended by the provider and the same as on the other smartphone via which SMS sending was possible without any problems.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
OK. I get it. I misread you. I thought you meant that you were previously on 19.1, but switched to LOS20 and suddenly started having issues. Now I see that you're comparing a current device against another device that was also running an LOS gsi. If it was working on an older LOS gsi on the same phone, but not on 20, that wouldn't make much sense.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I kind of had a similar issue a few months ago, when I swapped my active sim card from an older phone to my Note 20 Ultra (the one I'm using now). This was on the stock ROM, not a gsi. Basically, I got a carrier message saying that my settings for texts/calls/data were incorrect. And it was offering to remotely reprogram my sim card with the correct settings. The message looked legit, so I accepted, and the issues went away immediately.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Unfortunately, I never received such a carrier message.

I have pulled a logcat to see if the cause of the error can be found in it.

These are the locations I would associate the error with:

01-22 10:47:03.574 5636 16695 E Bugle : SendStatusReceiver: failure in sending message part. partId: 0, partCount: 1, resultCode: 104, errorCode: -1, messageUri: content://sms/7379 {x-message-id:0}
01-22 10:47:03.582 5636 16695 E Bugle : SmsSender: Unexpected sent intent resultCode = 104
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If it's an issue with GApps (worth testing), install DSU Sideloader. Grab the latest LOS 20 img file that doesn't have GApps. Use the DSU app to install that as a dualboot gsi, then boot into it and test there. You won't lose your current LOS if the results are similar. Just a quick reboot and you're back in. You can install and boot the whole thing in under 10 mins, on a reasonably fast device. But it needs root. Installation via adb is also supported, but I've never tried it that way.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Unfortunately, the logcat isn't very useful in this case, all it's saying is that the message failed to send with the Google app, with a result code of 104. But it doesn't give any real hints of the underlying problem.

There are logcat apps out there that can also check the modem logs, as well as Android's logcats. I think a modem log would be more useful, but it will probably be hard to interpret.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Here is the full logcat.

I hope more can be seen from this
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Not many views on your logcat. I checked it myself, couldnt find anything that stood out. Worst case, reflash stock firmware and test there. If it still happens there, then gsis in general can be ruled out as the culprit. Might also be worth getting a replacement sim from your carrier, available for a small one time fee. Or switch to esim, if your device supports it.
[Treble-Enabled Device Development A/AB ROMS] hunter3000:
Does anybody works Gpay via magisk with safynet fix? when i try to run this only shows for a while and closes.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Not working for me. My local transit authority uses Gpay as a payment option. But it always fails when I try to use it to buy tickets in their app. NFC is enabled, and I've already added a credit card.

I'm rooted with Magisk Delta and have @Displax's modded SN fix installed. All SN checker apps show that I pass. Pokemon go works, my banking app works. But Gpay/Android Wallet apparently doesn't.

Google should stop hating on rooted/unlocked/custom ROMed devices and just let us pay. As long as they get our $, why does it matter? They're greedy, but apparently not greedy enough to not discrimiHATE (intentionally mis-spelled) against us.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Thank you for your help.

Curiously, I tried sending an SMS to a new recipient over the weekend and it worked flawlessly.

With the messages that could not be sent, it can not actually be the receiver, because I could send SMS from the same cell with the same settings and the same SIM card from my other smartphone.

So SMS sending works, but only with certain recipients, while with other devices SMS sending works with all recipients.

I just can not figure it out.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Have you tested with any other non-LOS gsis? If so, same issue? What about testing on stock firmware?

Nearly all gsis use a lot of @phhusson's AOSP source code, it's a good idea to try them as a baseline for troubleshooting.
[Samsung Galaxy Note 20 Ultra Questions & Answers] aspidxt:
I have thermal camera (Hti-Xintai HT-201) it's connecting to phone's usb. When I connect it to my Note20U nothing happens, devise isn't starting. Flash drive works fine though.

But it works on my old Samsung S8. Moreover if I connect it to S8 and then quickly reconnect to Note20U it's works fine there, untill I disconnect it for some time

Same trick works if I connect thermal camera to power bank and then to Note20U.

Is it possible to configure OTG to provide power for longer so device can initialize?
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
I would be very thankfull, if you could help me with my problem.

After unlocking my bootloader successfully, I re-enabled USB Debugging in MIUI and booted into fastboot mode.

From there I booted the latest "twrp-3.7.0_12-0-munch.img"

1. Which is the correct way to install TWRP permanently (or after an TWRP update)?

https://twrp.me/xiaomi/xiaomipocof4.html

"Flash Current TWRP" or "Install Recovery Ramdisk"?

[Edit] ➡️ Flash Current TWRP

To remove encryption it is necesarry to "Format Data" before? or after? ROM flash. When I do that, all TWRP settings are gone (language, vibration off, 24h clock). Are these settings not stored permanent?

[Edit] ➡️ Before and after recommended here » OrangeFox Recovery wiki

2. When I want to flash ROM + GApps, do I need to reboot the recovery for switching partitions?

I flashed "Spark-13.1-Official-munch-20221025.zip" and "NikGapps-core-arm64-13-20220908-signed.zip". I can boot SparkOS, but there are no Gapps installed. The flashing process was skipped.

[Edit] ➡️ Yes

Thank's for your help!
[Xiaomi Poco F4 (Munch) / Redmi K40S] UniNick:
1. after fastbooting TWRP use Flash Current TWRP. No format data.

2. SparkOS needs global firmware to be flashed first, then reboot to recovery, then flash ROM, then format data.

There is a version with Gapps already included, working fine.
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
@UniNick

1. Flash Current TWRP is the prefered Installation Method from official site. Do I need to reflash TWRP after each ROM flash to survive? When formating data after ROM flash, the TWRP setting are also deleted (no more TWRP folder in internal storage).

2. My Poco F4 was shipped with MIUI Global 13.0.3.0 (SLMEUXM). So I downloaded and flashed Europe V13.0.7.0.SLMEUXM from https://xiaomifirmwareupdater.com/firmware/munch/

Baseband version is now higher.

I know there is a Gapps Version of SparkOS, but I don't know which Google apps are included and I just need a minimum of the package. Therefore I asked how to flash Gapps after ROM.zip, that both are on the same A/B partition.

I already had to reset/flash the "V13.0.5.0.SLMMIXM_20220815.0000.00_12.0_global" with MI Flash tool, because I had no access to Internal Storage with my PC to copy files on Poco F4.
[Xiaomi Poco F4 (Munch) / Redmi K40S] UniNick:
1. yes because most ROMs now bring their own recovery

2. Spark includes like a basic Gapps package
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
I will try it again tomorrow. Thanks!
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
After a lot of research I still have some questions. Many users have trouble understanding it when the installation instructions do not list all the steps.

I have read these flashing instruction on the XDA NikGApps page:

Flashing Instructions for A/B devices (Clean Flash is recommended)

Flash Rom in Slot A, Flash twrp, reboot to recovery

Flash Rom in Slot B, Flash twrp, reboot to recovery

Flash NikGapps

Flash Debloater (Optional)

Reboot

So I thought, that this would be the steps:

### First Install / Clean Flash ###

- fastboot boot TWRP image

- in TWRP select "Flash Current TWRP" under "Advanced"

- flash firmware

- reboot recovery (is this reboot necessary before flashing ROM ??)

- wipe > factory reset (recommended or not ??)

- flash ROM (current Slot A > flashing to inactive slot B)

- flash twrp.img in boot partition + (check the box "Flash to both slots" ??)

- go to "Reboot" and change slot

- flash ROM (current Slot B > flashing to inactive slot A)

- flash twrp.img in boot partition + (check the box "Flash to both slots" ??)

???

(optional for GApps)

- flash GApps

Error: Could not mount /system

- format data

- flash twrp.img (again necessary ??) + (check the box "Flash to both slots" ??)

- boot to system + install Magisk.apk

- in Magisk: patch boot.img

- reboot recovery

- flash magisk_patched.img in boot partition + (check the box "Flash to both slots" ??)

- reboot to system
[Xiaomi Poco F4 (Munch) / Redmi K40S] psklf:
Little bit complex.

Try this guide:

Reboot to recovery (twrp or ofox), I prefer boot recovery by fastboot, command is `fastboot boot rec.img` (You can download from orangefox official website)

Flash firmware (Optional)

Flash rom

Flash gapps (if flashed vanilla build)

Format data

Reboot to system
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
I'm not sure if GApps will be installed in the same slot if I flash it directly after the ROM.zip.

I have to reflash TWRP/OrangeFox before formating data and booting to system or it will be lost when I boot back to recovery.

When updating the ROM, the recovery is flashing it to inactive slot. Do I need to click through the (google) setup again, or is this data stored in another partition? When do I need to reflash GApps?

flash ROM.zip

wipe cache + dalvik

reflash recovery

reflash magisk_patched

reboot system
[Xiaomi Poco F4 (Munch) / Redmi K40S] psklf:
About GApps maybe this is the right way ...

flash ROM

flash recovery itself( w/ orangefox there is a checkbox)

reboot to recovery

flash gapps
[Xiaomi Poco F4 (Munch) / Redmi K40S] hammerheadache:
Please bear with me, as this is my first A/B device and I'm quite confused about the flashing procedure.

I successfully unlocked bootloader and flashed TWRP.

I tried to install A13 SparkOS vanilla + Basic NikGapps. Like @11insomnium said in the 1st post, ROM was installed fine, but Gapps package was not. I tried what @psklf says, no good... Each time I try to flash the Gapps package I get a message that /system size is 0KB, and of course the setup process is skipped due to lack of space...

On a side note, when flashing the ROM, step 1/2 completes fine, but on step 2/2 I get some errors about failing to access /system, /system_product, /vendor etc... However, as I said, ROM boots fine afterwards...

Am I missing something? Or is flashing the integrated Gapps ROM version the way to go?

@11insomnium did you manage to sort this out?
[Xiaomi Poco F4 (Munch) / Redmi K40S] 11insomnium:
@hammerheadache I'm still using the GApps version 20221113, but recently I updated my device to latest OFox recovery (R11.1_2_A12) and A13 firmware (V14.0.2.0.TLMEUXM). The result was that my fingerprints were deleted and I could't save new ones, so I reflashed the old version (V13.0.7.0.SLMEUXM).

I think you missed the reboot to recovery. This should work for you:

- flash ROM

- flash recovery

- reboot to recovery

- flash NikGapps

- reboot to system

Edit: Maybe this will also help you:

https://wiki.orangefox.tech/en/guides/flashing

I haven't completely understood it yet either 🙈
[Xiaomi Poco F4 (Munch) / Redmi K40S] amn1987:
I have read in EROFS ROMs like Spark or PE it's problematic to flash GApps or microG as the system is read-only. Also applies to some Magisk modules as well.
[Xiaomi Poco F4 (Munch) / Redmi K40S] hammerheadache:
Thanks for the info. That explains why there are ROM versions with GApps included.