As I'm sure you've seen by now, earlier today Google exploded a bombshell by unveiling the Android Wear smart watch initiative along with a number of partners that will be making the hardware later this year. Last but not least, the Android Wear Preview SDK was announced so that developers could start playing with the Android Wear watch emulator hooked up live to their devices and get the feel for how everything will work.

After watching all the videos and reading through all the details, I jumped into it straight away, signed up for the preview SDK, and installed all the necessary components. In this post, I'm going to show you what the SDK can and cannot do right now. Right now the focus is on handling notifications from various apps running on the device paired with the watch which makes Android Wear more of a sidekick rather than a full-fledged standalone device. This may all change, but many smartwatches already work in a similar fashion.

Without further ado, let's take a look.


The components involved are:

  1. Signing up for the preview SDK here.
  2. Once you're approved, you're essentially added to a tester group that gives you access to the Android Wear Preview app. Install it. Don't worry, you're not missing out on much - it's very basic and serves as a glue between the device and the watch. It sends notifications, receives responses, and acts on them - that's about it. The key here is that we can actually act on notifications, which is what a lot of smartwatches so far have gotten very wrong. Samsung tried but because of that had to limit support to only its own devices.
  3. Install the Android SDK.
  4. Install the Android Wear system image via the SDK, along with a few more things described here.
  5. Create an Android Virtual Device (AVD) with the Android Wear configuration and fire it up. You can pick a square or round watch shape - I recommend square because the round one cuts off a lot of information and is much more awkward to use. You'll see a demo later on in this post.
  6. At this point, you have to hook up the device running the Android Wear Preview app from step 2 to your computer, execute an adb command to set up communication (adb -d forward tcp:5601 tcp:5601), and you're off.
  7. If you're a developer, you can download 3 example apps that come with the preview SDK to get a better understanding of how the code works. Just look for the link in the welcome email. The apps are called ElizaChat, RecipeAssistant, and WearableNotificationsSample.
  8. There's also the official Android Wear Developers Google+ community - join up if interested.

wm_3-18-2014 12-36-03 PM Screenshot_2014-03-18-12-23-39

Left: AVD Manager. Right: Android Wear Preview Android app

So, what do you get once you start the AVD and connect it to your phone? Behold the Android Wear:


The hands-on part - the one you're really here to see

While the final product will be much more involved and sophisticated, the Android Wear Preview has concentrated strictly on notification handling. Here's what you can play with:

  • The home screen, which consists of the clock, the voice input button, and the topmost notification.
  • You can pull the top part of the screen down at any time to show the date and charge level.
  • The area occupying the very top 4-5% of the screen acts as a Home button and brings you back to the home screen.
  • The voice input button, unfortunately, doesn't work in the preview SDK. Huge bummer, since it's supposed to do this. Some of the provided sample apps actually initiate the dialog but voice input does not work, and the dialog just times out. The idea of bouncing input between taps, swipes, and voice is awesome, and I can't wait to try it out in real life.
    Update: You can actually type in the response using the physical keyboard and play around with responses that way.
  • You can scroll through your notifications by flicking up and down.
  • Each notification can have actions that you get to by swiping right-to-left. Each action occupies a full screen for easy tapping.
    For example, grouped Gmail messages offer an Open button, which opens the Gmail app on the phone. Individual Gmail messages offer Delete, Reply All, and Open buttons, which - you guessed it - act accordingly, also on your phone.
    This is something no other companion watch is able to do to my knowledge. The Galaxy Gear comes close and is able to pop up the app, but I don't think it can dive this deep into actions. I could be wrong though - I haven't played with the Gear since its launch (I decided to go the Toq and Pebble Steel route).
  • Notification stacks/bundles collapse multiple notifications into a more compact view. Unfortunately, 2 Gmail notifications for 2 separate Gmail accounts didn't stack the way they are shown here, but as you can see below, a sample app did it just fine.
  • Sometimes, the background changes from black to something else, like an exploded icon of a sender in the current Gmail notification.
  • Swiping left-to-right from the main notification area dismisses it. This also dismisses it on the phone, which is great - a lot of smartwatches maintain their own notification lists and don't sync both ways.
  • You can expand some notifications, such as individual Gmail emails, by tapping the bottom part where they start to fade away. This way, you can read an entire email without having to turn on the phone. Neat.
  • The screen dims after about 12 seconds. I'm really curious what will happen on a real device - will it turn completely off? Will we be able to wake up the display using a flick gesture or a voice command? These questions remain to be answered.
  • Neither Google Now nor Calendar notifications showed up on the watch for me. Perhaps they're missing some secret sauce. Too bad, as I wanted to test out paged notifications. The good news, however, is that the sample preview apps contain plenty of examples, which you can see below.

