yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] :
I've installed magisk 21.2 via twrp and everything was OK, but into the ROM it's like I haven't installed it. There's no root privilege. I followed the same steps of Lineage 17.1 but now it doesn't work. I have a Samsung a20e and in others GSI I installed Magisk without problems.
[Treble-Enabled Device Development A/AB ROMS] AshAssassin:
Try these - https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/

First try the v20.3-15bd2da8 build, it works on my device running the same 17.1 GSI.

If your device gets stuck at boot, then flash the magisk uninstaller zip (download it from the official magisk thread).
[Treble-Enabled Device Development A/AB ROMS] :
Thanks, I'll try it
[Treble-Enabled Device Development A/AB ROMS] Sanket Kalore:
A11 gsi are first neended to be made rw and edited to put magisk path like this follow these steps

Tutorial how to install magisk in A11 gsi ✌

Requirements :

Phhsuper su, mixplorer apk, or magisk zip (which you want to install) that's it 👇

1st : Create sbin folder in root storage if not available

2nd : now go to last in Root Storage and you see a 'init.environ.rc' file, open it in text editor and just add this line 👇

export PATH /sbin:/vendor/bin:/system/bin

And save it, remember you need root access for doing this all step : so install phh super su first and after doing above step

For safety net Change device fingerprint to pixel 3 A11 it works

As u said u get no superuser then edit that file in other gsi n paste via twrp file manager
[Treble-Enabled Device Development A/AB ROMS] Sanket Kalore:
Is there any way to contact AndyYan Sir
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
Hm, perhaps you should first read this: Generic System Image - what is it. Then, when somebody makes a "LineageOS-GSI", guess, will it be LineageOS or AOSP (pure Android)?

K.
[Treble-Enabled Device Development A/AB ROMS] :
Thanks, I'll try this way too
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Made a test build just now, but found out that somehow BT was broken. Can't release it like this, need to look into it.
[Treble-Enabled Device Development A/AB ROMS] birdibird:
The 19 Dec build is great. I am on a Cubot kingking mini and have seen no bugs yet. Everything works and it's very fast.

Thanks Andy & PHH

edit: only thing is that I can't get Magisk to work (on 17.1 it worked)
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
Thanks for this Los 18, smooth on my vndk 26 device. Only I don't have sounds at all. But I fixed it from @hamido guide in phh telegram. Hope next build this will be fixed..
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
Take your time :-).
[Treble-Enabled Device Development A/AB ROMS] AyHenry:
Is it gonna be based on Phh's 3.00L (latest stable release)?
[Treble-Enabled Device Development A/AB ROMS] AboodySahhaf:
how can I install it on a phone galaxy note 20 ultra
[Treble-Enabled Device Development A/AB ROMS] sam tyler:
If I understand this right, does this mean I would have to build myself a gsi ROM and the patch? I think that is a little beyond my pay scale. thanks for replying.
[Treble-Enabled Device Development A/AB ROMS] x53:
Shouldn't Settings -> Phh Treble Settings -> Misc features -> Securize suffice?
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
Can you provide instructions how to flash gapps? I cannot due to error 70 not enough space in system. There must be a way to do this?
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
How do you install PHH-SU? It fails to install for me. There is no TWRP for Xperia 10 III. So this looks like a dead end. I need to get gapps installed somehow and I am not able to. Even using franko with root and get error 70 not enough space in system
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Use VNDKLite (/system RW), and resize /system in TWRP before installing GAPPS, that's all I know.

As said in the 19.0 thread, I shouldn't even be offering help on GAPPS/SN, any info from me regarding these could be false/outdated.

Just the app (an APK), I don't believe that would fail.
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
I have Xperia 10 III, unfortunately there is no TWRP
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sorry, "error 70" was illusive. I'm afraid my 18.1 isn't for you then.

