Sounds like you need to zoom out a little more.

Perhaps the autloading algorithm should give up on map tiles that have gone off-screen?

Probably, but I thought the zoom was reasonable at the time. Was taking ~10 secs to traverse a tile (or so). Of course it's all relative to your speed (I did like the suggestion the map should zoom relative to the current speed).

The real problem with this is the bandwidth available - sometimes it sucks. Makes a 28.8k modem feel fast (ok, I guess it's about the same really). My experience with GPRS is it's very slow. I'd guess it takes about 10 secs to download a single map tile, vs. 2 secs with EDGE. Add in any dropouts while moving and download time can really lag.

(I've been so excited lately - I just got my EDGE phone and it's changed the whole experience for me - before having GPRS connectivity was useful in a pinch, but so slow. Now with EDGE, it feels like a decent connection. Like slow DSL, I guess. I sat in a bar tonight scrolling around, downloading maps, watching the progress bar in maemo-mapper just amazed at the speed. Guess I'm easily entertained)

A great idea actually. Plenty of opportunity there for tuning too - sample the download speed as well as current speed and load the queue (maybe non-trivial, but could be fun to tweek).

Brad.

that would be great as there are also other issues with localisation.
for example the german "Straße" becomes "Stravenueße" if it stands alone. combined words like "Universitätsstraße" do not get changed, though.

maemo mapper nokia 770
 

hi, nessuno parla italiano??
help maemo mapper

At 30 mph or more, you probably don't need to be at the most detailed zoom level; the further you zoom out, the fewer maps you will need to download, which should help alleviate bandwidth issues.

I don't think it's a thread inefficiency problem. I've tested auto-downloading on my Nokia 770 over my high-speed WAN (panning around a lot to stress the system) without any maleffect on the UI, so it's more likely a bandwidth problem, although that shouldn't affect the UI itself.

There is a built-in sanity check in the NMEA protocol, so unless your GPS is ignoring that part of the protocol, it shouldn't plot a point unless it is considered "valid" by the GPS receiver. This is, of course, receiver-dependent.

[QUOTE=bradb]- flite works great, but the volume is so low I don't think this is really useful without earphones. And by great I mean it has a terrible voice but is a real cool hack :-)

I've noticed this sometimes with my WAN connection, but only when that WAN connection is not currently in use. If I'm listening to internet radio while I start Maemo Mapper, for example, I have no problems. It's bizarre, but I'm not sure there's anything I can do about it without moving all of the bluetooth connection code outside of Maemo Mapper.

GPSD support (which will hopefully also assuage some of the nastier connection-related problems with Maemo Mapper) is coming with Maemo Mapper v0.2, which will be released for the 2006 OS.

I'll be releasing a v0.1.1 later this week to address some of the reliability issues.

Hi,
Firstly, thanks for a great applicaion - very slick in operation, does what it's supposed to do (mostly anyway, see below :-p) and without the bloat...

Secondly, I'm experiencing the locking up problem as discussed earlier in the thread - has any progress been made with this at all? I'd be willing to do any diagnostics with my setup if required.

Essentially what is happening is that mapper locks up and becomes unresponsive to any user input. Sometimes a small white box appears in the top right corner of the screen, similar in nature to the dialogue boxes that say "Searching for GPS reciever" or "Establishing GPS fix", although no text actually appears. The screen will still change back and forward from fullscreen mode - although the screen isn't properly refreshed when doing this.
It is possible to close maemo-mapper by clicking the red X in the top right. Reopening maemo-mapper results in it being unable to find the GPS receiver. Interesting, running 'hcitool scan' reveals no bluetooth devices (even though my BT phone is in range) and gives an error message along the lines of "Cannot open socket" (IIRC).

Rebooting fixes the situation. I don't believe the GPS reciver loses signal when it happens, but I could be wrong.

FWIW:
IT 2005 software edition, v 5.2006.13-7
Nokia 6230i phone with BT enabled and in range at all times (although not actually connected at the time)
An unbranded BT GPS reciever, claiming to be a model GNT-120 (chosen because it was cheap!).

Sorry for the lengthy post, I've tried to include as much detail as possible. Again, I'd be more than willing to do some debugging if required.

Thanks again,
Ed

**
And having just posted all that, I've noticed that you're planning to release v0.1.1 to address these issues - feel free to ignore me!

I've seen the same thing as ehjones, but don't have a good sense for exactly when it happens. The UI has definitely stopped running.

I fixed my own problem of errors when parsing route files. I open the .xml file in Notes and then save it. This removes/changes the characters which prevent correct loading of the file. The announcements will probably use the modified text but at least I can load the route.

Now that I have a route opened, I want to download the maps along the route using the relevant entry in the menu but it takes far too long. I think this is because I used an angle of 0.000000 when generating a nice smooth route and I suspect that a map is downloaded for each neighbouring location, ie. each jpg is downloaded several times. Is there any way around this, or will gnuite change this in a future version?

More of atof problem!
 

I think there are same kind of atof/ftoa problem in GPX route/trace files, because I have to replace dot (.) with comma (,) in lat and lon to get route files generated with "GPX driving directions" to work with my MaemoMapper and all saved trace files use comma!

:confused:

Flite
 

I'd also like to say this is one of the best apps I've used thus far for the 770. I even went out and bought the same bluetooth GPS reciever and hooked it up. Went driving around sometoday and I'm just totally blown away. This takes my nokia to a different level.

One thing I'd like to say is that there's a donate button on the site. Personally I already clicked and donated. I'm not trying to toot my own horn, but just suggesting that we all love open source and I personally think if we're going to encourage it, its good to give a little back.

So, my real question in all of this is flite. I've installed it, and the little 'flite test app' gives me text when I type it in. How-ever when I'm running mapper, I hear no speech at all, and I've got the volume turned all the way up. Is there anyway to trouble shoot this?