Hello Jason Right, Linux it is. I have found the download for the ubunto desktop iso and will be able to create a Bootable USB without issue, however, how do I go about using the Flirc with it? Sorry, but in my 35 years of using computers I have never used linux :( Thanks in advance Kevin
Hello Jason I agree, it makes no sense. Also, I am using Windows 10 Home on the HTPC when I prefer the Pro Editions as there are no restrictions or missing features. I have been doing some more testing and for some unknown reason I am now able to Wake the computer with 4.0.15. And now it has stopped working again. I really do not understand this. Would you recommend doing a Windows Reset first or trying the Ubunto on a USB Stick? Either way, I am going to wait until I receive the Bluetooth Adapter so that I can use my keyboard again. Really sorry about all this. Kevin
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.
Hello Jason Sorry, I got my versions wrong, I was able to Wake the computer for a while using 4.0.14 but when I upgraded to 4.0.15 I had issues again as in it would not Wake the computer at all. When I was using 4.0.12 things would work for a while and then just stop working, much the same as with 4.0.14. This whole thing is getting me confused. One other thing I tried was I unplugged the Flirc and removed all instances of it from Device Manager, Rebooted and plugged the Flirc in again. After doing this I was able to Wake the computer a few times before it failed again. I just do not know what else to check as I have gone over everything I can think of. I think I have decided that once I receive the ASUS BT400 this week I am going to perform a Factory Reset of Windows 10 and see if things improve. Sorry for causing any problems for you. Thanks in advance Kevin
Hello Yawor Thanks for the reply. This HTPC was a complete new build in December 2016. Windows 10 Home x64 was installed and is completely up to date and the only other programs installed are Plex Server, Plex Media Player, EasUs ToDo Backup, TeamViewer and of course the Flirc Software (2.3.1). I have made sure there are no leftovers in Device Manager. Also, the USB Root Hub has xHCI after it, I do not know if that is relevant but I thought it best to mention it. Thanks Kevin
This is getting weirder :(. I've upgraded to 4.0.15 and checked on both my computers and it still works properly. Jason has asked this before, but can you test on the same hardware but with a different system? Maybe one of the live usb distros so you don't need to modify your hard drive. I don't know if the sleep will work with live usb though (it should). How long do you have your Win10? Maybe there's some driver conflict caused by something you've installed before. Windows USB drivers can get messy sometimes and potentially non-related things start to misbehave. It's a last resort, but I wonder if system reinstallation (or factory reset in Win10) would help in this situation.
Hello Jason Sorry, I was not clear, since I discovered the issue concerning the Logitech Unifying Adapter I have had it removed from the system. The testing I have done with the 4.0.15 FW has been done without the Unifying Adapter present. Thanks in advance Kevin
Please find attached the desired files. The new Flirc with the "old" config seems to work in that case :) The Flirc gui was closed during the flirc_util error. Maybe it is a MacOs Flirc version issue.
Now, now :) Also, since downgrading from 4.0.15 to 4.0.12 I have been able to Wake the computer successfully each time, however, with 4.0.15 I have been unable to get Wake to work pretty much at all, sorry. Thanks in advance Kevin
Thanks Budwyzer. I agree. It would be very odd for such a device to do that. Which is why I was hoping Dave would confirm he actually had IR remote control of the Fire stick working using it and the Flirc USB. I am used to controlling everything with a Harmony One remote, so this is bugging me. Plus the odd shape of the Fire remote makes it a real PITA to use.
Can you do a test? Clear both old and new Flirc and then record one button on old one and the same on new one. Then save both configs and attach them here. Also clear new Flirc again and load config from old one and then also save it and attach as a third file. As for the flirc_util error, do you have Flirc GUI opened? It should be closed before accessing Flirc with flirc_util.
@yawor Thank you Yawor, I wonder if I made a mistake, but if I enter the command I get an error (v2.3.1, iMac el Capitan): funtypes-iMac:~ funtype$ /Applications/Flirc.app/Contents/Resources/flirc_util keys
dyld: Library not loaded: /usr/local/lib/libhidapi.0.dylib
Referenced from: /Applications/Flirc.app/Contents/Resources/flirc_util
Reason: image not found
Trace/BPT trap: 5@jason Thank You Jasen, I just tried it, first I cleared the configs again, loading the old config and saving it to the new Flirc. Unfortunately still without success.
Hello Jason Sorry about this but since upgrading from 4.0.14 to 4.0.15 I am no longer able to Wake the computer. I downgraded to 4.0.12 and I am able to Wake the computer again. Also, I have ordered a Bluetooth USB Adapter (ASUS BT400) to replace the Logitech Unifying Adapter so I will update you how things go when I receive it, hopefully on Wednesday next week. Thanks in advance Kevin
Hello Jason I tried running the device-log command again, this time without the Logitech Unifying Adapter present and the command worked this time. The results are: C:\Program Files (x86)\Flirc>flirc_util.exe device_log <1>malloc_addblock(49): Heap Block: 0x20001FAC - 0x20002FFF (4k) <3>init_modules(419): Module Load Error: &module = 0x0000EA60 <3>log_output_init(42): no log hw found <3>init_modules(419): Module Load Error: &module = 0x0000EAF0 Late I know but better late than never :) I will also try the 4.0.15 FW and update you. Thanks Kevin
I expect that power is a constant on both legs of the cable. There is no chip in that cable to do any switching, so the "both legs cannot work at the same time" comes into effect if you had two devices sending data to a single host.
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.