matt_garman

Most button presses ignored / only one in 5-10 button presses recognized

9 posts in this topic

FLIRC USB Firmware v4.1.1.  Remote is an Acoustic Research ARRS05G.  Using the Kodi profile.

OS is Ubuntu LTS 16.04:

matt@host:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

matt@host:~$ cat /etc/debian_version 
stretch/sid

Whenever I press a button on the remote, I'd say there's maybe a 20% chance it is recognized.  In other words, it seems most button presses are ignored.  This is with the FLIRC USB device plugged into the front of the PC, and me standing right in front of it, with the remote only a few inches away.

Using a (wired) USB keyboard, all button presses work immediately as expected.

I'm using Flirc v2.5.1, from Deb package flirc_2.5.1-1_amd64.deb (md5sum: 4ac86479eae26df57a676e9674bb699e).  Simply running Flirc and then exiting prints this out to the console:

matt@host:~$ Flirc                                                           
Can't load 'test.ini'                                                          
00: ff ff ff ff ff ff ff ff ff ff ff ff              ............              
00: ff ff ff ff ff ff ff ff ff ff ff ff              ............              
00: ff ff ff ff ff ff ff ff ff ff ff ff              ............              
00: ff ff ff ff ff ff ff ff ff ff ff ff              ............              
00: ff ff ff ff ff ff ff ff ff ff ff ff              ............              
Object::connect: No such signal QCheckBox::currentIndexChanged(int)            
[D] lib/libflirc/flirc_driver.c fl_major_version(387): something bad happened

That "something bad happened" doesn't inspire much confidence.

 

Share this post


Link to post
Share on other sites

don't hold the remote so close to the flirc. Even when you record it, you have to point it away from flirc, flirc is too sensitive. Try running as sudo.

Share this post


Link to post
Share on other sites
11 minutes ago, jason said:

don't hold the remote so close to the flirc. Even when you record it, you have to point it away from flirc, flirc is too sensitive. Try running as sudo.

The same thing happens when the remote is 10 to 15 feet away from FLIRC.  I put it close because I thought it might be a signal strength/integrity issue.

When you say "try running as sudo", run what under sudo?

To be clear, the general programming (i.e. the Flirc tool) worked just fine.  I was able to successfully program both the Simple and Kodi profiles.

The issue is when trying to actually use it under Kodi.  To add more detail, it's very inconsistent.  A few button presses might work as expected, but then another might take 10 or more presses to actually do something.  Only once have I seen a queue-type behavior, where I press the button multiple times, and the GUI delays then catches up.  Typically it as though the button press is ignored or not captured.

Share this post


Link to post
Share on other sites

What kind of remote are you using? Is the machine you are using it on the same as the one you pair it on?

Share this post


Link to post
Share on other sites
24 minutes ago, jason said:

What kind of remote are you using? Is the machine you are using it on the same as the one you pair it on?

Remote is an Acoustic Research ARRS05G.  Yes, I am pairing and using it on the same machine.

Share this post


Link to post
Share on other sites

Make sure the batteries are good.

Also, enable IR debugging in the File->Device Log. Enable IR debugging.

only hit the same button. Save to a file and post that.

Share this post


Link to post
Share on other sites

If that's not helpful let's set up a team viewer 

Share this post


Link to post
Share on other sites

Hi Jason, I will try the log.  I also have another remote I can test with.  It might be a few days (or even the weekend) before I have time to test this.  I will follow-up at that time.  Thanks!

Share this post


Link to post
Share on other sites

Log is attached.  What I did: reboot computer (figured best to start clean).  Started "Flirc" GUI program, did File->Device Log and Enabled IR debugging.

Then, within Kodi, I pressed the right arrow only, fifty (50) times.

Even after I was done pressing the arrow key, the log continued to fill... I watched it for maybe a minute or so, thinking it would eventually stop, but it never did.  So I saved it.  Log file clocks in at around 8000 lines (hence the gzip).

Hopefully this is helpful!

Thanks!

flirc_debug.20170719.txt.gz

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now