-
-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with Sanitas SBF70 since version 1.7.2 #252
Comments
I take it version 1.7.1 worked well for you? |
Yes 1.7.1 was working well. |
Please try the dev version and let me know if it works better for you. |
Just tested the new dev version but sorry, didn't solve the problem. |
Can you go to settings -> about and enable the debug log. Then try to connect to the scale and then attach the debug log here. |
Make sure you use the latest dev version when you do this. |
@nazco: can you provide the debug log? Need it to get forward with this. |
Sorry, has to wait until friday. |
@MartinNowack, @jflesch, @weliem: do anyone of you have this scale and if so, do you have issues with 1.7.3? Can you provide a debug log? |
@erijo I have this scale, but am currently running on 1.7.2. I've managed to reinitialize the scale to start re-associating my data to my account, I'll report if I end up with issues once 1.7.3 is pushed to the device. |
Hi. Keep up the good work 👍 Debug log |
Please try the latest dev version and attach the log. |
It should be the latest dev version, downloaded today. |
Yes, but I did a change after reading your log so I wanted you to test again with the new version. |
Ok. 2018-05-03 19:38:57.530 Debug AboutPreferences: Debug log enabled, openScale (dev) v1.7.3-dev_d9b8c625 (1525359575), SDK 24, motorola Moto G (5) |
Can you try searching for the scale in Bluetooth settings (in openScale) with the debug log enabled? Also, can you enable the Android bt snoop log and attach it as well? |
I just tried with developer mode and hci debugger. Stack trace: User actions: |
Here is the openscale debug log 2018-05-03 20:57:55.970 Debug AboutPreferences: Debug log enabled, openScale (dev) v1.7.3-dev_d9b8c625 (1525359575), SDK 24, motorola Moto G (5) |
I can't share the results from the hci debugger. The app crashes every time I press share.... Sorry but my skills are a bit limited... ☺ |
Hopefully fixes the crash reported in #252.
Please try again with the latest version and post the debug log. |
Tried it. No fix 2018-05-04 11:37:05.381 Debug AboutPreferences: Debug log enabled, openScale (dev) v1.7.3-dev_a3f64be6 (1525385180), SDK 24, motorola Moto G (5) |
It would be nice to have a BT log. Can you try again to capture the log as described here? |
Ok now bt fault logger worked. |
Can you provide the same type of log when you connect with the vendor app? |
I checked the zip file just now (on my phone, so I might have missed it) but couldn't find the bt snoop log. On my phone (Nexus 5X) I had to, after enabling the HCI snoop log, turn Bluetooth off, then on again and finally reboot my phone for the log to turn up. |
You can also check if the log is stored in /sdcard/btsnoop_hci.log on your phone. |
It's anyone able to provide the requested log? |
Since no one is answering, the problem doesn't seem so big. I'm gonna close this until somebody has some new input. |
I added some more debug logs. Could you please try the dev version again @ReidarHH and attach the log afterwards? |
First of all, I'm sorry for the late reply. I've been very busy. This last update did the trick. ☺ Now it is importing all previous measurements. Excellent work Erik. ☺ 👍 |
@nazco: does it work for you as well? |
For the record: problem was most likely fixed by 3f11e55 |
Works with the development version under android 8.0.0 but not with android 7.1.1. |
For info, my phone is running android 7 |
@nazco: please restart the device and see if it works then. If not, please attach the openScale debug log from trying to connect with the dev version. |
Sorry, I currently do not have access to the scale. @nazco I think increasing the sleep value is not the right solution. It covers hidden timing issues. For example, if the phone is under load, the value might not be enough. On the other hand, without load, the thread unnecessarily sleeps too long. |
@MartinNowack: from what I gather from reading a lot of comments on stackoverflow and other places, BLE on Android seems to suck big time. I'm not particularly found of sleeps neither, but it seems to be necessary on some devices to get a stable connection. But I'm open for any other ideas you or anyone else may have. (But I would still like to see the debug log from the dev version when you have time @nazco.) |
I will add some logs over the weekend. |
I think what @MartinNowack pointed out with the timings is right. I tried to collect the logs yesterday and this time the problem with the connection occurs again with just a slightly higher system load due to a running spotify. Here is the debug log.
|
I'll try it the next few days but I have to mention that the previous version worked or didn't worked in a very non deterministic way so I need some time to check if it is really solved. |
Have you had time to test this yet @nazco? |
Not yet sorry. I'll try to start with some tests this weekend. |
Couldn't see any problems with my android 8 device in the last 3 days with the latest development version. But could't test is with other android versions. |
Well, sorry it seems that with the latest dev build there is a new problem introduced. Now I need to have the app open and running to get values. Older values are ignored and not synced. I'll try to add a log tomorrow. |
I will close this issue due inactivity. |
Well the problem persists. |
After updating openScale on my Android 7.1.1 I can't receive data from my Sanitas SBF70 anymore. OpenScale informs me about a successful connection and then after a few seconds it tells me that it lost the connection. No data is received in this time. Maybe it is liked to the bluetooth optimizations mentioned in the release notes of 1.7.2. I also just updated to 1.7.3 but the problem persists.
The text was updated successfully, but these errors were encountered: