Exynos

Great performance is a good thing, but less time on the power cord is a better thing

64-bit processing is nothing to sneeze at, but it's also nothing new. The first 3Com PDAs used 64-bit processors. Every Intel Atom processor is 64-bit. I think Casio built an old watch with a 64-bit processor in it as well. It means nothing by itself, and the reason Apple's new Samsung-built A7 performs so well is because it was designed to deliver a particular experience to particular software. There's more to it than the number of bits.

While we're not going to dismiss the benefits of moving hardware and operating systems to 64-bit support, there's something much more important said to be part of Samsung's new Exynos design — a 14nm process.

To put it in simple terms, this refers to the way the processor wafers are built, and it's a measurement of space between components. When you move down to 14nm (nanometers) you do a couple very important things. You decrease the cost, and up the power efficiency. Advanced discussion of FinFET, MOFSET and MuGFET advancements are best left to the forums if you're into that.

When you have a minute hour to spare, ask Phil how he loves his Haswell (22nm) laptop. The 22nm process gives it awesome battery life compared to previous versions. Intel loves to crow about the Haswell, with good reason. They also offer a great example of the benefit of a 14nm process, with tests of their upcoming Broadwell chips being 30 percent more power efficient under the same load

TSMC has released a roadmap showing they are on-board, but Samsung can meet the demand. If these rumors turn out to be true, and Samsung delivers a 64-bit, HMP-ready 14nm Exynos processor, we may get the performance to power ratio we've been waiting for in our mobile devices. 

 
There are 59 comments

VAVA Mk2 says:

Wouldn't that help with battery life?

Posted via Android Central App

UJ95x says:

Yes "more power efficient"

Posted via Android Central App

dannyd86 says:

This market never gets dull.

We obviously need better battery life. We're used to 12-24 hour charge cycles but in reality that's horrible.

Batteries are so far, not innovating fast enough. So use less of the power we already have is the next best thing. Genius

Posted via Android Central App

MERCDROID says:

A 12 to 24-hour charge cycle is horrible? Where should we be at, then?

Posted via Android Central App

intrepid359 says:

At the dawn of time, dumbphones had battery life that could stretch well beyond a week on a single charge. Then humanity fought a brave war against the dinosaurs, but in these dark ages, our advanced battery technology was lost. Now we must suffer through battery life of mere hours or days.

Johnny Z says:

Except that those dumb phones were only used for making calls and texting on a tiny screen in the 10's of kilopixels. Play an album on it and you can kill it in a few hours. Now you have a computer in your pocket. Is that really bad battery life?

Posted via my Nexus 6 running 4.5 Lima Bean

os2baba says:

My Palm Pilot used to run for a month on 2 batteries. That's where we should be at. And at some point in the future we will get there. But at the moment, even a single day charge with heavy use would be great. Unfortunately, the 12 hour charge is really not heavy usage at all.

Johnny Z says:

I'm sure if my smartphone ran at 8MHz and had a monochrome screen (or close to it) I could get a month out of it too.

Posted via my Nexus 6 running 4.5 Lima Bean

dannyd86 says:

Yes smartphone are leaps ahead in power consumption then old dumb phones. That's the point, battery tech hasn't advanced along with it. Not at an equal pace anyways

Why are you defending batteries lol

Posted via Android Central App

Johnny Z says:

I bet if you put my 2530mah battery in the palm pilot it would last twice as long tho!

Posted via my Nexus 6 running 4.5 Lima Bean

dannyd86 says:

I'd prefer not to have to think about it. Isn't that where technology is generally moving. Things that just work. I'm shur companies are dumping huge amounts of money into batteryR&D. Not just for smartphones but for a number of applications. A lot of money to be made for whoever gets the next big move.

Posted via Android Central App

Aaron Watson says:

Great. :)

Posted via Android Central App

ScottJ says:

A smaller process also reduces heat production.

hotbbq says:

Sorta kinda. You are assuming the voltage goes down as well, but that isn't always a given. If the voltage stays the same on a die shrink you have the same heat envelope in a smaller area, this making it harder to cool. See also, Haswell vs Ivy Bridge.

NovaWiz says:

Haswell and Ivy Brdige are both 22nm. Haswell is hotter because its die is larger due to a bigger IGPU.

