[blockquote]Gábor Polczer said:
when devs put in new functions everyone is mad about buggy basic functionality, when they focus on fixing basic functionality users are rushing new functions. hard to make everyone happy, huh?
for me, it would be fine if the new Android app base functions were finally ok and later they expanded functionality in little steps. one can always borrow an iOS device if some advanced feature is crucial (like showing MOCs @ exhibitions), so it's far not as bad as some folks are saying. if iOS wasn't an alternate option, it would be really annoying, but please keep in mind that Android app is v0.80 while iOS app is v3.7.2 !!!
[/blockquote]
Now I can not agree with you because I bought my sbrcks in august, I got them for Christmas and I am still not able to use them for a model with 2 sbricks like the ultimate versions of Jurgen or my train where I need to control two 88002 with the same slider and running in the opposite way.
And why such a difference between ios android ?
v0.80 is also one month old!
[blockquote]Jurgen Krooshoop said:
Reading that supporting more than 1 SBrick will not be available in the next update makes me really sad. It's the one MOST IMPORTANT specific function I've been waiting for since the Android-app was released. Since all my SBrick-MOC's use 2 SBricks, the Android app is still useless and will be for some time to come...
[/blockquote]
I want to build your ultimate version of the 8043 and 42009 but I will not be able to control them...
when devs put in new functions everyone is mad about buggy basic functionality, when they focus on fixing basic functionality users are rushing new functions. hard to make everyone happy, huh?
for me, it would be fine if the new Android app base functions were finally ok and later they expanded functionality in little steps. one can always borrow an iOS device if some advanced feature is crucial (like showing MOCs @ exhibitions), so it's far not as bad as some folks are saying. if iOS wasn't an alternate option, it would be really annoying, but please keep in mind that Android app is v0.80 while iOS app is v3.7.2 !!!
Reading that supporting more than 1 SBrick will not be available in the next update makes me really sad. It's the one MOST IMPORTANT specific function I've been waiting for since the Android-app was released. Since all my SBrick-MOC's use 2 SBricks, the Android app is still useless and will be for some time to come...
[blockquote]Matej Papluh said:
[blockquote]Zsolt Majoros said:
Thank you for your feedback! We will implement the more sbrick support after we solved these device compatibility problems.
[/blockquote]
Sorry for maybe stupid question (I was 2 months out of the loop), but does that mean that the app officialy does not support more Sbricks on one profile ? Is this the same for iOS ?
I guess for the time being I'll have to solve it for the 42009 mod by having either 2 devices or 2 profiles on one with functions driver (steering, power, stabilizers, chassis lights) and operator (boom angle, lenghts, winch and rotation)
[/blockquote]
The android version still doesn't support more sbricks at the same time, we put aside this feature to solve other problems asap.
The iOS version is already supports more sbricks, we tested it with 6 sbricks at one profile.
[blockquote]Zsolt Majoros said:
Thank you for your feedback! We will implement the more sbrick support after we solved these device compatibility problems.
[/blockquote]
Sorry for maybe stupid question (I was 2 months out of the loop), but does that mean that the app officialy does not support more Sbricks on one profile ? Is this the same for iOS ?
I guess for the time being I'll have to solve it for the 42009 mod by having either 2 devices or 2 profiles on one with functions driver (steering, power, stabilizers, chassis lights) and operator (boom angle, lenghts, winch and rotation)
[blockquote]Miguel Angel Vilela said:
Will the next Android app allow us to update the SBrick firmware OTA?
Because, y'know, some Android users may not have access to an iOS device (or Mac) to update the SBrick firmware!
[/blockquote]
Of course!
[blockquote]Matej Papluh said:
So, back home after 2 months and to testing of v0.8
HTC ONE - now on Lollipop 5.0.2, still seems generally ok,
- joystick finally works, although sensibility on the 4.7" screen is not the best even when stretched to fill the height on landscape a slider is more precise
- Can't control 2 SBricks from one layout, I add and configure both of them and only the first work.
- Sometimes a profile is lost from the MOC, usually the last added one
Nexus 7 - still on 5.0.2
- first thing is minor, the joysticks on 16:10 layout (own or default) seem not to be centered
- what is worse, the control is not working well. It was laggy and buffering before, now there is less buffer, but more lag and stuck control (sometimes a value is stuck for 1-2 sec)
- Also it seems the mapping of controls does not go to full or something. For example a Volvo can climb a carpet with HTC and full slider and not with N7 ... maybe difference in 16:10 vs 16:9
We have a LUG event in 2 weeks and originally I planned to buy more than 2 Sbricks and have a full gang (dozer, volvo, digger, crane, crawler ...) for people to use. This was abandonded weeks ago. But with all these problems - works only on one of my devices (HTC) and no dual SBrick profiles - I'd be lucky to have at least the 2 I have working :(
[/blockquote]
Thank you for your feedback! We will implement the more sbrick support after we solved these device compatibility problems.
So, back home after 2 months and to testing of v0.8
HTC ONE - now on Lollipop 5.0.2, still seems generally ok,
- joystick finally works, although sensibility on the 4.7" screen is not the best even when stretched to fill the height on landscape a slider is more precise
- Can't control 2 SBricks from one layout, I add and configure both of them and only the first work.
- Sometimes a profile is lost from the MOC, usually the last added one
Nexus 7 - still on 5.0.2
- first thing is minor, the joysticks on 16:10 layout (own or default) seem not to be centered
- what is worse, the control is not working well. It was laggy and buffering before, now there is less buffer, but more lag and stuck control (sometimes a value is stuck for 1-2 sec)
- Also it seems the mapping of controls does not go to full or something. For example a Volvo can climb a carpet with HTC and full slider and not with N7 ... maybe difference in 16:10 vs 16:9
We have a LUG event in 2 weeks and originally I planned to buy more than 2 Sbricks and have a full gang (dozer, volvo, digger, crane, crawler ...) for people to use. This was abandonded weeks ago. But with all these problems - works only on one of my devices (HTC) and no dual SBrick profiles - I'd be lucky to have at least the 2 I have working :(
about the FW update: i guess updating on iOS now gives the same result as updating on Android with the future app, so it's more secure to use an iPad/iPhone and update to 4.2 asap.
about quick drive: this "different control possibility" means a completely new and not a selectable method? i mean this new way of control replaces the old one which will be obsolete from now on (because of the poorly optimized BLE data sending). or this new method is lesser but more compatible and still ok to use for controlling SBricks?
Hi,
In the past weeks, we tested on plenty of different devices, and we noticed that some of them has really weak BLE management service.
We send four packages for each channel per 90 milisec to support a really responsive and flawless drive experience, but these devices dies in this large amount of passed data (for example the galaxy S3).
The good news is that we created a different control possibility in the 4.2 firmware named quick drive, that requires to send quarter so much data over BLE, and it seems to work on devices with weak bluetooth layer.
The "bad" is that everybody must update the firmware to use the app. It's recommended for other reasons also, so it isn't a big problem i think.
At the moment we are working on implementing quick drive at android, and finalize + test the OTA.
A version is coming in the middle of the next week with these changes, we really hope this resolves all of your problems.
[blockquote]Maxim Baybakov said:
[blockquote]Tamas Misik said:
@For the others
The new App will be availabe soon. Our developers are working hard on it. They are fixed many bugs. More info about the new application the next few days.
Thanks for your help and your patience!
[/blockquote]
May I (and not only me) expect the fixing delay/freeze while giving the command and its running (5-8 sec) on Samsung Galaxy S3 9300?
[/blockquote]
We bought an S3 (I9300) to fix this problem, we're working on it.
Really strange, because on S3 (I9301) it's working fine, we'll find the solution.
[blockquote]Tamas Misik said:
@For the others
The new App will be availabe soon. Our developers are working hard on it. They are fixed many bugs. More info about the new application the next few days.
Thanks for your help and your patience!
[/blockquote]
May I (and not only me) expect the fixing delay/freeze while giving the command and its running (5-8 sec) on Samsung Galaxy S3 9300?
@Karl
We made porfile, instructions and extra parts list for the 42009S, and you will get your color cases soon, but please contact us here: info@sbrick.com for more informations because this topic only for the Android Application.
@For the others
The new App will be availabe soon. Our developers are working hard on it. They are fixed many bugs. More info about the new application the next few days.
Thanks for your help and your patience!
Samsung Galaxy Note 3. Android 4.4.4.
Bug report. App crash.
- If my brick IS powered AND BlueTooth was already ON: Every time I go to "Manage Bricks" the "Discovering Sbricks..." message comes up, then I see my brick listed in the background, and then the app crashes.
- If my brick is NOT powered, the app does not crash upon going to "Manage Bricks".
- If my brick IS powered AND BlueTooth is OFF, the app does not crash upon going to "Manage Bricks". The app asks me to turn on BlueTooth, I say yes, then it discovers my brick and lists it correctly. I am able to connect to the brick correctly.
I uninstalled and reinstalled the app and it still happens.
[blockquote]Christian Treczoks said:
[blockquote]Alexey Tikhvinsky said:This is international forum, so please DO NOT SPEAK YOUR NATIVE LANGUAGE, use English. Using your native language here is rude and impolite.[/blockquote]
Well, I can understand them. They are so seriously pissed that they returned to their native language for their rant.[/blockquote]
Thank you Christian for your understanding!
Not everyone needs a foreign language but he is Legofan;-)
[blockquote]Alexey Tikhvinsky said:This is international forum, so please DO NOT SPEAK YOUR NATIVE LANGUAGE, use English. Using your native language here is rude and impolite.[/blockquote]
Well, I can understand them. They are so seriously pissed that they returned to their native language for their rant.
And like them I hope that SBrick starts to get their act together. I withhold any recommendations and purchases until you have a real, working product. The software I've seen matches the reports I've read: The SBrick App is far, far away from being a marketable piece of software. If I was in charge I would reassign the person responsible and find someone to start from scratch.
Your Developers are lost with their heads in the clouds without being able to produce a working, basic product. The line of appearence, disappearence, and re-appearence of bugs indicate a completely messed up development process without even the most basic attempts on verifying the product before shipping. My boss would rip me another one if I was "working" like that, and in my company I am a one-man-show with a way more complex product...
Ok, then in English. I'm going to wait until June 2015 and then when the whole does not work I'll return my SBricks and demand my money. I paid for 2 pieces SBricks in yellow including a profile for the 42009. I get to today two bricks in gray, no functioning app and no functioning profile for the 42009.
hello!!
Good news, i have an update one my phone and sbrick can work now!!!!
But i have a question, can i connect 2 or 3 sbricks on the same MOC??, because I have already 4 IR lego one my MOC and I want to drive them with 2 or 3 sbrick. I try with Jurgen joystick, but it doesn't work!!!
Thanks
ben
klaus eicher, Marco Rocholz, Karl Fensterstock
This is international forum, so please DO NOT SPEAK YOUR NATIVE LANGUAGE, use English. Using your native language here is rude and impolite.
Regards, Alex