Glad to see you on the forum Stephan.
@nidza07: I think I remember hearing a thing or two about this being on the wire. Of course, talkback would throw a major wrench into everything since every planned swipe would have to be a two-finger gesture for the sake of passthrough, so that limits how many gestures you could otherwise have. I remember there being a hackers keyboard that had ctrl, windows and alt keys. I'm not sure if those can be passed through directly, whether stickykeys is on or off on the windows side. To that end, if it works, all one would have to do is install the hackers keyboard and they would have a fully working onscreen keyboard for the nvda remote.
As for the whole in-app purchase fiasco, that actually is not a problem with the app at all, but rather with the way Google Play policies work; the in-app purchase flag has to be applied before any in-app purchases can actually be implemented. The general paranoia surrounding in-app purchases is no isolated incident, dating back to when webviews would get hijacked with fake phishing popups, or the touch sensor being taken advantage of. I figured the developer was only looking for donation capability but would rather have it built in natively than having a paypal button, should users want to donate directly from their phone.

This is really cool! Does this work with other servers besides nvdaremote.com? Do you have plans to port this to iOS or do Apple's restrictions prevent this? I'd also love to have touch screen gestures as some point.

Unfortunately keyboards with emulated keys wont work, at least blind accessibility keyboard didn't. If you press something like tab it moves the actual Android focus instead of passing the key through to the application. Quite unfortunate as I was hoping this would at least be an alternative.

How can I enable the edit  field to control the PC using blind accessibility keyboard?

i think you nead a ficical keyboard to control your computer using this app. because, i tried menny keyboard apps. nothing works. sorry for my english.

What I use is actually a foldable bluetooth keyboard, which when folded is smaller than my hone. Thicker, but in hight and width smaller.

It's not a major deal. I can always get a USB OTG cable and connect a USB keyboard. This is really cool. I thought my GPD Win was cool, but this takes things to the next level. I assume this works over LTE?

The GPD Win is cool and of course NVDA Remote works on it. Then again, what's the point of controlling a super portable mini laptop from a cell phone? I suppose you can say because you can.

Speaking of the Compute Stick, is it possible to connect it to an HDMI audio extractor and use NVDA? That might make a nice low powered desktop PC that could of course be used with NVDA Remote and this app.

I still can't get over how awesome this is. If my compute stick idea works, I could take an Android phone and a keyboard everywhere I go and have access to Windows applications and features if I needed them. I essentially get my true dream of a pocket PC with LTE connectivity. The GPD Win comes really close, but it lacks LTE.

By the way, very nice update, seems like all the bugs from before are corrected. Connections are incredibly stable now.

Chris, I meant using a GPT Win, or a compute stick with a keyboard, to control a powerful windows pc, offering very portable high performance computing and removing the need for a laptop. Since we're blind, why take a big screen with us? All we need is sound and a keyboard. Android latency is the only left thing bothering me, guess I need a pixel.
Thanks for your appreciation. That's exactly what I thought when deciding to develop the app.

Actually, Jack, posting Narwhal to play store is one of my ways of promoting Android. People always ask me why I don't use ios. Now, my app is the third argument, after the price and eloquence.
I'm happy it now works for you. Indeed, I haven't noticed any crashes in the last days. This means either that no one uses the app, or that it doesn't crash.
I learnt a lot from this experience, mainly that android phones are very different, and that testing should be done by users, not the developers of the app. I knew the last   one, but sadly ignored it.

good idea. let me know if the accessibility service doesn't work, I can enable the old, less efficient key interceptor for chrome os. Guess i'ts better than nothing.