yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] luka_bubi:
Hi! I am having problems with last several versions of this ROM on Huawei p20 lite device. At first everything is working OK. After restart the mobile connection becomes unstable. That does not apply only to mobile data, but on calls and SMS also. The phone became practically unreachable. The reboot sometimes fixes the problem, sometimes not. Even in cases when another reboot fixes the problem, the unstable connection became an issue again after some time. I have tried limiting connection to 2G, 3G 4G modes as well as mixed mode (4G/3G/2G). I am using only CAOS11 ROM installed on top of stock ROM, with TWRP and NFC patches installed.

After using LiR I did not notice this issue, but I only used it for a couple of weeks (not sure if I did any restarts during that time), than switched back to CAOS11. And in a couple of hours I got this stupid issue again. Now I am back on stock ROM and hoping to receive a reply about what is this bug that I am getting and how to get around it.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
i had no issues with CAOS v312 and v313, and i have no same device - sorry, i can't help you

you need ask in my support TG chat and also in the XDA P20 lite threads

PS: i can help with one idea - check prop value with command "getprop ro.kernel.android.checkjni" should be none or 0
[Treble-Enabled Device Development A/AB ROMS] eremitein:
CAOS v313+ 2021.10.10

download /// changelog
[Treble-Enabled Device Development A/AB ROMS] DAE1964:
Just wanted to say thanks for your work.

Running latest build on my Essential PH-1 as my backup device.

Runs very smooth.

Cheers
[Treble-Enabled Device Development A/AB ROMS] luka_bubi:
I tried with stock EMUI9.1 and LiR v313 and I do not have the prop. value in those. I can not test on CAOS11, as I only have one phone and use it as daily driver so I can not afford not to have a connection.

The strange thing is that I had this problem with connection being unstable on last LiR v313 once. It happened while doing a reboot. The phone rebooted surprisingly quickly (the OS loaded way quicker than normally) and could not get the connection. After another reboot the loading times were back to normal and mobile connection was working fine.

I will try to ask on your TG group. In XDA P20lite group none had this problem, either with CAOS11 or any other rom. Perhaps they switch roms too fast for this error to appear :)
[Treble-Enabled Device Development A/AB ROMS] nizardho:
Could you please show me how to install the rom?

I have redmi go which I assume belong to arm a-only if I am not wrong.

I install rom (caos-v313+211010-arm-avZ.img.xz) via twrp 3.3.1 and selected image install to system image then succed but when I reboot system it said no os and phone just reboot itself and back to twrp.
[Treble-Enabled Device Development A/AB ROMS] nevermind23:
The rom itself is really really good, I liked it very much, literally everything is perfect for me. I have faced 2 issues, not sure if they are because of rom or I made something wrong.

1. Safetynet CTS profile fails, tried uninstalling magisk, still same, installed magisk again, tried magisk hide, riru + universal safetynet fix + magiskhide props config modules, vut still same. GSI description says to enable Safetynet option, how or where can I do that ?

2. TWRP terminal outputs

failed to mount /system_root structure needs cleaning​

I think it was like that even before installing magisk, tried changing system filesystem to EXT4, wiped all the data, it got fixed, then installed GSI along with magisk and it outputs same message again.

Any help would be appreciated

P.S. I have Galaxy S9
[Treble-Enabled Device Development A/AB ROMS] eremitein:
1. no need any magisk modules, remove them

guide in the OP: a. just enable SafetyNet option (recommended) b. disable SafetyNet and enable "Spoof Pixel 5" then reboot c. enable both options and reboot

all options in the Phh settings > Misc

and need v313 or v313+ build

2. try TWRP > Wipe > Advanced > System > Repair and then Resize
[Treble-Enabled Device Development A/AB ROMS] nevermind23:
Thanks, got safety net issue fixed thanks to that, but carier was not working so I decided to move on nobles rom.. l. unfortunately.

