when will the running application on android?
[blockquote]Javier García said:
To control the SBrick from profiles you have to asign one Sbrick to the profile and you have to asign actions for each of the four Sbrick's channels.
To do this you have to edit the profile and in the "linked SBricks" you have to select one of them and you get a new window with "Ports and Channels" where you have to asign actions to each port.
I hope this help you!
[/blockquote]
Oh, that's my fault! I did not realize i had to do this step. Very sorry! :( Now is working!
Thanks for your suggestion, Javier!
Hello Nico!
To control the SBrick from profiles you have to asign one Sbrick to the profile and you have to asign actions for each of the four Sbrick's channels.
To do this you have to edit the profile and in the "linked SBricks" you have to select one of them and you get a new window with "Ports and Channels" where you have to asign actions to each port.
I hope this help you!
Finally i got my Sbrick today. I use a N7000 (Galaxy Note 1) with SlimRom (cooked rom).
That is my feedback:
Finally got my Sbricks yesterday, but I'm having issues with the app on Android. I know it's still in Alpha, but I have some questions.
I can see the potential, but I'm really looking forward to being able to really test this thing out.
[blockquote]Philippe Hurbain said:
No, it works fine, no lag or commands that are repeated long after moving sliders back and forth. What I did see several times is the motor that keep on turning after I pulled my fingers off the screen. But it stops as soon as I hit the slider again.
[/blockquote]
Looks like it is not a phone problem I have the same behavior with my S4 (Gt-i9505) running 4.4.2
Maybe we need a firmware upgrade of the sbrick (like for ios) or an application fix.
X
[blockquote]Philippe Hurbain said:
No, it works fine, no lag or commands that are repeated long after moving sliders back and forth. What I did see several times is the motor that keep on turning after I pulled my fingers off the screen. But it stops as soon as I hit the slider again.
[/blockquote]
Exactly the same behaviour with my Sony Xperia Z1 Android 4.4.4
[blockquote]Matej Papluh said:
[blockquote]Maxim Baybakov said:https://www.youtube.com/watch?v=G4UFWNYyyEU[/blockquote]
Just a question, does the ASUS shows this behavior ? Please write to generic Android app thread if yes as not to break the thread. Thanks.
[/blockquote]
No, it works fine, no lag or commands that are repeated long after moving sliders back and forth. What I did see several times is the motor that keep on turning after I pulled my fingers off the screen. But it stops as soon as I hit the slider again.
[blockquote]ramiere benoit said:
Je regrette que cette aplication ne fonctionne que sur la version 4.3 alors que de nombreux smartphones, dont mon samsung trend lite ne disposent pas de cette version.
Pour utiliser ma SBrick je serait donc obligé de changer de téléphone ?
Il serait vraiment plus sympa de modifier l'appli pour qu'lle fonctionne avec la version 4.1 au moins.
[/blockquote]
Ce n'est pas l'application, mais le fait que l'OS Android ne prend pas en charge le profile bluetooth nécessaire. Il y a plein de tutoriaux pour flasher un téléphone sans risque, et les derniers firmwares samsung sur samfirmwares.com. A voir d'abord néanmoins si ton téléphone a bien le profile bluetooth BLE avant, car sinon, ça ne sert à rien (la sbrick a besoin de ce profile sinon elle ne peut pas communiquer avec le téléphone niveau hardware et ce n'est pas une mise à jour logicielle qui rendra la chose possible).
Bon courage.
Sylca
Je regrette que cette aplication ne fonctionne que sur la version 4.3 alors que de nombreux smartphones, dont mon samsung trend lite ne disposent pas de cette version.
Pour utiliser ma SBrick je serait donc obligé de changer de téléphone ?
Il serait vraiment plus sympa de modifier l'appli pour qu'lle fonctionne avec la version 4.1 au moins.
[blockquote]Jorge Pereira said:
[blockquote]Mihai Dreve said:
Using the sBrick app, I discovered my sBrick, assigned it to a MOC, but when I try to add a Profile, that screen is empty...
[/blockquote]
If you go to root (Home) menu, then Market, do you have Profiles? If you do (happened at least once to me when upgrading to an older version) try removing all Profiles then downloading all again.
You may also try clearing all aplicaton data and cache (tap it, App Info).
[/blockquote]
Jorge, you are the man! Such a simple action, totally slipped my mind. I was able to download all profiles, now I can assign them to my MOC.
I will test the sBrick as soon as I get a chance :)
[blockquote]Mihai Dreve said:
Using the sBrick app, I discovered my sBrick, assigned it to a MOC, but when I try to add a Profile, that screen is empty...
[/blockquote]
If you go to root (Home) menu, then Market, do you have Profiles? If you do (happened at least once to me when upgrading to an older version) try removing all Profiles then downloading all again.
You may also try clearing all aplicaton data and cache (tap it, App Info).
So, I finally got my sBrick yesterday, love how it looks, but let's talk about functionality, which is missing.
Using the sBrick app, I discovered my sBrick, assigned it to a MOC, but when I try to add a Profile, that screen is empty...
I am using the latest version of the Android app, I reinstalled it twice, I cannot use any profiles, thus I cannot use the sBrick.
Yes, I am doing this on an Android 4.4.2 device, with Bluetooth 4.0, as required. Any ideas? Thank you :)
So the 0.26 seems fix the port invert mixup. Good Job.
[blockquote]Maxim Baybakov said:
https://www.youtube.com/watch?v=G4UFWNYyyEU
The same problems in the port test
[/blockquote]
Now, this seems to be what I called lag on Nexus. Tried all the devices I have and the results are
Bad - Google Nexus 7, Motorola Moto G 1st and 2nd gen (all 4.4 and stock Android UI)
Good - HTC One M7 (4.3 plus HTC Sense 6.0)
It happens for sliders both vertical and horizontal (Test2 and Gamepad 2 profiles), and port testing screen too (other controls don't work for me). It seems to sample the sliding movement and buffer the inputs.
I did a quick test on port testing screen:
- if I keep sliding left/right the inputs are buffered.
- if I just click left/right, I can do it really fast and it seems OK
[blockquote]Denis H said:
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!!!!!
[/blockquote]
I too am using with 9398, as with Denis I'm using gamepad2 and noticed the motors often stay on even when the slider is released and resets. The last few updates seem to have reversed the sliders too, initially forward / back was reversed, then that was fixed, and now steering is reversed. :-)
At least I now know that the 4 on / off sliders next to the diagram of the brick in the linked brick screen reverse the controls!
All running on a Nexus 5, L5.0.1
[blockquote]Fernando Correia said:
[blockquote]Christian Treczoks said:a software like this would never, ever, be released.[/blockquote]
Yes, maybe not beta and still alpha quality. And then?[/blockquote]
I am well aware that software quality is no longer an issue today. A lot of software is thrown at the users in stages where it is not yet finished in the name of "rapid development". But a software that blows up at the second touch after it had several public iterations already? And how many times have we had the case of a "this bug is still there" in this discussion? Yes, ok, not all faetures are there, and bugs will lurk somewhere in the deep - thats alpha - but at least the shallow and reported bugs should be dealt with before any new release, even in alpha.
Hello again.
Finally I’ve received my SBrick and I’m like a child with new shoes!!
I have to acknowledge all the efforts made by Tamás Fábián so I could finally have my brick. Thanks again Tamás.
Yesterday, my son and I were testing Sbrick, , and despite the android app is not quite fine yet, we are very hopeful with SBrick and future developments.
I think that as a kickstarter project I knew there was an implicit risk but I think it is showing that the project works and has a great future ahead. These guys are making a great job so far. The hardware quality is very good and there is no relevant failures found so far. Android app has big issues, but still it allows to do some tests already and I am sure that soon improve its performance and options.
Cheers folks!
Hi Pedro,
You're right about the HW requirements and OS version not being properly communicated.
I think this was mainly because all the bus started around the use of iPhones with much less limitations, and Android being developed quite later.
The BLE compatibility started to be discussed at EB and I also made some explanations at TechnicBRICKs together with a poll to "measure" the compatible devices (from a list) that users itend to use.
But we should all realize this have been a joint learning process. Even until today Samsung Galaxy S3 was supposed to work and most S3 users had problems with it. Until a bug in the discovery process was found and fixed.
Eventual usefull info for the owners of older Android devices here:
https://social.sbrick.com/forums/topic/18/sbrick-support-for-android-phones-without-ble
At a certain point and because of the entensive discussion in som forums, everyone might get confident this was a widely known topic, but it is not.
Sbrick team should make the requirements more visible in the SBricks website, community, store, etc. Not only the Google Play app store.
Any help you may need, you know you can contact me. ;)
I'm soooooo glad connecting to the Samsung S3 now works properly! Good work Vengit!
But as often happens in SW industry, now that I can do more with it, there are also more issues to run into: :-)
This:
[blockquote]Maxim Baybakov said:https://www.youtube.com/watch?v=G4UFWNYyyEU[/blockquote]
Yup, having the same effect here, it seems to me as if using the sliders (or other controls) are sending each individual step from 0-255 regardless of the speed in which the user moves the slider. This seems to lead to buffering of all those commands and have them all executed in one iteration, whereas it should probably be time based.
I don't fully understand what the idea was to assign actions to the profile's elements. It seems that each profile may add profile controls to the available controls, and then you need to configure your sets sbrick ports and channels to match those.
I was testing my setup with a couple of profiles, as it seems natural to me that I can use different profiles for the same set. E.g. I may want to control it with a joystick now, but prefer a regular slider setup next time. However, the profiles are not aligned in their functions, which makes that impossible. For example:
I'm using 2 profiles: Test 2 and Joystick with 2 motors connected to port A and B. When I use joystick, I need to set the brick to use "Acceleration" and "Steering" whereas profile Test 2 requires me to set them to use Slider 1 and Slider 2. Wouldn't it make more sense to configure this per profile instead of per brick? So, on the profile you would configure which brick it should use and next for that brick specify which port should be linked to each function of the profile.