Android 2.1, right? I got a couple of crash reports from 2.1 indicating I'm using an API function that was added in 2.2 - I'll add a workaround to avoid those functions
Thanks for your continued work on making this awesome connected timepiece better all the time!
Currently the weather system is an either/or between google or wunderground - if you have the google weather provider suggested it uses the google APIs for geolocation and weather, if you select wunderground it uses their APIs (and requires the api key)
If you have wunderground selected, then select the "Update weather" option, does the current observation get updated? If so it sounds like the update timer isn't firing for some reason.
(You haven't turned on the battery level logging option, have you? That's known to interfere with the weather update, due to the way Android doesn't let you have multiple independent timers running)
The calendar widget is a bit WIP still, and really needs some configuration options, to define how far it looks ahead, which calendars it looks at, and so on. The number is always today's date, but it could be configured to show the date of the next appointment instead, if that makes sense.
Ahh cool - so was it just an issue with the combination of weather settings/geolocation you'd enabled? That stuff could do with a bit of tidying to make it more intuitive.