General known problems (bugs)

These are the general MGMaps issues that I'm aware of:

• Full screen problems — the menu may not work if you enable full-screen mode. As a workaround, disable full-screen (by pressing 1) before using the menu, then re-enable it (using the same key 1) when you're done.
• Exit hanging — the application hangs during exit if the internet connection hangs or if a networking error occurs.
• Pause/resume does not work in all cases — if the phone rings while you are running MGMaps, the application may be closed immediately.
• Caching problems — sometimes when the cache size is set to its minimum allowed value, you may notice that a map tile gets removed from the screen even if it was downloaded, and is re-downloaded after some time. Set the cache to a value higher than the minimum if your phone has enough memory to avoid this issue.
• Incompatible settings when upgrading — in some cases when you upgrade from an older version of MGMaps, you may find that you are unable to save settings or locations. In order to fix that, you should uninstall MGMaps completely, then reinstall it.
• GPS settings do not work in the welcome screen — as a workaround, first display the map by choosing Start, then go to Settings to enable or to configure the GPS.

Supported Devices

This is a list of phones and PDAs known to be supported in MGMaps version 1.19. For features introduced in MGMaps versions 1.2x (like GPS), see the next paragraph — advanced features.

• Fully supporting maps (for GPS support, see the advanced features):
  • Series 60, 80, 90 Nokia phones: N-Gage, 3230, 3250, 3650, 3660, 5300, 5500, 6110 Navigator, 6120 Classic, 6121 Classic, 6600, 6260, 6620, 6630, 6670, 6680, 6681, 7610, 7650, 7710, 9300, 9500, E50, E51, E60, E61, E62, E65, E70, N70, N71, N72, N73, N75, N76, N77, N80, N81, N81 8GB, N90, N91, N92, N93, N93i, N95, N95 8GB
  • most MIDP 2.0 Nokia Series 40 phones: 3110 Classic, 3220, 5140, 5140i, 6030, 6101, 6170, 6230, 6230i, 6275, 6280, 7270, 8800
  • MIDP 2.0 Sony-Ericsson phones: J300, K300, K500, K510, K530, K600, K608, K610, K700, K750, K800, K810, K850, M600, P1, P900, P910, P990, S700, S710, V630, V800, W200, W600, W660, W710, W800, W810, W850, W880, W910, W960, Z500, Z750, Z800, Z1010
  • Motorolas: A780, A925, A1000, A1200, E398, E680, E680i, E1000, E1070, i605, i870, i875, M1000, MPx220, RAZR V3x, V505, V551, V600
  • Blackberry: 7100, 7290, 7510, 7520, 7920
  • Samsung: A620, A640, A920, D500, D720, D730, E250, E900, M500, X700, Z500
  • LG: 225, CU500, KE970, PM325, Muziq
  • Panasonic: X700, X800
  • Benq-Siemens: CX65, CX75, EL71, S65, SF65, SK65, SX1, SXG75
  • Other: PocketPC/WindowsMobile phones (using the IBM J9 as J2ME VM), Sanyo (s750, M1, MM-5600, MM-7400), Qtek 8310, Sharp (550SH, 902), Sagem (myX5-2, myX8), and many other phones and PDAs
• Low-memory mode only: Some Motorola phones (V400, L6), some Nokia Series 40 phones with QVGA screens (6233, 6300).
• Supporting only maps: Sony-Ericsson phones with MIDP 1.0 (T610, T616, T630, T637, Z600, P800). These phones also seem to support satellite imagery, but their memory size is pretty low so the app may crash. Also Sanyo 8100/8200 phones seem to only support maps, due to the same low-memory problem.
• Not supported because of too-small memory size: MIDP 1.0 Nokia Series 40 phones (3100, 3200, 3300, 5100, 6010, 6100, 6610, 6610i, 7200, 7210, 7250, 7250i). These phones were supported in MGMaps version 1.0x, however Google has removed the old-style maps, so MGMaps 1.0x does no longer work.
• Not supported for various reasons: some Motorola phones (RAZR V3, V3m — V3x works fine), some Verizon phones (see the Proxy support section), some problems were reported with Sony-Ericsson P900/P910, Nokia 6820 displays white borders around map tiles, Toshiba VM4050 and Motorola E680 seem to be unable to launch the application.
• If your phone is not listed here, it's probably supported! You should download MGMaps (it's free, what have you got to lose?), and let me know if it works or not.

Advanced features support:

