Touchless Control

Though the UI for the Moto X is indeed stock android basically everywhere ($12.5 Billion later, Google finally killed Motoblur), there are two specific software customizations on the Moto X which are chief differentiators. The first of which is touchless control, which is essentially a combination of always-listening voice command, and Google Now.

The way it works is simple – say “OK Google Now” with the phone in literally any state, and you’ll get dumped into a special Google Now prompt. It works with the phone in standby mode (screen off, powered on, but in deep sleep), or with screen on.

 

There’s a training initialization which asks you to say “OK Google Now” in a very quiet room three times (I had to lock myself in a bathroom for the meter to register quiet enough) to enable the feature. After that, saying OK Google Now works well and powers on the phone to this menu. Users cannot change the OK Google Now keyphrase to something custom.

For this system, Motorola uses a natural language processor (NLP) of custom design that I haven’t quite tracked down yet. This controller constantly listens on the 3 microphones onboard Moto X for the “OK Google Now” keyword, then wakes up the AP and enables the Google Now prompt. Motorola says it went with this solution to enable always-on voice without killing battery life from running the main AP all the time (which does make sense). It works surprisingly well, maybe even too well, as even after training saying “OK Google Now” can turn on every Moto X around you. Just something to be aware of.

Contextual Processor

The contextual processor powers two other features, active display, and the gesture-enabled quick capture camera.

Active display is Motorola’s solution to the constant device checking and glancing that users do to find out why a notification fired. It’s a view that sits above the lock screen and displays the last few notifications and enables you to dive into the appropriate app that triggered it. Information just appears on the display when it’s in an off state, breathing in and out when the device is face-up on a surface. Otherwise, flipping the Moto X from face down to face up will bring up the display – I can’t screenshot it, this seems to live outside Android entirely.

To get a preview, you can touch the notification, and then drag up. Dragging left or right clears notifications. Dragging up into a notification will dive into the appropriate application.

There are privacy settings to enable or disable how much information you can have displayed on the active display notification screen so this doesn’t bypass if you have a lock screen on purpose.

I leave my phone face-up on my desk instead of face down to prevent screen scratches, where and the Active Display notification screen pulses periodically with the time and when notifications come in. It works well, I just need to spend time with it.

The other contextual-powered feature is quick capture, which is the quick enter camera gesture. Hold the Moto X, flick your wrist like a screwdriver, and you’ll get popped into Motorola’s camera UI for the Moto X.

The UI is very simplified and makes some interesting choices. Tap to focus and expose is disabled by default – instead tapping anywhere captures a photo. Tap to focus can be re-enabled in the settings, which fly out from the left, but now tapping anywhere focuses on that region and captures immediately. I’m not sure if I like this change. The camera sensor is 16:9, and the preview is likewise 16:9, so there’s at least no cropping going on.

The UI includes HDR, flash control, tap to focus enable/disable, slow motion video (720p60), panorama, location tagging, shutter sound, and the flick gesture enable/disable. What’s missing is photosphere support, unfortunately. Dragging right gets you into the gallery, and there are buttons for changing to the front facing camera and taking video instead of photos. This is sort of a tweaked Android 4.2/4.3 camera UI, with stuff just moved around and photosphere removed.

I’ve done some digging around and believe that Motorola is using a TI MSP430 microcontroller for its contextual processor, as this seems to do at least sensor fusion for the different situational positions. I’m not sure if this also powers the active display functions but wouldn’t be surprised if it did.

Introduction, Design & Hardware Thoughts on Moto X
Comments Locked

162 Comments

View All Comments

  • haukionkannel - Friday, August 2, 2013 - link

    Well it is made in USA so it will cost more. You can make cheap phones in Asia and use slave labour to do it. You as a customer have to deside if is a worth of it.
    I personally would like a full test of this device until I will make my desision. This seems to be extremy well done phone, so it has its merit even without the most powerfull hardware. I am guite sure that there will be customers to a phone that looks and feels nice in the hand.
  • darwinosx - Friday, August 2, 2013 - link

    It is assembled in the US with parts made in Asia. Big difference. And it's Texas where they have slave labor wages.
  • darwinosx - Friday, August 2, 2013 - link

    Because if they don't make a profit they go out of business. Did you really have to have that explained.
  • gorskiegangsta - Thursday, August 1, 2013 - link

    Indeed it is. :(

    I was hoping for a <$400 off-contract Nexus-type device. $199 on contract, when one can get HTC One, GS4, or iPhone 5 for the same price pretty much makes Moto X DOA.
  • boot318 - Thursday, August 1, 2013 - link

    Google should have Moto built their Nexus devices. I mean, do something with your investment. Anyway, I like the design for some reason. The 'curves' are to my likely. The price is an let down though.

    Thanks for this preview @ Anandtech and Brian
  • darwinosx - Thursday, August 1, 2013 - link

    This would further alienate the other Android manufacturers who except for Samsung are losing money by the bucketful and have been for years. Samsung of course won't say how much they make and are notorious liars anyway. But then so is Google.
  • dNj - Thursday, August 1, 2013 - link

    Not attacking you but I'm tired of the excuse, Google would alienate other Android OEM's. These OEM's have had years to do something impressive with Android. Yet all they end up doing is pissing on the Android brand with crap skins and duplicate apps already incorporated to the OS. It is way past the time for OEM's to sink or swim. I say let them all sink and leave the world with only a few solid Android device makers.
  • darwinosx - Friday, August 2, 2013 - link

    I suppose I agree but I doubt Google would.
  • krutou - Friday, August 2, 2013 - link

    Good luck with that.

    Android phones are popular but Google isn't automatically godly at making and selling phones.
  • darwinosx - Thursday, August 1, 2013 - link

    "The idea of a wood-backed phone excites me"

    Seriously?
    This phone will be a flop.

Log in

Don't have an account? Sign up now