BetaLabs

@Fleegs,

Assuming the installation was successful, you should have an icon within "installations" on your phone menu.

Fleegle - if you're accessing MapLoader in Data Transfer Mode you haven't solved the problem. See my post 71.

For Nokia Maps How To - see the User Guide on the Nokia Maps website. Turn by turn is a subscription service.

@Ben Rose
I'm a software developer too and I agree that it's impossible to test your applications against any os configuration out there. In this case it is even worse since you have both the phone and the computer to test which complicates things alot. What made me "curse" Nokia was their lack of error messages or logs. If i would have seen how that software was trying to connect to your phone, maybe you would have been able to spot the problem and fix it. A message like "Waiting for device" is dumb and useless to anybody having a problem. I'm not even talking about a nice error message that tells you what to do. A nice simple task log wold do. Something in the lines of:
1. "App started at"
2. "Checking USB connections..."
-> found device x...not a nokia phone
....
3. "Checking Bluetooth connections..."
-> found device x...not a nokia phone
....
etc.

The problem could come from a .NET bug or even a Windows driver but this isn't an excuse. If there's a problem with a proprietary API or library that you're using, you should switch to another API ASAP, not wait for that provider to fix it.

I'll admit that, since this is free software, it's understandable not to invest massive time and effort into it to make it work. Since the betalabs don't handle this application anymore, this thread should be closed with a last message directing people to the right place to post your questions.

Works fine for me on both E90 and N95. You guys must be doing something wrong, the software is fine.

Hello Stephane,
maploader is not compatible with Nokia 6110 since this device uses a different navigation software. For this device, you should always use Map Manager.

Best,
Stefan

Thanks for your answer Stefan.

I just followed waht's on this page :
http://europe.nokia.com/link?cid=PLAIN_TEXT_985070
step 1 : choose 6110
...
and step 4 : Download Nokia Map Loader.

It's very confusing, as I don't see where on this page that maploader is not compatible with 6110.

(just trying to help, thaks again for your kind answer).

I have same drama ! - I have installed Nokia Maps on the 6110, the website instructions now say "Launch nokia maps on your device" - Where is the launch pad ? How do I start Nokia maps ??? Any help greatly appreciated.

You don't have to use the N-series PC suite that is supplied with your N-series phone.

Go to the Nokia website and search for PC Suite. Choose to download and choose your phone model, I chose N95 for my wife's phone.

It installed the standard (not N-series) PC suite but it works fine with the N95 and so does Map Loader 2.0

Hi Stefan,

You asked "Geoff: are you connection in PC Suite mode?"

When I connect in PC Suite Mode, I just get "waiting for Device".

Doing a Web Search, it is clear that quite a few folk are experiencing this too. I've spent a great deal of time trying to problem solve this ( and I am farily technically clued up ), but with no success.

My ".net" install is the latest (3.5), and my PC Suite is the latest - 7.0.7.0. I thought it might be an XP 64 bit issue, but I get the same problem if I boot up in XP 32 bit.
One suggestion I've found that may be relevant is that MAPS 2.0 is looking for my phone as Drive "E". As I have three virtual drives on my PC, Drive E is one of my PC drives. Is it possible that Maps 2.0 is not fidning my phone because of this?

The only other thing that doesn't seem right is that the Maploader Icon in PC SUite just brings up the Maploader web page, rather than the Maploader software.

Anyway, Stefan, please can you help us to get to the bottom of this problem - because there is clearly a problem here.

Thanks,
Geoff

Forgive my previous comment - it's all explained here: http://nokiamaps.site666.info/. I reverted to older (better) version of maps for my region.

@Eugen,

You're spot on. For advanced users, better logging and error messages can be ideal. For average end users they are confusing but a simple write to a .log file in an application folder can be a godsend.

For those still with problems, have you guys tried using a Windows Registry Cleanup tool? There's a good one call Crap Cleaner http://www.ccleaner.com which is pretty good.

I'd advise that you uninstalled both Map Loader and PC Suite from your windows machine, then ran it to ensure they're cleaned off properly. Then try reinstalling.

@Tommi - Thanks for the acknowledgment.

Hi Stefan,

I have the same problem as Geoff.
I have a E90 (russian version) with the last update available at nokia.com (v. 07.40.1.2), Map Loader 2.0.2, .NET installed by MapLoader installation package and Windows XP Home SP2.
The phone is connected by USB cable directly to the USB port.
The PC Suite sees my phone and connects to it normally.
The Map Loader shows the message windows with the blinking "Waiting for device" at startup and this message doesn't go out.

