firebird
firebird copied to clipboard
nspire-emus
Firebird not working on Galaxy Note4 w/ Marshmallow 6.1
Hello,
is there a chance for a working Android-version in the near future? It has been quite cumbersome already to get the thing going even low-level at all. I had the boot1-,flash- & snapshot-files positioned in the \data\data...etc folder initially to have them directly available without navigation from the initial config-window and after failure to even load then also tried the source-directory on the external SD-card. In vain. In both cases the emulator obstinately refused to load at all.
Later, on loading from the documents-folder, the request to press "I" for loading failed again b/c the software-key "I" did not respond to key-press (no change to inverted "key_pressed-image" in the display) - and the whole thing seemed to hang indefinitely.
At some point (only heaven might know why) the system finally responded and the loading-process went on to continue but still took like FOREVER to finally load the emulator.
Most unfortunately, that is, only to leave me with a partially garbled interface. The "center keys-block" (around the joystick/touch-area) seemed to overlap with the main input-keys-area, leaving its essential upper-most row of keys like "ctrl","sto>" & "clear" unaccessible. This still is the current status.
With this functional torso I had actually hoped for a new version in the foreseeable future.
Hardware: Samsung Galaxy Note4 (btw, S-Pen stylus doesn't react either, only finger-fumbling will, which the S-pen stylus seeks to avoid in the 1st place), on Andriod Marshmallow_6.1 w/ 1440x2560 Display
nspire: CX CAS 4.5
greetings TomTom
Apparently Qt 5.11.1 has a bug which breaks building with the android NDK, so this test build probably won't fix the keys issue.
(btw, S-Pen stylus doesn't react either, only finger-fumbling will, which the S-pen stylus seeks to avoid in the 1st place)
Unfortunately not implemented in Qt yet: https://bugreports.qt.io/browse/QTBUG-43237
so this test build probably won't fix the keys issue.
Ahm, "test build"? I might try if only I knew where to download. Wherever I look the latest Android-apk seems to be the 1.4-build with all the above mentioned problems.
Ahm, "test build"? I might try if only I knew where to download.
I thought I linked it - maybe GitHub swallowed the file. Next try:
This time it worked, I had a chance to download & try. Unfortunately - but not unexpected the garbled input-key-field is still the same, so, still unusable for me. However the loading process seemed to be quicker and after the update I didn't have to press "I" again (maybe the ROM was still in memory??).
Emulation on a very basic level also seemed to work but without a "clear"-key etc. the fun comes to an end relatively quickly. Conclusion: hoping for the next release (although without you having access to a comparable Samsung/Marshmallow>Oreo-device I perhaps shouldn't hold my breath ;-)).