Live data from Hacker News

Google broke telephony for many Nexus users

code.google.com

31–40 of 115 posts

Re: Google broke telephony for many Nexus users

#31
post #18

Earlier quoted context omitted.

While both their claims and yours are anecdotes, I'm more willing to side with more people with similar anecdotes than a single one who then uses their single experience to try and invalid the multitude of other experiences expressed.

I don't think they're trying to "invalidate" anything, just state that it's not something everyone is seeing. I have 5.0.1 on a Nexus 4 and it's working fine. I also don't doubt in the slightest that something is screwed up and a lot of people are encountering a serious bug.

No, he was trying to invalidate, or could have chosen his words better. By saying his one experience makes the telephony bug reported by so many users to be "not aa common thing", he has (purposefully or carelessly) stated that his experience outweighs the multitudes who knew enough to go to that site to report the bug, and the folks at XDA who found a fix that works for many.

Re: Google broke telephony for many Nexus users

#32
post #13

I've seen this issue too on my Nexus 4. Rebooting fixes the problem, at least temporarily. Since I had just used the OTA updates for stock 5.0 and 5.0.1, another redditor suggested that I do a factory wipe. I haven't seen the problem recur yet, but it has only been a couple days. Because of this and other problems (random crashes), if I see any issue again, then I'll downgrade to 4.4.4. My typical uptime for that rel…

I probably have a related issue on my android 5.0.1 nexus 7 table.

It's not a phone so I can't test that but I am having a hard time connecting to WiFi manually sometime (for example if I have 2 per-saved WiFi AP's in range and I want to switch from one to the other) and only a restart seems to fix it.

The annoying part is not that it won't switch but it disconnects and refuses to connect to anything until you restart the tablet.

This release of Android is certainly full of bugs.

Re: Google broke telephony for many Nexus users

#33
post #13

I've seen this issue too on my Nexus 4. Rebooting fixes the problem, at least temporarily. Since I had just used the OTA updates for stock 5.0 and 5.0.1, another redditor suggested that I do a factory wipe. I haven't seen the problem recur yet, but it has only been a couple days. Because of this and other problems (random crashes), if I see any issue again, then I'll downgrade to 4.4.4. My typical uptime for that rel…

I have this too, but have not tried a factory wipe yet.

This is quite infuriating, and is the time I have considered moving to an iPhone or other non-Nexus device.

Re: Google broke telephony for many Nexus users

#34
I am looking at getting the Nexus 6 and its threads like this that make me think twice about leaving the iPhone. I prefer android, I love my nexus 7 but issues like this are the reason I left android to get the iPhone 5 from a Droid X2. Now, I thought if getting a Nexus google would support it more because my main issue with the Droid was that it was never updated...but now I am concerned.

Re: Google broke telephony for many Nexus users

#35
post #17

Earlier quoted context omitted.

The full quote should read "Hi, I don't think anyone from google is even looking at this since we have no resolution, upgrading of priority or even an acknowledgement response."

Would be interesting to know how high priority telephony has as a feature.

I'd say very high since technically Android is an OS for smartPHONEs. Note the word "phone."

Re: Google broke telephony for many Nexus users

#36
post #22

Priority-Small An indication that Google no longer considers the phone functionality of a smart phone to be all that important? Or is the Nexus 4 considered too old already? It is a little over 2 years old, which is a relatively long time in the mobile world. I'm curious to know what the cause of this bug is.

It's the default priority for user reported bugs before triaging.

And that causes a lot of consternation to users, obviously.

Priority should be divided into two fields in these systems: user-submitted priority, and dev team's priority. Look at all the people who feel directly insulted by the "Priority-Small" tag - they don't know what it means or if it indicates that Google hasn't triaged it (seriously, this old, and not triaged?) , they just feel minimized and condescended to.

Re: Google broke telephony for many Nexus users

#37

I am looking at getting the Nexus 6 and its threads like this that make me think twice about leaving the iPhone. I prefer android, I love my nexus 7 but issues like this are the reason I left android to get the iPhone 5 from a Droid X2. Now, I thought if getting a Nexus google would support it more because my main issue with the Droid was that it was never updated...but now I am concerned.

Given the complexity of the devices, I suspect any modern phone will come with a number of issues. For iPhones it is almost traditional that one serious issue will be found shortly after launch (like antennagate a ka "you are holding it wrong"). Curiously, the majority of users seems to get by just fine, so maybe some issues are not as big as they seem.

Re: Google broke telephony for many Nexus users

#38

I am looking at getting the Nexus 6 and its threads like this that make me think twice about leaving the iPhone. I prefer android, I love my nexus 7 but issues like this are the reason I left android to get the iPhone 5 from a Droid X2. Now, I thought if getting a Nexus google would support it more because my main issue with the Droid was that it was never updated...but now I am concerned.

The good news at least, is that the Nexus 6 seems unaffected by whatever this is (and may in fact be at the core of this). Nexus 6 shipped with 5.0.1 and I'm not aware of any Nexus 6 owners seeing this problem (when running stock 5.0.1). It's mostly the pre-5.0 android phones that are having this problem when upgraded to 5.0.1, so my guess would be that it either doesn't happen with a stock (from scratch, not upgrade) install of 5.0.1, or else it's some difference between the hardware/firmware in Nexus 6, and every other Android phone.

Re: Google broke telephony for many Nexus users

#39
I work for a telco (I don't speak for them, usual disclaimers apply).

Everyone gets really ranty when operators delay firmware updates. Yeah, some of them delay to force you to buy a new phone, or to stuff the ROM full of bloatware. Most, however, do extensive testing to make sure that customers don't ring up call centres making angry complaints.

Carriers (by and large) test the phone to make sure that the network portion operates correctly. They make sure that it complies with local regulations and that it's not going to interfere with the network. They also test that basic cellular functionality works. Many go further and check all standard operations of the handset.

It's been several years since I was responsible for device testing, but here's a list of problems that I remember from big name manufacturers (Nokia, HTC, Sagem) on their "final" firmware.

- 999/112/911 features not working.

- Reboots when receiving a text starting with a 0.

- Factory reset when receiving an MMS with more than one attachment.

- Inability to switch from 3G to 2G on handover.

- Caller ID always picking the first name from the SIM.

It was, frankly, an unending parade of shoddy workmanship. We'd file reports, wait for an updated firmware, test it again, see that it had more bugs, refuse to ship it.

Frankly, a few "enthusiasts" whining that they don't have a 0.1 firmware upgrade is a sensible price to pay compared to millions of customers storming your shops and demanding refunds.

Google has an atrocious attitude to customer service - it's part of their business model https://shkspr.mobi/blog/2013/02/googles-customer-contempt-c...

Re: Google broke telephony for many Nexus users

#40
This issue also affects users of CyanogenMod 11 which is currently based on Android 4.4.4 (https://jira.cyanogenmod.org/browse/CYAN-5728). The same thing happened to the HTC One M7, but HTC fixed it quickly with an OTA update (http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7). All in all it looks like the malfunction is caused by an automatic update of the Google Play Services framework. Not reacting at all so far is definitively not a good move of Google.
Post reply on HN