Jump to content
Flirc Forums

Nobuddy0816

Members
  • Content Count

    100
  • Joined

  • Last visited

  • Days Won

    2

Nobuddy0816 last won the day on May 4 2014

Nobuddy0816 had the most liked content!

Community Reputation

6 Neutral

About Nobuddy0816

  • Rank
    Advanced Flirc-er

Profile Information

  • Gender
    Male
  • Location
    Germany
  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 ;)
×
×
  • Create New...