Hi
Please change vertical offset key sensor, it very low on my galaxy note 3. Thank you!

Hi diebold, welcome to omnimaga and thanks for the feedback.
ATM, the only chance i have to test that high resolution (1920x1080) and pixel density ( >480ppi, xxhdpi, i assume ) is by using the terribly slow windows arm-emulator.
Could you please explain what do you mean by 'key sensor' or even better post a picture(s) (portrait and landscape). I could then try to find a fix for it.

I click "K" but clicked "R"

Well, that looks pretty awful! thanks for that.

Based on the windows arm-emulator (yeah, the sluggish one) here is (or rather, below is) how it should look on a xxhdpi device (1920x1080, ppi>400). The pictures are'nt yet in a final stage, i still need to properly scale the graphics, but that takes time.
BTW, this time i'm releasing a fat-binary .apk (winrar'ed due to omnimaga 1024kB file size restriction!), meaning, it should work on both x86 and arm cpu's..
Despite its version nbr being v1.01 is still in a beta stage. Essentially, i still need to fix the graphics.  Please let me know if that works for you.

key offset is still work

That looks way better. At least now you should be able to test all the available functionality.

The problem with the windows arm-emulator is that we need to hide the 'navigation bar'. I guess, i just found out how to do it. Is always better to have a real device to test. Oh well, we can't have everything, never.

I'm posting a quick-fix to the layout problems you're having and a little better graphics. See if that suits you, for the time being.  Good graphics require more time but are't that important...

Thank you very much for work. Graphics on 1.02 version very well and all functionality working but displacement response of buttons hampers to work normally

Okay, i suspect we might have a problem (i'll explain later) with fast cpu's. What's yours? Quad-core 1.9 GHz Cortex-A15?
Anyway, please try 'Nspiroid_fat_v102N.apk' which is slightly slower and tell me how it goes in your system. We are almost there .

it working similar previous version, my cpu is Qualcomm Snapdragon 800 Quad-Core CPU 2.3GHz

That's important info, thanks. But i still need the exact OS version on your phone.  Android has some version specific bugs, for which i've introduced some work-arounds which probably i'll need to remove.

*Edit*: What do you mean exactly by "... displacement response of buttons hampers to work normally"?. Do you mean that you press 'k' and you get 'd'. Can you please try to explain it a bit further?  I've never had/seen anything similar to that!

version 4.4.2
Yes I meant when you press on the top of the key "k" pressed "d" as if the calibration is shifted down all buttons have the offset response down to about 4mm, I think this is not a bug of the OS in other programs there is no such thing

Thanks, again. Unfortunately, i'm now pretty convinced this is yet another Android bug.  I just did a bit of 'googling' and found something with similar symptoms.
http://stackoverflow.com/questions/27258381/applying-keyboardview-in-android:
"On android 4.4 ; specifically Samsung Galaxy s4 and s5 , the custom keypad appears nicely. On Samsung galaxy s3 and the rest of devices with screen size less than 5inches, the keypad is distorted and looks like : ..."

Yes, Nspiroid uses KeyboardView. I'll see if i can apply some sort of workaround.

*Edit1*: I think i found a solution for the problem. Please give me some more time and stay tuned.
*Edit2*: Here goes v103.apk. I hope the keyboardview vertical offset bug is fixed in xxhdpi devices.

Yes, vertical bug is fixed. Great thank you! Good work!

Good! Thank you too for the precious feedback.

That's a silly little typo bug, that i've already fixed. Next release will be ok, thanks.

BTW, do have any possibility of testing Nspiroid on a Samsung S6 (1440x2560 px, ~577 ppi)? ATM, I'm working on the layouts to also support this rich guy's phone .

*Edit*: Here is Nspiroid_fat_v105.apk. It includes beta support for more expensive devices, e.g. Samsung Galaxy S6.
There are still some minor graphic glitches that i will fix later. ATM, all i want is to ensure the calculator functionality can be used near its full potential.