Trifecta beta release: New firmware, Android App and iOS App

Hi Reader,

We’re releasing new apps and firmware for beta testing.  This post has a few details about the new versions.

THANK YOU to all of the Android beta testers. Since releasing the beta last month I’ve received great (and precise!) feedback that have really driven the apps and firmware forward.  Duane, Joel, shockwaver, Tim, MoFoQ, Paul… and others who have written both in the forums and over email, your contributions have been invaluable.

To join the beta program for Android, follow the instructions here.

Apple makes beta testing harder – please email with “join iOS beta” in the subject line and you’ll be added to the testing list.  The iOS beta app is presently under Apple review and should be available early next week.

Firmware Changes (from last beta release):

  • On reboot, logging is now off.
    • Previously it was on, causing unintentional logfiles.
  • Processing has been broken up so that the meter can talk to phones that only communicate with a 7.5ms connection interval.
    • Certain LG phones have this issue (tested against LG Volt)
  • Corrects issue where PTC resistance was not being compensated for on RevH hardware, resulting in roughly 8ohm resistance offset
  • Fixed a memory leak that was causing meters to crash when left unattended
  • Fixed a bug that was spuriously waking the sampling task, occasionally resulting in premature samples while logging
    • This could also result in deviance in the logged reading because the reference voltage didn’t have time to settle
  • LED blinking is organized and more meaningful now
    • 1 blink/sec: BLE connected
    • 1 blink/10 sec: BLE disconnected and advertising, no SD card
    • 2 blink/10 sec: BLE disconnected and advertising, SD card mounted
    • 4 blink/10 sec: BLE disconnected and advertising, SD card error
    • 1 blink/20 sec: BLE off, shipping mode
    • 3 fast blink: sample written to SD card log
  • Fixed an issue where the SD card could stay awake longer than necessary while logging, increasing power consumption
  • Changed behavior where a logfile is created when an SD card is inserted, whether or not the user has configured logging
  • Log settings are now saved to non-volatile memory so if the meter is spuriously rebooted, it will resume logging without intervention

Android App Changes (from last beta release):

  • Adds continuity beeper to Diode Drop mode
  • Adds battery checking when connected to legacy firmware (previously displayed blank battery icon)
  • Graphing mode settings no longer rely on “option” button
    • Not present on many Android devices)
  • Graphing mode now features split screen zooming
    • Left and right can be zoomed independently by using left and right side of the chart
  • Graphing number of samples on screen is configurable
  • Improves handling of dropped/repeated packets

iOS Beta Changes:

  • Adds continuity beeper
  • Adds battery monitoring
  • Improved graphing mode
  • Adds support for latest firmware
  • Improves handling of dropped/repeated packets
  • UI upgrades

What’s next:

After the beta apps spend a little more time in the wild, they’ll be pushed to production.  The consistent feedback from users since releasing the product is that they like the hardware but that the UI is very rough, which I completely agree with.  Hopefully these new releases are a step in the right direction.

The next feature on the list is streaming logs out over the bluetooth connection.  We’re also getting ready for another production run, I’ll write more details on that as they become available.

Thanks for reading



6 Responses to “Trifecta beta release: New firmware, Android App and iOS App”

  1. Tom Dunn June 29, 2016 at 6:28 am #

    The iOS beta disconnects from the meter when I hit graph. I’m using iPad with iOS 9.3.2. Before installing beta, the graph function worked. I’ve just started using beta today, and not much time yet, but graph was one function I had been using. I do like the thermocouple temp readout, and the updated channel function setup. Haven’t tried logging yet

    • James June 30, 2016 at 8:49 pm #

      Hi Tom,

      I just bought an iPad so I can do some better testing there. I admit I only tested the beta iOS release on iPhones. I’ll try to get it patched quickly.

      Thanks again

  2. Tom Dunn July 1, 2016 at 5:32 am #

    James, I saw another iOS beta update today, iOS App 1.70 (946) and upgraded. It took 15 to 20 attempts to get a successful firmware upgrade, it kept failing to detect meter in bootloader, but it did finally take. The new app still drops out when I attempt to graph, and it is now much slower when changing settings, and now drops out of tha app sometimes when changing settings ie. Changing function, or changing samples. Is this the proper place to report these issues, or do you prefer another method?

    • James July 2, 2016 at 4:11 pm #

      Hi Tom,

      Thanks for the report. The support forum is probably the best way to report bugs right now, I’m considering splitting off a separate forum for beta reports. Emails to also work. So the short answer is no, there’s no single channel to report bugs on, just whatever is most convenient for you. Your report is received though, I think I’ve addressed most of what you were experiencing:


  3. Peter cole July 5, 2016 at 11:48 am #

    Beta user here, trying to load firmware with latest app. I keep getting “failed to enter OAD mode”. Same result on 2 devices (LG phone and Nexus 7, Android 5 & 6 respectively). Also, a few times (not sure exactly how) Mooshimeter got hung (no blinks) and I’ve had to do a manual reset.

    • James July 6, 2016 at 12:00 pm #

      Hi Peter,

      Thanks for the report. Can you confirm what version of the Android beta you’re running? In release 27 I added a manual walkthrough for devices that aren’t capable of automatically rebooting the meter… I’m wondering if that failed for you or if you’re using an earlier version.


Leave a Reply

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.

This site uses Akismet to reduce spam. Learn how your comment data is processed.