Notices

minigpsd itself generates the icon displayed in the statusbar. I have a version that substitutes a "never started" version in yellow (for now) if the file doesn't exist.

For those that the statusbar doesn't work for the BT stuff, could you check in /usr/lib/hildon-desktop/minigpsd-sb.py to see if it says import gconf or import gnome.gconf near the top? And can you set the Web Title?

If you look closely, the icon displays the satellites with signal strength. Those teeny blue to red to yellow to white dots. I know, you can't see them, but I'm working on that. It turns out that it is faster and easier in many ways to have minigpsd generate a pixmap than to try to do so in python from a datastream.

Start only when stopped, Stop only when started is also on my list now. I thought about it but I'll bump it up.

You also need to run minigpsd as user, not root (and/or remove anything in /tmp that may have been put there as root). It uses "sudo l2ping..." to determine if the configured bluetooth devices are there. To do that it adds an entry to /etc/sudoers but root cannot run sudo so gives that error.

I'll also try to setup my zdez.org site as a repository - I've looked at that, but as I've mentioned on MY tablet, Application manager isn't working normally. But I can take advantage of the newly reflashed to see what is going on.

The problem with mirroring bluez-utils-test is that they go with (and I think are part of) the bluez stack itself, so when bluez-* in the main section gets updated, any mirror in extras will break the dependency, or not reflect changes made in the mainline bluez stack source.

And one final word about AppManager - yes, I understand the behavior, but I still think it is bizarre or imbecilic. One goal (which only seems to be there when I complain about invisibility of non-user packages) is "think of the user, noobs need to be able to have a clean list of apps". And when doing a mere enable-disable puts junk in the list, and the enabled list is far from user only? Well, that is how it is supposed to work even though any average user would be completely confused. Before worrying about the next release, they should first untangle the contradictory goals of the application manager, repositories, categories, whatever, for the existing Diablo release. It shouldn't be this hard or confusing either for first time users, power users, or developers.

I am tempted to port one of the managers or write a python front-end of my own.

The state of your N800 is... strange. It definitely doesn't match what I've seen.

Is it possible you've got a corrupt image on your computer, and you're reflashing it with the same corrupt image? That's all I can think of...

fat fingers again.

Try the pre3 and see if the BT stuff works now.
(The standalone and statusbar were the same except for a typo I probably hit while closing my editor. Fixed now).

http://zdez.org/TZGPSD-Statusbar-Applet-0.30-pre3.deb

It is possible that the image is corrupt, but the various archives and layers are checksummed and they report no errors (in split or as the whole image). Generally something gzipped breaks badly after the error. But two images (n810 and n800 as separate files)? And that is one of the reasons I reflashed more than once - when it was acting strange, I redownloaded (or Nokia's windows flasher tool did) and reflashed and the same thing.

Confirmed and voted.

Thanks Tz1 It's all working now with http://zdez.org/TZGPSD-Statusbar-Applet-0.30-pre3.deb update . I can now edit all setings from the top down . Start and stop also woking fine ..


Thanks
computerfreek

l2ping doesn't seem to interfere with much of anything. rfcomm does.

That is part of the complication. l2ping needs sudo, and it is easier (and safer, and near-zero CPU) to add that one line to sudoers. I check for the device using l2ping (it may only ping once and just hear a turn-on announcement), and only when I see it do I do rfcomm. If the device disconnects, I go back to l2ping.

That was the only way I could manage to connect, break, and restore connections to my BT gps without interfering with everything else. If I lose the BT GPS (GPS lock or connection - think driving to a park, then walking around the park) I switch to the Nokia internal as the default device. (I still log the internal GPS stream to the KML file when the BT device is on and have a post processed comparison kml somewhere).

I should also add a root check on minigpsd and complain if someone tries to run it as root (as I've done myself mistakenly).

There is now a zdez repository. I put bluez-utils-test so there would be no missing dependencies and it seems to work in blue-pill on my clean n800. This will install minigpsd, but not the python applets, but they will be in user/navigation on your tablet.

http://www.zdez.org/minigpsd.install

I'm not sure if it will pick up updates (I need to read farther), but for the time being I will try to keep everything in sync, though source will still be at the top level

I'm reinstalling now, out of your new repository. I'll let you know it randomly causes the errors again (though I honestly don't think it should). From what I saw before, I liked it. I'm going to see what I can do about using it for the built in map program instead of the normal gpsd. Thanks for your work!

If you are looking for info on the deb repository, gene cash has an excellent explanation of how to implement it here, including how to update it. Assuming of course that you are running your own Linux server (which It appears you are, but that may clarify for any one else who sees this).

built in map program is working for me you have to start minigpsd then load map program it will ask to turn on GPS say yes it will load the default icon for gps but you will see it will not lock it will just use minigpsd at that point .works fine like that for me ..


Thanks
computerfreek