Google Promises Fix For 2.5 Year-Old Android Bug

Although it's only affected a small percentage of users, Google has promised to deliver a fix for an Android bug that is two and a half years old.

During the April of 2010, an Android bug was discovered that wouldn't allow a device to resolve a hostname to the correct IP address situated on a local domain. While Google initially didn't receive a considerable amount of complaints pertaining to the bug in question, the original filing on Google's Android issue page attracted increased attention as more and more users started to experience the problem.

The search engine giant has, however, finally promised a fix for the bug. That said, those still experiencing the bug will be disappointed to know that the fix won't be released until the next major version of Android arrives.

"The fix for this has gone in thanks to Kevin Tang. It will be available in the next major release," said a Google employee responding to the thread. "Guys, it was a matter of prioritization and resources. We don't have people to put on every requested feature and we certainly were not idle during this time," the employee said on the long wait. "I apologize it took so long. I can't say what the next version will be (neither know it nor can discuss it) but it will be after 4.2, which has already gone out."

Contact Us for News Tips, Corrections and Feedback           

Create a new thread in the Streaming Video & TVs forum about this subject
This thread is closed for comments
13 comments
    Your comment
    Top Comments
  • otacon72But if this was an issue with an iPhone you'd be slamming Apple left and right...lmao.


    It wouldn't be an issue because Apple would've never announced it.
    21
  • If it were Apple, you'd be "resolving it wrong".
    20
  • And more importantly it will be fixed on new software so if you have an older device you're probably SOL.
    15
  • Other Comments
  • For some things, you just have to put it on the backburner, or risk getting buried by the small details.
    14
  • And more importantly it will be fixed on new software so if you have an older device you're probably SOL.
    15
  • otacon72But if this was an issue with an iPhone you'd be slamming Apple left and right...lmao.


    It wouldn't be an issue because Apple would've never announced it.
    21