Omate TrueSmart

Omate TrueSmart emerged during the first major wave of crowdfunding for smartwatches. At the time, many wearable products were designed as secondary displays for smartphones: they showed notifications, controlled music or surfaced limited information while relying on a paired handset for connectivity. Omate pursued a more ambitious model. The TrueSmart was designed to contain the principal components of a small Android phone, including a cellular modem, SIM slot, GPS and application platform, in a watch form factor. Omate presented the product as a “smartwatch 2.0” and a telecom wearable. The product concept emphasized practical independence. A wearer could use the watch for voice calls, messaging, navigation and Android applications without carrying a smartphone. This positioning made cellular connectivity the principal differentiator rather than an optional feature. The device also included a camera, wireless networking, motion sensors and a color touchscreen, giving it a broader feature set than simple notification watches. The project went to Kickstarter on August 21, 2013, with a $100,000 funding objective and a scheduled campaign end date of September 20. The target was reached within about twelve hours, and total pledges exceeded $1 million before the campaign closed. Early backers could obtain the watch at discounted pledge levels, while later configurations varied by memory, storage and cellular-band support. The rapid response created substantial expectations for a small hardware company and increased the complexity of production, software preparation and global fulfillment. The production device was based on a MediaTek MT6572 dual-core processor and Android 4.2.2, with the Omate User Interface layered over the operating system. Hardware specifications included a 1.54-inch square display, GPS, Bluetooth, Wi-Fi, a micro-SIM slot, a removable battery and a microSD expansion slot. Separate versions were associated with European and United States 3G frequency requirements. The watch was physically thick by later smartwatch standards, measuring approximately 45 by 45 by 14 millimeters, but its size accommodated the radio, battery, sensors and phone-like electronics required for standalone use. The campaign and production process produced a series of specification clarifications. Marketing material described a 5-megapixel camera, while the production module was reported as 3 megapixels with software upscaling. The processor was advertised in some campaign specifications at 1.3 GHz, but certain 1 GB RAM and 8 GB storage units operated at 1 GHz. Omate attributed the lower clock speed to thermal limitations. The water-resistance presentation also became controversial. The product was promoted with IP67-related language and imagery suggesting use around water, but reference material says the watch was not independently certified in the represented manner, and warranty terms did not cover all water exposure. Opening the case to insert a SIM card, replace the battery or access the microSD card could also compromise warranty protection. Software and certification created a second major problem. During crowdfunding, Omate communications suggested that Google Play applications would be available. The watch later failed to qualify for official Google Mobile Services certification because it did not meet Android compatibility requirements. Omate acknowledged this after the campaign ended, and the TrueSmart shipped without official Google applications. The company created the Ostore instead, offering a smaller catalog and access to third-party application sources. The change narrowed the software ecosystem promised to backers and became one of the most discussed limitations of the product. Fulfillment was delayed by the project’s production difficulties and the size of the campaign. Omate reportedly upgraded some backers from lower-capacity configurations to 1 GB RAM and 8 GB storage as an apology for delays. The last reported Kickstarter batch shipped in mid-June 2014. Some supporters also reported customs complications, missing accessories and differences between the originally described and delivered charging arrangements. A charging cradle replaced an earlier cable concept, improving physical connection but creating limitations while the watch was charging. The TrueSmart also attracted criticism over software security and open-source compliance. Reference material describes a root-access configuration without appropriate permission controls, potentially allowing malicious applications to access user data. It also reports that some source code was not released even though relevant components were subject to GPLv2 obligations. These issues were especially significant because the product was built around a general-purpose Android platform and promoted an ecosystem that invited third-party software. Despite these shortcomings, the TrueSmart occupies an important place in wearable-computing history. It represented one of the earliest consumer attempts to deliver a fully independent Android phone in a wrist-worn product and helped demonstrate the appeal of cellular wearables through crowdfunding. Its experience also showed how difficult it was for a young hardware brand to coordinate radio variants, miniaturized components, Android certification, thermal management, waterproofing claims, accessories and international logistics. The available sources do not confirm whether the product remains manufactured or whether Omate continues to operate in the same form.

1. 2014Final reported Kickstarter batch ships

   Production delays extended fulfillment, with the final reported Kickstarter watches shipped in mid-June.

   Source
2. 2013Kickstarter campaign begins

   Omate opened crowdfunding for the TrueSmart on August 21 with a $100,000 target. The project reached its goal in approximately twelve hours.

   Source
3. 2013Crowdfunding closes above one million dollars

   The campaign ended on September 20 after reportedly raising more than $1.032 million.

   Source
4. 2013Google certification limitation acknowledged

   On October 22, Omate acknowledged that the TrueSmart would not receive official Google certification and would ship without Google Play and Google Mobile Services.

   Source

