wear-os

问题 I'm working on a watch face and its up and running but when I put it on my 360 it becomes slow to respond to interactions. I should note that the screen wakes when a notification is received but not when one turns their wrist to look at the time. Last thing I did was move code out of doWork and into CountDownRunner. Below is my code: import android.app.Activity; import android.os.Bundle; import android.os.Handler; import android.text.format.Time; import android.support.wearable.view

问题 I created a very simple android wearable app for a watch that uses the accelerometer sensor. I have the watch connected to a mobile device over bluetooth. When a certain value is detected by the accelerometer, I'd like for the phone to sound an alarm. I'm quite new to Android Programming, but I've been trying to read the documentation. I was looking at the Notification documentation, but I can't seem to figure out which data layer functionality I need. What I am trying to accomplish seems

问题 I have some problem when connect android wear with phone. I use android wear emulator (arm) & Genymotion emulator; When I connect from wear to phone my google api client returns a SERVICE_VERSION_UPDATE_REQUIRED error; (First, I also check some question like: Android wear app can't connect to google api services but I think my case is different). Tl;dr use play service wearable 8.4 => connect wear emulator + real phone -> work as well; => connect wear emulator + phone emulator(phone is

问题 I ve developed Android Wear App also SDK is 4.4AW. After finished that applitacion I tested on new android wear SDK that is 5.0.1 Emulator AND motorola360(with 5.0.1) then I recived this errror (Show in the below) Message Sum: can't resolve host Detailed Message: Unable to resolve host "URL": No address associated with hostname The App works perfect on 4.4 android wear but failed on 5.0.1 (I used Android studio and there is no Error before execution , Successful Build, Crash on Emulator.) Im

问题 I want to detect the connected Android Wear device in my app. I found the solution here using NodeApi. But the documentation doesn't say anything about that is it specific to Android Wear or not: Exposes an API for to learn about local or connected Nodes. Node events are delivered to all applications on a device. What is a Node here? Is it any device that connected over bluetooth or specific Android Wear device connected over bluetooth? I want to detect if the device connected is Android Wear

问题 I have tried to upload new Android wear app to google play developer console and I've got the following message: Upload failed APKs that use the 'android.hardware.type.watch' feature must have minimum SDK version of at least 23, and this APK has 20. If you are embedding a watch APK inside a phone APK, the phone APK does not need to use the 'android.hardware.type.watch' feature. my app is configured to sdk 20. I need it to be available for android 5.1. my app is designed for wear only and not

问题 I have followed the answer here: https://stackoverflow.com/a/24607317/624869 But wasn't able to update my driver. I get the following error in Windows: I am on Windows 7. My Nexus 5 is recognized just fine by ADB. Also my SDK is updated completely, all the way to Android 4.4W. Any ideas what's going on here? Thanks from a frustrated hopeful Wear developer. 回答1: It turns out the answer to my question was given by this answer: https://stackoverflow.com/a/24716409/624869 I'll copy and paste in

问题 I would like to determine the distance between an Android phone (Nexus 5X) and an Android Wear device (Samsung Gear live) by means of the Bluetooth RSSI. I found solutions to use the Bluetooth function readRemoteRssi(); as in final Runnable runnable = new Runnable() { @Override public void run() { // TODO Auto-generated method stub mBluetoothLeService.readRemoteRssi(); mHandler.postDelayed(this, 1000); } }; However, when using Android Wear, it is not necessary to use Bluetooth managers,

问题 I am trying to find the difference between having the WearableListenerService sticky or not sticky. This is because of the nature of the WearableListenerService that it does not run constantly. So is there any advantages of having it Sticky or not sticky? According to my testing, in both cases the behaviour of the service is the same. Service is created when phone reboots or when app launches. Even when it is not sticky, the wear is capable of connecting at any time, etc. Thanks! 回答1: In most

问题 In my app, I want to use the MessageAPI to communicate between my phone and my wear device. To send data, I use DataMap: Sending a message from my phone: MessageApi.SendMessageResult result = Wearable.MessageApi.sendMessage( googleApiClient, nodes.get(0), SharedConstants.Paths.PATH_WEAR_NOTIFICATION, dataMap.toByteArray()).await(); Reading the message on the wear device (WearableListenerService, onMessageReceived()): byte[] data = messageEvent.getData(); DataMap dataMap = DataMap