Follow up.

I also have an iPod touch, I got the iOS app and everything there seems to work fine. I think the android app is broken on my Nexus 7. It’s running Android 4.4.4

What devices is the Android apk known to work on?

Yes, I also don’t see any readings in the Android app. I have a 2013 Nexus 7 and a Nexus 4.

I paired the Mooshimeter in the Bluetooth settings (not sure if this is required) and that had no effect. It does connect, and I can see the LED flashing at different rates when I change the sample rate. But the raw ADC values are always 0.

I downloaded the Android app again moosh.im/s/app.apk and it has been updated. It now works just fine.

I confirm the new apk also works for me.

I’m running an S4, and I get a message “there was a problem parsing the package.” I’ve tried two different internet connections, 4G and over WiFi, andb both display the same message. Android 4.2.2

I’m running a Galaxy S II Skyrocket (Samsung SGH-I727) with Android 4.0.4, and am also getting the “problem parsing the package message.” I’ve tried various download methods including using my desktop and transferring the file to my phone, and always get the same message.

Well I’m on Cyanogenmod 10.1.3 stable on the S4 and for me, it’s about as good as things get. I’d hate to have to upgrade my phone’s OS and risk stability just to use the Mooshimeter. What I might do is get a separate device and go from there.

My Google Glass runs 4.4 but I haven’t looked at porting options yet.

I just tried it and get the same error.

Updated from CM 10.1.3 to 10.2.1 (Final for CM10 on S4) and now the app works. Waiting to receive the meter in the mail so I can’t test it at the moment. Using the regular /s/app.apk not /s/alpha

James: I cannot easily upgrade to more recent Android builds because AT&T (stupid) does not currently allow it, and I’m reluctant to root the phone. Tried installing app on my wife’s HTC One VX (Android 4.1.2; also AT&T) and got the same parsing error.

James,

Thanks. My Mooshimeter looks so good and is so promising that I’m anxious to get started checking it out and using it. May be an opportunity to upgrade my phone…

Sincerely,

Gordon

Got the meter and am very happy with the hardware and case. On my S4 running CM10.2.1, I get an error in both versions of the app, the alpha and the main release. The error is: “Disconnect failed. Status 133.” Secondarily, I get “Turhing BT adapter off and on again may fix Android BLE stack problems.”

I’m reluctant to move to any newer version of CM because it’s fairly beta for me, and I need stability. So, I installed the app on my Note 2014 10.1 tablet running 4.4.2 Samsung build Android and get a usable app however it crashes semi-frequently when switching back and forth between meter mode and plot mode. Also, I don’t know where you want app feature requests, but I would like a lock orientation button somewhere and/or a switch button to go back and forth between meter and plot.

And…I’m back. Did not want to deal with AT&T regarding a phone upgrade (yet), so I found a reasonable (I think) tablet. It’s an HP 7 G2 with Android 4.4.2 and Bluetooth 4.0 LE. I loaded the original app.apk, and it found my Mooshimeter noting the following: Version 1.02, 20:CD:39:AO:AB:FD, Rssi -10dBm. But I could not do anything from there. The tablet’s built-in Bluetooth “sees” Mooshimeter V.1 as an “Available Device” and will pair with it, but subsequent trials of various apks (inc. app-stable.apk, app-latest.apk, and app-initial.apk) do not work. All of the apks say “Android device is not scanning…” The built-in Bluetooth still sees Mooshimeter V.1, but BLE apparently doesn’t as it just sits in a perpetual scanning state.

One more thing: I also checked the Mooshimeter’s batteries. They were OK, but a bit low, so I replaced them with new batteries: no difference.

James,

I do not have in iOS device handy, so have not tried that option.

James,

Did a master reset of my Mooshimeter and power cycled my tablet. BLE now finds the Mooshimeter, as does the tablet’s built-in Bluetooth. The Mooshimeter app initially sees my Mooshimeter, shows it as “connected,” but it soon goes to “disconnected” and subsequent connect attempts time out.

Hi Gordon and James – I have limited experience with BLE App development so the information provided is just in the interest of helping with the fault finding. I have come across 2 situations where intermittent connections are one of the symptoms – even if it is a single connection and then never again.

The first is battery power whether it is the Central (phone) or the Peripheral (Mooshimeter). From what you have described Gordon and the signal strength that the RSSI is reporting this is less likely.

The second case that I have experienced is where there is another device that uses the same Service UUID and the App missed one of the error checks to exclude this particular Service and Characteristic combination. The area of code that I had this issue with was the connect to peripheral and characteristic setting notification call (I can’t remember off the top of my head what the iOS method call is). The solution for me was to do a conditional logic of if/then/else and account for all conditions. I have only developed on iOS so I am taking a leap that a similar situation may occur on Android. Hope this helps and doesn’t confuse the issue.

Some progress: downloaded the app from the Play Store, and managed to update the firmware (although it took a few tries). My Mooshimeter is now consistently seen by my tablet, but will not connect (“connection failed: error 129,″ and connection timeout). I’ve replaced batteries (again; they don’t seem to be lasting very long), rebooted, and power cycled the tablet: same problem. Saw a friend with an iPhone recently, but he could not remember his iTunes password to download the iOS app, so will try that approach later.