Shared publicly  - 
 
The Omate TrueSmart claims it "ships with Google Play Apps Store", however the screen size is 240 x 240 pixels. Assuming ldpi (the lowest density android supports) that gives a size of  320dp x 320 dp.

Android docs state that a small screen device must be at least 426dp x 320dp . http://developer.android.com/guide/practices/screens_support.html

How will the TrueSmart past the CTS if it does not fit into any screen size bucket?

+Omate TrueSmart 
14
3
Louis-Claude GOMEZ's profile photoHouston Hensel's profile photoSteve Albright's profile photoChris Lacy's profile photo
14 comments
 
Interesting to find out why, as it is it's shipping with Google Play App store, and most of the apps we tested from the app store are working as is
 
+Lokifish Marz MotoACTV and Wimm one didn't ship with the play store, thus shouldn't have had to go through CTS. If they got in anyway, it was "hacked" and doesn't mimic the situation with the Omate.
+Kevin Barry it could be something that's not tested in CTS yet. Once or twice a year I stumble along something like that.
 
+Lokifish Marz It "works" but it doesn't ship with it. I can go put the Play Store on a rasberry pi device with no screen, doesn't mean it's supported.
 
+Mike DiGiovanni  Fair enough but +Omate TrueSmart  would be in some serious legal trouble if they shipped with Play Store installed as it's a proprietary software application by Google. So either Omate is either begging for legal trouble or have the go ahead from Google. ROM developers have run into the same issue.
 
This is not a compatible screen.  The official compatibility specification can always be found at: https://source.android.com/compatibility/index.html

In particular, section 7.1.1 of the CDD says: Devices MUST have screen sizes of at least 426 dp x 320 dp ('small')

Supporting smaller screen sizes would involve the same thing we did when introducing small -- creating a new screen size bucket, which existing apps would not support, starting out with an empty store until apps are updated to support it.  (And note that I am not saying that any such work is going on or planned.)
 
The way I see it this could mean a few different things.

1) Google is adding support for "xsmall" style devices. This is the most exciting possibility as it means we're going to see more xsmall devices with the Play Store in the future. Perhaps a Nexus watch or perhaps Glass would fall into this category (it might already qualify for "small" depending on what DPI it is considered by Android). It also means that in order for any existing app on the Play Store to be installed onto the TrueSmart the app will have to be updated to explicitly state support for it. I would suspect a new Android version would be required for this but the TrueSmart says it will ship with 4.2.2.

2) The TrueSmart will not ship with the Play Store despite it's claims.

3) The TrueSmart will ship with a pirated version of the Play Store. This has happened with a few cheap tablets before. It's possible Google would take technical or legal action against Omate if this happened. This is unfortunate for app developers as we will get bad reviews for our apps not working properly even though the device is not Android compatible.

4) The TrueSmart ships with the Play Store as a certified device even though it should not be compatible. This would likely mean Google made a mistake during testing, but could also be due to some kind of exception like what was made for the original Galaxy Tab. This seems unlikely and would be unfortunate for app developers for the same reasons as (3).


+Omate TrueSmart Do you have a license to distribute the Play Store on your devices? Will existing apps on the Play Store be installable on the TrueSmart on day one or will the apps need to be updated to state they have support?
 
+Niklas Claesson  There's already four other Android based smart watches in production or already released that I know of.
 
It could have a million DPI, that doesn't make the screen larger than a small screen.
Add a comment...