I've tried to install Map Loader on another pc (also with XP Home SP2) and have got the same result.

I hope this info will help you to trace the bug (and for me - to get the maps on my phone ;))

What is the latest version of 2.0 and when was it updated? Is it worth updating again for me?

thanks

Nokia is one step ahead with the NSeries Phones but the NSeries PC suite is one step back. I am a first time Nokia user and had so much problems with the Nseries PC suite. Fortunately I'm competent in my computer and I have XP and Vista running.

I encountered very hard time too when updating N82 firmware because it doesn't run very well on Vista.

I can't imagine those with lesser knowledge solving the problems caused by the Nseries PC suite.But before the problem is solved, we suddenly have OVI software. So from Lifeblog to Photos to Ovi suite, I had no idea which to use anymore? Hahaha :)

Spent half of the day going trought the trouble of updating to version 2.0 on my Nokia N95 - it repeatedly refused to work until I've upgraded my PC Suite to 7.0, and now after all the hassle I have to learn that maps for my region (that I've upgraded too) are much worse with the version 2.0 than with the previous one (don't know how was that possible; but see for example southeast of Croatia, Dubrovnik region for example - the road is going through the sea most of the time). Very disappointing experience, if only it would be possible now to easily revert...

I too would like to confirm having the "waiting for device" problem:

-Nokia N95
-Nokia maps 2.0
-Nokia map loader 2.0.2
-Nokia PC suite 6.83.14.1
-Nokia Software Updater v.1.4.53en (noticing that this modifies everything with regards to connections and pc/mobile interface)
-Windows XPSP2, P4 3GHz asus mb, USB2.0 connection (no bluetooth to test)

I remember using this last year, when i first bought the phone. I think it was on another pc though, and with nokia maps 1.0 (the first firmware)

Hope it is resolved.

I should mention that I use a n95 with pc suite 7.0.7.0 and maploader 2.0.2

nokia map loader 2.02 to be exactly

Any help with regards to reverting back to TeleAtlas maps using MapLoader 2.0? As noted above, in comment #33 (many thanks to poster for figuring out what was the problem!), Navteq maps are *much* worse than TeleAtlas maps for some regions...

Hi, I can confirm what Geoff and German are experiencing. I encounter the "waiting for device" (forever) phenomenon. I use a E51 with maps 2.0, a brand new english language map loader, a German PC Suite on a Greek windows xp. I hope mixed languages don't matter to the program...

I just wanted to buy the navigation feature for our pan-European holiday trip. Go on Stefan, get it fixed! We are on the road starting next week-end ;)

Also, it is very strange that you can't move a window by dragging by window title. I am talking about this window:

http://hotimg23.fotki.com/a/213_35/232_157/kia-Map-Loader-Progress-Windo...

What a surprise! 'Unable to connect, check your internet connection' error message. No, check the skills of your programmers who apparently dont have the ability to make ANY Nokia software prompt for proxy password. Of course the same applies for Music Manager so it looks like i'm staying (not by choice) with iTunes.

I made the mistake to update my maploader software tot version 2.02 ( no choice really). Using a N95-v1 firmware 3.0x
From that moment i have the"" waiting for a device"" error. I tried all kinds of suggestions made here and on the many sites covering this issue. I reformatted the memory card, i tried usb mode, suite mode etc. To no avail.
Running Vista on two computers and both have the same issue.
There should be an update for this obviously crippled application called ""map loader".
During one of the suggested options i had to erase the maps. So for the moment i have nothing.
Please advice.

After experiencing the same "waiting for device" dramas as everyone I have got it working. This is how the final attempt went.
Installed the MAPS software & ran it on my 6110 - it was hidden in "applications" > "My Own" on my phone. The GPS eventually found a signal & showed my general location.
I then tried Maploader whilst connected in PC Suite - no good.
Exited PC Suite & unplugged USB.
Plugged USB again & connected in DATA MODE.
Opened up the phone's G drive from "my computer" & saw it now had the folder Cities created.
Started Maploader & this time it worked...........

Now can anyone tell me how to get Maps to let me give a destination address & then get directions ? I thought MAPS gives turn by turn directions ?

@Geoff,

You're right, I don't work for Nokia but I have worked in Windows software/OS support since 1993 when Windows 3.11 was released.

