[OFFICIAL] AOSP R Mod //CAOS11

[chaseadam]

...on PH-1 (mata) this build starts with SELinux permissive, which after Magisk becomes disabled(!). For comparison, other PHH based ROMs start with enforcing...

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?

 

[MarSOnEarth]

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?

Instead of a 'boot script' this, but if you can compile, than set 'BOARD_KERNEL_CMDLINE += androidboot.selinux=enforcing'

 

[chaseadam]

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.

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

 

[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.

 

[eremitein]

Fingerprint not working after reboot on nokia 6.1 (PL2) XD.
... the fingerprint issues is related to rom and i'm waiting for a fix

first check fingerprint in AOSP v313 - no need to wait if same issue because CAOS generally based on AOSP code

 

[eremitein]

CAOS v315 2022.01.21
download /// changelog

 

[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?

 

[eremitein]

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?

why not a stock vendor? try with stock one

 

[selo28]

why not a stock vendor? try with stock one

This vendor , vendor can it be used without installing?

 

[cuzimthatnerd86]

Guess this should read "the same as on AOSP Roar"

IT SHOULD read with an actual statement. If you're going to release buggy shi*, THEN HAVE SOME ACCOUNTABILITY

 

[eremitein]

IT SHOULD read with an actual statement. If you're going to release buggy shi*, THEN HAVE SOME ACCOUNTABILITY

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

 

[elocnix]

Hi all!
Thank you for this @eremitein, it really saved me a lot of nerves.
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!

 

[rw_on_xda]

That's it for now. Over and out!

Roger @elocnix !
over 'n out !

 

[Macusercom]

IT SHOULD read with an actual statement. If you're going to release buggy shi*, THEN HAVE SOME ACCOUNTABILITY

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

 

[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...

 

[eremitein]

CAOS v315+ 2022.02.28
download /// changelog

 

[DzbanCban]

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.

 

[eremitein]

apps crash when they ask for a permission (for example access to the dialer) when you give or not give it those permissions

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*

 

[DzbanCban]

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*

Aight, thanks for an answer!

 

[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.

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!