Sensor data not fully utilized in some cases

[GoogleCodeExporter]

Dear friends,

I am postgraduate student and I really like your great project. Recently, we 
are building a research prototype to analyze the sensor data usage of Android 
applications. We found one interesting issue in your code. In your app, the 
background monitors are running to collect environmental attributes (location 
etc.). If there is any change, the "HandlerService" will receive the change 
message, and analyze whether there is any rule registered that is satisfied by 
the change. We found that even the database contains no rules related to 
locations, the location monitor still runs in the background. Then the energy 
spent on location sensing is in fact wasted.

So we wonder whether there is a better design for saving energy. For example, 
the HandlerService analyzes the rules in database, and figures out which sensor 
needs to be activated. In this way, the sensor listener is only registered when 
it is necessary. 

Thanks for your attention! We would like to hear from you :)

Original issue reported on code.google.com by yepang...@gmail.com on 17 Jul 2012 at 4:22

[GoogleCodeExporter]

Completely true, and your suggestion is a great idea and you're correct 
omnidroid does suck up way more energy than necessary as a result.  I'd be 
happy to accept a patch in this regard.

Original comment by case.and...@gmail.com on 17 Jul 2012 at 4:45

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Cool. We will study your code carefully once time permits. Let us wait for a 
patch to make Omnidroid better.

Original comment by yepang...@gmail.com on 24 Jul 2012 at 12:54

[GoogleCodeExporter]

Any progress on this? Seems like it's a pretty big issue if this app always 
fires up the GPS.

Is the app actively maintained? Looks like the last release was 2010 or 2011. 
Could be that it was outstanding code incredibly well written and it has needed 
no maintenance! Or maybe devs have moved on, are busy, and life is happening... 
:-)

Original comment by callum.m...@gmail.com on 4 Dec 2012 at 12:17

[GoogleCodeExporter]

It's not really being actively maintained as most of the devs have moved on to 
other projects.  We'd gladly accept new devs into the project and accept 
patches.  This project was originally based on the Android 1.6 SDK, so I'm not 
even sure if it's compatible with the latest android releases.

Original comment by case.and...@gmail.com on 4 Dec 2012 at 5:50

[GoogleCodeExporter]

I have been using Omnidroid on Android 2.3.3 and so far it works very well. I 
will be able to help test Omnidroid on Android 4.x soon.

Hopefully, I can also provide a patch to fix this issue. Cheers!   :)

Original comment by yepang...@gmail.com on 7 Dec 2012 at 4:15

[GoogleCodeExporter]

That's pretty cool.  Testament to the platform to be that backwards compatible.

Original comment by case.and...@gmail.com on 7 Dec 2012 at 8:27