- This topic has 0 replies, 1 voice, and was last updated 8 years, 8 months ago by Anonymous.
- January 26, 2015 at 6:20 pm #1875Ben BuckGuest
Got my Mooshimeter in the mail today! Hooray!
I got it connected on a Galaxy S3 running Android 4.4 (Slim Kat rom version 4.4.2 build 4.1). I am able to connect to a meter and take measurements for usually less than 30 seconds at which point the meter disconnects (The app either freezes until I press the back button, or it reverts back to the connect screen with no message). Tried it on a Galaxy S5 with stock AT&T ROM, same issue.
Is anyone else seeing spotty readings in Android?
- January 26, 2015 at 6:27 pm #1876
That’s strange… I’m posting a new version of the Android app later tonight, it’s got a few stability fixes that may affect you. I’ll follow up when I upload it.
- January 26, 2015 at 10:25 pm #1881AnonymousGuest
I was having the same issue, FYI.
Moto X (1st Gen)
I deleted all the Bluetooth profiles on my device, and the problem seems to be resolved.
- January 27, 2015 at 2:39 pm #1905AnonymousGuest
Having the same issue with an Xperia Z2. I haven’t tried deleting all bluetooth profiles yet.
Andrew, did it keep working after you added bluetooth profiles back?
- January 27, 2015 at 3:30 pm #1909
Hi Andrew and Adam,
I made some changes to the Bluetooth backend in the latest build. If you’d like to try it grab the apk at moosh.im/s/alpha/app.apk
Let me know how it goes,
- January 27, 2015 at 4:20 pm #1911AnonymousGuest
Just tried it. Same resut at first, then I tried starting a screen recorder and now my meter doesn’t show up at all. I then removed all bluetooth pairings, rebooted phone, closed the app and deleted app data and cache and still nothing. Going to open the thing up and hit reset on the meter and see if that helps.
- January 27, 2015 at 4:22 pm #1912
Sorry you’re having trouble, keep me posted.
- January 27, 2015 at 5:07 pm #1913AnonymousGuest
Resetting the meter got it to show up again. The app currently disconnects after one reading. Video here:
- January 27, 2015 at 5:10 pm #1914
Interesting – thanks for the video! The app displays OVERLOAD as a placeholder text before the first readings are received, so I think the app is successfully connecting but failing to receive any readings at all.
What Android version is installed?
- January 27, 2015 at 5:21 pm #1915AnonymousGuest
It flashes one good reading (with all the green ‘A’ markers) and the voltage connected to the input before disconnecting. I’m running Android 4.4.4 on the stock 23.0.1.A.0.167 ROM for the Z2 (the most recent OTA build from Sony). If there’s anything I can do to help you with debugging just let me know.
The previous version got reaings for about 3-5s before disconnecting if that helps any.
- January 27, 2015 at 5:31 pm #1916
Hmm… very strange. Last question for now – when the app disconnects, is it because the meter resets? If the meter is resetting, you will see the LED blink solidly a few times instead of the normal “one flash per sample”.
I’m going to try to integrate log reporting in to the app so I can see what’s going on. More soon.
- January 27, 2015 at 5:49 pm #1917AnonymousGuest
I get a blip then 3 long blinks about 1s each so it is resetting.
- January 27, 2015 at 5:55 pm #1918
Bummer. That means something in the interaction between the meter and your phone is causing the meter firmware to flip out. I don’t have a quick answer for you, sorry, I’ll let you know when I come up with something.
“Android: Together not the same”
To marketers a slogan
To developers a warning
- January 27, 2015 at 6:18 pm #1919AnonymousGuest
No worries. I’ll take a gander myself if I can figure anything out between the two verions I’ve got. There’s not a debug serial port on the meter to log is there?
- January 27, 2015 at 6:22 pm #1920
Unfortunately no, no serial port on the meter.
I thought of two other experiments:
The meter has no elegant failure mode for battery death right now. Maybe when you wake the meter out of standby it is browning out. Can you try a fresh set of batteries?
One other experiment you could try is downloading a tool like BLE scanner and seeing if you can connect to the meter that way. You won’t be able to start sampling, but if the meter is just randomly dropping connection with a 3rd party app that would be indicative of something inconsistent on the OS level.
- January 27, 2015 at 6:48 pm #1921AnonymousGuest
Using this app
the device shows up and reports Generic Access Service, Generic Attribute Service, Device Information, and Unknown Service.
When it connects, the LED lights, then stays on for a few seconds, then shuts off. The BLE app remains connected. Measuring the cell voltage at the terminals I start at 3.030 (measured with Fluke 79III) and drop Immediately to 3.004 then back up to 3.006 when the LED goes off. When my phone sleeps in 10s the app disconnects and voltage rcovers to 3.030.
Connecting with your app shows a voltage drop to 3.007 upon connection then quickly going up to 3.022 when it reboots then 3.030 when rebooting is finished so I don’t think it’d be a brownout.
I can bring it into the lab tomorrow and see if I can get a roll trace and possibly a current measurement on one of our nicer scopes.
P.S.: So glad you used nice inserts for the screws so taking it apart like this doesn’t mess things up.
P.P.S.: Not sure how you have things wired up, but if you’re trying to get a debug serial port, sparkfun has a microSD breakout https://www.sparkfun.com/products/9419 which lets you get at the pins in the microsd connector with a minimum of hassle.
- January 27, 2015 at 11:04 pm #1922AnonymousGuest
Just tried clearing BT pairs and installing the new app. No changes, meter still behaves as before. The meter does not appear to be resetting when it disconnects (no long pulses on the LED). I have a fresh set of batteries in the meter as well.
- January 27, 2015 at 11:31 pm #1924
Thanks so much for the detailed report Ben,
I agree with your analysis – it sounds like the batteries are not the issue. I’d put money on this being a software issue. I haven’t uploaded today’s build yet (sorry, behind schedule), I’ll tweet when it’s up. It might be worth a shot.
Also do you know how to get Android logs with ADB? If so I’d be interested what the app is saying behind the scenes. I will try to add record gathering to the app so I can give you more useful information, this is something I should do anyway because I’m sure you aren’t the only one who will face a hairy problem like this.
P.S.: So glad you used nice inserts for the screws so taking it apart like this doesn’t mess things up.
Thanks! Yeah, was tempted at one point to design it with plastic snap tabs but worried about the lifespan.
P.P.S.: Not sure how you have things wired up, but if you’re trying to get a debug serial port, sparkfun has a microSD breakout which lets you get at the pins in the microsd connector with a minimum of hassle.
That’s helpful to know about, thanks! I rolled my own for debug, but your solution looks easier.
- January 28, 2015 at 12:34 am #1927
The plot thickens! I am now seeing the same behavior on my Galaxy S4 Active and a meter running production firmware. It’s happened a few times in a row now. If I can figure out what makes it go away for me I will let you know.
- January 28, 2015 at 11:23 am #1929
from last night
Very strange… it was consistently demonstrating the same failure you describe. I traced it to an error code 133 in the Android BLE stack (an error helpfully described as GATT_ERROR) when trying to write the meter settings.
Rebooted the device, turned bluetooth on and off, turned off all other radios (wifi and nfc), still same behavior. This was consisted for over an hour. Trying to figure out what I changed, I reverted the app to the version from a few days ago. It connected and worked. Upon reinstalling the latest version, that worked again as well.
Will let you know when I figure something out…
- January 28, 2015 at 2:10 pm #1937AnonymousGuest
Here’s the logcat. I cleared data, uninstalled the app, reinstalled the version I downloaded last night from moosh.im/s/alpha/app.apk, reset the meter with the button, started logging with CatLog, launched the app, hit the connect button, the meter then did the resetting flash, one reading appeared then the app bounced back to the radio scan screen. I then stopped the log and posted it below for you.
- January 29, 2015 at 3:02 pm #1970
Thanks so much Adam. I’ll check it out and get back to you.
- January 30, 2015 at 12:44 am #1976AnonymousGuest
The app up on github right now seems to be working for me. Now to figure out how to use it.
Thanks for all your help.
Please let me know if you’d like any more debugging data from me.
- January 30, 2015 at 1:20 am #1977
That’s great Adam!
Another thought occurred to me – maybe it’s the act of installing the app that makes the meter work again? Like I said, my phone went in to an identical error state for a while and was alleviated when I installed the old version. Maybe there’s nothing wrong with either version and installing the app clears some persistent data in the Android stack? That’s my working theory.
I’ll let you know if I figure it out, thanks!
- February 3, 2015 at 3:14 pm #2030AnonymousGuest
I think I have a similar issue. Meter shows up on the list, I hit connect, the screen shows overload for about 10 seconds then it takes me back to the connection screen. I tried on my LG G3 and a friends Nexus 4. The same problem occurred on both.
- February 3, 2015 at 3:20 pm #2031AnonymousGuest
A bit more info. When it takes me back to the connection screen the meter blinks its LED’s in the same way as if it was reset.
- February 3, 2015 at 3:22 pm #2032
Your crash report just hit my inbox, checking it out now.
- February 3, 2015 at 3:30 pm #2033
- February 3, 2015 at 4:36 pm #2034AnonymousGuest
Nice, I’ll give it a go now. One other bit of info that might be helpful. I tried and iPhone and it worked fine then I switched back to android and it also now worked. I hibernated the unit then woke it and the problem came back (and was fixed again by first using the iPhone).
- February 3, 2015 at 4:42 pm #2035AnonymousGuest
Just tried the update and it has the same problem. I hibernated and woke the meter up. Confirmed that the old version showed the problem. Uninstalled and installed the new one and it still has the same issue.
- February 3, 2015 at 5:32 pm #2036AnonymousGuest
Hmm I thought I replied. Are posts moderated?
I tried the update but it behaves the same. I found a fix though. If I connect to the meter with an iPhone then subsequent connections to my android phone work fine. If I hibernate the meter then the problem comes back.
- February 3, 2015 at 5:37 pm #2037
Posts to the forum go through a spam filter but are not manually moderated. Let me know if the forum keeps giving you trouble.
I see more crash logs… will check it out and let you know if there’s a revelation.
- February 3, 2015 at 11:10 pm #2039AnonymousGuest
Mine does close to the same thing on my android phone (Samsung S4, running CM12, android L), and android tablet (nvidia shield tablet running android L). In both cases I can see the meter, but when i connect the readings are all blank until it connects for an instant then it disconnects.
Like Phil noted, if an iphone connects once, then all android devices seem to be happy until a reset or sometimes if I disconnect the meter gets in a bad state and can’t be seen by anything. In that case I reset the meter and the iphone has to connect once to let any of my android devices connect.
I should note I’m running the latest apk you linked to in this post.
- February 4, 2015 at 12:32 pm #2042AnonymousGuest
I’ve got the same issue noted in this blog. I’ll be waiting for updates. I tried to get a logcat of the issue but I don’t have root so wasn’t able to obtain. I tried app.apk and app_latest.apk and both exhibit the same issue with showing “overload” then disconnecting from the meter. The LED flashes solid for 1 second on then off then on for 1 second then quick flash and it’s back to the connect screen.
- February 4, 2015 at 2:28 pm #2043
The good news is I’ve seen that issue come up here as well, so I think I can debug it. The bad news is I haven’t seen it come up consistently, so it’s tough to nail down. I’ll keep working on it and let you know when I have something, thanks. App progress should speed up once the last orders are out the door (<200 left!)
- February 4, 2015 at 5:21 pm #2045AnonymousGuest
Crashed on my droid S4. I tried an iphone, mooshi connected and stayed connected. Then the droid connected and stayed connected. I put mooshi in hibernation and the droid didn’t connect again.
James found a bug and has a new update. Now mooshi appears to work as expected. Very cool. Can’t wait for the logging feature to work.
- February 4, 2015 at 9:27 pm #2048AnonymousGuest
I’ve installed the latest app posted Feb 4th. It reads v1.02 but so did the last one I installed. I’d recommend rolling revisions on each upload.
I’m able to get readings for the last 10 minutes no problem. I’m questioning the accuracy but that’s another thread.
Thanks for all the hard work!
- February 4, 2015 at 10:01 pm #2049
Doh! Yeah, version number updates aren’t automatic right now so I forgot to change it. Thanks.
Let me know what accuracy issues you’re having – so far the accuracy reports from the field have been excellent.
- February 5, 2015 at 1:48 am #2052AnonymousGuest
Yup, nope; I think I have the same issue. My meter ran for a few minutes and now I can’t connect to it. I am using an HTC ONE M7, Android ver. 4.4.2
- February 5, 2015 at 2:07 am #2053
Did the app crash on you or is the meter just not showing up?
I just uploaded a new build that overhauls a lot of the issues that were causing instability…
or moosh.im/s/app-latest.apk if you always just want the absolute latest.
Give it a shot if it’s convenient.
Slowly but surely the Android app is getting more stable.
Hi Ty: The Android app now has auto-incrementing version numbers. Thanks for pointing that out!
- February 5, 2015 at 12:10 pm #2062AnonymousGuest
Good Morning James,
The app started up and ran for a few minutes, seemd OK though I can’t comment on the accurracy of any readings, I just goofed around with it. I turned the app off and after that, I couldn’t reconnect to the meter. The app started up fine and the meter showed up in scans but connection would fail or time-out.
I just downloaded app-latest.apk at 8:55a.m. pacific time ( where do I find the app version number?) No change that I can see. App starts up, scan shows one device in range, click connect and wait a few seconds….. I get “Device not connected”.
On the other hand, what a sweet little package!
- February 5, 2015 at 3:05 pm #2069
The version number isn’t exposed through the user interface at all right now (another feature for the list :-P). You can see the version through Settings->Application Manager->Mooshimeter. The version number is given at the very top.
As you know, the Android app is being updated quickly, so check back again soon. Since the app worked the first time and then stopped, I’m inclined to say it’s a process lifecycle issue that just needs to be hammered out. thing you might try is from Settings->Application Manager->Mooshimeter , force stop the app and clear all its cached data.
- February 5, 2015 at 4:52 pm #2072AnonymousGuest
Oh yeah… version number…. Apps Manager…I have got 1.0.2 (18)
Tried force stop and clear data but no change that I can see. The app still starts, the meter appears in the scan. After touching “connect”, I first get the message “Device disconnected” then “Connection timed out”
- February 5, 2015 at 7:20 pm #2074AnonymousGuest
Glad to help on the version number! As far as accuracy…after playing with it more it seems to be a matter of the reading oscillating for 2-3 seconds before it settles. In the case of a 10k resistor it may read megaOhms then ohms then finally settle back to kOhms and the correct reading. Sometimes it settles on a value a few kOhm off the correct reading. I have to take the probe off and re sample the resistor to get the correct reading.
- February 7, 2015 at 7:58 pm #2140
Sorry for the delayed response.
That is quite odd. Can’t think of what would cause a disconnect after roughly 10 minutes…
A few units have been found to have defective batteries. Have you tried resetting the meter, and if that doesn’t work, changing the batteries? I just put a video up of how to do that here:
Hmm… that’s quite strange indeed. I saw a behavior like that when I was writing the auto-ranging but I thought it had been hammered out. If you put the meter in resistance mode and turn off autoranging, does the oscillation still happen? My hunch is that when the meter switches ranges, for example from the 1Meg to 10k range, the current source is switching from 100nA output to 100uA output and it’s taking too long to settle. When it takes too long to settle it will give an out of range reading, causing it to switch ranges back to the old setting.
If that’s the problem it means a tweak in the autoranging code to allow a little more settling time in the next update.
- February 11, 2015 at 12:49 am #2232AnonymousGuest
Hmmm … Weird. I replied in this thread yesterday and I don’t see my reply. I think Phil (above) had a similar experience.
Yup, I replaced the batteries first thing. (I would have tested the old ones but my meter wasn’t working. tah dah tissshhh ) I did try the reset button to no effect. Uninstalled and re-installed the app. Forced stop and cleared data on the app. Tried holding common to ohms again, like the wake-up procedure. Anything else I might do?
As a diagnostic, I could try installing and running this on a different phone tomorrow if I get a chance. If that happens, I’ll let you know.
At this point is it just me left with this situation and everyone else in this thread is up and working?
- February 11, 2015 at 3:53 am #2233AnonymousGuest
Brett you’re not the only one, I’m waiting for stability improvements before I can even use it on all my devices. Waiting for updates and checking in once in a while with new app downloads.
- February 11, 2015 at 3:23 pm #2244AnonymousGuest
Just tried apk version 1.02(18) on an HTC ONE M8.
Android ver4.4.2 … No joy.
- February 13, 2015 at 9:15 pm #2282AnonymousGuest
I just installed the app from the iStore on an iPod. The app installed with no apparent problems and seemed to run OK and was even able to detect my mooshimeter as a bluetooth device but wouldn’t connect to it. That’s three phones and two OSes so far that my Mooshimeter won’t connect to. Maybe its not an app problem. Does anyone in the Vancouver B.C. area have a phone working with a Mooshimeter that I can test against?
- February 13, 2015 at 10:16 pm #2283AnonymousGuest
Hi again gang,
Just installed the app on an iPod. The app loaded OK and seemed to run OK. The app could see my Mooshimeter as a bluetooth device but it wouldn’t connect to it.
So far then, I have tried to connect my Mooshimeter to three different phones on two different OSes. I’ve done hard resets and re-initialised and cleared app data etc. each time. I wonder now if maybe its the meter.
Is there anyone in the Vancouver B.C. area with a working Mooshimeter that we could test against?
- February 16, 2015 at 11:08 am #2302AnonymousGuest
I have same issue as Adam. Did not change batteries but monitored battery voltage and saw only 0.02v drop during connection attempt so I think batteries are good. Tried BLE scanner, it does not cause reset – so I am thinking OS level is fine? Android 4.4.4 on Samsung Galaxy S5.
- February 16, 2015 at 11:12 am #2303AnonymousGuest
(I would report Mooshimeter app version but I do not see where that is reported. The reason I did not change batteries is I was uncertain how without exerting more force on PCB than I felt comfortable, and battery voltage looks OK)
- February 16, 2015 at 3:13 pm #2304
Sorry it’s giving you trouble guys.
Benjamin: You are right to be cautious about exerting too much force on the pcb. If you haven’t seen the little video I made about how to change the batteries, check it out here:
Brett and Benjamin:
I’m working on improving the firmware update interface now. The fact that you can see the meter on your phone is encouraging and leads me to believe it might be a corrupt firmware issue. But if you haven’t tried uninstalling and reinstalling the apps and rebooting your phones yet, give that a shot. I’ll try to have a build available for you later today that will let you force a firmware reload. More soon,
- February 17, 2015 at 8:13 am #2314AnonymousGuest
Yup, I have tried reloading the app, reloading the app and rebooting my phone, pulling the bateries, hard reset, clear app data, raising one foot and facing the east while reloading the app. I think I’ve tried everything. I’ve also tried several different phones so yeah, I kinda suspect that there’s something at the meter end. Incidently, I noticed another thread from someone with the same phone and Android version as me and his meter is working so maybe it isn’t just a compatibility issue, plain and simple. Weird huh?
- February 17, 2015 at 10:21 am #2316AnonymousGuest
Thanks. Just FYI I tried reinstalling app to no avail. Version shows as 1.02. The update you supplied fails to update, claiming that the app is not installed. That was true both before and after I performed the reinstall.
- February 24, 2015 at 8:37 am #2381AnonymousGuest
I have seen in some other posts that people have been doing firmware updates but I am not able to find instructions. Are there some instructions somewhere?
- February 25, 2015 at 10:11 am #2396AnonymousGuest
I have a LG L70 , and i downloaded the app, the phone detects the mooshimeter, but when i click connect, doesn’t appear the next step.
Bluetooth v4.0 A2DP
Android OS, v4.4 KitKat
- February 28, 2015 at 7:34 pm #2440AnonymousGuest
joy – on the home page I see the Android app is now available via play store, so I tried this. That time the upgraded succeeded, and – I can stay connected!
Now I’m hoping to get a pretty sine graph of the AC utility power 120v rms, haven’t gotten that to work. But, this is definitely progress! :) I can’t wait to see it all come together.
- February 28, 2015 at 10:14 pm #2441AnonymousGuest
Hey Ben Mord. Great news! +Yup….nope… Bummer. I just did a hard reset on the meter, uninstalled the app, reinstalled the app from “google/play” and….hey,… yeay… no. Bummer, I still get “connection failed, error 129”. Are there still others with this problem? Has anyone else solved this problem? I’m starting to feel like the kid who didn’t get picked for dodgeball….
- March 1, 2015 at 8:52 am #2443AnonymousGuest
Yeah! I got the firmware updater to run. Took a few minutes but seem to run OK. Still can’t connect though to the meter though. Still get “connection failed. Status 129” So stoked…then so bummed. I feel a haiku coming on.
- March 1, 2015 at 4:43 pm #2447AnonymousGuest
Hello James et al,
We now have an iPhone 6 in our house. I tried connecting to that. The iPhone could detect the mooshimeter but wouldn’t connect to it. I was able to update the firmware from my Android phone. Is it the case that the firmware is OS specific or somerhing? If not, this will be the 6th phone and the 5th OS that I have tried without success. Can you suggest anything else I might try?
- March 14, 2015 at 4:44 pm #2566AnonymousGuest
I kinda shelved my Mooshimeter for a while, other things to do, but I had a few minutes today so I checked Play Store and found that there was a new firmware version… Oh boy. I installed the new app version, sparked up ( and reset) my meter, installed the new firmware on the meter … and …. CONNECTED Yeah! I kid you not; The sun actually came out just at that moment.
So I’ve been runniing around the neighborhood measuring everything and its all good. I may not have enough Mooshimeters though.