Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Many Android bugs with 500+ stars closed as obsolete on December 25

code.google.com

Post reply on HN
Print view View original

101–110 of 201 posts

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#101

Post by zmmmmm »

diafygi wrote: post #28
krschultz wrote: post #22

At some point in a long living project, you have to declare some bugs are #wontfix. You are just lieing to yourself if you think you will ever get to the end of the bug backlog. It also can become an anchor, the team is focused solely on fixing bugs here and there instead of moving the ball forward (and hopefully fixing more fundamental problems along the way). I've made the call to mass close tickets like this. It's…

Then mark them as WontFix with a comment explaining why. Marking Obsolete without comment and restricting further comments is a huge slap in the face to your biggest supporters (those who went through the trouble of trying to contribute positively by filing/commenting/starring the bug).

But it's explicitly not a WontFix.

It's a "we're sorry, for whatever reason this issue is not getting traction. We are closing it because whatever the issue or reason is, whether it's on our side or the reporter's side, or something else, this problem is not effectively handled by this issue".

Closing as WontFix would inspire a thousand proclamations of "Google is never going to fix X!" when they may very well address it in the future.

I don't think what Google's done is ideal, I agree they should add a comment. However "Obsolete" is probably better than WontFix unless they really did analyse the problem and explicitly decide not to fix it.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#102

Post by kyrra »

umustbjoking wrote: post #70
jspaetzel wrote: post #37

I'm not sure if you guys actually even looked at what these requests were but most of them are irrelevant and rightly so... obsolete/irrelevant features. To choose one particular example that stood out to me from the first page with 198 stars: https://code.google.com/p/android/issues/detail?id=1140 I wont even get started on how much information this is lacking for it to be actually executed. The point being that mos…

Why look so far down the list? https://code.google.com/p/android/issues/detail?id=82 Bug 82. Number one on the list. Been open 6 years. Patch offered and integrated into CyanogenMod for years. Y u no integrate the patch Google?

There could be patent issues behind preventing it? Maybe telecom companies telling Google not to implement it.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#103

Post by e28eta »

duskwuff wrote: post #69
tehwalrus wrote: post #46

Earlier quoted context omitted.

There have only been two apple charging interfaces for iPods, iPhones and iPads (excluding the shuffle), and the new one was necessary (if I understood correctly) to take advantage of faster USB3 data transfer rates.

Lightning doesn't currently support USB3, unfortunately. It did get rid of a lot of obsolete old interfaces that were present in the 30-pin dock connector pinout, though, and opened up possibilities for new devices (like the HDMI adapter).

FYI, the HDMI adapter existed for 30-pin devices too, so that's not a good example.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#104

Post by fpgeek »

ljf wrote: post #66
Mikeb85 wrote: post #62

Earlier quoted context omitted.

Yup. I had 1 iPhone, my first and last Apple product. My mom just got an iPad mini, was infuriated when she discovered she can't buy Kindle books from the Kindle app like she could on Android. The artificial restrictions Apple places on developers and users are ridiculous. And Android 5 is the first release where I can say that Android is unequivocally a nicer experience than iOS...

Just so you know, you can't buy kindle books from the Android app anymore either - main reason I use Aldiko to read epub now. Agreed about Android 5 though, best yet!

Say what now? I just opened my Kindle app and the store hasn't gone anywhere.

Are you maybe thinking of Google blocking Amazon from including the Amazon Appstore in the Amazon shopping app? That's a different issue and, more importantly, that doesn't really affect what's possible on Android, just how convenient it is. After all, anyone who wants to can download the store Google blocked from Amazon directly.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#105

Post by e28eta »

cpncrunch wrote: post #98
arthursilva wrote: post #10

Android dev is smelly, even if you target 4.0+. Any mid sized app need several workarounds/hacks in order to work properly.

We target 2.3/3.0 and have required very few workarounds/hacks. iOS is a hell of a lot worse - there are various bugs either introduced or "fixed" (requiring a workaround) in each release.

