Ok well that's something. Now that they've assumed responsibility. Where's the fix? Come on GoogleGoogle sent me an email to follow-up on my call to support. Pretty much said 7.1 is the problem. It went on to say developers only got 7.1 the day before pixel was released. I'm lost.
Maybe sticking with Android is a better choice than going into Google products. A company of this size should have a fix pretty damn quick.So it looks to be an issue of Google not having enough time to test everything thoroughly and completely. Kind of a case of "Will worry about it and deal with it later" or as issues arise
So it looks to be an issue of Google not having enough time to test everything thoroughly and completely. Kind of a case of "Will worry about it and deal with it later" or as issues arise
I guess just unexpected from Google.This is now the (industry) norm. Release first. Patch later.
Android is GoogleOk well that's something. Now that they've assumed responsibility. Where's the fix? Come on Google
Maybe sticking with Android is a better choice than going into Google products. A company of this size should have a fix pretty damn quick.
I'm highly aware that Android is Google. This is the first device released by Google. Sticking with Android while using a device other than a Google device sounds like a better idea than the pixel to me.Android is Google.
Also.. If anything Google can release the patch faster than a carrier branded phone would be. Not always since there are exceptions to the rule but usually carrier branded phones take awhile to update.
Married here as well. 2 kids. I don't work near home so I absolutely NEED my device to work as the intended phone when I need it. It really pisses me off when I call my wife and the call drops. Finally connect and then drops again. Its so damn frustratingI will be honest. I mostly can't stand talking to people. I am married, I have a absentminded 12 yo son(I know what 12 yo has his or her wits) and carry a phone for work. Having said that, some part of me likes having the signal issues. Another reason to get off the phone or not answer.
I, of course, dont want to spend this kind of money on something for it to not work. So maybe I get the new one at christmas and even though its fixed I still get to hang up on people and just say" oh well, must have been that darn pixel phone"
Almost as important to me in getting a new phone that works is maybe getting one that doesn't make that rattle, that most seem to be ok with. Honestly to me this is more important then the signal and I know there would be little chance I would get a replacement for that.
I'm highly aware that Android is Google. This is the first device released by Google. Sticking with Android while using a device other than a Google device sounds like a better idea than the pixel to me.
I have given up on my pixel xl for now. I switched back to my Nexus 6 made by Motorola, awsome connection. Google definitely needs to take lessons from Motorola. I'm not a Motorola fan, but I am a fan of their patented radio/antenna setup.
I had a z force. Gave it up for the pixel. I didn't have any dropped calls using that device. Held a signal at home too.I had three pixels,all couldn't hold a call at my house.I bought a Motorola Z Play from Motorola no more doped calls.
Verizon network is not the same everywhere. Different vendors supply network equipment for different regions and settings can be different even on two towers next to each other.Makes no sense that this would be carrier related and would make Google look like total fools having a phone that was basically released on Verizon with all the commercials and what not to have a phone that they are pushing that doesn't even work on their network. I am blaming software. I lived at my present location and in the same area for many years and have been with Verizon for 12 years. Never had any issues with connectivity in the past. To go from having 3-4 bars constant on all my previous phones to having 1 bar that drops down to none with this phone. I totally blame it on software. IMHO