Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,730
  • Joined

  • Last visited

  • Days Won

    228

Everything posted by jason

  1. Wouldn't by any chance have another operating system around to try?
  2. Try putting the flirc on a separate hub as the unifying receiver. For example, if they are both in the back, move one to the front. Very strange. I have a unifying receiver as well as a bluetooth dongle, and tried for several hours to reproduce this without seeing anything. I tried in linux and windows 10, I also don't have any unifying software installed.
  3. No need to enable it on generation 2.0, it's going to be grayed out. Are you guys using the wake key to wake the machine? Don't record the wake key, that maybe be an issue, just use any other recorded key
  4. I can't reproduce this, my computer crashes when I go into suspend. Indurating. No way I can really debug this remotely without some special hardware either. Let me scratch my head.
  5. Okay, tried this: rundll32.exe powrprof.dll,SetSuspendStateLooks like it's turning of my USB to both keyboard and flirc.
  6. Any chance you guys know how to enter S3 manually?
  7. How did you find out what sleep mode you were using?
  8. In "Device Manager" scroll down to flirc keyboard and click on it, then double click on your keyboard device, when the window opens click on "Power Management" make sure the box that says "Allow this device to wake the computer" is checked. Let me know if that was checked. I'm pulling my hair out over this. How are you getting your machine to turn on again. Do you have to hit the power button, or can you hit a keyboard key?
  9. Thanks for all the quick feedback, I appreciate it. Okay, so I can't reproduce this, maybe it's because I'm doing a suspend vs deep sleep. How are you guys entering sleep? What I'm doing is recording the following key: http://cl.flirc.io/jA4m I enter sleep mode using that, and then hit any recorded key to wake the machine up. I've done this for hours without it giving me any issues. But again, I supposed I need to figure out how to enter deep sleep. I'm so very sorry for this, but I'm not going to give up. I'll ensure you guys that are helping me and being patient through this receive refunds as a thanks for my gratitude. PM me for that, but lets keep at it.
  10. I'll see if I can whip something up to save the device log to file from the GUI. In the mean time, try the attached. nemo.beta-4.0.14.bin
  11. really glad to hear that and thanks for hanging in there.
  12. Kevin, might need to run the command prompt as an administrator. Not to worry, still very much working on it. I appreciate the help and feedback
  13. the gui needs to be closed for the commandline to work
  14. Also, I ship a commandline version with the GUI. Make sure the GUI is closed, and then run the following command: flirc_util (or flirc_util.exe if on windows) device_log This will spit out a log of information to the commandline, please paste that here as well.
  15. Kevin, Foxxi, can you guys tell summarize problem with each version. Also, what OS are you guys running on? .11 was actually waking for you both? Let's come up with some terminology: present on wake: device shows up when the computer wakes up wakes from suspend: device will wake the machine up from a suspend state. Simple true or false for each of these would be extremely helpful, also, these are independent of each other. Thanks for the help.
  16. I appreciate all the feedback and help testing guys. Here is another version to try. Don't worry, I'll get it. nemo.beta-4.0.12.bin
  17. Thanks Kevin for pointing me back to this thread. Can you try the attached. File->Upgrade, point to this image. Does it ever work, or is it intermittent. nemo.beta-4.0.11.bin
  18. Just the media center keys on the Controller->Media Keys will work. The 'wake' key wont work for rev2 on the keyboard controller yet, I'll need to put in a patch for that. Added to my list of things to do. Does a keyboard wake your machine up?
  19. can you guys send me a link to a device, I'll try and build in support.
  20. great, glad it's working now. Thanks for letting me know.
  21. Yeah, Amazon is an official channel too. You really shouldn't need the right angle adapter, have you tried it without? Mine is behind our tv that's against our wall, doesn't skip a beat.
  22. Don't use the profile you are using. Add the Flirc - FireTV profile, then record over those keys. Not sure which profile you are using. I'm going to reach out to logitech shortly and get them to create a profile.
  23. Do you mean that keys feel sticky? Do they eventually un stick?
  24. I was working at NVIDIA and close to the team that was working on the shield. I had no idea they dropped the IR support until I started getting emails from people telling me they are actually encouraging folks my way. Whoever is doing that at NVIDIA has no idea that I was working there a couple months ago along side the shield team. Crazy. I really appreciate the feedback. Unfortunately, it's a lot easier for someone emotionally driven to send me an upset email than it is for the happy users at home to write in. So it really fuels me in the pursuit of a better product/products. Thank you. That's a lot of flircs. Any need for any more just write in and I'll get you a discount. Really goes for anyone here. Thanks guys.
×
×
  • Create New...