Latest lineage 18.1 updates as of 2022.08.10 apply cleanly for a "user" build and a locked bootloader.
Wth microg, It is possible to pass all safety net checks with
- a patch to set ro.boot.verifiedbootstate=green (I did not try leaving this set at yellow),
- a patch to set the build finger print to "motorola/kiev_retailu/kiev:11/RZKS31.Q3-45-16-8-3/018f4:user/release-keys" Note this string is from `fastboot getvar all` and is one character different than the current lineageos 18.1 default.
- a patch to set the PLATFORM_SECURITY_PATCH to "2022-05-01"
In my case, the bootloader is locked and it is a user build so there is no need to reset those variables.
It may be possible to use magisk to accomplish the same thing with an unlocked bootloader and userdebug build. I no longer use magisk and I have not attempted this.
I did try ih8sn; however, this did not work with a "user" build as ih8sn seems to depend on the su binary being present from a userdebug build. For compiling your own "unofficial" builds, I suspect ih8sn would work for a userdebug build, an unlocked bootloader, and the appropriate variables set via ih8sn. I have not verfied that this works.
Using microg, I can include the android auto stub app plus the required permissions (described
here). This builds without error, Android auto seems to run fine, but my limited testing (using a rental vehicle - I don't own a vehicle that supports android auto) did not succeed. I was not using my vendor supplied device usb cable for this test. Based on testing with an iphone and a non standard apple usb cable (which also did not work until the offical apple cable was used), it's possible the failure is due to the cable. Android auto seemed to recognize it had been connected to the vehicle, but the vehicle (a recent honda) refused to connect. I tried both using the "gapp" stub app and the full google app, google maps was installed and functioning.
Since I don't need micro g, safety net, or android auto, the above testing with microg was "just for fun."