[General Questions and Answers] Droidriven:
You can try downloading the app on PC then decompile the apk using APKtool, then extract the watch faces you want then see if there is a setting on the watch that allows you to use other downloaded/installed watch faces. If so, if you can get the watch face moved over to the watch somehow then select it as your active watch face.

---------- Post added at 09:43 PM ---------- Previous post was at 09:34 PM ----------

I don't think you understand how android is partitioned, the purposes the partitions serve or what gets installed/stored/read/written to/from which partition and when.

The storage problem with your device is that you have a limited data partition, this is where user apps are installed, that is why you can't install very many apps. Along with a limited data partition, you have a limited amount of internal storage(user space or /data/media partition), this is probably why the "move" action fails.

Removing system apps does not give you more space to install more user apps because removing system apps only gives you more empty space in the system partition, this empty space doesn't get used by the data partition to install more user apps, it just remains empty to be used by the system when/if the system ever needs it.

You probably can't move the app to sdcard because you need enough empty space to "cache" the data that is being moved before it is actually moved to the new location. I could be wrong about that being your specific cause to your issue, but, it is one thing that can be the cause of the kind of issue that you are having.

The way it works is:

1) you select the file to be moved.

2) when you execute the move, it doesn't just "pick it up" here then "put it down" there, it first has to read the data being moved, as it is reading that data, it is also writing that data to a type of cache, when the complete file has been read from it's original location then written to cache, bit for bit, it then starts the process of reading from cache and writing to the new location.

So, it "picks it up" from your data partition, then "puts it down" in "cache" as it is being read from data partition, then, when the whole thing has been moved to cache, it "picks it up" again from cache then "puts it down" again in the new location that it is being moved to.

In other words, you need enough "extra" empty space in your internal storage to accommodate the cached data as it is being moved to external storage. If you don't have enough space to "cache" the data being moved, the process fails.

The same rule applies when you are extracting or compressing large files also. A 2GB file actually requires 6GB of space in order store and extract or compress the 2GB of data. 2GB to physically store the data prior to extraction/compression, 2GB to cache the data as it is being extracted/compressed and 2GB to physically store the extracted/compressed data after it has been extracted/compressed(the cached data gets dumped or more or less actually IS the data that gets written to the new location). I hope that made sense.

One more thing, and this is VERY IMPORTANT, it isn't a good idea to push the limits of your storage. Here are a few reasons why it is a good idea to leave a reasonably functional amount of empty space in data partition(where user apps are installed and in user storage(aka internal storage, aka /data/media partition).

1) if your storage becomes too full, the device can become soft-bricked and won't boot due to not having enough space to cache data as the device is booting. The device has to be wiped and/or flashed in order to solve this issue.

2) your device has a cache partition, but it doesn't always use the cache partition to cache data. Some data gets temporarily cached to internal storage during some user initiated actions, if you don't have enough space to temporarily cache data, some user actions don't work.

3) it also makes the device a little slower and makes it work a little harder, especially when multi tasking, it has to use/dump/re-use its limited storage/cache resources to keep up with everything that is running in the background and the things you are using in the foreground.

Leaving enough empty space to give you a comfortable storage "buffer" is always a good idea. It is good to leave at least 5-10% of your storage space empty.