5 ms·

I was extremely disappointed by the noise given by the M7. To make use of the data it spits out, you need to apply filters to clean it up. There are better out

by rismay 13y ago

I was extremely disappointed by the noise given by the M7. To make use of the data it spits out, you need to apply filters to clean it up. There are better out of the box solutions for programmers. For example, https://www.alohar.com/developer/ https://www.alohar.com/developer/. Also, it is not as battery efficient as they promised. It is more battery efficient than the 3rd party offerings. However, I ran iOS 7 on my iPhone 5 for months and got better battery life running the same apps. Amazing since by that time the battery on the iPhone 5 was 1 year old.

rm999 13y ago
> it is not as battery efficient as they promised ... got better battery life running the same apps The point of the article is that the M7 is always active (even if you aren't running apps), so the battery usage of the M7 is baked into the phone itself. This means you can't compare the M7 to non-M7 because you'll actually be comparing the 5S to earlier phones, which have different processors/batteries/etc.
statusgraph 13y ago
Not applying filters is precisely the right thing to do; it gives developers the most flexibility in interpreting the data. Filters by definition lose data, and can only be chosen with a specific use case in mind.
- mturmon 13y ago
  True. Crudely speaking, some applications might be interested in high-frequency jitter ("how bumpy is it here") and others might be interested in low-frequency overall paths ("where in your neighborhood did you go").
alariccole 13y ago
No, whether or not an app is using the APIs does not affect the battery. As this article states, and for my experience building fitly.io, the M7 is detecting at all times. The APIs only access the activity logs.
lnanek2 13y ago
> I ran iOS 7 on my iPhone 5 for months and got better battery life running the same apps I doubt most apps take advantage of the M7 yet. So if you run them on a 5S, they are going to be using battery, and the built-in logic is going to be using battery.

by rismay 13y ago

rm999 13y ago

> it is not as battery efficient as they promised ... got better battery life running the same apps The point of the article is that the M7 is always active (even if you aren't running apps), so the battery usage of the M7 is baked into the phone itself. This means you can't compare the M7 to non-M7 because you'll actually be comparing the 5S to earlier phones, which have different processors/batteries/etc.

statusgraph 13y ago

Not applying filters is precisely the right thing to do; it gives developers the most flexibility in interpreting the data. Filters by definition lose data, and can only be chosen with a specific use case in mind.

mturmon 13y ago
True. Crudely speaking, some applications might be interested in high-frequency jitter ("how bumpy is it here") and others might be interested in low-frequency overall paths ("where in your neighborhood did you go").

alariccole 13y ago

No, whether or not an app is using the APIs does not affect the battery. As this article states, and for my experience building fitly.io, the M7 is detecting at all times. The APIs only access the activity logs.

lnanek2 13y ago

> I ran iOS 7 on my iPhone 5 for months and got better battery life running the same apps I doubt most apps take advantage of the M7 yet. So if you run them on a 5S, they are going to be using battery, and the built-in logic is going to be using battery.