Android issue tracking is in the open, so the numbers are available to anyone:
There have been a bit over 9000 issues reported. about 600 released (fixed and shipped) and 600 for future release. It's hard to characterize all combinations of issue type and status. For example, there are 8 unreproducible enhancements. There are about 3500 new (not yet reviewed) defects. Issues can be "starred" so priority in Android issues is democratic. Of the 64 assigned issues, the only ones that have a "house on fire" number of stars are bugs in the alarm clock. So if your issue isn't getting attention, maybe it's fairly obscure. However there are a couple hundred "New" issues with a significant number of "fans." Plus a couple dozen more highly rated issues that have been reviewed. Again, this is hard to characterize: Are the low-priority assigned issues sitting there waiting for higher priority issues to be cleared? On the whole, the number of high priority unresolved issues looks OK for a system the size of Android, especially with an open and democratic input side for issue tracking. The only qualitative problem I can identify looking at the way the voting system on defects works is that the most user-visible issues get 10X the votes of serious but less visible issues. I think Google's bug reviewers can figure that out. It looks like Google has about 7 people working on bug fixing plus a few other engineers with assigned issues. So it looks like there is no resource imbalance. There might be separate sources of issues, such as OEMs' and carriers' QA processes that might contain issues not visible here, but with the large number of Android users, it is unlikely there is a mass of "hidden" issues. Based on the available numbers, I don't think you can say Android is very buggy. On Jun 6, 5:25 pm, "[email protected]" <[email protected]> wrote: > It seems that Android is very buggy compared not only to the iPhone, > but to pretty much any other software. It's not just minor bugs either > - pretty much every developer will come across many serious bugs. Some > examples: > > - When you run the "sdk setup.exe", the very first thing that happens > is that it informs you that it can't connect using https, so you have > to change the options to use 'http' instead. This appears to be a bug > in the .exe rather than any kind of user issue because the https url > works fine in the browser and this error seems to affect everyone. > Sure, it's trivial to work around (just do a google search and you > figure it out in 5 seconds), but the user shouldn't have to do that. > It makes it look unprofessional. > > - When you view a TabWidget in the layout editor it crashes. > > - Every time you run an app in the emulator, it starts off with the > screen locked so you need to press the Menu key. > > - Various socket bugs (or perhaps all the same bug) related to > IOException not happening. Even something as simple as just trying to > connect to a remote host that is not listening will cause it to hang > instead of immediately returning an error. > > All of these bugs have been logged for months (some by me, some by > other people) with no indication of any fix. > > At the moment I'm just using the emulator, but I'm wondering if the > phones themselves are this buggy or if all the bugs are just in the > development environment and emulator. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
