According to sources ofΒ Fudzilla, the upcoming Pixel 2 will feature a Snapdragon 836, the first phone to do so should this report pan out true. As of right now, Qualcomm has not yet confirmed a release for the Snapdragon 836, but from what this report claims, this bump from the current top-tier Snapdragon 835 would bring about a 10% increase in performance.
Beyond that bump in performance, it is also reported that battery usage improvements will also be made, but without specifics from Qualcomm yet, it’s hard to share much about specs.
Not so shockingly, the SD 836 is reported to not be exclusive to the Pixel 2, but a few other devices will feature it later this year. These reported devices include one from OnePlus and Xiaomi.
While no one would complain about the latest from Qualcomm being included with the new Pixel, it’s not as if the Snapdragon 835 is old news.
// Fudzilla



Xioami and one plus also exclusively will also use the 836???? Can you say one plus 5T? Maybe I shouldn’t order the 5 then .
So if the Pixel 2/2XL will be the first phones with the 836 (and should release in Sept/Oct) then the OnePlus device would be a OnePlus 5T with the 836
Good thing I return op5….
My next phone if has a headphone jack.
I think this is like the only early Nexus/pixel renders that I actually like. 6p leaks looked like garbage but I ended up loving it.
This makes when to buy a phone even more difficult with semi-yearly processor updates.
Keep hearing about battery performance increase and don’t see clear evidence
Yeah because Qualcomm hasn’t even admitted to the 836 existing
My last few trip to droid life, very sad. Maybe there is an 1950sradio-life site.
Just bring the beast already. Don’t know how much longer my N6 has left lol
Snapdragon 836 is a 835. When they make chips and as time goes by they getting better yields usually requiring less power for the same clock.
Could these be the phones that support T-Mobile’s new network upgrades… the longer wavelength RF spectrum?
I saw something yesterday about the 845. Came off of a document in the Apple case. Saying that it is going to come with ARM cores. I sincerely hope that is not the case.
I’ll believe battery usage improvement when I see it. Nexus 6P actual battery failure has really disappointed me.
So it’s kind of like last year? With them having the 821 over the 820. Imo, not a big deal, but this pretty much seals the deal that the phone will once again outshine all other Android phone’s in performance thanks to whatever gains the 836 has over the 835 alongside Google’s crazy software implementation.
> These reported devices include one from OnePlus
This is the important news. OnePlus 5t is coming later this year.
Hopefully with OIS this time
I don’t understand Qualcomm making a second processor again this year. Seems like a waste of money and resources. Just stick with the 835.
I wonder how much of it is just throwing a bone to those mfrs who weren’t able to get 835s in volume b/c of Samsung. Since it’s now 1 higher, then people can have “competition” to Samsung.
It is just a tweaked 835. Not new
You’re really complaining?
Nope, not complaining. Just trying to understand their thought process.
You fools, why would you buy a phone in late 2017 without an SD836?!? Do you not know that 836 is a higher number than 835???
I agree that it would be stupid to make your decision based on such a small thing. However I think the reason these sorts of chips (x+1) is that the manufacturer wants customization and then it gets sold to a few other companies as well to cover the cost and why not. I think the customization something in particular such as better image processing or ai processing. Those two in particular I would guess for this phone. Qualcomm might be putting some 845 optimization in it to test how they are and to make it look better.
Well, it would be dumb to spend the same amount of money if you weren’t getting the latest technology. Thought I’m hoping it’s more than performance. (hardware encode/decode h.265) so you can stream 4K Netflix/Amazon and actual implementation of QC 3.0.
Note that the source article from fudzilla contains no source. This is complete speculation.
Yes, Google…
http://www.gifimagesdownload.com/wp-content/uploads/2016/03/Bring-It-On-gifs.gif
At this point these chip updates are about as interesting as watching paint dry. Every year it is the same thing. Upgrades so small they are hardly worth mentioning.
Just enough changes that Qualcomm justifies no longer releasing drivers for newer versions of android for their older chips in order to force people to upgrade from perfectly-powerful chips.
Doesn’t make me update at all. The chip in a device doesn’t hold much away when I look at a device these days. For the past few years the chips were fine. Heck I was running a 3 year old device that was still as fast as the flagships released this year.
I hear you. For me, though, regular security updates are very important. So QC not releasing updated drivers does force me to upgrade. Although, if I’m being honest, I tend to upgrade once a year anyways. Gotta scratch that itch. (Yes, I’m a statistic here. Ugh.)
I was big into the security updates as well until I started looking at them. Then I noticed they moat of them are bs and will never effect the average person. I also only will use aosp so all of the security updates are there as well as many security updates to the kernel that most device (even flagships) never even see even in the monthly security updates.
Now I focus on bootloader status above all else. If I can’t put aosp on it then I won’t use it. Too much privacy invasion otherwise.
Yeah but that unlocked bootloader/easily-hacked recovery situation is a security problem in itself. I work in an industry-of-interest to foreign state hackers so I’ve resigned to stop the rooting and rom’ing in order to opt for official security patches on a regular basis.
I had one of the early-released Cyanogenmod installs on my G1 – been doing this for a while. I think the Nexus 4 was the last phone I heavily rooted/rom’d – been mostly stock since.
So again, I hear you. I was there several years ago but when the DHS contacts you to say “hey, watch out”, some priorities change. π
I can understand that. All my devices have to be certified for a few places I work. To the point some oem are even banned from being on the property. So I hear ya there.
Even those security patches are a bit behind. Mainly the kernel ones as most devices seldom really see a kernel update.
The biggest issue with security and the unlocked bootloader is someone getting access to the device. Which as long as you are careful and take some precautions then it’s not a worry. An example is i can’t be more then 3 feet from my phone without my headset and watch alerting me. Not that I really need that but an extra step never hurts.
Yup. It’s all about risk assessment. I choose the attack vectors that require a higher level of sophistication than 60 seconds with the device to trivially install keyloggers/backdoors.
The way I figure, if China targets me, I’m hacked no matter what. But they have to target me with real effort and not slipping a $50 to somebody who can get physical access to my phone for a minute to flash something on there real quick in TWRP. I want to at protect myself from the novices as well as the sweeping attacks. In the end, I have nothing interesting enough for China to target me individually.
Lastly, while we have some incredibly talented kernel devs in our community, I’m not sure I trust them when it comes to security (I don’t trust many when it comes to security – I know the limits of when I cannot trust myself). Sure, they may put in some security patches. However, I don’t necessarily believe that they have the experience and training to fully understand some possible vulnerabilities that they’re introducing. This isn’t a dig at anybody – and I appreciate their work and all. But in my mind, it seems it’s at best a lateral shift rather than a substantial improvement. And you still have essentially a wide-open System partition at that point (via recovery & friends).
Don’t take this as judgement or anything else. I’m simply sharing the rationale behind what took me to this conclusion. I believe you understand – mostly sharing for others, honestly. I suspect you know pretty much all of this and there’s no new info for you here. π
Agreed. If a couple try like China or even the US for that matter wants the info on my device they would get it. Part of the reason I am still a paperwork kinda guy. Nothing really important is kept on my device.
The only kernel devs I trust are the ones that keep merged with the upstream Linux kernel from kernel.org. These are the most updated patches made by the lead Linux kernel developers. The ones that have earned the trust. Other then that I only trust myself and normally look over every single commit added. Mind you I also build the OS for my own device. So I know everything that is going into my device.
I do understand this completely. Not taking anything badly. Seldom can one have a conversation from 2 different views and it be a civil one without name calling or the such.
Ahhh, so those are skills I lack. I am a developer but with very different technology and it would take a lot of time to ramp myself up to be able to vet code like this. I can do distributed enterprise cloud architectures and web development all day (well, I *do* do it all day), but not so much OS, kernel, etc. I’d trust myself even less than the more well-known kernel devs in the Android community. π
I too look at unlocked bootloader as my number 1 concern I’ll pay more for a phone that I can do what I want to and has a good development community. And I will upgrade depending on how the community moves so I have the most choices available to me
The community means nothing to me. As just have an unlocked bootloader will not be a sure thing that developers will pick the device up. That I rely on only myself for.
Security updates are almost never dependent on QC updates. They’re usually issues with the OS or libraries, not drivers.
Yes and no. The monthly updates, you’re correct.
The QC updates are more with about kernel-level drivers and those prevent/impede mfr’s from releasing OS-level updates. But with those OS-level updates come additional security improvements as well. I was lumping all of that together in my comments about security – not just the monthly updates.
So you are correct but my vague choice of words mean something slightly different.
Browser speeds and camera load/shot times are the only things noticeably faster between my XL and OPO.
It doesn’t matter to me. When they end support for the 835 the 836 will likely reach EOL at the same time. As for performance, the 821 didn’t seem much better than the 820 (if at all) because they chose to use the same clock.
that red one looks so good
Meh. Don’t care about the soc update, care about the battery size.
I disagree and agree lol Give us the 836 with a massive 4000 mah battery! And take my money!
If the 836 is anything like the 821 it will just be a higher clocked version without much other improvement. The 835 is already a solid chip, a huge battery would make the pixel 2 really enticing.
A 4,000mAh battery? LOL. Good luck with that. I’d be amazed if it was any bigger than last year’s Pixel XL.
s8 with its “modest” battery has been great. I have high hopes for the Pixel
It hasn’t sucked… But I want Z Play level battery life.
Sad thing is the S8+ now gets more battery life than the Z play 2
The S8+ gets 8+ hours of SoT in a charge? Doubt it.
Yeah I get 8+ screen on time on my s8+.
Pics or shens.
https://uploads.disquscdn.com/images/08c128c404b9d4c92ffe1e9a6e9fb1894f063c81c4a73f0a245025f276e7798d.png
Need another to show the battery graph with no charging points within that time period.
https://uploads.disquscdn.com/images/60bd7a5d900c76a836cff1d00f2c45318b486002d3315b133aa3fdfc72d26f0f.png
8+ hours consistent. Never experienced once any random battery bugs. Unlike so many other phones.
Looks like you just left the screen on without actually using the phone for anything with device idle and Android system/OS right behind the screen there.
I get 8+ hours daily on the phone. I use it alot for work too. I can tell you this. It gets about double the screen on time from when I had a nexus 6p without any heat and emitting 300% less radiation.
Well that’s good to know that you can get 8+ hours of SoT when you’re not actively using the phone. I might see what my wife’s Z Play will get by leaving the screen on overnight on a static screen to see how it compares. Considering it gets 10+ hours while activity using it (streaming YouTube/Facebook vids, browsing, reading eBooks,etc.), I have a feeling it will take most of the next day after 16+ hours to actually kill it like that. Subtract the 15% battery capacity the Z2 Play lost from the Z Play and that should be what it gets too since its specs are pretty much identical otherwise.
The screen on times are full use of the phone regularly not just trying for some high time. The z play is a battery champ but the z2 play is “normal” for a snapdragon 625/626 (which are the s8’s weak cores a53 running all the time).
I’ll agree, My S8+ gets great battery life.
https://uploads.disquscdn.com/images/6be660d2280b858036a442b45aff8383a093b717d694c1eac5d6a6577d898a96.png
My S7 Edge got 7 hours or so. best phone battery I’ve used in a long time on Android.
Wow. We have a very different idea of what great means when it comes to battery life. The battery life of the S8 isn’t anywhere near what I would call “great”.
Battery life is really a matter of use. I can easily kill any battery no matter how big in about 4 hours. With almost minor use. How strong your signal is makes a big difference. The real strength and not the bars the carrier shows you which are almost never real.
That is the problem.. The snapdragon 835 has a huge battery advantage from last generations 821 but in response all the oems decreased battery size to make more profit.
If the pixel 2 XL is made by LG, I’m going to have a hard time telling myself it’s ok to buy LG hardware. I just need something soon because this 6P of mine is on its last legs.
Yup. Love my 5X (am I the only one?), but after dealing with a bootloop, I can’t see spending top dollar on an LG.
If you can buy it from the Google Store, then I’d be less worried. They have been *very good* at supporting their customers, even with out-of-warranty devices.
I just had a very good experience with them where I had a Pixel with a spontaneous LCD crack (it was literally just sitting on the dining room table, good one second, cracked 5 minutes later when picked up) that they treated as a “defect” rather than “damage”. The only odd thing was that there was no glass crack, just an LCD crack beneath the glass. I had already set expectations that they’d let me know how many hundreds of dollars it would take to fix it but instead they offered to send a new (refurbished) phone to me free of charge.
I had another experience after I bought my Pixel. I sold my N6P & my wife’s N5X on Swappa and within two months, the buyer started getting bootloops on both (about a month apart). Even though both were out of warranty, Google even replaced both phones for that person after contacting me to make sure it was okay by me (i.e. not stolen phones).
They really do bend over backwards to help their customers, so that would alleviate any of those LG concerns for me. *IF* you can buy from the Google Store. Seriously, I wouldn’t consider buying anywhere else, even if it was $50 cheaper.
You might be. That phone is pretty bad. Only phone I ever owned that vibrated my arm, from fingertips to elbow, when having the volume turned up. For those that haven’t heard a 5x… it isn’t loud, clear, crisp, or anything like that. It’s just a crappy speaker stuck in with zero thought behind build quality. Kinda like the rest of the phone.
So if you buy a Pixel 2 XL and it’s like that, you should obviously return it and get your money back. This is a very convenient process at most places. If you think it’s that bad, don’t keep it. Simple as that.
Our experience with a N5X was much better, though we kept ours in a fairly tough case.
My 6P is like new again after I replaced its battery due to the early shutdown issue. I can see myself using it for another year at least if I need to. I’m looking at the Z2 Force though if it comes to T-Mo.
Pixel always get the slightly updated processor like Snapdragon 821
You’re basing it “always” happening off of it happening… 1 time?
????????????
Is he lying though?? π
well, guess they kind of did it with the 6P. Used the SD810 v2.1
Nexus 5 was first with 800, Nexus 6 first with 805, 6P had 810 v 2.1
Those arent Pixels
Pixel is the spiritual successor to the Nexus line
It’s happened with literally EVERY Pixel so far
still doesn’t justify the use of the word always
Oh, I know, I was literally joking
Please make that front grill a speaker, please make that front grill a speaker…
I second this plea!
In reviewing the Z2 Play, I found it to be a MUCH better implementation for a speaker than a bottom firing jobby. Way nicer to use and listen to audio that way.
iPhone 7+ with stereo sound is great. Too bad Samsung didn’t do it with the S8.
I’ve found the Samsung speakers in their mobile offerings (Galaxy Nexus, 2012 Nexus 10 and 2013 Nexus 7) to be anemic at best. My OG Droid, OG Moto X and 2015 Moto XPE all had good sounding and LOUD speakers in them by comparison.
Definitely one of the things I miss most about my Nexus 6P.
So true. It’s actually the ONLY thing I think is better about the 6P. I absolutely love my pixel, but I’m always reminded how much I miss the dual front facing speakers from my wife’s 6P. I really thought it’d be a no-brainer for Google….give us back our front facing speakers!!!
I wouldn’t mind if it was dual side firing speakers not a bad compromise
Kys
If the 2016 HTC 10 could do it, and the 2017 HTC U11 did it (with improvements to boot) along with a bottom firing speaker…there’s really no excuse. Like, no excuse other than they just didn’t want to spend the extra time and money implementing it.