With all the changes that have happened in recent months with Google
Maps for your mobile device, we'd like to make sure that we have a
more centralized way to track what bugs people are experiencing. With
that in mind, we're starting this thread, complete with a template
that you can use to report a bug to this group. Your posts will allow
us to collect useful information about the bugs that you're
experiencing.
First and foremost, please make sure to distinguish between a problem
and a bug. We love hearing your feedback on your Google Maps likes
and dislikes, but let's keep this particular thread focused on
features that are broken!
Before you post a bug, remember to check out this thread:
There's a ton of useful information that you might find pretty useful
before you post! There's some guidelines in there that you should
check out to ensure you're not duplicating reports.
And finally, if you've gone through all the steps in that thread and
you're still pretty sure you've found a bug, post your bug report to
this thread using the following template:
1. Google Maps for mobile version:
2. Specific device (Manufacturer, model name, model number):
3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
Windows Mobile 6 Professional, etc):
4. Summary of issue (including error messages):
5. Reproduction Steps/Notes:
6. Desired Results:
7. Workaround (if you've found one):
8. Links to other posts about this issue (please don't repost bugs):
We'll compile the results and make sure all of your information gets
to the right place, even if we can't reply to every post. We
appreciate your feedback and help as we work to improve Google Maps
for your mobile device!
I am an ATT User with a Motorola RAZR2 V9 w/opera mini
I am using google mobile maps version 2.02 #2029
The my location feature only works on the Edge network not on the 3G
network. Since most places are converting to the 3G network is the
Google team working to get it working on the 3G network.
Thanks hope I got all the information for you.
On Mar 3, 11:44 am, Maps Guide Ravi <earth-guide-r...@google.com>
wrote:
> With all the changes that have happened in recent months with Google
> Maps for your mobile device, we'd like to make sure that we have a
> more centralized way to track what bugs people are experiencing. With
> that in mind, we're starting this thread, complete with a template
> that you can use to report a bug to this group. Your posts will allow
> us to collect useful information about the bugs that you're
> experiencing.
> First and foremost, please make sure to distinguish between a problem
> and a bug. We love hearing your feedback on your Google Maps likes
> and dislikes, but let's keep this particular thread focused on
> features that are broken!
> Before you post a bug, remember to check out this thread:
> There's a ton of useful information that you might find pretty useful
> before you post! There's some guidelines in there that you should
> check out to ensure you're not duplicating reports.
> And finally, if you've gone through all the steps in that thread and
> you're still pretty sure you've found a bug, post your bug report to
> this thread using the following template:
> 1. Google Maps for mobile version:
> 2. Specific device (Manufacturer, model name, model number):
> 3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
> Windows Mobile 6 Professional, etc):
> 4. Summary of issue (including error messages):
> 5. Reproduction Steps/Notes:
> 6. Desired Results:
> 7. Workaround (if you've found one):
> 8. Links to other posts about this issue (please don't repost bugs):
> We'll compile the results and make sure all of your information gets
> to the right place, even if we can't reply to every post. We
> appreciate your feedback and help as we work to improve Google Maps
> for your mobile device!
Please note, if you don't fill out the template, I can't collect all
your bug data. It's as simple as that! Asking questions, etc, can be
done in other threads, but PLEASE PLEASE PLEASE try to use the
template to report bugs to us.
Thanks,
Ravi
On Mar 3, 4:54 pm, Kevin619 <Kevin...@gmail.com> wrote:
> I have never been able to get the My Location feature to work (via the
> cell tower data) on my Sprint Treo 700wx.
> No matter where I am or how many times I try, GMM tells me "Your
> current location is temporarily unavailable". Has Google decided to
> not support the Treo? Not support Sprint? Or, is Sprint hiding the
> location data from GMM?
> Kevin
> On Mar 3, 8:44 am, Maps Guide Ravi <earth-guide-r...@google.com>
> wrote:
> > Dear Google Maps Help Group,
> > With all the changes that have happened in recent months with Google
> > Maps for your mobile device, we'd like to make sure that we have a
> > more centralized way to track what bugs people are experiencing. With
> > that in mind, we're starting this thread, complete with a template
> > that you can use to report a bug to this group. Your posts will allow
> > us to collect useful information about the bugs that you're
> > experiencing.
> > First and foremost, please make sure to distinguish between a problem
> > and a bug. We love hearing your feedback on your Google Maps likes
> > and dislikes, but let's keep this particular thread focused on
> > features that are broken!
> > Before you post a bug, remember to check out this thread:
> > There's a ton of useful information that you might find pretty useful
> > before you post! There's some guidelines in there that you should
> > check out to ensure you're not duplicating reports.
> > And finally, if you've gone through all the steps in that thread and
> > you're still pretty sure you've found a bug, post your bug report to
> > this thread using the following template:
> > 1. Google Maps for mobile version:
> > 2. Specific device (Manufacturer, model name, model number):
> > 3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
> > Windows Mobile 6 Professional, etc):
> > 4. Summary of issue (including error messages):
> > 5. Reproduction Steps/Notes:
> > 6. Desired Results:
> > 7. Workaround (if you've found one):
> > 8. Links to other posts about this issue (please don't repost bugs):
> > We'll compile the results and make sure all of your information gets
> > to the right place, even if we can't reply to every post. We
> > appreciate your feedback and help as we work to improve Google Maps
> > for your mobile device!
1. Google Maps for mobile version: 2.0.1.17
2. Specific device (Manufacturer, model name, model number): Samsung
SGH-i620
3. Exact OS: Windows Mobile 6 Standard
4. Summary of issue (including error messages): GPS Position updates
initially, and then no more
5. Reproduction Steps/Notes: Use a Bluetooth GPS device (like
http://www.ascen.com.tw/GPS740.html), connect it to GMM. Wait until
the position is found. Move. Nothing happens to the blue dot, it stays
where you were.
6. Desired Results: GPS Position should update (i.e. move the map to
the place where I am) also when I am moving
7. Workaround (if you've found one): Stop GPS-connection (menu-5),
start GPS-connection. Position updates once.
8. Links to other posts about this issue (please don't repost bugs):
http://groups.google.com/group/Google-Maps-for-mobile/browse_thread/t...
2. Specific device (Manufacturer, model name, model number): HP IPAQ
512 Voice Messenger
3. Exact OS: WM6 Standard (OS version says 5.2 under Assetviewer)
4. Summary of issue (including error messages): My location does not
work. Under 'Help', 'About' it says 'myl:N/A'
5. Reproduction Steps/Notes: Every time. I have tried other software
that tries to get hte MNC/LAC/SID on this phone and none return
anything.
The Processor is a TI OMAP850, Rev ES1.1. Phone is on Vodafone NZ, GSM/
GPRS
6. Desired Results: Make it work!
7. Workaround (if you've found one): None
8. Links to other posts about this issue (please don't repost bugs):
Too many to count!
1. Google Maps for mobile version:
2. Specific device (Manufacturer, model name, model number): Palm Treo
700wx
3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
Windows Mobile 6 Professional, etc): Windows Mobile 5
4. Summary of issue (including error messages): When attempting to use
the "My Location" feature, GMM is unable to estimate my location based
on cell tower info. GMM responds "Your handset doesn't seem to be
compatible with My Location (beta) feature".
5. Reproduction Steps/Notes: See above
6. Desired Results: I'd like to have the "My Location" feature work as
demonstrated in the YouTube video. My phone is a WM5 device and I was
under the impression that "My Location" should work with WM5 devices
7. Workaround (if you've found one): None
8. Links to other posts about this issue (please don't repost bugs):
On Mar 3, 8:44 am, Maps Guide Ravi <earth-guide-r...@google.com>
wrote:
> With all the changes that have happened in recent months with Google
> Maps for your mobile device, we'd like to make sure that we have a
> more centralized way to track what bugs people are experiencing. With
> that in mind, we're starting this thread, complete with a template
> that you can use to report a bug to this group. Your posts will allow
> us to collect useful information about the bugs that you're
> experiencing.
> First and foremost, please make sure to distinguish between a problem
> and a bug. We love hearing your feedback on your Google Maps likes
> and dislikes, but let's keep this particular thread focused on
> features that are broken!
> Before you post a bug, remember to check out this thread:
> There's a ton of useful information that you might find pretty useful
> before you post! There's some guidelines in there that you should
> check out to ensure you're not duplicating reports.
> And finally, if you've gone through all the steps in that thread and
> you're still pretty sure you've found a bug, post your bug report to
> this thread using the following template:
> 1. Google Maps for mobile version:
> 2. Specific device (Manufacturer, model name, model number):
> 3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
> Windows Mobile 6 Professional, etc):
> 4. Summary of issue (including error messages):
> 5. Reproduction Steps/Notes:
> 6. Desired Results:
> 7. Workaround (if you've found one):
> 8. Links to other posts about this issue (please don't repost bugs):
> We'll compile the results and make sure all of your information gets
> to the right place, even if we can't reply to every post. We
> appreciate your feedback and help as we work to improve Google Maps
> for your mobile device!
1. Google Maps for mobile version: 2.0.1.17
2. Specific device (Manufacturer, model name, model number): Moto Q9c
3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
Windows Mobile 6 Professional, etc): Windows Mobile 6 Standard
4. Summary of issue (including error messages): When attempting to use
the "My Location" feature, GMM is unable to estimate my location based
on cell tower info. GMM responds "Your handset doesn't seem to be
compatible with My Location (beta) feature".
5. Reproduction Steps/Notes: See above
6. Desired Results: I'd like to have the "My Location" feature work as
demonstrated on the website. My phone is a WM6 device and I was
under the impression that "My Location" should work with WM6 devices
7. Workaround (if you've found one): None
8. Links to other posts about this issue (please don't repost bugs):
On Mar 4, 1:03 pm, Kevin619 <Kevin...@gmail.com> wrote:
> 1. Google Maps for mobile version:
> 2. Specific device (Manufacturer, model name, model number): Palm Treo
> 700wx
> 3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
> Windows Mobile 6 Professional, etc): Windows Mobile 5
> 4. Summary of issue (including error messages): When attempting to use
> the "My Location" feature, GMM is unable to estimate my location based
> on cell tower info. GMM responds "Your handset doesn't seem to be
> compatible with My Location (beta) feature".
> 5. Reproduction Steps/Notes: See above
> 6. Desired Results: I'd like to have the "My Location" feature work as
> demonstrated in the YouTube video. My phone is a WM5 device and I was
> under the impression that "My Location" should work with WM5 devices
> 7. Workaround (if you've found one): None
> 8. Links to other posts about this issue (please don't repost bugs):
> On Mar 3, 8:44 am, Maps Guide Ravi <earth-guide-r...@google.com>
> wrote:
> > Dear Google Maps Help Group,
> > With all the changes that have happened in recent months with Google
> > Maps for your mobile device, we'd like to make sure that we have a
> > more centralized way to track what bugs people are experiencing. With
> > that in mind, we're starting this thread, complete with a template
> > that you can use to report a bug to this group. Your posts will allow
> > us to collect useful information about the bugs that you're
> > experiencing.
> > First and foremost, please make sure to distinguish between a problem
> > and a bug. We love hearing your feedback on your Google Maps likes
> > and dislikes, but let's keep this particular thread focused on
> > features that are broken!
> > Before you post a bug, remember to check out this thread:
> > There's a ton of useful information that you might find pretty useful
> > before you post! There's some guidelines in there that you should
> > check out to ensure you're not duplicating reports.
> > And finally, if you've gone through all the steps in that thread and
> > you're still pretty sure you've found a bug, post your bug report to
> > this thread using the following template:
> > 1. Google Maps for mobile version:
> > 2. Specific device (Manufacturer, model name, model number):
> > 3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
> > Windows Mobile 6 Professional, etc):
> > 4. Summary of issue (including error messages):
> > 5. Reproduction Steps/Notes:
> > 6. Desired Results:
> > 7. Workaround (if you've found one):
> > 8. Links to other posts about this issue (please don't repost bugs):
> > We'll compile the results and make sure all of your information gets
> > to the right place, even if we can't reply to every post. We
> > appreciate your feedback and help as we work to improve Google Maps
> > for your mobile device!
1. Google Maps for mobile version: 2.0.1.17
2. Specific device (Manufacturer, model name, model number): Moto Q9C
3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
Windows Mobile 6 Professional, etc): WM6 Standard
4. Summary of issue (including error messages): Traffic updates no
longer work. I live in Baltimore and all sections of road are showing
as grey, where they used to work fine.
5. Reproduction Steps/Notes:Just pull up baltimore, at the zoom level
where you can see the 695 beltway. There is no traffic info.
6. Desired Results: To get my traffic updates back :-)
7. Workaround (if you've found one): if I zoom in really close, I can
get the traffic updates to show again. Please help!
8. Links to other posts about this issue (please don't repost bugs):
1. Google Maps for mobile version: 2.0.0.12
2. AT&T Tilt 8925 (manufactured by HTC)
3. Windows Mobile 6 Professional
4. Summary of issue (including error messages): Google Maps quits
forcibly when data connection is lost.
5. Reproduction Steps/Notes: Use Google Maps in an area with sketchy
receptions. As soon as the data connection is lost, Google Maps quits
without giving the choice of trying to reconnect. Even though you
could argue this is a feature request I strongly consider this a bug
as it renders the program non-functional, drastically decreases
usability and causes distraction to the user.
6. Desired Results: High priority: Do not quit but at least allow for
viewing already cached data. Lower priority: Automatically try again
or at least provide option to manually try again. I'm not aware of any
desktop application that shuts down when you pull the network plug so
why should a smartphone application do that? Beside that, Google Maps
is great :-)
7. Workaround (if you've found one): None!
8. Links to other posts about this issue (please don't repost bugs):
1. Google Maps for mobile version: 2.0.5
2. Specific device (Manufacturer, model name, model number): Sony
Ericsson P1i
3. Exact OS (ie. Symbian S60, Symbian UIQ, Windows Mobile 6 Standard,
Windows Mobile 6 Professional, etc): Symbian UIQ 3
4. Summary of issue (including error messages): I have a flatrate for
my data connection but this flatrate works though a special APN which
only accepts HTTP connections to port 80 and 443. The Java version of
Google Maps could download the map material without any problem but I
cannot get a connection with the native UIQ3 app. The app just hangs
on Loading until it asks if I have a data plan (Error: Transaction
error; Zeitüberlauf -33)
5. Reproduction Steps/Notes:
Start app, wait for a while and a message appears which asks if a data
plan is available.
6. Desired Results:
Downloading the map files
7. Workaround (if you've found one):
--
8. Links to other posts about this issue (please don't repost bugs):
