Thanks, alsutton. I'd say this isn't a terribly important requirement since there is a workaround to get the desired information through a try/ catch block (just need to determine a good candidate ODK-unique method to call which won't be likely to …
Considering you referred to the ODK developers as "they", I think I'll leave this question open, since this is just your opinion and not an answer to my question. I'll post my own hackish solution when I get it working, in case you are correct and …
I don't see any evidence such an expectation. The ODK is a thin layer on top of Android which to me implies the creators designed it with compartmentalization in mind. If not, why wouldn't they have simply modified the Android SDK, rather than iso…
You don't need separate APKs - just run things in different pipelines. For my app, the goal of maintaining backward compatibility to Donut while targeting and taking advantage of the latest features when available, and supporting unique devices and…
It's not just other device running OUYA framework that this would be used for (although I disagree that is not useful information in itself). There is also the situation where the OUYA device itself is running a custom ROM (cyanogen for example). …
My question has nothing to do with overscan or the advantages/ disadvantages of maintaining separate branches. I'm asking a specific question of how to detect the OUYA framework, not just the OUYA device.
Reading proc/cpuinfo (native equivalent of…
