Topic | Initialization failed:status 1

Home Forums Mooshimeter Support Initialization failed:status 1

Tagged: 

This topic contains 16 replies, has 2 voices, and was last updated by  Henry 2 days, 14 hours ago.

  • Author
    Posts
  • #16867 Reply

    Brett Richard Johnson

    I carry two mooshimeters most of the time. Today I can’t get either to work. I can see them during scan. If I connect to either one, I get the error initialization failed ; status 1. Both meters worked fine until as recently as the last day or two. I have a new Pixel phone with android 7.1.2 . I think I got an update, maybe on the 3 so that may have something to do with it. Anyone else experiencing something like this?

  • #16919 Reply

    Roland. Heinl

    Hello,

    I had the same issue.
    It was working with a newer Android 7.0 Version and stopped
    a few days ago.
    But it was still working with an older android version and smartphone.

    I had the same gueswork like you.
    I tried a few setup changes an couldn’t solve the problem first.
    Now I decided to try a few hardware changes.

    I didn’t have a SD card in the slot yet. So I put a 16 GB SDHC card in the slot, made a reset, connected again and now it is working.

    Hope it’ll also help you

    Good luck

  • #17470 Reply

    René Arts

    I am experiencing the same issues with Android 7 on my Lenovo P2.
    Tried replacing batteries, reinstalling the app.
    I feel it should not be necessary to place a SD card to be able to properly use the Mooshimeter, which I really love working with, though currently I am heavily disappointed by these issues!
    Has anyone already found another (temporary) workaround?

  • #17798 Reply

    Brett Richard Johnson

    Yup…. Nope… still struggling with this. So bummed. I actually went and bought a regular multimeter today because I couldn’t get either mooshimeter to work. I am pretty sure it happens when my phone and I walk out of the meter’s bluetooth range but once I do that, I can’t connect to either moosh so does that seem like a problem at the phone end, rather than just with one meter?
    I have a bunch of other bluetooth devices, mostly speakers and headphones, and they don’t seem to die if I walk out of range. They just go to sleep and wake up when I get back. Mooshimeters become zombified and to recover one, I seem to have to reload the firm ware in most cases. This sort of relegates my mooshimeters to the bench for now and I’ll have to take my new dumb meter for field work.
    working in green bush
    lights, relays, unlabelled wires
    no moosh, much bummage

  • #17831 Reply

    René Arts

    Mine does work from time to time, though I haven’t figured out the condition(s) which triggers it to connect again. The indicator LED is still flashing every 10 seconds, and flashes every second (like while it is connected) while the app says it is initializing.

  • #18198 Reply

    JP

    I have the same problem now, was working great, can pait under Bluetooth, but in the app it’s always the unplugged icon and initialization failed -1

    Seems there is no app update, no firmware update. Anything I can do?

  • #18404 Reply

    Infinion

    I’m having the same problem. Only reprogramming with bootloader will bring it out of the error – 1 zombie state. If I continue trying to connect I get a connection failed status 133 and won’t be able to attempt a connection again until I force close the app.

  • #18588 Reply

    Sam

    Same problem here, using Pixel XL. Can’t get it to connect most of the time, have tried switching BT on and off, restarting the phone, all that. Very irritating.

  • #18617 Reply

    Richard

    If you want to dig in deeper, here are instructions how to build and get debug output of the app:
    https://github.com/mooshim/Mooshimeter-AndroidApp/issues/64#issuecomment-323034715
    (But please open a new bug report then).

  • #18655 Reply

    Guillaume.C

    Hello,

    I join up the people here, I bought a mooshimeter 2 weeks ago, I used it for about a dozen of time. The praticality of the device falls appart if you have to restart and reload the firmware to make it work again…

      I’m currently on a samsung galaxy A3 and the only ways to manage to pull it out of failure like “error -1” or “status 133” is to reload the firmware.

    If the devs are unable to provide any stable firmware/apps whatever reason there is.
    I would be nice to know the procedure and which version of apps and firmware that are considered as really stable.

    Thanks you

  • #18675 Reply

    René Arts

    Since I was still experiencing issues, last week I re-flashed the firmware on my mooshimeter (just normal OTA via the app). Had to use the slow/old method BTW to let it succeed. Though the version is still the same (there was no update, just reflashed out of curiosity), I have not yet to encountered a failedstatus -1; the meter seems to be working fine and reliable again. Problem is a few days after the firmware flash I also received an OTA Android (security patch) update, so I’m not sure whether reflashing is a reliable method. Maybe one of you guys can test it as well?!

  • #18676 Reply

    Harry
    Participant

    I just had the same Issue (but “Initialization failed: status -1” exactly).

    I mainly use my S7 Edge on Android 7.0 with Mooshimeter App v1.0.34 (2115), firmware 1477971088, and had logging running over night. It’s the first time I had this problem and firstly I thought It was maybe because I changed the Log interval from 1s to 10s after ~3h off logging (-> first time this error, first time switched this value while logging).

    I tried ~10 times to connect, meanwhile closed the app, no success. Then I switched to my second device (Note 4 on Android 6.0.1 – same App version) and there, I firstly had the same Issue but I think on the second attempt the app initialized correctly. After that (closed the app) I could connect with my S7 Edge without error…

    So maybe this Issue is related with Android 7? Just wanted to write this quickly down here, maybe it helps others. I’ll keep watching this. :)

  • #18704 Reply

    René Arts

    I’m running Android 7.0 btw, with security patch level of 01-07-2017, still running fine after the firmware flash.

  • #18973 Reply

    Harry
    Participant

    Had a log running the last hours. Connected, stopped logging, clicked “load available logs” … no logs in list but message “Waiting for log data” for minutes and mooshimeter status led was disconnected with SD present. (like I described yesterday here https://moosh.im/f/topic/cant-download-log-from-sd-through-app-disconnects-and-sets-itself-values/ ).

    Then trying to connected/closing the app/reconnect/closing app/disable-enable Bluetooth/…. every time “Initialization Failed. Status: -1” and sometimes there was written something like “no device detected”, although the mooshimeter was shown on top with ~ -60 dBm signal strength.

    Then after like 10 or 15 times a new message appeared “I don’t recognize this device… aborting“. After that I could connect to the meter. Like yesterday, the app itself set values sampling to 32smpl and log time to 10s by itself (was 265smpl and 0s before).

    So connected and next try reach my log, load available logs -> no message, no logs, meter disconnected (with SD present) -> “Initialization Failed. Status: -1” …

    This is now starting to really annoy me! :(

  • #19017 Reply

    Henry

    I tried to use my meter today and had the same symptoms as Harry. This is most inconvenient.
    I’m running Android 7.1.1 on a Moto Z Play

  • #19018 Reply

    Harry
    Participant

    Yesterday I had the same issue again, this time tried to document nearly every step via screenshot, since there seems no error log available (this may be a good idea, wouldn’t ;) ). Minor or less the “procedure” was the same as written above.

    You can look at them here (20 screens, look @ date/time):
    Samsung Galaxy S7 Edge, running Android 7.0 (security 08/17)
    https://drive.google.com/open?id=0BxEZsMPKTcshbGFTLUNrakpsa00

    Hopefully this helps. I know James is very busy and alone with this project atm, but this had to be fixed asap! Or is my device (and therefore Henrys too) maybe defective?

    Best
    Harry

    PS: One day later, everything worked as normal and I could receive the logs via app… but that’s not a acceptable status!

    I’ll try the next times with Android 6 device…

    • This reply was modified 2 days, 15 hours ago by  Harry.
    • This reply was modified 2 days, 15 hours ago by  Harry. Reason: Robinson Route
  • #19021 Reply

    Henry

    I should reiterate my problem, I haven’t been able to connect at all. It worked until recently, but now all I get is the “Initialization Failed. Status: -1” message. I have no other phone to test this with.
    I’ve been really impressed by this little device since I got it last winter, but in my mind it’s been downgraded from “useful tool” to “broken toy”. A great idea, but the software needs to be as robust as the hardware.

Reply To: Initialization failed:status 1
Your information: