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.