• MetaWatchManager rm11b (Updated 10 March)#

  • AgnesLinux Reply #51, 1 year, 2 months ago

    Reply
    Quote from: benjymous at Mar 05, 2012, 03:26 AM
    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
    I MUST make sure to buy a Nexus phone as my next Android device.
    Yes, both of my Android devices - Flipout & Charm - are running 2.1--update 1.

  • benjymous Reply #52, 1 year, 2 months ago

    Reply
    rm11a fixes the 2.1 incompatibility, and adds the preferences backup/restore feature - otherwise there's no real need to upgrade from rm11

  • AgnesLinux Reply #53, 1 year, 2 months ago

    Reply
    OK rm11a works except the backup feature (I don't need it though). I get the same error when attempting to backup my settings.

    Thanks for your continued work on making this awesome connected timepiece better all the time!

    Update 3: I just key a WU API key & switched to using geolocated weather updates in rm11 and now I have the more timely weather updates again, with the bonus of decidegree precision (shows 1.3 °C where I am) & correct graphics to reflect the time of day here. I'm really liking this.

    Update 2: I just noticed the weather observations are not updating automatically anymore. It is set to use Google. WU no longer works (do I need an API even just to pull weather now that's not geo-located?). I've gone several hours now since the last update. Upon exiting MWM & reloading it, the new observations then come up. This may have to do with your code to revise every 6 hours. Maybe it is revising the observations and forecast every 6h. As of now, the weather widget is now useless to me if it's not updated at least once an hour.

    Update: Suggestion for the calendar widget: have it always show the next appointment date & time even if it's days in the future (I have several appointments programmed that take place later this week but are not showing today (widget shows '5 NONE', likely meaning there are no appointments scheduled for the 5th). Perhaps limiting it to showing only up to the same date next month would be smart if the widget doesn't have room for the month value.

  • benjymous Reply #54, 1 year, 2 months ago

    Reply
    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.

  • benjymous Reply #55, 1 year, 2 months ago

    Reply
    It's also worth noting that some settings don't take effect properly until the app has been quit and restarted, so try that, too, and let me know if that makes any difference.

  • Smithers Reply #56, 1 year, 2 months ago

    Reply
    Quote from: AgnesLinux at Mar 05, 2012, 03:36 PM
    Thanks for your continued work on making this awesome connected timepiece better all the time!

    Well said and to all the devs making this a better piece of tech with every release.

    -----
    Smithers. [Galaxy Nexus / Android 4.0.3 / MW Digital FW:0.8.2 / RM11a]

  • AgnesLinux Reply #57, 1 year, 2 months ago

    Reply
    Quote from: benjymous at Mar 06, 2012, 04:31 AM
    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.
    The weather is updating perfectly fine now that I am back to using WU (with an API & geolocation this time).

    I am not using the battery logging but I do have the indicator widget turned on.

  • benjymous Reply #58, 1 year, 2 months ago

    Reply
    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.

  • AgnesLinux Reply #59, 1 year, 2 months ago

    Reply
    Quote from: benjymous at Mar 07, 2012, 06:53 AM
    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.
    I had no geolocation enabled when I was attempting to use Google. Another possibility is maybe Google doesn't update the weather as frequently as WU. I'd still expect your app to check every 30 minutes though, which I found odd that it did not.

  • jeffreytz Reply #60, 1 year, 2 months ago

    Reply
    Just upgraded to rm11a from 10 - benjymous, fantastic update. Thanks for all the work on this. I really love the new big calendar widget and having multiple screens/rows. So far everything seems to be working perfectly via my Galaxy Nexus.