I have the older version 2.0.15 installed on some other Pads and it works perfectly, are there by any chance that I can find the 2.0.15 apk or can you( @Emil ) give that version to me?

Hi,
I'm trying to pair a new set of two flic buttons with my Samsung Galaxy View (running Android 5.1) with the latest version of the Flic-app and the pairing process goes fine and it recognizes the button presses. However when trying to set the single press option for a button the screen starts the animation to open the 7 different categories but some error is generated and the app goes back to the button screen with the Single-, double- and hold options. This happens over and over. This is a deal-breaker for me since I need to set the single option to Sent intent (this only to block the other two press options so they are not recognized after I fetch the buttons in the Flic grabber from the SDK).

Any suggestion to get the single click option chosen again (worked before) or other way around to blick the other two press options for the button once it has been grabbed and in active mode?

@Emil do you have some ideas that could help me?

@tobi-fp Hi, sorry i cannot. The steps below however should help you somewhat to implement it yourself!

@Emil @anton you got any intel on this? Does every device need a separate account and the credentials some how stored in the device for the initiation. Just the credentials (in the SDK) is problematic to make a general build process with separate credentials for each device. Any suggestions?

The current android application uses the Unity game engine and the Flic SDK for button integration.

As I understand as off today the Flic app requires the user to login using a Flic account in order to use the Flic button functionality.
I'm now contacting you guys to ask whether or not it is possible to use the Flic app (mainly the Flic chooser) without having to login. This since if I login with the same account on two different devices the paired buttons for device #1 will be seen in device #2's marked as inactive and paired with device #1.

One solution to solve the discovery of other buttons is to create a unique account for every device, however I wonder shy isn't it possible to use the Flic buttons in some sort of Offline mode, why do you have to use some sort of identification key/credentials together with the app and the SDK?

@Emil Hi,
Thanks for the update and I have now further investigated the changes and the 300 ms input lag is gone in active mode as suspected. Very appreciated! The reaction times are now more or less correct when compared to other applications. Maybe still a little slower in measuring reaction times using these buttons together with the Unity Engine. It's however hard to say where the bottleneck is, if it is in the button detecting and sending the presses to the Android OS, or in Unity Engine detecting the press events etc.

Thank you for the feedback provided in this tread.

Have a nice day!

Hi again @Emil and @anton,

I've semi-solved the problem by using an external activity, much like the demo one to connect the Flic buttons to it and simbly make a Unity wrapper class that asks it if a button has been pressed. Not a nice fancy solution but a dirty one that at least has the functionality!

In my experiments I've measured the input delay on active mode and it seems to be around 300 ms, is that something you can confirm or deny? It may depend on the hardware receiving the signals as well...

For other people looking for Unity integration of their Flic buttons I would recommend to do this way at least for now, remember to read up on launching activities from Unity, how to communicate with these and how to structure everything in the project. I can't share any of my code but there are some good starting advice.

@Emil Yeah, that's what I figured from the sounds, The active mode surely have lower latency but playing a flappy-incarnation with that delay was... special Where can you active this mode for other applications? Via the SDK or settings in the applications? I looked around and did not find anything...

I want to measure reaction times with my application and I think that the Flic buttons are not fully suitable for this purpose due to the input latency, however they could be if the latency is constant and do you have any public datasheet with these kind of specifications for the buttons?

I'm not an expert on the Android system so I don't really know what would be the best approach in this case, however I do know from my experiments the last couple of days that as you use the SDK today is not compatible with Unity based applications for Android.

In an Unity based application the flow is as described below:
The main Unity Activity is fetch in a C# java object wrapper. The C# code then instantiates a Java holder class with the main activity passed as a parameter. The C# code then calls a method of the newly created Java object to start a new Activity (which hold the code for grabbing the buttons). The activity is created, then from the C# code the started activity is fetched into a Java wrapper object. Then C# code calls the initiation of the buttons as explained in the "Tutorial". The Flic Grabber screen is shown and I can choose which Flic I would like to grab. So far, so good.
Then when the grabber thinks it is done it is closed, but since I cannot make the Unity main activity have the onActivityResult method the result from the Flic grabber is not processed correctly (I think) when the onActivityResult method is implemented in the Java activity i instantiated.

Do this make any sense to you or do I need to explain more?

I'm glad you are taking your time to look into this! Have a nice day,

Edit:
I've read up on broadcast receivers and stuff and it seems to be a possible solution for Unity applications.

Oh, that did not sound good at all, I can understand that decision. However it seems very hard to connect the flic buttons to an Android Unity application since the SDK needs to use the main activity. I have tried to work around it, but I think I cannot do anything more since the usage of onActivityResult(int, int, Intent) method and one can't really extend the Unity activity to use the required function, or is there a convenient way you or some other user know of?

I have noticed that the flic buttons does not react instantly to input, there is a small delay, or rather a small delay until the button press sound is played on the android device, is there a input delay in the button before sending the press signal or is it in the android device? You have any idea?

Any news about this? Looking for the same functionality.