This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: call notifications, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest. - Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding, hands-free - Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future.

Meta M1

No idea yet, seems protocol is not documented!

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: call notifications, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest. - interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding, hands-free - hands-free
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future.future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Meta M1

No idea yet, seems protocol is not documented!

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: call notifications, caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding, hands-freeforwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white LCD e-paper smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains background daemon talking to the watch and daemon configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white e-paper smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains background D-Bus daemon talking to the watch and daemon configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white e-paper smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and daemon configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white e-paper smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white e-paper reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a propietary, proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED and LCD), -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), Voice Calls notification and control, Conversations notifications forwarding,Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support (SirenSong, QuasarMX), Set "silent" profile when watch is connected, Phone to Watch time synchronization, basic notification forwarding, rearranging watchfacesTransliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface
• Missing: caller id, media player controls, controls for native app, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization
• Missing: installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Voice Calls Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification and control, Conversations notifications forwarding,Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible forwarding, rearranging watchfaces
• Missing: caller id, media player support (SirenSong, QuasarMX), Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface
• Missing: media player controls for native app, controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronizationsynchronization, Voice Calls notification and control, Conversations notifications forwarding,Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support (SirenSong, QuasarMX), Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface
• Missing: media player controls for native app, widgets, installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, Voice Calls notification and control, Conversations notifications forwarding,Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support (SirenSong, QuasarMX), support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface
• Missing: media player controls for native app, widgets, installing Pebble programs, updating firmware, running JavaScript side of Pebble programs.programs, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, Voice Calls notification and control, Conversations notifications forwarding,Missed forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface
• Missing: installing interface, installing/removing Pebble programs, updating firmware, running JavaScript side of Pebble programs, programs.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, time synchronization, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs.programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during the this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX MotionXis a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts
• Missing: sending calls and quick replies, notification forwarding, calendar, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contactscontacts, sending/receiving calls (no mic), notifications
• Missing: sending calls and quick replies, notification forwarding, calendar, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating firmware, widgets.firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, sending/receiving calls (no mic), notifications
• Missing: quick replies, calendar, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a wiki I've been thinking about opening for sometime now. Basically, the goal is to document how to use several models of smartwatches with Sailfish, and whenever applications are required, to compare different applications if they appear.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support.
• Missing: updating support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, sending/receiving calls (no mic), notifications
• Missing: quick replies, calendar, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

This post is a In this wiki I've been thinking about opening for sometime now. Basically, the goal is to we document how to use several models of smartwatches with Sailfish, and Sailfish. In addition, whenever applications are required, to compare different applications if they appear.required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, calendar, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro.@javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016.2016. No idea about protocol, so not supported.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here . Again, no idea about protocol, so not supported.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a new "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but being a very popular watch there are some 3rd party protocol implementations around. a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is not yet public, as far as I know. However, it seems reasonable to assume it will be similar to classic Pebble.supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML. It is under active development.QML.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs
• Missing: updating firmware, running JavaScript side, background daemon

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

U8/ U80/ U8+

Connects well to Jolla - Calls, Contacts and Audio work however other notifications do not work as there is no way to allow access to them via Bluetooth, looking around for an app or patch that will enable this.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

U8/ U80/ U8+

Connects well to Jolla - Calls, Contacts and Audio work however other notifications do not work as there is no way to allow access to them via Bluetooth, looking around for an app or patch that will enable this.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs

Pebble Time

Pebble Time (& Time Steel) is a color reflective LCD smartwatch with a CortexM µC. Protocol is supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

U8/ U80/ U8+

Connects well to Jolla - Calls, Contacts and Audio work however other notifications do not work as there is no way to allow access to them via Bluetooth, looking around for an app or patch that will enable this.

Sony SmartWatch 2

Connects to Jolla Via Bluetooth (NFC Pairing does not work for obvious reasons); however SW2 Android app (installed via Jolla Android store) which is needed to connect to SW2 watch functions does not pick up the watch. The watch will confirm that it's connected to Jolla but the Android app on Jolla handset does not recognise the watch is connected so none of the features or notifications work.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.

In this wiki we document how to use several models of smartwatches with Sailfish. In addition, whenever applications are required to use a smartwatch, we document all the available applications.

Basically, if it doesn't appear in this list, it is likely your smartwatch won't work with Sailfish.

MetaWatch

This is Strata/Frame version; not the newer Meta M1 version. The older MetaWatch is a basic black&white reflective LCD smartwatch, with barebones hardware (MSP430 µC), documented protocol and partially open firmware. The watch can't run programs; smartphone programs are supposed to be able to push images to the watch, though. Basically, this is used to show some widgets. Battery life is around a week.

Salmeta is an in-progress program to connect your Jolla to the MetaWatch. Binaries are currently available only on javispedro's OBS repository. Salmeta only works with the latest MetaWatch firmware, and is under active but slow development.

