Topic | Mooshimeter App update Bug

Home Forums Mooshimeter Support Mooshimeter App update Bug

Viewing 8 reply threads
  • Author
    Posts
    • #15043 Reply
      Anonymous
      Inactive

      The mooshimeter app update option needs work. The option to skip the upgrade is only available after “fully connecting” (where the measured probe values are visible, not simply showing connected via the icon in the list of scanned meters).

      The big problem in my case, the meter shows FW 14779791088, but the app still forces (No option to skip at this point) an update to 14779791088 (yes, it tries to update to the EXISTING version); success message/reboot; forces update again. This effectively makes the device useless below 50% battery life. Why not have an option in the Scanned-Meters display to skip the upgrade? For that matter, as a feature request, I’d love to see the app save the previous 2 firmware revisions for easy rollback.

      I’d call it “acceptable” not to be able to update firmware below 50% charge, not being able to use the meter at all and having to figure out why (reinstalling the app, deleting and reinstalling, installing the app on a second device, power cycling the device repeatedly) is not.

      Details
      IOS 10.11
      Mooshimeter app version 1.09 (1346)
      FW 14779791088

    • #15062 Reply
      admin
      Keymaster

      Hi Louie,

      Thanks for the report. I think a default in the app that some users are hitting is that if the app connects to the meter while it’s still in bootloader mode, it will jump straight to the firmware update page. The meter is in bootloader mode for 8 seconds after rebooting, so after a successful upload if the user doesn’t wait long enough, he can end up seeing what you’re seeing. I think this is a counter-intuitive behavior, so I plan on adding some behavior to maybe force the user to wait 8 seconds at the end of a firmware upload. Do you think this is the update loop you’re experiencing?

      Best
      ~James

    • #15064 Reply
      Anonymous
      Inactive

      That is absolutely not what is happening. This occurred numerous times within the 8 seconds and many more times well beyond 8. We’re not talking a couple of times, probably more like 30 until I saw the issue with the battery charge below 50% and threw in some new batteries which fixed the issue immediately. (I did try a hard reset via removing batteries before moving to new ones).

      The icing on the cake to this issue is you can’t actually view the battery life while it is in this state :/

    • #15069 Reply
      admin
      Keymaster

      Hi Louie,

      Thanks for the clarification, and sorry for the continued trouble.

      It sounds like something I haven’t seen before. Can you email me at james@moosh.im with shipping information and we can arrange a replacement?

      Best
      ~James

    • #15073 Reply
      Anonymous
      Guest

      Hi James,
      I grâce the same problem as Louie,
      My mooshim is trying To reprogram it self on
      each connexion…

      I haven’t yet tried new batteries as did
      Louie for fixing thé issues…
      But my batteries are down 50%…
      I live in Central Africa and need support
      on this issue

      Best Regards.

      Didier NZANZU

    • #15074 Reply
      Anonymous
      Guest

      Hi James,
      I have the same problem as Louie,
      My mooshim is trying To reprogram it self on
      each connexion…

      I haven’t yet tried new batteries as did
      Louie for fixing thé issues…
      But my batteries are down 50%…
      I live in Central Africa and need support
      on this issue

      Best Regards.

      Didier NZANZU

    • #15075 Reply
      Anonymous
      Guest

      I am seeing some similiar behavior. Using an Android tablet occasionally on initial connection the meter will go into the Firmware update mode. It has the latest firmware and tries to reload the same version of firmware.

      Not sure if this a pilot error problem or a bug with the App?

      I have not paid full attention, but it might be that when the meter is found on the connection screen, I may be touching the meter description at the top of the page rather than waiting for the meter display to show up??

      I have only used the meter a handful of times so far, still tying to figure out the quirks of the App.

      I found that if the meter is Logging, you cannot force the meter into Shipping mode directly, you first have to stop the Logging, then put the meter into Shipping mode. Might be useful to have a pop up message that the meter is Logging and the Logging feature needs to be turned off before putting the meter in Shipping mode.

      j

    • #15077 Reply
      admin
      Keymaster

      Mr. Nzanzu,

      Please let me know if the problem persists after trying the update with fresh batteries. This is the issue for most failing firmware updates. Also please let me know what kind of Android phone you are using so I can look for patterns.

      Jfoj,

      Thanks for the note regarding going to shipping mode while logging enabled. I’ll add it to the issue list.

      Thank you both –
      ~James

    • #15108 Reply
      Anonymous
      Guest

      Same problem here. Meter would indicate that it already had the latest FW version but would always download it over and over. Additionally, I could never Set the device name. And occasionally the Logging:OFF / Logging: ON toggle would not toggle. And occasionally the SD card would report that an error had occurred. The battery voltage was below 50%

      So, tried different SDHD card (32GB, extended FAT32 format under Windows 10 in Parallels window on iMAC). Removed batteries, waited, pressed reset button (?), and installed new batteries. Seems to work properly now.

      I’m assuming that being able to email your SD logs from an iPhone 6S, latest iOS, depends on having the beta app? From the metering page the logging ON/OFF button never goes to any other page.

Viewing 8 reply threads
Reply To: Mooshimeter App update Bug
Your information:




This site is protected by reCaptcha and the Google Privacy Policy and Terms of Service apply.

The reCAPTCHA verification period has expired. Please reload the page.