Anyways, nice GSI and very good work. Good luck
[Treble-Enabled Device Development A/AB ROMS] B83C:
[ 577.586470] [2021:11:14 18:54:42]init: property_set("ro.boottime.adbd", "577585513423") failed: property already set
[ 577.587591] [2021:11:14 18:54:42]init: Created socket '/dev/socket/adbd', mode 660, user 1000, group 1000
[ 577.587981] [2021:11:14 18:54:42]init: cannot execve('/sbin/adbd'): Permission denied
[ 577.592281] [2021:11:14 18:54:42]init: Service 'adbd' (pid 4933) exited with status 127
[ 577.592304] [2021:11:14 18:54:42]init: Sending signal 9 to service 'adbd' (pid 4933) process group...
[ 577.592434] [2021:11:14 18:54:42]init: kill(4933, 9) failed: No such process
[ 577.841011] [2021:11:14 18:54:42]SMBCHG: get_prop_batt_status: CHGR_STS = 0x05
[ 578.270416] [2021:11:14 18:54:42]FG: fg_is_batt_id_valid: fg batt sts 0xc
[ 582.585627] [2021:11:14 18:54:47]init: starting service 'adbd'...
[ 582.587308] [2021:11:14 18:54:47]init: property_set("ro.boottime.adbd", "582586353942") failed: property already set
[ 582.588400] [2021:11:14 18:54:47]init: Created socket '/dev/socket/adbd', mode 660, user 1000, group 1000
[ 582.588795] [2021:11:14 18:54:47]init: cannot execve('/sbin/adbd'): Permission denied
[ 582.593048] [2021:11:14 18:54:47]init: Service 'adbd' (pid 4935) exited with status 127
[ 582.593070] [2021:11:14 18:54:47]init: Sending signal 9 to service 'adbd' (pid 4935) process group...
[ 582.593193] [2021:11:14 18:54:47]init: kill(4935, 9) failed: No such process
[ 583.280906] [2021:11:14 18:54:47]FG: fg_is_batt_id_valid: fg batt sts 0xc
[ 587.586469] [2021:11:14 18:54:52]init: starting service 'adbd'...
[ 587.588142] [2021:11:14 18:54:52]init: property_set("ro.boottime.adbd", "587587188940") failed: property already set
[ 587.589246] [2021:11:14 18:54:52]init: Created socket '/dev/socket/adbd', mode 660, user 1000, group 1000
[ 587.589640] [2021:11:14 18:54:52]init: cannot execve('/sbin/adbd'): Permission denied
[ 587.593884] [2021:11:14 18:54:52]init: Service 'adbd' (pid 4936) exited with status 127
[ 587.593906] [2021:11:14 18:54:52]init: Sending signal 9 to service 'adbd' (pid 4936) process group...
[ 587.594030] [2021:11:14 18:54:52]init: kill(4936, 9) failed: No such process
[ 588.290333] [2021:11:14 18:54:52]FG: fg_is_batt_id_valid: fg batt sts 0xc
[ 588.311873] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.311895] [2021:11:14 18:54:52]nl80211_dump_scan exit
[ 588.311948] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.311957] [2021:11:14 18:54:52]nl80211_dump_scan exit
[ 588.312457] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.312471] [2021:11:14 18:54:52]nl80211_dump_scan exit
[ 588.312495] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.312503] [2021:11:14 18:54:52]nl80211_dump_scan exit
[ 588.315052] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.315080] [2021:11:14 18:54:52]nl80211_dump_scan exit
[ 588.315128] [2021:11:14 18:54:52]nl80211_dump_scan enter
[ 588.315137] [2021:11:14 18:54:52]nl80211_dump_scan exit

How do I fix this? It (init process) is eating up my cpu....

(These messages keep flooding my dmesg non-stop)
[Treble-Enabled Device Development A/AB ROMS] chaseadam:
Cheers on an excellent build, working smoothly on a PH-1.

I see mentioned that the build supports Enforcing SELinux mode. I have set it manually via `adb shell` but it does not survive boot. Is there a recommended method to survive reboot?
[Treble-Enabled Device Development A/AB ROMS] chaseadam:
My guess is the dm-verity disable required on the PH-1 will keep security checks "red".

