4 ms·
Good job cherry picking that ticket! Also right in your comment "first page with 198 stars", let me direct you to the title of this post "Many Android bugs with
by joshstrange 12y ago
Good job cherry picking that ticket! Also right in your comment "first page with 198 stars", let me direct you to the title of this post "Many Android bugs with 500+ stars closed as obsolete on December 25". 198 !>= 500, if YOU ACTUALLY EVEN LOOKED at what these requests are you would see a number of them are VERY relevant:
* iCal .ics support (https://code.google.com/p/android/issues/detail?id=1257 https://code.google.com/p/android/issues/detail?id=1257)
* Phone burning battery while idle (https://code.google.com/p/android/issues/detail?id=22878 https://code.google.com/p/android/issues/detail?id=22878)
* API to access in-call audio (https://code.google.com/p/android/issues/detail?id=2117 https://code.google.com/p/android/issues/detail?id=2117)
* Unable to connect to hidden SSID (https://code.google.com/p/android/issues/detail?id=1041 https://code.google.com/p/android/issues/detail?id=1041)
* Allow longer SMS (https://code.google.com/p/android/issues/detail?id=2318 https://code.google.com/p/android/issues/detail?id=2318)
> If they are still relevant a year later maybe you should go through and do something productive like creating a new issue with updated details.
I wouldn't be surprised at all if the people filing these bugs or replying to them just gave up after waiting multiple years and switched to a custom ROM that does address the issue or even switched OS's.
- bestnameever 12y agoI also wouldn't be surprised if they have switched phones and are no longer experiencing the issue. For instance the phone burning battery while idle was made obsolete over a year ago and no comments have been made in the last year either. Maybe it should be marked as obsolete.
- digi_owl 12y agoSadly the battery issue is painfully generic, and the built in battery UI hopelessly inaccurate. I have experienced that the UI claimed that Play services were eating battery. But when i brought up a good old top report and looked at CPU time i find that Facebook was blocking the CPU from reaching sleep state. killed the Facebook process and the problem went away rapidly. And recently i have seen Plume having a similar issue. I can actually observe the CPU time rising when it is nowhere to be found outside of the top readout (no entry in the task switcher etc). But checking the Android battery readout i see nothing about Plume being a battery hog.
- joshstrange 12y agoI think that's the real problem. A tool designed to help you determine what is chewing up your battery seems to be fundamentally broken and is not being addressed.