Notices

tz1,
I finally found some time to get back to trying zmapper. I started out before by running the program as a user, and then using the "root" command from the easy package, or from nitapps.com, or somewhere. Both ways if failed. Today, for fun, I tried "sudo zmapper" and it launced without issue. So I installed strace (thanks to qwerty for posting the correct "components" for the sdk repo) and ran zmapper with it. The failure seemed to come from the zmapper looking for a "/media/mmc1/zmap/zmap.lock" file. Since I made my zmap folder on the internal card, not my external, it couldn't find the folder. I created a zmap folder on the external card through the file manager, and now every thing launches fine. It does load maps from the internal card (where I moved them to after I got zmapper running with sudo), but still uses the external lock file.

Should that be the hard coded location for the lock file? And does it make sense that launching with sudo would ignore the lack of a folder, not even creating a new one? I have the full output of strace available if it would help.

Are you using 0.20 or an earlier one.

I shouldn't have hard-coded the lock (unless in /usr/lib/zmap), so I'll check into that.

Also, what does strace say if you don't do "sudo"? It might not be able to read or write a needed file.

I'm experiencing very bad battery life on my N810 since installing this, so I wanted to remove it to verify this was causing it.
After uninstalling minigpsd using the application manager, I still had the panel indicator, so I disabled that. But I guess that means it wasn't uninstalled completely.

Should I have disabled the indicator before uninstall? How to check it is uninstalled completely (or steps to take to do so)?

thanks

The tzgpsd-statusbar-xxx needs to be uninstalled.

The statusbar applet, the config applet, and minigpsd are three separate packages.

To uninstall you need to remove all three individually since they are installed individually.

Without minigpsd being active the battery life shouldn't be much less (and should improve - the only drain is the statusbar applet polling every few seconds)

thanks, found them. Now to check if this was the cause of the battery drain...

I've occasionally had the internal gps driver go to 100% cpu (the statusbar-cpu applet or using the "top" program in an X term will show if anything is keeping the CPU busy)

the statusbar-cpu applet has not shown me such things....

The only two causes of battery drain I can think of is some bit of hardware left on (e.g. the backlight, wireless, bluetooth, GPS, audio even if the mixer has it muted, camera), or heavy CPU usage.

First day without minigpsd installed and battery drain looks the same, so it is most probably not caused by it.

Now to find out what does