Fabian Vogt

> Great stuff - and works out of the box with my android and windows. > > As i want to use the windows version with my colleagues in a...

> > However, on the first start it creates a kit with the values from the `boot1` and `flash` keys in the settings. You might be able to utilize that...

Not limiting speed was meant for accelerating boot times and file transfer, what's your usecase? 100% should be fast enough for general use, as that's what it's meant for.

200% would still make everything twice as fast, including input repetition and idle timeouts. Not sure how to offer that option in a user friendly way, because the option itself...

The emulation speed is used for timers, so a 1s tick will be 0.5s instead when running at 200% speed. The current design does (intentionally) not allow to separate CPU...

We can only map to physical buttons on the nspire keypad, @ is only reachable using one of the OS menus.

Definitely not! Except for the two misbehaving columns the layout looks fine though, so I don't know what went wrong here. The keypad layout was changed now to include key...

Sorry, I haven't got around to upload the .apk yet, I'll do it today.

Try this: It contains an unfinished button label rework, so some keys look odd. [QtApp-debug.apk.zip](https://github.com/nspire-emus/firebird/files/224214/QtApp-debug.apk.zip)

Hi, here's a (completely untested) build with the latest Qt 5.7.0. Maybe it solves some of your issues: [QtApp-debug.apk.zip](https://github.com/nspire-emus/firebird/files/368087/QtApp-debug.apk.zip) > Tried the test.apk posted in this thread, and whilst better...