I know someone else who once successfully built 18.1 with GAPPS though, if he's willing to upload and share...?
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
Thanks for your help. That would be nice if someone could share that build.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
I was able to install OpenGapps Pico without TWRP as a Magisk-module.

This skript was the key to convert a regular OpenGapps-zip in a magisk-module.

Can anybody help with getting SafetyNet-checks passed?

My Device is Sony Xperia 10 III (Lena) with unlocked bootloader, with latest LOG18.1 GSI (vndklite).

Tried already:

Magik deny-list (Zygisk)

Magisk-module Universal SafetyNet Fix

Magisk-module Shamiko

Magisk-module MagiskHide Props Config

LSposed-module HideMyApplist with Magisk-module Enhance mode

Magisk gives me this warning after opening the App:

An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
OK, I am already a big step closer to the solution.

After installing Magisk regularly, I first installed the Franco Kernel Manager because of the lack of TWRP for my device.

Through this I was then able to flash UnSu.zip, which completely removed phh-su (/system/bin/phh-securize.sh didn't work).

This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.

Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.

YASNAC now already showed "Basic integrity -> Pass".

But now I have not found a way to pass the CTS-profile match.

Does anyone here know what settings to set via MagiskHideProps Config?
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
It works and gapps is installed, however google contact sync does not work.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
I don't use google contacts, therefore I have not noticed.

@gnomiik

Is SafetyNet passing for you?
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
It fails. To be honest I don't even know what Safetynet is for. All my apps work just fine. What do you use as an alternative for syncing contacts? I wouldn't mind getting off google
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
The SafetyNet status indicates whether a device meets a set of safety standards set by Google.

Various tests run in the background for this purpose.

Mechanisms such as signature spoofing or various Magisk apps are used to try to obtain a valid SafetyNet status even for custom roms that might not meet the strict requirements, e.g. by hiding the fact that the device is rooted or has an unlocked bootloader.

Most banking apps as well as some other apps like Pokemon Go check the SafetyNet status and cannot be started if SafetyNet fails.

It is also a prerequisite for the device to be considered "certified" in the PlayStore. Only certified devices can download certain apps, such as Netflix.

Good alternatives to synchronize contacts are DAVx⁵ or ActiveSync.

You just have to check whether the desired provider and the apps used support CardDav or ActiveSync.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
For me Securize also didn't work (Sony Xperia 10 III).

I solved it with flashing UnSu.zip.
[Treble-Enabled Device Development A/AB ROMS] Aj_$tyle$:
hey @AndyYan are you going to provide security patches for android 11 ?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Am I not doing that right now? :)

If no other factors interfere, I'll build 18.1 until T comes out, supposedly around September.
[Treble-Enabled Device Development A/AB ROMS] nancy6:
We're waiting for March 2022 security patches.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Merged barely hours ago, plus I'm busy with 19.1 right now.
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Hello

I think you are missing part of the logs, you don't have the beginning. I pass you my logs under EMUI (Siberia 302 and DarJoker Kernel). WIFI works perfectly.

My log start at 11.706695 and you at 17.205139
[Treble-Enabled Device Development A/AB ROMS] T3mmi3:
Was able to flash both 18.1 and 19 on my Xperia 1 III XQ-BC62 but my service is not working. It detects the sim card on both slots but doesn't receive service. Sorry in advance if there is an easy fixed I missed but I couldn't find a fix relating to my issue anywhere. I was able to get service on a rom with gapps preinstalled but not for this rom.

On a sidenote, is the only way to flash gapps without twrp or do i have to sideload it with root?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with March security patches. [Insert obligatory backup-and-test warning here]

Back in mid-November I made a silent change to the variant names, from `treble_arch_xxx` to `lineage_treble_arch_xxx`, since the prefix is needed for Lineage's build system (see corresponding issue). However, recently while inspecting a bug specific to my LOS GSIs, I found out that the new name might be too long and overflow certain hardware HALs. This build attempts to rectify that by trimming the names to `lineage_arch_xxx`. If you hit weird bugs that's specific to this GSI and only happened starting December, it might be related and this build might fix it.

