Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How does 31% faster or 64-bit matter at all? If the phone is responsive, it doesn't matter what is in the thing.
 
"iPhone 5 will not support simultaneous LTE data and voice on any carrier, and cannot possibly support SVDO on CDMA carriers.

So on AT&T, iPhone will fall back to HSPA+ while on a phone call. On Verizon/Sprint, there will be no data while on a phone call (while every other CDMA/LTE smartphone does support LTE data while on a phone call)."
http://m.imore.com/iphone-5-reporte...e-and-data-over-lte-or-all-verizon-and-sprint




" When an AT&T iPhone gets a call, it just falls back from LTE to UMTS and runs both voice and data over 3G."
http://www.pcmag.com/article2/0,2817,2409716,00.asp



" It should be noted that iPhone 5 users will not be able to access LTE speeds while on a call."
http://appleinsider.com/articles/12..._data_over_4g_lte_limited_to_certain_networks

Ah it drops down to 4G HSPA+ not HSPA. That's why it's still speedy.
 
A7 Processor to Be 31% Faster and 64-Bit, iPhone 5S to Support Motion Tracking?

Ah it drops down to 4G HSPA+ not HSPA. That's why it's still speedy.
So you admit I'm correct, no LTE. Fantastic. That's all I wanted. :)

Also, HSPA+ is 3G, despite what that icon in your system bar says....but I don't feel like quoting more articles, so we'll let that go.

----------

The A6 is plenty was...heck the A5 was too. How about a 31% bump to battery life.
I'd gladly take a slightly larger device for longer battery life, I hope they do more that just bump the size to maintain current run times.
 
The same reason I upgraded my 'original' iPhone... The evolution and therefore demands of an evolving iOS and subsequent Apps will ultimately slow a device which cannot cope with an ever increase in hardware requirements.

Bigger and more advanced Apps and iOS becomes = The need for more power to support it.

