Why 64-bit processors really matter for Android

It's not really about the bits, but the new ARM-based processors will make a difference

One of the biggest buzzwords of 2014 when it comes to mobile hardware is "64-bit." It gets thrown around like some sort of magic that makes everything about your smartphone or tablet better. It has to be better, because 64 is more than 32, right?

The fact is, that while 64-bit processing has both advantages and drawbacks when used in something like a smartphone, the hardware that supports it can make a major difference because of other new manufacturing processes. While using these new chips is also a bit of future-proofing as Android itself and third-party software moves towards 64-bit, the tangible and more important changes come with the new ARMv8 chip architecture.

There's plenty out there for folks who love to pore over white papers and look at diagrams and flowcharts, but for the rest of us — who really only care that these new 64-bit processors are better — things get more confusing. We love to get technical sometimes, but I think we can break things down for the folks who just want an overview without talking about registers and SMID and bandwidth.

Let's do that.

ARM Cortex

For starters, we're talking about chips based on the new ARM AArch64 architecture. Other companies, like Intel, have developed their own 64-bit architecture for use in smartphones, but most companies will license ARM's spec for their chip design. Some, like NVIDIA or Qualcomm for example, will expand on ARM technology with some of their own IP to make their design even better. In any case, this new architecture, whether it's only the ARM spec or it includes other proprietary changes, will do two things — optimize for performance and use less battery to do the things we want our mobile devices to do.

When you get to the nitty gritty, that's what all the latest advancement in mobile CPUs are about. We have more then enough raw power to do anything we need to do on a mobile device, so we need to optimize it and make it more battery friendly. New features are always great, and for sure we'll see them used in the near future, but what we want is for our phones and tablets do do things better and use less juice while doing them.

new chips can do the things we want our mobile devices to do

The thing is, it's not necessarily the move to a 64-bit architecture that allows for the improvements we want. Yes, 64-bit is a big part of the future of mobile hardware and applications, but with the majority of user-software still 32-bit, the new chip features aren't being used. In fact, these apps don't even "see" the new features because they weren't coded for any of them. And for heaven's sake — stop saying the big deal about 64-bit hardware is the ability to use more than 4GB of RAM. That's just one of the more minor features of the architecture, and pales when compared to things like the ability to fetch more data per cycle — which will allow for things like TouchWiz to be as "fast" as AOSP. For reals.

stop saying the big deal about 64-bit hardware is the ability to use more than 4GB of RAM

The really big deal, which Alex and I wandered into in a recent episode of the Android Central Podcast, it the move to ARMv8 on these 64-bit chips. I reached out to NVIDIA — a company pretty familiar with 64-bit ARM processors and rumored to be the Android L launch partner — and this is what they had to say when I asked why the new 64-bit chips are important to Android:

Nearly all mainstream and high-end consumer notebook and desktop CPUs transitioned to 64-bit many years ago, and for good reason-- they afford higher performance for applications coded to use the 64-bit features, and larger memory addressing for the operating system and multiple applications.

For Android, the story is not simply 64-bit, but really more about the new ARMv8 Architecture. In addition to enabling 64-bit applications, ARMv8 brings a host of improvements in power efficiency as well as performance that have a direct and significant impact on nearly every 32-bit Android application in the market today.

Google announced at this year's I/O conference that the next version of Android – "L" - will offer 64-bit CPU support. In fact, NVIDIA is already developing L on our 64-bit Tegra K1 mobile processor, which includes our custom-designed Denver CPU.

Denver is an amazing CPU - and the first 64-bit CPU for Android. It completely outpaces the other ARM mobile offerings. Each Denver core is a 7-way superscalar processor internally– rather than 3-way seen in many ARM-based chips - and with much larger caches. Denver is the highest performance mobile ARM CPU ever created – it's designed for the highest single CPU throughput and will be coming to devices later this year."

Nick Stam, Director of Technical Marketing at NVIDIA


