- This topic has 0 replies, 1 voice, and was last updated 8 years, 9 months ago by Anonymous.
- January 20, 2015 at 9:52 pm #1790Richard SmithGuest
I got my 2 meters today. I’ve woken both of them up and I can connect to either one of them and I see the led start to flash. However, I can’t get a voltage or resistance reading out of either one.
Voltage always shows zero and resistance always is -007.90
The preferences screen comes up blank and About does not produce anything.
Does the android app work on a nexus 7 (2nd Gen) ?
- January 20, 2015 at 10:19 pm #1791AnonymousGuest
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?
- January 21, 2015 at 9:03 am #1792AnonymousGuest
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.
- January 22, 2015 at 11:25 am #1796AnonymousGuest
I downloaded the Android app again moosh.im/s/app.apk and it has been updated. It now works just fine.
- January 22, 2015 at 4:51 pm #1802AnonymousGuest
I confirm the new apk also works for me.
- January 22, 2015 at 5:10 pm #1806
Great to hear the new binary worked for you – I uploaded it last night. It’ll be updated quite frequently over the next few weeks, I’ll poke the main mailing list next time there’s an update.
- January 25, 2015 at 4:48 am #1839AnonymousGuest
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
- January 25, 2015 at 11:38 am #1840AnonymousGuest
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.
- January 25, 2015 at 3:32 pm #1842
Hi David and Gordon –
Android BLE support got much better with version 4.4 and that’s what the app is presently built against. I think it should run in 4.3 but I haven’t tried it. Is it possible for you to upgrade your Android OS?
- January 25, 2015 at 4:08 pm #1844AnonymousGuest
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.
- January 25, 2015 at 4:12 pm #1845
I rolled a separate version of the APK that should support back to 4.0. I don’t have an Android 4.0 device to test with though.
Would one of you try downloading it and giving it a shot? If you can connect and get readings, I’ll merge the changes in to the main branch.
- January 25, 2015 at 4:15 pm #1846AnonymousGuest
I just tried it and get the same error.
- January 25, 2015 at 4:18 pm #1847
Acknowledged, found an error in the build. Will have a new binary for test up in a few minutes.
- January 25, 2015 at 5:17 pm #1848
Sorry it’s taking a while. The app is using parts of the API that were only introduced in Android 4.3. So I am looking to see how far back I can make the app compatible without a total refactor.
- January 25, 2015 at 6:22 pm #1849
So I’ve tested in Android 4.3 and it should be OK. Unfortunately there were several substantial changes between 4.2 and 4.3 that require some deeper revision to the code. I’ll revisit this later to see if a backport is possible.
For Cyanogenmod – it looks like BLE is not supported until 10.2. If you can get to 10.2 the app should work.
- January 26, 2015 at 12:38 am #1867AnonymousGuest
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
- January 26, 2015 at 12:41 am #1868
Excellent! You’re the only CM user I know of so far so let me know how it goes.
- January 26, 2015 at 9:41 am #1869AnonymousGuest
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.
- January 26, 2015 at 1:03 pm #1872
I just looked up the specs for both the Galaxy SII and the HTC One VX and confirmed what you already know… An additional issue with the Galaxy SII is that using Samsung’s Android releases it doesn’t support BLE at all (according to the wikipedia page) even though the hardware is theoretically capable and can be made to work if you root it.
As for the HTC One VX, I’ll see if I can get the Android app building for earlier versions of Android soon, but right now I have to focus on fulfilling remaining orders and fleshing out some of the features still missing from the app. I’m very sorry to make you wait longer, I’ll try some backporting experiments soon. A lot changed between Android 4.1 and 4.3.
Let me know if there’s another way I can help in the meantime. Best,
- January 27, 2015 at 10:26 am #1903AnonymousGuest
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…
- January 28, 2015 at 6:34 am #1928AnonymousGuest
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.
- January 28, 2015 at 11:29 am #1930
Please post feature requests to the Github repository under “issues”:
Yes, the Android app is definitely still a little rough. The nice part about software is that it can be updated easily, expect it to improve soon.
Error status 133! I’ve been battling that as well. Unfortunately that status simply means “GATT_ERROR”, which is the almost most generic error code available for the bluetooth low energy stack. It seems to indicate stack instability but it’s unclear where. Anyway, working on it, more soon!
- February 8, 2015 at 12:03 pm #2167AnonymousGuest
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.
- February 8, 2015 at 12:07 pm #2168AnonymousGuest
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.
- February 8, 2015 at 2:46 pm #2175
Running through my mental checklist… bluetooth is clearly on, you’ve reinstalled the app, running Android 4.4… the best suggestion I can offer right now is to try rebooting the device. The Android app is being updated frequently, I’ll let you know when there’s a new update to try.
Just an idea for an experiment – does the meter work when connecting from an iOS device?
- February 8, 2015 at 9:10 pm #2181AnonymousGuest
I do not have in iOS device handy, so have not tried that option.
- February 8, 2015 at 9:52 pm #2182AnonymousGuest
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.
- February 9, 2015 at 7:23 pm #2207AnonymousGuest
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.
- February 10, 2015 at 5:21 pm #2226
Sorry, I don’t have any fresh ideas. I have made it a priority to improve reporting of error logs from the Android app so I can see what’s going on though. Presently the app only sends a log if the app crashes, but I try to add a way to send the logs without a crash. Hopefully we can get this figured out.
Thanks! I only wanted to add that it’s probably not a case of overlapping service IDs. The Mooshimeter is using full 16 byte UUIDs, the base of which was randomly generated. I need to add the battery notes to the troubleshooting/FAQ page though.
- March 1, 2015 at 1:58 pm #2445AnonymousGuest
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.