Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's much smoother than the others.

The iPhone 5 isn't the best example as it's an A6-based and low screen-res device, meaning it's very powerful. Take a look at, say, the iPad3's keyboard lag under iOS7. It cannot be fixed by fine-tuning the animation speed as it's not because of the animations that it's slowed down.
 
My iphone 5 was laggy...It still is in certain tasks.
Speeding up animations has helped.

Your name... don't you have a game center with that name and you play real racing 3 ? Because I had you on my friends list and removed you because you were too good at rr3
 
The iPhone 5 isn't the best example as it's an A6-based and low screen-res device, meaning it's very powerful. Take a look at, say, the iPad3's keyboard lag under iOS7. It cannot be fixed by fine-tuning the animation speed as it's not because of the animations that it's slowed down.

The 5s also has that awful keyboard rotation lag.

----------

Your name... don't you have a game center with that name and you play real racing 3 ? Because I had you on my friends list and removed you because you were to good at rr3

Lol, huh?
 
I don't know what you have in mind but no other company out there keeps supporting and putting out new firmware updates for their phones even over 4-5 year old devices.
They just come with whatever comes preinstalled and don't get any newer versions at all.

1, the Android sources are public. Anyone can compile them. This is why unofficial ports exist for even the earliest devices. (I know - I've deployed 4.0/4.1 on a lot of pre-2011 Android handsets.)

2, Google do support their own Nexus handsets for years. It's only lazy 3rd party HW manufacturers that don't - but, again, for more popular models you will surely be able to find unofficial Android ports even after years.

3, Google have their apps in the Play Store, indepdendent of the current firmware version. That is, when they add a new feature to, say, the Maps client, it becomes available on all Android versions, even 2.3.x ones.

----------

The 5s also has that awful keyboard rotation lag.

Nope, it's not the rotation, it's the responsiveness of the keyboard (and even the initial presentation in many cases).
 
The 5s also has that awful keyboard rotation lag.

----------



Lol, huh?

I play real racing 3 and I had an user on my friends list called "thepoobear" and this user was so good at rr3 that he finished all the races and I removed him from my list because I couldn't win any race. Isn't that you?

----------

1, the Android sources are public. Anyone can compile them. This is why unofficial ports exist for even the earliest devices. (I know - I've deployed 4.0/4.1 on a lot of pre-2011 Android handsets.)

2, Google do support their own Nexus handsets for years. It's only lazy 3rd party HW manufacturers that don't - but, again, for more popular models you will surely be able to find unofficial Android ports even after years.

3, Google have their apps in the Play Store, indepdendent of the current firmware version. That is, when they add a new feature to, say, the Maps client, it becomes available on all Android versions, even 2.3.x ones.

----------



Nope, it's not the rotation, it's the responsiveness of the keyboard (and even the initial presentation in many cases).

Strange, my iphone 4 never lagged on ios 7 when rotating the keyboard.
 
I play real racing 3 and I had an user on my friends list called "thepoobear" and this user was so good at rr3 that he finished all the races and I removed him from my list because I couldn't win any race. Isn't that you?

I don't plAy iOS games anymore.
 
1, the Android sources are public. Anyone can compile them. This is why unofficial ports exist for even the earliest devices. (I know - I've deployed 4.0/4.1 on a lot of pre-2011 Android handsets.)

2, Google do support their own Nexus handsets for years. It's only lazy 3rd party HW manufacturers that don't - but, again, for more popular models you will surely be able to find unofficial Android ports even after years.

3, Google have their apps in the Play Store, indepdendent of the current firmware version. That is, when they add a new feature to, say, the Maps client, it becomes available on all Android versions, even 2.3.x ones.

Exactly.
Lazy manufacturers and 99% of consumers out there will not know or even bother compiling their own custom ROM and installing them to their device.
Its not as simple as going to settings and clicking update or plugging to iTunes and doing it.
The Maps example is very good but that is nowhere near the case with all the other 3rd party apps on the play store. Fragmentation is a huge issue with android.
Its way worst than Apple's system no matter how you try to put it.
Show me another 5 year old android device that runs the latest version software without a custom hack. Just by clicking accept and updating OTA.
 
2. Some of the major OS bumps was little more than a new surface on old code. For example, both iOS6 and 7 added very little new runtime features or background daemons. (iOS4 and 5 are pretty different: blocks (which work even on the 3G), background synching, screen mirroring, AirPlay support etc. are major additions, some of them also requiring additional runtime daemons.) Still, the iPhone 4 pretty much struggles with iOS7. Again, it shouldn't: iOS7 changed (added) VERY little, compared to either iOS4 or 5, except for the complete surface change. Such few changes just shouldn't slow down the iPhone 4 THIS bad.

Sorry, but Background App Refresh is a pretty major addition in this area?!
 
I play real racing 3 and I had an user on my friends list called "thepoobear" and this user was so good at rr3 that he finished all the races and I removed him from my list because I couldn't win any race. Isn't that you?

----------



Strange, my iphone 4 never lagged on ios 7 when rotating the keyboard.

My keyboard and my friends iphone 5s keyboard lag nasty when rotating.

----------

But you're him, right?

Nope. :cool:
 
My keyboard and my friends iphone 5s keyboard lag nasty when rotating.

----------



Nope. :cool:

So if you go to "messages" and while you type something and rotate the iphone, it laggs? Only my r mini does that.
 
So if you go to "messages" and while you type something and rotate the iphone, it laggs? Only my r mini does that.

Butting in here- it does lag for me on my 5. Reducing transparency makes it smooth (just stating that as fact).
 
Sure does. Low FPS. Seeing as I've seen two iphone 5s do it as well as my iphone 5, I'm assuming it's iOS 7.

That's so funny because my 4 does this on ios 6 but when I was on ios 7 I was surprised it doesn't.
 
Sorry, but Background App Refresh is a pretty major addition in this area?!

How many apps are doing this on your iDevice now? I bet none of them. This is why I haven't listed this as a hugely CPU/memory-taxing feature - unlike, say, true multitasking in Android or Symbian.

----------

Show me another 5 year old android device that runs the latest version software without a custom hack. Just by clicking accept and updating OTA.

1. In many cases, sticking with the old version is better than (forced) upgrading to the latest - which renders the device practically useless. Particularly with Apple and their horrendous final iOS upgrades for almost all their iDevices. (Except for, maybe, the iPad 1, which was practically killed after two years, having never received iOS6.)

This is why a lot of iPhone 4 / 3G / 3GS etc. users do want to return to iOS6/3/5, respectively.

2. again, staying at an older OS version isn't that big a problem under Android as

- Google's own apps are basically independent of the OS version and can be installed on almost anything, giving almost the exact same set of features; unlike Apple's stock apps that only come with firmware upgrades, not separately

- it's much easier to target legacy OS versions when programming Android than when doing the same with iOS. With the latter, targeting pre-iOS4.3 (everything small-screen 1st and 2nd gen) is very hard. No such restrictions in the android world, where you can even develop for 1.x devices.
 
[/COLOR]

1. In many cases, sticking with the old version is better than (forced) upgrading to the latest - which renders the device practically useless. Particularly with Apple and their horrendous final iOS upgrades for almost all their iDevices. (Except for, maybe, the iPad 1, which was practically killed after two years, having never received iOS6.)

This is why a lot of iPhone 4 / 3G / 3GS etc. users do want to return to iOS6/3/5, respectively.

2. again, staying at an older OS version isn't that big a problem under Android as

- Google's own apps are basically independent of the OS version and can be installed on almost anything, giving almost the exact same set of features; unlike Apple's stock apps that only come with firmware upgrades, not separately

- it's much easier to target legacy OS versions when programming Android than when doing the same with iOS. With the latter, targeting pre-iOS4.3 (everything small-screen 1st and 2nd gen) is very hard. No such restrictions in the android world, where you can even develop for 1.x devices.

I'll have to agree with you that staying on older versions on some devices is better off. Would be better if Apple allowed you to restore to older versions besides forcing you to only restore to the latest one available.
Sounds like you're a very happy android user:D What are you doing here?
 
How many apps are doing this on your iDevice now? I bet none of them. This is why I haven't listed this as a hugely CPU/memory-taxing feature - unlike, say, true multitasking in Android or Symbian.

But I didn't contrast Background App Refresh to "true multitasking" in Android/Symbian. I brought it up in contrast to supposedly "major additions" in previous iOS like screen mirroring and AirPlay support that you mentioned yourself. I just found it odd that Background App Refresh was omitted in a discussion about additions to runtime and background daemons in iOS.

In answer to your question, I don't know how many apps are refreshing in the background right now, but even if it's none, I'm sure there is at least some extra burden on the OS to manage it, calculating and scheduling when to refresh etc. which is no less than an AirPlay daemon! :)

edit: I don't think it's insignificant that the description of Background App Refresh in Settings is probably one of the only (?) places in iOS that says turning the feature off may preserve battery life.
 
Last edited:
I'll have to agree with you that staying on older versions on some devices is better off. Would be better if Apple allowed you to restore to older versions besides forcing you to only restore to the latest one available.

Yup, that'd be great.

Sounds like you're a very happy android user:D What are you doing here?

No, I'm not, at least not yet. In real life, I use the iOS (iPhone 5, iPad 4) + Symbian (Nokia 808) combo - they're perfect complementers. I just happen to know Android programming very well (have developed several apps) and also have some Android handsets (nexus7.2013, several handsets), but, generally, I only use them for development or when absolute portability is required and I can't take the iPad 4 with me.

I've been contemplating getting the Note 3 so that I can retire my iPhone 5 + Nokia 808 duo but, now that the iPhone JB is out and I can record phone / Skype calls and can enhance the video recording, I've decided to wait a bit more for the GS5 to see whether it'll have 4K video recording and optical image stabilization (the latter is painfully missing from the Note 3).
 
Yup, that'd be great.



No, I'm not. In real life, I use the iOS (iPhone 5, iPad 4) + Symbian (Nokia 808) combo - they're perfect complementers. I just happen to know Android programming very well (have developed several apps) and also have some Android handsets (nexus7.2013, several handsets), but, generally, I only use them for development or when absolute portability is required and I can't take the iPad 4 with me.

I've been contemplating getting the Note 3 so that I can retire my iPhone 5 + Nokia 808 duo but, now that the iPhone JB is out and I can record phone / Skype calls and can enhance the video recording, I've decided to wait a bit more for the GS5 to see whether it'll have 4K video recording and optical image stabilization (the latter is painfully missing from the Note 3.

Cool.
I just cant see myself switching to android. To me a JB iphone is perfect for my needs. Just gotta wait for all my hacks to be updated for ios 7 and then I'd be happy:)
 
Although you may think that there is a conspiracy by Apple regarding iOS upgrades for the iDevice how would that explain those who claimed/reported that Mavericks have speed up older Macs and longer battery life...a little off tangent to the subject but related to the OS upgrade!

Lessons learned from developing Mavericks OS and shall be integrated to iOS?! :rolleyes:
 
Hmm... and why don't they optimize the OS? Because they forgot about the old devices? No, simply by not doing anything about this is the proof that they want to make them slow. It's like you want to kill someone and one day you see him or her being hurt and you leave him or her there to die.


Freaky !
 
It might be a simple loop continuously executing NoOperation's in the main kernel - dunno. It's not even guaranteed they use an ARM NoOp code but some kind of an even-harder-to-find code (e.g., waiting for some semaphore).

The kernel is big and it's almost impossible to debug it for people that have no kernel source code.

That is, it's not just playing with files in the file system. The slowdown is implemented in a far lower, far harder-to-find level.

Simple loops? You clearly have no experience programming, let alone kernel exploration.
 
Last edited by a moderator:
Simple loops? You clearly have no experience programming, let alone kernel exploration.

1, I did use the experssion "dunno" in my OP. You seem to have ignored it. With that, I stated I don't really know how slowdown is exactly implemented.

2. Indeed I'm not a kernel programmer / hacker. However, I seriously doubt you have as much experience in iOS / Android app programming as I have. The two (Kernel hacking vs. app programming) has little to do with each other.

3. In my OP, I used exactly the same assumption as people during the heyday of Microsoft. They did state MS has added NoOp loops into their OS'es to force people to upgrade hardware.
 
Last edited by a moderator:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.