Developer Terms and Conditions The Development Android development Calibration Timeout on UDOO-Neo w/ Android

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #2912

    Problem:

    I am encountering a timeout when calibrating the SCiO using the provided example code when paired with Android 5.1.1 on the UDOO NEO.

    Pertinent information:

    • The light on the SCiO illuminates to the white-pinkish calibration color, then turns blue, demonstrating it received the signal.
    • I have successfully Calibrated and Analyzed material with the SCiO when paired with an Android 6.0.1 smartphone using the same code.

    Additional Information:

    • I downloaded the Alpha version of Android 5.1.1 for the UDOO NEO microcontroller from the devs here: http://www.udoo.org/forum/threads/android-5-1-1-alpha-for-udoo-neo-full.3449/
    • Here is the full output I get when I start a calibration:

    ————–——-——————-——————-——————-——————-——————-——————-—————–——-

    03-10 08:53:15.255 3143-3143/consumerphysics.com.myscioapplication D/BluetoothGatt: setCharacteristicNotification() – uuid: 00003491-0000-1000-8000-00805f9b34fb enable: false

    03-10 08:53:15.289 3143-3143/consumerphysics.com.myscioapplication D/BluetoothGatt: setCharacteristicNotification() – uuid: 00003491-0000-1000-8000-00805f9b34fb enable: true

    03-10 08:53:15.874 3143-3143/consumerphysics.com.myscioapplication D/BluetoothGatt: setCharacteristicNotification() – uuid: 00003491-0000-1000-8000-00805f9b34fb enable: false

    03-10 08:53:15.885 3143-3143/consumerphysics.com.myscioapplication D/BluetoothGatt: setCharacteristicNotification() – uuid: 00003491-0000-1000-8000-00805f9b34fb enable: true

    03-10 08:53:17.996 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 11.651ms

    03-10 08:53:18.954 3143-3156/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 12.168ms

    03-10 08:53:20.007 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 13.635ms

    03-10 08:53:26.026 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 5.706ms

    03-10 08:53:28.929 3143-3952/consumerphysics.com.myscioapplication W/l: reset data – will wait for first packet

    03-10 08:53:30.547 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 10.895ms

    03-10 08:53:33.562 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 10.743ms

    03-10 08:53:34.562 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 6.484ms

    03-10 08:53:35.569 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 5.067ms

    03-10 08:53:36.582 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 9.113ms

    03-10 08:53:37.587 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 8.624ms

    03-10 08:53:40.122 3143-3156/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 5.899ms

    03-10 08:53:40.163 3143-3156/consumerphysics.com.myscioapplication I/art: Background sticky concurrent mark sweep GC freed 22917(852KB) AllocSpace objects, 0(0B) LOS objects, 38% free, 1548KB/2MB, paused 6.717ms total 56.294ms

    03-10 08:53:40.913 3143-3952/consumerphysics.com.myscioapplication W/l: reset data – will wait for first packet

    03-10 08:53:41.604 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 9.567ms

    03-10 08:53:44.119 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 15.646ms

    03-10 08:53:45.898 3143-3143/consumerphysics.com.myscioapplication E/MainActivity: Timeout while calibrating

    03-10 08:53:46.630 3143-3145/consumerphysics.com.myscioapplication W/art: Suspending all threads took: 11.308ms

    ————–——-——————-——————-——————-——————-——————-——————-—————–——-

    Any advice would be greatly appreciated!

    #2924

    Update:
    Today, Connecting to the Android 6.0.1 smartphone times out too, with no change to the code.

    Is there any way to make these operations more reliable or at least informative to devs?

    What causes time-outs with the SCiO?

    #2929
    Ayelet
    Keymaster

    Hi Vaish,

     

    Thanks for reporting these issues.

    We will transfer the problem to our software team and update soon.

     

    Ayelet,

    The Consumer Physics Team

    • This reply was modified 7 years, 11 months ago by Ayelet.
    #2957

    I found that clearing the app data for the SCiO example app on the Android 6.0.1 smartphone and reentering all information again will temporarily resolve the issue.

    This did not fix the issue with the UDOO NEO’s calibration, however.

    #2960
    Ayelet
    Keymaster

    Thanks,

    Transferred to our software team.

     

    Ayelet

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.