- This topic has 0 replies, 3 voices, and was last updated 4 years, 7 months ago by Anonymous.
- September 2, 2017 at 12:49 pm #18786TimPGuest
My Rev1 Mooshimeter always goes to Bootloader mode on my Nexus 5 phone. I can’t get it to go to display mode at all. It displays 1477971088 as both the Current Build and New Build. Here are the things I have tried:
Replacing batteries (multiple times)
Power cycling the meter – dozens of times
Loading the firmware – multiple times
Rebooting the phone – several times
Uninstall and reinstall the app on the phone, with a reboot between.
Using a different device (Nexus 7)
Still no joy. In the past, it would do this repeatedly and after removing and reinstalling the batteries I would eventually get success. But no longer.
- September 2, 2017 at 2:27 pm #18787AnonymousGuest
I hope this gets addressed. I have the same problem on my S5 phone, and I’ve tried everything you’ve mentioned TimP.
It is completely unusable as is.
- September 8, 2017 at 7:10 am #18842AnonymousGuest
Same issue tried Samsung phones and a Droid turbo
- September 8, 2017 at 10:43 am #18846AnonymousGuest
I had exactly the same issue today (after the mooshimeter was logging throughout last night – with an failure code 460 after ~6hours and really strange ampere values after that – http://mooshigraph.strcmp.org/?u=59B2DF9F01495E72D1 – but that’s another story)
Anyway, today in the morning I wasn’t able to connect to the mooshimeter, because it wasn’t seen in the app (have 2 devices, Android 7 and 6.0.1 – both the same, tried multiple times) but the mooshimeter was still logging to SD as LED told, so I decided to let it run further and do my business.
In the afternoon the app seems to be able to connect but ends up exactly in the above described bootloader loop. (I have some screenshots but there are no further details). I tried most of the stuff as above with no success (incl. 2 or 3 times “updating” the firmware), then I decided to let the batteries out for some hours and do some sports.
After that, now in the evening, I put the batteries back in the mooshimeter, opened the app and it connected as it never has been anything, what the…?
The strangest thing now for me is, that this failure happend to other people at the exact same time – so I guess it hast anything to do with the application itself and the updating function (although there was no update!).
- September 8, 2017 at 12:37 pm #18851AnonymousInactive
I just read that there was an issue reported by Richard a time ago, that sounds a bit similar to these one:
- September 14, 2017 at 4:39 pm #18935AnonymousInactive
I’m seeing the same issue on a fresh install today. After successfully upgrading the firmware, the app refuses to stop asking me to upgrade the firmware.
Then, if I manage to turn off the firmware upgrade warning, which can only be reached by upgrading the firmware(!), the app spends many seconds initializing… every time I make a connection.
This is on a Moto G4 running Android 6.1
On a Nexus 5X running 7.x, which I first connected after the firmware was upgraded, I don’t have this issue.
- September 16, 2017 at 5:04 am #18967AnonymousInactive
I’m on a Nexus 5 (Android 6.0.1) and cannot reproduce the issue. My mooshimeter is already at the newest firmware version, though (1477971088).
When I changed the app to show me the dialog anyway (“There is a newer version of the firmware available, would you like to upgrade?”), selecting “No” still works (no upgrade dialog, just straight into the value display).
- September 23, 2017 at 5:09 pm #19031AnonymousGuest
I’m also having the same problem on a Galaxy S3. So what’s the solution?
- September 24, 2017 at 6:52 am #19035AnonymousGuest
I got my meter working. Here is what I did:
1. removed both batteries
2. removed SD card
3. hold reset button for 5 seconds
4. Use the App Manager to “force stop” the application
5. Use the App Manager to clear the cache
6. Use the App Manager to clear the data
7. reinstalled batteries
8. reran application
I’m not sure which step was necessary to get the meter working, but these steps worked for me.
- September 28, 2017 at 12:14 pm #19043AnonymousGuest
i’m in the same update loop and i have tried everything suggested,
i have tried 2 android devices and one ipad
current firmware is 1477971088 it is trying to update to same
- September 29, 2017 at 8:13 pm #19050AnonymousGuest
Same problem here current firmware is 1477971088 it is trying to update to same ios app
- October 19, 2017 at 11:25 am #19097AnonymousGuest
This usually happens when batteries are low: