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!
Would you provide your SBrick connection status to the statistics thread I tried start ?
https://social.sbrick.com/forums/topic/68/device-sbrick-connection-compatibility-statistics/
It should not replace this one, just used for collecting pure statistics on which device type/model is generally connecting OK or not.
Hi gents,
Give feedback (always useful for developers - include your android version and phone/tablet model), but keep in mind that the android actual version of the app is still in development, it's a beta version just released for us to test our just received Sbricks and be able to play a little bit during our vacations.
After all efforts done to have the hardware ok and send it, I think Sbrick team can have a little rest during this holiday period, even if we are also on holiday, with our Sbricks, impatient to see them animating our models.
Let's be comprehensive and patient... Roma did not get built in one day!
Sylca (simple backer)
[blockquote]Zsolt Pogonyi said:
Hi Everybody!
I can't pairing my phone with SBrick. I have Sony XPeria SP, Android 4.3, BLE Checker say BLE Supported. nRF Master Control Panel can connect, without previosly pairing. SBrick LED blink shortly after switching power on. I tried it with AA batteries (8881) and rechargeable battery box (8878). My phone bluetooth settings found the SBrick, but can't pairing. I have the latest SBrick Android App version 0.0.21 and this can't discover SBrick. Please help!
[/blockquote]
Hi same phone, same problems. The first time I was able to pair with SBrick, but since the older version of the app didn't work, I unpaired the devices in order to start the whole procedure again - then I couldn't pair my devices anymore. I tried to clear the bluetooth cache, but it seems it doesn't clear right, there are always 12kB of data in cache that just won't go away. I tried the same on XPeria M, first time pairing wnet ok, app was working, after unpairing, no pairing could be done again!
Seems to be a huge gap between the current app version 0.0.21 and what is shown in some of the promotional videos.
And certaily acts like 'alpha' software. Certainly has a lot of potential. Is there a timeline for a beta release that might be more usable and closer to some of the promotional videos?
Thanks,
Ben
Hello,
I currently have a fully up to date samsung galaxy note 3, I am having trouble controlling my creations at all. The profiles in the app can't be adjusted, and for some reason the motors I am trying to power are acting really weird. I can't wait till the adroid app catches up with the ios one because right now it's between the android app and my iphone 4s which isn't exactly compatable with the app screen size wise (more details in the ios forum...). Bottom line, I can't easily control my creations so I hoping for a some serious updates. I know you guys are trying your best, just trying to share my experiences so far...
Thanks,
Justin
[blockquote]Sylvain CACHEUX said:
...
Interresting point: when having a pb with a profile, go to market, delete profile, then redownload it and it works better! (does not work with joystick or gamepad 1 for me - sometimes app crashes when deleting the profile in the set edition)
...[/blockquote]
Thanks. Your confirmation of this behavior had me trying again and succeeding.
I want to add, that for the profile to reload I needed to remove it from all MOCs. I tried deleting it from market before and it failed reloading, but left it linked to one of the early MOCs.