icebike says:

But the voltage DOES go down. That's the whole point of going to 14.

The chip size is already more than small enough, 14nm isn't going to save significant
space in the package. The whole point is power reduction.

With smaller leads and smaller gaps and smaller printed components (transistors) you simply don't need NOR can you have the same power running on the chip.

ScottJ says:

Bingo.

Qwkslvrmz says:

I love the advancements that are being created for the mobile industry. Excited to see where the next couple years takes us!!

Posted via the AC app on a nexus 4

MERCDROID says:

This.

Posted via Android Central App

s2weden2000 says:

n0

MERCDROID says:

¿Que?

Posted via Android Central App

frettfreak says:

Thats pretty awesome! I dont really care about the 64bit anything on my phone at teh moment. But 14nm i am DOWN!! 14nm and 64bit is cool, but unless KitKat is 64bit it REALLY doesnt matter.

Jlav78 says:

64 bit isn't great. All the 64 bit apps on my laptop lag compared to the 32 bit. I downloaded the android SDK in 32 bit and I've had no issues

Posted via Android central app on my newly-rooted LG Google Nexus 4

icebike says:

64bit can actually be detrimental.

Unless you have a large amount of memory to address, (in excess of 4gig) there really is no NEED for 64bit.

Where it becomes useful is the size of internal registers used to move data around expand to 64bit, but the the load time typically stays the same. So in the time you could load a 4byte (32bit) register, you can also load 8 bytes (64bits), which makes moving stuff around way faster.

90 percent of computer programming is simply moving stuff hither and yon. Read the text file, send it to the screen. Read the music file, pipe it to the audio processor. Read the triangle mesh, send it to the GPU.

For computations 64bit is often slower. Takes more time to add two 64bit registers (in most architectures).

True 64 bit can be a bloatarama, but it can be useful in UD, high RAM, so long as you keep the code tight.

John Nemesh says:

Thank you for that! Most people don't understand that until phones start coming with more than 4GB of RAM, 64 bit does NOTHING for them!

biggbrother2 says:

The top 4 stories are about Samsung yet no news on the Nexus 5. Samsung continues to be the big story within the Android ecosphere. Google has a big problem on its hands.

The Nexus 5 is supposedly the worst kept secret yet not a single leak as to when it will be released. Not even the vaunted Android Central has a mole that deep apparently.

Lasted rumor is Nov. 1...

Posted via Android Central App

MERCDROID says:

Please, take a break, from the Nexus 5 news. How is the advancement of technology a bad thing? For Google, or anyone?

If anything, this is great for Google and the industry, as a whole. A smaller cpu process allows for OEMs to squeeze more energy from smaller mah batteries, which equates to thinner, yet more efficient handsets.

They can't write about what they don't know or are forbidden to.

It will eventually be released, just be patient.

Posted via Android Central App

hotbbq says:

Give me a break, give me break, break me off a piece of that Kit Kat Droid.

MERCDROID says:

Lmao. I want a kitkat, now.

Posted via Android Central App

NoNexus says:

Speaking of that, have you seen any of the wrappers around? I have yet to see them

----------------------------------------------------
My S-Pen went through hell to deliver this important message to you

MERCDROID says:

I haven't, and I'm a little surprised that I haven't. This "campaign" started back in July, didn't it?

Posted via Android Central App

Jlav78 says:

September

Posted via Android central app on my newly-rooted LG Google Nexus 4

_X_ says:

