About GinKage

GinKage

It's not just about a check in VR services: there's also a check in System Server that starts the VR service if "vr_high_performance" is reported (see AOSP): https://github.com/aosp-mirror/platform_frameworks_base/blob/master/services/java/com/android/server/SystemServer.java#L946 That's kind of important for the Sustained Performance mode Daydream depends on. There might be other differences, but the bottom line is: unless the handset reports these flags, Daydream won't fully work.

GinKage

I absolutely agree here: the "code" you're referring to is not Google code, it's hardware capability flags that the handset is reporting to the operating system, and it is device-specific. It is indeed in Samsung's full control, and doesn't require any AOSP modification.

GinKage · ‎01-02-2020

Just like that, without any notice or warning, Daydream no longer works on my S9+. The same applies to S9 and Note 9, which used to be perfectly compatible with Daydream, but now all you get is this: Note that the scene behind this dialog window is actually perfectly rendered, and the phone itself is using the "low motion-blur" screen mode. The problem is, in Android 8 and Android 9, these phones have defined a system flag "android.hardware.vr.high_performance", which is no longer defined on Android 10. This is a Samsung-specific problem, as Pixel phones running Android 10 can still use Daydream perfectly (as reported in this Reddit thread). Hopefully Samsung will be able to get around to fix this problem in a future system update, as it only requires them to add a single xml file to the system image...

Re: Android 10 update kills Daydream compatibility

Re: Android 10 update kills Daydream compatibility

Android 10 update kills Daydream compatibility