An early telecom wearable positioned as a self-contained Android phone on the wrist, differentiated from companion smartwatches by cellular independence, calling, navigation and application support.

• Omate TrueSmartStandalone cellular smartwatch2013

  A wrist-worn Android phone with a 3G GSM micro-SIM slot, voice calling, messaging, GPS, Wi-Fi, Bluetooth, Android applications and a 1.54-inch 240-by-240-pixel touchscreen. It used a MediaTek MT6572 dual-core platform, Android 4.2.2 and Omate’s customized OUI software. Hardware included a camera, accelerometer, magnetometer, speaker, microphone, vibrator, removable 600 mAh battery and microSD expansion. Configurations varied by RAM, storage and regional cellular bands.

• OstoreApplication marketplace2013

  Omate’s replacement application distribution channel for the TrueSmart after the device failed to obtain official Google certification. The store offered a limited selection of applications and included access to third-party application sources, but it did not provide the Google Play experience initially suggested during crowdfunding.

• 2013Omate TrueSmart Kickstarter

  International

  Omate used Kickstarter to introduce the TrueSmart as an independent cellular Android smartwatch. The campaign ran from August 21 through September 20, beginning with a $100,000 target and finishing above $1 million in pledges.

  Outcome. The campaign demonstrated strong early demand but was followed by production delays, specification disputes, certification limitations and extended fulfillment.

  Source

• 2014Upgrade selected delayed ordersOther

  Production and shipping delays affected multiple Kickstarter configurations.

  What changed. Omate upgraded some 512 MB and 4 GB configurations to watches with 1 GB RAM and 8 GB storage as an apology for delays.

  Aftermath. The upgrades partially addressed fulfillment concerns, although accessory delivery and other backer complaints remained.

  Source
• 2014Adopt a charging cradleOther

  The original charging approach was changed during development in response to connection and usability considerations.

  What changed. Omate supplied an external charging cradle in place of the earlier cable arrangement.

  Aftermath. The cradle provided a more robust connection but made it difficult to press the watch buttons while charging.

  Source
• 2013Position the watch as a standalone telecom wearableStrategy

  Most early smartwatches functioned primarily as companions to smartphones, while Omate sought to differentiate the TrueSmart through independent cellular operation.

  What changed. The company integrated a GSM/3G modem, micro-SIM support, Android applications, GPS and phone functions into the watch and marketed it as “smartwatch 2.0.”

  Aftermath. The positioning made the TrueSmart distinctive, but it also increased the product’s hardware, thermal, software and carrier-compatibility complexity.

  Source
• 2013Replace Google Play with the OstoreOther

  The TrueSmart could not satisfy the requirements for official Google Mobile Services certification.

  What changed. Omate shipped the watch without official Google applications and used its own Ostore marketplace, including access to selected third-party application sources.

  Aftermath. The software ecosystem was smaller than the Google Play experience suggested during the campaign, creating dissatisfaction among some backers.

  Source

• 2014Specification, water-resistance and fulfillment disputesControversy

  Backers and commentators raised concerns about the camera’s native resolution, processor clock speed, water-resistance claims, warranty restrictions, delivery delays, missing accessories and customs problems. The reference material describes these as recurring project complaints rather than a single formal legal proceeding.

  Source
• 2014Security and open-source compliance concernsControversy

  The device’s root-access configuration was criticized as exposing user data to malicious applications, while incomplete publication of source code was reported as inconsistent with GPLv2 obligations for relevant components.

  Source
• 2013Google Play and certification controversyControversy

  Campaign communications suggested Google Play support, but the TrueSmart did not meet the requirements for official Google certification. Omate acknowledged the limitation after the crowdfunding campaign had ended, and production devices shipped without Google Mobile Services.

  Source

• 2014Kickstarter fulfillment extended into 2014

  Manufacturing and production issues delayed delivery beyond the original expectations. Omate upgraded certain backers to higher-memory and higher-storage configurations, and the final reported Kickstarter batch shipped in June 2014.

  OtherProduct generation
  Source
• 2014Backers reported specification and accessory discrepancies

  Reference material describes complaints concerning processor clock speed, camera resolution, missing or delayed accessories, charging hardware, customs charges and the absence of the originally anticipated companion-software experience.

  Other
  Source
• 2013Omate launches Kickstarter campaign for TrueSmart

  Omate began crowdfunding the TrueSmart as a standalone Android smartwatch with cellular connectivity. The campaign exceeded its $100,000 goal within roughly half a day and ultimately raised more than $1 million.

  CampaignProduct launch
  Source
• 2013TrueSmart Google Play support was withdrawn

  After the campaign, Omate acknowledged that the watch could not obtain official Google certification and would therefore ship without Google Mobile Services and Google Play. The company substituted its Ostore marketplace.

  OtherRegulation
  Source

1. Omate TrueSmart
2. Omate official website