Just right click on the free space of the menu bar (right of the "Flash" menu).

Hi Vogtinator,

First of all, it is great to finally have an nspire emulator for Android.
I installed it on an S4 mini and it works :-)
It looks nice and, once started up, is quite usable.
Cannot say yet about stability, but looks promising.

I have anyway some comments that I consider quite important to make the app usable:

- The main annoyance (common to all nspire emulators I have tried) is that there is no way to save the state.
  If I exit the emulator and restart (even if I switch to another app and I come back after a bit of time), everything is lost.
  There must be a way to implement saving the current state so that I can "switch off" the emulator and come back
  to the same point when I "switch it on" again.

- This might help as well with the second big issue: startup time.
  Whenever I start the app:
  - I have to press the "bomb" several times until it starts booting (I do not really see the point: it should
    just start when when I open the app).
  - Then it takes more than 2 minutes before boot is completed and I can type my expressions
  This makes the emulator unusable as a day-to-day calculator.

I am asking myself if there people really USING these emulators or if there only around perosns developing them.
That is for sure a lot of fun, but without true usability, you cannot really get a wide and happy user base.
For this reason I am still using very good and usable TI-48 emulators on my PC and Android phone/tablet.

I think that if you concentrate on developing the Android (and IOS) variant (this is what puts you apart from the other branches of the main emulator) you can have a good success among the many kids that use the nspire at school.
I would be for sure available to pay some euros on Google Play for a good emulator.

It might be I am completely wrong and I did not understand the "right way" of using the emulator.

I would be gratefull if anybody would comment and tell me how people is using it efficiently.

Yes, what I ment was "suspend and resume".

Having first to save the scratchpad in a document and then save the flash, coupled with the boot time of the emulator makes it really unconvenient.

I understand the issues with the RAM dump. I would guess that most of the users of the meulator would be like me and not use it for heavy work (in that case the HW would be much faster). I that case the RAM should be mostly empty a compression should be very effective.

I know you do it for fun, but this would be a recognition for your work and would make people think that there is quite some work behind this software.

While trying to reposition some of the floating docks, I clicked by mistake on the Close icon ( right beside the Redimension icon ).

Meanwhile before implementing such feature, a paliative would be to start Firebird Interface on Tabs mode, or at least indicate the existence of that option for the naive users on a README file.

The Flash Menu could be improved if it include the option of not only Saving a Flash Image, but also of Loading another previously saved ( or already available one ), without the need of opening the Settings / Nspire tabs and selecting a Flash Image and Boot1 file ( from that tab options ).

Also at the Create Flash Image menu, Boot1 is indicated by a Manuf tag and placed below Boot2 which shows up a bit confusing for the naive user to fully understand that a Boot1 file is required at that point.

A bit more explanations on a README file would let the users know exactly what to provide on each field, with instruction for them how to obtain Boot1 and Boot2 image files from their own physical calculators, by meens of ndless and polydumper.

While trying to Generate a New image file from the Create Flash Image menu, ( with all the required files provided and correctly identified after each selection, except for the provision of Diags which I left None and selected to Boot from Boot2 and Not Diags ), I ended up with an Application Crash on Windows 7 32bits.
 
   The Boot and OS files I provided were the Same ones I succesfully used on Nspiroid [ https://www.omnimaga.org/ti-nspire-projects/nspiroid-ti-nspire-emulator-on-android-(zenfone-5)/30/ ] and kARM-TI [ https://www.omnimaga.org/ti-nspire-projects/karmti-ti-nspire-emulator-with-skin-16585/420/ ] were I succesfully generated the Flash Image files which I Ported to Firebird ( after Not being able to generate a New Flash Image directly from Firebird, due to the reported Windows application Crash ).

Overall my very First impressions on Firebird were very good ones, showing up as a Very Promising Project due mainly to its broad range of covered platforms, with a vast array of implementations, based on a Same common ground, leading its final users to an easier adaption from one platform to another.
 
  The only missing points which deserve a bit more attention by now are an Improved Documentation, by the inclusion of a README file describing in more detail the Boot and Flash Image file creation ( or import ) process,

and the "definitive" closure state of floating Docks described on the Windows port, and which I dont know if similar behavior could happen on other platforms like Android ( and where I simply do no know how to Restore the equivalent of a Registry entry on a Android ARM Tablet without root access ).

Thanks very much for All the attention, hoping to have provided Valuable points requiring some attention on future releases of Firebird,

PS: A missing option for the Non developer users would be to allow not only for Firebird to Start Emulation Automatically, but Also allowing the choice of starting with focus on the Keypad window open ( in place of the Serial Monitor actually selected and opened by default ). The inclusion of a simple ( exclusive ) Selection option ( by means of Radio Buttons ) between Keypad and Serial Monitor, would allow for such configuration, leaving both developers and common users the ability to opt for their preferred choice of initialization.