@Piru
It is not tough, at all.
@gurthuk
Google mobile aliases are mess already

Use your e.g. 3.X native browser Try
m.google.com or
mobile.google.com and switch to mobile device.
What you get... Google sees Amiga UserAgent and considers it unknown (no wonder). Note that if you were using IE or Firefox or Safari or else, Google would know it and serve you a normal webpage.
But all unknown UAs are considered as very old or odd cellphones. Old cellphones used WML instead of xHTML so what you get is a WML document, not viewable in any www browser since it's just some XML.
Say, I worked for two years in a mobile industry, enabling new phones in mCMS so that any phone is served properly. All you gotta do is forge your UserAgent. It's easy to pick on the web (the string) and if you introduce yourself as a decent WindowsMobile device (e.g. QVGA, VGA maybe), you will be served pure xhtml, formatted to 240 x 320 resolution so fine for Amigas.
So I think it is about to catch HTTP request on a system level and change it, that's all. I am eager about the result...