Live data from Hacker News

Remember broken Nexus telephony? This is how Google treats it's customers

code.google.com

61–70 of 114 posts

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#61
post #47

I feel like Android 5 is a step back, UI-wise. One of those "change for the sake of change" things. I don't see how a triangle, square, and circle are more user friendly than a back button, a home button, and a tab button. Chrome is also crashing constantly on 5.03 and the new keyboard is very very bright at night. Not a telephony issue, but I feel like 5.03 was a step back and I've actually contemplated downgrading…

The chrome is very annoying. Constant crash and New Tab takes a few seconds. But the most annoying is tabs are treated like apps.

When I'm on tube and read Effective Go I need to scroll through all apps and tabs to go back to it.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#62
post #6
post #3

This is your second submission of it after https://news.ycombinator.com/item?id=8838578 I agree this may haven't been resolved nicely, but hidden extrapolation from a few employees to the whole company is not cool on your side either. There are people in there, working their butts off to make one of the largest open source projects better.

There is also another employee who marked a disfunctional telephony on a phone as "Priority-small." I think we're seeing a pattern here.

I refer simply to getting angry at the whole company for action of a subset of employees. That's so common today and makes me think I don't ever want to own or work for a large, multi-project company.

I do agree it's by no means a small priority ticket and not one that should be closed without a fix. Although there is a solution mentioned in https://code.google.com/p/android/issues/detail?id=82949#c44... which actually worked for me.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#63
post #6
post #3

This is your second submission of it after https://news.ycombinator.com/item?id=8838578 I agree this may haven't been resolved nicely, but hidden extrapolation from a few employees to the whole company is not cool on your side either. There are people in there, working their butts off to make one of the largest open source projects better.

There is also another employee who marked a disfunctional telephony on a phone as "Priority-small." I think we're seeing a pattern here.

I think they're handling this poorly and that for a company as big and rich as google, "we only have so many people fixing Android 5 bugs." is a pretty weak excuse.

That said, I bet google knows better than we do how many active Nexus 4 users are still out there, my suspicions is - not many.

Here's my guess - they prioritize bugs not just on severity but also based on number of users impacted, and who those users are (in this case, people who are still using a phone that was discontinued over a year ago, have manually updated their phones and then reported a bug in the AOSP tracker. a demographic I suspect is going to be very hard to satisfy no matter what). I'm guessing they hope that people will take this problem to the carrier they bought it from (if they got it from someone besides google), contact google play store customer support (who have always been helpful in my experience), downgrade, or just move on and buy a more recent phone.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#65
post #41
post #23

Of course there are multiple rationales for choosing a platform, but support is certainly one of them. A while ago someone made a nice graph of how good Apple/Google are at maintaining OS support for their devices, it's pretty informative (although I'd like to see a new one). http://www.fidlee.com/android-support-vs-ios-support/ In this case the Nexus 4 is still officially supported by 5.0... but not being able to ca…

My wife has an N4 running 5.0.1 with no issues re calling, so if there is an issue for these users it's an isolated one and not a systemic problem with all N4s. Most of the Android phones on the page you linked are not Google phones. Whether or not they get updated is up to the manufacturers and carriers, not Google. You'll note that the Nexus phones have more update support in general. Whether providing major update…

Ahh, the ol' "works for me". Just because it works for your wife doesn't deem it as a non-problem, as seen by the hundreds of comments on a single bug report in the span of just a couple days.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#66

I'm going to cross the streams a bit here and bring up a major concern going forward. Right now, "Project Ara" is Google's project to create a modular phone that allows hot-swappable components in a totally customizable pocket device. That is, you could have 3 cameras and no wifi in your device if that's how you choose to put it together. How in the hell do we expect the Android OS to actually make this anything but…

They would definitely have to tweak and re-arrange android to work in a more modular system, where software can be built by the manufacturer/on the fly with pre-built components you can put in the software (depending on what module you have in the phone)

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#67
post #21

Earlier quoted context omitted.

Google is "Nexus customer support", they just don't particularly care about doing that job. Google drops support for their own developer phones faster than Samsung and HTC do. E: To address the initial downvoters: why don't you explain yourselves. How is Google not responsible for supporting nexus devices? They're sold directly by Google, they're produced for Google, and they're heavily marketed by Google. Google pro…

Well...the phone itself is over two years old now, which means it's about 18 months out of support if you're equating it with certain other vendors' devices; Nexus phones actually fare better than some other devices. That said, the fact that Google decided to push 5.0 to it is in itself amazing to me, Nexus status or not. I have a Nexus 4 that runs 5.0, and when I've switched to it from my Windows phone I've noticed…

>Well...the phone itself is over two years old now, which means it's about 18 months out of support

That is a horrid mentality being permitted in the phone industry. My "2013" Moto G has a 1.2GHz quad core with a 300+ dpi screen. It's completely unacceptable to declare that device out of support as a consumer technology.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#68

I've the same model (Nexus 4) and can confirm this issue. Can't believe Google's response to this.

My daughter and both have the Nexus 4 and I don't recall ever having this problem. Suppose its a carrier issue? We're on TMobile.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#69
post #42

The difference between android and iOS and windows phone is that android has an open bug tracker, making issues like this a lot more visible. Maybe this issue doesn't affect many people, or google determined that it only happens for phones on a certain carrier and can't disclose that publicly. Sure, the bug could have been closed with a friendlier message, but an open bug tracker seems like a good thing to me

Agreed. JIRA is managed this way as well and it does lead to a lot of anger around 12 year old issues that really should be implemented. However, at least we can see what is going on.

Re: Remember broken Nexus telephony? This is how Google treats it's customers

#70
post #57

Earlier quoted context omitted.

Yes, as far as I'm aware the option to default to NuPlayer system-wide is only present (and default) in 5.x

It's not on by default and it's labeled "Experimental" on my Nexus 5 running stock 5.0.1.

That's interesting. I didn't realize that only some 5.x devices came with it enabled by default. I can only speculate as to why some devices come with it turned on and some don't, but I've definitely supported some Nexus 5 users on 5.x who had it turned on by default - they didn't even have developer options enabled prior to contacting me.
Post reply on HN