And it's not just NVIDIA that will be building chips that have the potential to rock our socks off. ARM has two processors that use the v8 spec — the Cortex-A53 and the Cortex-A57. These are pre-built processors, and can be used as-is in any SoC from any manufacturer. While NVIDIA and Qualcomm and Samsung will be building the spec out into something more — and potentially better — other companies can drop these right in and enjoy the benefit. That means we can enjoy the benefit, too. With companies like Huawei building their own chips now, or OEM's using MediaTek SoCs, even the entry-level smartphone will benefit from the move to ARMv8.

the story is not simply 64-bit, but really more about the new ARMv8 Architecture

I'll dig past the rumors and nonsense about what's next for Android and cut right to the chase. We're going to see 64-bit Android L on brand new hardware soon. Some of it will be using 64-bit ARMv8 processors. Some will not. But the move to the new architecture is coming from all vendors, and 2015 has the potential to make our mobile devices a step closer to what we have always wanted them to be — a true desktop-class computer you can carry in your pocket, that can last long enough on a charge to enjoy using it.

I can't wait.

Jerry Hildenbrand
Senior Editor — Google Ecosystem

Jerry is an amateur woodworker and struggling shade tree mechanic. There's nothing he can't take apart, but many things he can't reassemble. You'll find him writing and speaking his loud opinion on Android Central and occasionally on Twitter.

  • So instead of drinking out of one fire hose I'll be able to drink out of four fire hoses?
  • I'd change it a bit: Instead of a fire hose feeding into a garden hose and back into a fire hose it will now be one continuous fire hose =-= ~> === Posted via Android Central App
  • I cannot find anywhere on the article anything stating that the CPU will have a 64 bit data bus in addition to 64 registers and memory addressing space. If the data bus is not 64 bit wide, then there is no I/O advantage as it is being argued. If the data bus is serial (I have not checked the details on ARM architecture), then sending a 64bit word is not faster than sending 2 32bits words. My old HP48SX calculator had a Saturn CPU with 64bit registers. Great, right? No! It had a 4bit data bus. Filling out those 64bits used to take 16 cycles!
  • Even modern ARMv7 SoCs with Cortex-A15/A17/Krait can use over 4 GB RAM via LPAE.
    Majority of Android apps are ARMv8-ready because Dalvik/ART is a managed runtime, so all Java-apps will use ARMv8 enhancements without additional work from developers. But NDK apps, like games or browsers, will require additional optimisations.
  • Majority of Android apps - yes, the vast majority of apps people are actually using - no. 23 out of 25 top apps int the US chart are NDK apps.
  • Now if they would pair the high-performance 64-bit chip with 4.7" 1080 screen, 3+ GB RAM, a 3000 mAh battery, a 16 MP camera and raw Android, we could all be happy.
  • 4.7"? It's almost 2015. The market demands large 5"+ displays all other things being equal.
  • /s Posted via Android Central App using an LG G2.
  • I don't agree. I have bigger hands, I still don't want a huge phone. I have tablets and other screens if i want something bigger. What I want is a high content phone that doesn't need to be 6" tall.
  • +1. And that's why my wife next phone will be the Z3 Compact. Posted via Android Central App
  • My thoughts exactly. Can't wait for the Z3 compact myself. I'm just glad there's at least one company not nerfing their phones just because the phone is smaller. I wish more companies followed suit.
  • Yep... 4.7" should be the maximum size for a smart phone.. I can't wait to see a drop in original moto x price :) Posted via the Android Central App
  • i remember when the Droid X2 came out and i said that's way too big of a phone (4.3 inch). Now i have the Droid DNA (5 inch) and i absolutely love it. No size is perfect for everyone, but saying 4.7" should be the maximum is like Apple logic, telling the consumer what they want. That's what's so great about android you can have a 3.1 inch touch screen or a 6.5 inch screen. Get whatever you want. There is no maximum size a phone should be. to each his own. Carry on.
  • Amen. Please keep screens under 5" without skimping on the specs!!
  • Agreed like the Z3 Compact, awaiting reviews but Sony pretty much have my money already.
  • I'm trying to decide between the new Moto X or the Xperia Z3. I have the Z2 already, but the Z3 has a slimmer profile and looks more ergonomic... The Z2 is pretty solid, but it's a brick. It isn't easy to hold it for long periods of time.
  • Trouble with the Z3 they seem to update it every 6 months so after a 2 year contract we'll be on the Z7. Fortunately the Compact version appears to be on a yearly cycle.
  • I don't do contracts, and I buy new phones all the time, so that part isn't a problem. Right now I have (5) Xiaomi Mi4, (2) 64GB OnePlus Ones, (1) Sony Xperia Z2, and (1) LG Optimus G for AT&T. I think that's all I have right now. I'm selling all of them except for the Z2, so it's hard to keep track of what's coming in and what's going out lol
  • I'm happy with the size of my 5in S4, but nooo bigger!!! Posted via the Android Central App
  • No. There should be a choice. There should be phones under 5" as well as larger. My current phone is 5.5" and I don't plan on buying anything smaller. Many people enjoy their huge phones.
  • The new moto x!!!! Wait... Well shit, I'm bummed again. Posted via Android Central App
  • I believe this Franken-droid you speak of has already been forged and it has been named Droid Turbo. This beast should be on sale soon, and though it has a 5.2" display it should be a similar form factor to the 2013 Droid Maxx. Also note that it's 805 Snapdragon may not be full 64bit beyond its memory bus. We'll know more when it's officially announced.
  • is that good? yes.
    do I care? No.
    a mobile processor spends very less amount of time in it's highest state. I am least bothered about that few mins of peak performance. do this allow more efficient SOC? i will rather want a vendor giving me a 14nm SOC.
  • Intel's Core M. Lower wattage than the Tegra 3. Destroys everything else performance-wise. Too bad the cost will be $200+ for that SoC.
  • Intel - "Snatching defeat from the jaws of victory in mobile for the last 10+ years."
  • Why not both? :)
  • Grabbing more data per cycle is great, but it is really only a benefit if the cycles are being filled. I'm not sure of the CPU situation on mobile but on desktops it is virtually impossible to completely fill the pipeline so being able to grab more data isn't super helpful. More SIMD instructions or MIMD instructions definitely help though and I'm guessing that is a big part of what they are doing with v8 to make use of the extra data.
  • 64-bit chipset in a new Sony device would make PS4 Remote Play amazing. Posted via my $10 a month Unlimited talk & text FreedomPop Galaxy S III
  • You've hit on the central fallacy of 64bit, one that I would have expected Jerry to mention, as he's been around the block enough times to know. 64bit helps out tremendously in data move operations, which is what a computer spends most of its time doing. Not high power math, not super speed calculations, just schlepping data from one place to another, sometimes to storage, sometimes to screen, but MOVING DATA is 95% of a computers work load. If you can do that in 64bit chunks its far fewer instruction cycles. HOWEVER that's only half the story, and Nvidia's evasive answer to Jerry did nothing to tell the other half of the story. (Hint to Jerry: they wrote you off as a noob, I'd be insulted at that reply). If the clock cycles to load or store using a 64 bit register is slower than the cycles to load/store a 32bit register there is zero gain. Quite often this is the case. 64bit Linux does not run any faster than 32bit Linux on many processors because the clocks involved in 64 bit addressing, 64bit loads, 64bit stores are often twice as long as 32bit operations on some processors. Without a fairly big improvement in instruction clock cycles 64bit alone does nothing for you. Its often visibly slower. This was historically true of MOST 64bit processor from Intel, especially prior to Core 2 line. If Nvidia is rushing to add 64 bit in the same way that Intel did initially (tandem 32bit memory loads to 64bit registers ), prepare for the big yawn. If they did it right, and didn't pay a big clock cycle penalty, then you may (just may) see a performance boost.)
  • ARMv8 isn't x86-64, and Android isn't GNU/Linux. ARMv7 SoCs can use 32-bit CPU and 48-bit memory for example, so Intel problems are Intel problems. AFAIK, Tegra K1 with Denver CPU has 64-bit CPU and 64-bit-memory.
  • "ARMv8 isn't x86-64"....... right "Android isn't linux"........ wrong.
    Although is never mentioned as it, android has a linux core and is, by definition, a linux distro. Everything else.... looks right
  • Android isn't _GNU_/Linux. Keyword is GNU. Google Android uses complex virtualisation technologies and it has multiple differences from classic GNU/Linux distros like Fedora or Debian. For example, Android isn't compatible with Linux Standard Base (LSB) specification, Android's middleware is more similar to OpenBSD etc. In Intel ISA x86-64 is only an extension to classic x86, so the main feature of this extension is 64-bit execution/memory. ARMv8 is more complex iteration than x86-64. In Intel's x86-32 architecture you can use only 32-bit CPU and 32-bit memory mapping. In ARM's Aarch32 you can use 32-bit CPU and 40-bit memory mapping.
  • You write too much and say too little.
    Do you even understand my expressions? Please check icebike's comment again... He never said "GNU"
    (And I never said "ARMv8 is x86-64" so the second paragraph is useless too) Look, whether or not Android counts as a Linux distribution is a matter of definition. It uses the Linux kernel, so for most people, like me, Android is a Linux distribution; but some people just disagree by noting the lack of support for many GNU tools in Android, including the glibc.
  • Do you think it will encourage the development of alternative device formats within Android. Perhaps like the ASUS Transformer or even viable laptops?
    Are we likely to see Android and Chrome OS merging? Awesome AC.
  • I don't think that Chrome OS can be merged with Android. Android has multiple differences on kernel layer like wakelocks. Chrome OS uses mainline kernel without them. Yes, Google implemented Chromium WebView in Android and announced limited support for Dalvik/ART in Chrome OS, but I'm not sure that this merging is possible. Maybe Google will discontinue Chrome OS in the future because Android becomes more complex and flexible than Chrome OS.
  • Is there any reason to stay away from devices like the Note 4 that don't support 32 bit? Or is there nothing to worry about? Posted via the Android Central App
  • I was wondering the same. Will the transformation to 64bit be seamless or will the new adopters see issues with compatibility? Posted via Android Central App
  • 64-bit is backwards compatible with 32-bit :)
    Obviously 64-bit hardware + 64-bit software is best, but 32-bit software can run on 64-bit hardware
  • The Note 4 does support 32-bit...did you mean 64-bit?
  • Yeah I was thinking faster than I was typing. I meant to say that the Note 4 is 32 bit and not 64 bit. I'm just curious if there is a reason to wait until there is a 64 bit phone in that for factor or if the Note 4 will be just fine. I'm planning on keeping the device for 2 years. Posted via the Android Central App
  • Note 4 with Exynos 5433 SoC uses ARMv8 Cortex-A57+Cortex-A53 CPUs with Mali-T760 GPU.
  • Let's not forget the most important reason for Android reason: bragging rights against all those iSheeps out there.
  • Well Apple already uses 64-bit chips OPO | G3 | N5
  • And they use ARM-v8A architecture
  • And they're no faster than 32 bit Android devices for most purposes.
  • thats debatable. the A7 was probably the best ARM chip for about 8 months.
  • Maybe so, but benchmarks aside, the iPhone really doesn't do typical tasks any faster than a similar Android phone, and battery life is not a strong point of the 5s either.
  • Nah, we've all seen the benchmarks. Of course, if we compare the latest Android with the, now year old, iPhone 5S then we could say you're right.
  • At least in this aspect you came more than a year late. Those year old iPhone 5S have been using 64bit processors and have been taking advantage of them.
  • Thanks Jerry. This is a great explanation of the architecture and it's benefits in laymen terms. Hmm..... I really think I will wait until the 2015 iteration of Android software and devices to see what's in store.
    I mean version one of anything is Ok but version 2 of 64 bit operating systems and hardware will likely improve upon the first offering. Meanwhile I will hopefully install Android L to my Nexus 5 and see how that works, but not expecting much visible performance improvement - but that's ok cause it's fine for me now. Makes me wonder though. Will there be two versions of Android L a 64 bit and a 32 bit just like there was for Windows 7?
  • Yes. Otherwise how do you update older phones to L?
  • And for heaven's sake —stop saying the big deal about 64-bit hardware is the ability to use more than 4GB of RAM. Thank you, Jerry!
  • But that will be a huge plus for Samsung. By the time 64 bit CPUs are mainstream, Touchwiz will probably consume 4 GB RAM.
  • Haha true that Posted via Android Central App
  • Hey! I knew some of those words!!
    Lol, jokes aside thanks for the article Jerry, I actually didn't get a headache reading it like I normally would with breakdowns like this. Eager to see the next nexus now Posted from my caseless GS5, because I believe in myself
  • Awesome write up and also love the teasing of Nexus 8 thrown in there for good measure :)    
  • Nice presentation but it still isn't going to make any noticeable difference. It's great for marketing though.
  • Says the 8-bit wizard
  • awesome.
  • So I was planning to buy the J Butterfly 2 as soon as its available in India. I will be using this phone for atleast 4 years. If I buy it will this new wave of 64 bit apps kill the old ones? Should I buy the 64 bit phone? Please help.
  • I think all anyone can do is speculate on this. 4 years is a long time the smartphone world so it is hard to say. However most apps are compiled to bytecode and run through Dalvik (or ART with Android L onwards) which handle making it run on whatever processor you have and so shouldn't have a problem continuing to run on a 32-bit processor. It's possible developers that use the Android NDK to compile to native code may not support older processors, but I expect that will be the exception for a few apps and games that need high performance. Posted via Android Central App
  • I think expecting 4 years of functionality out of a smartphone may be a bit much. 2 years definately, 3 years possible. But after 4 years, assuming that the CPU can still hold up, I would think that your screen would be broken or your battery, or even buttons on the phone. As for apps, I honestly doubt that there will be any amount of significant apps will require 64 bit.
  • 4 years was max to max sir. But 3 years is a definate. You have answered my question sir thank you for you time. I will be gettin the E8 or the butterfly 2, if i can get the butterfly 2 in India that would be great.
  • Samsung HQ: With 64-Bit Tech we will be able to access more of the battery power and finally introduce our 8K screen!
  • I think most likely the nexus 6 will have some firm of 64bit, either nvidia or Qualcomm Posted via Android Central App
  • Well yes. Seeing how Nvidia is confirmed to be coding with Android L and given all the other rumors it should be 64 bit based. Posted via the Android Central App
  • Yes, contrary to what AC mentioned in their podcasts, I believe there will be a tegra k1 denver phone release this fall.
  • > will allow for things like TouchWiz to be as "fast" as AOSP. For reals. that should read:
    will allow for things like TouchWiz to be as "fast" as AOSP [b]was[/b]. For reals. its not as though aosp won't be able to take advantage of any architecture improvement. m.
  • So, in summary, just as we said when Apple used this as a marketing gimmick, the 64bits are not important.
    The new architecture that happens to use 64bits is important, however.
    Not difficult to say, or understand, is it? Ñ
  • I have many conflicting feelings about this, I am a dip elect comp tech net admin, when I retired about the same time I abandoned the desktop as a pain in the butski, Android 4.4.4, is without a doubt the worst high pixel, Bluetooth audio OS, we have yet to produce. You're watching a high def video, and the whole OS collapses into reboot, how can we compete with a 64 bit Apple OS, that runs high resolution video, in days, they release iPad mini 3, iPad mini 2 will get cheaper second hand. It's already 64 bit, resolution display, 4G, and it doesn't randomly reboot. I feel like a traitor defecting to the walled garden, but what choice do I have when perfection, project butter's speed and reliability is being abandoned, for what, some Microsoft like unreliability. Where is the laser like focus of Jelly Bean 1 and 2, we were so good at getting product out to the customer, at a cheap price, in the future of UHD tablets and smartphones, I hope you don't get slaughtered. Sorry, like a rat leaving the sinking ship, I am abandoning a system that can't exploit the super powers of the hardware, masses of GPUs, CPUs, RAM, flash, good screens, what do we do, at the border of 64 bit, head into self confusion. Love you googameistro, but your tearing my heart out with unreliability, if you want me back, get into the ecstasy that was project butter again.
  • I have a S5, a Note 3, and a Nexus 7. And i haven´t had a self-reboot for... weeks? maybe 1 or 2 month? And i use root, custom roms, and mods on 2 out of 3 devices. So don´t tell us your reboot problems are androids fault - because they are not.
  • I'm not sure your point, as a hardware guy, my carrier got in the way of my updates, a year ago shortly before I went off contract again, so I rooted my galaxy nexus, bricked it, that was a no resaler, now running a 32 GB Nexus 5 and 10 QHD. Most folks ain't going to root their devices, look I'm not a programmer, just a hardware jock, but if a network administrator can't get their device to run high resolution video, without random reboots, sorry, something is drastically wrong, I've done whole factory resets, but the problem has remained. Do you know how it tears out my heart to have to shift again, I was a Windows 8 pre release tester, a year before it was released, then, it became bloatware, so in my first year of retirement, I abandoned the desktop. After 3 years, I went nearly all android, now after 4 years with android, I'm preparing to bail out, high resolution video is big time important to me, do you really think a hardware jock, would want to move to a platform, that's more expensive, per transistor. Where flash is very expensive, with low RAM, but crashing while I just watch a video, most of that is handled in the hardware, GPUs, why is the software getting in the way, we used to say we supply 10 times the power, so we expect the software folks, to make the device twice as user friendly, not 1/10 th as useful. Again after the magnificent job they did with project butter, why'd they make it, so video crashed, this'll lose sales, but I am retired, so why should I work so hard on something as simple as video.
  • Never had any reboots watching HD video on my Nexus 5 nor my Tab Pro 10. Only reboot I had was on the Nexus 5 with a beta paranoid rom. Also iOS devices have a higher chance of crashing and rebooting. They aren't that stable, so you might consider switching to the dark side ;)
  • Wrote you a reply, but Chrome crashed, no time to rewrite, I have to see what Apple have released.
  • Yeah......my Nexus 5 rebooted on me midcall after 2 weeks use. After that, a couple of times. Even one reboot a month is too much for me. Chrome has been crashing several times this week too...
  • Oh, it's so hard betraying a platform, that gave me so much, when the desktop became a waste of time. We all know how when the desktop moved beyond 32 bit, apart from XP 64 bit. It all hit the fan, it was ground down by bloatware, crapware, so when the googameistro focused on speed and reliability. I knew we were on a winner, we were super competitive with Apple on a price performance basis. Oh I remember, the original nexus 7, 4 cores, 12 graphics cores, 1 GB of RAM, in those days it was a lot. At 4.2.2, things were running supper fast, then with all the advantages of an ecosystem, tight core, things began to deteriorate. It was like a super fast repeat, of the tech wreck, nexus folk began to be treated like guinea pigs. The magic of well curated services over the internet began to disappear. Into the future, we have to tackle 3D UHD, yet if we allow self confusion to dominate, we'll be stuffed like a dinasour our (think my spelling is wrong.) The tightness of the original iPhone is starting to bite us badly. I prepare to do treason, how hard it is for me as a hardware nutter, but in a difficult transition like 64 bit, UHD, it's hard to avoid the logic that locked down is better, see the huge gains in 4.2.2. Posted via Android Central App
  • Never had my nexus 5 reboot like that watching HD. However I have a ipad mini and my wife has an ipad2 and we where recently forced to update to ios8 to install some software needed for university.. since ios8 the devices have become pretty much useless. Oh you say you prefer 4.2.2? at least when you upgrade with android to say 4.4.4 and find it is causing you problems you can flash back the 4.2.2 rom.. can we with are apple devices? nope we are stuck with ios8 causing our devices to freeze/slow down.
  • You actually can go back to ios7. You have to go to http://www.ipswdownloader.com and download the appropriate image file for the iPad 2. Then start iTunes, connect the iPad 2 and hold shift when clicking on check for updates. This allows to manually select the image file and revert to iOS 7
  • So all the major platforms have become unreliable, what a sad state of affairs, remember the halcyon days of Jelly Bean 2, Windows XP, it just works Apple, my sisters Apple HD all in one, goes birko every now and then, when I retired a year ago, I abandoned the desktop and I am a qualified network administrator. As I said earlier I tried to flash a ROM, but bricked my Galaxy nexus, for many of us, going mobile meant a smaller OS, object oriented software, managed services, apps ecosystem, which using keep it simple stupid ie. KISS, less GIGO, garbage in, garbage out. Works better, when I watch an upscaled Blue Ray, from FHD, to UHD, it just works because, it's straight forward, sometimes a movie in QHD on my Nexus 10, is beautiful, but then there are the other times, when you're trying to catch up on something, you missed on the TV and it goes crazy and completely reboots. Look at how successful digital TV has been, I get 30 channels of HD TV, 5 of them in FHD, upscaled to UHD, it can be exquisite, I've probably said it before, hardware guys supply 10 times the power, we expect the software guys, to make the devices twice as user friendly, that hasn't happened in a long time, have we seen what hardware does ? 192 GPUs, 4K screens in 6" phablets in 2015, $50 USB 3 sticks in 128 GB, 1 GB/s WiFi ac, 64 bit systems that can use more than 4 GB of LPDDR4, graphics RAM, but maybe the software will ruin it, take all the fun out of it.
  • Will it give me a longer battery life? I didn't think so.
  • So which is more important, 64-bit, or MOAR CORES............
  • I love this articles, Jerry is like the Steve Wozniak of AC. Posted via Android Central App
  • 4 GB of RAM. Yes...I just went there.
  • Thank you Jerry for the Information, well done.
  • Nah!! 64 bit don't really matter on a phone. Posted via the Android Central App
  • Hey Jerry, how do you know so much about all technical stuff ? Thumbs up to you
  • Great stuff, Jerry! Thanks for taking the trouble to write so well. Posted via Android Central App
  • And for heaven's sake —stop saying the big deal about 64-bit hardware is the ability to use more than 4GB of RAM.
    I wonder why this wasn't said when the iPhone 5S came out? Seems a bit hypocritical to me.
  • I guess I thought this WAS said. I know I heard that the upgrade to 64 bit iphone was more about the future than the present and I still don't think the present is fully here yet which is why I am going to wait and see what 2015 brings.
  • You're right, it was said. But anybody who said it was labeled as a blind iSheep.
    Now that Google announced that it's going down the same path, everybody nods while saying: "yes, that's the correct thing to do" and now, all of a sudden, it's not so stupid nor just a marketing gimmick to have a smartphone with a 64bit processor and less than 4GB of RAM. Quite an example of sheep behavior.
  • I can wait, it's all useless fake importance. Posted via the Android Central App
  • Android Architecture :-http://thatsjavainfo.com/android-tutorials/android-architecture/