Hi Garvin,
yes, looks a bit like a caching problem. Summing up the experience I gained: it's nice to have this plugin, though it seems to be hard to really get it set up in a decent way, especially when having static pages. For instance, when your main page is not the blog page, I have not found a good way yet to forward the user to the blog page (the mobile theme does not contain the menu buttons). In the config of the plugin you can redirect mobile devices to another host, but that does not help here since the redirect holds for all the pages then (so also the blog page itself).
But even when the mobile user accesses the blog, one crucial feature is missing: the option to turn off the mobile theme, which keeps one trapped into the mobile output. This gives no route back to information which might be on static pages, or information hidden away by the mobile theme.
Also, that the developers themselves use WPTouch now for their site does not add confidence that the development of the plugin will continue. If I would understand more (anything) of how this all works, I would try to improve a bit myself, and maybe I will try, but that is nothing to hope for
Somehow these mobile variants of pages remind a bit of the WAP efforts, which never succeeded. So maybe doing without a mobile version at all is the best choice at the end. At least an option to turn the mobile version off seems to be crucial.
Anyhow, thanks again for your help!
Cheers,
Lars