GAC – Tizen Client for Google Authenticator

GAC is a Tizen Application for Gear wearable devices. It has been tested and can run on Gear, Gear 2, Neo, Gear S, Gear S2 and Gear S3 devices.

It can be installed on any of the devices above through Gear App available for Android and iOS smartphones.

A user would need to obtain a Google’s 2-step verification code before she can use the application.

Detailed instructions about how you can get the Google’s code could be found here. After receiving the code a user can either enter it directly to the device if it has a proper keyboard (Gear S, Gear S2) or create a gac-codes text files and import it to the device using “Init from File” menu as described in this link.

On Gear S2 you can toggle accounts while on an account page by rotating a bezel:

gac

Here how adding a new code screen looks like on a Gear S device:

auth-screen4

Application’s menu allows selecting either an account or another menu item such as “Init from File” or “New Account’:

gac-menu

Help pages are always available on either Gear device to improve a user’s experience. This is how the look like on Gear S:

gac-square-menu

 

7 thoughts on “GAC – Tizen Client for Google Authenticator

    • It is. Go to “Gear->Galaxy Apps” and search for “Client for Google Authenticator”. It’s available for many Gear models: Gear 2, Gear 2 Neo, Gear S, Gear S2, and Gear S3. What is your model?
      Finding GAC in Gear App

    • @ruky – what I’ve posted is a screenshot of a Gear app on my Android (Galaxy 6) device:
      1. Install the Gear app on your mobile device
      2. Make sure that your Gear device is connected to your mobile device
      3. Open Gear app and select “Galaxy Apps”
      4. Search “Client for Google Authenticator”
      5. Install it on your Gear device

      What Gear model do you have?

  1. Done,
    It works like a charm.
    However, I have to mention that the configuration is kindda tricky, even more adding the changes to the google interface. But it works

    • I know, config is tricky, but using MP3 approach should not be that bad. I wish Google to release an interface for getting a shared secret directly from the mobile app, but they don’t have any incentives to do that.

      Thanks for using.

Leave a Reply

Your email address will not be published. Required fields are marked *