Thanks for the remark. Alas chosing modem is not like writing a letter to Santa Claus, we're happy when we find one modem that meets like 90% of our requirements. STK is waaaay down on the feature requirement list. (with Option GTM601 and Option GTM801 we found even two modems that are pretty 'nice' and drop-in replacement of each other, just one is 3G, the other 4G. The GTM609 even adds CDMA to the set of features!)

I don't know of any modem module that supports STK. GTA02 calypso modem didn't either. The explanation is simple: STK defines mandatory full control over display and keyboard, e.g for bank TAN/PIN generator that can't get attacked by keyloggers etc. With a modem+AP design this is impossible to implement and guarantee on an open platform.
Does android support STK? If yes: how do they do that?

Anyway check the Option modem datasheets I linked to in previous post (and in this post), it seems we'll use those modems and that defines what they support. The rest is AP/userland/community then. USAT seems well feasible when the modem supports it, though I recall our cracks at OM boggled from STK even, back when. Luckily calypso didn't allow it anyway ;-)

Generally speaking our modems will not support the ISI interface that Nokia N900 BB5 modem used, which is a PITA for compatibility to Nokia Dialer *) etc, but a grace for projects like the ones linked in your next post. The Option modules have full free docs of their interface afaik.

/jOERG

*) nevertheless I hope we can implement some sort of comatibility layer or interface lib to expose modem functions to system via the "usual" libisi API