Seems there is some method to leaving dm-verity on (see ASOP.zip in https://xdaforums.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/#post-85554137), but as mentioned there, the image may be specifically built for the storage format (which generic GSI images do not have):

Unfortunately, this device requires specific storage mapping in the kernel so that it might not be able to use LineageOS as the baseline image.

In order to overcome this inconvenience, you must build a stock AOSP image and disable verity. It is somehow complicated for newbies. Therefore, I am here to make it easier for you.
[Treble-Enabled Device Development A/AB ROMS] MarSOnEarth:
Since then, after trying many GSI ROMs, I've switched to OctaviOS [detailed instructions] A couple of glitches here and there but overall trouble free in daily use, and it passes SN w/ MagiskHide. One curious thing; although the OP provided boot.img can be used for rooting, Magisk would show "Ramdisk No". Switching to .32 OEM boot.img results in "Ramdisk Yes". Either way there seems to be no difference in how the phone operates that I could observe.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
CAOS v314 2021.12.27

download /// changelog
[Treble-Enabled Device Development A/AB ROMS] warchild98:
I'm using this rom on my old Nokia 6.1 2018 and so far so good this is the best rom!

I also got lucky because i'm able to pass safety net with magisk.

The performance and ram usage shocked me as well since i'm coming from lineageos where the performance was good (but was stuttery in some apps/games since almost all ram was taken for some reason). In this rom this doesn't happen and it's appreciated very much.

But i do run into some issues like:

1. a2dp bluetooth playback is not working for me (not really a problem since i use my wired headphones most of the time anyways, but i would like to have a2dp working as well).

2. can't transfer multiple files using bluetooth (only photos and audio files). Files like .apk just fail to send for some reason (it worked on stock and other roms).

3. NFC Beam isn't available (it worked on stock and some other roms).

I haven't tested anything else yet since i use this phone as an "iPod" only.
[Treble-Enabled Device Development A/AB ROMS] yatsura2k:
Fantastic - thank you for continuing to support CAOS R.
[Treble-Enabled Device Development A/AB ROMS] MarSOnEarth:
I know this will come as a disappointment, but on PH-1 (mata) this build starts with SELinux permissive, which after Magisk becomes disabled(!). For comparison, other PHH based ROMs start with enforcing, and after Magisk become permissive. Same everything else. The only change is system.img. With that though, when set to Pixel 5, the ROM passes SafetyNet. Odd.
[Treble-Enabled Device Development A/AB ROMS] chaseadam:
From my research it is part of the kernel cmdline now, but not sure where that is set. I am willing to re-compile.

I would prefer a recommended non-Magisk method to setenforce survive reboots. It appears most solutions just execute setenforce during the boot process, but use frameworks like Magisk to manage it. What is the recommeded way to add a "boot script" in Android 11?
[Treble-Enabled Device Development A/AB ROMS] MarSOnEarth:
Instead of a 'boot script' this, but if you can compile, than set 'BOARD_KERNEL_CMDLINE += androidboot.selinux=enforcing'
[Treble-Enabled Device Development A/AB ROMS] chaseadam:
Thanks for the pointers MarSOnEarth! I now have "enforcing".

Seems that selinux status is set by the boot.img (which I presume you are getting from nguyenquangduc2000's AOSP 11 download). That has the cmdline set to `permissive`. You can modify the cmdline with `abootimg` by extracting bootimg.cfg and then updating boot.img with the modification.

➜ AOSP11 abootimg -x boot.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
➜ AOSP11 ls
boot.img bootimg.cfg initrd.img system.img vendor.img zImage
➜ AOSP11 cat bootimg.cfg
...
cmdline = quiet androidboot.hardware=mata user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 loop.max_part=7 androidboot.selinux=permissive firmware_class.path=/vendor/firmware_mnt/image buildvariant=userdebug veritykeyid=id:7e4333f9bba00adfe0ede979e28ed1920492b40f
➜ AOSP11 vi bootimg.cfg
➜ AOSP11 abootimg -u boot.img -f bootimg.cfg
➜ AOSP11 adb reboot bootloader
➜ AOSP11 sudo fastboot flash boot_a boot.img
Sending 'boot_a' (25057 KB) OKAY [ 0.839s]
Writing 'boot_a' OKAY [ 0.765s]
Finished. Total time: 1.628s
➜ AOSP11 sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.050s
[Treble-Enabled Device Development A/AB ROMS] warchild98:
Fingerprint not working after reboot on nokia 6.1 (PL2) XD.

Btw, wifi did not reconnect automatically..so i flashed enigma kernel and now it's working just fine (but the fingerprint issues is related to rom and i'm waiting for a fix).

Bluetooth wasn't working either..so i disabled AD2P offload and now it's all good.

That's it for now i guess.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
first check fingerprint in AOSP v313 - no need to wait if same issue because CAOS generally based on AOSP code
[Treble-Enabled Device Development A/AB ROMS] eremitein:
CAOS v315 2022.01.21

download /// changelog
[Treble-Enabled Device Development A/AB ROMS] selo28:
Smsung a8 plus sma730f için This i am using vendor but i am having some problems.

Hang up.mobile data etc. Could the problem be with the vendor?

How can I use gsi versions on this device without any problems?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
why not a stock vendor? try with stock one
[Treble-Enabled Device Development A/AB ROMS] selo28:
This vendor , vendor can it be used without installing?
[Treble-Enabled Device Development A/AB ROMS] cuzimthatnerd86:
IT SHOULD read with an actual statement. If you're going to release buggy shi*, THEN HAVE SOME ACCOUNTABILITY
[Treble-Enabled Device Development A/AB ROMS] eremitein:
who are you to judge developers?.. well, if i did release a buggy shi* - give me the logs of issues which you have in my gsi but haven't in aosp. and even after that I don't owe you anything, read opening topic and disclaimer about void warranty and your personal ACCOUNTABILITY
[Treble-Enabled Device Development A/AB ROMS] elocnix:
Hi all!

Thank you for this @eremitein, it really saved me a lot of nerves. (y)

So, here it goes.

Nokia 3.2 DS

(codename: deadpool_sprout; arm64, ww00 version, latest December 2021 OTA)

Flashed caos-v314-211227-arm64-bvZ-lite last week and it's great!

Few glitches as expected, but overall it's flawless.

There were minor sound issues but after I enabled Use alternate audio policy

(Phh Treble/Qualcomm features) they were gone.

Bluetooth worked out of the box, but only for data transfer.

Sound was a no-go (speakers, headphones) but thanks to @warchild98's post

I also did Force-disable A2DP offload and now it's doing good.

That's it for now. Over and out!

🍻
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
Roger @elocnix !

over 'n out !

;)
[Treble-Enabled Device Development A/AB ROMS] Macusercom:
Please step it down a notch. You can of course state your opinion and say that it is buggy, unusable etc. but there is no need for cursing. No developer has intentions of releasing buggy software and users here are just trying to help.

