I have the same "long" delay. Especially when using steering control or two ports.
When the slider quickly move in different directions, for example 20 times, brick continues to perform these commands for 15-20 seconds.
Several times the application was closed itself.
Inversion of ports does not always work (if on/off is the inversion).
(Samsung Galaxy S3, 4.3)
Hi,
Just test the android 0.25 version with the Crawler 9398 and a MOC (is a car), both have only steering and acceleration....now with my samsung S3 i can discovery and connect the sbrick...THANKS fot that!!!!!
This are my observations/issues:
- The joystick and gamepad 1 profile don't work at all.
- Gamepad 2 works, but both sliders are too big....so i can't reach the max power without exit the screen with my fingers (left for steering and up/down for acceleration/reverse)....not a good experience with this type of creation. For Cars/4x4 we need a gamepad with both shorter slider, and binary (0 = stop and 1 = full throttle)
- For some reason when i go 50% with any slider (with gamepad 2) and release the slider....the engine get stuck at 50% without touching the screen.
- With gamepad 2, i choose the steering in the "C" slot.....if i reverse only that port....don't work....i have to also reverse "B" port to work properly......strange issue.
- I noticed that there is a delay when i touch the sliders in the cel and the engines actually start to move.....with my MOC (car) that runs faster than the Crawler is impossible to drive with that delay. This can be improved?? i know that with BT devices is always a very little delay, but i think in this case is longer that the "normal".
Also i try to change the Gamepad 2 profile editing the .json file......what's "frame" description? for the x,y,z,w
Thanks!!
[blockquote]Christian Treczoks said:
a software like this would never, ever, be released.
[/blockquote]
Yes, maybe not beta and still alpha quality. And then?
I think we all should be a bit more comprehensive! Since the kickstarter campaign and as all other kickstarter projects we knew there was an implicit risk.
And we honestly must admit these guys have made a fantastic job so far!!!
I must confess that I was prepared for considerable delays, when I raised my pledge. I did it mainly to expresse my support and to help this project to happen. Something we didn't get from LEGO for years, and probably we will never get.
After all they have managed to deliver the hardware to us, with the minimal delay of one month!!! Honestly I never expect such good performance. I've seen projects from much bigger companies with plenty of resources allocated, to fail miserably or to slip far from that!...
Ok, we have delays with the apps, but we have quality hardware and aparently without relevant failures found so far (firmware bugs count little here as they can be solved with ease).
Furthermore Vengit is in at least 4 app/sw development fronts (iOS, Android, WP, Profile Designer, SBrick firmware), with at least one pretty stable (iOS) at the brick delivery time. Android has big issues, but still it allows to do some tests already!
Ok, still a lot to do in what regards the profiles design and management, poor documentation (but app still in heavy developemt phase), but come on! Were you really expecting much more than this at this point?Or did o preffer to have nothing released to test, meaning you could do nothing with your SBricks?
This you can also test and give your feedback/suggestions to incorporate the product.
Other platforms support will arrive at their time! Give them time a space to make the right decisions and software design, which IMO where they should focus now, for us to get the perfect product.
Also you never heard from Vengit about excuses for the "delays", and I know there were several difficulties with significant impact, that could have caused much bigger delays by themselves and were also not their responsibility. They have always resisted to the tempation of making them public and after all we already have the SBricks in our homes!
Kudos Vengit!!
Just updated.
a) Select my MOC, tap "linked profiles" -> crash.
b) How do I remove a set from the "my sets" list?
c) And why is this app "portrait mode only"? - Nearly every other app I use works in any orientation, and, as a table user, I prefer landscape.
Still quite alpha, it seems. If my software would crash after only two taps, QA would rip me another one, and I would have to bring cake for all. But a software like this would never, ever, be released.
Leg bedre, Christian
thanks,
any release notes to share ? ;)
Tested on Nexus 7, I needed to wipe the app and reinstall to get the profiles work, port tester was working right after update.
Otherwise no change for me, was working before and its also now. And there still seems to be much more lag and random inputs on Nexus 7 compared to HTC One.
New android app here: http://sbrick.com/apk/SBrick_0025.apk
[blockquote]Tamás Fábián said:
The sets are removed intentionally, they had no real function. We'll figure out some other method to store the set number if you're building an SBrick into an official lego set.
I fixed the discovery bug yesterday afternoon, we'll put a version to the store ASAP.
[/blockquote]
Thanks, Tamas.
The sets are removed intentionally, they had no real function. We'll figure out some other method to store the set number if you're building an SBrick into an official lego set.
I fixed the discovery bug yesterday afternoon, we'll put a version to the store ASAP.
[blockquote]Norman Chalcraft said:
Samsung Galaxy S3 - GT19300 - Android4.3
Cleared cache, deleted data, uninstalled 0.21.
Installed 0.22 - changes since 0.21 - only the version number.
Still can't add a Set, only a MOC. Still can't discover a brick. We live in hope!
[/blockquote]
[blockquote]Norman Chalcraft said:...
Still can't add a Set, only a MOC. Still can't discover a brick. We live in hope!
[/blockquote]
https://play.google.com/store/apps/details?id=com.vengit.sbrick&hl
SBrick 0.0.22
got the 0.22
[blockquote]Fernando Correia said:
...
It is stated in several places that SBrick requires a BLE (BT Smart) compatible device.
It is also written that Android brought support to this only with version 4.3.
...[/blockquote]
Unfortunately technical limitations are nowhere to be found on the Sbrick KS page or homepage so I really feel for the guys having incompatible HW. The early pledgers had no playstore page to tell them the version compatibility.
In terms of consumer laws the missing/hidden compatibility can be a reason for full refund. SBrick is being marketed to general population and not to specialist (as engineering sample). So blaming it solely on the customers is not really correct.
Verson 22 is available. I have cleaned the cache, deleted the datas, uninstalled the application before installing the new version
(I have a gt-i9505 runing stock 4.4.2) I have downloaded Test 2 and port inverter works fine now :-)
I am now looking forward to be able to control 2 channels with only one slider
Thank you for this update
Regards,
Frederic
Pedro,
It is stated in several places that SBrick requires a BLE (BT Smart) compatible device.
It is also written that Android brought support to this only with version 4.3.
First you can check if your hardware supporte BT Smart. Then if it is the case you can look for cooked ROM with a newer Android version, that supports the required functionality.
SBrick is great if you have the right hardawre. Involved technology is quite new, so a couple of double checks are required to know if you have some chances to get it working with your current hardware before buying SBrick. Otherwise the only option is to upgrade to a newer Smartphone or Tablet.
Best,
Fernando
I'm very surprised and disappointed after the excitement of receiving my sbricks.
I tried to get the app from Google play and it says it is incompatible with both my Asus tablet and my ZTE smartphone (android 4.2.1 and 4.1.1 respectively).
What can I do to work this around, maybe I didn’t read some instructions, or when are you expanding the app to a broader range of devices?
I still admire your work, now I just want to take advantage of it…
Regards,
Pedro
I agree with Jetro.
Rather than doing profiles, I think it would be better to split the screen into small sections, for each of which user can choose slider (for example 2 vertical units, 1 horizontal unit (or the contrary if positionned in landscape)), button (1 V unit x 1 H unit), joystick (2 V units x 2 H units), gyro (idem), ... controls and place them like he/she wants (and zones for naming (like "door opening" or "train A speed"), then configure with which Sbrick each control would be affected (with inverterds), then save his display.
Like this, train users, for example, could control several trains in the same screen on a tablet, including lights, rail junctions, or other particular functions.
Thank you, and happy new year !
I have just received my sBrick today. I was able to install the app on my Samsung Galaxy S2 (custom ROM: cyanogenmod, Android 4.4.4) and my Samsung Galaxy Tab Pro 8.4
A few comments on the app:
Please push out a general update to the backers when you have a functional beta of the app
I received my SBrick a few days ago. The iOS app works alright on the iPhone 4S. It connects to the Sbrick most of the times. I can download profiles from the market,
and most of them works.I have the same problems as many of you have mentioned; the motors stop when full power is applied, and "identify LED" does not work.
Also also have a Galaxy Note (GT-N7000). This device does originally only support Android versions up to 4.2.1, but for the sake of the Sbrick, I rooted
and flashed it to Android 4.4.4 (using Slimroms). The Sbrick app works almost perfectly now! Motors can be powered 100% without shutting down, both in the port tester and in the various profiles. Identify LED also works.
Samsung Galaxy S5
Android 4.4.4
SBrick version 0.0.21
Port testers work.
Profiles can be downloaded from the market.
Brick can be paired.
No profiles work with the paired brick, varied bugs similar to those already reported - gyros don't work, some motors/ports don't register.
Shrill sound appears to be motor braking when sliders are in the "off" position, but not actually off. Recommend adding a "dead zone" to all self-centering controls where the motor is physically off to improve battery life.
Product is essentially unusable at this point.
When is there expected to be a profile building tool?
The description in the Android Market (now) says "This is an alpha preview build, not for production use!".
So the team is working on somethine better, it just means Android users have to wait. It may not be ideal but since the hardware is done and the iOS App seems OK a lot of people can work it fine.
I can wait!
I would probably describe it as Alpha rather than Beta considering most of it doesn't work, especially in comparison to the iOS one. (Which is an entirely different looking app)
Generally, at the moment the port testers work most of the time. The LED tester only work on rare occasions.
Amusingly, I have an S4 which can connect to the brick but with a very unstable and unfunctional app and a Apple 4 which has a nice app, but can't connect. Fun and games!
Just received my SBrick in the mail. Installed SBrick app v0.0.21 from the Play Store.
I have a Nexus 4 running stock Android 5.0.1.
Here is my feedback for the app:
I hope this helps yous guys somehow.
Unfortunately I cannot control the SBrick in order to control my creations.
Let me know if there is anything that you would like me to try out and give you feedback!