•  Previous
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 15
  • Next 
 
Thread Rating:
  • 3 Vote(s) - 5 Average
[T3] 2.4GHz and IR Air Mouse Remote Control
#46
(2016-09-23, 22:51)dasco Wrote: Hi kusanagi

I have three Windows 10 machines and the problem you describe happens on two machines. The two machines that have problems have dedicated graphics cards. Where as my NUC that has integrated graphics in the CPU works fine. However i have not narrowed down the problem as i have a work around that suits me. I just set the machine to go to sleep after 5 Minutes of no use and it will not wake up until a button is pressed. Hope this helps and may give you a direction to narrow down the problem if the work around does not suit.

Hi Dasco, thanks for your reply. My Windows 10 machine is a Zotac ZBOX CI520 that have only an integrated Intel graphics, essentially the same as a NUC, but the problem happens anyway. Sad
I will try my luck with the sleep time workaround if after a few more days I can't get to correct this problem.
Could you tell me the exact model of your NUC?

Best regards.
Reply
#47
(2016-09-24, 03:25)kusanagi Wrote:
(2016-09-23, 22:51)dasco Wrote: Hi kusanagi

I have three Windows 10 machines and the problem you describe happens on two machines. The two machines that have problems have dedicated graphics cards. Where as my NUC that has integrated graphics in the CPU works fine. However i have not narrowed down the problem as i have a work around that suits me. I just set the machine to go to sleep after 5 Minutes of no use and it will not wake up until a button is pressed. Hope this helps and may give you a direction to narrow down the problem if the work around does not suit.

Hi Dasco, thanks for your reply. My Windows 10 machine is a Zotac ZBOX CI520 that have only an integrated Intel graphics, essentially the same as a NUC, but the problem happens anyway. Sad
I will try my luck with the sleep time workaround if after a few more days I can't get to correct this problem.
Could you tell me the exact model of your NUC?

Best regards.
My NUC is a i5 Haswell Model (D54250WYK) This works perfectly when put to sleep using the power button.
Reply
#48
Remote came in yesterday.
Unfortunately, there are some problems with it:
- sometimes after adjusting volume (on or two up presses) the slider just goes all the way up. There is no led flashing, it just maxes out the volume. Nice feature for watching late night movies when kids are asleep Smile
- a couple of times after pressing some keys led just starts flashing rapidly, alternating between red and green color. Stops after a few seconds and during that time remote is unresponsive.
- sometimes there is no response to the key press, led flashes but nothing from Kodi.
Looks to me that the wifi range on T3 is not as good as on my old MX3-M, but didn't have the time to test the IR.
I guess could be some problem with the receiver.
Bad luck Sad
Reply
#49
(2016-09-27, 07:05)c-shadow Wrote: Remote came in yesterday.
Unfortunately, there are some problems with it:
- sometimes after adjusting volume (on or two up presses) the slider just goes all the way up. There is no led flashing, it just maxes out the volume. Nice feature for watching late night movies when kids are asleep Smile
- a couple of times after pressing some keys led just starts flashing rapidly, alternating between red and green color. Stops after a few seconds and during that time remote is unresponsive.
- sometimes there is no response to the key press, led flashes but nothing from Kodi.
Looks to me that the wifi range on T3 is not as good as on my old MX3-M, but didn't have the time to test the IR.
I guess could be some problem with the receiver.
Bad luck Sad

Hi c-Shadow

If your using Windows you could change your Audio controls from Windows Controlled to Kodi Controlled to see if that fixes your problem. However you need to install Auto Hot Key to do it.

I use the Kodi Audio on my system and do not have the problems you have indicated

1st step install AHK onto your system if you have not already.
2nd Step open Notepad and put the following code in it;

#ifwinActive,Kodi ;following items active in Kodi Only
VKAD::VK77 ; Windows Mute to Kodi Mute
VKAE::VK78 ; Windows Volume Down to Kodi Volume Down
VKAF::VK79 ; Windows Volume Up to Kodi Volume UP

3rd step. Save the above file with the Extension ".ahk" example "Windows Audio to Kodi.ahk" without quotation marks.
4th step. Right click on the AHK Script you just created and select "Compile Script" This converts the script to an executible file that you can run in Launcher4kodi.
5th step. Add the AHK Executible file to Windows Startup: " C: > Users > "Your Computer Name" > AppData > Roaming > Windows > Start Menu > Programs > Startup"

Restart Machine and Windows Audio Controls will now be Kodi Audio Controls on your T3 remote.
Reply
#50
I'm using libreelec which is linux based.
It seems that this remote is constantly "pinging" the receiver. If carried away from HTPC it flashes red-green.
The receiver was plugged in the back of my HTPC and there is a lot of cables, close to the speaker and other obstacles. Two days ago i plugged it in the front usb and so far so good.
This is the test i made: carried the remote to the kitchen, pressed volume up and volume on the HTPC in the living room went to 100%. If carried even further, at one point remote loses connection and starts flashing red-green.
It really could be that this receiver unit has weaker signal than my old MX3-M.

Besides the problem with the receiver, remote works ok, colored keys can be mapped which is an improvement over MX3, dedicated <back> and <enter> keys are fine, but the key with overlapping rectangles is not even registering in linux.

The device registers in linux like this:
Code:
lsusb
Bus 004 Device 002: ID 1d57:ad03 Xenta