XDA is a platform for everyone with projects like this allowing for users to compile it themselves and change things if they are unsatisfied. If you're like I am and never having compiled a ROM or kernel before, you and I are in the same boat: at the grace of the energy and time provided by developers 😉
[Treble-Enabled Device Development A/AB ROMS] whitetigerdk:
Love this ROM as my daily driver on P20 Lite.. Any plans on CAOS 12 S ? Seen (and tried) a few other S GSI's on my Huawei phone - and they seem to be working quite nice.. Would rather go with a CAOS 12 S instead though...
[Treble-Enabled Device Development A/AB ROMS] eremitein:
CAOS v315+ 2022.02.28

download /// changelog
[Treble-Enabled Device Development A/AB ROMS] mystifuzz:
I have installed this GSI on my SM-T500 and I can tell that it feels more responsive than the LOS 19 GSI. 👀

microG and Magisk seem to work properly!

I have ran into this one issue though, apps crash when they ask for a permission (for example access to the dialer) when you give or not give it those permissions. Permissions do get applied though.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
this is a normal behavior because used patch for fixing storage issue on the old vendors

just re-open app after giving permission, that's all *not_a_bug*
[Treble-Enabled Device Development A/AB ROMS] mystifuzz:
Aight, thanks for an answer!
[Treble-Enabled Device Development A/AB ROMS] elocnix:
Thanx for a new release @eremitein!

Dirty flash (same version though v314>>v315-arm64-bvZ-lite)

on Nokia 3.2 and 'fastboot erase cache' just in case.

So far, so good. (y)

I noticed one small change in Phh Treble Settings/Misc features/Disable HW overlays is checked by default.

Not sure should I leave it like that, because it 'Eats more CPU and battery'. :)

Cheers!
[Treble-Enabled Device Development A/AB ROMS] nguadien:
On REDMI NOTE 10 5G/POCO M3 PRO 5G it has a very limited brightness range - Too low at max (=40% stock rom brightness) - Too bright at min (=20% stock rom brightness).

I searched around for a fix to lower my min brightness and gain more max brightness without results.

How can I fix this, guys?

*Note: I already tried "Use linear screen brightness slider" and "Force alternative backlight scale" in Phh Treble Settings but they didn't affect min and max brightness at all.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
CAOS v316 2022.03.21

download /// changelog
[Treble-Enabled Device Development A/AB ROMS] eremitein:
for minimal brightness try option "Allow setting brightness to the lower"

but the best way is a creating treble overlay for your device, see manual and samples
[Treble-Enabled Device Development A/AB ROMS] nguadien:
Sorry for bothering you, call volume is barely hear-able, thus I sold Xiaomi devices and bought ROG Phone 2. Before selling I locked the phone and returned it to stock. All in all Redmi Note 10 5G is a very bad device for GSI roms.
[Treble-Enabled Device Development A/AB ROMS] pigeon35:
Hi Eremitein , just wanted to say thank you so much for CAOS Android 11.

No problems, just a thank you :)

I'm using a 2020 UMIDIGI Power 3 and the OEM only released 6 months of updates. So I tried custom ROMS and am so happy to use yours.

Started with v314 on a fresh install over a OEM fresh install + factory reset + wipe.

