jason
-
Posts
3,757 -
Joined
-
Last visited
-
Days Won
231
Posts posted by jason
-
-
Thank you so much for the post and the gratitude. I tell everyone that takes the time to give positive feedback, it really makes the hard work worth it.
-
re-run as sudo
Or, you'll need a udev rule, create a file called 51-flirc.rules
put the following in the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
That is a bit extreme, every USB device becomes read/write accessible to all users, but honestly, it's absolutely stupid that you need root privileges to write to a usb device.
-
hmmm... weird.... works again. and again the repeating keys. I thought it had gone, because it worked fine for about 20-30 keypresses (was testing it). And then it went haywire again. Please can Jason help me. The Flirc is useless like this. And without the Flirc, the whole Raspbery pi is useless....
Does this happen on another machine? If you use another remote, does it go away?
Can you post your configuration?
Do the keys only repeat after pressing a remote button?
How quickly are you repeating keys when pressing your remote. This shouldn't be a problem, could need a replacement.
-
Full time Job + Flirc + newborn baby = 0 time :(
I'm forever sorry for the delay, this was absolutely not intentional.
I finally had time to merge this into the branch, add the appropriate settings, and get this into the release candidate fw v1.1.0
The firmware is bundled with the GUI:
You have to enable this feature!! Please read the instructions:
Instructions to give this a try:
1) Download the
2) Launch the GUI, the gui will detect you don't have the latest supported firmware, and automatically upgrade for you
3) Launch the CLI bundled with the GUI and run:
flirc_util noise_canceler enable
Verify! The below output shows me noise canceling is enabled.
flirc_util settings Settings: sleep detection: Disabled noise canceler: Enabled inter-key delay: 6 keys recorded: 0 keys remaining: 169 memory used: 0% No Keys Found
You should not have to re-record buttons. If you do record buttons with this enabled, you will get less spurious noise recorded. (hopefully none).
Provide feedback regarding this issue in here: http://forum.flirc.tv/index.php?/forum/58-v110-rc/
Otherwise, it's very easy for me to loose track of issues and which firmware/gui/cli version they correspond too. I'm going to get better about that as well as tracking known problems, and providing feedback of implementation schedules. -
are you both using a harmony?
-
Shouldn't be happening. Could you do a few things. Could you upload your configuration file to this forum, and could you also try uploading the 1.0 firmware again. It's right here:
We'll get it sorted out.
-
This post will be updated when the plugin matures.
Grab the latest here: https://github.com/flirc/flirc-xbmc-plugin
Sean did an amazing job putting together the official flirc XBMC plugin. You can now program your flirc directly in XBMC with the flirc plugin. There will be support for all the major keys.
fw-1.1.0-beta is supported, however, there are a couple kinks we are working out. The GUI does not let you know you have already recorded a button.
The GUI will look and feel exactly like the desktop application. There will be better support for upgrades in the future.
Linux users need to add a udev rule. Instructions will be added to the project readme soon. I will be working on cleaner ways to get this on your system without manually adding a udev rule.More updates will come, please leave feedback and requests regarding this plugin in this sub-forum.
The plugin works on the following platforms:
Raspberry PI
Linux
Mac
Windows
-
1
-
-
Try bios settings, removing boot from usb support.
-
I got the keys I programmed as "Backspace" and "Escape" to work by using the attached "keyboard.xml" file that someone had posted at the XBMC forums. Well, not perfectly as both keys do backspace but it is good enough. The Flirc controlled remote even works for navigating around the Android OS with the arrow keys and the enter and exit keys. Pretty sweet setup now.
Edit: oh yeah, with the above "keyboard.xml" file the Rii mini keyboard keys (Escape, backspace, and shift) still don't work within XBMC but the Flirc remote does.
Thanks so much for posting this
-
The receiver in flirc is tuned for 38khz, anything really far beyond or below that and it starts to have trouble.455 is a proprietary frequency that beo uses to control their devices.But the beo4 remote is capable of being a universal controller which can still control other standard consumer devices. So just like any other universal controller, you would need to add a `samsung` device.There are people using this remote with flirc.
-
I believe it's the power supply. It's not just the voltage and current capacity that matters, but the quality.
These small little power supplies are called switching power supplies. They turn off and on rapidly charging and discharging an inductor/capacitor.
The cheap ones have a lot of switching noise on what's supposed to be a stable '5 volts'. If you look at the output, you'll see it looks like this:http://t0.gstatic.com/images?q=tbn:ANd9GcSxE9mD2JzLoeLWI0xjBdL_egsW4r_emuF_2y-gFepzWHXY4UCM
At any rate, try using another one. Because it's disconnecting leads me to believe it's definitely a power supply issue.
-
I heard a very strange thing that you have to have usb devices plugged into rpi+openelec when the system boots.
I don't have one to try this on, but that's probably what's going on. Let me know. -
I too see this. works fine on my USB2 but the 3 just will not see it. can test if it works from remote as the config clears on removing at the moment.
all drivers are seen in device manager as if its working. could be a probing issue on the software.
When did you download the GUI? I posted a new version recently that should have updated drivers and better windows 8 support. Let me know if you can give that a shot.
-
should work, if it doesn't, report it.
= )
-
Windows it's in the folder: Program Files \ Flirc\ cli \
Linux: just type in all lowercase: flirc
Mac: not shipping it.
All of them you can get in the beta section of this forums. Including the raspberry pi version. -
windows 8 fix updated, let me know.
-
glad it's up and running. Thanks Chris.
-
okay, just another day or so, I'm going to release a gui update too. I'm almost there. I'll point you to the release forum.
-
Did a little more testing in Notepad. It's sending the Enter key on average once per second. Some are slower, but then there will be a burst of several key presses. The computer is not very usable like this, I have to unplug the flirc to get anything done.
Don't worry, I'm already convinced everyone's issues are real. This isn't a hardware problem, I test every one I sell, so it's definitely environmental and firmware inhibited. I'll post a fix tomorrow. I'm not going to leave you guys hanging.
-
I'm going to post an update this weekend to address this. Keep a close eye on the beta forum. I'm going to put in a bit of noise detection, this feature will have to be enabled, (not on by default).
Various updates are coming along with a new beta GUI.
Not to worry guys, I've had a proposed fix in for a while, I just have to publish it.-
1
-
-
Hehe, being in the XBMC Team has advantages. Thanks a lot for your sponsorship, BTW :)
Besides the dev kits, they are currently shipping to the kickstarter backers. The non-kickstarter pre-orders will only be fulfilled starting June, Ithink.
My sincere pleasure and the least I can do, XBMC is the reason why I started flirc. I only wish I had more time to poor into it, with a full time job and a new born baby, I'm working literally non-stop.
Ah, makes sense. I'll see if I can get android on the raspberry pi up and running to see if the same thing happens. Although, it could be the USB chip in there, which is probably just the phy on the Nvidia tegra, so really I should just try and find a development kit at work. ;)
-
Yes, thanks for the update! That's great it's up and running. Very strange, I would have never guessed that setting changes from OS to OS. How did everyone get an Ouya? I was going to try this but it's still on pre-order.
-
so for others looking at this, this is built into the new cli, will be built into the GUI soon too
-
1
-
-
It works quite well for me on an Ouya + XBMC.
Only bothering thing is that it seems there is some kind of undesired auto-repeat.
Seems ok under windows, but under Android, keys auto-repeat, and with a near zero delay.
Anyone else with this issue? Or, better, with a solution? ;)
Do you have this auto-repeat issue when you plug the device into another system? May be an excuse for me to purchase an Ouya. Let me know. I guess this looks like an Android problem, unless I'm mistaken.
Flir app doesn't works on Windows 8 or Mountain Lion(10.8.2)
in Firmware Bugs
Posted
I'll clean up the downloads page. The latest, or 0.96 windows version is the same exact version, with a different installer for the signed drivers.
Flirc.exe [ 0.96 ]
Or, you can install the beta, which is very stable. Both work on windows 8.