And now it's time for some illustrations and animations.

SNAGHTML64f6b4fe 3-18-2014 12-01-06 PM 3-18-2014 12-01-27 PM

Left to right: home screen, individual notification, swiping through the actions

3-18-2014 12-21-52 PM 3-18-2014 12-21-45 PM 3-18-2014 12-21-36 PM

Left to right: various actions that then get forwarded to the phone

3-18-2014 12-22-57 PM 3-18-2014 12-16-33 PM 3-18-2014 11-55-30 AM

Left to right: dismissing a notification starts fading it away, dimmed screen, disabled voice actions

SNAGHTML6510c5f0 SNAGHTML651103d9 SNAGHTML651319aa

More examples - these have a single Open action or none at all

SNAGHTML656cea34 SNAGHTML656d3a65 SNAGHTML656d6665

Hey look, Spotify (above) and Play Music (not shown) do work out of the box, including pause, unpause, next, and previous!

SNAGHTML651bba8b SNAGHTML65189d1c SNAGHTML651bd50d

User input

SNAGHTML654004a5 SNAGHTML653fee86 SNAGHTML6540195d

User input (continued)

SNAGHTML6516e40a SNAGHTML651a5f51 SNAGHTML651a7735

Various samples that come with the SDK preview

SNAGHTML65220cb0 SNAGHTML6522f1ff SNAGHTML65235794

Various samples that come with the SDK preview

Shall we move on to the GIFs?

Paging through actions in a notification and then dismissing it

Note: This is the round watch face - as you can see, elements get cut off, and using a square watch face is much more enjoyable. After this first GIF, I made the switch.


Going through notifications and reading a long notification


Screen dimming


