Support Wear 2.0

[xxv]

Wear 2.0 is out; migrate the watch face to Wear 2.0 and make sure it is compatible with older devices too.

[Snowflake6]

Just received a new Android Wear 2.0 watch and installed the watchface. It works great in every way except one... The watchface is about 15% smaller than the screen.... :) Is there an easy way to make it scale?

[keithzg]

I recently bought an LG G Watch Urbane to try AsteroidOS on, but then discovered my favourite widget was available for Android Wear, so after some hemming and hawing I decided to keep the used G Watch Urbane for AsteroidOS tinkering and buy a Fossil Q Explorist. It just arrived today, and I've noticed the same thing, the watchface is significantly smaller than the screen is.

I'm a lot better at Qt/QML than I am at Android development (hence my interest in AsteroidOS!) but I'm not entirely a stranger to Android development, so in the grand Free Software tradition of scratching one's own itch I'm going to take a stab at trying to fix this :)

[xxv]

Thanks! I haven't had the free cycles for this project in a while. Looking forward to your PR 🙂

[keithzg]

Okay, it has been a while since I did any Android development, so I have to admit I was surprised anew by just how damned complicated and fragile Gradle is! I've basically spent 99% of my time fighting with it and 1% of my time trying to actually figure out how to upgrade to Wear 2.0 (which is a process that doesn't seem to have any straightforward or comprehensive documentation anywhere?) and fix the sizing. In the end, I do think I fixed the sizing! I just can't get the damned thing to build again after trying to back out my other changes, since I just inevitably descend down Gradle dependency hell, so I'm not ready to create a PR yet . . .

The trick, though, turns out to just be as simple as tossing the contents of the nodpi-drawable folder into the hdpi-drawable folder, at least for my watch. The clue was in @Snowflake6's description of it being "about 15% smaller", which on my Q Explorist isn't true---it's actually drawing significantly smaller than that, in fact it looks so similar to if it was using the BoxInsetLayout that I wasted some time pursuing that until I remembered the ~15% comment, and that made me certain the problem must be in the DPI somehow rather than purely in Wear 2.0.

Anyways, I'm going to continue doing battle with the needlessly hostile side of Android development, and hopefully I'll have something soon! Hell, hopefully I can get it to build again at all; I tried just setting it up again from scratch but I'm currently stuck on

Manifest merger failed : Attribute meta-data#android.support.VERSION@value value=(26.0.2) from [com.android.support:percent:26.0.2] AndroidManifest.xml:25:13-35
	is also present at [com.android.support:support-v4:26.1.0] AndroidManifest.xml:28:13-35 value=(26.1.0).
	Suggestion: add 'tools:replace="android:value"' to <meta-data> element at AndroidManifest.xml:23:9-25:38 to override.

which is fairly baffling since nowhere is either of those versions defined, so presumably something is pulling them in and they're ending up in the autogenerated manifest. It sure isn't clear to me!

As a result of this all though I ended up pulling out my old G Watch Urbane, and being reminded of how great this watchface looks has bolstered my determination . . .

[RobertWarrenGilmore]

Any update on this?

[xxv]

I haven't touched this code since before I put up this ticket so I can't say I have anything new to share. Maybe other folks on this thread have more info!

[Snowflake6]

Not I, i'm afraid. I started trying to re-code it to be DPI independent (as @keithzg pointed out, it's because of the change in screen resolution, I went from a 240 pixel screen to a 320 or 360, I think). I kept getting build errors as well, and eventually my spare time to work on it ran out.

I've since moved to the Garmin ecosystem... My Vivoactive 4 measures uptime in days, not hours, compared to every Android-based watch i've owned.

[rhysperry111]

Just thought I'd leave a comment here to see if anyone's made any progress so far. This is by far the most beautiful watch face I've seen, and surprisingly practical too.