MetaWatchManager rm11b (Updated 10 March)#

@ benjymous Thanks, that seems to have done it.

Thanks, this seems to be working great via my GSM Galaxy Nexus and firmware 0.8.2 on my digital watch. The icon preview is very cool, and I like how I can have the 4 day weather forecast show until there's a missed call or gmail.

So I think I figured out the sticky notifications - they only work for things like SMS, correct? Not "Other Apps". I use Google Voice on my Nexus, no one really has its "real" number, so most of my notifications are coming through that. It displays the notification text on the watch pretty well but it would be great if google voice messages could work like SMS messages.

In lieu of that would it be possible to add an option to be able to "dismiss" non-sticky notifications as well? That way if you set the timeout on non-sticky notifications to 120 seconds it could act like a sticky notification.

Recall last notification also now works for me with this build (seems to work for sticky and non-sticky notifications).

Music controls are also working fine. I use headset emulation as I only listen to media with a headset connected and this way it works with my podcast player (Doggcatcher) as well as Google Music (the MusicServiceCommand worked fine with Google Music but not Doggcatcher).

Thanks again, this is awesome

@serountree Great - thanks for letting me know
@jeffreytz Yeah - the notifications UI needs a bit of a revamp - I plan to replace all the notification checkboxes with a choice of off/popup/sticky rather than having a single sticky option

First of all thanks you for rm10 version. Very convenient variant of MWM!
Small functional suggestion - it would be nice to display metawatch battery voltage (or % of charge) on main MWM display.

@mbasov Yeah, I plan on adding some extra watch and phone status widgets - the only issue is that polling the watch battery also drains it faster, so we'd need to find the right compromise there!

If anyone wants to add their own widgets, I've done a fair bit of refactoring in the codebase, so that the widgets are now in their own separate classes, so it would be easy to fork the code, add your own widget classes, then submit it back to me to merge.

I'm also going to integrate Craig's intents for external widgets when I get a chance

@benjymous, I like the idea of the check boxes per notification type.

I've noticed one other thing, if I ever use the music control screen the buttons on the left side stop working for functions outside the music control screen (i.e. battery status and watch info screen and the pairing screen won't display). The LED light button still works fine though (probably because it's mapping wasn't changed by the music control screen).

I thought button mapping was being fixed in firmware 0.8.2, or is this something else?

I'm sure this has been thought of but one feature I would like to request is skipping backwards / forwards of tracks as part of the media controls.

I'm using MW with a tablet hooked up to a stereo and can use it as a remote control. It's super useful to do it from my watch!

-----
Smithers. [HTC DesireHD / Virtuous Quattro RC3[ICS] / Android 4.0.3 / MW Digital FW:0.8.2 / RM10]

@jeffreytz It was sort of half fixed

In 0.8.1 and earlier, the FW would forget the re-assigned keypresses pretty easily (e.g. if you bring up the menu, or after a notification)

In 0.8.2 the bindings stay put, but when MWM unbinds them, the FW doesn't restore the default actions (so they get left doing nothing)

I've requested an extra FW message that will restore the default button bindings, which should make it all behave as expected.

Quote from: benjymous at Feb 14, 2012, 08:59 AM

@mbasov Yeah, I plan on adding some extra watch and phone status widgets - the only issue is that polling the watch battery also drains it faster, so we'd need to find the right compromise there!

I am telling about printing watch battery information on MetawatchManager main screen on PDA/Phone.
I think, it can't consume more watch battery power because MWM already have got this information and store it on SD card...

Quote from: benjymous at Feb 15, 2012, 03:15 AM

@jeffreytz It was sort of half fixed

In 0.8.1 and earlier, the FW would forget the re-assigned keypresses pretty easily (e.g. if you bring up the menu, or after a notification)

In 0.8.2 the bindings stay put, but when MWM unbinds them, the FW doesn't restore the default actions (so they get left doing nothing)

I've requested an extra FW message that will restore the default button bindings, which should make it all behave as expected.

In what situations would unbinding occur?