I don't want to be a nitpick, but it's "its customers". Possessive its (for some reason, the words google, possessive and customers together like that make me feel uncomfortable). Not "Google treat it is customers".
I don't mean to nitpick, but you used the term 'nitpick' incorrectly.
Remember broken Nexus telephony? This is how Google treats it's customers
101–110 of 114 posts
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#102Earlier quoted context omitted.
> If there was a newer Nexus that wasn't the size of an iPad, I'd upgrade; but there isn't. The Nexus 5 isn't that much bigger than the 4, and certainly isn't as big as the Nexus 6. It's also not nearly as expensive as the 6. Size comparison of the 5 and 4 (from the left, respectively): http://newlaunches.com/archives/google-nexus-5-competition-c...
I really like my N5, and i have been enjoying Lollipop as a user experience. I use ADW launcher and keep my device very trim in terms of apps; the only niggling issue currently is that TextSecure does not receive group texts from iTards when WiFi is enabled, but they are aware of the problem so it is a m00t point. It bears consideration that the N5 is not carried by Verison [CDMA].
The Nexus 5 does actually have a CDMA radio and works well on Sprint and its MVNOs. The problem is that Verizon won't list it as an approved device in their database, which means it won't provision for them. From what I understand, it's a control issue, not a technical issue; they can't get carrier exclusivity with an unlocked Nexus phone so they don't want it on their network. In short, the problem is Verizon, not the radio in the phone.
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#103Earlier quoted context omitted.
> but it's clear now that Google not only cannot be depended on for their software (see Google Reader) How about all versions of Android 4.3 and down? 60% of the Android user-base is now without updates for critical security errors. Their support is ridiculous.
I have a Nexus 4 on Lollipop and I was experiencing this issue too, and saw the response. Last night I bought an iPhone.
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#104Earlier quoted context omitted.
I really like my N5, and i have been enjoying Lollipop as a user experience. I use ADW launcher and keep my device very trim in terms of apps; the only niggling issue currently is that TextSecure does not receive group texts from iTards when WiFi is enabled, but they are aware of the problem so it is a m00t point. It bears consideration that the N5 is not carried by Verison [CDMA].
> It bears consideration that the N5 is not carried by Verison [CDMA]. The Nexus 5 does actually have a CDMA radio and works well on Sprint and its MVNOs. The problem is that Verizon won't list it as an approved device in their database, which means it won't provision for them. From what I understand, it's a control issue, not a technical issue; they can't get carrier exclusivity with an unlocked Nexus phone so they…
Seeing as the hardware is there, is it theoretically possible to jigger the channels (technical term) and use an N5 on Verizon?
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#105Earlier quoted context omitted.
Google is well know for their abysmal costumer support, but this is just the last straw; a telephone that cannot make calls, not even emergency 911/112. And such issue is marked as "Priority-small" and dismissed. It was good while it lasted, but it's clear now that Google not only cannot be depended on for their software (see Google Reader), but also cannot be relied on for our hardware needs. At least they have the…
> but it's clear now that Google not only cannot be depended on for their software (see Google Reader) How about all versions of Android 4.3 and down? 60% of the Android user-base is now without updates for critical security errors. Their support is ridiculous.
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#106Earlier quoted context omitted.
I have a Nexus 4 on Lollipop and I was experiencing this issue too, and saw the response. Last night I bought an iPhone.
Good luck with your iOS 8 bluetooth connectivity issues. (other than that, everything seems to work fine)
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#107Earlier quoted context omitted.
let's follow Google's logic. they advertise nexus as being the pure Google Android experience. they own android source. if there's a problem in your nexus software, why isn't it a problem in Google owned pure android code? what could the support guy possibly do other than ask you to reboot and then file a ticket himself in some closed system bug tracking for the engineers? this completely shows that either 1) nexus a…
I don't see why they would bother with the internal dev ticket for a report with so little information. Hopefully they would keep track of how many "audio stops working" reports they were getting, but it doesn't rankle me that they would essentially disregard the first couple dozen (people make stupid complaints).
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#108Earlier quoted context omitted.
You know, that is a valid option. When iPhone 4's telephone broke because of the "grip of death" antenna issue, Steve Jobs himself came out, apologized, offered a free bumper case to mitigate the issue. Compare that to this. And the telco of Nexus is Google! Google just pointed to contact Google.
> And the telco of Nexus is Google! It isn't, Google doesn't run their own mobile network or mobile virtual network ( yet ). Contacting the technical support team of the company that provides you the SIM card that is inserted into the Nexus device will have an effect. I know it seems backwards because the issue has actually been introduced with Google's OTA update but those technical support calls get escalated and e…
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#109Earlier quoted context omitted.
I don't see why they would bother with the internal dev ticket for a report with so little information. Hopefully they would keep track of how many "audio stops working" reports they were getting, but it doesn't rankle me that they would essentially disregard the first couple dozen (people make stupid complaints).
The phone function of your telePHONE is pretty damn important and not something that is _stupid_ to complain about.
Re: Remember broken Nexus telephony? This is how Google treats it's customers
#110Earlier quoted context omitted.
> It bears consideration that the N5 is not carried by Verison [CDMA]. The Nexus 5 does actually have a CDMA radio and works well on Sprint and its MVNOs. The problem is that Verizon won't list it as an approved device in their database, which means it won't provision for them. From what I understand, it's a control issue, not a technical issue; they can't get carrier exclusivity with an unlocked Nexus phone so they…
Thank you for explaining that. I am on Tmobz and their customer service has been exceptional to date (which is why i left Verizon) but i miss the connectivity as i travel in rural areas a fair amount. Seeing as the hardware is there, is it theoretically possible to jigger the channels (technical term) and use an N5 on Verizon?
For extra coverage while traveling, you could order a SIM from Ting[1] (a Sprint MVNO that I've used and really enjoyed), and switch to it for coverage on Sprint's LTE network; they fully support the Nexus 5. It's not as expansive as Verizon's network, but from my experience it tends to fill in the gaps left by T-Mobile. I say that because my service is with Straight Talk on T-Mobile's network, and my wife's phone is on Ting. Everywhere I don't have coverage, she does, and vice versa.
Ting charges a base price of $6 per month per device, then charges for metered usage. My wife uses about 800 MB of data, about 80 minutes of calls, and about 300 texts per month, and her bill comes in at under $40 per month. I won't pretend to know your travel itinerary, but if all you do is order the SIM and activate it once every few months, you're probably looking at less than $70 per year to have the convenience of extra coverage when you need it.
Or, you could forgo all of that and go back to Verizon on a Moto X, it's the closest you'll get to a Nexus device on that network, but then you're back in user-hostile support territory.