On occasions I develop for the Gear S2/S3 watches from Samsung. (From a development perspective these watches are nearly identical, so I will collectively refer to them as the Gear S watches). When returning to develop after a period away from them there are a few mistakes that I find I sometimes make. Looking in some support forums I see there are others that make these mistakes too. To both help out others that run into this (and as a note to myself) I've made this post to cover some of the checks necessary.
- Ensure Debugging is Enabled
- Ensure Wifi is Always Enabled
- Check the watch's IP address
- Ensure the watch is unlocked
- Connect to the watch from SDB
- Redeploy the development certificate
Ensure Debugging is Enabled
Before anything else will work debugging must be enabled on the watch. This setting will be cleared if you've done a hard reset on the watch or if you have connected it to a different phone. You can change the setting by navigating to Settings ➜ Gear Info ➜ Debugging and ensure that the setting is checked.
Ensure WiFi is always enabled
You'll want to have WiFi set to always on. If you have it set to "Auto" you might not be able to connect. If it is set to "Off" then you will invariably will not be able to connect. Setting WiFi to "Always On" will cause the battery to drain excessively. When developing you'll want to have the charging cradle close by. To set WiFi to always be on navigate to Settings ➜ Connections ➜ WiFi ➜WiFi and select "Always On."
Check the Watch's IP Address
You need to know the watch's IP address to attach to it for debugging and deployment. Remember that the IP address will be different if you go to a different wireless network or could be different if you reconnect to the same network. To see the watch's IP address navigate to Settings ➜ Connections ➜ Wi-Fi ➜ Wi-Fi networks ➜ select your network ➜ scroll down to the IP address.
Ensure the Watch is Unlocked
The watch must be unlocked for the initial connection. While this may be obvious what is less obvious is how quickly the watch can become locked again. The heart rate monitor on the back of the watch also acts as a presence detection sensor; the watch is aware of when it's been removed from your wrist and will go into a locked state almost immediately if you have a lock code/patter on it. When handling the watch if your finger passes over this sensor the watch may lock. You could unlock the watch, set it down in the cradle, and it could be locked again because of your finger coming close to the sensor.
Heart Rate Monitor on the back of the Gear S2
Connect to the Watch using SDB
Before opening Tizen Studioconnect to the watch using SDB. From the command line on your computer (or Terminal if you are on a Mac) navigate to the folder that contains Tizen Studio and then into the tools folder inside of it. Type the following substituting your own IP address here.
sdb connect 192.168.1.181
If this is the first time the watch has connected to the machine from which you are typing the command the watch will prompt you to accept an RSA key. If you don't accept it the connection attempt will fail. Sometimes when you attempt to connect the command line tool will print a failure message the first time even though it has actually connected. Run the command a second time and you'll get a message that the watch is already connected.
Redeploy your Development Certificate
You only need to do this if the watch has been reset since the last time you've done development on it (or if you've never developed on the watch before). Certificate management is a topic of it's own; I won't go into it here. Provided that you have a handle on development certificates the above should be enough to get your watch connected to your computer for development.
I've had the original Galaxy Gear since last year. When it was first released it used Android as it's operating system (And not Android Wear, that wasn't available at the time). Earlier this year Samsung decided to make Tizen the main operating system of it's watches. Tizen is an operating system derived from Samsung's Bada and some other efforts that Intel and others had underway.
The current climate in which it is being released is interesting. Google has released Android TV as their solution for the living room. Samsung and Apple have both released car solutions. Some televisions already suuort a series of applications for connecting to services, and the most dominant mobile operating systems are Android and iOS. In this environment Samsung is releasing an operating system to compete for market share across all of these fronts; the living room, car infotainment systems, portable mobile devices, set-top boxes, and more are the target device types that Tizen is aimed for. I might be pessimistic were it another company releasing a new operating system but I'm expecting better outcome from Samsung.
This week Samsung is releasing the Galaxy Gear S in the USA. This is the first Tizen devices with data connectivity. A few days later from the 11-13 November at the Moscone Conference Center (San Francisco) Samsung is hosting a developers conference covering Tizen and development for the Watch and the Tizen powered Televisions (among other topics, such as the SmartThings platform). I plan to be there. I've already started to look into Tizen and made my first Hello World program of types. The details of it can be viewed over at The Code Project.
From working with this first project and seeing the number of web standards that the HTML side of the development story is based on I can see it seems to be an easy platform to jump into. Those that have already been doing mobile application development with HTML will be able to start development with little effort compared to starting other platforms. Getting started is easy. Though some amount of additional effort will be needed when thinking of how tasks are divided between a phone application and a watch application; applications on the Gear S can run independently of the phone or in conjunction with an application on the phone.
bada is Samsun's operating system for lower priced phones (note: the lowercase 'b' is not a type, it is always spelled in lower case). I had interest in an earlier version of bada but there was one thing that kept me away; the SDK did not have support for 64-bit computers. You could run it on 64-bit computers but it would creash frequently and behave in odd ways. Version 2.0 of bada was recently release and one of the new features the SDK has is that it will work on 64-bit computers. I am downloading the SDK now and hope to get started with it soon.
You can find more information and the SDK download from bada.com.
Yesterday the popular misconception of the day was that Samsung was planning to drop Windows Mobile. This rumor was fueled by the announcement that Samsung was going to release a new platform that it has developed called "Bada." Seems that the blog-o-sphere took this announcement to mean that Samsung's WM lineup would be replaced with Bada based phones. DigiTimes is reporting that Don Joo Lee has stated that "Samsung Electronics will continue to adopt Windows Mobile- and Android-based platforms for new smartphones launched in 2010, but will quit Symbian and adopt in-house developed open operating system Samsung Bada." Now that this has been straightened up, on to other things.
Found via WMPowerUser.com
I was checking to see if there were any updates on the Samsung Mobile Innovator's Site (http://innovator.samsungmobile.com) and saw something new. On the landing page there was a new addition added to the platform links called "Bada." What is Bada? That's what I wanted to know. Well on the site there was a link titled "What's Bada" so I clicked on it to see what it had to say.
Purpose of bada
More and more people want rich and connected application-experiences that are currently available only for smartphone consumers. Samsung has developed bada to make these exclusive smartphone experiences available to everyone.
Key features of bada
Samsung design principles aim to deliver simple, intuitive, and innovative user experiences through innovative visual design. Samsung bada includes a next generation UI framework with feature sets and design elements that facilitate leading-edge user interfaces for every bada application.
Consumer demand for service-based applications is growing. Samsung bada includes integrated support for service-oriented features to enable the development of connected applications. Samsung bada developers can implement various service features in applications without the high learning curve required by previous platforms.
Samsung bada encourages the integration of common experiences and functions across application. Extensible core functions include a dialer, messaging, and address book, which applications can freely use.
I've not dug through the site yet but this is something that I'll be keeping my eye on to see how it developes.
In keeping their SDK up to date with their phones Samsung has updated it's Windows Mobile SDK to version 1.2. In addition to the features that the previous SDK had this new SDK adds access to the FM Radio and the front facing camera! The new phones added to the SDK compatibility list include the GT-C6625 Valencia, SCH-m490/m495 T*Omnia, and GT-I8000 Omnia II.
From Samsung's announcement:
The Samsung Windows Mobile SDK offers APIs to use advanced features unique to Samsung phones. You might already have experience using advanced capabilities featured in the Windows Mobile APIs, like GPS, Bluetooth, or multimedia support. In addition to the Microsoft Windows Mobile APIs, you can use Samsung APIs to access phone features such as the accelerometer, notification LEDs, and haptics feedback.
Version 1.2.0 of the SDK includes new APIs for FM Radio and dual camera functionality. It also includes support for three new phones: the GT-C6625 Valencia, SCH-m490/m495 T*Omnia, and GT-I8000 Omnia II.
For more information on the SDK visit http://innovator.samsungmobile.com/down/cnts/toolSDK.detail.view.do?platformId=2&cntsId=4604
Found via twitter, @MobileInnovator
WMExperts.com picked up a little rumor by way of Mobili Linija about a phone they say is designated i8000 and they say it is the next Omnia. Of course this is just a rumor so nothing to confirm yet, but this will be exciting if true.
- Windows Mobile 6.1
- Quad-band EDGE, 2100MHz HSDPA.
- 3.7-inch AMOLED touchscreen (!) at 480x800 pixels
- Qualcomm MSM6290 processor
- Bluetooth 2.0
- WiFi b/g
- 1500mAh battery
- MicroSD card
- 8.1MP camera with flash, VGA video at 30fps.