Jump to content

jason

Administrators
  • Posts

    2,761
  • Joined

  • Last visited

  • Days Won

    119

Everything posted by jason

  1. You'll want to add Device: Flirc Model: Shield Clear your configuration on the device. The configuration is built in. Let me know if that helps.
  2. Yeah, I'm back on development, will get a release out in 2 weeks.
  3. I don't know what the hell is wrong with windows. I'm sorry. There are no viruses. It's crazy. It doesn't say what it is, it's erroneous.
  4. I dug into this more, it's a generic linux kernel bug. From: https://stackoverflow.com/questions/35728129/usb-hid-device-poll-interval-on-linux/36002731#36002731 Another Reference Report, this states there is a workaround, there is not. An official kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=60586 with a discussion on the topic: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg24939.html I will not be changing the polling time in firmware to accommodate for this stupid linux bug. There is a way to change the polling time for specific USB devices, but mainly keyboards and mice. Flirc is a USB HID device, so there is no specific way to do the custom generic HID interface polling override. However, there seems to be a possible way to do it by patching the kernel: https://gitlab.freedesktop.org/panfrost/linux/commit/2ddc8e2d2b5902b376fee51585c8eed72b8836e7 This may be the route I try. But it's not urgent, since the workaround is fairly easy, just set it up on another computer. But it looks like I can just compile a patched kernel module so we can override the poll time of flirc, include it in my package. Free upcoming product for anyone willing to put the time in to the above to get the poll time override working on generic HID devices.
  5. It's done, packaging is done, I just have to pull the trigger. But the pandemic has been killing me. Every day, I'm slammed. I'm going to try and kick it off this week.
  6. I'd be interested in knowing this too. By the way, who the hell has a PS/2 port on their PC still?
  7. There is a bug in the upstream kernel. Do your pairing on another machine. I don’t have time to debug the kernel. The Kernel is dropping USB packets. I’ve got a ton of debug logs that show it on the wire ,and the kernel stack never gets it. The remedy is to slow down communication to the USB device. It’s possible to just push an update (which will have to be done on another machine), and the USB poll time increases and slows it down to fix it. But It slows it down considerably. If you use the blue port on the pi, it has a phy in front of it, and doesn’t help mitigate it completely, but helps a lot.
  8. Make sure the GUI is closed before running the command line.
  9. Make sure the GUI is closed before running the command line.
  10. looks awesome, pair that with the profile, and try it, let me know if that works. If it works, it's the remote
  11. something is not right, it's sending inconsistent signals. Is it low on batteries? You have any remote handy that you can try to see if we can narrow this down?
  12. Can you also post your config file? Can you do this again, don't hold your remote too close to flirc, in fact, point up towards the ceiling. Not seeing good results in the above.
  13. Open up my app on your PC, go to File->Device Log. Enable IR debugging. And press and hold the button in question. Post the log here.
  14. It should work, unless you are using a harmony. What remote are you using?
  15. Oh shit, I know what's going on. Sorry. You have two devices. For convenience, each device is setup to work with the harmony profiles out of the box, but can't know what it's plugged into. So all are enabled. Download my software, insert Flirc1. Go to file->Advanced. Disable All but Shield. Plug back in shield. insert Flirc2. Go to file->Advanced. Disable all but firetv. Plug back in firetv. So sorry about that.
  16. They should not be using the same commands, they are different. You aren’t pairing them with my software are you? Those profiles are pre-paired.
  17. It must be the backlight in your TV, it's emitting IR. Learn the signals with the TV off, and then it should ignore those spurious signals. Give it a shot, let me know.
  18. can you post your saved configuration?
  19. try in another room. Probably the lights. Let me know how that goes.
  20. @qwerky Overloaded with work, send me an email, I'll send you a new gen flirc. I don't want to look into the first generation at the moment.
×
×
  • Create New...