[blockquote]Michael H. said:
how to force firmwareupdate?
both sbricks are still running firmware v4.1. i tried to update to firmware 4.40 using my iphone (5s, ios 8.x) and my android tablet (nexus 7 2013, android 5.01) without success. the apps are uptodate on both devices. the iphone app tells me to update to 4.40. update runs smooth, but after the firmware update the sbricks firmware is still unchanged. the android app request a update at every time. update in save mode stops sometime, sometimes it finishes. risky mode does the same and the firmware won't get updated. i tried to sbrick simple control app to update from 4.10 to 4.40, but the update progress allways stops after sending about 3000 bytes.
is there a solution or option to force a update?
regards
michael
[/blockquote]
This is exactly the same issue I have. iOS and Android apps complete the update without doing anything, and the simple app fails after a few kB.
how to force firmwareupdate?
both sbricks are still running firmware v4.1. i tried to update to firmware 4.40 using my iphone (5s, ios 8.x) and my android tablet (nexus 7 2013, android 5.01) without success. the apps are uptodate on both devices. the iphone app tells me to update to 4.40. update runs smooth, but after the firmware update the sbricks firmware is still unchanged. the android app request a update at every time. update in save mode stops sometime, sometimes it finishes. risky mode does the same and the firmware won't get updated. i tried to sbrick simple control app to update from 4.10 to 4.40, but the update progress allways stops after sending about 3000 bytes.
is there a solution or option to force a update?
regards
michael
Does not matter when did you restart your phone :)
Please download this simple control application? Does it work on your phone? Can you control the SBrick with this application?
https://play.google.com/store/apps/details?id=com.vengit.blecontrol&hl=en
Dear Makar,
Did you restart your phone after the firmware update?
Hi Marc,
The 1.7 verison was just a really small update in the android application. This isn't the new version.
Our developers working on a tottaly new application which will be available soon :)
But thanks for the bugreport. I don't see the main buttons on my phone (LG G3, lollipop) when I open a profil. What kind of devices do you have exactly?
Hi all,
I have upgraded both my phone (Lollipop) and my tablet (KitKat) to v1.7. Just a short indoor test tonight, should be able to test outdoor this week-end (depending on the weather!).
You guys forgot something when the app switches to full screen mode (i.e. when you launch a profile) : it's a real full screen until you touch the screen, then the top notification bar and the three Android main buttons come back. The bar and buttons should be deactivated, that's why we have the close button in the profiles, right ?
Marc
Chris, first of all, try the SBrick Simple Conrtol application. Tell me how's it going with that.
However, if you've paired the SBricks, and then made the phone to forget them, you probably won't be able to connect to them again from the same device until you do a successful OTA update to firmware version 4.4 with a different device.
Please try to acquire a different Androidphone, install SBrick Simple Control from the Play Store, connect to the SBricks and do OTA Update on them one by one.
NEVER unpair a paired SBrick that has a firmware version less than 4.4. It can cause the SBrick and the phone to work together. This is beacause the old firmware stores certain information about paired devices, and this can interfere with future connections. Firmware 4.4 solves this problem.
The phenomenon is described on this wiki page: https://social.sbrick.com/wiki/view/pageId/34/slug/android-sbrick-stops-working-after-ota-workaround
I am not sure that pairing first helped any. As I was not able see the either SBrick in the App. Once I told the phone to forget the Sbricks in the bluetooth settings, I was able to discover the Sbricks (line showing image and MAC address). However, I was not able to connect to them. Received this error message: "Could not connect to Sbrick. It might have been powered down or gotten out of range."
I am currently running SBrick App 1.7 Dated 9/17/2015 on a Motorola Droid Turbo (XT1254) with Android 5.1 standard non-rooted OS.
bachaddict: thank you for the feedback, yes we've also found that pairing can improve the situation, especially with Android 5.0.
Marc, Chris: we've released bugfixes to the official SBrick application, please update your apps and see if there's any improvement. If there's no change, try the "SBrick Simple Control" application, it uses the BLE engine of the new application still in development.
I have two SBricks via for my support the SBrick Kickstarter campaign. When receivd them, I added one of them to my technic creations, I was very disappointed the interface on both the IPad and Android apps. So much so that I threw both SBricks back in the box.
Today, I found them again. So I decided to see if things have improved.
Using my Ipad Mini and Motorola Droid Turbo, I updated the SBrick software. Using the IPad I was able to update the firmware on each of SBricks. IPad interface is still outdated and not very intuitive.
The Andoird App is no better if not worst. I can find the SBrick but I cannot connect to the SBrick, which mean I cannot test it any further right now.
It appears both of apps have been updated resently, which is great to see development is progressing.
Once I have played with both apps more, I will post more.
[blockquote]Tamas Misik said:
Our developers has rewrote the whole application...
[/blockquote]
Excellent :)
It's sometimes the best solution. v1 teaches a lot, to include the traps and mistakes to be avoided, then comes a time when you say "that's how we should have done it".
Let's wait a bit, so, I'm sure it'll be worth waiting!
Marc
I've had the same issue for months, over several updates - Sbrick visible, but no control at all. Sbrick Simple Remote finally gave me a clue when doing OTA - it fails at 2400 bytes (tried 3 times). That means the main app's OTA was also failing, but never reporting it. Firmware 4.3, App 1.6.1, Simple app 2.3, Android 5.0.2 on 2013 Moto G.
I will borrow an iPhone this week and see if I can get 4.4 on the brick.