Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Nobuddy0816

  1. Afaik the flirc device behaves like a usb keyboard, so the wake up feature is hardware related. With OE installed on a x86 machine, you need to configure the s3 energy saving options in the bios to wake up (and boot) the system, if you put the system into suspend mode via OE.
  2. All guys using XBMC older than 13.1 (including OpenELEC) have to keep in mind, that there is a bug with it, wich can causes the described behaviour with nearly every remote (IR and/or radio controlled). Just a hint.
  3. Ah, ok, now i got it. You just want to use flirc in some kind to analyze the different ir signals for output the data you need to program the app!?
  4. I got that, but was still wondering, for what purpose do you want to use it exacty. I'm using XBMC and have the choice to use flirc (what i actually do) with a remote or can use an android app of my choice to control XBMC over WIFI (e.g. Yatse). Also there are many apps, provided by manufacturers like e.g. Samsung, to control TV and/or HiFi components, which connected via WiFi/ Ethernet to the internet/home network. So beside the customization capabilities, where's the advantage to read out and program ir codes to an app, when already hundreds of apps are available and ready to go? @ Jason: Sure, the haptic feelings of a real remote are none to a slicky touchscreen. Apps are always a supplement to a remote due to it's limitations depending on its purpose (like controlling XBMC).
  5. What do want to use it for? If i'm using a Android device, there are many remote solutions via wifi, so flirc should be obsolete. The only difference is maybe more customization...
  6. If this is still actual: Try to check the energy saving options in the bios. Maybe the usb ports "fall asleep" when the pc/OE is idle. Flirc might do not wake up the ports, but the keyboard (cabled) do!? Just a hint...
  7. Yep, the addon is outdated for Gotham (final) and needs to be modified for full compatibility.
  8. Under which condition do you use the flirc device? Is this behaviour reproducable under any Program, or is it always the same program? Are you using XBMC 13(Gotham)?
  9. But it's still fact, that you will probably face random key repeats using xbmc gotham beta thru rc1. The recently released final isn't available for our pi yet. To check, if your flirc device is faulty, just try another remote around you, learn the basic keys to flirc and see, if the flirc devices behavior is changed (or still repeating the back key). Is it only the back key, which is causing the issue?
  10. No, this is an issue to xbmc itself. Raspbmc has a workaround in its settings, but this do not work for me. You can use the latest stable version (OpenELEC 3.2.4) or Raspbmc with XBMC 12.3. There you will have no problems. I have two pi's running with raspbmc (Gotham RC1) running. The one using the flirc device is running without any issues, even no constantly repeats. The second one is running the same config, but using a keysonic rc remote. Here this nasty issue persists. I'm trying to play with the advancedsettings.xml at the moment. I will post the results ;)
  11. You're using XBMC Gotham beta or RC1? Then this isn't an issue caused by the flirc device! It's a bug within xbmc itself. I'm looking for a solution, but didn't found something yet.
  12. How do you use your flirc device with?
  13. Which XBMC-Version are you using? The Gotham betas and the rc1 have an issue with remotes (ir and RC), which causes randomly nonstop key repeats. This isn't an issue due to the flirc device. I'm searching for a solution at the moment, but didn't found anything yet.
  14. Really strange behaviour. - What kind of mouse/keyboard are you using? - Can you test a different mouse and/or keyboard to check, if this issue persists? - How do you connect the flirc device (direct into usb, expansion cable, usb hub)? - Did you try another usb port (on another internal hub) to force a driver reinstallation? - Did you checked the device on a different computer? Are there similar issues? - Check the system settings w/wo the flirc device plugged in. Are all usb devices recognised correctly? Any yellow triangles?
  15. It's seems that flirc isn't fully compatible to usb3 yet, so for upgrading and programming usb 2.0 is the better choice ;)
  16. Did you tried usb 2.0 ports instead of usb3 if available?
  17. Try as follows: Remove all flirc related content from the system (software and driver), if possible go back (again) to a restore point before the system's first contact with flirc. Disable temporarely any running av-software during the following installation process to ensure a clean and error free installation of the software and especially the driver. Some security software intends to interupt the driver installation and/ or try to put it into sandbox mode or isolates the driver partially etc. So the best way is to disable the av software, install the flirc content and reactivate the av software to normal mode. This behaviour depends on the functionality of the software you use. After (re)installation of the flirc software and drivers plug in the device and wait for the recognition/ driver installation. Now it should work as wanted. I have installed the flirc software and drivers on three different machines with different windows versions (7/8.1 32bit/64 bit) without any hassle. Also there were never any problems with av software (using kaspersky and avast av), except the described behaviour of sandboxing. Nothing malicous found ever, the software is clean. Some basic suggestions for programming the flirc device: - Always program flirc in a "silent" enviroment, keep away any other ir related devices, which might interfere with flirc. - Try to find the optimal distance between flirc and your remote for best responsiveness. Don't point your remote directly to the device. Try an angle of approx 45° - Ensure to give flirc full usb power, plug it directly into an usb port from the mainboard if possible. If you're using hubs, the only active ones with power supply. - Try to not use the "go"-button. Choose your Profile and bind the keys manually.
  18. As long as you learn different ir code to each flirc device, it should work without interfering each other.
  19. You cannot compare the price for a rpi, which is produced in a high count amount, to the flirc-one-man-show ;) And the rpi's price depends on the "thought of education". And finally: compared to a similar mce compliant remote including the needed ir receiver it's quite the better value :D
  20. This depends on the remote managing the different profiles. Mostly, you will have different layouts with each profile due to different devices from different manufacurers. There are some remotes, which left the basic tv controls (vol up and down, prg up and down) untouched while switching to another profile like dvd/bd. This is truly an unusual way to program a remote, but will fulfill your needs getting a single profile to control at least two devices. The second remote is needed to feed the universal remote with different ir codes, seperated from your tv ones to avoid interfering each other. +1, my daughter gets it very quick (she's 10) and often gives my wife a helping hand :D On the bottom line: There will be no way to find the "holy grail" all-in-one solution. You have always to choose between easy handling and complex controlling. I use a silver ATV remote (just 7 buttons) for easy handling my xbmc. I've compensed the lack of buttons with additional mapping on free tv buttons to flirc. So i have two remotes around. For complex controlling xbmc, i use a 7" Android tab with "Yast".
  21. The solution might be quite difficult to realize (without switching a profile on the remote) Every universal remote are using profiles to match the desired device. So they will map all needed buttons on the remote to emulate the original one. On the other hand, most universals have also a learning mode, to copy commands from the original remote to the universal one (just the way flirc learns commands too). So, you will always have the same effect with the original remote to the universal remote, if you using profiles. One option is: Copy the needed commands for your tv from the original remote to the universal one via learning. Then you need to copy all the needed buttons for your xbmc from a different (old) remote, wich is not compatible to your tv. And then you map these different buttons to flirc for using with xbmc. Otherwise you have always to switch between profiles with your universal remote or use a second one beside the original remote from your tv.
  22. You asked before buying, thats the best way to avoid disapointment. For me, first of all flirc is some kind of a replacement for classic wmc remote solutions, with much more flexibility. But you can also use it a way beyond standard pc environment. Nearly any device with an usb port dedicated for control input could respond to flirc. Why not even bd players...?
  23. ok so this is kinda specific android treatment for android devices where flirc is connected to!? Flirc receives the command a remote sends to it (e.g. "a") and flirc passes it through to the android device (like an ouya). The app acts as a "man in the middle" and "translates" the "a" key to "vol up"!?
  24. Hm... in theory yes. The BD-Player needs the capability to be controlled via a usb keyboard. In second you need to know the (keyboard) commands for mapping the flirc. Then you can map the buttons from your pioneer remote to the keyboard commands of your oppo by using the general keyboard profile in the gui. You can test this by plugging a standard usb keyboard into your bd player and check, if it responds to keypresses in any way. If so, flirc should work. You have also to keep in mind, that you have to use unused buttons from your pio remote to avoid unwanted reactions from your av receiver.
  25. Didn't get the point!? What is it good for and how do you use it?
  • Create New...