- This topic has 0 replies, 2 voices, and was last updated 5 years, 10 months ago by Anonymous.
- November 6, 2015 at 8:33 pm #5592kestrelGuest
I just pulled out my original run Mooshimeter. I believe that I left it in sleep mode. I wasn’t paying close attention, but I suspect it was already in the bootloader before I attempted to wake it up. I had just installed the latest Android app (released a few days ago) and it went directly to ‘bootloader’, I think before I attempted to wake the meter.
I have (re)installed the firmware about half a dozen times. I’ve reset. I’ve pulled and replaced the battery. On my Nexus 5 I consistently get what appears to be a good firmware load and then it returns to the bootloader with a firmware version. The Nexus 5 is running bone stock Marshmellow with one update that arrived about yesterday.
I also have a Nexus 9 running bone stock 5.1.1 also with an update that arrived about yesterday. …I don’t know why my 9 hasn’t receieved 6.0. It also has the latest mooshimeter app. When I use it to load the firmware, it also appears to load correctly. However, when the meter reboots the app reports bootloader with invalid firmware instead of a firmware version. After flashing with the 9, the 5 also reports invalid firmware until reflashed from the 5, then they both report bootloader with a firmware version.
This is an original run meter that has seen very, very little use. HELP?!
- November 6, 2015 at 8:46 pm #5595AnonymousGuest
To be absolutely certain that I had not just been catching the bootloader because of running apps, I just turned off bluetooth on both of my devices and then installed the batteries. Still bootloader when I then turn on bluetooth and start the app. However, I am seeing a different blink that I don’t think I saw before. 2 long slow’s followed by 2 short blips. This pattern repeats.
- November 7, 2015 at 1:33 pm #5609
That sounds like you’ve gone through all the steps I would suggest for diagnosing the meter, really sorry for the trouble.
Just making sure I understand: the pattern you’re seeing is 2 long slow blinks, 2 quick blinks, a few seconds of delay, then repeat from the beginning? Or is it 2 long slow blinks, 2 quick blinks, then just an occasional blink?
If it’s the latter, the meter might have reset to shipping mode somehow, try waking it up by shorting the Ω and C inputs together for 10 seconds or so.
One more question/thing to try: Is there an SD card in the meter? If so can you try removing and seeing if the behavior changes? Kind of a long shot but I’ve seen defective SD cards cause reboot loops.
If none of those are the case, I think you’ve done your due diligence so we’ll happily exchange the unit. This is the second unit we’ve heard of misbehaving after 6 months in the field so it’s important to us to get them back and understand any latent issues so we can address them.
Please follow up with firstname.lastname@example.org so you’re not posting addresses in a public forum.
Sorry again for the trouble, thank you!
- November 8, 2015 at 1:07 am #5630AnonymousGuest
I have same kind of symptoms when updating firmware with my htc one m7.
Fw-update seems to go as planned, but after reboot it says “Bootloader, Invalid firmware” and blinks steady 1 sec on, 1 sec off. This happens on every app-version after ~1.0.11 (not 100% sure, last tried to install everything i found few weeks ago)
But, everything works again, if i downgrade to 1.0.10 app and install fw 1426035947. Then i can update app to 1.0.16 and it works, as long as i would not let it touch the firmware.
I have also tried different batteries, with and without sd-card, tried that “wakeup routine” and so on. I’ll have to hijack another phone from some friend to see if that helps..
- November 8, 2015 at 4:29 am #5636AnonymousGuest
LG C70 did the trick for me.
Transfer was also faster with that cheap (but newer) phone at ~1500bps, my own htc one m7 shows speeds about 900bps (and tells that update was succesfull, then fails).
Now i just need to avoid fw-updates with my htc one m7, until this is fixed(?) or i got some newer phone..
- November 8, 2015 at 3:47 pm #5648AnonymousGuest
Solved! …mostly. I decided to go through all the steps one more time, taking note of everything I had learned this far. In that process I thought of the batteries. I had actually thought of them before, but discounted that possibility because of all the claims of low sleep power consumption, even with the radios on. Since I had always set the meter to shipping/no radio when putting it away and had made so very little use of it, there was no chance of dead batteries. Also, the processor was running and was able to reflash the firmware. Let’s check anyway…
…1.0 volts on each of them!
New batteries and it’s working again. But, the question of why they were dead remains. They were the original batteries it was shipped with.
New problem: I selected manual voltage range, it went to 600v range and the app crashed. It took me a while to figure out that that state was in the meter. After a battery pull, I got it going again. The app crash was 100% consistent on both my Marshmallow Nexus 5 and my Lollipop Nexus 9.
- November 8, 2015 at 11:21 pm #5656
Ville: I’m very happy you got it working!
Kestrel: I’m very glad you got your meter mostly working, HOWEVER: If I understand you correctly, you managed it by uploading an old version of firmware. I am quite sure this old version of firmware will give you incorrect resistance and current readings.
Both Ville and Kestrel: I am quite sure the culprit in the failed upload is the accelerated firmware upload (another user has reported, over email, similar difficulties). Unfortunately the accelerated process just seems to fail on some Android phones. Fortunately Google doesn’t have a long waiting period for uploading new apps.
So I see the clearest path forward as this: I’ll add a “legacy upload” button to the firmware upload page, which uses the old (and slow) method of firmware update, but obviously uploads the new firmware image. I expect to have this in place by Wednesday.
Further reading only if you’re interested:
Why is this happening: In the push to get the first run of Mooshimeters out the emphasis was always in measurement accuracy, reliability and making sure all the features work. Those earlier versions of firmware, and the apps, were written with the assumption that there was only one kind of Mooshimeter in the world. But the second manufacturing run has some subtle differences that the firmware needs to account for. So the new versions of firmware and the apps first check to see what version of hardware they’re dealing with and act accordingly, but the old versions will plow blindly forwards despite there being slight differences in the hardware.
Thank you both for your reports on getting around these issues, they really help in coming up with solutions. All the best
- November 9, 2015 at 4:24 pm #5666AnonymousGuest
No, I did not down grade to an older version. Let me try to summarize and be accurate:
My batteries were at 2.0 volts combined.
With low batteries, firmware updates using Nexus 5 running Marshmellow appeared to always work. Updates using a Nexus 9 running Lollipop may have always failed.
With the low batteries, the app always reported connecting to the bootloader and the LED on the meter was always a repeating pattern of 2 longs and 2 blips. I can’t say where in the cycle was the start/end. It could have been 2 blips followed by 2 longs, or some other…
Replacing the batteries without further changes to the firmware (had previously been flashed using latest app) made the meter functional.
Selecting manual voltage range results in 600v range being selected. Once it is selected, the app crashes immediately on connection. Restarting, deleting data and reinstalling all fail to fix it. The problem state is stored in the meter and meter reset was required to recover.
I was not expecting dead batteries. Should a early first run meter with very little used and stored in hibernate mode have dead batteries?
- November 9, 2015 at 6:11 pm #5668
Thanks again for the details. They really help nail the problems down.
I was not expecting dead batteries. Should a early first run meter with very little used and stored in hibernate mode have dead batteries?
I suspect your meter was affected by a power consumption bug that I fixed back in March – details here. I’ll just quote the relevant text:
In hammering out the logging feature I found a nasty bug that was causing excess current draw in standby mode. The bug raises the quiescent current draw from <10uA to about 300uA. This bug lowers the expected battery life of the meter to less than a year. So performing a firmware update is highly recommended! Technical explanation: The bug was one of the oldest in the book. There is an IO line with a 10K pulldown resistor on the MCU that was being driven high and not reset when the MCU goes to sleep.
So if you’ve just updated to the latest firmware, I think you are all set regarding the power consumption issue. Now, regarding:
Selecting manual voltage range results in 600v range being selected. Once it is selected, the app crashes immediately on connection
I don’t have a fast answer for this one, that’s very strange. I’ll test it out.
More soon, thanks again!
- November 14, 2015 at 5:45 pm #5825
I saw the crash report you submitted through Google Play – it was extremely helpful. I added a handler for the exception you’re experiencing in the latest Android app release. I haven’t figured out what’s causing the exception yet, but the handler should stop the app from crashing when the error condition occurs.
- November 15, 2015 at 1:52 am #5839AnonymousGuest
Just got 1.0.17 app and updated to fw 1447458797 by lecacy-mode with my htc one m7 (android 5.0.2, last official update) succesfully.
Is it possible that old hardware was not fully compatible with newer bluetooth-code and htc keep the old stuff with this phone? Or is there another problem that just fixed the same way? As you thought (and mentioned it beside lecacy-box) this problem should be fixed by android 5.0..
- November 15, 2015 at 5:16 pm #5850
I’m really happy the legacy mode worked for you. Thanks for the info.
I can’t speak to the specific combination of Android version/HTC phone you’re using, but the behavior of the bluetooth libraries definitely varies between manufacturers. It makes it quite difficult to support all these Android devices… This is why I made the “legacy mode” a check box the user could configure instead of just running a check in the background and forcing legacy mode on Android versions <5. On some 4.4 devices the accelerated upload works fine, on some 5.0 devices it fails. Honestly BLE on Android is a bit of a mess from a developer's perspective.
Sorry I can't give a more clear answer, I'm happy the legacy mode worked for you. Please let me know other problems as they arise.
- December 2, 2015 at 11:24 am #6048AnonymousGuest
the legacy mode does NOT work for me, I’m stuck with an apparently bricked mooshimeter because its app is buggy and I’m sent over and over again to do the bootloader. Aaargh. Back to my good old SK 100 Kaise. ‘cause this one still works after decades.
- December 2, 2015 at 12:31 pm #6051
Really sorry to hear that. Can I offer one more thing to try? If you have a friend or colleague with an iOS device, download the Mooshimeter app on their phone and then connect to your meter from that. iOS’s BLE stack tends to be much more reliable and once the new firmware is on your Mooshimeter you shouldn’t have to update firmware again until you choose to.
If that doesn’t work and you’re want to mail your Mooshimeter in, we can flash it with new firmware. If you want to go that route please contact us over email, email@example.com
- December 2, 2015 at 1:09 pm #6059AnonymousGuest
Tried this, too; but the iOS does not even see the moosh…???
- December 2, 2015 at 1:17 pm #6060
That’s very strange… Are you sure that the meter is disconnected from the Android device?
- December 2, 2015 at 1:18 pm #6062
Oh – sorry for double post – it would help to know the Android and iOS versions as well.
- December 10, 2015 at 11:21 am #6801AnonymousGuest
As the Android device never properly connected (at least not according to the moosh app which is stuck in bootloader) it’s hard to tell what REALLY is going on.
(is there a way to monitor this forum via email? going back to the site feels so 1980s…)
- December 10, 2015 at 2:30 pm #6817
Thanks for letting me know about the email issue in the forums, notifications are supposed to be an option but obviously it’s not showing up. Looking in to it.
You can guarantee that the device is disconnected from the Android device by turning off Bluetooth on the Android device.
I hope this helps, will write more regarding forum email notifications soon.
- October 18, 2016 at 3:03 pm #14522AnonymousGuest
I’m jumping on the thread here. My meter is doing the same thing on iOS. It starts the firmware update without asking. After it completes the update I reconnect and it trys to update again. The meter shows the correct version but it still keeps trying to upload. It never seems to get to the install step.
- October 22, 2016 at 12:26 pm #14539AnonymousInactive
I’ve had my Mooshimeter for a bit over a year and only used it once at the beginning right after purchase. I hooked it up today to use and was presented with the update which appeared to work however it continued to insist on an update even though the old and new version numbers matched the newest version! After changing batteries, re updating several times, ‘unlocking’ attempts, and clearing the app cache, I finally resolved by uninstalling the app and then re-installing. Hope this saves someone else some time!
- October 23, 2016 at 11:29 am #14555
Hi Zefram and Softsmyth,
I think a design choice I made is causing some confusion with users – right now, the meter boots up in “bootloader” mode, and it stays there for about 8 seconds before moving to “application” mode, where you can make measurements.
If you connect to the meter while it’s in bootloader mode, the app assumes you want to upload firmware and it will start uploading, even if the old version matches the new.
I’m going to add a warning on the app side to ask the user if this is what they want to do, because I suspect often the user is just trying to connect.
- April 13, 2017 at 6:00 am #16414AnonymousGuest
Same problem here. Has in storage mode for over a year and woke it today to look at something. Continually into boot loader mode, no matter how long I waited for it to boot. Tried iOS and Android.
New batteries and everything works!!!!
Old (original) batteries were at ~1.1v each.