A3 remote issues on U22

Ferrocene

Member
Hi John,

thanks for 003A FW, and for fixing the Neo A3 air mouse return key.

With 003A FW, the following Neo A3 air mouse keys give incorrect symbols as follows,

@ = "

" = @

# = £

~ = ¬

\ = #

| = ~

and { } | only appear after Fn + Shift are both pressed together twice.

While on the subject of the Neo A3 keyboard, with the introduction of the new 0, 90, 180, 270 screen rotation, is there any intention to enable what looks like a Fn + 180 degree screen rotation symbol on the keyboard?

As I mentioned previously, there are occasions especially when trying to change settings, when I have to press far harder on my Neo A3 keyboard than I feel I should have to, and sometimes have to give up and resort to pressing the up, down and enter keys to change a setting, it's as if there is something wrong with the key press sensitivity.
 
Last edited:
Make sure you have English US for physical keyboard:
Settings/More Settings/System/Languages & input/Physical keyboard/SAGE SAGE AirMouse
Thanks Marty, I changed the physical keyboard from English UK to English US and that has sorted my @ " ~ # \ | key issues, very grateful to you cheers.
 
Hi guys. I have a problem myself with the A3 remote when using the virtual keyboard. I can move around the letters OK, but when I try to press on a letter it doesn't type it?
 
Hi guys. I have a problem myself with the A3 remote when using the virtual keyboard. I can move around the letters OK, but when I try to press on a letter it doesn't type it?
Same is happening for me on the A2 Lite, I will put it on the bug tracker (y)
 
Same is happening for me on the A2 Lite, I will put it on the bug tracker (y)

Thank you. More irritating than being a problem..just glad my u22 updated from 002 to the new 003A firmware ota after doing a factory reset(y)
 
Hi guys. I have a problem myself with the A3 remote when using the virtual keyboard. I can move around the letters OK, but when I try to press on a letter it doesn't type it?
We're aware of this problem and intend to include a fix in future OTA update.
 
Back
Top