bladox.com

[Tim]

I'm trying to set up a timer - using timer_start() but I'm getting a strange problem. See log below

33.862 TO ME: d0 11 81 03 02 27 00 82 02 81 82 a4 01 01 a5 03 00 00 a0 90 00
33.878
33.893 FROM ME: 80 14 00 00 0c
33.909 FROM ME: 81 03 02 27 00 82 02 82 81 83 01 32
33.925 **SAT** timer set: index 01

The ME is returning an error code of '32' (Command data not understood) - but I'm getting a value of '1' returned from timer_start(). I would expect an error code of '0' in this case. Is this a known bug? Is there a workaround?

[pz]

Thanks for bug report, didn't know about this issue. Quickest workaround is to check terminal profile if timers are supported. Assuming it's properly reported there.

[Tim]

OK - thanks for the reply. Actually the terminal profile reports that timers are supported so I guess it's a bug in the phone's implementation.
Let's name & shame - it's a Motorola Defy running Android 2.2 - and I've seen the same problem in another Motorola Android phone.
Anyway, thinking about this I guess I can examine the specific Result value in the terminal response (...which I'll find in Buf_A() ??) and look for success values of 00, 01 or 02.

[pz]

Yes, terminal response should be in buf_A().

Could you drop a line to info@bladox to send you a newer kernel hopefully fixing this?