Simulator Bugs

I'm attempting to collect as many of the simulator bugs as I can right now. We're aware of several issues (intercepting the light button when it shouldn't, font inconsistencies, etc.), but if there are any others you have not already seen reported or discussed here in the forums, please let me know.

Keep in mind that this is a simulator and not an emulator so it's unlikely that we will do much in the short term to address things like simulator speed/performance vs. device hardware.

jim_m_58 over 10 years ago

This one has been reported (a few months back), but want to make sure it's not forgotten!

If you are doing makeJsonRequest(), after that's called 10 times, the simulator crashes. It doesn't need to be during the same "run" of a .prg

jim_m_58 over 10 years ago

Not a bug, but a suggestion. When running "Simulate>Fit Data>Playback File", any chance it could remember the last directory used, so you don't have to navigate back all the time?

Former Member over 10 years ago

The simulator does not show the mark lap screen when auto-lap is invoked or a lap is set by the source code. The F3 does, though.

Here I consider it an F3 bug, not a simulator bug, but it is an inconsistency that leads to unexpected bad surprised on the device.

Furthermore, a "press" on the ESC button does not terminate the simulator, even if the event is not intercepted and masked. This means that the correct behaviour of the ESC button cannot be tested on the simulator, in particular for cases where the ESC event is (sometimes) not passed to the default handler.

jim_m_58 over 10 years ago

Again, this may be on the list already, but just to make sure. Things that aren't available on the real device and probably will never be, such as "TextPicker" on the va, probably should be caught in the simulator when simulating a va.

Another example us using "tones" in a va simulation.

It would also be nice to be able to toggle things like "phoneConnect" in the simulator (right now I have to set a boolean in my code if I'm running in the simulator to bypass the check), and also provide a way to generate ActivityMonitor History. Today, the only way to test anything that uses history is on the real device.

Former Member over 10 years ago

Using tones is allowed, on the vivo, in the simulator.

jim_m_58 over 10 years ago

Using tones is allowed, on the vivo, in the simulator.

The va doesn't support tones. no "tone maker" HW! Also, i seem to recall in at least one version of the FW, if you tried to play a tone on the va, it would crash. (no FW for it since there isn't the HW..)

travis.vitek over 10 years ago

He knows that. He wants the simulator to return false for Toybox.Attention has playTone for devices that don't support it.

jim_m_58 over 10 years ago

He knows that. He wants the simulator to return false for Toybox.Attention has playTone for devices that don't support it.

Now I understand. I'd posted about tones earlier and thought it was a response to my post. ("on the vivo, in the simulator" - thought he was saying both on the vivo AND in the simulator!)

travis.vitek over 10 years ago

This is a minor complaint, but the Low Power Mode menu is wonky. I reported this previously here.

rconradharris over 10 years ago

I'm seeing a bug where the Back button on the simulated Vivoactive is being treated like a PreviousPage, not Back.

On the actual Vivoactive itself, everything is A-OK.