[Deal] Woot selling ‘factory reconditioned’ LG G Watch for $69
Nervous about getting into Android Wear? That’s understandable with any platform that you’ve never invested in or tried. Now, though, is seemingly the time to get into Google’s wearable platform as one retailer has a launch device for less than $100.
On Woot, the LG G Watch is available for $69. While this is not for a brand new model, it is ‘factory reconditioned’ and Woot notes that this means the device is as close to being new as possible. Woot also offers a one-year protection plan for an additional $11.
Come comment on this article: [Deal] Woot selling ‘factory reconditioned’ LG G Watch for $69
How to develop a simple Android Wear app
Early last month, Alex Mullis wrote an excellent article discussing everything you need to know about developing for Android Wear. We are going to take this a step further by developing a simple Android Wear App. Developing for Android is an exciting endeavor, but including Android Wear features in your app is even more fun, trust me!
Before we begin, please keep the following at the back of your mind. Wearable apps, even though they are very similar to apps built for handhelds, should be quite small in size and functionality. You do not want to attempt to replicate the entire functionality of your handset app on a wearable. Rather, you should look for ways to complement the handheld app using the wearable. Ideally, most operations should be performed on the phone, and the results sent to the wearable.
Preparation
Our app will be a simple Android app, that sends a notification from a phone to a paired Wear device, with a corresponding wearable app, with a single clickable button.
For this article, we assume you are using Android Studio. Android Studio is the de-facto standard for Android app development. To develop apps for wearables, you need to update your SDK tools to version 23.0.0 or higher, and your SDK with Android 4.4W.2 or higher.
You should then set up either an Android Wear Device or an Android Wear Emulator.
For an emulator,
- Create an Android Wear square or round device using AVD Manager
- Start the emulator device
- Install the Android Wear app from Google Play
- Connect your handheld to your development machine through USB
- Forward the AVD communication port to the handheld device with the command
adb -d forward tcp:5601 tcp:5601
(this must be done every time you connect/reconnect your handset)
- Start the Android Wear app on your phone and connect to the emulator through the app settings.
For an Android Wear Device,
- Install the Android Wear app on your smartphone via the Google Play Store
- Pair your handset and wearable using the instructions in the app
- Enable developer options on your wear device (tap build number seven times in Settings > About)
- Enable adb debugging
- Connect your wearable to your development machine, and you should be able to install and debug apps directly to your wearable.
Create your Project
The complete source code for this tutorial is available on github, but you might want to create your own project to get a feel for the process. Android Studio provides wizards to help create a project, and they are the best way to setup your Android wearable project. Click File > New Project, and follow the instructions
The process is similar to creating a phone/tablet project. Simply make sure you select both “Phone and Tablet” and “Wear” in the “Form Factors” window.
When the wizard completes, Android Studio will have created a new project with two modules, mobile and wear. For each module, you can create activities, services, layouts and more. Remember, the smartphone app (mobile module) should do most of the work, like intensive processing and network communications, and then send a notification to the wearable.
“mobile” module
The mobile module is the same Android development you are used to. For our mobile module, we create a simple Activity, with an EditText field, and a Button. The text entered into the EditText gets sent to the Wear device as a notification, when the Button is tapped.
The layout is pretty straightforward:
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
android:paddingBottom="@dimen/activity_vertical_margin"
tools:context=".MainActivity"
android:orientation="vertical">
<EditText
android:id="@+id/editText"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginBottom="16dp"/>
<Button
android:id="@+id/actionButton"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
style="@style/Base.Widget.AppCompat.Button.Borderless"
android:text="@string/show_notification"
android:onClick="sendNotification" />
</LinearLayout>
The MainActivity is also pretty straightforward:
public class MainActivity extends AppCompatActivity
EditText editText;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
editText = (EditText) findViewById(R.id.editText);
public void sendNotification(View view)
String toSend = editText.getText().toString();
if(toSend.isEmpty())
toSend = "You sent an empty notification";
Notification notification = new NotificationCompat.Builder(getApplication())
.setSmallIcon(R.mipmap.ic_launcher)
.setContentTitle("AndroidAuthority")
.setContentText(toSend)
.extend(new NotificationCompat.WearableExtender().setHintShowBackgroundOnly(true))
.build();
NotificationManagerCompat notificationManager = NotificationManagerCompat.from(getApplication());
int notificationId = 1;
notificationManager.notify(notificationId, notification);
Notice that when building our Notification, we called the extend() method, providing a NotificationCompat.WearableExtender() object.
Running the mobile module
You run the mobile module the same way you run any other Android app. As long as you have it paired with a Wear device (emulator or real), running the project on your device will display notifications on your wearable.
“wear” module
At this point, you should be able to view notifications from your mobile device on your wear device. We, however, are not content with that, and are going to build and run an actual Wear app. Wear devices, generally have a far less screen estate than handhelds, and are usually round or rectangular. This brings it’s own set of layout challenges. True to type, Google has some excellent design guidelines and UI patterns for Android Wear developers. The Wearable UI Library is included in your project automatically when you use the Android Studio project wizard to create your wearable app. Confirm that it’s there, if not then add it to your wear build.gradle file:
dependencies compile 'com.google.android.support:wearable:+'
If you created your project using the Android Studio Project Wizard, you will have an activity setup already for you with two different layout files for Round and Rectangular wear devices. The activity_wear.xml file is shown below:
<?xml version="1.0" encoding="utf-8"?>
<android.support.wearable.view.WatchViewStub
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:id="@+id/watch_view_stub"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:roundLayout="@layout/round_activity_wear"
app:rectLayout="@layout/rect_activity_wear"
tools:context=".WearActivity"
tools:deviceIds="wear">
</android.support.wearable.view.WatchViewStub>
Take note of the base widget. It is a WatchViewStub, which is a part of the Wearable UI library. You must declare the “app:” XML Namespace xmlns:app=”http://schemas.android.com/apk/res-auto” because the Wearable UI widgets declare their attributes using the “app:” namespace.
Take special note of the app:roundLayout and app:rectLayout items. This specifies the layout file to load depending on the shape of the wearable screen. Nifty!
Both our round_activity_wear.xml and rect_activity_wear.xml files are quite similar, except for a few caveats. The widgets in round_activity_wear are centered vertically and horizontally, while for rect_activity, they are simply centered horizontally. Using WatchViewStub, you have the freedom to design your layout completely differently for round and rectangular screens.
round_activity_wear.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:layout_box="all"
tools:context=".WearActivity"
tools:deviceIds="wear_round">
<Button
android:id="@+id/button"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:text="@string/hello_round"
android:onClick="beginCountdown" />
<android.support.wearable.view.DelayedConfirmationView
android:id="@+id/delayedView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
app:circle_border_color="@color/green"
app:circle_border_width="20dp"
app:circle_color="@color/white"
app:circle_radius="60dp"
app:circle_radius_pressed="60dp"
app:circle_padding="16dp"
app:update_interval="100"/>
</FrameLayout>
rect_activity_wear.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical"
tools:context=".WearActivity"
tools:deviceIds="wear_square">
<Button
android:id="@+id/button"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"
android:text="@string/hello_square"
android:onClick="beginCountdown" />
<android.support.wearable.view.DelayedConfirmationView
android:id="@+id/delayedView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"
app:circle_border_color="@color/green"
app:circle_border_width="20dp"
app:circle_color="@color/white"
app:circle_radius="60dp"
app:circle_radius_pressed="60dp"
app:circle_padding="16dp"
app:update_interval="100"/>
</FrameLayout>
WearActivity extends android.app.Activity (note not AppCompatActivity), just like any normal Android smartphone or tablet Activity. We set an OnLayoutInflatedListener object on our WatchViewStub, which gets called after the WatchViewStub has determined if the wearable device is round or rectangle. You locate your widgets using findViewById() in the onLayoutInflated method of the OnLayoutInflatedListener. In our case, we instantiate the Button and DelayedConfirmationView, and then call showOnlyButton() to hide the DelayedConfirmationView and show only the Button.
public class WearActivity extends Activity
private Button button;
private DelayedConfirmationView delayedView;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_wear);
final WatchViewStub stub = (WatchViewStub) findViewById(R.id.watch_view_stub);
stub.setOnLayoutInflatedListener(new WatchViewStub.OnLayoutInflatedListener()
@Override
public void onLayoutInflated(WatchViewStub stub)
button = (Button) stub.findViewById(R.id.button);
delayedView = (DelayedConfirmationView) stub.findViewById(R.id.delayedView);
delayedView.setTotalTimeMs(3000);
showOnlyButton();
);
public void beginCountdown(View view)
button.setVisibility(View.GONE);
delayedView.setVisibility(View.VISIBLE);
delayedView.setListener(new DelayedConfirmationView.DelayedConfirmationListener()
@Override
public void onTimerFinished(View view)
showOnlyButton();
@Override
public void onTimerSelected(View view)
);
delayedView.start();
public void showOnlyButton()
button.setVisibility(View.VISIBLE);
delayedView.setVisibility(View.GONE);
Running the wear module
To run the wear module, select the wear run/debug configuration, and click the play button (or type Shift+F10). Since this is a debug build, you install directly to your wear device (or emulator). Make sure your device is connected (or a wear emulator is running) and select your device when prompted.
Deploying a release version
While you install your app directly unto a wearable during development, publishing and releasing an app for users is quite different. Your wearable app must be embedded in a handheld app, and it is automatically pushed onto wearables that are connected with the user’s handheld. Visit the Android Developer page on packaging wearable apps for more information on properly packaging your wearable app.
As usual, the complete code is available on github for use as you see fit. Happy coding.
Android Wear gets a YouTube app, complete with Chromecast support
Android Wear apps are growing pretty rapidly, and a new app has hit the Play Store that will let you watch YouTube videos right on your wrist. The app is appropriately called Video for Android Wear & YouTube and will stream YouTube videos right to your Android Wear smartwatch. I’m not sure I’d really enjoy watching anything on a tiny watch-sized screen, but hey, options are cool.
In addition to functioning as a YouTube player, the app has a few other tricks up its sleeve. You can cast videos directly from your watch with this, which I could definitely see coming in handy. Find the video you want using its voice-navigated search menus, then quickly cast the video up to your television without ever having to touch your phone. It would be like having a remote control that’s always on your wrist.
Other than that, the app also supports audio playback through Bluetooth-connected speakers. That’s especially important since most Android Wear watches don’t actually have speakers on them, so don’t expect to watch videos exclusively on your watch if you care about sound.
The app is free, and while it seems a bit like a novelty app, it might be worth checking out just to show off at parties.
via: Android Police
Come comment on this article: Android Wear gets a YouTube app, complete with Chromecast support
Video for Android Wear & YouTube app bringing videos to… your watch?