• Working features: Basic connecting (Bluetooth Classic & Smart), time synchronization, basic notification forwarding, rearranging watchfaces
• Missing: caller id, media player controls, widgets

Pebble

The Pebble and the Pebble Steel both have the same internals, so they are both included in this list. The Pebble is a black&white reflective LCD smartwatch with a basic CortexM µC. The firmware is closed, the protocol is not documented, but a python communication library is officially supported. The Pebble can run programs on the watch itself, but many of them require a corresponding program running on the phone in order to perform useful work or connect to the Internet. Battery life is around a week.

Pebbled allows connecting the Pebble with a Jolla. Pebbled is available in OpenRepos. Package contains D-Bus daemon talking to the watch and configuration app in QML.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, Voice Calls notification and control, Conversations notifications forwarding, Missed calls notifications, New email notifications, Twitter and Mitakuuluu notifications, MPRIS compatible media player support, Set "silent" profile when watch is connected, Phone to Watch time synchronization, Transliterate strings to plain ASCII, daemon management app, "org.pebbled" DBus interface, installing/removing Pebble programs, running JavaScript side of Pebble programs, Pebble Appstore support, Updating firmware.

SkippingStones is a purely QML implementation of the Pebble protocol and corresponding application. It is available in OpenRepos. Being a purely QML program, you must keep it open in the background to connect to the watch.

• Working features: Connection (bluetooth classic), notification forwarding, caller id, music player control, time synchronization, installing Pebble programs

Pebble Time

Pebble Time (& Time Steel) is a color colour reflective LCD smartwatch with a CortexM µC. Protocol is supported by python library. Pebbled is working on adding Time compatibility.

Samsung Gear 1/2/S

The Samsung Gear series are color colour OLED smartwatches with high specs (e.g. Samsung Exynos SoC, up to 1GiB of RAM). Despite the fact that the Gear 1 uses Android, and the Gear 2 and S use Tizen, the same phone programs can handle all of them. Battery life is around 3 days.

The Gear uses a proprietary, encrypted protocol, but some progress has been made to connect to the watch. An example command-line daemon is able to connect to the watch, set the time, and forward notifications to it, from the Jolla. There is no user interface for it, but there could be one if there's enough interest.

• Working: basic connection (bluetooth classic), time synchronization, basic notification forwarding, phone call forwarding (hands-free)
• Missing: every other feature, user-friendliness

Qualcomm Toq

The Qualcomm Toq uses a always-on Mirasol color colour screen (generic name is IMOD), and a CortexM µC. It averages between 5-6 days of battery life.

It has closed firmware and undocumented protocol. However, most of the firmware is written in Lua, and the protocols used are based on JSON and OBEX; therefore, it seems easy to write programs for it. I have started writing a Sailfish program to connect to it, Saltoq. Currently it's very much a work in progress, if you're interested in using it it's best you contact @javispedro .

• Working: basic connection (bluetooth classic), time synchronization, recent messages, call log, music control, contacts, calendar, sending/receiving calls (no mic), notifications
• Missing: quick replies, weather, stocks, installing custom apps or watchfaces, updating firmware

Android Wear

No idea yet, undocumented protocol! Because many smartwatches seem to be based on Android Wear, it may be interested to tackle this protocol in the future. Generally, Android Wear smartwatches all have color colour touchscreens, but varying technologies (OLED -- Moto 360, LG Watch; reflective LCD -- Sony Smartwatch 3), and 1-2 day battery life.

webOS

At CES2015, LG and Audi displayed a smart watch running webOS, expected delivery at the beginning of 2016. No idea about protocol, so not supported.

MotionX

MotionX is a "open platform" for watchmakers to build smartwatch features into traditional watches, created by Swiss watchmakers. First watches expected in June 2015, with a total of more than ten watches during this year. Read more here. MotionX is currently used in wearables, such as Nike+ Running and Jawbone UP. Again, no idea about protocol, so not supported.

U8/ U80/ U8+

Connects well to Jolla - Calls, Contacts and Audio work however other notifications do not work as there is no way to allow access to them via Bluetooth, looking around for an app or patch that will enable this.

Sony SmartWatch 2

Connects to Jolla Via Bluetooth (NFC Pairing does not work for obvious reasons); however SW2 Android app (installed via Jolla Android store) which is needed to connect to SW2 watch functions does not pick up the watch. The watch will confirm that it's connected to Jolla but the Android app on Jolla handset does not recognise the watch is connected so none of the features or notifications work.

Other

• Meta M1: No idea yet, seems protocol is not documented!
• Liveview: No idea, albeit there were some programs for N900/N9.
• MBW150: Doesn't work on Jolla because of lack of Bluetooth DUN support.

Feel free to edit this Wiki to add whatever smartwatches you've tried, or comments, software or ideas.