• Full-Screen mode is supported on most of the MIDP 2.0 phones. This includes the Nokia, Sony-Ericsson, Siemens, Motorola phones listed as fully-supported above.
• GPS support over bluetooth was reported to be supported on most Nokia Series 60, 80, 90 phones, on Nokia, Sony-Ericsson and Siemens phones with bluetooth (like Nokia 6255i or SE K750i or Siemens SK65). It does not work on some PDAs and Windows-Mobile phones that do not have support for the JSR-82 standard. Also NOT supported:
  • T-Mobile SDA and other Windows-Mobile based phones are not supported.
  • Siemens SX1 (seems to run an older version of Symbian that supports only MIDP 1.0).
  • Some Series 60, 2nd edition phones were reported to crash quickly after GPS is enabled. These include Nokia 6620, 6630 or 7610 (but not 6600 or N70, where MGMaps works fine).
  • Motorola V600, RAZR V3, Sony-Ericsson S700, P800, Z800 are listed here as not supporting JSR-82.
• Internal GPS support was reported to work succesfully on Siemens SXG75, Motorola iDEN i870, i875. As for the rest of the GPS-enabled phones:
  • Some Motorola phones (A920, A1000, E1000) do not support the JSR-179 standard, but GPS can be enabled on these phones. See the news page for more details.
  • Sprint phones also do not support the JSR-179 standard and use another custom implementation, support for these phones is under development.
  • Nokia 5140i with Xpress-on GPS Shell does not support JSR-179, and does not work with MGMaps.

Known problems with specific phones:

• Nokia Series 60 3rd Edition phones (some of the newest Nokia smartphones, like the E60, E61, E70, N80, N91) do not allow the Java application to access the GPS device over bluetooth. Instead, you need to pair the phone with the GPS before starting MGMaps and select Internal for the GPS Device in MGMaps - the application will then use the bluetooth GPS paired.
• Nokia Series 40 2.0 phones (many new Nokia phones, see above, 6230i, 6230, 3220, 5140, 6021, 6170, ...) — the application might not work, with or without proxy enabled. If that is the case and the screen remains blank or you see the "map tiles not available" images, you need to set up a new access point for the application. Click here to view/download detailed instructions (sent to me by Frank Dellé), initially written for Opera Mini but adapted to MGMaps (they should work with any J2ME MIDP application that needs internet access).
• Some Blackberry phones cannot download the application and display Error 907 Invalid Jar. See the workaround on a Blackberry forum, I'm also pasting it below with the links changed to MGMaps:
  • Change the Content Mode in your BlackBerry browser to "WML only"
  • Point the browser to http://wap.mgmaps.com/mgmaps.jad
  • If that doesn't work, point the browser to http://wap.mgmaps.com/mgmaps.jar
  • Don't forget to put the browser's Content Mode back to "WML & HTML" after you've downloaded and installed the application

Mobile Operators

Mobile GMaps is not operator-dependent, it only needs internet access. In theory, as long as your mobile provider allows internet access, the application should work.

Unfortunately, things are not that simple in practice. Many operators rewrite the web communication in order to "optimize" the web content for mobile phones, especially when using WAP plans (Internet plans are designed to access the web from the computer using a mobile phone as a "modem", so pages do not need to be optimized). This sometimes means that they change the images (resize/reduce the number of colors) or make other changes, and if that happens the application may not work.

Known problems with operators:

• Some Blackberry phones do not work on T-Mobile, USA, even with proxy correctly configured (see below). If that happens, try the following:
  • Go to Options->TCP (or Tools->TCP)
  • APN: wap.voicestream.com
  • Username: (leave empty)
  • Password: (leave empty)
  Once you have saved the APN information, you should reboot your Blackberry by removing and reinserting the battery.

Proxy Settings

Proxy settings for:

• WAP/GPRS access with T-Mobile, USA:
  

  Proxy Server: 216.155.165.50
  Proxy Port: 8080
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

  Alternate settings (if the above do not work):

  Proxy Server: 216.155.175.188
  Proxy Port: 8080
  Proxy Username: guest
  Proxy Password: guest

• WAP access with O2, UK:
  

  Proxy Server: 193.113.200.195
  Proxy Port: 8080
  Proxy Username: o2wap
  Proxy Password: password

• WAP access with Cingular, US:
  

  Proxy Server: 66.209.11.32
  Proxy Port: 8080
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

• WAP access with Vodafone, UK:
  

  Proxy Server: 212.183.137.12
  Proxy Port: 8799
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

• WAP access with Orange, Romania:
  

  Proxy Server: 62.217.247.252
  Proxy Port: 8799
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

• WAP access with Vodafone, Romania:
  

  Proxy Server: 193.230.161.231
  Proxy Port: 8080
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

• WAP access with Ancel, Uruguay:
  

  Proxy Server: 200.40.246.2
  Proxy Port: 3128
  Proxy Username: (leave empty)
  Proxy Password: (leave empty)

More proxy configuration details coming soon...