Chris!
-
Posts
1,300 -
Joined
-
Last visited
-
Days Won
50
Posts posted by Chris!
-
-
The problem lies in that you can get into the bios menu with flirc plugged in. If you could then it would show up in the boot menu (
seconds in).Do you have a USB memory stick, does that cause booting up to fail. It might be worth emailing ZOTAC to see if they have any tidbits of information
I've never seen anything thing like the issue you're having as bios is always accessible - it's just one of those things like gravity always keeping you on the ground.
-
I've highlighted the thread to Jason.
@zaphodFlirc: Sorry for getting mixed up with the power supply issue - I should read things more carefully :)
-
Wow this really is a puzzler. I've just re-watched your videos and it really does mess things up - it doesn't compain that there is no OS on Flirc, it just sits there.
Screenshot of ERROR msg:
It says "Stopping remote control daemon(s): LIRC (I guess this should be Flirc ? or its and process or something ?
Shouldn't be as Flirc doesn't use LIRC. All that is on the device itself - it just turns up as a USB keyboard.
One thing I did perhaps notice (or couldn't see correctly) - the initial bootloader part (zotac screen) is really quick.
How did you get into the BIOS settings before?
When do you press the key combo for the BIOS screen, when the zotac boot image is shown?
-
Hmm. Driver issues... I don't have an informed opinion on these (I don't have access to a windows machine and sometimes it seems to depend on the motherboard)
I can program the arrows and enter and use them in explorer but they quit after a random set of time. Sometimes it's 30 seconds sometimes its 5 minutes.
The flirc GUI program isn't running in the background?
I tried programming the device on an old Windows Xp Netbook. I would state that I am having "success" with that.
When you program using the netbook, what happens when you take the flirc out and put it into the windows 7 computer?
Does Arrows and enter quit after a random set of time? (like they did when you programmed it on the windows 7 computer)
I hope we can get this little guy working on my main rig
We definitely want this too :D
Do both Flircs exhibit this behaviour or is it just one?
-
Could do but we'll keep it around just in case :)
(We have top men working on it right now.
who
Top. Men.)
-
ALSO!
Video from all menues in my bios:
I replied to this video on youtube
-
Well, that's not the source of my problems. I'm running a full desktop with Windows. It's most likely a firmware issue with Flirc in combination with Harmony.
Oh yes, sorry I meant to reply to zaphodFlirc. I know Jason has some new firmware coming soon to address some issues, it might have a fix in it for your issue. Hopefully this will be soon or Jason will reply to this thread soon
-
Oh no... they should be as simple as my video. Something must be up with yours - I can understand the "office-space" situation.
We'll make sure we get some working ones to you (they are tested before they leave us - but rarely go bad not long after). In the meantime could you try doing the following steps - then we'll know if they're definitely broken:
1) Open Flirc GUI for windows/mac/linux: http://www.flirc.tv/downloads/
2) Plug in Flirc (may start behaving erratically still but try to persevere)
3) Grab version 1.0 of the flirc firmware here: http://blog.flirc.tv/library-version-history/
4) Load firmware onto flirc using "upgrade firmware" in the Flirc GUI
5) Clear the configuration (file --> clear configuration)
6) Close the Software and take Flirc out of the machine
7) Put Flirc back in the machine and open the software and try and program arrow up, arrow down, arrow left and arrow right. Then switch to windows file explorer and click on an object once and try and move it about using your remote buttons assigned to arrow up etc (like you would if you were using a keyboard).
If that doesn't work and it's still misbehaving, could up share your configuration with us using the forum (file ---> save configuration).
Also, what remote control are you using?
-
The only change from before the problems to current (i.e. with the problems) is a new power supply for the raspberry pi that the Flirc is connected to.
Sounds like the culprit. Not all power supplies are created the same.
Jason's explanation:
The power supply amps wont really be the issue, it's the quality. The cheap ones have a lot of noise but the chargers in the phone can compensate. Since there is no filtering on the pi (USB runs at 5.0 Volts), then anything crappy on the main shows up on USB. However, that being said, it will still show up in the OS. It wont perform well.
Here are some other threads that have reported power-supply related raspberry pi problems:
-
Thanks Chris. As a comparison, i also use youtube.com/tv which is youtube's couch mode. Flirc works fine with that.
The plot thickens...
-
Sorry for my late reply but I thought i'd give it a go too.
I get exactly the same thing (using beta firmware 1.1). Although if you bring up the control display before pressing flirc stuff then it responds better but is still really unusable.
I also tried getting a USB keyboard and attaching it to my mac - that behaved fine.
It's really strange that Flirc is the only one acting weird.
I'll move this thread to bugs forum so Jason can have a look at it at some point. I'm perplexed
-
Oh no! Let's sort this out
What remote are you using to control flirc?
-
Ah yes, just checked. I've reported it as an issue (you are using the beta firmware aren't you?):
The exit button on harmony remotes should be mapped to Esc not backspace. We'll get it sorted for the firmware going stable :)
-
Yep, you'll want to make the sata drive the primary (or master) boot drive. Then all other devices mounted should be the 2nd, 3rd etc option.
Take a picture of the bios screen if you're still struggling, post it in this thread and we'll help :)
-
I just need to get my head around the different layers of abstraction and how to match them up.
Let us know how you get on. It's usually better to not think too hard as Flirc is meant to be simple :)
-
Hi Cindy, welcome to the forums,
You are correct, there is nowhere that tells you what is mapped to what button.
Though as Flirc sends keyboard pressed to the computer you can open a word processing app - or notepad - and press buttons on the remote and it will display what flirc is sending (also accessibility keyboards in various OSs do a great job)
I've pointed out a few of my issues with the harmony setting here:
Please feel free to add to it if you find anything else.
Pleasant regards :)
-
Yup, looks like it.
I'll keep an eye on the new beta's so it doesn't creep it's way into the next release
Thanks for reporting, How are you find Flirc in general though?
-
This... I did not know about.
I thought the plan was to implement API's that the XBMC addon could talk to but i'm not sure.
-
Can someone please help me by getting the fw_repeat.bin file please
Old Beta's are depreciated when new ones come out. Check out here:
The above two points are the only cons but with the flirc, I feel there are too many if's and buts to make it work perfectly.
For example.
Pros of Flirc.
Infra Red so batteries wont die.
You can use your universal remote instead of an alternate PS3 remote.
Cons.
Flaky in a sense, flirc will learn the remote but not play back well.
Constant additional key presses.
Has an external object sticking out. If you use a bluletooth keyboard and mouse then the ps3blulmote is a total clean solution vs a flirc.
There's a thread I started so I could direct people interested in Flirc to it to see if it would be suitable for them... like an amazon review. If you feel like formatting your post as described and adding it that would be super :)
Pleasant regards
-
EDIT: Easier method/ way not to mess up your default keyboard layout.
So on android you can create different key layouts for individual keyboards as long as the file names indicate the device (see attached)
I created a key layout for flirc and restored my stock generic one so that other keyboards arent affected.
Instructions
Step 1: root/ install superuser
Step 2: move attached file (unzipped of course) to /system/usr/keylayout/
Step 3: on Flirc software program the following buttons for android commands ie: program the buttons on your remote to the keys which correspond to the following android commands
esc: back
home: home
F2: MENU
F3: play/pause
F4: play/pause
F5: Stop
F6: rewind
F7: previous track
F8: next track
F9: fast forward
Done
all other keys are default, of course you can edit the key list to whatever you want...
Interesting stuff. I'll have to check if we can distribute keymaps through the play store as i'm sure a lot of users won't want to root (and many will have no problem).
Really should get myself an android media box or something of android that I can plug a flirc into
-
This is awesome - glad someone found the time to post a great guide.
I'll be directing people here for android related things :)
this is off-topic I hate the ouya launcher but installed nova launcher and open launcher for google tv both of which work really well
I saw a video of the Ouya launcher... seemed an acquired taste.
-
Awesome stuff :)
-
Are you using the harmony settings:
Manufacturer: Flirc
Device: XBMC
This is beta firmware and is still a bit rough around the edges. I still recommend this device for now: http://forum.flirc.tv/index.php?/topic/22-harmony-remotes/
Then you assign any function in the harmony software to a button (doesn't matter what) then assign that button using the flirc software to win key + 1 ()
-
Like this?
Using this method you can start XBMC from windows.
You could then use the XBMC shutdown menu to close XBMC and return to the desktop
Does this answer you question?
- 1
Help Please - Erratic Behavior
in Remote Controls
Posted
I agree, this does seem like a driver issue. We've had contracts outside of Flirc to help try and fix this but we are going to have to keep looking into it.
For more information could you post the spec of the Windows 7 64bit machine. e.g. motherboard.
Having more information to find a common element in the machines it does work in and the ones it doesn't work in would likely help a lot.
Cheers