Since I'd been having a lot of trouble getting this working, and I assume others will as well, the issue with the 10 second press to reset is the device it's currently paired to cannot be connected to it.

In my case, I have Flic buttons paired with Raspberry Pi devices. To unpair it, I had to turn off the service that was listening for Flic button presses. Once I did that, the button lit up red when clicked. This is the indication I needed so I could reset it. At that point, I was able to pair it to another device the same way as a fresh button.

It looks like this functionality has been added based on my latest use of the Android app.

If you look under the battery you find the serial number. If it starts with AA you have a too old button (our first batch).

What exactly do you mean with "force quit"?

@baobei Thanks. I got reply from flic team and it was replaced with new flic button. New button working perfectly.

My observation is, it can work with one app at a time. To make it work with other app, it require to forget from previous app. And couldn't find any method in SDK which can identify with which app it is workable currently.

You could for example send an Intent to your activity. If it does not exist (due to inactivity) it will then be recreated.

Sorry for late reply. We are currently not considering any other release channel than Google Play due to low demand. If you don't rely on 3rd party apk sites you can probably install the app on a Google Play-enabled device and extract the apk from it.

Hi, I am having the same problem running applescripts. The Shebang is present and on the first line. The script runs outside of HaxWithFlic just fine but I get the Shebang error when using the flic.
Does anyone know how to fix this?

W

@mircea.barba
Did you managed the problem?
I really cant understand why there is no Swift Tutorial...

Any updates? Three months passed...

Example of how to publish artifact to jCenter - https://github.com/OleksandrKucherenko/binding-tc/blob/master/binder/build.gradle

Look into [ ARTIFACTS ] section of file.

Not even for development in android emulator? Even from command line would be good enough.

Our current solution is that 3rd party apps depend on the Flic app to deliver the button events (easiest is through intents). There are multiple reasons for that:

We can provide a small simple open source library that is easy to integrate. The 3rd party app does not need to run a service in foreground mode (BLE connection apps need that in order to not be terminated while in the background). It simplifies when multiple apps wants to use the same button. Most important, the Flic doesn't need to have a pairing to each app (and force the user to run the pairing process). If we find and fix bugs or do improvements in our BLE code those fixes can be rolled out directly so that each 3rd party app doesn't have to upgrade their Flic SDK version.

@yuvalshu No, the 500 ms delay can not be changed. If you want something else then you would have to implement your own logic to distinguish between click/doubleClick/hold using the raw down/up events.

Yees, this was it.

Now I can see the icon for my button in the app. I was wondering why there was so much white space above the button label.

Thanks for your support.

Markus