Numbered badge on MS Health Live Tile

[MDK22]

I'm on 14393.5 on my Lumia 1520, Health tile pinned w NO number on badge, yet.

I have motion data turned ON, edited Health tile preferences, showing all ...

A guess = Number of hours left on Battery, number of notifications on Band, dunno, because of the numbers you show.

I have NO Band, NO number on badge - but, health does record my steps (at least it used to)

 

[LarsCor]

No badge, but no live tile neither.

 

[poit57]

My badge went from a 6 yesterday to a 5 this morning when I woke up. It's definitely nothing to do with battery because when I woke up and plugged in my Band this morning, it had 1% battery. I still can't find any type of notifications in the Health app on my phone, and nothing on the Band itself to correspond with this badge number.

 

[Roberto Velazquez R]

I already explained this weird situation to MS Band2 support, everybody should do the same ,open MS health app>menu>Helps & feedback

 

[sp4072]

I have been looking into it, trying to figure it out. The only thing I can think it might be is a rounded number of the sleep duration, but I am not sure.

 

[evillama]

Mine changed from 5 to 6 today. Absolutely no clue why...

 

[JDH58]

So mine has progressively increased every few days. Started at 4, skipped 5, went to 6 and now 7. I cannot correlate to anything.

 

[Dave McQueary]

My number has stayed at 5 but my sleep hours have not.

CURSE YOU MYSTERY NUMBER!

 

[fly_branch]

Mine still has a 4 and has never changed. The only four I can come up with is 4 connected applications. Unless I take my age divide it by 10, subtract 7, add 2, multiply by 5, and then divide by 6 and then that might be the 4.

 

[gbobman]

Seems as if they updated something and didn't tell us. Went from a 6 to a 5 then back to a 6. Phone 8.1 with Band 2.
I'm flummoxed.

 

[evillama]

My suspicion is the dev team enabled a troubleshooting flag while coding and accidentally released it into production, so it has no end user value.

 

[kdk24z]

I received my Band 2 replacement today. I was having the battery issue where it would shut down and say the battery drained even though it had 75 to 95% charge.

Before I synced my replacement band to Microsoft Health app, there was no number in a circle on the tile. That's why/how I ended up here to find out what it is and how to get rid of it.

I'm on a Lumia 925 with 8.1.

 

[hdtvchris]

Mine seems to jump around randomly. I have a number 2 right now and I had 2 missed calls today. Maybe its tied to missed notifications. Il keep watching it.

 

[Rgodel]

Apparently it is a bug: https://www.reddit.com/r/MicrosoftBand/comments/4w4h9d/notification_on_health_tile

...an interesting theory was put forth by another user that the number indicates how many times you have reached your daily step goal.

 

[kdk24z]

I don't think it has anything to do with step goal. I didn't have any numbers showing on my live tile until I connected and synced my band 2 replacement. Then it suddenly showed a 4. The next day it showed a 5 after a night's sleep. It has remained at a five ever since and I've met my step goal every day since and it hasn't changed. I guess it's still a mystery.

 

[fly_branch]

Maybe it is keeping count of the number of apps Windows mobile has lost this past week.

 

[Nate Silver]

With the Android version of the app, I notice now that when charging the Band, the app will throw up a number (1) on the tile.....er...icon, indicating a notification, namely that "your MS Band is now fully charged". So maybe its something to do with a future similar notification feature on the Windows version of the app. If so, it certainly doesn't appear to be ready for prime time.

 

[PhalanxPunx]

That could be true, but they probably would have released an update to the app to stop that. Just my guess though.

 

[anon(5415472)]

It's a feature that was accidentally pushed but isn't ready for primetime yet. So until they finish it, it's a bug.

 

[evillama]

My suspicion is the dev team enabled a troubleshooting flag while coding and accidentally released it into production, so it has no end user value.

Well, it wasn't for troubleshooting per se, but guess I was right...