Bugs? Gripes? Use Google's official bug tracking site (list inside)

[virtus]

So most of us are happy with our Droids, but we all have at least one item that we just wish Google would fix. Lucky for us, Google has a site dedicated to tracking bugs, issues, and feature requests!

So in addition posting questions here, go to Google's issues site and let them know directly! All you need to do is click the link and click the little white star icon. Issues with more stars will theoretically get more attention, so let's let Google know what we want.

I'll keep a running list of direct links in this post for everyone's convenience. If you want me to add more just post it in this thread along with a link to the issue.

Bluetooth Voice Dial Support
Exchange support for Global Address List
Exchange support for ActiveSync provisioning protocol
Exchange support for signatures
Exchange Calendar Appointment Invites have no accept or decline buttons
When headset is unplugged, sound does not return to speaker.
Issue 5853: Softbuttons lights on the Droid stay on while charging
Feature request: add support for GSM 6.10 8Khz/mono in a RIFF WAVE audio container
Issue 1151 Install apps to SD card
Issue 1181 [VoiceDial] Voice confirmation for Voice Dialer
Issue 3795 Couldn't unlock phone after "too many pattern attempts"

If any of these issues bother you, please take a moment to click the link and click on the white star to let Google know that it's important! Leave a comment for the devs while you're at it.

There are currently over 400 issues posted and you can add your own. This list is just for quick and easy reference for common issues among the readers of this forum.

Also, note - this is for issues with Android as a whole and not necessarily Motorola or Verizon.

 

[gonzoguy24]

Nice post. It is very clever of you to remind these people there is a place to have your voice heard

 

[Redflea]

So most of us are happy with our Droids, but we all have at least one item that we just wish Google would fix. Lucky for us, Google has a site dedicated to tracking bugs, issues, and feature requests!

So in addition posting questions here, go to Google's issues site and let them know directly! All you need to do is click the link and click the little white star icon. Issues with more stars will theoretically get more attention, so let's let Google know what we want.

I'll keep a running list of direct links in this post for everyone's convenience. If you want me to add more just post it in this thread along with a link to the issue.

Bluetooth Voice Dial Support
Exchange support for Global Address List
Exchange support for ActiveSync provisioning protocol
Exchange support for signatures
Exchange Calendar Appointment Invites have no accept or decline buttons
When headset is unplugged, sound does not return to speaker.

If any of these issues bother you, please take a moment to click the link and click on the white star to let Google know that it's important! Leave a comment for the devs while you're at it.

Also, note - this is for issues with Android as a whole and not necessarily Motorola or Verizon.

I've starred all these issues quite a while ago, and agree we should "voice" our desire to get these fixed...but it's pretty frustrating to see them ignored in 2.01 and seemingly unaddressed in 2.1.

Assuming 2.1 comes out for us with similar core features to the N1 release, and none of these issues are addressed, I get concerned regarding how Google is prioritizing things...they appear much more interested in flashy UI (animated wallpapers) and cool widgets (admittedly, I do love the News widget) than dealing with basic functionality issues like above. Makes me sad...

 

[virtus]

I've starred all these issues quite a while ago, and agree we should "voice" our desire to get these fixed...but it's pretty frustrating to see them ignored in 2.01 and seemingly unaddressed in 2.1.

Assuming 2.1 comes out for us with similar core features to the N1 release, and none of these issues are addressed, I get concerned regarding how Google is prioritizing things...they appear much more interested in flashy UI (animated wallpapers) and cool widgets (admittedly, I do love the News widget) than dealing with basic functionality issues like above. Makes me sad...

That's exactly why we need to use their own issue tracking site to tell them what is important.

BTW, it's nice to see that the status on the Exchange Signature issue has been changed from "Reviewed" to "Assigned"!

 

[messenger13]

Issue 5853: Softbuttons lights on the Droid stay on while charging

 

[alostpacket]

I've starred all these issues quite a while ago, and agree we should "voice" our desire to get these fixed...but it's pretty frustrating to see them ignored in 2.01 and seemingly unaddressed in 2.1.

Assuming 2.1 comes out for us with similar core features to the N1 release, and none of these issues are addressed, I get concerned regarding how Google is prioritizing things...they appear much more interested in flashy UI (animated wallpapers) and cool widgets (admittedly, I do love the News widget) than dealing with basic functionality issues like above. Makes me sad...

Why is this always the criticism? You really think the guys who fix exchange issues are the same coders making the liquid wallpaper? I can assure you they aren't.

They did fix that serious browser scrolling slow bug at least. But I'm sure they are working on exchange issues.

I understand your frustration in it taking awhile however.

 

[alostpacket]

You know I also wonder if this may be a little bit due to google free project choice culture. If I were a google engineer I wouldnt really want to work on exchange issues either.

 

[welterbf123]

While in navigation mode, I can recieve calls and when the call is done, it resumes navigation mode. But if I want to make a call, I have to exit navigation mode then reestablish a new map when the call is through. There should be a way to put navigation mode in the background and then resume it when the call is done.

 

[virtus]

While in navigation mode, I can recieve calls and when the call is done, it resumes navigation mode. But if I want to make a call, I have to exit navigation mode then reestablish a new map when the call is through. There should be a way to put navigation mode in the background and then resume it when the call is done.

There is a way. The droid can multitask so all you need to do is hit the Home button while you are navigating (no need to exit). Then select the phone or contacts app and you are good to go. Navigation will continue to run in the background. I do it all the time.

 

[welterbf123]

Hmmm....I must be doing something wrong then, because everytime I try it I have to reestablish my map. I'll have to take a closer look.

 

[YankeeDudeL]

Issue 1151 Install apps to SD card

 

[virtus]

If you are on a call too long and deviate from the route, the navigation could fail since the data link is broken while you are in a call.

Let's keep this on topic:
Feature request: add support for GSM 6.10 8Khz/mono in a RIFF WAVE audio container

 

[virtus]

Added Issue 1181 [VoiceDial] Voice confirmation for Voice Dialer per this thread.

 

[virtus]

Added Issue 3795 Couldn't unlock phone after "too many pattern attempts" per this thread

 

[drathos]

While I think this thread is a good thing, I have to point out a problem with it.

If any of these issues bother you, please take a moment to click the link and click on the white star to let Google know that it's important! Leave a comment for the devs while you're at it.

The only comments you should leave are off the constructive variety. DO NOT leave a "me too!" type of comment. Several issues that I've starred have been losing stars because of people doing that. Every time you leave a comment, it emails everyone who has starred the issue.

Unless you have something constructive to say, star the issue and do nothing else.

Quite frankly, I'm not sure how much Googlers actually pay attention to those issues anyway. One of the issues I starred was for a night mode in navigation. While it did get added in to version 3.4 of Maps, the issue is still marked as New and never even got assigned.