minible
minible copied to clipboard
mooltipass
#002 Contact Support, fixed by Device Settings, Battery Problem?
Expected behavior
Works as usual
Actual behavior
Best case, can unlock card, then freeze immediately. Other behaviour:
- black screen on disconnect
- previous frozen screen on reconnect
-
#002 Contact Support - battery status in moolticute: 0%
Tried letting it charge for about 30 minutes. Same symptoms.
Step by step guide to reproduce the problem
N/A Maybe letting the battery run out with BLE enabled.
Firmware Version
AUX MCU version: 0.70 Main MCU version: 0.80 Bundle version: 8
Moolticute Version - If Involved
v0.53.7
Operating System
Mention if you are using either:
- Windows 7
- (Fedora 35)
Fix:
I enabled the following device settings:
- Switch Off Device after USB Disconnection
- Disable BLE on Card Removed
- Disable BLE on Device Lock
After reconnecting/reboot everything seems to work. Battery seems to charge.
I'll leave BLE off for now just to be safe.
PS: A backup mooltipass with up-to-date database files is a really really good idea :D
hmmmm.... I'm wondering if that's not a device-related issue. can you get in touch with us at support(at)themooltipass(dot)com so we can send you a replacement device to check? :)
Just received a Mooltipass BLE Mini today and out of the box it wan't charging even after sitting on a 2.5A 5V capable charger and a 5A charger.
Now having the same issue with a ! #002 Contact Support message and the device acting strange trying to recharge. Have sent messages through the Mooltipass.com Contact Us interface. Wondering if I too might have a bad device. Tried battery reconditioning and now the device won't charge past 80%. Since it's not fully charged I cannot update the bundle.
hello @billgertz could you update your unit to bundle v8 using www.themooltipass.com/updates ? Bundle v8 does fix 002 & battery issues :)
@limpkin Responded at support as well. Pressing shift and select bundle file button at same time changes nothing. Still cannot upgrade the firmware. Um, now what?
@limpkin
Thanks for getting back so quick - but still having problems. To answer your question: yes I followed the directions to initialise for update and then tried to update as outlined:
Update Step 1: Enable Update Mode on your Mini BLE Connect your Mooltipass Mini BLE to your computer through USB and make sure your device is fully charged:
Insert a card the wrong way around (chip facing up) to get to this screen:
Update Step 2: Enable Moolticute’s Developer Tab, Upload your File In Moolticute, press CTRL-SHIFT-F3 (Shift+F3 on Mac) in such a way that all keys are pressed at the end of the shortcut. The BLE Dev tab will appear in the top part of the application.
Pressing Shift and Select Bundle File makes no difference. Is there a method via the command line? This cannot be so hard.
damn, it seems you may have found a bug on the bypass mechanism @deXol do you know what key should be used for MacOS?
@billgertz in the meantime would you have access to a non macos computer? AFAIK there's not a way to do this through command line
@deXol @limpkin
I've tried the following key combos already, or at least I think I have ;-/:
- Option
- Command
- Control
- Control+Command
- Control+Option
- Command+Option
- Shift+Option
- Shift+Command
- Shift+Control
- Shift+Control+Command
- Shift+Control+Option
- Shift+Command+Option
@delXol @limpkin Parallels Windows 10 VM doesn't seem to passthrough whatever USB device. Can you clarify which devices(s)? need to be passed through? Windows 10 system I cannot change tabs, although all other software on the system works without issues. Pressing on with the native Win10 system to see if I can muddle through.
@delXol @limpkin Although I could not change tabs Control+Shift+F3 did bring up the BLE Dev tab. I prepped the device for firmware upload, pressed Shift+Upload Bundle File. And of course it errors with a message:
Error: Upload bundle finished with error
Yes I rebooted the Windows system. Now what?
MacOS should still be shift (https://github.com/mooltipass/moolticute/blob/master/src/BleDev.cpp#L174), but our developer let us know in some cases MacOS may remap it to CMD+SHIFT. @billgertz can you confirm the keys are pressed while you click on the upload button?
@limpkin @delXol
We finally got there! Yeah team!
Tried Command+Shift and it worked! One step closer. Even after prepping the device as outlined in the instructions I was getting the same error as I did on the Native Win10 system:
Error: Upload bundle finished with error
I had removed the card... The instructions didn't say to remove the card. The device said to remove the card and I dumbly did so.
We're making progress! I'll update the manual to reflect that potential issue. Can you confirm the device is showing the "Please remove card" animation?
Yes it had and that's why had removed it. BTW - I edited the parent post so you might need to refresh your browser to see that we got the firmware to update.
Looks like device charge is still suck at 90%. Do I need to do yet another Battery Recondition?
Awesome! Glad you managed to update :). I indeed recommend on doing a final battery reconditioning... I apologize for all these adventures?
Do you need a MacOS QA? Would be happy to help, so no one else goes through this. Reconditioning, hopefully for the last time.
We do welcome any advanced testing that can be done on MacOS, as it has historically been quite capricious with our software :)
Okay - BTW are you using any CI tooling for testing (travis with Linux UI test tooling xvfb, or MacOS UI test tooling atomacosetc)? Probably need to move this conversation to Discord or like service.
Still having a wee hiccup - the device didn't charge past 90% add still doesn't. It's still throwing #002 Contact Support message. Rebooting clears the error but when connecting to USB it comes back after a while. Do I do another battery recondition, or is there something up with the device?
I'm starting to think this device might have issues... would you be able to update to the latest beta at beta-updates.themooltipass.com ? let me know if you can't fetch the update as I haven't updated this page for a little while
I was able to download it when I left the registered email address blank - so the same issue as the production firmware download page. You corrected the production page so that [email protected] was registered against my serial number. Firmware loaded and upgraded. Moolticute About page reports bundle 11.
The battery still reads 90%. Is the meter sensitivity to the closest 10s of a percent? It should just jump from 90 to 100% when completely charged, right?
Okay, it's been an hour, and still not charging past 90%. So do I try another battery recondition?
Hello Bill,
90% max charge can be expected (see user manual). Out of curiosity, what "time spent" did the battery reconditioning procedure give you?
Mathieu
On Thu, Oct 27, 2022 at 1:26 PM Bill Gertz @.***> wrote:
Okay, it's been an hour, and still not charging past 90%. So do I try another battery recondition?
— Reply to this email directly, view it on GitHub https://github.com/mooltipass/minible/issues/340#issuecomment-1293383887, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPCNMYYNPNYLEUC4IN6LOTWFJRFFANCNFSM5VO7DKJQ . You are receiving this because you were mentioned.Message ID: @.***>
Well over five hours, but it died with that Contact Support !#002 - let me look at the logs. The last recondition was done before the upgrade to bundle 11.
can you try disabling it and see if this improves your 002 issues? :)
On Thu, Oct 27, 2022 at 2:23 PM Bill Gertz @.***> wrote:
Yes
— Reply to this email directly, view it on GitHub https://github.com/mooltipass/minible/issues/340#issuecomment-1293446978, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPCNM7K3Z3DI75R6CFYCR3WFJX5FANCNFSM5VO7DKJQ . You are receiving this because you were mentioned.Message ID: @.***>