View Single Post
Posts: 324 | Thanked: 739 times | Joined on Jun 2009 @ São Paulo, Brazil
#84
Originally Posted by rlinfati View Post
@rubberduck the version 4.6 is not the same version of traysh

the actual method is use the cell tower because is power efficient, the gps will drain your battery, you can not change it.

the interval is in seconds, and not new position are submit before of last_update_time + interval

the daemon is not running at the startup, i need more testing before of enable this option ( roaming, 3g can be expensive and a battery drain )

the version of traysh have some bugs, and need to be fixed before to submit to extras... but i backport some features from their code.

btw, if you run from terminal, can see a log of the operations...
It's good to know you're back in development. I didn't thought you did, that's why I didn't upload my hacks this week.

By moving the gui out of the daemon to a separate file and using QCoreApplication instead of QApplication, I got a working daemon that only takes 2MB of RAM, including shared libraries. The updates are working as they should now, the program won't connect to internet and will update when connected. Also, I implemented some code to not update the location with a less accurate position, it considers the uncertainty of the new and of the previous positions. As a daemon, it is working really very well now, tough bigger update intervals are still missing.

To reduce battery drain, might we could turn the gps off and turn it on only when we want a new position. Of course this aproach will only work if the update interval is big.

About using cell tower, here where I am it's not possible to get a position with a better accuracy than 800 meters, and that's a lot. My girlfriend has an iPhone 4 and her positions are very precise, so I'm pretty sure the official Google updater uses the GPS. It would be nice if we could measure the battery drainage...

I think we should split the app into 3 standalone binaries: a very lightweight daemon that only updates the position, a settings GUI witch can be run from the system settings but also from the daemon or the latitudeGUI (this already happens if the username is wrong) and the latitudeGUI witch is only a viewer and witch may run the daemon if it's not already running (to provide the updates) and the settings, to configure it. But that's your decision.

I'm attaching a new deb, please have a try. As I mentioned, the gui won't work, it won't load at all, but the daemon is working really very well.

Probably the changes I made to the code I was working on won't fit in the git anymore, will they? I'm a git newbie. How can I upload my changes? I'm attaching my current code here as well.
Attached Files
File Type: deb googlelatitude_0.5-1_armel.deb (59.5 KB, 106 views)
File Type: gz googlelatitude_0.5-1.tar.gz (296.0 KB, 106 views)

Last edited by traysh; 2011-01-24 at 08:04.
 

The Following User Says Thank You to traysh For This Useful Post: