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!
Hello,
Just a suggestion: as there is more and more profiles, it's becoming a little bit hard to remember which one have sliders, or steering whell, or light switches.
So it would be very nice that, when selecting the profile, we could have a little image of the controlers, just to quickly see which profile it is really in terms of controlers.
And as previously asked, inverters for each port would be very nice to have.
Thank you :-)
Sylca
[blockquote]Sylvain CACHEUX said:
Edit: I uninstalled the app, reinstalled, redownload the market, recreate a new moc profile, and this time it worked! I do not know what changed, I guess the cache has been reset.
[/blockquote]
Same here, Android app crashes and you can't save an sbrick in a moc until you uninstall and re-install.
As mentioned elsewhere the brick makes a high pitch whine when operating, and there's no obvious way to reverse inputs it seems. Also noticed that sometimes on 'releasing' a slider the motor not stop, and you have to tap in the middle position when the control already is to stop or centre.
All that, given it's in Beta and I've got it working within an hour I'm quite happy :-) Just have to remember down is forward, and up backwards...
Iain
Just tested one of my Sbricks for the first time. First time right! Love it. Using Sbrick 0.21 on a Samsung S5 mini. Ultimate control, 4 slider controle, over the 42030.
The only thing I notice; it creates a very high pitched sound when active. Is that normal?
Okay, has anyone manage to get any profile to work on a Galaxy S4? I removed them and downloaded the current set (Including Test 1 & Test 2 now.) None of them do diddly squat.
The bit which amazes me is the ports work perfectly via the Manage Brick test interface. Just create a section of the interface in the APP where we have better access to those 4 sliders. At least then people can do some stuff.
Another thing I have noticed, is that you can't delete the sets you have created under My Sets. I removed the profiles from each one, then tried to remove the Sets themselves. Nothing. Delete icon does nothing. So be careful not to create to many Sets.
Just imagine if the SBrick has been shipped out at the original release date :)
I don't mind the release of the SBrick before it is really ready, just because the Test ports part of the App shows you what it will eventually be capable of. Just gotta sit tight a while.
Thanks to Tamas for publishing the communications protocol in the forum Suggestions.
Using this information together with the utility nRF Master Control Panel I have been able to control my Sbricks. This shows that there aren't any significant problems with the Sbrick itself, it is just major problems with the Android app.
Uninstalled Sbrick app and installed new version from Playstore, version 21, on to my Samsung Galaxy S3 running Android 4.3.
Changes? None in performance that I can see!! Still can't add a set only a MoC. Still can't discover any Sbrick! Only change that I can see is the version number!
[blockquote]Toku Betsu said:
My SBrick app updated last night. Was previously on 0.0.20 and is now 0.0.21. Apparently a scan fix has been done.
[/blockquote]"Apparently" yes, because I see no changes on my LG G2. SBrick visible in Bluetooth menu of the phone, but SBrick App can't find it.
Also the LED doesn't go on, it just flashes for a fraction of a second when you turn on the power. Not sure if this is normal behavior?
Yesterday I resived my SBrick.
After powering on the SBrick the manual says the LED should turn on. I did not... I though is my SBRick broken.
But after 2 times re-installing the App my Samsung S5 I was able to operate the SBrick.
I found that the LED is working if your turn it on in the Manage Brick menu (identify led).
I installed the SBrick on my 41999 and only profile Gamepad 2 was working, except the speed control was working reverse.
I don't know who to reverse the output controls.
The Joystick does not work at all and the steering profiles do not react very well.
Gamepad 1 does not work at all, sometimes the app stoppes. Test 2 only shows 1 slider. So I probably have to re-install the app again..
I also installed the SBrick app on our IPAD (software 6.1.3.) and IPOD but both cannot find the SBrick....
I hope the software bug will be fix sone
Hello everybody,
I'm running the app version 0.0.21, on Samsung Galaxy Note II, version android 4.4.2.
The market is ok, I managed to download all profiles.
With the Sbrick manage bricks, I find a sbrick, the identify led works (I noticed that last time I tested, the 2 first on/off, it did not worked, then the 3rd time it worked), the port tester works with all ports, and the OTA (???) indicates that the function will be available soon.
When I select the home page in the menu, it just displays a welcome message. When taping on it, it displays a kind of controler (joystick, black screen with white border, ...) but nothing happens on Sbrick.
When I select "my set", I tap the "+" and create a new profile via the "add new moc button (no possibility to add an existing lego model). This adds a profile. When taping on it, I can rename it, then change its image. I can also find my sbrick (discover is a bit long). Then I tap on the Sbrick to set the ports, which works. I tap "save your set!" button and ... it crashes. Impossible to save. If I tap on the profile before, it opens the profile screen (with buttons, sliders, etc.) but it warns me that "couldn't discover all bricks!" with cancel and retry button. Retry redisplays the same message, and cancel let me on the profile, which is obviously not working.
I tried to change the port on my Sbrick, but same error, the app is crashing, returning to my phone screen when saving my set. I manage to change the profile, and go into the sbrick ports, but always crashing when saving.
Edit: I uninstalled the app, reinstalled, redownload the market, recreate a new moc profile, and this time it worked! I do not know what changed, I guess the cache has been reset.
It may be helpful for others, that's why I'm posting :-)
So that's all I can test for the moment...
I guess you guys take some rests with your families during the holidays, after all the work you did with the hardware part, and think the app will be improved in january!
Best regards,
Sylca
Hi, finally I managed to test my SBrick on other phones, since I can't get mine to work:
It bonded perfectly with my friend XPERIA M running on 4.4.2 Android and the app worked fine. I thanked my friend and tried to clean her phone since she won't be needing neither the app nor the BLE bond with the SBrick - no problems there. But then I tried to re-bond the SBrick to her phone and it wasn't possible anymore! The phone displayed a message that went something like this: "The phone can't connect to SBrick because of the wrong PIN number or wrong password"
I guess the same happened on my phone (XPERIA SP, Android 4.3) and my tablet (LG G-pad 8.3, Android 4.4.2) - at first I could connect the with the SBrick just fine, but when the app wasn't working at all I disconected the device in order to try a clean start - then the phone and the tablet couldn't be connected anymore - also the message like on my friends phone doen't appear.
Is it possible, that when I disconected the SBrick form my phone (the only option is to tap "disaple connection with SBrick) that it was actually a lock for that connection and now it won't connect anymore?
How do I reverse that and is it even possible without beeing an Adroid programmer???
Thanks for you help,
best regards, miha
Nordic nRF Master Control Panel is a fantastic piece of software. Unfortunately SBrick-App still doesn't discover my SBrick (Nordic does).
In the meantime SBrick on my LG G2 didn't start anymore. It just closes one second after starting without any feedback. Had to reset my phone, as deleting all data and cache and force closing the app didn't do anything.
So... still no luck on my LG G2, I ran a few tests on a Moto G and a Galaxy Note 3 though:
(some old comment about APIs)
I'm considering diving into an Android App myself, but my guess is I don't have time for that in the next 4 months, as I have many higher prio-activities next to my regular workweek.
EDIT - Actually, I might as well have a look so I requested membership for development. I want this damn thing to be big success, so anything I can help with is a good thing.
[blockquote]Norman Chalcraft said:In order to check the visibility of an SBrick I have installed the utility Nordic nRF Master Control Panel. Using this can discover an SBrick, connect to it and even Bond with it.[/blockquote]
Thank you for program! Now I saw my bricks :)
At least we have three people with a problem "discovering sbrick..." using Galaxy S3. I hope we will not stay without attention!
Check it on your PC when logged in to play store
https://play.google.com/store/apps/details?id=com.vengit.sbrick
Does it list yor devices as compatible ?
And per info written here it does not support your version (only 4.3+ ) because of Bluetooth profile support
After another round of tests.
- linking and unliking profiles is a sure way how to crash the app, after two - three times it is a sure thing
- also playing with the profiles, port testing, assignment of functions, etc leaves the app in a state that it won't controll the SBrick althoug it is discovered. There are different level of disconnect - sometimes the port test works but profiles don't, sometimes after jumping the screen back an forth it starts working (not on first try), sometimes not event the port testing and LED light respond and restart of app and SBrick is needed
- sometimes I cannot choose anything from the menu - restart app
- here is my take on profiles as l
- Still haven't found a way to invert controls, tried the switches in the SBrick controll setup, but does not work for acceleration, steering nor sliders
I also found some (.json) files in the storage and tried editing those. But it does not seem to take effect, even when changing a single digit in one slider position. Other than that the descriptive language does not seem to be difficult, I'd suggest to release the option to hand edit the profiles for those who like to experiment. And describe some of the values and references.
I have the feeling that the HW received a good chunk of development, but the SW at least the Android one, is utterly lacking.
If you have problems in catching up, please go opensource ! Somebody else will...
Hi SBrick team
I received my SBrick with delay - after Christmas... it's fine ; )
But connecting it to my Samsung galaxy S4 mini or S3 with android 4.3 ends on permanent "Discovering SBricks"
I just realise that it is not only my problem...
What next ? I can wait but kids are disapointed for second time,
Greets & waiting for support
Marcin
I've been playing around with my 2 SBricks for a while. Well, play around, I tried to, but I'm having trouble getting them to work, the same with the App. I'm sorry to post this big pile of complaints, and I do expect a lot to be improved, but so far I'm underwhelmed.
The build quality of the bricks is excellent, as is the packaging. The rest is a nice touch... althogh I'm missing the instructions to build it into 42009 (actually I'll like to try and do that myself) Note that this is the most important part, software can be fixed on the fly.
So please bear with me while I spew out my complaints after playing around with the SBricks for about an hour, and the App for the past few verions.
First of all my LG G2 won't pair with the SBricks, my wife's Moto G seems to work every now and then but I'm getting messages about the PIN being denied, even though I can only assume there is no PIN to enter. The LED only flashed for a fraction of a second on startup. I've tried everything with my LG G2, it can see the bricks but not pair with them, de SBrick App will keep searching forever. Really dissappointing but really not something I can pin on the SBricks, who knows maybe my LG G2 is at fault here. I did unpair the SBricks to re-Pair, and they seem to be instantly deny the connection. I'm hoping for a Lollipop Update soon and/or I'll factory reset my device somewhere in the next few months, so I'll check it then.
So... Once I'm paired and SBrick will find the SBrick I can setup the controls, and all ports seem to function. I had to fumble around a lot to get anything to work. "All further steps will be explained through the SBrick app itself" is far from true. There's nothing in the App. Guessing and playing around with it will get you there...
I'm sorry to say the App is just the worst. I realize it isn't finished, but it's in a state where I wouldn't even release it to Google Play. The Menu sometimes doesn't work, brings you to the wrong screen, or just doesn't to anything, the back button is showing some really unexpected behavior as well. Available profiles are really rushed and the accelerometer worked on the wrong axis for me. Edit and Delete icons on top mostly don't do anything. If there is nothing to delete, or the delete button does nothing, don't display it. The background is horrible, I'd rather have a grey/neutral backgorund than the blurry half-repeating image thay is there now.
However, I like the structure of Sets and Profiles. Putting a title and an image in there is a nice touch.
The input of the App is really laggy, my SBrick took 0,5 sec to 1 second to even respond to some commands. Don't know why, but this is really bad.
I'm having doubts that the know-how is available to you for building a proper Android App, it seems that it was built by an inexperienced team. I'm sorry if that seems insulting, but that is how I feel about it's current state. The software is the key to the SBrick's usability and it's failing right now. You should consider bringing out an API as soon as possible, because there are a lot of Android Hobbyists out there that will blow this App away with something better in a matter of weeks. Get community support on this!
I hope you see my rant as the constructive criticism that I meant it to be. I might find the time to get into detail about the App and post some more specific problems I found.