Yes only at 7-11. I was going to save it... but kitkats are one of favorite candy bars :(

Posted via Android Central App

DocToxyn says:

I found them at a rest stop in Pennsylvania. Bought two, plugged one code in and won $5 Google Play credit.

NoNexus says:

Damn I go to 711 all the time and have yet to see one

----------------------------------------------------
My S-Pen went through hell to deliver this important message to you

NoNexus says:

I see you are starting to get to where I have been for a few months

----------------------------------------------------
My S-Pen went through hell to deliver this important message to you

MERCDROID says:

Yeah, it's getting just a little annoying. It's the end of October: honestly, not too much longer to wait.

No offense to anyone; I'm awaiting the Nexus 5, just like many other people. But, I fail to see the reason or "need" to mention it in the comments section of articles that don't pertain to it.

Posted via Android Central App

frettfreak says:

I would agree, somewhat. The BIG problem we are all going to have with Samsung if they are not kept in check is becoming a walled garden like apple. Look at ALL the recent crap from samsung (gear and homesync for example). They are not compatible with android, only with Samsung. Now they have a gaming platform and other new stuff coming out that i bet will only be compatible with Samsung. So, really its not doing anything for Android unless you are willing to go all in on Samsung. Which is CRAP cause they would not be where they are today without ANDROID.

NoNexus says:

In case you hadn't heard, Samsung is having a little get together today and I imagine that is where all the news is coming from. The N5 is vaporware at this point

----------------------------------------------------
My S-Pen went through hell to deliver this important message to you

jwyche007 says:

Evleaks says it's November 1st so you better believe it's November 1st.

He wouldn't throw away his credibility on something like the nexus 5 launch date I assure you.

Posted via Android Central App

icebike says:

And then there will be the top five stories about Nexus, and people will be grousing about all that coverage.

Ya can't win for losing.

TenshiNo says:

There's some speculation that Google could surprise us all and announce it today, at the Samsung Dev Con:

http : / / www . tomshardware . com/news/kitkat-release-date-android-nexus-5,24700.html

NoNexus says:

No way in the world.

That was written for click bait.

No way Google pisses off Samsung like that

----------------------------------------------------
My S-Pen went through hell to deliver this important message to you

AC already said they aren't gonna talk about rumours.

Stop regurgitating what you read in blogs. Samsung isn't a problem for android.

Posted via Android Central App using an LG G2.

jwyche007 says:

Good to see Samsung pushing the envelope. Obviously I would never buy anything with an Exynos processor but this should push Qualcomm to up the anti on their stuff.

It's a win-win for us consumers.

Posted via Android Central App

TenshiNo says:

I promise you that shrinking the die size is every chip manufacturer's goal.

MERCDROID says:

True, but one manufacturer accomplishing it first is great motivation for the others to hastily play catch-up.

Posted via Android Central App

hodan says:

HOLY SHIT! Isn't that what Intel is working on?

Posted via Android Central App

s2weden2000 says:

that's right!

Duncan1982 says:

The great advancements continue to amaze, and its all round beneficial for such processors to continue grow and expand in terms of speed v power consumption. Obviously they are going smaller and means slimmer and sleak design for future smarties, a great time for tech and i like how its progressing.

Just one more thing why on nearly every post is there repeated mentions of the Nexus 5?

Posted via Android Central App

ConTejas says:

Smarties have and always will be a candy ; P That is all...

deltatux says:

Ummm, there's an error in the article, Intel didn't move the Atom for SoCs to 64-bit until Bay Trail. All the Intel Atom SoCs before Bay Trail have been 32-bit processors...

Duncan1982 says:

Con tejas and a kit kat will always be a biscut and jelly bean a sweetie-THAT IS ALLLLL dafty lol

Posted via Android Central App

Give me UD, use that 14nm, in 64 bit, GRAM, to make a Nexus 10 UD, Sammy, you were half way there a year ago. 4X5" FHD = 10" UD and yes Sammy keep on stacking that RAM in, give us 6GB.

ScottJ says:

I hope that makes sense to you.

Hopefully Qualcomm has an equivalent in terms of 64-bit chips. I'd really like Exynos to be in all Samsung model phones, but I don't see it happening again for a while. Unless the big.LITTLE architecture is what caused problems with Samsung's chip supplies this year. I also hope they abandon big.LITTLE. Either go 2-4 A57 cores or don't do it at all. They can do better than just putting in A7's or A53's on the same die to reduce power consumption.

Scots Man says:

In my day it was called MOSFET.... ;)

plunder says:

A friend in the RF development world told me that as the tracks get smaller the possibility of chip damage by cosmic rays increases. He said this IS a design issue for chip selection in flight critical systems in avionics. I don't know what the actual risks to domestic systems running inside an aircraft really are, it could be more of a "theoretical" risk. Also - I have not heard about a raft of bricked phones, tablets and laptops from frequent fliers.

Does anyone else have solid data or actual experience with this issue?

So what laptop is Phil using these days. If you fly a lot, anything that saves weight and extends your battery life is great news.

Awesome A C