Audio clicking, and left wing switch non-functional
Up to General discussion
Got my droid, and some things work, some things don't.
I have a link between fux and tux. Using tuxgi I can flash the eyes, move flippers, etc. I can play local wave files, and they sound fine.
However, if I play an external wave file, or use the tts program, all I hear is some clicking. Another article suggested weak batteries, but I am using the AC power, and it doesn't help. I've also tried putting tux and fux right next to each other, and 6 feet apart - the clicking doesn't change. BTW, when using tts, the mouth opens, then I hear the clicks, then the mouth closes. So much of the communications is ok, but the audio is not.
One other problem - if I push on the right wing, the eyes blink, and the status window shows the button press. However, if I press the left wing, I can hear the microswitch click, but the eyes do not blink, and the status doesn't show a button press. This may just be a loose wire, but I have not investigated yet.
Should I return this droid for replacement?
The clicking problem seems to me like the audio is not transferred properly, or, the circuit inside Tux doesn't process the sound properly.
I read that the line-in on Tux is more or less directly connected to the speaker (with only the amplifier in between). Can you connect some audio output to the line in? If you hear the sound properly, then it would have to be the firmware, some circuits, the wireless link or maybe fux, but at least the speaker and amplifier would be working.
Seeing that non-audio commands to Tux do work, I bet the wireless link is okay too.
So that would narrow it down to the audio-processing part, which may be either hardware or firmware inside Tux, assuming the line-in test worked ok.
Then again, I could be totally wrong..)
That one I have no idea what it is.FYI, I noticed clicking on my Tux, and realized that they were window open / close events on Fedora Core 9 Beta. Doesn't sound like this is the source of your clicking, but it is clicking none the less.
I am also having the same problem with Tux's right wing (left when you look at it).
Running the tuxd in debug mode, I find that if I push down and hold it, I get:
debug: right flipper pushed
debug: right flipper released
where as if I hold down any other button, I get:
debug: head button pressed
only.
I also noticed that I can press left and head buttons as fast as I want and they register. The right wing seems to be "challenged". There is a word that correctly describes the behavior, but it now has a bad connotation.
-T
I didn't get much trouble with the wings switches myself, more with the head button that is sometimes hard to keep pressed but that gets better after some usage. The wing mechanism is a bit tricky and we've seen some problems on production that it was hard to trigger the switch, but if you can hear the click, it always worked fine for me. I just hope it's not a problem of firmware. You go that from the beginning?