You know the world has gone nuts when people start watching videos on their smart watches. It’s simply not what Android Wear devices were made for, and it truly beats the purpose of a wearable, but it may have its benefits (which we can talk about later). The point is it’s now possible to enjoy your videos straight from your wrist, thanks to the new app Video for Android Wear & YouTube.
Video for Android Wear & YouTube allows smart watch owners to view YouTube videos on their tiny screens. After opening the app, one can simply perform a voice search to find any video. One is then presented with a plethora of results you can scroll through. Select one and you are ready to go! The video starts playing on your tiny screen and you are presented with options to pause, resume, seek and control volume.
Sound is an important part of a good video experience, right? We know most of you are wondering exactly how that works on the Video for Android Wear & YouTube app. Android Wear smart watches have no speakers! Thankfully, there is a solution to this. You can use any Bluetooth headphones or speaker to enjoy your clips to their fullest. These have to be connected directly to the watch, though, not the phone.
Still not satisfied? I mentioned an app like this may have its benefits, and that is what we are going to talk about now. Videos for Android Wear & YouTube (they seriously need a shorter name!) comes with full Chromecast support. This makes it unbelievably simple to watch YouTube videos on the large screen when your phone is not within reach, or when you are simply feeling too lazy to pull it out of your pocket.
#gallery-1
margin: auto;
#gallery-1 .gallery-item
float: left;
margin-top: 10px;
text-align: center;
width: 33%;
#gallery-1 img
border: 2px solid #cfcfcf;
#gallery-1 .gallery-caption
margin-left: 0;
/* see gallery_shortcode() in wp-includes/media.php */
Interested? You can head over to the Google Play Store to download the Video for Android Wear & YouTube (really?!). It is free to download, but offers in-app purchases. Developer appfour mentions it’s compatible with all Android Wear devices, so you shouldn’t have a problem. If it takes a while for the app to work, it’s because the Android Wear part of the app is larger than usual. Just give it some time.
Who is downloading? Is this really an app you see yourself using?
Moto 360 gets a price drop to just $150 from Motorola and Google

