I have multiple Minix remotes. A couple of the small simple remotes that come with the Minix boxes and 2 A2 Lite plus an A3 remote. It happens with ALL of them. Well, maybe not the small simple remotes, as I have never used them, but definitely with all the A2/A3 remotes. I cannot imagine all of them being faulty, unless they came that way from the factory.
And it happens all the time. Very very annoying.
I have experienced this with all my Minix remotes and assumed it was normal. It is random, can go for days without hiccup and then it appears, sometimes a one off, other times every click until reboot. It does become annoying because we tend to use our remotes under motor reflex so the double click from a single click on the remote can come at exactly the wrong time, it is happening right now as I type this message on the A2 Lite.
OK, a slight adjustment to my previous comment in this thread, but be warned, this is going to do your proverbial boxes in lol
.......
As explained above I had an A3 that
chronically exhibited similar behaviour in the past but a replacement immediately solved it.
Then, I began using CoreELEC again a couple of weeks ago but prior to that I'd never had this problem crop up again once in several years. (Out of
roughly 8 x A3's or 4 x A2 Lites that I use or have access to, & all used with a whole list of MINIX Android based devices.
They're not all 100% trouble free either though I might add. Sometimes the fly mode/gyro positioning can get very screwy on a backlit A3 & the fly mode can sometimes be hit & miss with a couple of the standard variants too.)....
...
However, I've since been experiencing similar issues again very recently specifically with a backlit A2 Lite with CoreELEC & a U22. (Many inputs would frequently just not register at all from the remote especially with the D-pad, sometimes a single press would completely randomly input as multiple inputs, & somehow it's even been magically interpreting a specific key/button press as something else altogether. (As I previously experienced it, not only is it pretty damn annoying & frustrating, but under the wrong circumstances potentially dangerous as it's actually caused file deletion too before I put in or re-enabled the respective manual safeguards to stop it!!))
Even more oddly, I noticed these problems becoming far worse depending on the relative positioning of the remote to the dongle. (Why is this anything to do with it at all lol
? Apparently line of sight to the dongle, (which obviously
shouldn't make any difference
at all as it's not IR & direct line of sight shouldn't be required period. Nevertheless, it's still happening & I can consistently confirm, & recreate it, but
only with this one backlit A2 Lite). I'm also only roughly 5 M from these devices which is well within the 10 M maximum range.)
(I have some 3 inch USB A male to female extension cables so I connected one of those to allow the actual dongle to hang down in front of the device to ensure direct line of sight.
Voila, all noted problems instantly solved . (It's not a particularly pretty solution but it has at least confirmed what was causing it for me & I can't recreate the problem at all with the dongle connected via an extension (USB) cable/guaranteed line of sight.)
Despite a lot of effort trying, I just cannot get this issue to recreate with this one backlit A2 Lite with Android on the exact same U22, or with a U9-H. I also can't get it to recreate with CoreELEC or Android with a T5 either. (It's just happening with this one remote & a U22 with CoreELEC which is seriously bloody weird!!! Why can't it be recreated with a different OS on the same device, or on a different device with the same OS? Or, why can't I recreate it using a different A3/A2 Lite under the same conditions as above? It's completely baking my noodle lol!! I've also started over with a completely fresh CoreELEC three times on the U22 as well, still the same thing each time, Android fine but with CoreELEC the remote starts to get screwy unless it has 100% line of sight.)
I'll probably have to revert to a standard A3/A2 Lite with CE & the U22 as they're not doing it at all. However, that's certainly a shame as my CE U22 is in a darkened room so the backlit keyboard in particular is extremely handy & the keyboard on a standard remote is very difficult to see indeed. (I don't use the keyboard on any of my A2 L/A3s enough to have completely memorised every character position either as some have
.)
I am now starting to wonder if it has something to do with the actual "base" Android firmware version as my U22 currently has the CEC/ARC fix test firmware installed & whether that's contributing to this as well(????). But, the same still applies as above, why just this one backlit A2 L & no other remotes exhibiting the same behaviour???
Perhaps that one particular dongle is prone to Wifi interference & line of sight is enough to minimise these issues but then become more pronounced again without the line of sight??? (If it was happening with a remote that I had more than one of I'd try re-pairing the same remote with another identical dongle & see if that was a factor but I only have one backlit A2 Lite & as far as I'm aware they have slightly different dongles (controllers) to the standard A2 Lite variant.)
Obviously, what's affecting this particular backlit A2 Lite could be completely subjective especially as I essentially have a test Android firmware dual boot too. As much as I question if it would be if any assistance either it may still be worth simply trying to adjust the position of your devices so that the dongle has an improved line of visibility to the remote too, (even though it shouldn't matter at all), or if you have a USB extension cable try it. It can't do any harm other than things don't look as tidy but even if it's just to see if it could possibly reduce and/or imorove these problems what's to lose?
(It's unlikely that I'll be changing the Android FW any time soon because of the known issues the current public release FW still has upon my AVR/TV, but as & when I do update the Android firmware I'll add additional info to this thread as to whether this particular issue changes or not based on the actual Android FW version installed.)
