|
|
2010-05-08
, 16:31
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Jan 2010
@ Australia
|
#2
|
|
|
2010-05-08
, 16:37
|
|
Posts: 103 |
Thanked: 120 times |
Joined on Sep 2009
@ London
|
#3
|
|
|
2010-05-08
, 16:43
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Jan 2010
@ Australia
|
#4
|
|
|
2010-05-08
, 18:11
|
|
Posts: 103 |
Thanked: 120 times |
Joined on Sep 2009
@ London
|
#5
|
|
|
2010-05-08
, 18:17
|
|
|
Posts: 670 |
Thanked: 359 times |
Joined on May 2007
|
#6
|
|
|
2010-05-09
, 12:35
|
|
Posts: 110 |
Thanked: 38 times |
Joined on Apr 2010
|
#7
|
|
|
2010-05-09
, 13:32
|
|
Posts: 103 |
Thanked: 120 times |
Joined on Sep 2009
@ London
|
#8
|
|
|
2010-05-12
, 09:08
|
|
Posts: 103 |
Thanked: 120 times |
Joined on Sep 2009
@ London
|
#9
|
|
|
2010-05-18
, 17:59
|
|
Posts: 1 |
Thanked: 0 times |
Joined on May 2010
|
#10
|
I've spent the last week trialing Sygic Mobile Maps on my N900 (trial version from Ovi Store). Overall a very good package and miles better than what Ovi Maps has ever been on Symbian (and there's no point even comparing it with the Maemo version of Ovi Maps).
There's one major bug that's a deal-breaker for me though. Since I haven't been able to find anybody else complaining about it, I'm hoping that I'm just doing something stupid and that it can be fixed.
I've enabled "AutoLock after 5 minutes" in the System settings (I guess that most N900 users are doing the same given the sheer amount of private data we hold on these things). So that works fine: after 5 minutes of inactivity, the phone locks and asks for my unlock code.
Problem is: when Mobile Maps is running and routing me, the phone still locks itself every 5 minutes. So every 5 minutes, I have to enter my unlock code to be able to see the map (not the safest thing to do while driving).
That obviously shouldn't happen. When Mobile Maps is running in the foreground and routing, it's fairly obvious that I don't want the phone to lock itself. Disabling AutoLock altogether is of course not an option.
Is there some hidden setting somewhere I've missed or is this a bug in Mobile Maps?