I'm quite excited about the Pixel 3. Android P looks great, and a device about the same size screen/dimensions as my S8 (which is the perfect size IMO) without curved edges is what I want. I considered the OnePlus 6, but don't really want to go that large. I anxiously await Pixel 3.
If there's one of them I'm leaning towards, it's definitely and only the Pixel 3. Little to no interest in the 3XL.
I just hope the 3 doesn't get pricey or get shorthanded in any way, like if only the XL gets dual cameras on the back or something.
The good thing is, the Pixel 2 XL will be supported until 2020.
With the leaks being underwhelming as it is. I think i’ll stick with my pixel 2xl and not bother upgrading. Maybe i’ll spend money i don’t have on a new iphone 5se.
Read wireless charging may be on it... Although I can't be sure where I'd seen that rumor at
I wonder if they will continue with the 2 year warranty. As others noted, I have zero interest in the 3xl if the 3 has the same specs. I can overlook less ram but not much else.Just as an FYI for those concerned about a singular camera module on the back of the Pixel 3/3XL: the budget iPhone 6.1 model (rumored) may have a singular camera module at the back. Google may be able to get away with one camera module at the back.
I wonder how good Google's quality control gets though? Their blunders were so bad that it led to two year warranties on the 2nd gen Pixel devices.
I wonder if they will continue with the 2 year warranty. As others noted, I have zero interest in the 3xl if the 3 has the same specs. I can overlook less ram but not much else.
Another thing, if you're going to insist on the USB c port as the new 3.5 mm headphone jack, provide some damn USB c earphones.
It's time Google stopped cheapping out. It's not like the Pixels are inexpensive.
Wouldn't consider them notches as the space on either side isn't filled in with static (Status Bar) information that frees up your normal screen real estate like a notch does.And let us boost the volume some! Seriously the headphone volume on these devices are weak.
---
Oh, it's kinda funny, reading about notches and such when I realized that my pixel XL 2 has a shallow notch as well, and on the chin. The notch I'm talking about is the front facing speakers.
As I've noted, not as severe as the renders of the XL 3 and not technically notches, in my book I guess they could be described as such.
New renders.
The imbalanced front panel just screams ugly. That's the issue with the notch trend on Android devices, they almost always mean a bottom bezel/chin that throws the whole design of the front even more out of balance.
Realistically, the iPhone X's surrounding bezels are rather thick, but they're even all around the sides and bottom, and that illusion makes it feel and seem balanced in its own way. Not the case with Android OEMs' notches. The closest to looking remotely balanced is the OnePlus 6.
Google's insistency on keeping front-firing dual speakers is a contributing factor to this ugly design. It's a real shame because it's clearly not the only way -- nor is it the best way -- to do dual speakers.
And to those who argue for the notch because it pushes the notification bar up and to the sides and thus buys you more screen space, I find that argument weak because...
1) It doesn't buy you that much more screen space. Certainly not enough to justify such an offensive and intrusive front panel design. Also, don't full screen apps slide away the notification bar anyway along with the buttons? What will happen in those apps when there is a notch? How does it become "full screen"? It blacks out the split notification bar? Doesn't that end up being the same thing? And...
2) You actually lose screen space for the notification bar itself, which means potentially losing information, like the battery percentage, and less notification icons.
None of that makes a notch worthwhile in the Android world.
Not a big fan of the "fangs" design on the back either:
And I still don't buy that there's not enough room to include a 3.5mm headphone jack. If Google wants to argue that USB-C is a better headphone jack, as they have said in the past, sure, then where is the USB-C earphones included in the box, Google? Why not stand by your decision and help consumers with the transition?
Have you seen the state of USB C headphones? They're all pretty expensive, sadly.
Indeed. Which is why Google's reasoning that the USB-C is the new headphone jack falls flat. The market isn't ready. And their only temporary solution, the dongle, is a nightmare. It's highly unreliable and finicky.
According to some reports, it's more reliable on Android P beta, so maybe it's a software issue?
That's promising. It's been near useless for me and my Pixel 2.
Until the dongle works as effectively as a 3.5mm jack used to or until the market has viable solutions to USB-C headphones, OEMs should keep the 3.5mm jack. Samsung, OnePlus, and others understand this. There's no reason for any OEM to be so far ahead of the curve that it hurts consumers. We have to all keep in mind, this isn't an added feature. It's actually removing a feature. Bluetooth works just fine with or without a 3.5mm jack. That's what frustrates me. It reeks of Google just wanting to push Pixel Bud sales.
And it's all particularly embarrassing for Google considering they made fun of Apple for removing the 3.5mm jack.
That's promising. It's been near useless for me and my Pixel 2.
Until the dongle works as effectively as a 3.5mm jack used to or until the market has viable solutions to USB-C headphones, OEMs should keep the 3.5mm jack. Samsung, OnePlus, and others understand this. There's no reason for any OEM to be so far ahead of the curve that it hurts consumers. We have to all keep in mind, this isn't an added feature. It's actually removing a feature. Bluetooth works just fine with or without a 3.5mm jack. That's what frustrates me. It reeks of Google just wanting to push Pixel Bud sales.
And it's all particularly embarrassing for Google considering they made fun of Apple for removing the 3.5mm jack.
I just had another thought, and it's that I wish somebody would open up the Pixel 2 XL and just take pictures. I wonder what they did with that extra space, or if they just left it empty. I wonder what the real reason is for removing the port. For Apple, it was "bigger taptic engine". For Google?
I just had another thought, and it's that I wish somebody would open up the Pixel 2 XL and just take pictures. I wonder what they did with that extra space, or if they just left it empty. I wonder what the real reason is for removing the port. For Apple, it was "bigger taptic engine". For Google?
^^^^ This^^^^There are teardowns, I believe.
It's a question of design and engineering, if you're asking me. Regardless of what Apple or Google say, Samsung and other makers have found ways to incorporate a headphone jack. In Samsung's case, with full waterproofing, the infinity display, room for a micro SD slot, etc. I'm sure Apple and Google could figure it out. They just don't want to.
There are teardowns, I believe.
It's a question of design and engineering, if you're asking me. Regardless of what Apple or Google say, Samsung and other makers have found ways to incorporate a headphone jack. In Samsung's case, with full waterproofing, the infinity display, room for a micro SD slot, etc. I'm sure Apple and Google could figure it out. They just don't want to.