[randomerr]

I would love to plug a cheap accelerometer an get these efficiencies. But it leaves me some questions:

* Will these techniques work on a stock Android device for stock programs (ie Google Maps)?

* Will the different (extra?) calculations cause my processor's calculation to go up, killing battery life? I didn't see any testing on this and your statements seemed questionable - "Herewith, the algorithm should not consume whole battery within 3 minutes as well as all available RAM."

Doesn't Android already have similar filters? I would assume they do since they've been in the business for a while.

This looks like great theoretical ideas. I hope you can use it to get a job at Google or turn it into a marketable product.

[Gen1us2k]

1. It won't be working on stock devices, unfortenately. It's library to integrate to your android application

2. Extra calculations don't consume as much battery as GPS and with this technique we use GPS less often. In other hand we use accelerometer and magnetometer. I tested this by eye :) and didn't find big difference between GPS only solution and presented solution. But as written in article - it doesn't accumulate coordinates.

3. Android already has similar filters. They use Kalman filter and many interesting things. See here : https://android.googlesource.com/platform/frameworks/native/... and other files. They did really huge work here :)

[londons_explore]

For 1., on android you can have third party location providers I believe, and then any app could use it.

[Gen1us2k]

Yes, but you need to specify coefficients somehow for that and add calibration step.