I already learned not to upgrade to the latest iOS revision the hard way. My iPad 1 was perfect until iOS 5 :-( Therefore I get this year iPad 5. I will upgrade my iPhone 5 only up to iOS 8. I hope it will manage that fine. Keep my fingers crossed.
 
A7 Processor to Be 31% Faster and 64-Bit, iPhone 5S to Support Motion Tracking?

Motion tracking? I wonder what all the people who made fun of Samsung's S4 will say if apple try the same thing...?
Apple will probably put thought into it. TouchWiz looks like it was designed by a color blind 5 year old. And those functions don't always work properly.

Apple has lost it's footing on innovation, but they've mastered refinement.

----------

I already learned not to upgrade to the latest iOS revision the hard way. My iPad 1 was perfect until iOS 5 :-( Therefore I get this year iPad 5. I will upgrade my iPhone 5 only up to iOS 8. I hope it will manage that fine. Keep my fingers crossed.
I don't plan on moving my iPhone off jailbroken iOS 6.1.2 until I see some speed tests. I haven't seen anything in iOS 7 that my phone doesn't do right now. And there are no hiccups.

All that translucency, more apps running in the background...something is going to stutter.
 
A7 Processor to Be 31% Faster and 64-Bit, iPhone 5S to Support Motion Tracking?

Please, show is all your data.
A good place to start would be a quick poll on what percent of people actually password protect their phone and would benefit from a 'faster' finger scan.

Also, bleeding market share to larger screen devices would be a good indicator, too.

Whatever they add, I just hope it's not visible in the digitizer.
 
A good place to start would be a quick poll on how many people actually password protect their phone and would benefit from a 'faster' finger scan.

Not really. I don't password protect my phone because it's annoying. I would start protecting my phone more with a fingerprint reader, assuming it worked quickly and consistently.
 
Motion tracking? I wonder what all the people who made fun of Samsung's S4 will say if apple try the same thing...?

Am sure Apple will make it (if they do it at all) funcional and useful and not like Samsung for one of lifetime use (just like their ad where the persons eats ribs and wants to respond a call). If people dont use it like the windows tablets 5 years ago, then its like it never existed. The true innovation is when you make a technology useful for the user. If its not useful, its just technology, not innovation. After the maps app fiasco, Apple will be rly careful before releasing a new tech, hardware or software.
 
A7 Processor to Be 31% Faster and 64-Bit, iPhone 5S to Support Motion Tracking?

Not really. I don't password protect my phone because it's annoying. I would start protecting my phone more with a fingerprint reader, assuming it worked quickly and consistently.
I plan to clog up the lockscreen with useful items via IntelliScreen for jailbroken iOS7...so it'll be useless to me.

Just polishing up my Mission:Impossible spy kit, can't wait to start lifting fingerprints and unlocking phones :p
 
A good place to start would be a quick poll on what percent of people actually password protect their phone and would benefit from a 'faster' finger scan.

For me it would not be about locking and unlocking.
Each time an App would ask for a password, you could simply touch the sensor to authenticate.

No fiddling with AppStore passwords, web site logins and so forth.
 
Read up on how ARM is going "64-bit", sir. The ARM v8 architecture is 40-bit/48-bit initially, expandable for some day in the distant future to 64-bit, and is capable of executing both legacy 32-bit and "64-bit" code.
That's only for the purpose of maximum memory address space, not actual integer instructions. The instruction set itself is truly 64bit, but the maximum amount of physical RAM that is addressable by the chip is not 16 exabytes (2^64), but instead is 1 TB (2^40).
 
A good place to start would be a quick poll on what percent of people actually password protect their phone and would benefit from a 'faster' finger scan.

Also, bleeding market share to larger screen devices would be a good indicator, too.

Whatever they add, I just hope it's not visible in the digitizer.

Every single person I know has password. Except me, I hate to type codes just to unlock my phone.
 
Maybe you should read up on linux and android kernel and see how its arch works.ohh and just so you know android right now supports multithreading and my galaxy s4 I'm typing this on is using ddr3 ram.

That little tid bit at the end with the new armv8 instruction set made me laugh out loud man,thanks I needed that! Do you really think apple is going to go from a cortex a9 based arch and skip a15(big little) and go directly to the next next gen that even arm and Samsung that work together making a15 and don't even have that working right yet in the 5s? Ohh and only get a 31% increase of performance when in fact going to true 64 bit will double its performance and a15 alone is over 40% faster then a9 arch

Rumor has is that apple signed a new deal with Samsung for a8 socs and you can bet your iPhone that is when you will see arms 64 bit soc in an iOS device and of course it will be built by Samsung since they are working together now with arm to get a15 done right.

This is taken right out of your anandtech site witch is just saying what a57 is like and not a working soc but the funny part is the a57 is 30% faster then a15 clock for clock in 32bit mode and even faster in 64 bit.

So do you really think apple is going to use a57 in the 5s when its only 31% faster and that 31% is still not even close to a15 performance?

In your article they mention the a57 being 3x faster then a9 so if apple said 331% faster then a6 I would think it had a true next gen 64 bit arm core running armv8

I hear you but I think your missing my point Apple would never use an A15 core as its to much of a power hog as its used today. Secondly the A6 processor is based off of Armv7 instruction set its not an exact duplicate as Apple has modified the cores.

Quad core configuration in a mobile Soc is not as efficient as it seems yes it has processing power but there's a lot more to it than that. Raw processing power will only get you so far, Apples way if controlling the OS while developing the software in tandem can reap just as powerful a combination not on paper but in the end result.

It's the great car vs the great driver argument, you can build the fastest car in the world but a great driver in a slightly less powerful car can still win the race because he has better tactics and experience.
 
64bit doubles the memory bandwidth and therefore the transfer from and to the GPU. That's a major improvement. It's not about address space, but bandwidth.

With 32-Bit software (and almost everything still is 32-Bit software), it actually burns twice the bandwidth at zero benefit, because all those registers have to be filled with zeros.

There are only very few applications that actually benefit from or require 64-Bit hardware.

Also, addressing more than 4 GB RAM can easily be done with PAE ("Physical Address Extension"), which is something that all 32-Bit Linux kernels support.

Basically, history currently repeats itself once more. I remember the time when 32-Bit software was actually slower than 16-Bit software and when 4 GB RAM in a desktop computer were still something out of a Science Fiction movie...
 
So you admit I'm correct, no LTE. Fantastic. That's all I wanted. :)

Also, HSPA+ is 3G, despite what that icon in your system bar says....but I don't feel like quoting more articles, so we'll let that go.

----------


I'd gladly take a slightly larger device for longer battery life, I hope they do more that just bump the size to maintain current run times.

I agree with you on the battery size. I'm curios how ios 7s new true multitasking will be on battery life.
 
How does 31% faster or 64-bit matter at all? If the phone is responsive, it doesn't matter what is in the thing.

31% does matter. Because of all the stuff you (developer) don't do now, because of how 'sluggish' it feels when you try to implement it.

64bit will make it 2-4x faster at moving stuff around (most important, since VM stuff is pretty small value on a limited memory system), AND you can do a lot of things in memory stuff faster (e.g. encryption). And more accurate (where they have been using 32bit because of the bandwidth limitation)


iOS/iDevices leadership in 'response' is a key differentiator. As we move to 'motion detection' and 'facial recognition' and 'voice control' moving from 32 bit to 64 bit is more than 2X as fast in doing compute intensive stuff as you not only calculate and move 2X faster, you also remove a lot of assembly/disassembly of the payload).

We think a 0.1sec delay in screen changes as 'slow' (see amazon's study on that) and show 10% decrease in satisfaction. And that's just page turns for text/pictures.

We need a consistent 0.01-.05sec response to feel 'comfortable' in how a virtual device responds to our actions. I'm old enough to remember pinball machines I'd avoid because the paddles didn't respond accurately.

So... 64Bit is a big thing.
 
Motion tracking? I wonder what all the people who made fun of Samsung's S4 will say if apple try the same thing...?

Depends on if it works or not. The problem with Samsung was adding 4 or 5 new features but none of them working very well. That's how they got the gimmick tag.
 
As for the developer toolkit, yeah there should be signs, unless Apple doesn't care about 64bit apps right off the bat.
Look at the bigger picture.
  1. Get a 64-bit processor into the iOS devices running iOS apps better than ever.
  2. "Secretly" work on getting OS X to run natively on the ARM processor.
  3. Update Xcode to create universal binaries.
  4. Update MacBook Air with ARM processors leaving MacBook Pro with Intel processors.
Since the MacBook Air was never intended to be a work horse, putting ARM processors in them make sense, with the added benefit of differentiating the two lines of notebooks.
 
Normally I would agree with this point but times are changing......apple has very stiff competition now so maybe they step their game up a bit on this version of the phone.

Then throw in the fact you really have to cost justify the difference between the iPhone 5c and the 5S. If Apple doesn't give the 5S more horsepower there really wouldn't be a big enough drive to pay the extra money for it.

Yeah. That makes sense.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.