Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Nathan last won the day on April 26

Nathan had the most liked content!


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Nathan's Achievements

  1. Yep. Bottom of the case is plastic and there are enough gaps around the body that wifi has not been a problem ever since onboard wifi was introduced.
  2. Hi, nope, both sides of the pad work equally well. Be sure to remove any film before applying.
  3. I'm guessing the simplest way to deal with this issue is when we add long press functionality (or whatever we end up doing). Make a quick tap play and a long press of the same button pause. Or vice versa.
  4. Just to double check, can you unplug the remote, remove the batteries, and then plug it back in? If it still does the red light thing, PM me.
  5. Sorry this was missed the last go around. Will add a ticket so we catch it this time
  6. Looks to be a Windows bug. Should have a fix in place with the next release.
  7. This is really a Flirc issue, it sounds like. Simplest way to debug is to plug the flirc into a computer, open the app, go to File - Device Log, and then in the new window tick Enable IR Debugging. Ideally you'd do this with a laptop in the same environment as where it's sitting normally. Then you'll be able to see whether the codes are showing up in your Flirc as you send them.
  8. Have you tried relearning the buttons within the Flirc app? While there, you can switch to the Full Keyboard controller and add Pg Up and Pg Down to some pre-programmed dummy keys on the Skip
  9. Yep, that's the goal. Ultimately it'd be really nice if we had something like a wikipedia of remote codes. Or at the very least a way to make it where once a code has been recorded by a community member, it never needs to be recorded again. Lot of background work on how to make this happen. edit: It occurs to me I might have misunderstood what you were asking for. If you mean pre-built activities, probably not. Everyone's setup is unique. We try to make guesses about how people will use the Skip, but they're ultimately just guesses.
  10. Nope, should still be fine to use. Thermal pads (and Pi chipsets) are much more forgiving than Intel/AMD CPUs and compound paste. :)
  11. Nathan

    I wished ?????

    You kinda answered your own question with regard to learning. The learning function is alpha software, and it's gonna feel like alpha software. It'll continue to improve as we go along.
  12. The film should just be clear/transparent. You should be able to tell if it's on by touching it. If it's sticky, then the film is off. If it's slick, then the film is still on there.
  13. The short answer is probably yes. The longer answer is we want to create a way to make buttons do two different things with long press being one possible way. The other way is to use the color button as an alt that changes all buttons, not just the color buttons. I think that might be third on our current feature list behind learning (which we're working on now) and smart activity switching (which is planned next).
  14. That is definitely in the plans. I think for the most part we're just holding off until the Skip can handle remote learning and possibly smart activity switching. Smart learning is definitely the biggest blocker though. We don't expect all Amazon buyers to be as technically savvy as our forum users, so we need to make it as mistake proof as possible before going wide on Amazon.
  15. No worries. Given the somewhat unusual shape of the Pi5 heatsink, it's natural for long time users to be a little perplexed by the fairly different thermal pad. :)
  • Create New...