Hallo Klaus,
Thanks a lot for looking so deep into it. Each of your findings is an expert advice.
My apologies, I should have mentionend that I threw this in at an early stage
because it is going to be a paid application once completed.
Currently, it is designed on a 1280x800x1.0 template only.
Your Asus tablet is a fine choice as it scales x1.5 (1920/1280). That's what I call 'to the standard'.
Device paused: I will see to it by shifting certain code out of Activity_Resume.
Default city: at this stage it defaults to the coordinates as set in settings.
Click on Local: as above
World button: sorry, "World" is misleading. I changed it to "Seek", perhaps better "Get Weather".
City list: the app seeks for cities in a radius of 1 degree around selected center coords. If no
city is found, it will expand the radius to 3, 5, 10, 20, 30, up to 40 (the latter for Antartica and the North Pole).
The search is therefore not restricted to countries. It is a borderless app

Anyway, I will restructure the database so as, for instance, a default city can be set with less error-prone code.
Downloading the APK: browsers react differently on file extentions. Please right-click on the link and select "Save link as..."
This should work for most modern browsers.
Autoscaling: After exchanging thoughts with NDude today, I checked your unparalleled tutorial and code samples.
Erel and you spent so much time and effort in finding solutions and I believe, there is no simpler means right now.
Yet, all this time required for scaling is too much for me. At the end of the day, one would need a real device to be
absolutely sure. My largest app in the market is composed of over 30 activities. If I wanted to scale them for all
screens, scales, plus aspect ratios out there, I'd probably run mad. For the time being, I explicitly specify for which
screens an application is designed for and disencourage a purchase for other devices.
My best regards
Robert