Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by yawor

  1. You just need to bind mount home dir to directory under chroot root: mkdir -p chroot_root/home/user mount -o bind /home/user chroot_root/home/user or just: mount -o bind /home chroot_root/home if you want whole home mounted. Please remember to umount all the binds after the work with chroot is finished. For example, if you will try to delete whole chroot dir with the mounts still on you will also delete content from source directories!!! You could also write a script that bind mounts everything that's needed, calls chroot and then umounts all binds mounted earlier. Umounts will wait for chroot to exit. I think that scrhoot actually does something like that in automated way so I don't see why wouldn't it work with 12.04 root.
  2. Hi, The distance during the programming was probably too small and the signal is too strong and causes overdrive of the IR receiver. The minimal distance of 1 meter is more of a rough guess than a specific value. You will get better results moving much further away from the Flirc during programming. You can also point the remote at the ceiling instead of Flirc directly so the signal received by the Flirc will be the one bounced off the ceiling.
  3. yawor

    hi there and thx!

    You can use S4 which is a "save to disk" state (hibernation in Windows terms). It saves current memory into a file and shuts down the power to most of the components but still allows to wake the system using external events like keyboard (or Flirc). Actually S5 should also allow the wake to work (at least according to MSDN article about Windows/ACPI power states) but maybe it depends on the mother board itself.
  4. All you need to program Flirc is Flirc software and hardware on the same machine :). And yes, you are reading it correctly. You can program Flirc on one machine and then just plug it in on another and it will work. Flirc software is only needed for programming. It's not used in normal day to day operation. There is a nice solution for building on multiple distros but it is based on virtualization. It is called Vagrand. It supports multiple virtualization apps but Virtualbox is most popular. You create a config file (contains name of base system image for example) and you can add a bootstrap file which is called on first boot to install all that is needed for the task. After that you just call vagrant start in the directory where the config file is and it clones the base system image, starts the machine in headless mode (so no window with virtualized OS console) and if this is a first boot it runs bootstrap script. After that you have an SSH access to the machine (or multiple machines at the same time). When you end your work you just need to shutdown, suspend or even delete machines (if you delete then it will be created again if you want to start it). On the other hand you should not have any problems with creating chrooted 12.04 environment using debootstrap. ---edit--- I've tested debootstraping Ubuntu 12.04 (precise) on Ubuntu 14.04: mkdir precise_root debootstrap precise precise_root mount -o bind /dev precise_root/dev mount -o bind /proc precise_root/dev chroot precise_root /bin/bash I've added /bin/bash to chroot because I have zsh on the machine as a default shell.
  5. yawor

    hi there and thx!

    I've also been planning on buying the Harmony remote myself, but in the end I've bought One-For-All URC-6440. There is a community forum dedicated to EUI/OFA remotes which also hosts a community developed application called RemoteMaster which can program those remotes. We've been working hard to bring support for URC-6440 and other from SimpleSet series. There is even a firmware extension for 6440 (installed very easily in this model) that brings a lot of additional functionality making this remote the best there is for the price, which is much lower than for cheapest Harmony remote.
  6. Jason, Ubuntu 12.04 is an LTS and it's not even near its EOL. Every Ubuntu LTS (starting with 12.04) has a 5 year support, so 12.04 will still be supported for 2 years and a few months. I know that it is already outdated, but for sure it is still alive :). Of course the system being still supported doesn't mean that you need to still support it yourself - especially that you are doing it all alone and the software is only needed for actual programming, which can always be done on another machine. To support new distros and still support 12.04 you would actually need to build multiple versions and discern them in your apt repository based on version name. BTW I don't use Ubuntu on desktop any more because of it ageing very fast for each particular version. I'm using Arch Linux at work and at home for at least 2 or 3 years now with much success (rolling release distribution for the win :)) and I haven't thought even once of returning to Ubuntu.
  7. I don't know how hard it would be for Jason to implement this, but you need to remember that Flirc is a generic receiver that accepts almost any modulated IR signal, so I don't know if it is possible to just do an exception for a particular type of remote. Flirc basically takes the signal it receives and compresses it to a 4-byte irreversible hash. It would need to recognize the signal as an Apple Remote one and treat it differently. Anyway Jason is the only person that can tell if this is possible or not. On the other hand, unless you either have tens of those remotes or you frequently change the button mappings I don't see a problem of recording them all. How many buttons does it have? I think it's around 6 or 7. Flirc has a capacity of something about 170 keys so it is possible to record around 24 of those remotes.
  8. Based on the Windows key in the upper right corner I'm guessing that this is an MCE remote. MCE remotes are using RC6 IR protocol which uses different signal on each consecutive key press. There are at least 2 different signals for each key (sometimes there are even more). Flirc can't automatically figure out what are the other codes for the same key so you need to program it to recognize them. Select a key you want to program into Flirc and press it in the GUI and then press the button on the remote. Then repeat the procedure for the same key until you get an error that the button is already recorded.
  9. You are probably using RC build from the forum which has this bug. Please download officialy released 1.3.0 (firmware 3.3) version from the main page http://flirc.tv/downloads_windows/
  10. The USB connector on mine is also slightly bent so don't worry. Also the status command shows this exact message for me too - I think only Jason knows why :). I'm just helping on the forum so I don't know what return path/method you should take. I think you could try writing to Jason directly (via PM or E-mail - address is on his profile page) or wait until he responds here.
  11. If LG Google TV doesn't support universal remote mode with MR400Q then I don't think you can do anything for this remote to work with Flirc. Also I think that LG is using some proprietary Bluetooth profile/protocol for its Magic remotes so there is probably no chance to use the remote with Bluetooth dongles unless someone write a driver for it (I couldn't find any).
  12. Try forcing the firmware upgrade again. It is in Advanced options in File menu. After that format it and try recording again. If this doesn't help then there is probably something wrong with the Flirc itself.
  13. OK so you start the GUI, select one of the controllers from the Controllers menu (or use current one) and click on a button you want to record a remote button for. GUI shows a message "Press the button to be paired with 'xxxx'" and nothing happens when you press any button of the remote, correct? What remotes have you tried to use? Also try to keep the distance between remote and Flirc because it is really sensitive and the IR signal can be too strong if you point it directly at Flirc from short distance. I think the recommended minimum distance is 3 feet (1 meter) or you can point the remote at the ceiling and let the signal bounce of it.
  14. Does the Flirc app show the firmware version? It should be in the lower left corner of the app.
  15. Hi, First of all Flirc doesn't support key sequences. But I also see a problem with your approach. I don't think that you could do this even if Flirc supported sequences. Flirc is sending HID key codes compatible with HID keyboard standards. You can't just send any arbitrary data. So unless you are actually able to execute functions you want using standard keyboard you won't be able to do this using Flirc. I think that you can do everything with keyboard what you can do with a standard remote is because TV's firmware supports a keymap which maps keyboard keys to TV functions. If there are no special/factory functions included in the keymap then you can't execute them using HID keyboard/Flirc.
  16. Hi, EDIT: I did some additional research and it seems that MR400Q is distributed with LG Google TV models - not the classic Smart TV ones. If you have a Google TV model then it probably won't work the way I've described. I don't know anything about LG Google TV models so I don't even know if LG implemented the universal remote function in it or not. I have MR400 model, but I think that besides full keyboard on the back of MR400Q model both models work in the same way. The LG Magic remotes work by connecting to TV using Bluetooth. All commands except power button (which is sent using IR diode in the remote) are sent over Bluetooth. Flirc can only receive IR signals. Fortunately LG has added an ability to their TVs that allows to control other devices using Magic remotes (and only Magic, standard remotes don't have this ability). The way LG implemented this function is really smart. The remote itself doesn't know anything about other devices. It is all implemented in the TV's firmware. When you are in the universal remote mode and press some button the command is still sent using Bluetooth to the TV. The TV knows that it is in universal remote mode and knows what device is selected and what IR code should be sent. It sends this info back into the Magic remote using Bluetooth and the remote blasts the IR signal using its own IR diode. You need to set it up using TV input source menu. I have all the menus in my language so I don't know how exactly those menus are called in English so you need to try and guess what I mean if it's not exact name of the menu or function. 1. Go into Input source selection menu. 2. Press yellow button: "Universal remote setup". 3. Press "Start" on the screen and you should be presented with device type selection (there may be other screens between, just skip them). (below points are based on my research - I've spent hours finding a device which would allow me to use as much buttons as the remote allows - this is based on the MR400 model which doesn't have many buttons to begin with - you can use this config if you don't have home cinema or soundbar or some other device from LG besides TV) 4. Select Home Cinema. 5. Select Input on which you have your computer with Flirc connected (like HDMI1 etc). 6. Select LG. 7. Select Remote model 1. 8. Finish the setup. If you have some other LG hardware (like soundbar or some other speaker system or home cinema) then you probably need to select other device type or manufacturer. I didn't have much success with other device types than Home cinema so my best bet is to still use Home cinema and just select different manufacturer or remote model. I actually have LG Soundbar but fortunately the keys I have on the Magic remote didn't interfere with Soundbar much. The Magic remote will automatically switch modes depending on which input is your TV. When it's on inputs other than the one you have your computer on it will act like a normal TV remote. But when you switch to the input you configured the universal remote on then it will start sending IR signals for some keys (depending on device selected during setup). In addition to physical buttons on the remote you also have an on screen remote where you can press additional buttons not available on the remote itself. Because the way this whole function works (I've described it in the beginning of this post) by pressing the button on on screen remote the remote still sends proper IR signal. Now there are some restrictions with this mode: - For universal remote mode to be active the TV must be turned on and correct input must be selected. - Physical power button on the remote always sends the power on/off command to the TV itself - if you want to send a power on/off command to the Flirc then you need to use on screen remote when in universal remote mode. The TV also gives you the ability to send Power On command when you switch to the input you have your remote configured on and there is no signal. The dialog will pop up with Power On button on it. When you press it, the remote will send proper IR power on signal. - Some keys are always mapped to the TV itself and you can't use them with other devices. On my MR400 those are buttons are: Smart, 3D, [1][2][3]/Q.MENU (this button activates on screen remote), Mute and Volume buttons. Those are always invoking actions directly on the TV. Of course MR400Q has more buttons so I can't tell you how it will behave. - The scroll doesn't work in universal remote mode - at least I couldn't find a device which maps it somehow. - The gesture control does nothing for the universal remote. When you activate gesture control the cursor on the TV appears and you are back in TV remote mode - it goes back to universal remote mode when the cursor disappears. I don't know how will the keyboard part of the remote behave but I suspect that it won't work in universal remote mode or it will invoke functions directly in the TV. If you have some additional questions then don't hesitate to ask. I'll try to answer then the best I can.
  17. Hi, It's a well known problem with MCE remotes. Read this thread, there's a solution: http://forum.flirc.tv/index.php?/topic/884-disappointed-in-performance-of-my-new-flirc/?hl=xbox360#entry5839
  18. Can you take a picture of F8 and F9 keys if they also have a secondary function printed on them?
  19. Do the other media keys (like play, pause, ff etc) work for you? Is there a second set of symbols on the F1-F12 keys (possibly in another color) on your keyboard that can be accessed using the Fn key? Keyboards with Fn key usually have those. If yes then can you describe the symbols on the F8 and F9 keys? Or maybe make a photo? In my opinion the keyboard is sending some other media (or consumer) keys when pressing those keys with Fn. Maybe the symbols (if there are any) will point which keys they are. If there are no secondary symbols on F1-F12 keys then you need to do some work on your own to find out what code needs to be sent. You can use the same technique I've described recently for finding keys for Android TV device. Read this thread just don't worry about Android stuff. You need to use the method with recording consecutive key codes for each remote button and then test it on the device.
  20. Have you already tried media keys in Flirc GUI? Select Media keys in Controllers menu.
  21. Hi. Why would you do that? Do you want to simulate some function from your hardware keyboard where you have Fn key to modify function key functions? That won't work. The Fn key is probably not even a system-visible modifier. It probably changes mode in hardware keyboard controller so when you press F4 key with Fn then the controller sends different data to the system.
  22. Have you already tried plugging Flirc to another USB port? It sometimes helps when the problem is driver based. Are you maybe using USB3.0? If yes try plugging into USB2.0.
  23. OK it seems that it's not flashed correctly. Close the GUI and open it up again when the Flirc is already connected. Does it ask you if you want to upgrade the firmware? If not try again using "Force firmware upgrade" in advanced options. Do you have access to another computer to try firmware upgrade on it?
  24. Hi, Can you please post what version of GUI and firmware do you have? The firmware version should be reported in the GUI.
  25. Just remember that the thread I've mentioned is not for reporting bugs but rather to let us know how can we make the documentation better. Reporting a bug there won't help with documentation :). You should report bugs in the Bugs forum (or Development forum if it's in beta firmware/software).
  • Create New...