Today did a dirty flash to upgrade from v314 to v316, working well! Relieved to have those security patches.

Not only great ROMs, but another of your posts helping a different user advised how to get phone jack working with Android 11, which also worked for me.

"Misc > Use alternate way to detect headphone jack

Misc > Disable audio effects

Reboot"

Is it possible to buy you a beer / coffee / server bandwidth as a thank you?

In a previous post there was "If you want to help, you can send donations to https://www.paypal.com/paypalme/electrikjesus". Is that still the best option?

Thanks again!
[Treble-Enabled Device Development A/AB ROMS] eremitein:
thanks for your feedback))

i have no donation links, i guess if you want you can send donation to @phhusson https://github.com/sponsors/phhusson/
[Treble-Enabled Device Development A/AB ROMS] iqbaldalban:
how can i remove the gap on the home screen like in the photo, I tried to move the app to the gap but it didn't work
[Treble-Enabled Device Development A/AB ROMS] eremitein:
try to change grid size in the Styles & wallpaper or change DPI Display size
[Treble-Enabled Device Development A/AB ROMS] Frost_I7:
Hi there.

Thanks for that mod release.

I've been looking for something stable for my Honor 7C (AUM-L41) for over a week... Everything seems to works fine on my end with 2022.03.21 build.

A few little questions:

1. Is there an easy way to make the notification LED use all of its colors (for now there's only red)?

2. Previously (on AOSP) offline charging worked by simply adding the 720x1440 folder from the original system and adding (typepermissive charger) to plat_sepolicy.cli, but now it doesn't seem to work that way. (Maybe that was just a coincidence before, and there was actually more to that.)
[Treble-Enabled Device Development A/AB ROMS] eremitein:
hello

1. maybe this possible in another GSI, mainly LineageOS based. maybe need to check logs and find a way to change some kernel nodes to the write access - i can't help with it

2. which build version you flashed? in the v316 there is already added typepermissive charger, just need to copy folder and check permissions for files (in the previous builds typepermissive charger combined with another offline charger hack)
[Treble-Enabled Device Development A/AB ROMS] Frost_I7:
1. Alright, thanks for the info on that. Still, it's not a big issue, so I may or may not look into it later.

2. At first, I flashed v315 (2022.02.28) after unsuccessfully trying to flash v316 (my mistake, I flashed it on top of another GSI). While writing this - I tried to do the same on v316 (Screenshots with permissions are attached), but it still just blinks for few times and then goes into recovery. Well, again, it's not that big of an issue for me.

And also: What happened to the mixer_paths? Is there some different system for that now?
[Treble-Enabled Device Development A/AB ROMS] garconblair:
Thanks for this great ROM. I have installed arm64-bgZ version on Lenovo Tab M10 FHD Plus tb-x606x, and so far everything is working as expected, very smooth. I installed Magisk.apk 24.3 and when I opened it I had a message : Requires additional setup for Magisk to work properly. Do you want to proceed and reboot?, I put Yes, but after that I couldn’t boot into system. I flashed the ROM again, and installed magisk apk, without that additional setup, and it’s working well as a root manager. But I have that message each time when I open magisk. Do I need to patch boot image and flash in fastboot to get rid of it ?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
it's a part of vendor so depends on the specific device

yes, try that. but if your device comes with dynamic partition and you did delete "product" partition before then you need restore it with minimal possible size, otherwise you will get bootloop again (see thread https://xdaforums.com/t/tutorial-ma...with-dynamic-partition.4311045/#post-85390677)
[Treble-Enabled Device Development A/AB ROMS] NisseGurra:
Just installed the latest Caos 11 on my Lenovo Legion Y700 tablet. Runs extremely well. Only missing auto brightness and wake by cover lid. Everything else functional.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
for cover lid fix i have no idea, for auto brightness need to create device specific overlay from stock system resources, see https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay?
[Treble-Enabled Device Development A/AB ROMS] richbumx:
I am trying to install this on a Legion Y700 tablet like NisseGurra above, after flashing on fastboot i'm just stuck in a boot loop. installation seemed ok. not sure where to go from here
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
Running a Samsung SM-T510, but a shot in the dark:

Did format data *before* flashing CaOS ?
[Treble-Enabled Device Development A/AB ROMS] richbumx:
NisseGura helped me fix the issue. As per his instructions:

"fastboot flash vbmeta vbmeta.img

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot reboot recovery

Make an factory reset"

this did the trick for me. Everything pretty much works on my Legion Y-700. if you don't install a custom rom, the Chinese market only Legion Y700 doesn't get notifications. using a GSI fixed that right up