Kevin Cowans Posted January 31, 2017 Report Share Posted January 31, 2017 (edited) HelloMy issues seem to be fixed in the v2.2.1 release.ThanksKevin Edited January 31, 2017 by Kevin Cowans Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted January 31, 2017 Report Share Posted January 31, 2017 (edited) Hello allUnfortunately it seems I was premature in stating that my issues were fixed.I installed the new version (v2.2.1), rebooted and then, using my Remote I put the PC to Sleep, then I selected my HTPC Activity on my Harmony Remote and the PC Resumed.At this point, thinking that the issues were fixed I put the PC to sleep again and went to watch some TV.Unfortunately, upon returning to the PC I selected the HTPC Activity on my Remote however the PC did not Resume this time, I had to use my USB Wireless Keyboard to Resume it.Upon checking, the Flirc USB is showing as Disconnected again, sorry.Please let me know if you need any further information.Thanks in advanceKevin Edited February 1, 2017 by Kevin Cowans Quote Link to comment Share on other sites More sharing options...
Foxxi Posted February 1, 2017 Report Share Posted February 1, 2017 (edited) Hello allUnfortunately it seems I was premature in stating that my issues were fixed.I installed the new version, rebooted and then, using my Remote I put the PC to Sleep, then I selected my HTPC Activity on my Harmony Remote and the PC Resumed.At this point, thinking that the issues were fixed I put the PC to sleep again and went to watch some TV.Unfortunately, upon returning to the PC I selected the HTPC Activity on my Remote however the PC did not Resume this time, I had to use my USB Wireless Keyboard to Resume it.Upon checking, the Flirc USB is showing as Disconnected again, sorry.Please let me know if you need any further information.Thanks in advanceKevini have the same2 times the pc gets waked up with the stick but when its on (in the windows) the flirc is disconnected, i have to remove it and plug it in againthe advanced settings are greyed out. Edited February 1, 2017 by Foxxi Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 1, 2017 Report Share Posted February 1, 2017 HelloIt is good to have this confirmed that I am not alone.ThanksKevin Quote Link to comment Share on other sites More sharing options...
madmanuel Posted February 4, 2017 Author Report Share Posted February 4, 2017 Hi Kevin, unfortunately, I've got the same thing happening. It works once or twice, but then gets disconnected again :( Quote Link to comment Share on other sites More sharing options...
Bean72 Posted February 4, 2017 Report Share Posted February 4, 2017 I haven't had any issues since the update, I use it on a daily basis as well. Have you tried on a different PC to see if you run into the same problems?I also noticed after the update I had to change the usb port that flirc is plugged in to because it had connection issues. Prior to the update I was messing around a lot with the USB power management settings in hopes of getting it to work, using a different port on a different internal hub fixed it for me. Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 5, 2017 Report Share Posted February 5, 2017 HelloI am enclosing a couple of screen captures of Device Manager showing the error for the Flirc USB.After I receive this error if I Disable the Device and then Enable it the Flirc Keyboard Device will show under Keyboards and the Flirc will work fine until the next time I receive the error.I hope these help.Kevin Quote Link to comment Share on other sites More sharing options...
SimonH Posted February 8, 2017 Report Share Posted February 8, 2017 (edited) Latest version is working for me so far - but only just installed and tested today though ... will report back if I find issues. Edited February 8, 2017 by SimonH Quote Link to comment Share on other sites More sharing options...
jason Posted February 10, 2017 Report Share Posted February 10, 2017 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 Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 10, 2017 Report Share Posted February 10, 2017 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.binHello JasonI have updated the FW and will test it over the next few days and post my findings here.Unfortunately this issue is the worst kind, intermittent, however, it happens more often than not.Thanks in advanceKevin Quote Link to comment Share on other sites More sharing options...
Foxxi Posted February 10, 2017 Report Share Posted February 10, 2017 i do a view test and i works good on my htpc. thanks for the fast update Quote Link to comment Share on other sites More sharing options...
revs Posted February 10, 2017 Report Share Posted February 10, 2017 Just registered to get the beta firmware and will test! Quote Link to comment Share on other sites More sharing options...
revs Posted February 10, 2017 Report Share Posted February 10, 2017 (edited) Bad news I'm afraid - although initially it looked like it was working, every now and then it just wont wake from sleep.It does however always show as connected in the GUI (even if wake from sleep didnt work). Also i can always wake up the PC using a keyboard when the FLIRC doesnt work, so USB wake is ok. Edited February 10, 2017 by revs Quote Link to comment Share on other sites More sharing options...
Foxxi Posted February 10, 2017 Report Share Posted February 10, 2017 did you re register the wake up button again? i had the same but after reg the wake up, it works great Quote Link to comment Share on other sites More sharing options...
revs Posted February 10, 2017 Report Share Posted February 10, 2017 did you re register the wake up button again? i had the same but after reg the wake up, it works greatI havent, as I assumed that after it worked a few times that I didnt need to re-register.Since my last post, its worked, still testing (i have the PC set to sleep every few minutes, and when it does I grab the remote and test) Quote Link to comment Share on other sites More sharing options...
Foxxi Posted February 10, 2017 Report Share Posted February 10, 2017 yes now after 20 tests i have it also again, it do not wake up :( but it works better then with the last version Quote Link to comment Share on other sites More sharing options...
revs Posted February 10, 2017 Report Share Posted February 10, 2017 Yep mine just stopped working again, after successfully waking up the PC for quite a while Quote Link to comment Share on other sites More sharing options...
jason Posted February 10, 2017 Report Share Posted February 10, 2017 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 Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 10, 2017 Report Share Posted February 10, 2017 Hello JasonI had chance to test the 4.0.11 FW and the issue of the Flirc being disconnected when Resuming from Sleep seems to have been fixed (at least it is during the testing I have managed to do), however, the Waking from Sleep still does not work.Waking is also not working with 4.0.12 FW.Thanks in advanceKevin Quote Link to comment Share on other sites More sharing options...
Foxxi Posted February 10, 2017 Report Share Posted February 10, 2017 thanks but 0.12 do not wakeup at all here,0.11 runs a lot better Quote Link to comment Share on other sites More sharing options...
jason Posted February 10, 2017 Report Share Posted February 10, 2017 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 upwakes 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. Quote Link to comment Share on other sites More sharing options...
jason Posted February 10, 2017 Report Share Posted February 10, 2017 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_logThis will spit out a log of information to the commandline, please paste that here as well. Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 10, 2017 Report Share Posted February 10, 2017 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:Windows 10 Home x64 (up to date as of today)present on wake: device shows up when the computer wakes upTruewakes from suspend: device will wake the machine up from a suspend state. FalseSimple true or false for each of these would be extremely helpful, also, these are independent of each other.Thanks for the help. Also, running the command you gave gives the following error:PS C:\Program Files (x86)\Flirc> .\flirc_util.exe device_log[D] lib/libtransport/hid.c hid_send_packet(83): IError getting versiondevice disconnected, can't run commandI checked in the Flirc GUI and the Device is showing as connected.I hope this helps.Thanks in advanceKevin Quote Link to comment Share on other sites More sharing options...
jason Posted February 10, 2017 Report Share Posted February 10, 2017 Also, running the command you gave gives the following error:PS C:\Program Files (x86)\Flirc> .\flirc_util.exe device_log[D] lib/libtransport/hid.c hid_send_packet(83): IError getting versiondevice disconnected, can't run commandI checked in the Flirc GUI and the Device is showing as connected.I hope this helps.Thanks in advanceKevinthe gui needs to be closed for the commandline to work Quote Link to comment Share on other sites More sharing options...
Kevin Cowans Posted February 11, 2017 Report Share Posted February 11, 2017 (edited) Hello JasonThe GUI was closed.I even tried running the command after a Reboot and received the same Error.Thanks in advanceKevin Edited February 11, 2017 by Kevin Cowans Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.