jason
-
Posts
4,023 -
Joined
-
Last visited
-
Days Won
259
Everything posted by jason
-
I'd honestly run Linux. That'll tell you for certain if its bios or driver caused. I'm sorry as well.
-
really makes no logical sense. 14 and 15 are identical. In 15 I'm also checking for S2 and S3 on top of S1. 14 only checks for S1. Newly round apis in the chip. Im with Yawor. Download ubuntu on a USB stick. Boot it. See if the issue persists.
-
Kevin, you said earlier: Sorry about this but since upgrading from 4.0.14 to 4.0.15 I am no longer able to Wake the computer. im so confused. Now you said 12 was is the only one that works.
-
Because of your funny hardware issue with the logitech, I doubt this would have fixed it.
-
Holy shit the suspense is killing me. :)
-
Okay, confidence is fairly high with this one. Give this a shot. nemo.release-4.0.15.bin
-
try it and let me know.
-
One more note, the GUI should always be closed once you're done pairing. So there is no need to have it running without flirc present. I will address it, but it's really low on the list of priorities at the moment.
-
Transfer "old" configurations to a new Flirc dongle
jason replied to Flavia's topic in General Questions
I just pushed an update to try and fix this. Thanks to Yawor, he confirmed I had a bug. However, there is a small chance it wont work. Long story shorty, the new version are slightly different in capturing keys. Give the update a shot, and let me know. -
What OS are you running? I only see this occasionally for some reason. On my mac, it's fine 90% of the time, and then when my computer is left long, for some reason, the search slows down.
-
What motherboard model do you have? I'll read the manual to see if I can spot anything.
-
How about the order in which you plug in things. Does it make any difference if you plug in flirc or the unifying receiver first? On your other machines, do you have the same problem? Maybe the motherboard manufacturer has a usb driver update. USB devices have no idea what's plugged into the same machine, so it's most likely a usb stack/driver bug.
-
I think this is suspend vs sleep.
-
Wouldn't by any chance have another operating system around to try?
-
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.
-
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
-
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.
-
Okay, tried this: rundll32.exe powrprof.dll,SetSuspendStateLooks like it's turning of my USB to both keyboard and flirc.
-
Any chance you guys know how to enter S3 manually?
-
How did you find out what sleep mode you were using?
-
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?
-
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.
-
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
-
really glad to hear that and thanks for hanging in there.
-
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
