This is a program which is developed by Google also to help their developers to evolve in building great apps for the Android platform. A bug is a sort of error, which does not appear on every environment where the files are executed, but only in some of them. For example, there can appear a bug telling you that the speed of the transfer is 1 GB per second, when the bandwidth is of only 100 MB per second. This appears because of the browser, because of the screen type, because of other internal software problems, because a CD is inside the CD-ROM and you did not know about it and so on. The causes are among the most diverse you could ever thing.
I have been amazed to see that I received errors because I had another program opened, which was a music program, and the application gave me headaches. The interesting thing is that I have discovered this later after I have tried all the possible ways to get rid of the bug. And I don’t develop apps for Google. It was just a bug when I wrote a simple code line for a project.
The life of a bug refers to the fact that a new bug is filed as being New. A contributor reviews periodically the bugs that are available in the Open Source Project of the Android platform and selects them so that they are categorized in different classes. The bugs are placed in one of the four sections that follow and they usually switch from the first level to the fourth. The first is New as I said before. The second is Open, then it comes No Action and then Resolved. The bugs that are in the Resolved section will most likely be included in other software releases of the Android, because the bug was tested and re-tested, so that it can be included without any problems into a program.
It would be interesting to see how a bug which is now a piece of code, correct code, will gain some bugs during the execution. So, the bug could generate other bugs. This is a common problem, in fact and the developers know it.11