- This topic is empty.
- Posts
Glad to see the new app & firmware. Although I haven’t made a proper measurement, I have the feeling that the data readout is a little smoother, and graph plotting less jumpy.
I noticed a couple of glitches:
Firstly, on exiting the app (pressing “back” from the connect page) I sometimes get the error “Unknown request code” and am returned to the measurement page.
Secondly, on connecting to the Mooshimeter it has sometimes forgotten the previous readout selections, and logging has turned itself on.One or other of these hiccups occur roughly half the time, but I can’t see any consistent cause. Nexus 5 with Android 6.0.1.
I haven’t noticed that glitch myself but I have noticed that it still has the glitch where after updated the f/w, it wants to go into f/w update mode even though I connected to the “mooshimeter” not the “bootloader”
not sure if it is just my situation or if other ppl notice that too
I have the same problem, but I borrowed my wife’s iphone to load and it gets stuck in the software loading loop on it as well. This has rendered an absolutely wonderful tool absolutely useless. What other options do I have?
I’ve also noticed my own phone/mooshimeter combo appearing to get stuck in firmware update mode, but I was always able to un-jam it by quitting the app (swipe it out of the phone’s app list) and putting the phone in aeroplane mode for a few minutes. Once I rebooted my phone, but I’m not totally sure it was necessary in order to reset the connection.
James has mentioned that Android’s bluetooth system is a bit of a mess. If it’s half as bad as Linux bluetooth, then it’s an absolute nightmare to work with. Other manufacturers deal with this by simplifying the wireless communication: not allowing firmware updates, requiring configuration buttons on the remote device, not having low-power standby modes, not having multiple data channels, etc. So really we’re lucky that somebody is trying to make something better out of a very complex and difficult technology.
Thanks Tim. It’s true the Android BLE libraries are pain. So much so that there are popular libraries that market themselves entirely on working around Android bugs. For example, SweetBlue. I actually tried out sweetblue at one point, but it didn’t solve the particular issue I was running in to and would require some deep refactoring of the mooshimeter app, so I skipped it. I may reconsider soon (the beta app is heavily refactored and would be easier to integrate the external library in to).
Joe – Sorry about the update loop behavior. I’ve tracked down that issue – the problem is that after you finish the firmware update, the Mooshimeter disconnects from the Android phone and needs to reconnect. But the Android layer caches what services are available from the Mooshimeter and, upon reconnection, tells the app that the meter is still in Bootloader mode. Rebooting the Android phone after a firmware update usually solves this issue. On some phones a full reboot is not required, and it is sufficient to restart the bluetooth subsystem (by either toggling bluetooth or setting the phone to airplane mode and back).
Hope this helps, or at least sheds some light on the issue. Thanks!
~James