cc @Crrrr
[Treble-Enabled Device Development A/AB ROMS] Hugo B.:
Hi, the rom works great on my Samsung A530F but I can't set a pin/ password or any kind of lock. Attached are the logs, "relevant.TXT" is the crash part. "logcat.txt" is the full log. Any ideas on how this may be fixed? Thanks :)
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
Thanks for cc-ing me. Unfortunately, the jack problem persists.

The last version that does not have this problem with regards to the Samsung A20e remains the older older 18.1-20211108.
[Treble-Enabled Device Development A/AB ROMS] x53:
Solved: Big delay receiving SMS (e.g. 30 minutes) using buildin SMS/MMS app (com.android.messaging). Or even worse you have to unlock your phone to receive a message. Solution: Use a third party app (e.g. Simple SMS Manager) or do once: adb shell dumpsys deviceidle whitelist +com.android.messaging. Here I've found a detailed explanation.
[Treble-Enabled Device Development A/AB ROMS] x53:
Is it somehow possible to unlock the phone without those first swype up? Older android versions asked instantly for the pattern or the password after pressing the power button! Now we have to swype up additionally after pressing the power button. I don't like that. I have read that some os have a function to disable that. Does exist a setting (e.g. skip the slide page) within lineageos or is there some way using adb? Would be glad for suggestions.
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
In call volume is low. How can it be increased? Yes, I've already installed viper and it raises volume by +6db on all apps except for in call volume it doesn't work. I don't have qualcomm so the mixer_paths edit won't work. I tried modifications to /vendor/etc/default_volume_tables.xml since I have a mediatek device, but that also did nothing. Any help would be appreciated!
[Treble-Enabled Device Development A/AB ROMS] x53:
I have MTK device, too. Using buildin audioFX app doesn't help? Otherwise I've found the advice to use engineering menu to increase or calibrate volumes. Sadly we can't reach it typing *#*#3646633#*#* using lineageos, it's only possible with stock rom. I'm searching a solution for myself.
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
I can't reach the engineering menu either. AudioFX doesn't affect call volume only music or volume in other apps.
[Treble-Enabled Device Development A/AB ROMS] gnomiik:
Does anybody have a solution how to reach MTK Engineering Menu in LOS? This has to be solvable!
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Anyone using this on a Moto G Power (2021)?
[Treble-Enabled Device Development A/AB ROMS] nancy6:
We're waiting for the April 2022 security patches.
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
Excuse me? @AndyYan does this as a community service. We have no right to expect/wait for anything. FYI he posted an update to Sourceforge on 10th April if you can be bothered to look.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
It's built, not uploaded yet due to IRL events. Had to rebuild a few times due to unexpected problems.
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
I have also same problem to build LeaOS ..rebuild few time
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with April security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] Cenfus:
I'm wondering if this rom will work on a Umidigi f1 play.
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
Check if it is compatible with Project Treble. There is an app for that. As a general rule, GSIs work only on Project Treble devices.
[Treble-Enabled Device Development A/AB ROMS] Cenfus:
My phone supports Project Treble but not seemless system updates. Is that a problem?
[Treble-Enabled Device Development A/AB ROMS] -Alf-:
It's not a problem at all.
[Treble-Enabled Device Development A/AB ROMS] Cenfus:
Excellent, will report back if successful.
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
The difference is that you will have to install the updates manually using TWRP.
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
I am happy to inform you that the jack problem has been solved with the lineage-18.1-20220414 version, with regards to the Samsung A20e.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Fun, I didn't do jack (pun intended) about it :ROFLMAO: Guess it was something upstream...
[Treble-Enabled Device Development A/AB ROMS] silvio.alencar:
[Xiaomi Mi Play: 'lotus']

Hey there... I have a A partition scheme device (Xiaomi Mi Play, 'lotus').

