Jump to content
Flirc Forums

jason

Administrators
  • Content Count

    2,501
  • Joined

  • Last visited

  • Days Won

    107

jason last won the day on August 1

jason had the most liked content!

Community Reputation

156 Excellent

About jason

  • Rank
    Administrator

Profile Information

  • Gender
    Male
  • Location
    Santa Clara
  • Interests
    flirc, that's all I have time for.

Recent Profile Visitors

14,005 profile views
  1. It's on flirc, you need to repair nothing. It should just work with your previously paired remote.
  2. Yes, shoot me a PM, let's connect over skype or gchat or whats app and lets get this worked out.
  3. I’ll need a volunteer to help pin this down. Not much time, but a good amount of interaction on trying various firmware images. Let me know who’s up for it. I’ll compensate with a refund and some additional products, some which will be released within the next few days and weeks.
  4. Yeah, I'm at a loss. I can't reproduce this. @arabesc Can you please let me know if this is happening with you and if W3CB suggestion work?
  5. That’s correct, go to file->upgrade firmware Not to worry, if it’s the wrong one, it wont upload. You can’t brick it.
  6. This is not working, we're messaging hours a part. I'll DM you my private contact info.
  7. Just saw this. Will look at this tomorrow. Definitely can't have the GUI open if you are doing this through the commandline
  8. I'm around right now, we're probably on different time zones. (I'm in PST) I'm also available most of tomorrow. Let me know what works.
  9. In your flirc.ini, can you make sure that libusb logging is enabled? libusb = false ; Log libusb events. <-- change this to true. I know my fix worked for a bunch of people, we can do a team viewer so I can look at it if the log doesn't show anything.
  10. I'm positive it's a firmware issue, but I can't for the life of me reproduce this. Can you guys post your OS version, your hardware version, whether it's USB 2.0 or 3.0 ports? Any other information. A picture of device manager when it boots into this 'bad state'. Etc. Here is the latest firmware, upload the correct sku for your hardware. Once I see the problem, I'll have a fix pushed in seconds, but there is no reason for you guys to keep waiting anymore. I'm really sorry. nemo.release.bin dori.release.bin
  11. Thanks for the extra info. I haven't been able to reproduce this yet with multiple flircs and pc's and usb ports. I must be missing something. Not to worry, I can always give you guys the old firmware, but let me continue looking, I'm sure I'll find it shortly. Today wasn't the best from a time perspective, I was split amongst a few things, but this is considered red hot urgent.
  12. In this state, does the GUI detect flirc and no buttons work? Or the GUI doesn't recognize it?
  13. If you go into file->advanced Can you tell me the sku you guys are using?
×
×
  • Create New...