![\"Watch\"](\"./images/trtlwear.jpeg\")
Making a wearOS watch face and avoiding some of the faff. (TurtleWare 2.0 pt2)
\n\nThis is part 2 of a 3 part blog post about making v2 of turtle wear watch face. You can check out part 1 here
\n
Starting off, WearOS is the same as Android for 99% of things. Meaning you can write the app Kotlin (or Java if you love some boilerplate) and use all the same Android libraries. So for folder structures and initializing the project can be done in Android Studio just like you would a phone app. For Turtle Wear 2.0, there are two important entry points. The CanvasWatchFaceService and the MainActivity.
\nThe CanvasWatchFaceService is the place where you run all the watch face visuals. You set an inner class that contains a CanvasWatchFaceService.Engine() which deals with refresh speeds, ambient and active visuals, and custom tap commands. The CanvasWatchFaceService is pretty standard and should look something like the below:
\nclass TurtleFace : CanvasWatchFaceService() {\n\n var specW: Int = 0\n var specH: Int = 0\n private val displaySize = Point()\n\n companion object {\n private const val INTERACTIVE_UPDATE_RATE_MS = 1000\n private const val MSG_UPDATE_TIME = 0\n }\n\n override fun onCreateEngine(): Engine {\n return Engine()\n }\n\n private class EngineHandler(reference: Engine) : Handler() {\n private val mWeakReference: WeakReference<Engine> = WeakReference(reference)\n\n override fun handleMessage(msg: Message) {\n val engine = mWeakReference.get()\n if (engine != null) {\n when (msg.what) {\n MSG_UPDATE_TIME -> engine.handleUpdateTimeMessage()\n }\n }\n }\n }The inner class Engine has a lot more moving parts, but some bits to consider are:
\nThis should be familiar to anyone who has made an Android app, this is where your android.intent.action.MAIN and android.intent.category.LAUNCHER is set to on the manifest. In this case, it will be the launch point for the settings app.
\n![\"Simulator\"](\"./images/simulator.jpeg\")
There are a few catches with working on wearOS apps when it comes to debugging, especially with a watch face. The first being the standard configuration. This will always finish building with the settings app open, which if you are working on watch face changes is a bit annoying. It’s better to have this as the configuration settings.
\n![\"configSettings\"](\"./images/wearconfig.jpeg\")
This way the app will build but nothing will change on the device or simulator. Next is setting up devices to debug the build on. There are two options here:
\nOpen up the Android Virtual Device Manager for this and select “create a new virtual device” at the bottom. Choose WearOS as your hardware, Select Pie as the system image but don’t select the Chinese version unless you specifically want that, everything else is fine on default so you can click finish.
\nFor this method, you should have an Android phone or tablet connected to your workstation already. Make sure it’s got developer settings enabled and has allowed your workstation access. You also need the Wear OS app installed on that device and Bluetooth connected to the wearable.
\nOpen the WearOS app on the Android device and scroll to the bottom where advanced settings are, at the bottom here is “Debugging over Bluetooth”. Turn that on and you should get “Host: Disconnected Target: Connected”. Once that’s done go into terminal and enter the following commands:
\nadb forward tcp:4444 localabstract:/adb-hub\nadb connect 127.0.0.1:4444Now your wearable should be fully connected and ready to debug
\n![\"Manifest\"](\"./images/manifest.jpeg\")
When making a wearable app and specifically a watch face, there are some permissions you need to have set in the manifest. They are:
\n<uses-feature android:name=\"android.hardware.type.watch\" /><uses-permission android:name=\"android.permission.WAKE_LOCK\" /><uses-permission \nandroid:name=\"com.google.android.wearable.permission.RECEIVE_COMPLICATION_DATA\"\n/>Another set most apps will likely need is internet access, you will likely also need Bluetooth access as part of this if you want to communicate with the connected device.
\n<uses-permission android:name=\"android.permission.INTERNET\" />\n<uses-permission android:name=\"android.permission.BLUETOOTH\" />\n<uses-permission android:name=\"android.permission.ACCESS_NETWORK_STATE\" />\n<uses-permission android:name=\"android.permission.FOREGROUND_SERVICE\" />Slightly less important is location services, Turtle wear needs this information to get weather data for your location.
\n<uses-permission android:name=\"android.permission.ACCESS_COARSE_LOCATION\" />\n<uses-permission android:name=\"android.permission.ACCESS_FINE_LOCATION\" />For the CanvasWatchFaceService, it need to be declared specifically as a watch face. So we start by flagging it as a service and giving it the Bind Wallpaper permission.
\n<service\nandroid:name=\".watchface\"\nandroid:label=\"@string/my_name\"\nandroid:permission=\"android.permission.BIND_WALLPAPER\">Next, we set up the metadata for the watch face and what the watch face example screen looks like on a square and circular screen type. The examples are used when the user selects the watch face from the selection screen.
\n<meta-data\nandroid:name=\"android.service.wallpaper\"\nandroid:resource=\"@xml/watch_face\" />\n<meta-data\nandroid:name=\"com.google.android.wearable.watchface.preview\"\nandroid:resource=\"@drawable/preview_digital\" />\n<meta-data\nandroid:name=\"com.google.android.wearable.watchface.preview_circular\"\nandroid:resource=\"@drawable/preview_digital_circular\" />The last part is identifying it as a watch face.
\n<intent-filter>\n<action android:name=\"android.service.wallpaper.WallpaperService\" />\n<category \nandroid:name=\"com.google.android.wearable.watchface.category.WATCH_FACE\" \n/>\n</intent-filter>\n</service>The main activity manifest setup is thankfully very default android.
\n<activity\nandroid:label=\"@string/app_name\"\nandroid:name=\".MainActivity\">\n<intent-filter>\n<action android:name=\"android.intent.action.MAIN\"/>\n<action android:name=\"android.intent.action.VIEW\"/>\n<category android:name=\"android.intent.category.LAUNCHER\"/>\n</intent-filter>\n</activity>Without this inside the application area of the manifest, you will not be able to make any API calls out from the phone on newer devices. The error messaging on this is vague so it took ages for me to find this.
\nandroid:usesCleartextTraffic=\"true”![\"Watch\"](\"./images/watchface.jpeg\")
If you check most places for how to draw the watch face, you will generally see very large OnDraw functions that require canvas drawing. I instead prefer to use xml layouts in the same way you would with an android application. This is a little less efficient but a lot more readable code in my opinion. To set this up first have a lateinit View outside the engine. Then on the OnCreate you inflate it like this:
\nval inflater: LayoutInflater = \ngetSystemService(Context.LAYOUT_INFLATER_SERVICE) as LayoutInflater\nwatchLayout = inflater.inflate(R.layout.watchface, null)With the view now inflated, you can set it up with the screen dimensions on the OnDraw like below.
\nwatchLayout.measure(specW, specH)\nwatchLayout.layout(0, 0, watchLayout.measuredWidth, watchLayout.measuredHeight)\ncanvas.save()\ncanvas.translate(mXOffset, mYOffset - 40)\nwatchLayout.draw(canvas)\ncanvas.restore()With that done, you now call any element you need to update wherever you need. For example, this is called on the OnDraw elsewhere for showing the current time.
\nprivate fun setTimeandDate() {\n val now = System.currentTimeMillis()\n mCalendar.timeInMillis = now\n val date: TextView = watchLayout.findViewById(R.id.date_number)\n date.text = String.format(\"%02d/%02d\", \n mCalendar.get(Calendar.DAY_OF_MONTH), \n mCalendar.get(Calendar.MONTH) + 1)\n val hour: TextView = watchLayout.findViewById(R.id.hourtime)\n hour.text = String.format(\"%02d\", mCalendar.get(Calendar.HOUR_OF_DAY))\n val min: TextView = watchLayout.findViewById(R.id.mintime)\n min.text = String.format(\"%02d\", mCalendar.get(Calendar.MINUTE))\n }![\"Launch\"](\"./images/launch.jpeg\")
That’s mostly in terms of the tricky bits of getting the Turtle wear v2 up and running. The Google play store takes submissions to it just the same as it would an Android app.
\n