dmesg
[136783.335993] input: FREEWAY TECHNOLOGY as /devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3:1.2/0003:1D57:AD03.0003/input/input19
[136783.390060] hid-generic 0003:1D57:AD03.0003: input,hiddev0,hidraw0: USB HID v1.01 Keyboard [FREEWAY TECHNOLOGY] on usb-0000:00:13.0-3/input2
[136783.393264] input: FREEWAY TECHNOLOGY as /devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3:1.3/0003:1D57:AD03.0004/input/input20
[136783.393740] hid-generic 0003:1D57:AD03.0004: input,hidraw1: USB HID v1.01 Mouse [FREEWAY TECHNOLOGY] on usb-0000:00:13.0-3/input3


Following is the output from evtest.
Normal response, on keydown evtest registers "value 1" and on key release "value 1":
Code:
Event: time 1475086924.355701, -------------- SYN_REPORT ------------
Event: time 1475086935.675610, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1475086935.675610, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1475086935.675610, -------------- SYN_REPORT ------------
Event: time 1475086935.875520, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1475086935.875520, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1475086935.875520, -------------- SYN_REPORT ------------

When the repeating event occurs, there is no "value 1" but instead evetest registers "value 2" indefinitely:
Code:
Event: time 1475086989.163544, -------------- SYN_REPORT ------------
Event: time 1475086991.115757, type 4 (EV_MSC), code 4 (MSC_SCAN), value c018a
Event: time 1475086991.115757, type 1 (EV_KEY), code 155 (KEY_MAIL), value 1
Event: time 1475086991.115757, -------------- SYN_REPORT ------------
Event: time 1475086992.117440, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.117440, -------------- SYN_REPORT ------------
Event: time 1475086992.150754, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.150754, -------------- SYN_REPORT ------------
Event: time 1475086992.183881, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.183881, -------------- SYN_REPORT ------------
Event: time 1475086992.220568, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.220568, -------------- SYN_REPORT ------------
Event: time 1475086992.253986, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.253986, -------------- SYN_REPORT ------------
Event: time 1475086992.287260, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.287260, -------------- SYN_REPORT ------------
Event: time 1475086992.320602, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.320602, -------------- SYN_REPORT ------------
Event: time 1475086992.353892, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
Event: time 1475086992.353892, -------------- SYN_REPORT ------------
Event: time 1475086992.387221, type 1 (EV_KEY), code 155 (KEY_MAIL), value 2
...
Reply
#51
(2016-10-02, 09:04)c-shadow Wrote: the key with overlapping rectangles is not even registering in linux.
You could use the key with rectangles also.
Hint: tune .config/hardwaredb.d for the remote.
I'll post my settings later
Reply
#52
(2016-09-27, 07:05)c-shadow Wrote: Remote came in yesterday.
Unfortunately, there are some problems with it:
- sometimes after adjusting volume (on or two up presses) the slider just goes all the way up. There is no led flashing, it just maxes out the volume. Nice feature for watching late night movies when kids are asleep Smile
- a couple of times after pressing some keys led just starts flashing rapidly, alternating between red and green color. Stops after a few seconds and during that time remote is unresponsive.
- sometimes there is no response to the key press, led flashes but nothing from Kodi.
Looks to me that the wifi range on T3 is not as good as on my old MX3-M, but didn't have the time to test the IR.
I guess could be some problem with the receiver.
Bad luck Sad

Hi c-shadow

Do you have the receiver plugged into a USB 3 port. I have had strange behavior when plugged into USB 3 ports problems fixed when plugged into USB 2.

Worth a try if you have not already.
Reply
#53
I've had this remote for a while now. I like it, but it does have a repeating key problem, or at least the one I have does. In RF mode, press and hold the volume up key (for example) and with it pressed flip the remote upside down. Now let go of the key. For me, it repeats indefinitely. The remote doesn't send a key released signal to the PC until I've pressed something else.
Reply
#54
(2016-10-15, 00:14)dasco Wrote: Hi c-shadow

Do you have the receiver plugged into a USB 3 port. I have had strange behavior when plugged into USB 3 ports problems fixed when plugged into USB 2.

Worth a try if you have not already.

No, its plugged into USB 2 port.
Reply
#55
Just ordered a few of this. They look great. The mx-3 was such a pain with the wakeup, and sleep-forget-idiocy.
Reply
#56
Has anyone bought this remote? The keyboard is better than T3, all keys are programmable, and the price is even lower.
Image
Reply
#57
Allegedly suffers from the problem of the remote going into mouse mode every time it wakes up, same as MX3.

See review on Amazon UK
Reply
#58
Really. Thanks.
Reply
#59
Had to change batteries on remote today as i was getting random repeats and range issues. approx 5 Months of use out of batteries.
Reply
#60
Hello, Forum noob here. I just got my hands on one of these remotes and for me it works great on my android box without any mods just plug and play. However, I also have a retropie (rasberrypi3) with kodi and the remote only works as an air mouse and the keyboard does nothing. I added keymaps but only succeeded in causing the airmouse to no longer work!?! So has anyone tackled this problem? or does someone have keymap file that will work for this setup? Thanks in advance. Oh and if you are tempted to tell me to search and read for the answer before posting you know what you can go do. I have googled until my eyes are burning and not found an answer that worked for me. So please experts, lead me down the path to success.
Thank you for your time in advance.
Reply
  •  Previous
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 15
  • Next 



[T3] 2.4GHz and IR Air Mouse Remote Control53