I would like to point out that the policy of certifying specific phones as daydream-ready (and only allowing daydream apps to start on these phones) created the following situation that is really user unfriendly:
The ZTE axon 7 was certified as daydream-ready on release (with android N installed), which is the reason we bought it as a developement / testing device.
But the recent update to android O removed Daydream support, while the hardware (and most extensions to my research ) are obviously still the same.
The simplest solution probably would be the following: Since the 'Daydream developer options' are already there, what about adding an option to 'override' the check if the device is certified - this would make it much easier for us developers to write and test applications without breaking the integrity for normal users.
sewasewa777
commented
5 years ago
Hello,
I would like to point out that the policy of certifying specific phones as daydream-ready (and only allowing daydream apps to start on these phones) created the following situation that is really user unfriendly:
The ZTE axon 7 was certified as daydream-ready on release (with android N installed), which is the reason we bought it as a developement / testing device.
But the recent update to android O removed Daydream support, while the hardware (and most extensions to my research ) are obviously still the same.
The simplest solution probably would be the following: Since the 'Daydream developer options' are already there, what about adding an option to 'override' the check if the device is certified - this would make it much easier for us developers to write and test applications without breaking the integrity for normal users.