Oz3.5.2 And 6000l Curiosities

[vputz]

Quick check to see if what I'm seeing is an OZ fault or just some "feature" of OZ on the 6000L.

I've read in other threads about the occasional weird lines that show up.  That's fine, no worries there.

"Keyboard does not use FN", as I've seen in other threads --well, it does, but it's press-and-release FN, your next keypress will be "FN-ized".  This is at least usable, but typing numbers is painful (fn-1-fn-2-fn-3-fn-4 instead of just holding down fn and pression "1234").  Worse, I seem to be unable to type control characters, which makes many console programs problematic.  Is there any way to get control characters on the 6000L OZ?

Opie-recorder records a Hideous Screeching.  I'd like to just use the built-in microphone, but it doesn't seem to work.

XMame off the feed gives me the alarming message that "error: compiled byte ordering doesn't match machine byte ordering".  Will I need to compile XMame myself?

Scummvm from the feed looks for libivorbisdec0 and wants a version that's not in the feed.  Bug or feature?  I can try compiling via OE.

Other than that--fantastic OS, great device.  But it would be nice if I could make a bit more headway.

-->VPutz

[chapster]

The following could be GPE specific I guess;

I've found that the function key can be held down, but is sticky as well, so FN + Q or FN, Q both give a 1.

As for the control characters, try either the calendar or contacts buttons in conjunction with the key of your choice so, the button with the little dude on it pressed in conjunction with 'd' will send EOF.

HTH

[vputz]

The following could be GPE specific I guess

I think it is.  The FN key doesn't work for me in Opie the way it's working for you in GPE, nor do the calendar/addressbook help with control characters.

BUT...

I did discover something interesting.  I had remarked that holding down the buttons was unrecognized (for example, if I pressed the contacts button or held it down, I was getting the response as if I had pressed it.  Correct behaviour should recognize both as different events).  BUT!  If I hold down (for example) the calendar button for a while and press a DIFFERENT button (like the wheel button or the dot button on the 6k), it sends the "held down" event.

Weeird.

-->VPutz

[vputz]

OK, I think the FN key business is Opie-specific.  If I ask Opie to go to a different terminal like terminal 1 (text only) then the keys DO work as you describe (FN key works normally, calendar key works as CTRL).

So now I just have to figure out how to work around Opie, apparently.  Eventually I may switch to GPE, but the power problems that I'm hearing don't encourage me.

-->VPutz

[vputz]

OK, working with the new version of OpenEmbedded.  I can't compile ScummVM at all, since it relies on qte-for-opie-2.3.9-snapshot-20041221 (same reason I can't compile xmame), which can't be patched, apparently.  And I can't build my missing libvorbisidec because it doesn't exist in the OE feed.  The info on libvorbisidec1 indicate that it's the tremor library, but I can't build tremor since bitbake gives me "svn: Syntax error in revision argument 'svn'".

Hurm.

Well, I'll keep trying, I guess.  Not sure what I'm missing yet.

-->VPutz

[chapster]

Good to hear success with the CTRL keys - difficult to manage without.

As for GPE and the power problems - you are right to be put off. It's pretty unuseable I think. You can't suspend it - you just have to wait for it to time out. And when it's suspended, you can't get it
back without a bunch of resets - at least that's what I find. The only saving grace is that when on external power, it never suspends so the problem doesn't arise. Not very portable though ;-)

I've been concentrating on getting my WiFi working - which it is now, with WEP et al. Now I'll stray into
the area of APMD and suspend/resume.

[Mickeyl]

FYI: I upgraded qte in OE to a more current snap.