The value o A-V: is pretty close to zero which is good. But this is just a snapshot of the entire movie. Is this pretty much the case for the entire movie? If that is the case, it should have pretty good A-V sync. There are some dropped frames but that shouldn\'t be too bad. If your A-V: is pretty close to zero all the time during playback, then the problem might be the audio stream is ahead or behind the video stream during encode. If that is the case a -delay option should fix the problem.
Experiment with mplayer playback on the encoded video file first. If the audio is ahead of the video, use a delay with a negative number. For example, to delay the audio by 200 ms, use -delay -.2 (mplayer values are entered in seconds). Once you have figured out this magic number, use that on your encode script. Like I said, I use 200 ms and it works pretty well for me.
Don\'t expect perfect sync all the time though as mplayer is always struggling to keep the A-V sync and some frames just are harder to decode than others. The A-V: value will not always be close to zero but it should be pretty close. If you fast forward or rewind, you will see the A-V: value jump up and then gradually go down to near zero.
If that still does not fix your problem, try experimenting with lower bitrates and resolutions. The zaurus 5500 I think has a 200 Mhz processor whereas the 5600 (which I have) has a 400 Mhz one. You however have the benefit of more memory.
If you still have version 1.0 of the createogm script, fix the AV_DELAY variable in ogmmerge by adding the $ in front of it.
