How much credit does Apple deserve for the coming mobile 64-bit evolution?
0. phoneArena 18 Dec 2013, 17:21 posted on
There has been a lot of talk over the past few months about the move to 64-bit processors mobile processors. Obviously, the talk began with Apple's surprise announcement that the A7 system-on-a-chip (SoC) that would be found in the iPhone 5s was a 64-bit processor, making it the first 64-bit processor in a smartphone. But, as always happens when Apple does something like this, there is a debate about who was really "first"; so, I wanted to take a look at the entire ecosystem and talk about how much credit Apple really deserves in the coming mobile 64-bit evolution...
This is a discussion for a news. To read the whole news, click here
107. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
Apropos the 64-bit apps I listed.
A side by side comparison is impossible since you can only run the 64-bit versions on 5s.
But a side by side comparison of the same app on 5 and 5s is very well possible, and 5s easily smokes the 5.
Both 5 and 5s operate at the same clock speed. So it would be safe to say that the 64-bit A7 is much faster than the 32-bit A6.
I can't tell you about power consumption since I came to 5s from 4. All I can say is that the battery life on my 5s is satisfactory and people who came from 5 are reporting 5s to be considerably more battery efficient.
As an ARM expert however I can say for certain that the A7 consumes much less power than the A6 while dealing with a large chunk of data thanks to its cache efficiency I mentioned in another comment.
You simply cannot expect such trivial apps like Twitter to be significantly faster (do they have to?), but I assure you they consume less power on 64-bit.
But all above this, it's extremely important completing the transition ASAP, making everything run in 64-bit on ARM64 due to the switching overheads that aren't existent on x86_64.
Apple almost completed this process already and will call it finished by spring 2014 where the devs are forced to use XCode5 and make their apps compatible to iOS7 which in turn means that they will have no reason for targeting below iOS6.
Google better do things right since it's gonna really hurt.
111. shiv179 (Posts: 22; Member since: 08 Aug 2012)
Thanks for the replies JakeLee.
I don't know if the experimental ART runtime will have any impact, let's just wait and see what Google comes up with.
I am not an Android fanboy by the way, I just like to give companies a chance to prove themselves, even if the odds are stacked against them.
114. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
ART isn't a big deal either.
It's just the name of Google's Dalvik JIT compiler, not a new technology.
If you look at the Quadrant benchmark results, you will see huge differences between SoCs. Quadrant is a pretty useless benchmark since it measures everything running in Java which means all the results are saying about is how well the JIT is implemented.
You'll see the Qualcomm based ones performing the best, because Qualcomm acquired a very capable JIT compiler.
(Nexus' suck bad at Quadrant with Google's stock JIT)
I don't think Google's ART is any better than Qualcomm's JIT though.
90. Loubielou (Posts: 355; Member since: 11 Jul 2012)
Samsung deserves this Credit not Apple,as they produced for Apple,but Apple thinks they are Superior but without Samsungs Help they would struggle,thats Why?people think the Court Cases between these two companies better Stop.as Apple would not be able to find a Better Supplier
115. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
A prime example for the ignorant, invented stories I hate.
Sammy won't be able to run its fabs at full capacity without Apple.
All the chief officers at your company should appreciate your presence, right? Why don't you ask for a salary of $3mil/month then?
121. platformwars (Posts: 86; Member since: 14 Sep 2012)
I have spent the last hour reading your comments about this topic and I must say that you are very well informed.. But as a reader I was a bit distracted by all the other comments also..
I would very much love it if you write a full article about what you've been saying in detail for all of us(without much knowledge of how everything works) in a seperate article or a blog..
As a consumer i would like to make informed choices and dont want a phone next year that on paper blows the competition out of the water but when it comes to real time performance is just as powerful as a last years device.
I am on a nexus 4 and it is working flawless for me.. but am looking to upgrade in March/April when HTC and Samsung introduce their flagships for the year..
I am not a fanboy and would like a experience that makes my life easy and need a phone that i can use for 1.5/2 years without feeling outdated.
So thanks for all the insight.. and i urge phonearena to let Jake write an article about what he's actually saying:
1. Google's problems and what they have to do
2. Apples advantages or disadvantages right now with the 64bit as compared to Anroid
3. In the coming 2 years, will 32 bit be only available on low end devices? or not even that?
Thanks Jake.. looking forward to your reply.
123. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
Unlike some optimistic souls claim, 64-bit Android is far from ready.
If you are fine with your N4, why don't you wait a little bit longer for iPhone6 or Nexus6, probably the first 64-bit Android phone?
Be warned though, the first bunch of 64-bit Android phones and their customers will be victims of Android's advance.
2014 will be a tough year for all Android OEMs for the following reasons :
- they have no chip that's significantly faster than the previous ones
- FHD resolution is more than adequate for vast majority of customers
- increasing the screen size further makes no sense
On the brighter side, they will be more or less forced to stop all those number games and start to polish their products instead. Something really reasonable might happen during this phase like a race for enhanced battery efficiency.
Everything would be fine as long as they all competed under the same condition, but there is a company that cares a sh*t about this : Apple
A 5+" iPhone6 with a resolution of 2272*1280, 3000+mAh battery, the blazingly fast A7x chip, and 2GB RAM will simply break all the records both in benchmarks and sales numbers.
Look at the three reasons above again. None of them applies to Apple since Apple has been doing so well so far even with a smaller screen, a smaller battery, and a chip that's just up to par.
Apple will go rampage while Android is vulnerable the most; It's time to harvest.
I really don't know how the Android OEMs are supposed to compete against Apple during the transition phase.
Lower end 32-bit ones will sell, but it will be hard for the upcoming 64-bit flagships to justify their retail prices comparable to iPhone6's when the performance isn't nearly up to par. That's a serious problem, and it will last for several years thanks to Google's laziness in dealing with the fragmentation.
Who will survive this phase when Sammy is the only OEM making money from Android even now?
What Google needs is a reboot, a hard reset shortening the transition phase even if it means ditching a large portion of the backward compatibility.
No pain, no gain. Transition hurts.