I'm trying to get my GYR3101US remote working in lmce. If I plug it into the core then the buttons all seem to work. If I plug it into any of my 3 MDs then the windows button pauses and that's pretty much it.
The remote is being detected as "GO Cordless GC1005M" (#1812) on all systems.
Any ideas what might be wrong?
Thanks in advance!
Please update the packages on all your media directors. Orbiter was recently changed to accomodate some needed fixes.
-Thom
Thanks Thom for the help.
I did a chroot to each moon and did an apt-get upgrade. It updated a bunch of pluto packages but the remotes still aren't fully functional on the MDs. The mouse keys, the arrow keys and the Windows key work but nothing else (tested in videos and in tv).
Did I update the packages correctly?
That may work, though i just ssh to the MD as root and perform a:
apt-get update; apt-get upgrade
I have updated to the latest version, using the apt-get methods. I am still having no luck with my Gyration remote.
I can use it as a mouse. During media playback though, the Win/Menu button merely pauses/un-pauses the media.
I will try a SQL/CVS update tonight, and see if it is a template issue.
Best Regards,
Seth
Hi Seth - long time no talk! What issue are you experiencing specifically? Could you confirm we're talking about 810 and the gyration 3101? I'm not having any issues what so ever with any of my remotes on 810 on any of my media directors and I'm on the latest rev of 810. I'd like to be able to reproduce the issue so we can get closure to it.
I can't speak for Seth but I'm running the latest 810 and 3101 remotes. They use to work but then stopped (don't remember exactly when but it was a while ago).
The windows key pauses and resumes and I think 1 other button works but no other buttons do anything. I was thinking of rebuilding from scratch to see if that solves the problem. Just haven't had the time yet.
Again, if anyone experiences these issues, please update both apt and the dce repository in sqlcvs.
-Thom
:)
Hi All.
This is on 810 - latest apt-get update/upgrade.
I have done a sqlcvs sync for DCE, WEB, and IR.
After it completed, I reloaded the router. No difference.
After that I rebooted the MD with the remote. No difference
After that I rebooted everything. No difference.
I am downloading the RC1. I plan on trowing up a new core, dual booting 810/1004. Can test with 1004, then run 810 for Production. I have some newer hardware that I would like to test. But if it is horribly broken, then I will have 810 to fall back on.
Not sure what else to try. Truth be known we use weborbiter and android touch orbiter more than the remote. Currently we have an MCE remote hooked to this MD using the USB-UIRT, and it works swimmingly.
Let me know if there is anything else to try.
Off Topic. I just purchased an LG 50" plasma (50PV450) and am going to attempt hooking up serial control. After this is successful, I wish to create a proper template, so that it is available to other users. Can't wait to see this thing work over rs232 control.
Thanks, and Best Regards,
Seth
Hi Seth - what issue are you experiencing explicitely? Is the stop button turning down volume, only the pause button works, or is it something else?
Hi.
:)
No the stop button does not work at all. Initially you press the Windows button, and it will call up the menu bar. And the gyro mouse and the left an right button work. Nothing else does. After you select and play some media source, if you press the windows button again. It only pauses the media. It does not bring up the menu again.
I can not get the number keys or the media keys (play/pause/stop/ffwd/rwd/rec) to work at all. The volume button also does nothing.
It's like it was before Thom created the template for the working version I had before the update.
Tonight I will try deleting it, and re-adding it, to see if it pulls a working device template.
Best Regards,
Seth
Hi Seth -
Thom just suggested another way to check as well, if you look at your 1812 device template (the GO cordless blah blah), what does it say next to the block device (string)?
Mine has: /dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-kbd|/dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-mouse
An older revision will have something different.
;D
Hi.
I will check that tonight when I get home from work, I should really open it up so that I can access the webadmin from outside the house. :( See if it is in fact wrong. Then try to figure out where to get the right one.
Thanks and Best Regards,
Seth
Thanks Seth, I'm interested to know the result!
:)
Evening. I have checked the template being used for my gyration remote. it is 1812.
The following is in the device info:
Block Device /dev/input/event1
So it is different from your working template.
Regards,
Seth
No seth, not in the device instance, in the device template itself. In the original device template, this is blank, in the new one, it's like Murdock's.
-Thom
I did the same thing!
Go to: Advanced --> Configuration --> Device Templates
Pull down "Device Template" and start typing Go and you'll pull up the 'Go Cordless GC1005M' and click on "Pick device template"
Block Device (String) 158 is under the 'Device Data' heading and you're looking for the 'Default Value' column to the right of the 'comments' column. What do you have there?
Hi Seth - any luck on this?
Uplink just fixed the Gyration & Fiire remotes and we have released an update to Dianemo users this evening.
All the best
Andrew
Thanks Andrew, Seth or tkmedia could you confirm whether this fix worked for you?
Quote from: Murdock on September 04, 2011, 04:50:31 PM
Thanks Andrew, Seth or tkmedia could you confirm whether this fix worked for you?
Just to let you know we have found a problem with the 'fast forward' button on the Fiire remote with this update. At the moment this is the only issue we are aware of. However there is no fix for this specific issue right now - and none on the horizon either I am afraid.
All the best
Andrew
Hi all,
I have the following under
#152 Block Device(string)
/dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-kbd|/dev/input/by-id/usb-Gyration_Gyration_RF_Technology_Receiver-event-mouse
So it is just like Murdock's. Yet mine still does not work.
Not sure what else to check. Please let me know.
Best Regards,
Seth
can you comment out (or add the LV_DEBUG log level to your pluto.conf), reload router, and tail -f | grep for GenericHIDInterface?
-Thom
Ive managed to get most of my Gyration working by editing the #59 Configuration(string) data field with the following:
1,10,U,Y
2,11,U,Y
3,12,U,Y
4,13,U,Y
5,14,U,Y
6,15,U,Y
7,16,U,Y
8,17,U,Y
9,18,U,Y
0,19,U,Y
Down,104,R,Y
Up,98,R,Y
Left,100,R,Y
Right,102,R,Y
ok,36,D,Y
SkipNext,171,R
SkipPrior,173,R
chup,120402,R
chdown,120403,R
fastforward,216,D
Rewind,176,D
Pause,127,D
Play,215D
Mute,121,D
Stop,174,D
voldn,122,R
VolUp,123,R
Record,175,D
Guide,120362,U
info,138,U
help,134,H
Power,150,U
Halt,223,H
Music,120391,U
Videos,120393,U
tv,234,U
Pictures,187,U
Back,166,D
menu,120389,U
start,110,U
media,120366,U
lights,120273,H
I wouldnt be able to tell you which exact fields Ive changed, but comparing to what you have may be revealing.
Dennis
Hi. Sorry, with the flooding and what not here in PA, I have not had a chance to check into this. I did though this morning get the opportunity.
Here below are my entries from #59 on the template. Most are identcal to yours, but there are some that are different. I have marked them in red:
1,10,U,Y
2,11,U,Y
3,12,U,Y
4,13,U,Y
5,14,U,Y
6,15,U,Y
7,16,U,Y
8,17,U,Y
9,18,U,Y
0,19,U,Y
Down,104,R,Y
Up,98,R,Y
Left,100,R,Y
Right,102,R,Y
ok,36,D,Y
SkipNext,120163,R
SkipPrior,120165,R
chup,120402,R
chdown,120403,R
fastforward,180,D
Rewind,152,D
Pause,110,D
Play,179,D
Mute,160,D
Stop,164,D
voldn,174,R
VolUp,176,R
Record,177,D
Guide,120362,U
info,134,U
help,134,H
Power,223,U
Halt,223,H
Music,120391,U
Videos,120393,U
tv,237,U
Pictures,187,U
Back,234,D
menu,120389,U
media,120366,U
lights,120273,H
Not sure if changing them is correct. Perhaps someone else can look at their #59 to get a third or even a fourth pair of eyes on the issue.
Best Regards,
Seth
;D
I can confirm that the codes Dennis posted above, do in fact work. I replaced the ones in my #59 with the ones he has posted in this thread, and now it works without issue.
Perhaps we can have this newly modified template submitted that way the next person who installs RC1 will not have these issues.
Best Regards,
Seth
Glad they worked for you Seth!
Dennis
Thx - Worked for me too. Old codes were:
1,10,U,Y
2,11,U,Y
3,12,U,Y
4,13,U,Y
5,14,U,Y
6,15,U,Y
7,16,U,Y
8,17,U,Y
9,18,U,Y
0,19,U,Y
Down,104,R,Y
Up,98,R,Y
Left,100,R,Y
Right,102,R,Y
ok,36,D,Y
SkipNext,120163,R
SkipPrior,120165,R
chup,120402,R
chdown,120403,R
fastforward,180,D
Rewind,152,D
Pause,110,D
Play,179,D
Mute,160,D
Stop,164,D
voldn,174,R
VolUp,176,R
Record,177,D
Guide,120362,U
info,134,U
help,134,H
Power,223,U
Halt,223,H
Music,120391,U
Videos,120393,U
tv,237,U
Pictures,187,U
Back,234,D
menu,120389,U
media,120366,U
lights,120273,H
I'm not smart enough to figure out WHY the old codes stopped working... but using xev, i wrote down the codes generated for the buttons.. then tested them in the template..
It was ROUGH without the remote working.
Dennis
Thanks, works for me too!
I was finally able to reproduce this on a fresh MD install of 1004. I've updated the SQLCVS repo with batch 3468 to correct it with the mappings in this thread. Moving forward the gyrations should 'just work' for everyone.
I'm running 8.10 and had the same problem, but once I manually edited the device template, all is well. The latest updates do not have the fix for 8.10, so I'm hoping those will also get fixed.
I'm glad someone else had the same problem I had for once.
I did an update/upgrade yesterday of my 8.10 system and the functionality of my Gyration GYR3101US deteriorated.
Specifically, volume up and down did not work nor did the mute although I think volume down caused MythTV to turn off. The power button did nothing and the pause acted as if the Windows button had been pressed.
The #59 entry of the 1812 template matched the entries in http://forum.linuxmce.org/index.php/topic,11871.msg83769.html#msg83769 (http://forum.linuxmce.org/index.php/topic,11871.msg83769.html#msg83769)
It looked like the entries that Seth noted as different http://forum.linuxmce.org/index.php/topic,11871.msg83808.html#msg83808 (http://forum.linuxmce.org/index.php/topic,11871.msg83808.html#msg83808) were the ones that I was having problems with so I updated the 1812 template with them and did a Quick Reload Router and now my remote works as expected again.
Now the question is why is the behavior of my remote different than others?
- Tom