The OS has changed a lot over those 15years, but it hasn't changed to the extent that a small registry hiccup can't cause this kind of issue. It's also still unable to workaround issues where 3rd party applications may be able to lock device drivers or cause port conflicts.

It's not feasible for any application developer to test their software alongside every other piece of software in existence. Most people are on XP/Vista now, we're talking machines that have Windows builds up to 7 years old.

Most home users continually install new and software on their PCs without a care in the world. The often results in viruses, trojans and other malware which can cause grave issues - but ignoring all that, some software programs just don't work well together.

For example millions of people, including myself, use Apple iTunes. It's horrible, buggy, software and Apple release an update to fix issues seemingly weekly. Owners blindly click yes they'd like to update and more and more changes are made to their windows machine. Some software prompts that a windows restart is required after installation - simply not doing this restart promptly is enough to make many applications not function correctly. But Joe user is blind to all this, they just do what they want and expect it all to work.

The best analogy I can come up with is that installing software on an old Windows build is like trying to use adhesive to glue something to a dirty surface. If you're lucky, the glue will find a clean spot and make a suitable bond. Otherwise, it won't work properly and the joint will be poor. Most consumers just keep adding more glue in the hope it will stick. They'll say the adhesive is no good and try another brand. Ultimately, one can only guarantee a bond if you start with 2 clean surfaces.

How practical all this might be is irrelevent. It's simply a fact. Anybody with a decent experience in Windows support knows that you can spend days...weeks...without finding a solution to a software install issue. I've seen environments (airports and city banks) that have a 20min fix rule. If they can't get it working withing 20mins, they re-install the machine from scratch. We know that simply turning off the PC without shutting it down cleanly can make it not even boot again, let alone cause minor software issues.

I've worked in Enterprise Global support for a major software vendor. You have to be quite confident to turn to a customer and tell them that they have a windows build issue. Major customers like banks, airlines and telecoms companies who spend millions of dollars a year on licensing and paid over a million dollars a year for premium support. The fact was that the software worked in a suitable environment and, on occasion, they didn't have one.

Excepting a few minor device drivers, a clean Windows XP install is exactly the same on every PC. Every single clean PC will have the same application registry settings, the same basic utilities and no conflicting third party software. This is the ONLY environment that a software vendor can test in and, if an application works in this state, it's a working product.

Now, on occasion there will be major conflicts with commonly used applications. If, for example, an application conflicted with MS Office or McAfee Anti-virus then it's clear that whilst the application may work in a sterile environment it may not be entirely suitable for purpose. Which is why many vendors test alongside these major apps. In many cases, a public beta is used to expose the product to more potential issues.

Inevitably, it won't work for everybody. For whatever reason, their Windows has gone bad and not much is going to revive it. It may be that, after numerous support tickets have been logged, a vendor may see a pattern in the issues. Like all the affected people happen to use a specific iTunes version on the same machine. Then they may test with that specific version of iTunes and find a conflict. This can then be investigate and sometimes fixed.

But often these patterns are just impossible to find. There may not even be a pattern, just random corruption.

Sometimes a vendor gets lucky and somebody like me is affected by the problem, which is why I was desperate to reproduce the issue for Eugen above. If I can recreate the issue, there's a large chance I can find the cause. I've had application problems in the past. The first thing I do is whack it on a clean build machine. If it then works, I continue installing all the other apps that are on the affected machine. If we're lucky, the installation of one of the other apps will break the new app. We then know which application is conflicting with the new one and can log a reproducable software problem with the vendor. We're not always that lucky though. Often we get the new PC to the exact same software levels as the old one and still the new software works. Windows was just broken somewhere. At this point we have 2 identical machines, one works, one doesn't. So we format the bad machine and put a clean build on it ready for next time.

So yes, it's probably bad windows install. If could be a bad Nokia install. But one thing is for sure, the software works.

Update:
after waiting for 4-5 minutes I get the not compatible with nseries pc suite message.
When will be the maploader compatible with it?

Uhm, I have a BIG problem

@Eugen - Which operating system are you using?

Oh, and i've tried both usb cable and bluetooth connections. For the usb cable i've set my phone in both data transfer and pc suite modes. No luck

@Eugen

I just ran my again to test. I was running map load 2.0 but not 2.0.2. It offered me an upgrade, I accepted.

Now running 2.0.2 I ran map loader and erased all my map data then re-added it all.

No errors, all working perfectly.

I'm actually using PC suite V6.86.9.0, which is a different version to you. When I find a moment I will upgrade and try again with my E90 - although your version of PC Suite worked just fine for my wife's N95.