We may be writing very different kinds of iOS apps, but most of our SDK upgrade problems stem from (often accidental) misuse of Apple's APIs, or a documented change that Apple made.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#106

Post by [deleted] »

ksk wrote: post #48
titaniumdecoy wrote: post #21

Earlier quoted context omitted.

This is a common but completely unfair criticism of Apple. Plenty of people complained when iOS 7 was made available for the iPhone 4 (because the hardware was too slow to run it properly). And Apple still sells and supports relatively ancient hardware (the iPad mini) as a result of their current strategy of selling last year's model as the second-best option.

The reason people complain is because iOS updates are a horrible kind of bait and switch. You update the OS because you think its awesome, but are unable to downgrade when you find that in reality, its slow and bloated. The most infuriating thing in all of this is that my iPhone 4S is STILL a fast device. The CPU hasn't shrunk since the time I bought it. Apple has decided that I am unworthy of restoring my phone to t…

[deleted]

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#107

Post by joshstrange »

jspaetzel wrote: post #37

I'm not sure if you guys actually even looked at what these requests were but most of them are irrelevant and rightly so... obsolete/irrelevant features. To choose one particular example that stood out to me from the first page with 198 stars: https://code.google.com/p/android/issues/detail?id=1140 I wont even get started on how much information this is lacking for it to be actually executed. The point being that mos…

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)

* Phone burning battery while idle (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)

* Unable to connect to hidden SSID (https://code.google.com/p/android/issues/detail?id=1041)

* Allow longer SMS (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.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#108

Post by shortstuffsushi »

sarciszewski wrote: post #57
shortstuffsushi wrote: post #47

Earlier quoted context omitted.

If you guys are really interested, the profile you linked has a list of projects. Glancing at the "vogar" project which it says is owned by e...@google.com (first I happened to pick), you can see links to the blog of Elliott Hughes. His site indicates he's a Google employee. So, not exactly proven, but seems to fit the bill.

Except Ellion Hughes shows up elsewhere as elliot...@google.com https://code.google.com/p/enh/

True, and as I said, my single link research is by no means proof, just the nearest I could find that seemed to make sense.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#109

Post by ben1040 »

chambo622 wrote: post #42
sangnoir wrote: post #32

Earlier quoted context omitted.

I have a Galaxy Nexus (2011) that's stuck on 4.2. I wouldn't mind receiving bug-fix releases.

Small correction, the GNex was updated through 4.3.

The poster may have had the Verizon model; it never got 4.3. They just abandoned it at 4.2.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#110

Post by sambe »

Bud wrote: post #85
ksk wrote: post #48

Earlier quoted context omitted.

The reason people complain is because iOS updates are a horrible kind of bait and switch. You update the OS because you think its awesome, but are unable to downgrade when you find that in reality, its slow and bloated. The most infuriating thing in all of this is that my iPhone 4S is STILL a fast device. The CPU hasn't shrunk since the time I bought it. Apple has decided that I am unworthy of restoring my phone to t…

Most of the criticisms of brand-new OS updates being "slow and bloated" are from extremely impatient users (or professional clickbait critics) who don't even have the good sense to wait a few hours or a day or two for the processes that can make major upgrades a bit sluggish on ALL devices to complete, such as rebuilding databases, the fact that OS updates often result in dozens or even hundreds of app updates that h…

I'm sorry but this is simply untrue. Every time I have hardware 1-1.5 generations behind (which is not always, I've done it both ways) the OS upgrade makes it somewhere between noticeably slower and painfully slow. I've recently used an identical model side-by-side that was not upgraded and it is vastly snappier. this has nothing to do with waiting for x.0.1 or app updates. In this case we are talking about iOS 7 on 4S, I'm refusing the iOS 8 upgrade for obvious reasons. I've seen others have similar problems in previous iterations whilst my newer hardware was fine.

People are fond of overstating Apple problems and I'm grateful that the opportunity to upgrade exists at all. However it is a fact that it often destroys the performance so the ability to revert seems very reasonable. I also find the extent of the degradation puzzling.

Post reply on HN