Forums » Support

Back To Topics

SBrick Android App

    • 19 posts
    March 9, 2015 12:20 PM CET

    for everyone still having issues with controlling SBrick (even from port tester) on Lollipop see my findings below.

    checked v0.8 on three different Nexus 5 phones this weekend, and the conclusion is: my Nexus 5 was still unable to control SBrick until i deleted all my BT pairings/trusted device settings (a headphone and a soundbar were paired/trusted). after doing so and couple of reboots and reinstalls everything seems to be ok now. other two Nexus 5 phones worked out of the box with the same unmodified 5.0.1 OS (they had no BT pairings prior installing SBrick app), so this gave me the idea to check BT settings. reported to devs, i hope this has to something with our issues.

     

    if it does not help, try to manually pair SBrick with the phone through Android setting. it worked me for the first time (but not later on) and made my SBricks finally controllable in the App.


    This post was edited by Gábor Polczer at March 9, 2015 12:25 PM CET
    • 7 posts
    March 8, 2015 11:17 PM CET

    0.8 does not work on a Galaxy S 5 with Lollipop (5.0) installed.

    • 7 posts
    March 7, 2015 10:07 PM CET

    0.8 does not work on a Galaxy Tab 4 or a Galaxy S 5

     

    Tab 4 - Profile assignment to creation does not stick, impossible to configure SBrick to specific features of the profile.

    S 5 - Attempting to discover SBricks crashes the app reliably.

    • 95 posts
    March 7, 2015 8:52 PM CET

    [blockquote]Miguel Angel Vilela said:
     

    And on top of all the issues... where is your issue tracker? I think your life (and ours!) would be a lot easier if you had an issue tracker like Bugzilla to keep track of each bug / feature request in one place, rather than have them all scrambled together in this forum like spaghetti ;)

    [/blockquote]

     

    This is a good idea. We will be able to know if a feature should works or not...

    • 3 posts
    March 6, 2015 9:50 PM CET

    What about firmware uogrades for the android app. I see that the iOS has the ability to do firmware updates and I have done one. If I then switch the Sbrick to operate from android will it still work? Are the firmware updates cross platform?

    • 4 posts
    March 6, 2015 9:02 PM CET

    Tried it on Nexus 4 with 5.0.1 android.

    When I want to select a profile on a creations, apps crashes. With all profile. Consequently, I can do nothing. things are getting worse and worse...

  • March 5, 2015 2:33 PM CET

    More on the latency prroblem: it seems to be specific to ports B & D and only when using them from a profile.

    Any control of any profile reproduces the issue, while latency is relatively low in all ports when using the port tester.

    So if I use only the left side of the SBrick, I can control a little car. More or less. Even the "low latency" ports (A & C) are lagging behind my commands enough to make it really hard to drive a little, mildly fast car (Sheepo's MAP, 2 L motors, 1:3) anywhere in particular. It's a lot more a crazy random bumper car than anything else. Making the car 3x slower, I can play a bit with it, but the latency still makes it harder to drive than with the PF IR controls. An example exercise is to leave the car centered on my Microsoft Natural keyboard, from a starting position on my desk near the keyboard. It's quite harder with the SBrick than with PF IR. Using the port tester makes the exercise a bit easier.

     

    Another issues I'm seeing is that when assiging the ports for a "Linked SBrick" in a MOC, the on/off switches do nothing. I can't invert port C where I have the Servo, so I had to invert port A instead (which does work) and use the Gamepad II profile upside down. While kinda usable, it's uncomfortable.

     

    Also, "Connecting to SBrick" isn't working very well either: every time I want to switch between a MOC's profiles and the port tester I need to restart the SBrick and the app, sometimes multiple times, otherwise it will never manage to connect (time out). Switching between profiles within one MOC seems unaffected so far.

     

    And on top of all the issues... where is your issue tracker? I think your life (and ours!) would be a lot easier if you had an issue tracker like Bugzilla to keep track of each bug / feature request in one place, rather than have them all scrambled together in this forum like spaghetti ;)

  • March 5, 2015 1:11 AM CET

    Version 0.8 seems a little bit better: it finally manages to connect to the SBrick when opening a profile! (Nexus 5, latest Android version)

    But I only got that one step forward, then faced Big Bugs:

    - Latency is TERRIBLE. Several seconds pass between me sliding the slider all the way to one side and the motor starting to spin. Are your logs collecting timing data?

    - Motors keep spining after closing profile.

    These 2 bugs make the SBrick unusable. You can't drive a vehicle that takes 2 seconds to start moving and 4 seconds to stop moving! I've tried several times and it's always 2-5 seconds between sliding the slider to one side and the motor spining, and 4-5 seconds between letting go of the slider (it returns to center immediately) and the motor eventually stopping.

     

    Plus the app still crashes miserably when trying the set the photo for a MOC. I get to pick an image, but a second or two after a tap on my photo... "Unfortunately, SBrick has stopped". Every. Single. Time. And "My Profiles" still doesn't load my profiles.

     

    Also, I have to say the workflow from fresh install to a working profile is long, confusing, far from intuitive. Once the UI and flows are final, please write a better User Guide for SBrick. I've read https://social.sbrick.com/wiki/view/pageId/9/slug/user-guide-for-sbrick and it's too densly packed with text and no images, hard to follow. Screenshot please, don't make reading this User Guide just as hard (or even harder) than using the app.

    • 41 posts
    March 4, 2015 10:41 PM CET

    @Tamas

    I install the 0.8 LOG Version and test with my Samsung Galaxy S3 (android 4.3):

    - Fresh install, i can discovery the sbrick in the port tester screen, BUT the port tester is not working (upload 1 log of this). The led on/off is working.

    - I try again in the same screen and now the sbrick is not longer discovery, i try severals times with the same result (upload 2 or 3 logs of that)

    - Try to discovery the sbrick in the profile screen and the sbrick CAN'T be discovery (upload 1 log of that)

    - The app hangs a lot.

     

    Hope you receive those logs and solve this issue.....the current app is NOT WORKING at all with the S3 (and suppose with others models).

    • 5 posts
    March 4, 2015 7:22 AM CET

    At Last an App that finally has some function! Using HTC One 4.4.3, can now control one brick with Joystick and sliders.  Would love to use the Volvo 42030S with two bricks, but cannot asign brick functions.  When second brick is added app goes crazy and flickers.  Much better but still along way to go to be as good as IOS.

    • 5 posts
    March 4, 2015 4:40 AM CET
    Hello,
    As I said with the Galaxy Note 4 and Android 4.4.4 a SBrick works without problems. No crashes . You can still enroll a second SBrick where you can test the channels and the port tester also goes but the second SBrick not work in the profiles. Only the first registered SBrick .
    Unfortunately, the reverse function does not work. Only either all or no reverse .
    I hope this will be .
    greeting
    M.R.
    • 7 posts
    March 4, 2015 3:24 AM CET

    0.8 does not work properly on Samsung Galaxy S5, Android 4.4.4

    Attempting to add a brick to the profile (which causes the app to look for SBricks) crashes the app every time. Version 0.6 worked better.

    • 275 posts
    March 3, 2015 10:49 PM CET

    [blockquote]Jetro de Château said:

    Why keep post APKs here instead of just putting them on Google Play?

    [/blockquote]

    The 0.8 is downloadable from the google play.

    This is a logger version, it can help for us in debugging: 

    SBrick.apk (v.080 Log): http://goo.gl/UEXTUu

  • March 3, 2015 10:44 PM CET

    Why keep post APKs here instead of just putting them on Google Play?

    • 164 posts
    March 3, 2015 7:46 PM CET

    Thanks for your feedbacks!

    Here is the v0.80 Andorid application, SAME as the previous I posted, but this version has a "Log" function.
    If your device can't connect to the SBrick, please help us and download the following apk:
    SBrick.apk (v.080 Log): http://goo.gl/UEXTUu

    Please
    try to use this App and if your device can't connect to the SBrick, then just press the "Upload Log" button on the "home screen", and we will see everything what happened in your phone.

    This App records everything in a "log" file. Please keep it in mind, if you are using the App for a long time, the result can be a large file, so please don't use the "data connection". When you are using the app make sure you only enabled Wifi connection on your phone

    Thanks!

    • 25 posts
    March 3, 2015 5:05 PM CET

    Hello,

    I'm like Philippe Hurbain. It seems to be working better (Samsung Galaxy Note II with 4.4.2) but I have to test further.

    Nevertheless, still no roadmap or information about debuging future work... Still waiting.


    This post was edited by Sylvain CACHEUX at March 3, 2015 5:07 PM CET
    • 95 posts
    March 3, 2015 1:00 PM CET

    [blockquote]Jurgen Krooshoop said:

    Just installed version 0.8 and I could notice some improvements. Most functions work now, exept for one:

    I can now assign 2 SBricks to 1 profile and assign all the profile functions to the SBrick ports, but the profile can controll only 1 (the first) SBrick. All functions assigned to the second SBrick do not respond. So only half of my excavator profile works.

    Using Sony Z3 Compact, Android 4.4.4

    [/blockquote]

    This is one of the function I am waiting for. I would also like to control more than one channel with the same slider;-)

     

    • 23 posts
    March 3, 2015 12:16 PM CET

    Just installed version 0.8 and I could notice some improvements. Most functions work now, exept for one:

    I can now assign 2 SBricks to 1 profile and assign all the profile functions to the SBrick ports, but the profile can controll only 1 (the first) SBrick. All functions assigned to the second SBrick do not respond. So only half of my excavator profile works.

    Using Sony Z3 Compact, Android 4.4.4

    • 3 posts
    March 2, 2015 10:27 PM CET

    The latest 0.80 works partially on my Samsung Tab S with Kitkat. I can no longer save a profile to test. I can see the sbricks or sbricks(I am trying to get Jurgens Beltlink 220 to run) but it has problems seeing two sbricks. I can identify the two bricks and run all the motors with very good control....but that is it!! I also get the message that Sbrick has stopped working just when things are going good! I also have the latest ipad mini and even that app has a few problems still. BTW I would like to get the profile that controls Jurgens excavator. Is it still available?

    • 16 posts
    March 2, 2015 9:15 PM CET

    I still have to test more extensively, but 0.80 seems to work pretty well on my Asus ME572C. Yeah !!! :D

    • 95 posts
    March 2, 2015 8:36 PM CET

    I found a little bug in 0.80. When I leave a profile, the motor does not stop to spin

    • 5 posts
    March 2, 2015 7:13 PM CET
    Super... funktioniert jetzt endlich mit meinem Galaxy Note 4 und mit meinem LG GPad 8.3
    Keine Abstürze. Der Porttester funktioniert jetzt. Die Profile auch. Nichts ist verzögert.
    Nur zwei SBricks werden noch nicht unterstützt. Beim zweiten angemeldeten SBrick kann man die Ports testen aber in den Profilen funktioniert nur der erste angemeldete SBrick.

    Weiter so... dann geht vielleicht auch der Rest mir der nächsten Version.

  • March 2, 2015 6:45 PM CET

    Es wird immer schlechter statt besser :-(

    LIFETAB S8312

    Android 4.4.2

    SBick App Version 0.8

    Die kopplung zwischen Pad und Brick dauert ewig.

    • 19 posts
    March 2, 2015 6:37 PM CET

    it's not necessary just easier to follow this way. comments can't be tracked when there is too much of them.

    • 21 posts
    March 2, 2015 6:13 PM CET

    [blockquote]Gábor Polczer said:

    Maxim, Samsung Galaxy S3 is not even on the list, you should add it first if you have problems with it.

    [/blockquote]
    And developers for what ?!
    With my poor knowledge of English, I wrote several times about the error for Samsung S3. And now it turns out that it was necessary to add some sort of record in the "wiki". Are you kidding ?! Kindergarten...