4 ms·

I think you'll be pleasantly surprised by the speed bump. I believe everyone is underestimating just how fast the A5 is going to make this phone.

by bjtitus 15y ago

gravitronic 15y ago
How does it impact battery life? To be honest I find the existing generation fast enough (and while I do enjoy gaming on my ipod touch 4g, I find 3d graphics completely overkill) but really the battery life is what's abysmal...
- pohl 15y ago
  Good question. The results in mobile devices seems to be counter-intuitive, to me. A faster processor often means that, according to usage patterns, the work gets done faster and the machine can go into one of the many power-saving states more quickly, leading to better battery life. That probably varies by what you're trying to do, but for a smart phone the sooner it's done and back in your pocket, the better.
  - gte910h 15y ago
    The CPU bound processes in most apps are tiny portions of the entire app.
    - pohl 15y ago
      Don't take my "back in your pocket" comment too literally. The CPU is going to go into low-power states quite frequently while you're using these I/O bound applications you describe, and the sooner it can, the better. I don't think what I'm saying is controversial in the mobile industry. For example, here's an old article that has a quote about the effects of Intel's Quick Start technology from back in the year 2000 that captures what I'm saying: http://www.anandtech.com/show/2782/2 http://www.anandtech.com/show/2782/2 “"Intel has figured out that it is best to use full CPU power for a split second to finish a task and then put the CPU to idle as this conserves battery life the best. Although one may suspect that when running complex operations the CPU would not have time to go idle, this is not the case. To illustrate this point, Intel used an example of DVD playback. Very stressful on the system as a whole, Intel's quick start technology allows the CPU to "hurry up" and perform the DVD decoding operations and then go idle until the frame is displayed to screen and the next scene needs to be calculated. This saves battery life because, although the system may require 3 watts or so to "hurry up", the power consumption goes down near .25 watts when idle. By averaging these two numbers, one can quickly see how quick start can extend battery life."”
      - gte910h 15y ago
        While what you're saying about CPUs is correct, that is not the main battery hog in smartphones (additionally why Apple is staying so far from LTE at the moment) The biggest demon is by FAR the radios. The amount apps and the phone use that is mostly determined 1> by how much the user wants notifications (which are basically implemented by constant polling, even in background notifications), or 2> how network intensive the apps are that a person is using. Additionally, stuff like having bad connections to your cell provider make the radio receiver power have to be turned up (as well as broadcast, but the receiver is the worst part usually), and constantly using bluetooth will kill you as well. The bad thing about the radios, especially if you have stuff like lots of apps doing push notifications, as well as a fast polling interval for your mail, is that you're doing this even when the phone is in your pocket. Second to the radios is technically another radio, but people only do 1 way comms with it and don't really think of it as a radio: THE GPS SYSTEM. Apple vastly improved this (it used to pretty much leave the system on, now it pulses it on and off unless your app requires the older mode for some reason, such as Navigon type turn by turn navigation). Again, this is a part of the phone that optimization did help with (as often time the GPS radio doesn't come on if the phone can figure out your location from other mechanisms), but still, you're generally speaking going to see most GPS heavy apps running while the user is using them. Sure driving faster will get the phone in their pocket faster, but I'm not sure an added hour of battery life is worth unsafe driving. I'm not saying graphics and the like don't eat up huge chunks of power, I'm just saying that a vast majority of people eat most of their power on much more pedestrian things than Infinity Blade.
        pohl 15y ago
        True. I didn't mention radios (or the backlight, for that matter) because I was replying to a specific question regarding the effect of the speed bump.
- yakto 15y ago
  Battery life is supposed to be better - 8h talk time.

I think you'll be pleasantly surprised by the speed bump. I believe everyone is underestimating just how fast the A5 is going to make this phone.

by bjtitus 15y ago

I think you'll be pleasantly surprised by the speed bump. I believe everyone is underestimating just how fast the A5 is going to make this phone.

gravitronic 15y ago

How does it impact battery life? To be honest I find the existing generation fast enough (and while I do enjoy gaming on my ipod touch 4g, I find 3d graphics completely overkill) but really the battery life is what's abysmal...

pohl 15y ago
Good question. The results in mobile devices seems to be counter-intuitive, to me. A faster processor often means that, according to usage patterns, the work gets done faster and the machine can go into one of the many power-saving states more quickly, leading to better battery life. That probably varies by what you're trying to do, but for a smart phone the sooner it's done and back in your pocket, the better.
- gte910h 15y ago
  The CPU bound processes in most apps are tiny portions of the entire app.
  - pohl 15y ago
    Don't take my "back in your pocket" comment too literally. The CPU is going to go into low-power states quite frequently while you're using these I/O bound applications you describe, and the sooner it can, the better. I don't think what I'm saying is controversial in the mobile industry. For example, here's an old article that has a quote about the effects of Intel's Quick Start technology from back in the year 2000 that captures what I'm saying: http://www.anandtech.com/show/2782/2 http://www.anandtech.com/show/2782/2 “"Intel has figured out that it is best to use full CPU power for a split second to finish a task and then put the CPU to idle as this conserves battery life the best. Although one may suspect that when running complex operations the CPU would not have time to go idle, this is not the case. To illustrate this point, Intel used an example of DVD playback. Very stressful on the system as a whole, Intel's quick start technology allows the CPU to "hurry up" and perform the DVD decoding operations and then go idle until the frame is displayed to screen and the next scene needs to be calculated. This saves battery life because, although the system may require 3 watts or so to "hurry up", the power consumption goes down near .25 watts when idle. By averaging these two numbers, one can quickly see how quick start can extend battery life."”
    - gte910h 15y ago
      While what you're saying about CPUs is correct, that is not the main battery hog in smartphones (additionally why Apple is staying so far from LTE at the moment) The biggest demon is by FAR the radios. The amount apps and the phone use that is mostly determined 1> by how much the user wants notifications (which are basically implemented by constant polling, even in background notifications), or 2> how network intensive the apps are that a person is using. Additionally, stuff like having bad connections to your cell provider make the radio receiver power have to be turned up (as well as broadcast, but the receiver is the worst part usually), and constantly using bluetooth will kill you as well. The bad thing about the radios, especially if you have stuff like lots of apps doing push notifications, as well as a fast polling interval for your mail, is that you're doing this even when the phone is in your pocket. Second to the radios is technically another radio, but people only do 1 way comms with it and don't really think of it as a radio: THE GPS SYSTEM. Apple vastly improved this (it used to pretty much leave the system on, now it pulses it on and off unless your app requires the older mode for some reason, such as Navigon type turn by turn navigation). Again, this is a part of the phone that optimization did help with (as often time the GPS radio doesn't come on if the phone can figure out your location from other mechanisms), but still, you're generally speaking going to see most GPS heavy apps running while the user is using them. Sure driving faster will get the phone in their pocket faster, but I'm not sure an added hour of battery life is worth unsafe driving. I'm not saying graphics and the like don't eat up huge chunks of power, I'm just saying that a vast majority of people eat most of their power on much more pedestrian things than Infinity Blade.
      - pohl 15y ago
        True. I didn't mention radios (or the backlight, for that matter) because I was replying to a specific question regarding the effect of the speed bump.
yakto 15y ago
Battery life is supposed to be better - 8h talk time.