One question. You have run the maps software previously on the memory card to which you are trying to install? Please check your memory card and confirm you have a folder by the name of "CITIES". If not, run Maps on the phone again and let it lock on to a GPS signal. When the CITIES folder is created, try map loader again.

It works for me using Bluetooth or Cable, the connection type doesn't matter much but cable is faster.

asdasda

This version is working very well.But i want a software which also supporting Linux like open source operating system.This software is vista compatible.Ok.
Expecting more updation from Nokia.
Thanks
----------
Nikky Philip
Social Media Marketing - 511157223.522673
http://www.widecircles.com

Yes, I can confirm that data transfer mode in the middle of the maploader "waiting.." DOES make a difference.

Regarding "Waiting for device": I didn't try any tricks, but I only turned off my antivirus monitor software and Nokia Map Loader now works - in "PC Suite" connection mode. :)

Nokia Map2.0 not for S40? where is the Link!

Still no support for Nseries PC Suite :( add it to the next update please?

I was experiencing the "Waiting for Device" issue with my setup (Nokia N95 8GB, Windows XP running under Parallels on a MacBook, Map Loader v2.0.2) after reflashing the firmmare on my device.

I found the solution was to (a) install Nokia Maps on the device, (b) run Nokia Maps on the device, (c) wait for Nokia Maps to find a GPS signal.

If I did ALL of the above, then the "Waiting for Device" issue went away.

you have to plug in your memory card run nokia maps and go through all the accepts then run nokia map loader with the device set to pc suite

Hello
Mark: no, it will not. It will use the settings from Internet Explorer.
JayWalk: yes, we are working on this and it should be in a future release.

Best regards,
Stefan

WoooW.. Sorry but there's no way to install it on the Mass Memory?? Becouse I have a N81 8Gb and the Phone Memory is not so Big.. And Now, with Nokia Maps 2.0, Python and 1 theme installed, I have only 640Kb of Free Memory.. Not so Useful!

wanna mac version :-/

when we r can test first beta version of MapLoader fo OS X?

@Eugen,

Glad you got it sorted and the software DOES work after all :-)

OK......I have the E71 and here's how I get the MapLoader to work:

1. plugin usb cable to your PC (PC suite mode)
2. Open PC suite, click on "Download Maps"
3. Map Loader will run automatically
4. wait for a while......Voila!

Ben,
I presume that as your name is a link to the Jaffacake site, you don't work for Nokia.
Either way I don't find your post at all helpful.
a. Your suggestion that I do a new Windows install is not one I intend to take up, and not a sensible suggestion or proportionate response in my view. That would be a mammoth task, and absolutely a last resort. Certainly not worth it just to get Maps 2 functionality.
b. Your assertion that "Clearly there is an interaction with a 3rd party app here" goes well beyond what you can know based on the evidence. Other people who claim to have solved the problem have NOT solved it by reinstalling windows. Also you state "with a clean formatted Nokia" and the problem could just as well be with S60, and the device itself.
c. I know well enough what the beta labs blog is for, and I don't need you to tell me. I also mnow only too well that the quality of Nokia support via the Careline is abysmal, and whenever I have tried to use it I have found it a complete waste of time. Furthermore this is a new product, and many people are having the same problem, and I think it is perfectly reasonable to ask for help via this blog. Stefan has been prepared to help others with support-related issues via this blog.
d. Unless you do atually work for Nokia (in which case can you please tell me what your role is within Nokia), may I request that you avoid telling me how I should and should not interact with Nokia.

if your having the waiting for device problem with nokia maps loader.
1)instill your memory card in your phone the load up nokia maps from your phone after your done with that close it.
2)after that connect the phone to your comp. in pc suite mode
3)the load up nokia maps loader then it should work

thanks,

But the most important feedback for the Nokia Maps is why it is sooo expensive!?! Just for experimenting with the software, I decided to choose a small baltic region, and one year license was about 120 us dollars??? I got my e61 for 300 dollars, so driving instructions for have of price of the phone?!?! this doesn't make sense :-) pls explain... I would probably pay something around 20 dollars and only for unlimited regions... pls reconsider pricing asap!

http://hotimg15.fotki.com/a/213_35/232_157/a-Map-Loader-Expensive-Licens...

Keep up a good work!

There seem to be a problem with removing the Nokia Maps 2.0

Is there anyway to remove nokia maps 2.0 without formating the phone memory? If i do that would it also remove my places/poi/landmark?

Thanks