3 ms·
> When asked for comment, Google told us that the feature had only ever been released by accident — that it was experimental, and that it could break some of th
by ChrisAntaki 13y ago
> When asked for comment, Google told us that the feature had only ever been released by accident — that it was experimental, and that it could break some of the apps policed by it.
Oh, it would definitely break some apps. Considering it would introduce new uncertainty. It's still an amazing feature.
- raverbashing 13y agoYeah, because checking return codes and error values is overrated Thanks Google, for making my phone less secure.
- signalnow 13y agoIt was never official, it was never announced nor documented.
- josteink 13y agoYeah, because checking return codes and error values is overrated Even Google's own non-AOSP camera is guilty of this too. The API docs says an app should check for camera capabilities before using them. Still the PhotoSphere feature in Google's non-AOSP camera attempts to set Flash-settings on devices with no flash-capability. To overcome the issue you have to rewrite the camera-interface code to ignore API calls to SetFlash, SetLightmode etc when not supported, instead of throwing as you should be doing according to the docs. So yeah. Even Google is guilty of this one.
- The_Double 13y agoGoogle is one of the worse offenders when it comes to not following android guidelines. Their apps consistently break back button behavior, don't follow UI guidelines, etc.
- hahainternet 13y agoBy allowing you to install software they make your phone less secure. Better buy a feature phone ASAP!
- jevinskie 13y agoI can't believe they question Google's authenticity when they say it was accidentally released too soon and then go on to criticize the feature for being unpolished and incomplete!