Voice actions :(


Date and charge level pull-down


Pressing the invisible Home button



Google's Android Developers Youtube account goes even deeper into the developer preview:

The next video shows how voice replies can do the heavy lifting of replying to messages without using the phone. Too bad this doesn't fully work in the SDK preview, although you can type in the responses using the keyboard instead:

And that about wraps it up. As you can see, the preview SDK really is quite simple and concentrates strictly on notifications. By the time the full SDK comes out, developers will have already had a chance to make sure notifications work well in their apps.

I'm now excited about the future of wearables more than ever because I think the approach is finally correct for the first time. A device with a tiny screen should be glanceable, controlled hands-free, and allow for a lot of imprecise presses, and it's exactly what Google is going for with Android Wear. The 2nd half of 2014 can't arrive soon enough. After all, that's when we should expect this:

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • fireworksordie

    this is looking so cool. though i'm trying to imagine tapping the "invisible home button" and it seems like it would be a bit strange.

    • http://www.androidpolice.com/ Artem Russakovskii

      It's the same idea as the Toq's invisible action button that's located on the watch band. I imagine it's going to be pretty natural to tap the top of the Wear watch to end up at the top.

      • fireworksordie

        ah, that makes more sense. this is all so exciting. my pebble will have had a nice year and a half of life, i guess.

        • http://www.androidpolice.com/ Artem Russakovskii

          I just got my Steel 2 days ago :(

          Then again, Wear isn't out yet.

    • Dennis Ulijn

      The Moto 360 has the button on the side. I bet you that's their home button.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      Emulators will often add these invisible / virtual buttons when they are supposed to represent a hardware button or some kind of input that just can't be represented on the screen. A "Home" button is probably a platform-specific feature that is up to the OEMs to implement however they like. It could end up being a capacitive button on the face, a physical button above or below the screen, or even something crazy like a sensor that detects gestures.

  • Zech Zimmerman

    The Android emulator doesn't have Gapps (if I'm remembering correctly) so Google Now features wouldn't work... I think.

    • http://www.androidpolice.com/ Artem Russakovskii

      That has nothing to do with that. The watch emulator is very simple but the phone is the one serving up the Now notification since it's fully-featured and not an emulator. If Gmail works, I don't see why Now or Calendar shouldn't.

      • Zech Zimmerman

        What about the search abilities on the device? Is the phone pushing all of the info down?

        • http://www.androidpolice.com/ Artem Russakovskii

          Search isn't available at the moment. Nothing about the mic works, so we can't test it.

  • hagen.sal

    The preview of the watch in the developer video looks rather fake and edited-in actually. Let's hope it will still work and look similarly in the final products!

    • tom

      The complex voice control is all that is so far a concept. This article shows basically everything else working very well ..?

    • Aaron Berlin

      The videos say that they're simulated screens. But in any event, you can't compare what you get out of Android running on a VM on a computer to running on native hardware. They're doing this more-or-less from scratch, and I can't imagine they aren't putting a premium on smooth UI.

  • remister

    Yes Yes Yes, give us more GIF until they release the damn thing!!!111!!!!

    • ProductFRED

      I'm going to print out each GIF frame-by-frame so I can tape a flipbook on my arm and pretend it's a Wear watch.

  • david coffey

    I'm officially in the market for a tech wearable when this hits the street. This is done right.

    • Justin W

      I was initially not thinking about it until I saw the Moto360... Now I'm sold.

  • remister

    Spotify looks a bit clunky, no music controls? Hopefully when this hits there will be a UI where you can search or look through your own playlist.

    • Ryan O’Neill

      You can bet there's gonna be music controls when this rolls out. The SDK was only released this morning, so no apps are optimized to use the Android Wear actions.

      • remister

        Well, obviously that would be on Spotify devs if they want to implement that. Crazy if they didn't. Sadly I heard they won't be implementing Chromecast support.

        EDIT: Even at that, I think there might be a generic control UI within the API system.

        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          Android (and pretty much every other mobile OS) offers a built-in interface for music players to hook into that allows for external player controls. That's how so many of them can work without custom lockscreen controls and widgets. As long as Spotify implements that interface (they must, right?), the watch can do the same, once the wearable team implements it. In the meantime, notification-based controls are working.

          • remister

            May I see a gif/pic of that, before I go bezerk.

          • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

            I was just showing it to Artem, refresh the page ;)

    • tom

      the one I saw was just a now-style notification about a new song, not a now-playing screen.

    • Aaron Berlin

      I'd love to see what this looks like when you have a persistent playback notification (or a "Now Casting" notification). Maybe that's not possible from within the sdk?

      • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

        At the moment, persistent notifications don't seem to be mirrored to the watch interface. I suspect that will remain true since you wouldn't want all of those background services to make a mess of the watch notifications.

        • Kcls

          I'm guessing things like music and apps that cast from the phone would show up, but that's it. Only media apps.

          If they all show up, I can just see people walking around with an "Advanced Task Killer" persistent notification on the watch. *shudder*

        • http://www.bordersweather.co.uk/ Andy J

          I would expect high priority ones to show up - as stuff like flight alerts and whatnot from Google Now use those. The DevBytes video makes it crystal clear that the NotificationListener service introduced in 4.3 is what makes Android Wear possible.

          • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

            I'm not sure if I'm reading your comment as you intended it. The second sentence sounds like you're contradicting something, but I'm really not sure of what. I apologize if I'm misinterpreting. Nobody was disputing that 4.3 enabled notification mirroring. The question is about which persistent notifications will or won't appear. Most music players set a fairly high priority so that the player controls appear at the top of the list, and not surprisingly, they are showing up on Wear. Utility apps (like SwipePad) that use a persistent notification to keep themselves running are usually going to set priority to minimum so they stay out of the way.

            Maybe there's more to it, but that's as far as I've had time to play around. I've been hip deep in teardowns for the last few hours.

  • TheUndertaker21

    you seem to compared it to Samsung so much, yes we know that Gear is just a test smartwatch, but it's the Best current smartwatch out there, something that you can't deny unless you hate samsung products!!! try to have some justice and don't support one side while not the other, your site name is Android, so you better talk equally about all Android products!!!

    • http://jordanhotmann.com/ Jordan Hotmann

      This makes the gear look like a baby toy.

      • hot_spare

        'This' doesn't exist.

    • remister

      This will only inspire Gear devs to do better, if anything.

    • Dennis Ulijn

      I will consider even thinking about buying the Galaxy Gear IF I CAN USE IT! If you don't have a samsung phone, you're out, for the moment. I know it's coming up, their support for different brands, but now that I've seen this...

      • tom

        is it coming up? I was pretty sure their OS solution for wearables made supporting non-samsung devices impossible.

        • Dennis Ulijn

          From what I heard the Galaxy Gear 2 and Neo 2 will support different brands. Probably through an app on the phone, maybe limited use, but Tizen, what the Gears are running can communicate with this app.

    • imlip

      well... like you said. samsung gear is the best currently available so of course he will compare it to the gear.

      By the way, the gear is the best of the worst. releasing an unpolished product just to be the first is a really bad strategy.

    • http://petercast.net Peterson Silva

      "yes we know that Gear is just a test smartwatch"

      Is it being sold? Oh, it's the second generation already, I see... It is not a "test" smartwatch. It is a product.

      "your site name is Android"

      Funny you should say, because, you know, Gear is not running Android anymore :)

      • TheUndertaker21

        so laugh I forgot to funny, teach me some android master I need to learn from you, we'll see in 2015 when Samsung enters the market with the flexible displays, making every single point of yours WRONG. go study some android KID

        • http://petercast.net Peterson Silva

          Haha, I really don't understand people who get so attached to companies. I really don't have time for your petty fights, mate, and your text comprehension is so broken it hurts (What part of what you said has any relationship to what I said? Well, nevermind...). Farewell ;)

    • http://www.androidpolice.com/ Artem Russakovskii

      What the heck are you rambling about? If anything, I said the Gear came the closest to what Google is trying to do. But I don't own one, so I can't compare it further.

      • TheUndertaker21

        there is a famous football commentator at which in every single match International or Local he says his famous quote '' but Messi is better '' and you remember me of this guy, he just as you talks about some unnecessary things while commentating on a match just as you who try to put you hate against Samsung, just to remember you Samsung has %65 Market Share, and guess what ??? That number won't gonna easily come down!!!

        • Dennis Ulijn

          Dude, first you say he needs to think of Samsung because this is an Android website, and then when he DOES make the comparison to the Samsung Gear he's downplaying Samsung... There's enough Samsung news on Android Police, but news like this, a smartwatch that WILL actually shape the future because it has the proper software behind it, is what I want to read about. I don't want to read about Samsung opening a can of new products, throw them at the wall and see what sticks. I'd like to invite you to count the comments for random AP articles and AP articles about Samsung.

          PS I don't find AP downplaying Samsung. Leave that to the Verge.

        • http://www.androidpolice.com/ Artem Russakovskii

          Lolwut, now I hate Samsung somehow? I use a Note 3 as my primary device, and my previous one was the Note 2 and S2. Go troll elsewhere.

    • http://turbofool.com Jarrett Lennon Kaufman

      Define "best." That classification depends entirely upon what you expect out of a smartwatch. For my definition, the Pebble is currently the "best" smartwatch. But if for you "most features" equates to "best," then sure, it's probably the Gear. Just define your terms.

  • slick8125

    any chance google deliberately put out glass before this to test drive what people actually want with wearables? pretty brilliant if that was their plan. although i'd guess common sense told them to leave the camera out *cough*samsung*cough*

  • David Fleck

    I really hope there are standalone Android wear devices, not just companion devices.

    • John Samuel αΩ

      That doesn't appear to be the case. The phone deals in notifications, but without a phone there would be nothing to receive notifications from. It could probably be rooted to run its own version of Android, but it would be sort of useless since I'm assuming this thing only has the ability to communicate via bluetooth 4.0 (low power).

    • Ash

      Maybe you should wait one from Apple :)

      Joke aside, I believe standalone Wear is possible, but it will have limited functionality, unless the device has standalone internet connection.
      So it depends on Wear manufacturer, what kind of hardware they willing to put into their Wear device.

    • Fatty Bunter

      There will be once battery drain is low enough to support a cellular radio chip and still have the device last more than a day.

      • David Fleck

        I think you are spot on. This is also why I have purchased stock in battery manufacturers.

  • Android Developer

    So even the emulator for the watch is super slow? Or is it because it's a GIF animation?

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      But remember, the emulator running ARM without any tricks is going to run fairly slow framerates. The screens in the video are simulated, so they also can't be used as a precise judgement. Still, I expect the final product will be a lot more similar to what we see in the video than what we see from the emulator (especially after it has been gif'd).

      • Android Developer

        Wait, are you saying the normal emulator runs fine on your PC ?

      • Android Developer

        Wait, are you saying the normal emulator runs fine on your PC ?

        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          heh? Where did you get that? I said the emulator produces slow framerates.

          • Android Developer

            You wrote "without any tricks", so I thought you are saying you have tricks to make it work well.
            I don't get why Google still doesn't keep its promise to make the emulator much faster. There was a lecture at least 2 years ago that they said it will be faster, and I can't see the emulator working well on any OS or PC.

          • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

            oh, by "tricks" I was referring to using stuff like HAXM with an Intel image or using Genymotion instead of the standard emulator. I agree with you, it's painfully slow, even on obviously scaled down and optimized things like the Wear image. I would love to see Google partner with or buy Genymotion and migrate it in as a default.

          • Android Developer

            Well I think it all started by their weird decision to use the awfully slow VM called Qemu , instead of one that really works well like VirtualBox.

            At least, that's from what I've tested and noticed.

          • Brandon Smith

            I have a 16GB RAM, i7 Haswell rMBP and it still runs terribly. With that being said, using the Intel image definitely helps. Also, the emulator doesn't run _terribly_ if you lower the specs of the emulated device, which worries me a bit in light of the Wear's supposed spec range.

          • IamTheFij

            Have you seen the Simulator?

            They now offer x86 system images that will allow you to Simulate Android rather than emulate the full architecture. This is considerably faster. Unfortunately there is no x86 image for the watch firmware.

          • Android Developer

            Which "Simulator" ?
            The x86 image didn't work for me as well as I my PC can do using VirtualBox . My PC isn't that new, but it easily simulate a full blown Ubuntu there using VirtualBox ...
            Yet it can't run Android well...

          • IamTheFij

            You're misunderstanding what is difficult. Running a virtual box or simulator doesn't waste many cycles. Emulation does.

          • Android Developer

            I'm saying I really ran Android in the past on VirtualBox, and it ran really well.
            I think I ran it using a "Android-x86 Project" image :

            Anyway, it's very fast, but it's not comfortable and doesn't give you the same features as on Google's android emulator.

            There are also other alternatives that show that Android emulation can be much faster on the PC. For example Ganimotion ,BlueStacks, etc...
            I even had "jar of beans" which was a package of many useful built in stuff for development . it was portable, rooted, and with play store all built in . sadly it was removed and discontinued .

          • IamTheFij

            Oh, I see. That makes much more sense. I think the biggest issue is that it's not trivial to get the Android x86 simulator working. It does provide more of a familiar experience than doing it with VirutalBox

          • Android Developer

            I don't understand why you keep calling it "simulator".
            all of those solutions are emulations, of a real full blown OS.
            I think the whole reason that Google's emulator is slow is that it uses Qemu as the virtual machine. All other solutions worked really well for me.

          • IamTheFij

            I meant emulation of a different architecture.

            This is really the difference I'm referring to. https://www.virtualbox.org/wiki/Virtualization

            "While emulators theoretically allow running code written for one type of hardware on completely different hardware (say, running 64-bit code on 32-bit hardware), they are typically quite slow. Virtualizers such as VirtualBox, on the other hand, can achieve near-native performance for the guest code, but can only run guest code that was written for the same target hardware (such as 32-bit Linux on a 32-bit Windows host)."

            Also highlighted in the documentation for Qemu "When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC)"

            The complicated (costly and slow) part is translating instructions for ARM to run on x86. This is not done with the x86 images that you used or the ones included in the Android SDK.

          • Android Developer

            I see, but how come they don't use this method now that we have Android working well on Intel architecture?
            Also, how does the emulator/simulator of IOS and WP work? I've seen them both and they work well in terms of speed (though WP had many bugs on my PC) ?

          • IamTheFij

            That's the real question! The x86 version should be pushed as the go-to version and should have better support.

            The ARM emulation should be provided as a catch-all like "Good to use just in case."

            iOS in XCode is also a simulator. When you compile an App in XCode for debugging it actually compiles for x86 instructions (I believe it does both and provides two binaries) and runs in a simulated iPhone environment, but on the local arch.

            The WP8 emulator is hard to tell from the documentation (I have no experience with it personally). http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402563(v=vs.105).aspx

            I do know that most WP apps are going to be .Net. This puts it in a situation like Android where the device, ARM or x86, will be running a virtual machine. In Android it's Dalvik and WP it's the .Net Runtime. So if the runtime is ported to the platform it provides a good simulation of the environment without translating instructions to ARM. My guess is that this is what they are doing.

            I do see you can do native C++ on WP8 now, but I'm not sure if that code is compatible with their phone emulation tools or if it requires you to target your compile to ARM or x86 when building for it.

          • Android Developer

            Have you seen the video that Google promises to make the emulator much better, that they show a prototype of playing a 3d game inside it?
            I wonder what became of this promise.
            I also wonder when ART will make things better.

  • wollac11

    So if these devices come with a mic for voice commands do you think you could also use them to take voice calls from your wrist? Even better would be if there was front facing a camera too so you could do video Hangouts on it!

    • remister

      One thing at a time now. Remember nothing too battery intensive.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      Don't forget, you need a half decent speaker so you can understand what the other person is saying. On top of that, huge noise cancellation so the speaker doesn't interfere too much with the mic. I get what you're going for, but it's probably not going to be a very good experience...at least, not until these things can be refined.

  • http://www.flickr.com/photos/77537273@N03/ Herman

    The resolution of this preview (presumably the highest resolution it will support) does not let me down at all, I was expecting much worse. After all, with these smaller buttons and text, it should still be readable so I am expecting a decent pixel density on these smartwatches.

  • http://www.flickr.com/photos/77537273@N03/ Herman

    I don't know

    Can you repeat the question

  • cole

    Is there anyway for this to be ported to the sony smartwatch 2 (when full sdk is released) , would def make the watch a million times better.

  • KoRRo

    regarding the wake/home i'm thinking about a phisical key. the home you used looks to be outside the screen, so probably it won't work like that in a real product. also in the moto 360 there's something similar to the knob of a real watch that could act as a phisical button. imo this will work as the hidden home button and probably as a power/wake button.

  • dogulas

    Those knowledgeable: Do you think it would be feasible for Google to implement a display feature that would allow the user to set a custom degree rotation for the round smartwatch display? This wouldn't be the hardware, it would be an OS feature. That way you could adjust it to an ideal angle for the perfect view, since watches are difficult to get in line with your sight. A 45 degree angle would be awesome and perfect in my opinion.

    • esper256

      People who know something about previous round displays indicate that the black strip at the bottom is a technical limitation regarding where the controller interfaces with the display. So rotating would be challenging because the black band has no pixels there to display content.

      • dogulas

        I didn't notice a black band. But maybe that was only visible in the Motorola version.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      Pixels are generally square (or at least lined up rectangles), and the OS renders its graphics that way. On pictures/images, things won't look too different when they are rotated, but there will be some minor distortion. Text and lines are going to come out pretty pixelated and fuzzy. It's not that it can't be done, you just won't like the result. Look at the Gmail icon and how crumby the edges of the envelope lines are for a fair idea of how it would be affected.

      With a really high pixel density, this effect gets a lot less noticeable, but I don't think we can expect the first round of devices to hit that kind of mark. Give it a generation or two (when even watches have 300+ ppi) and this will become much more practical.

    • Key

      That would be awesome. Combine with gyroscope (if any) so watch face rotates based on gravity. I hope some OEM put gyroscope in their Wear smartwatch. Or Apple will ;)

  • John Samuel αΩ

    This is the first I've seen "call a cab to take me home" action on Google Now. Is there any information about that anywhere? Really interested to know how exactly it works. Obviously it could get your location and now knows where your home is, but how is it communicating with the cab company?

    • Frederick Stephens

      M. Knight Shyamalan level Plot twist: Google just hinted to taking on Uber

      • Googlr

        Ask your Android Wear watch to call you a taxi to take you home - Google sends a driverless car to pick you up. THE FUTURE!!!!

  • Samuel Hsieh

    I hope there is TTS support on this. Like "OK Google Now, read me my notifications" or something.

  • John Smith

    >Individual Gmail messages offer Delete, Reply All, and Open buttons
    >This is something no other companion watch is able to do to my knowledge.

    There is several apps for pebble that can dismiss notification, and the best is AutoPebble from Joao Dias that can mirror the notification, including buttons (for gmail is reply and archive) and open app on phone... and it can do a lot of fun stuff.

  • Péter Szentkirályi

    If anywhere, the CARDS UI of webOS would be perfect here! Imagine swiping thorugh the different notifications horizontally then dismissing the unwanted ones vertically. HNGGGGGGGGGGGGGGGGGG

  • spsp01

    03-20 18:59:18.900: I/ActivityManager(444): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x13200000 cmp=com.google.android.wearablepreview.app/com.google.android.clockwork.home.HomeActivity} from pid 6059
    03-20 18:59:19.270: V/Zygote(6649): Switching descriptor 31 to /dev/null
    03-20 18:59:19.280: V/Zygote(6649): Switching descriptor 9 to /dev/null
    03-20 18:59:19.290: I/ActivityManager(444): Start proc com.google.android.wearablepreview.app for activity com.google.android.wearablepreview.app/com.google.android.clockwork.home.HomeActivity: pid=6649 uid=10056 gids={50056, 3002, 3001, 3003}
    03-20 18:59:19.580: V/ActivityThread(6649): com.google.android.wearablepreview.app white listed for hwui
    03-20 18:59:19.660: D/ClockworkHome(6649): onCreate: com.google.android.clockwork.home.HomeApplication
    03-20 18:59:19.720: W/ClockworkHome(6649): not a notification listener, but we don't have perm to change it.
    03-20 18:59:19.770: D/ClockworkHome(6649): localNode=13ee364c-ebd8-40ff-80a0-cc489d91d80e
    03-20 18:59:19.960: D/BluetoothManagerService(444): Message: 20
    03-20 18:59:19.970: D/BluetoothManagerService(444): Added callback: android.bluetooth.IBluetoothManagerCallback$Stub$Proxy@41de5088:true
    03-20 18:59:19.970: D/BluetoothAdapter(6649): 1100047848: getState() : mService = null. Returning STATE_OFF
    03-20 18:59:20.070: D/ClockworkHome.Media(6649): starting media control receiver
    03-20 18:59:20.330: W/dalvikvm(6649): Unable to resolve superclass of Lcom/google/android/clockwork/home/stream/TemporaryActivityViewWrapper; (20)
    03-20 18:59:20.330: W/dalvikvm(6649): Link of class 'Lcom/google/android/clockwork/home/stream/TemporaryActivityViewWrapper;' failed
    03-20 18:59:20.330: E/dalvikvm(6649): Could not find class 'com.google.android.clockwork.home.stream.TemporaryActivityViewWrapper', referenced from method com.google.android.clockwork.home.stream.StreamLayout.buildWatchface
    03-20 18:59:20.330: W/dalvikvm(6649): VFY: unable to resolve new-instance 516 (Lcom/google/android/clockwork/home/stream/TemporaryActivityViewWrapper;) in Lcom/google/android/clockwork/home/stream/StreamLayout;
    03-20 18:59:20.330: D/dalvikvm(6649): VFY: replacing opcode 0x22 at 0x0004
    03-20 18:59:20.410: W/dalvikvm(6649): Unable to resolve superclass of Lcom/google/android/clockwork/home/stream/TemporaryActivityViewWrapper; (20)
    03-20 18:59:20.410: W/dalvikvm(6649): Link of class 'Lcom/google/android/clockwork/home/stream/TemporaryActivityViewWrapper;' failed
    03-20 18:59:20.410: D/dalvikvm(6649): DexOpt: unable to opt direct call 0x0aee at 0x0a in Lcom/google/android/clockwork/home/stream/StreamLayout;.buildWatchface
    03-20 18:59:20.530: W/dalvikvm(6649): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/google/android/clockwork/home/speech/hotword/HotwordJni;
    03-20 18:59:20.530: W/dalvikvm(6649): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/google/android/clockwork/home/speech/hotword/HotwordRecognizerRunner;
    03-20 18:59:20.530: D/AndroidRuntime(6649): Shutting down VM
    03-20 18:59:20.530: W/dalvikvm(6649): threadid=1: thread exiting with uncaught exception (group=0x41633c20)
    03-20 18:59:20.540: E/AndroidRuntime(6649): FATAL EXCEPTION: main
    03-20 18:59:20.540: E/AndroidRuntime(6649): Process: com.google.android.wearablepreview.app, PID: 6649
    03-20 18:59:20.540: E/AndroidRuntime(6649): java.lang.UnsatisfiedLinkError: Couldn't load clockwork_micro_hotword_jni from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.google.android.wearablepreview.app-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.google.android.wearablepreview.app-1, /vendor/lib, /system/lib]]]: findLibrary returned null
    03-20 18:59:20.540: E/AndroidRuntime(6649): at java.lang.Runtime.loadLibrary(Runtime.java:358)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at java.lang.System.loadLibrary(System.java:526)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at com.google.android.clockwork.home.speech.hotword.HotwordJni.(HotwordJni.java:5)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at com.google.android.clockwork.home.speech.hotword.HotwordRecognizerRunner.(HotwordRecognizerRunner.java:58)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at com.google.android.clockwork.home.HomeActivity.onCreate(HomeActivity.java:77)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.Activity.performCreate(Activity.java:5231)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2265)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.ActivityThread.access$800(ActivityThread.java:145)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1206)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.os.Handler.dispatchMessage(Handler.java:102)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.os.Looper.loop(Looper.java:136)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at android.app.ActivityThread.main(ActivityThread.java:5114)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at java.lang.reflect.Method.invokeNative(Native Method)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at java.lang.reflect.Method.invoke(Method.java:515)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:607)
    03-20 18:59:20.540: E/AndroidRuntime(6649): at dalvik.system.NativeStart.main(Native Method)
    03-20 18:59:20.550: W/ActivityManager(444): Force finishing activity com.google.android.wearablepreview.app/com.google.android.clockwork.home.HomeActivity
    03-20 18:59:20.850: I/WindowManager(444): Screenshot max retries 4 of Token{41ea7450 ActivityRecord{41911c70 u0 com.google.android.wearablepreview.app/com.google.android.clockwork.home.HomeActivity t39 f}} appWin=Window{41c2ae30 u0 Starting com.google.android.wearablepreview.app} drawState=4
    03-20 18:59:20.850: I/ActivityManager(444): Clearing package preferred activities from com.google.android.wearablepreview.app

  • Tavishi

    Can we control the notification coming on the wear??