I worked in the last 30 years helping developers to do their job and i know exactly how they work, they prefer workarounds instead to fix things.
Not here they don't. Unless there is really no other way. So if there is another way, like I said, I'm all for it.
I do not have vu+,I connected the bluetooth keyboard.
Not relevant for this issue, this is about alphanumeric IR remotes.
When it came to IR devices, the transmitter is not aware of it's own capabilities does not transmit how many keys have or which ones, not even the type of transmitter, those are defined in the driver, in this case the driver is more capable then expected....
Vu driver report KEY_A because it has that defined and can be used, this is not wrong.
VU+ could have used a different RC type for example, the old Dreambox had multiple remotes, which can be distinguished just fine.
No matter how you twist it, we're in this mess because the VU+ drivers don't make the difference, but call everything a "Dreambox remote control (Advanced)". No doubt because that is a string the old DMM Enigma checked on, and their Enigma is an antique fork of that DMM version.
I didn't had a qwerty remote but i saw that the Vu driver is capable to understand more than a simple remote control and wanted to build an Android app to send all qwerty codes which is almost done, I even bought a QWERTY remote for 20 euros to make my dream comes true, but surprise, we have a workaround here and we are not willing to purchase a 20 bucks qwerty remote control to do a better job.
Are you now suggesting someone of us needs to spend some of their own money to fix a problem, for free, that you have?
I have a better idea, why don't you buy us such a remote?
I worked in the last 30 years helping developers to do their job and i know exactly how they work, they prefer workarounds instead to fix things.
Then you should, as no other, know that when an issue is found, you do a root cause analysis, and you fix the root cause. As we can't do that (we don't have access to the driver source, and as said the driver can't see the difference either), the next best think is to work around it.
And, again as already mentioned, I don't have any issue with introducing an override config value to you can define you have an alphanumeric remote. It wasn't done, because you are the first one to complain about this remote.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
