I think I might revert back, there’s quite a bit of lag on this version. I’m use to ios 10 being snappy as hell.
Anyone else experiencing this?
Anyone else experiencing this?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Gosh I am finding IOS 11 GM to be so a lot slower than 10
- Thread starter shenfrey
- Start date
- Sort by reaction score
1. I will tell you where it stutters (all iPads). Open Safari. Press home button and return to home screen. Open 2-3 apps and close them and return to home screen. Then tap on Safari and observe the animation. It stutters.
2. Swiping homescreen on iPhone to go to next or previous pages stutters. The subsequent swipes are smooth.
3. Multitasking on iPads is slower. In the sense, there is no clear all apps button. If I want to manually flick up the apps, I cannot do it at superfast speed. I have to wait for the cards to animate and come to my swiping position.
4. Booting up is definitely slower. I compared both 7 Pluses in my house side by side. One was on 10.3.3 and other one was on 11.0 GM.
Apart from fps drops during some animations giving an illusion of stutter, I found iOS 11 GM to be same as iOS 10.
2. Swiping homescreen on iPhone to go to next or previous pages stutters. The subsequent swipes are smooth.
3. Multitasking on iPads is slower. In the sense, there is no clear all apps button. If I want to manually flick up the apps, I cannot do it at superfast speed. I have to wait for the cards to animate and come to my swiping position.
4. Booting up is definitely slower. I compared both 7 Pluses in my house side by side. One was on 10.3.3 and other one was on 11.0 GM.
Apart from fps drops during some animations giving an illusion of stutter, I found iOS 11 GM to be same as iOS 10.
I am finding a much bigger delay when pressing the home button. Takes about a full second.
On my iPad Mini 2 I noticed significant slowness moving to the GM from the preceding release. Before the update my Mini 2 actually ran a little faster than iOS 10.3.3 but after the GM it was painful. Power cycling helped a bit but the overall performance is much worse than it was. I decided to roll back to 10.3.3 on my Mini.
Performance is really good, the animations are just really bad. It can be fixed in a software update.
Yes on iPhone SE, I do see a ton of sporadic stuttering, slow downs, unresponsiveness.
[doublepost=1505409590][/doublepost]
I hate that kind of artificial input blocking, it's all over iOS.
It's not "artificial " input blocking. There's a reason why it's done. Letting a user trying to initiate another action before the previous task is completed is a recipe for disaster. Sometimes in complicated multithreaded operations it becomes a necessity.
Not true. For example in iOS11 it now lets you tap on icons while the unlock animation is in progress, something that wasn't possible in iOS10 and a very welcome change. This means I can quickly unlock phone and immediately tap on an app to launch it, no need to wait for the icon splash animation to finish.
Unfortunately iOS is very inconsistent in this field, some areas they block input, other areas like I mentioned they don't.
I’ve been running the beta on my iPad Air for a few weeks. I definitely have some lag. In general the keyboard lags in lots of apps. All apps seem to be slower when switching from another app, even if they are already running. Notes in particular takes a while to load up. I also noticed Safari will often show the wrong image for the last open tab. What I means is when you return to Safari after using another app it will show a tab other than the one currently open, which was the last one used.
I’ve seen the 3rd party keyboard lag (stock seems fine) and the Safari saved load screen too. The first one is much more serious to me than the second.
It was possible in one place through code optimisation, doesn't mean it will be possible everywhere else.
Plus when you unlock the device the processes are already in a specific state of sleep and there might be a condition when background thread can be halted to enable user interaction just to give that illusion of "fast" usability. Not possible in every scenario.
The lag in 3rd party keyboards is probably down to optimisation requirements from the specific developers.
I've studied this extensively, and there is no consistency or explanation for many scenarios where it's undesirable to have this input blocking. The iOS11 example I gave you, it turns out iOS8.4.1 it allowed input during animation too, but Apple blocked it on iOS9 and iOS10, and unblocked it in iOS11. If you are curious there is an extensive thread about it here: https://forums.macrumors.com/thread...responsiveness-due-to-input-blocking.1942001/
It's not a malicious "blocking" or "unblocking" as it comes across from your posts. I'm just saying that it's a requirement most likely.
how to kill an ipad on ios 11
open notes app
open safari .... make it go side by side with notes.
'un-tile' safari and try to make it a floating window
tada...you're now stuck with a non responsive ipad.
anyone else with this issue?
open notes app
open safari .... make it go side by side with notes.
'un-tile' safari and try to make it a floating window
tada...you're now stuck with a non responsive ipad.
anyone else with this issue?
LMAO how do you come up with such bugs? I keep myself at basic cosmetic level bugs.
Unfortunately I am unable to reproduce it because I don’t know how to untile safari and float.
It's not that it's malicious, it's just bad engineering. And if you see the thread I linked, it's very inconsistent, some iOS versions introduce more blocking, some remove it, some re-introduce it.
I just tried it, fully expecting you to be correct and the iPad to freeze because there are definitely still some glitches there. Worked fine though, started with notes, brought in Safari in split then made it go into slideover and everything was fine. I even tried moving it around left to right, split in split etc. Probably some small detail we’re missing to repro though.
[doublepost=1505419753][/doublepost]
It’s exactly that. Whatever they did to the “window manager”* in iOS 7 they have never quite got a handle on or fixed and things seem to regress randomly. Eventually they get things smooth in each iOS cycle but I suspect the underlying issue never get fixed.
*for want of a better term, given there are no windows in iOS