DEVICE_INTEGRITY not passing with gmscompat

[silvzr]

Devices running gmscompat (Google Services as user apps instead of system ones) can't pass device integrity but only basic one. Maybe gmscompat gives as a CTS result an old fingerprint which never worked? If so I was never able to find it @osm0sis (since your fork can bypass hardware attestation but doesn't work either)

[osm0sis]

Is gmscompat from microG or what? Is it an APK or what? You can use my fork and try to remove/hide anything conflicting with my custom.app_replace.list feature.

[silvzr]

Is gmscompat from microG or what? Is it an APK or what? You can use my fork and try to remove/hide anything conflicting with my custom.app_replace.list feature.

gmscompat is built-in into a lineageos fork (actually discontinued), so it's literally the same as the grapheneos one. Fact is that I don't know if there is any overlay or system app conflicting with it, I checked all directories mentioned in your template but didn't find anything related to it

[osm0sis]

Unfortunately probably not much to be done then, unless you can find the source and there's a prop to be set that can disable it or something.

[silvzr]

Unfortunately probably not much to be done then, unless you can find the source and there's a prop to be set that can disable it or something.

I have the ROM source but I wouldn't know where to look into. My first doubt was if someone with gmscompat (so probably on grapheneos) was ever able to pass CTS and device integrity through rooting cause it's known that it doesn't pass it by default, but since MicroG can pass it I don't see how it wouldn't be possible for gmscompat