yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Johannes89:
Hi i forgot.. Should i install something else too ARM64 a only didn`t boot maybe i skipped something?

can you show what i should install?

or complete setup for arm64 a only ,samsung galaxy s6

I dont know if it even fit here lol maybe my vendor is not good enough
[Treble-Enabled Device Development A/AB ROMS] santosst:
I tried to boot LOS18 on my Chuwi Hi9 Air (vndk26, A-only) and have no success.

Although the boot "stuck on vendor logo", I was able to take logs, and the problem seems to be related to missing libraries. If you prefer, I can send the logs through phh's group.

The first log shows a lot of errors regarding liblog.so, like

03-09 05:52:01.705 720 720 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.audio@2.0-service-mediatek": library "liblog.so" not found: needed by main executable

Then I added liblog.so to /system/system_ext/apex/com.android.vndk.v26/etc/vndksp.libraries.26.txt and copied these libs from ROAR. I also copied libstdc++.so from ROAR to the folders /system/system_ext/apex/com.android.vndk.v26/lib and /system/system_ext/apex/com.android.vndk.v26/lib64 since I did not find them (and I know they are essential for my device)

With these updates, I tried to boot again but failed. The second log shows other linker errors like these:

03-09 06:49:12.492 738 738 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.mediatek.hardware.imsa@1.0-service": library "android.hidl.base@1.0.so" not found: needed by /vendor/lib64/vendor.mediatek.hardware.imsa@1.0_vendor.so in namespace (default)
03-09 06:49:12.540 733 733 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.wifi@1.0-service": library "libwifi-system.so" not found: needed by main executable
03-09 06:49:16.250 1114 1114 E vndksupport: Could not load /vendor/lib64/hw/android.hardware.keymaster@3.0-impl.so from default namespace: dlopen failed: library "libkeymaster1.so" not found: needed by /vendor/lib64/hw/android.hardware.keymaster@3.0-impl.so in namespace (default).
03-09 06:49:16.258 1115 1115 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/viarild": library "librilutils.so" not found: needed by /vendor/lib/libc2kril.so in namespace (default)

I checked that some of these libraries are present in ROAR, so I think they need to be here in LOS too.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
So yeah, that A-only build still doesn't really work... Frustrating :/

If it doesn't work for you, can you report your VNDK version? Sounds like that Oreo (26/27) has another issue of its own.
[Treble-Enabled Device Development A/AB ROMS] ariadnejro:
Your latest LineageOS 18 ROM boots ok on an Alldocube X Neo, a AB Snapdragon 660 tablet. However, I had to go back to 17.1 for two main issues: Chrome can't sync with a google account (although other apps as Gmail or Keep can) and the system doesn't boot if I install Magisk. HW acceleration was working fine. By the way, which are the recommended Gapps for Android 11?
[Treble-Enabled Device Development A/AB ROMS] Tims Fong:
lineage-18.0-20201116-UNOFFICIAL-treble_arm64_avS.img can't booting Stay in the power-on animation,SD821,vndk27 Aonly.thanks.
[Treble-Enabled Device Development A/AB ROMS] -Alf-:
Null
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Another A-only build should be uploaded in the coming hours while I sleep (cable net's a snail at night). See if this one works?
[Treble-Enabled Device Development A/AB ROMS] Tims Fong:
lineage-18.0-20201116-UNOFFICIAL-treble_arm64_avS-v2.img,SD821 vndk27 Aonly,Booting! Nice!So far. It's the best Android 11 GSI.
[Treble-Enabled Device Development A/AB ROMS] santosst:
This new build worked well for me:victory:
[Treble-Enabled Device Development A/AB ROMS] romulocarlos:
Hello everyone!

Someone using this ROM on a Moto G8 Plus can do me a favor? Test if wifi works well when bluetooth is turned on, and vice versa?

I'm asking because on stock ROM we're facing a big problem... A lot of people (a mean a really LOT of people) is facing this: when wifi and bluetooth are turned on at same time, wifi performance slow down a lot, bluetooth lost connection or can't pair, and other bugs. Just look at google for "moto g8 plus wifi bluetooth problem" and you will understand.

By this way, we can sort wich type of bug is this (hardware or software, mainly).

Thanks in advice.
[Treble-Enabled Device Development A/AB ROMS] michaelmantz:
i installed this on my remi 9 with dynamic system update, how can install google play store? can't figure out which google apps i need to make google play work...
[Treble-Enabled Device Development A/AB ROMS] Tims Fong:
https://sourceforge.net/projects/opengapps/files/arm64/test/20201116/
[Treble-Enabled Device Development A/AB ROMS] michaelmantz:
Thanx but, i don't know If Installation trough twrp works in dynamic system Update?
[Treble-Enabled Device Development A/AB ROMS] ygb7:
The lineage-18.0-20201116-UNOFFICIAL-treble_arm64_avS-v2.img does not boot on my ZTE Axon 7. After flashing the image with TWRP 3.2.3, It just keeps booting back into TWRP 3.2.3 Recovery menu.

I run lineage-17.1-20201114-UNOFFICIAL-treble_arm64_avS.img.xz just fine on the same ZTE Axon 7.

Do I need another Boot image, Vendor or Recovery to run Lineage 18?

I would really appreciate a pointer to step by step instruction for installing Lineage 18 that include which required boot, vendor, recovery files are necessary to successfully run Lineage 18.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
We've booted on multiple devices by now, Oreo vendor included, so at this stage I reckon it's a device-specific issue. Tried AOSP yet?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
You might have noticed that I've uploaded test builds for other archs, but obviously leaving several uploads at home unattended is a bad idea, and some of them seem incorrectly uploaded, so don't download them yet, I'll check up on them when I return.
[Treble-Enabled Device Development A/AB ROMS] reynard1:
guys whats avs and bvs mean?
[Treble-Enabled Device Development A/AB ROMS] petre22:
Check this....
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Turns out all of them uploaded nicely - all archs go! If they work as well, we'll be ready for another year to come.
[Treble-Enabled Device Development A/AB ROMS] damprobot:
You should consider the Moto g6 play for a-only, it boots roar and caos a11 which is based on roar just fine.
[Treble-Enabled Device Development A/AB ROMS] damprobot:
Just booted your rom on a-only, works well aside from the ui lag that's apparent on a11 gsis
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Hi OP, will this ROM ever work with vndk28?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Be more exact please? My ZF5 was 64A VNDK28 and that was the test device I booted on.
[Treble-Enabled Device Development A/AB ROMS] Gomeman:
hi , just to confirm that it boots on my Gome fenmmy note c7. (OREO)

Besides that the serial control is enabled and says that it has performance impacted , it also lags , and tones dont work.

Installed opengapps 11 pico test. Probably has more bugssssss.

Going back to 10 , since i need it for a daily use.

Anyway Thanks, keep going.
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Is that booting the Android 11 or 10 GSI? I was under the impressions you can't boot Android 11 over VNDK28 yet.

EDIT: Apparently its only VDNK Lite it won't boot over?

My device is VDNK-lite 28, I can boot Android 10 images fine but I heard I can't boot 11 images.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
if your device need AB roms, so for Android 11 you need take -vndklite build

if your device need A-only, then take regular Android 11 for A-only

i have arm64 AB vndk-28-lite and i using -vndklite builds (or -lite) of Android 11 GSI
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
I have arm64 A only vndk28lite so I guess I'm out of luck! There don't seem to be any lite arm64 a only builds of 11.
[Treble-Enabled Device Development A/AB ROMS] Tims Fong:
https://github.com/phhusson/treble_experimentations/wiki

"Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+."
[Treble-Enabled Device Development A/AB ROMS] eremitein:
you no need vndklite, take regular Android 11 for A-only (read careful my previous message)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I don't know who of you did this, but HALT IMMEDIATELY!

The community is not fanboy ground - the users decide which GSIs they prefer and use, and no one has the rights to forcefully intervene (in this case, by vandalizing other's work). Doing it in MY name, on top of that, is even more unacceptable. And since when did lazy me assemble a "team"?

I've already clarified the matter with [MENTION=2576073]harvey186[/MENTION] on Telegram. Harvey - I'm sorry for any potential loss the rogue had cost you and I hope your site recovers soon!
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Hahah this looks like something a 12 year old made ?. I hope [MENTION=2576073]harvey186[/MENTION] gets things under control!
[Treble-Enabled Device Development A/AB ROMS] harvey186:
I can't understand what benefit it has, to hack my download server?

It's ok, I'm able to recover.
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
Guy's, i hardly can comment this without using strong words ... some individuals have their fun with site-hacking and keeping harvey186 AND AndyYan from improving their work by making them unnecessarily rebuild servers and have discussions that nobody wants.

The world is so broken ... making me speechless.

[MENTION=2576073]harvey186[/MENTION] and [MENTION=4467696]AndyYan[/MENTION] ... keep on rolling, don't let you be influenced by such ... (take your favourite worst name ;) ).

Cheers

Kurt
[Treble-Enabled Device Development A/AB ROMS] Yogart99:
Hi Andy , I like the ROM but I can not install gapps , it says low disk space when trying to flash from twrp . System only has 30 megs available. Is there anyway I can get gapps on it ?

Or can you make a build with gapps?
[Treble-Enabled Device Development A/AB ROMS] nozerorma:
Hey did you try to flash this in a G8 Plus? How did it go?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
you can try LOSQ rom, i added patch for this. on my Xiaomi device with gapps that patch works and wifi speed is not slowing down
[Treble-Enabled Device Development A/AB ROMS] romulocarlos:
No, didn't tried. My phone is under warranty, and as we are facing problems with wifi+bluetooth, I'll not flash, because maybe I need to return my phone.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Some things on my mind right now:

1. New XDA web is bad, and new XDA app (which just takes you to the web) is worse.

2. My day job is consuming me heavily, to the point that I don't even want to visit XDA/TG daily. Dangerous direction, I know. I'll still try to pump out builds though.

3. Google again made a "feature drop" for Android 11 (11.0.0_r19), and it only reminds me of the disastrous last one (10.0.0_r18). I'll wait for this one to be fully tested and merged before making my next move (including new LOS18 builds, script upload and perhaps a new thread).
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
@AndyYan Sorry to bother you when you have heavy day job work.

REQUEST: If possible can you push your git changes to LOS17.1 to github. I recompiled it last week - unfortunately surface flinger crashes. (treble_arm64_bvS)

I need a custom los (for a cubot X19) - just need to tweak battery, and brightness (I reduce config_screenBrightnessSettingMinimum to 1 as default min brightness 10 is lot high for my eyes)

Thanks for the great work.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with December security patches. [Insert obligatory backup-and-test warning here]

LOS 18.1 booted and seems to behave fine locally as well - targeting a weekend release.

@RubenGreg Are you saying that my build works but your personal ones break? But there hasn't been noteworthy changes to Q in a while... Also, what you need sounds like they could be done by a device overlay.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Duplicate
[Treble-Enabled Device Development A/AB ROMS] Mrigendra10:
Glad to hear that. I was waiting for it. Your Los 18 'testing' build worked exceptionally well on my Nokia 8.1 with Q vendor. I found no issue in the daily usage except for the fact that RAM usages were bit high and battery drained a bit faster.
[Treble-Enabled Device Development A/AB ROMS] tj639:
A instalação no teclado m30, não consigo instalar o arquivo img.Xz que o twrp não encontra, como faço para alterar o arquivo para zip?
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
Thanks for pushing updates

Yes, your build for LOS17.1 works but my compiled los 17.1 does not. I will test the new 'push updates' and report back in the next days.

Do you mean I just create overlay; and build; compile; install that apk only? I will try that. Thanks.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Learn how GSIs work. Extract and flash image. And English only.

Push overlay to /system/product/overlay, set correct permissions, reboot. If the overlay is correctly written it should come into effect.
[Treble-Enabled Device Development A/AB ROMS] tj639:
I extracted the image anyway, you can't install it with twrp ...
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
There's an "Install Image" button in "Install".
[Treble-Enabled Device Development A/AB ROMS] tj639:
I forgot to mention I tried it too, I chose the system option if I'm not mistaken and it didn't work was in infinite loop, I waited for 40 minutes and nothing unfortunately !! Can you tell me which option is correct and I also tried it on PC fastboot and nothing ..
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
Thank you for the ideas...

Happy to tell you.. I wrote overlay by copying existing oneplus overlay. Works great.

config.xml

<?xml version="1.0" encoding="utf-8"?>

<resources>

<bool name="config_enabled_lte">true</bool>

<bool name="config_wifi_dual_band_support">true</bool>

<integer name="config_screenBrightnessDark">1</integer>

<integer-array name="config_autoBrightnessLevels">

<item>1</item>

<item>10</item>

<item>50</item>

<item>90</item>

<item>100</item>

<item>150</item>

<item>200</item>

<item>300</item>

<item>400</item>

<item>500</item>

<item>800</item>

<item>1000</item>

<item>1300</item>

<item>2000</item>

<item>3000</item>

<item>4000</item>

<item>8000</item>

<item>20000</item>

<item>30000</item>

</integer-array>

<integer-array name="config_autoBrightnessLcdBacklightValues">

<item>1</item>

<item>3</item>

<item>7</item>

<item>16</item>

<item>25</item>

<item>30</item>

<item>35</item>

<item>44</item>

<item>58</item>

<item>65</item>

<item>75</item>

<item>85</item>

<item>95</item>

<item>104</item>

<item>110</item>

<item>120</item>

<item>125</item>

<item>135</item>

<item>145</item>

<item>255</item>

</integer-array>

<!-- Minimum screen brightness setting allowed by the power manager.

The user is forbidden from setting the brightness below this level. -->

<integer name="config_screenBrightnessSettingMinimum">1</integer>

<!-- Maximum screen brightness allowed by the power manager.

The user is forbidden from setting the brightness above this level. -->

<integer name="config_screenBrightnessSettingMaximum">255</integer>

<!-- Default screen brightness setting.

Must be in the range specified by minimum and maximum. -->

<integer name="config_screenBrightnessSettingDefault">42</integer>

<integer name="def_screen_brightness">42</integer>

<bool name="def_screen_brightness_automatic_mode">true</bool>

</resources>

Cubot/X19/AndroidManifest.xml

<manifest xmlns:android="http://schemas.android.com/apk/res/android"

package="me.phh.treble.overlay.cubot.x19"

android:versionCode="1"

android:versionName="1.0">

<overlay android:targetPackage="android"

android:requiredSystemPropertyName="ro.vendor.build.fingerprint"

android:requiredSystemPropertyValue="+CUBOT/X19_EEA*"

android:priority="11"

android:isStatic="true" />

</manifest>

Android.mk

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_MODULE_TAGS := optional

LOCAL_PACKAGE_NAME := treble-overlay-cubot-x19

LOCAL_MODULE_PATH := $(TARGET_OUT_PRODUCT)/overlay

LOCAL_IS_RUNTIME_RESOURCE_OVERLAY := true

LOCAL_PRIVATE_PLATFORM_APIS := true

include $(BUILD_PACKAGE)
[Treble-Enabled Device Development A/AB ROMS] janhammer504:
Hi,

Please, how do we flash LOS 17 GSI on devices shipped natively with android 10 :

Or how to flash system.img on /super partition ???

On TWRP, it's not possible. In fastboot, this erase vendor partition because it's mapped from /super partition !!!

Edit : i will try in fastbootd

Anyway, Thank You
[Treble-Enabled Device Development A/AB ROMS] methuselah:
then you need to live with the issue. This issue is riddling a lot older and new devices alike. As another user said he added a patch maybe it can work for you. But coming over to xda and asking in custom GSI won't be good for you. If you need to stay on stock its upto you. Probably with another update things will be good for you.
[Treble-Enabled Device Development A/AB ROMS] mohamedfaky:
Hello, first happy new year,

I'm using Infinix hot 9 play X680B that it's SoC is mt6762 and trying to flash Lineage OS 17.1 gsi but facing issues, after flashing it in fastbootd the device soft breaks, it stops at fastboot when reboot.. the device shipped with android 10 and it supports Treble project, system as root, it's arch is arm64.. i'm using this package lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from here , i can't use one with N at the end from github because it seems bigger that no space found in super to resize system partition it gives me this error FAILED (remote: 'Not enough space to resize partition')

can anyone help me?
[Treble-Enabled Device Development A/AB ROMS] romulocarlos:
Thank you for the reply.

Well, I'm living with this, as my only option is return my device to warranty. And I think this will not solve the problem.

And, yes, not only g8 plus is suffering. I saw cases with Redmi Note 8, g8 power and even Nokia 5.3. They use same SoC, which let me believe is maybe a driver problem, because not only all devices with this SoC is suffering. So, maybe a GSI with another driver let me know if this is the real cause. Is why I ask on GSI.

Anyway, can you point me to this patch, please?

Thanks
[Treble-Enabled Device Development A/AB ROMS] methuselah:
Mate its better you sell the device. Go for another SOC. I guess moto g8 plus is not good. No custom ROM development. Afaik patch is known I saw no hope. Get a another good device like second had one plus or brand new one if u can afford. These issues will be thing of past. I also tossed my g8 to my wife. She use it for studying and casual calling.
[Treble-Enabled Device Development A/AB ROMS] svratonzo:
Installed on Huawei Mediapad M5 Lite, it works.

But i cannot installa USB AUDIO PLAYER PRO app, due to USB OTG incompatibility.

Could you help me to solve this issue?
[Treble-Enabled Device Development A/AB ROMS] uristled.ru:
I’m not that much of a online reader to be honest

but your sites really nice, keep it up! I’ll go

ahead and bookmark your website to come back down the road.

Many thanks
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Hi Andy, what's the chances of getting one last build of 17.1 with the latest Lineage sources/Jan 21 security patch?

I understand your efforts have been moved to Android R however Q is the last compatible version for some users.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Hoho, no one said "one last build", not yet... I was just waiting for the merge to happen.
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Oh I see, that's good to hear! Thanks for the info :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with January security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] Vulnerability:
Dirty flashed fine over the previous build, thanks for keeping our devices up to date!
[Treble-Enabled Device Development A/AB ROMS] mbscomplex:
Think I might have a bug with spoof package permission. I get a prompt and then in the checker app it still stays red, but microg checks all the boxes, except device registration keeps dropping. In the spoof package permission screen there's no apps listed. Tried

but still red. I don't know what else to do.

arm64 avS

Besides that it really runs great on my weird 2017 huawei.(y)
[Treble-Enabled Device Development A/AB ROMS] jagritvats6:
Lineage 17.1 works well on Lenovo K8 note though Bluetooth doesn't seem to work at all. Lineage 18.1 works too but no MTP, bluetooth doesn't work in other ROMS like EvolutionX 4.0 too
[Treble-Enabled Device Development A/AB ROMS] tamaraxxx:
Hello,

I also installed the Lineage 17.1. It works well on Elephone U3H though Bluetooth doesn't seem to work at all. it keeps crashing all the time, therefor i can't use the ROM right now as daily driver, because this is my only working phone.

Stock Rom works well with bluetooth, can it be a problem of this ROM?
[Treble-Enabled Device Development A/AB ROMS] jagritvats6:
In my phone Lenovo K8 Note, bluetooth doesn't seem to work with any GSI , I have tried EvolutionX 4.0 , Lineage 17.1 and Havoc OS too
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I've installed on Samsung Galaxy Tab A 8.0 (2019) (SM-T290). Still setting it up, but so far it's working well and seems stable. Thanks for adding phh-su — I can't use Magisk on this tablet because WiFi won't work with it, and an alternative is appreciated.

Many thanks. (y)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with February security patches. [Insert obligatory backup-and-test warning here]
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Thank you a lot for your great work

Just downloaded and installed LOS18.1 on my J530F.

Remarkable fix of the old proximity sensor bug that shuts off the screen while calling.

Calls now are ok.

It seems useless to install Magisk, as system is already rooted.

Did not install whatever gapps,

Minor bugs detected: absent calling ringtone, cannot even be set from the phone app (but vibration works), radio s-meter not following field strength, a pair of random reboots in not well defined situation. I'll stay watching and then will report. Thanks a lot again.
[Treble-Enabled Device Development A/AB ROMS] :
Have you tried to resize system in twrp? Random reboots should disappear
[Treble-Enabled Device Development A/AB ROMS] Alvin50:
Thank you for your suggestion.

Presently I'm with Orangefox recovery, though I could well come back to TWRP.

Which way should I resize my system? can you please address me to some existing post?

Now my installation is already 15 hours old, and I have experienced nearly ten auto reboots, but have identified that some of them come from rotation sensor. If I try to rotate the phone while I'm browsing, I have a partial reset, in the sense I see the initial LOS logo and am thrown out of my navigation to the phone main screen.

A true cold reset happens if I try to change settings in some app, e.g. the call ring tone, that stays anyway unresponsible.

A cold reset might also have happened while inadvertendly swiping over the proximity sensor with the phone lying on the table and no calls active.
[Treble-Enabled Device Development A/AB ROMS] :
In twrp (but it's the same in orange fox): mount system, then go to wipe menu, advanced wipe. Now select system and at the bottom of the screen you have repair/resize (or something similar). Click to resize and then reboot. In 99% of cases the problem goes away (sometimes some magisk modules can cause the same problem).