Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,820
  • Joined

  • Last visited

  • Days Won

    241

Everything posted by jason

  1. Make sure ADB debug is off in your firetv settings.
  2. I have two repo's, one for 32 bit, and one for 64. I'll post a statically compiled binary soon. But I recommend the installer. You can ignore the last upgrade attempt, erroneous. If you don't install it via apt-get, you wont get the udev rule, which will require you to use sudo.
  3. PM Me, I'll send you the new one. Not worth any one's trouble banging our heads against the wall.
  4. that's correct. Just wanted to make sure. It's possible interface 0 has the driver, which is the keyboard. That would cause this. You'll have to remove it the driver on that one. Let me know if that's helpful.
  5. Do you have the stainless steel version, or the plastic version?
  6. I've als updated the windows media center controller so it should be fully accurate for you guys to use: http://cl.flirc.io/kpNo
  7. Thank you guys so much for being supportive and awesome. Really does mean a lot.
  8. Thanks so much for the patience, means a lot. Pushed publicly as well.
  9. Once again, thanks for the awesome feedaback. Sat down today and figured out all the issues. Bug that caused all other keys to stop working without modifiers. ctrl+f and ctrl+b - windows is so picky. I need to insert control, then 'f'. Then I need to release the 'f' then the control. All this is being done now. This is probably the last one you'll test and the one that will be pushed publicly. (Understood you are using nemo, they are identical, but for those who don't have the nemo sku, the dori is posted here too) dori.release-4.0.24.bin nemo.release-4.0.24.bin
  10. Okay, I've figured out the issue. Here is an update. I think I'm going to always sequence the modifiers by default. Don't see why not as I'm emulating a keyboard and no one can push them all at the same time. Let me know if there are any issues. dori.release-4.0.23.bin nemo.release-4.0.23.bin
  11. These are the current releases. I'll reproduce the issue you provided and issue a fix most likely by tomorrow. dori.release-4.0.21.bin nemo.release-4.0.21.bin
  12. Ah I'm out right now. I'll post old images for you when I get the girls in bed. Thanks for the explanation. This is actually really helpful
  13. Ah I'm out right now. I'll post old images for you when I get the girls in bed. Thanks for the explanation. This is actually really helpful
  14. The remote profile would select the correct flirc. Let's say you pair a panasonic tv profile with one flirc and a samsung profile with the other flirc. Each would respond accordingly.
  15. Sorry for the delay, took me a bit longer. I've got a working firmware image. I will have an advanced setting to enable/disable this. In this current version, it's enabled by default and can't be disabled. Please let me know if it's working okay. If you try to upload and get 'invalid sku' try the other image. I will update the GUI later to post more detail about the firmware, at this time, it's guess and check. nemo.release-4.0.22.bin dori.release-4.0.22.bin
  16. http://cl.flirc.io/khGH It wont light up once you've recorded it.I think just the standard keyboard keys will do that.
  17. I'll buy this remote and try and figure out what's going on
  18. I'm confident this was the issue. After seeing it, finding the problem, understanding it, I have extremely high confidence. This problem only exists for a small portion of users, and it follows windows as well. Blatant disregard to violate the USB spec. I owe you guys a second unit for your patience and help.
  19. Thanks for the patience guys. We've got a beta image working, but it stops working ofter some time. There is likely a security check that happens periodically. We'll figure it out and I'll keep you guys posted.
  20. I owe you guys the thank you. And endless amount of gratitude for your patience and support.
  21. Okay guys, I think I figured it out. I pushed an update, GUI version v2.3.8 which has new firmware in it. So confident, I made it public, however, this may in fact just fix @Montas system. But I'm fairly confident. Seems to be a windows only thing, they send a set remote wake up feature request down to the device, in which case I would send a stall/nack. Windows said, 'oh yeah, fuck you' and then disconnected me. I'm now returning OK. This is not a required feature, apparently windows 10 says it is. Please don't leave me hanging if it works, please report back here and let me know. This was both brutal in finding, repeating, and solving.
  22. I just announced the new one at maker faire, it's in mass production now. The one on amazon is the original.
  23. I've got the other system up and running @Montas suggested and I've reproduced it. I'm furiously trying to find a remedy and won't stop until I do.
  24. Got most of the hardware, will start assembling and installing windows tomorrow. Don't worry about uploading anything just yet. Let me see if I can reproduce this on my own first.
×
×
  • Create New...