Gyration Remote Works on Core but not Media Directors

[rdmustang]

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!

[tschak909]

Please update the packages on all your media directors. Orbiter was recently changed to accomodate some needed fixes.

-Thom

[rdmustang]

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?

[Murdock]

That may work, though i just ssh to the MD as root and perform a:
apt-get update; apt-get upgrade

[seth]

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

[Murdock]

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.

[rdmustang]

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.

[tschak909]

Again, if anyone experiences these issues, please update both apt and the dce repository in sqlcvs.

-Thom

[seth]

 
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

[Murdock]

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?

[seth]

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

[Murdock]

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.

[seth]

 
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

[Murdock]

Thanks Seth, I'm interested to know the result!

[seth]

 

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