riedquat - valueable resource for those who seek.
Home Blog Technical Reports Art Articles RapiDocs Coding Bugs Links Reviews Projects: CherBot Daimonin Gridarta

Cher's personal Android bug list

previous: HTML5 a programming language? - FAIL!
next: First android App: LAN Pinger
twitter button

Android is very very cool, but like all software it has a few bugs.

This is my personal bug list. I use this list to remember and keep track of the bugs that I found. This way I can make sure that I report and help fixing all of these bugs to help to improve and develop Android.

  1. InetAddress.isReachable() methods never do ICMP. (Implementation bug, unsolved, reported as ↗#20106)
  2. InetAddress.isReachable() do not document that their current implementation never does ICMP. (Documentation bug, unsolved, I decided not to report because I rather want this to be fixed instead of documented)
  3. InetAddress.isReachable(NetworkInterface, int, int) only ever returns true for pinging the NetworkInterface's own InetAddress. Reason: InetAddress.isReachableByMultiThread() in its branch for not loopback address (currently line 822) invokes isReachableByTCP() with a wrong order of arguments: addr and InetAddress.this got confused. (Implementation bug, unsolved, reported as ↗#20107)
  4. ProgressDialog lacks a documentation of its threading behavior, especially regarding the proxy method that it offers for ProgressBar. (Documentation bug, unsolved, reported as ↗#20108)
  5. InetAddress forgets to initialize transient field waitReachable upon deserialization. When using InetAddress.isReachable(NetworkInterface, int, int) on deserialized InetAddress instances, several NullPointerException will be thrown. (Implementation bug, unsolved, reported as ↗#20203)
  6. ListActivityView uses the wrong parameter name in method onRestoreInstanceState. (↗#20300)
  7. android.widget.ArrayAdapter lacks documentation regarding write-through on List. (Documentation bug, unsolved, ↗#20311)

BTW: The android community on #android-dev was very helpful to track down the bugs. Thanks go in particular to alankila and tmzt. They are very responsive, helpful and open-minded. Not only did they point me to the source but also discussed the bugs with me. Thank you!

End Of Line
 . 
..: