I finally tested it with my WS1088.
I got it working but:
1) I'm a bit confused at the Android end by Home and Away and "Are you at Home?". It actually seems to mean is the "server" at Home. Or is this supposed to be to choose between your local IP and public IP?
2) The Android app seems to want to turn on it's side. It keeps deciding I'm holding my phone in landscape orientation even when I'm not.
3) Once I've pressed Fn the Android app shows the Fn icon forever even if I cancel by pressing Fn again.
4) The server sometimes uses 100% CPU on one thread. I haven't figured out what triggers it yet though.
5) The Android Back key will not get me out of the app. It behaves like a iPhone app and the only way out is the home key. Maybe I'm weird but this irritates me.
Much of the design and features came from the old Win500 and all the comments that were given for that app.
1) The home and the away give you 2 ip addresses/addresses to access your scanner. Many routers do not do loopback. So if you have your public ip, you might not be able to access it from inside your network. This option of home/away settings gives the option of an address to connect to from within your network and another from outside (and the matching ports). Eventually I might change this to a list, so you can connect to other scanners as well, but for now, this is enough.
2) Check your display settings in the app. It should default to using the sensor, but you can also lock it in landscape mode or lock in portrait. Perhaps that was checked at some point during your testing.
3) Odd. It has not done that in my testing or the testing done by the others. I am sure it happened to you, no doubt. Do you at least hear a beep from the scanner when you press the fn key again? Does the scanner itself still have the fn showing, or just the app? This should not happen.
4) Not sure on why this. I know I have some issues with the driver here, but those can be reproduced using the official demo app and not my software. I have not noticed those issues spiking my cpu either. I specifically watched on my machine during development and saw it stayed around 13%. I did have one thing during development that I changed because it was going to 26%. What does the official app do? Can you identify when the app hits 100%? Maybe there is something and I can fix it. First thought would be virus protection, but then the virus protection process would be using the cpu, not my app. I assumed you knew it was my app from task manager. If not, load task manager when you see the cpu spike to see what process is spiking. If you can recreate this, maybe there is a fix, or at least an explanation.
5) This is totally from Win500a. I remember this was asked for from a few people. Same with the exit in the menu, option to hide the stop button, keep screen awake, large LCD. A lot of the options were originally suggestions. I sometimes hit back and remember it does not go back. Maybe I can add that as an option. I can look into that.
I hope these answered your questions. Feel free to contact me directly if you'd prefer or here for more info. I should have mentioned stuff about the original Win500 app. I wrote that app years ago originally just for me to use, then decided to share it. I actually do use this stuff too, so I want it perfect for me as well as you. I've already had a few people tell me about things not working, or ideas, such as the conventional logging not working, or screen size memory. I'm open for suggestions. If I can do it, I probably will if not too over the top. Here's a link to the very
original Win500 Thread if anyone is interested, it is sorta neat how far the app has come. Those first screenshots are funny.
