Interestingly, an art::interpreter::UnexpectedOpcode exception shows zero Google results, and the rest of the stack trace doesn't really show much Mycelium logic involved at all. Note that stack frame 6 looks incorrectly symbolized suggesting we might perhaps be trying to execute data-as-code or something else malicious is going on.
Summary: Something that looks like it might be some exploit is running on my phone. Documenting it here incase it turns out to be some advanced attack being tested out on me. If it's a regular bug, it's probably one in the android art compiler rather than mycelium itself. No coins stolen - I guess the exploit failed to run properly!
Mycelium worked fine on this device for a while. Now crashes on startup. Not sure what changed, but here is the crashlog.
myceleumlog.txt
Interestingly, an
art::interpreter::UnexpectedOpcodeexception shows zero Google results, and the rest of the stack trace doesn't really show much Mycelium logic involved at all. Note that stack frame 6 looks incorrectly symbolized suggesting we might perhaps be trying to execute data-as-code or something else malicious is going on.Summary: Something that looks like it might be some exploit is running on my phone. Documenting it here incase it turns out to be some advanced attack being tested out on me. If it's a regular bug, it's probably one in the android art compiler rather than mycelium itself. No coins stolen - I guess the exploit failed to run properly!