I've attempted to install/boot 18, 17. While they won't even show the boot animation, version 16 is working. I'm using it for couple days.

The questionar: Is it possible to upgrade by flashing 17 or 18 'over it' with an img? Not a clean install, I mean.

Or flashing via twrp or 'fastboot flash system' will result the same as 'dd' command and ultimately will result in data loss?

I'd like to know this way works because I wasnt able to reproduce anything promising by clean installing 17 or 18.

Thanks!

UPDATE:

I've attempted to flash without formatting and performing clean installs. I was unable to make it work. Thanks all.
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
If your problem is data loss you can use the Migrate app.
[Treble-Enabled Device Development A/AB ROMS] silvio.alencar:
Huh, I think I didn't make myself clear, but my major concern woulbe be installing LOS18, or 17 but I couldn't managed to do it.

Eventually I decided to stay on LOS16, since I wasnt able to install 17 or 18. Stills better than bloated MIUI.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]

EDIT: Some bootloops happened below. Until those are cleared (resolved, or at least figured out why), exercise extra caution.
[Treble-Enabled Device Development A/AB ROMS] Mohinesh:
Am getting bootloop in The lastest version...idk if its only me...can anyone confirm?
[Treble-Enabled Device Development A/AB ROMS] keymanhattan:
19.1 on A12 - A127F installation ok -no errors- but goes on bootloop
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sh_t, I made zero changes on my side... I'll spare a test device and investigate. If one of you can log me the boot loop it'll be nice too. Others, please exercise extra caution.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
What @gregeerg sent me:

E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E AndroidRuntime: java.lang.IllegalStateException: Signature mismatch on system package com.qualcomm.qti.logkit.lite for shared user SharedUserSetting{11ffcb2 android.uid.system/1000}

Looks like the OS is tripping over a non-standard vendor app, and even more unexpectedly, if I understand correctly, happens on a clean wipe too.

@Mohinesh @keymanhattan Please post here in public (no PMs - leave debug traces available for searching in the future):

At least 1) which phase you looped at (OEM logo? LOS logo?), 2) wiped data or not and 3) does PHH's final AOSP R build work for you;

And ideally 1) logcat on this release, and 2) which (if any) previous LOS release once worked.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
At least you have ADB. While bootlooping, try:

adb shell
su
pm disable com.qualcomm.qti.logkit.lite
reboot

And see if it goes further. If not, more logs, it might get stuck on some other apps.

I've added some more needed info on the above post, please go through and let me know what you missed too.

Also, I've tried reproducing on my side using a copy of the app I found in FairPhone 3. Unfortunately I can only semi-reproduce it - it does spew out a similar error on directly installing the APK:

INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.qualcomm.qti.logkit.lite has no signatures that match those in shared user android.uid.system; ignoring!

...but when embedded into vendor, it doesn't cause a bootloop and seems to just get ignored silently with no mentions of it.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@gregeerg 's bootloop had been narrowed down to the rogue QCOM LogKit app plus a dirty /data. However, as @keymanhattan 's device is Exynos-based, I suppose this reason doesn't apply to everyone. @Mohinesh @keymanhattan - as the last mentioned message said, waiting on your info.
[Treble-Enabled Device Development A/AB ROMS] keymanhattan:
@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
It's not that clear cut. Go back to that post and post all info as required there.
[Treble-Enabled Device Development A/AB ROMS] jfudisj_17639:
Hi, so I installed this GSI on my SM-A125F and I have a problem: when I boot the phone it works perfectly, but when i lock the screen or it goes black, the touch doesn't work anymore until I reboot the system and the same again.

Can anyone help me please? Thank you.
[Treble-Enabled Device Development A/AB ROMS] Crrrr:
In general (not only for this update) I get a bootloop at the LOS logo after recharging my Samsung A20e from zero battery. However, I discovered that if I simply log to TWRP and from there I select reboot to system I get a normal boot. Maybe this could do the trick in this case as well ...?
[Treble-Enabled Device Development A/AB ROMS] tosiaczus:
Samsung A51 sm-a515f