Motorola and various other retailers have constantly been discounting the Moto 360 to the low price of $150, likely because the second generation model isn’t too far off. In case you’re still interested in picking one up for a discounted price, you’ll be happy to hear that both Motorola and Google have dropped the price of the watch to just $149.99. We’re not exactly sure if this is the watch’s permanent price point from here on out, but if we had to guess, we’d say that it is.
If you choose to go through the Google Store, you can buy the Moto 360 in either Black or Stone Gray color options. If you choose to go through Motorola, however, you’ll be able to customize your watch with different colored bands and cases. Note that the metal bands are slightly more expensive, so keep that in mind before you place your order.
Related Videos
.rvs_wrapper
width: 350px;
.rvs_wrapper.align_left
float: left;
.rvs_wrapper.align_right
float: right;
.rvs_wrapper.align_center,
.rvs_wrapper.align_none
width: 100%;
.rvs_wrapper.align_center
text-align: center;
.rvs_wrapper.align_center.cbc-latest-videos ul li
float: none;
display: inline-block;
vertical-align: top;
.rvs_wrapper.cbc-latest-videos:not(.align_none) ul li:nth-child(2n+1)
clear: both;
.rvs_title
font-weight: 600 !important;
margin: 0 !important;
font-size: 24px !important;
.rvs_wrapper.align_right .rvs_title
padding-left: 20px;
.rvs_title a
font-family: ‘Roboto Condensed’;
color: #3a3a3a;
.rvs_wrapper.cbc-latest-videos ul
padding-top: 10px;
.rvs_wrapper.align_left.cbc-latest-videos ul li,
.rvs_wrapper.align_none.cbc-latest-videos ul li
padding: 0 15px 0 0;
.rvs_wrapper.align_right.cbc-latest-videos ul li
padding: 0 0 0 15px;
float: right;
.rvs_wrapper.align_center.cbc-latest-videos ul li
padding: 0 7px;
.rvs_wrapper.cbc-latest-videos ul li > a
font-weight: 400;
.rvs_wrapper.cbc-latest-videos ul li > a .yt-thumbnail
margin-bottom: 0;
@media only screen and (max-width : 480px)
.rvs_wrapper
width: 100%;
text-align: center;
body .rvs_wrapper.cbc-latest-videos ul li
padding: 0 7px;
display: inline-block;
float: none;
vertical-align: top;
So is the Moto 360 still worth it? Considering that the 2nd generation watch likely isn’t too far off, you might regret this purchase if the new model launches soon. No, it’s not the most powerful smartwatch on the market, but $150 isn’t much to spend on a device that may end up adding a ton of convenience to your everyday life.
Remember, the Moto 360 originally launched for $250 and stayed at that price point for some time. So if you’re in the market for an Android Wear device and would like to save a bit of money, the Moto 360 may be a decent option for you. If you’re interested, be sure to head to the links below for more information.
Moto 360 price drops permanently to $149 through Motorola and the Google Store
Moving forward, the Moto 360 will cost less from two of its sellers. Both Motorola and the Google Store have knocked the starting price of the smartwatch down to $149, a drop of $100 compared to the launch price. This, however, is not just a sale or temporary discount. The price of the Moto 360 through Motorola and the Google Store is permanently $149 to start.
This price drop could indicate that a successor to last year’s model is one the way. Based on Motorola’s current release cycle, the new Moto 360 should arrive in late August or early September. Until then, an Android Wear device at this price is quite the steal.
[Google Store] [Motorola]
Come comment on this article: Moto 360 price drops permanently to $149 through Motorola and the Google Store
Huawei’s Honor Band Zero is a circular smartwatch with a sleek design
Huawei took to Twitter, teasing a render of its upcoming wearable, the Honor Band Zero. There’s very little details on the watch, aside from what we can spot in the photo. The Chinese manufacturer has yet to launch the Huawei Watch, meaning the Honor Band Zero could be a long ways out. After all, this is merely a 3D render.
Based on the image, the Honor Band Zero will look similar to the Moto 360 and LG G Watch in some aspects, except without buttons. Considering that this is just a render of the wearable, it’s hardly worth speculating what the final product will look like. The one thing we do know and what was intended to get out of this render is that Huawei will be focusing on a sleek and minimalistic design, as mentioned on Twitter:
#Honor‘s smart wearable device that embodies a minamalistic design, that’s#HonorBandZero.#HuaweiFacts
Hopefully we’ll see more details soon. Anyone interested in the Honor Band Zero?
source: Huawei Device (Twitter)
Come comment on this article: Huawei’s Honor Band Zero is a circular smartwatch with a sleek design
5 tips to get more battery life out of your Android Wear smartwatch
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
Smartwatches are still a relatively new technology in the tech industry, and as many other new wireless technologies do, smartwatches are struggling with battery life. While manufacturers and other clever people work this out, we’re left to find out novel ways of saving battery life on our first generation smartwatches. So if you’re using an Android Wear smartwatch, here are 5 tips to get more battery life out of your Android Wear smartwatch.
1. Adjust the brightness on your display
On-screen time is the biggest killer of battery life on any smart device, be it a smartwatch, smartphone or any tablets. So it stands to reason that the brightness of your display is going to influence how much on-screen time you’re going to get. Some Android Wear smartwatches will have an ambient light sensor which gives you an ‘Auto’ setting, adjusting the brightness depending on the surrounding light situation – for the most part, this works well, however if you’re not getting the battery life you want, you can always just set it to the lowest brightness and see how you go.
For the smartwatches without ambient light sensors, you’ll again want to try and see how you survive on the lowest brightness setting, but the earlier Android Wear devices are known to struggle with readability in full sunlight on that setting.
2. Turn off always-on/ambient display
For some, a smartwatch that has a blank screen when not being used doesn’t make sense, which is where the always-on setting comes in. As its name suggests, it allows your watch face to be ‘always-on’ in a manner of speaking – rather than stay active in full colour, the watch face will become a black and white silhouette, letting you still see the watch face while the watch isn’t active.
Admittedly, this doesn’t use a huge amount of battery (at least compared to how much brightness affects it), however, if you’re scrounging for an hour or two of battery life to get through the day, you may want to ensure that this setting is set to ‘Off’.
3. Switch to no notifications
As I mentioned earlier, on-screen time is the real killer here, so any strategy for saving battery life needs to reduce the amount of time that the screen remains on. Android Wear devices have three notifications profiles: “All”, “Priority” and “None”. As the names suggest, “All” gives you all notifications, “Priority” really only lets phone calls come through, and “None” ignores all notifications.
Since “All” turns your screen on each time you get a notification, switching to the “None” profile will get you that little bit of battery life saving since your display isn’t turning on. This might not work for everyone since you will lose track of when and what notifications are coming through, but it does make a huge difference if you get lots of notifications on a daily basis.
4. Switch to Theatre Mode
This point is basically point 3 on steroids. If switching to the “None” profile still isn’t getting you enough battery juice, then you’ll have to get drastic. There is a mode on Android Wear devices called “Theatre Mode” – as the name suggests, it is designed for the times when you don’t want to be interrupted with a bright light on your wrist, including inadvertent touches of the display and bringing your arm up to see the time.
Turning “Theatre Mode” basically makes your smartwatch ignore all random touch input as well as gyro movements and you’ll only be able to wake it either using a physical button, or if your device doesn’t have this, a double tap of the display. This could give you a little more battery life if you’re the type of person who randomly touches the screen or (God forbid) likes to check the time a lot.
5. Switch to Airplane Mode
If point 4 is somehow not working for you, then this point is your ultimatum to your smartwatch. Like smartphones, Android Wear devices have an “Airplane Mode” which switches off all external communication like Bluetooth and Wi-Fi.
Of course, this means your Android Wear device is basically dead to the world around it and you’re not quite using it as a smartwatch, but you will definitely save on battery power. I’d recommend this as a way to save battery life at the end of the day, or on big nights out when you’re out past your normal bedtime.
And that’s my list. I hope some of you find this useful, and if you do, please leave me a comment down below and let me know if you want to more of these guides in future.
This post was originally published on WatchFaceADay.com where I am the founder.
The post 5 tips to get more battery life out of your Android Wear smartwatch appeared first on AndroidSPIN.
[Deal] Grab a Moto 360 for $149.99 from Woot
Earlier today, Woot kicked off a new deal on all three colorways of the Moto 360. Buying the smartwatch using this promo saves customers a whopping $100; so you now can pick one up for as little as $149.99. However, stock is extremely limited — so if you want to bag yourself one you better act fast.
You’ll find the links for each of the colorways below:
Will you be taking advantage of this offer? Let us know below!
Come comment on this article: [Deal] Grab a Moto 360 for $149.99 from Woot
Finally: Spotify now has Android Wear functionality
<ins class="adsbygoogle"
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
Apps with proper Android Wear functionality are far and few between at the moment, but thankfully, Spotify has finally joined those ranks. Spotify now has Android Wear functionality after an update was pushed out today, and it brings many requested functions to your wrist worn wearables. Along with the standard music player controls like skip track and volume controls, you’ll also be able to swipe and browse through your playlists as well as radio stations that you have saved to Your Music.
There are some quirks however: single tracks don’t seem to be able to be selected, and the Spotify app can’t be started from the watch itself – you’ll need to start it from your phone first before you can start interacting with it on your smartwatch. A few oversights, but we’re hoping they’ll be addressed in a future update. If you’re interested in checking out the update, it is available from the Play Store now:
What do you think about the new Spotify Android Wear update? Let us know your thoughts in the comments below.
Source: Phandroid
The post Finally: Spotify now has Android Wear functionality appeared first on AndroidSPIN.























