Home › Forums › Ask the Flomies › Android SDK test example
Tagged: Flomio SDK Android
-
AuthorPosts
-
July 2, 2018 at 10:14 am #63340
Hi,
I tested the Flomio Test app from google play using android tablet and FloBLE plus:
https://play.google.com/store/apps/details?id=com.flomio.android.sdk.testWorks great
I am trying to find a similar example where I can use it as a base for an app on Android studio.
I found one here:
https://github.com/flomio/cordova-plugin-flomio/issues/16However, nothing appears when I select FloBLE plus
there is no scan for readers and at the Bottom it only appears a SEND APDU button, If I click it it says “Please select a reader from the list before sending an PDU command”.I try to pair the FloBLE using android Bluetooth settings, but it still does not appear.
What am I doing wrong?
July 2, 2018 at 3:43 pm #63344Hi Hector,
Our native android SDK hasn’t been worked on in a while unfortunately.
Here is a link to the latest SDK but it is not something that we will be maintaining much going forward as we are moving to a cross platform Javascript SDK.Scott
July 3, 2018 at 3:28 am #63351Hi Scott,
Thank you very much for the link. I managed to get it to see the FloBLE with the SDK you sent.
However I dont know how it happened, but I think I bricked the device. It behaves shows both LEDs solid on power up and then only the left LED red.
I found the flash tool to try to unblock it:
However, if I plug it to Windows PC while pressing the small button on the back. It constantly beeps every couple of seconds. Like rebooting itself over and over. And I cannot find the reader on Device Manager.
How to fix this?
July 3, 2018 at 7:22 am #63353I have not seen this problem so unfortunately I don’t have any suggestions but I will reach out to others on the team and see if they have seen this.
July 3, 2018 at 8:31 am #63354Thank you!
I tried a different PC and it is the same problem. It kind of reboots all the time and device manager gets refreshed every couple of seconds.
July 3, 2018 at 8:32 am #63355Have you tried your device with any other of our SDKs? Try using the NFC Actions app on iOS so you can determine it’s not a software problem.
July 3, 2018 at 8:36 am #63356Hi,
Yes, it was working previously with NFC Actions app. I also worked before with the ACSSmartAccess app for iOS. But now it seems to be bricked, only the Red LED on the left is On all the time and the NFC Actions keeps scanning for reader but not finding any
July 3, 2018 at 9:01 am #63357July 3, 2018 at 9:26 am #63358Thank you Scott,
Mmm.. I have not managed to get to use the flash tool. The ACR1255 keeps resetting every couple of seconds when what I assume is boot loader mode connected to a windows PC. It is funny that it does not that when connected to a Mac. But I assume that there are no flash tools for OS X are there?
July 3, 2018 at 10:23 am #63359You’re right, there’s no flashing tool for OSX. Trying to get the flash tool to work on windows is your best shot at fixing the device.
July 3, 2018 at 10:43 am #63360I think as soon as I can get the device not to reset when connected to a Windows PC, then I will be able to find it in the device manager and update drivers, etc.
I tried using Parallels from the Mac, it starts resetting as soon as I connect the device to Windows.
July 3, 2018 at 5:52 pm #63368I managed to flash the firmware and it works now. It needed to be done on a Windows 7 PC. Somehow it was rebooting all the time when connected on a Windows 10 computer.
The NFC actions app in iOS works without problem. But neither the Android Test app, nor the ACS SmartAccess for Android can find the reader on bluetooth. Which is funny because it did before the device got bricked.
July 4, 2018 at 6:56 am #63374Glad you made progress with flashing the device and that it’s working in some capacity. I have not been able to reproduce the problem and I have tested the Android Test app with the v1.16 firmware.
-
AuthorPosts
You must be logged in to reply to this topic.