Version below works fine

lineage-18.1-20211108-UNOFFICIAL-treble_arm64_bvS-vndklite

Version:

lineage-18.1-20220511-UNOFFICIAL-arm64_bvS-vndklite

cause bootloop

After Samsung's boot logo there is black screen for few seconds and reboot.

There is logfile in the attachment. console-ramoops-0

[ 0.000000] [0: swapper: 0] charging_night_mode : 0x0(0)[ 0.0 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Treble-Enabled Device Development A/AB ROMS] tosiaczus:
In that case I am disoonnecting the usb and then restart phone pressing vol- + power and then connect usb again.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Checked the log, unfortunately it seems too early a failure and beyond my skills.

At this moment I can only suggest 1) trying a newer (but still R) stock base, and 2) trying LOS 19.x instead.
[Treble-Enabled Device Development A/AB ROMS] Nowty_Nethshan:
i managed to get bluetooth media working by enabling "Force-disable A2DP offload" and bluetooth workarounds to "MediaTek" as my phone is a galaxy A10s, but the audio seems to randonly cut off and comeback and also the bluetooth range is VERY VERY poor. cant walk like 2 feet away from bluetooth device , audio stops playing. Thanks in advance for any help! Also im using the vndklite version.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with June security patches. [Insert obligatory backup-and-test warning here]

Next month's will supposedly be the final 18.1 build, after which I'll need to make room for The nexT big Thing.
[Treble-Enabled Device Development A/AB ROMS] DarkEvinho:
how to instal Gaaps on LOS bvS.img , dont works for me (partition size small error in twrp)
[Treble-Enabled Device Development A/AB ROMS] x53:
Little side note: I've dirty flashed lineage-18.1-20220511-UNOFFICIAL-a64_bvS.img.xz over lineage-18.1-20220315-UNOFFICIAL-a64_bvS.img.xz and have had problems with two apps. Those apps (OsmAnd and Transistor) didn't work anymore. They had forgotten all settings like factory settings. Even worse they won't accept new data. Bottom line all resettings didn't help. I had to reinstall both apps. However, I don't see a difference between reinstalling apps or removing app data and cache. But in my case there was a difference. Osmand has had a second big problem. With ROM 20220315 I had located all my maps and data on external sd (folder: /storage/xxxx-xxxx/Android/data/net.osmand.plus/files). This place doesn't work anymore using the new rom. Since rom upgrade Osmand has no rights to read/write this folder, created by it's own?!? Since that new rom I have to place all osmand data in /storage/xxxx-xxxxx/download/net.osmand.plus/files. I know about the access problems using Android 10/11. But in my case I was using Android 11 the whole time and I did only a small upgrade. Bottom line, I never would have guessed so much problems and work with this small upgrade. Has anyone noticed similar problems e.g. with other apps? I've some other older apps installed. They showed no such problems.
[Treble-Enabled Device Development A/AB ROMS] HProt:
Hi, tell me what's wrong. If i used GSI from Google and charging with the device turned off it work fine. When i use GSI Lineage OS and charging with the device turned off, tablet show logo and does not load, generally freezes and does not turn off even if the wire is pulled out.

I see that in the GSI Lineage OS in /system/init/hw/hw/init.rc the gsicharger service is spelled out and in /system/etc/init/hw/init.rc at the bot charger. Maybe this is the matter? But there are no lines in boot.img

on charger

class_start charger

on property:sys.boot_from_charger_mode=1

class_stop charger

trigger late-init

I tried to add with my hands

on charger

class_start gsicharger

on property:sys.boot_from_charger_mode=1

class_stop gsicharger

trigger late-init

Does not work.
[Treble-Enabled Device Development A/AB ROMS] Sheepmister:
Flash Rainbow kernel it fixed the touch issue,search in samsung galaxy a12 thread