Let’s try it this way. Double click your home button for app switcher. See how fast it slides in. Now single click your home button. Do you see the delay?
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.
Apple has PURPOSELY introduced lag/delay with Home Button interactions
- Thread starter d5aqoëp
- Start date
-
- Tags
- ios 11
- Sort by reaction score
- Status
I’ve just tried this on my 7 plus running 11.1. Double click and app switcher slides in instantly with no delay. Single click to exit takes maybe half a second longer.
Exactly. On iOS 10 the single click and double click were the same speed.
No, Siri starts. But tat is still different than interrupting an opening app which is instant. But what you described on iOS 10 sounds like a bug, which is why imo it was fixed.
Last edited:
Interrupting the open app animation is instant. I agree with that. What I am saying is that once you start the app switcher, the response is instant and when you single click it to exit there app switcher there is a delay.
And if that delay is meant to wait for the double click then why is the delay still present when we want to exit the app switcher?
Technology rolls on my friend. Try not to fall for the sensationalism, it is unbecoming.
Last edited:
no, and not every note 7 exploded. only some. i didn't say anything about feedback, so, once again, you're making assumptions ("by your logic..."). "all devices on the planet'.... prove it. prove anything you're saying (and you can't, we've already had numerous people post on this very thread with different experiences than yours).
"All devices on the planet".... briliiant. and impressive that you have this knowledge. meanwhile, every note 7 every made has exploded....
The delay you speak of is present on 10.3.3 when single clicking to exit multitasking also on my iPhone 7. Weird. Never noticed it there till now but I hardly ever exit multitasking.
I think you are proving my case that that was a bug in iOS 10.3.3 for i7 class devices.
lol, my GF is horrified that i am still participating in this thread (i've abandoned it twice so far). she reminds me that conspiracy theorists generally are steadfast in their beliefs, even in the face of real-world contradictory evidence...
as this thread proves! (and there's that word again, 'proves').
so pointless to continue. look how long we've gone round & round, and nothing changes. so, am returning (again) to the real world, where life happens... and people don't stress about minutiae... real or imagined....
as this thread proves! (and there's that word again, 'proves').
so pointless to continue. look how long we've gone round & round, and nothing changes. so, am returning (again) to the real world, where life happens... and people don't stress about minutiae... real or imagined....
If it was a bug fix then Apple knows they fixed it which automatically means feedback entry should closed instantly. The reason it’s open is because Apple hasn’t fixed anything of the sort. After a year or so all bugs are ironed out from the OS and 10.3.3 had like 8 betas before release.
Or it's open because Apple hasn't spent the time looking into it. The reason isn't known, as usual it can only be supposed.
I agree it's a fix for the animation double click jiggle, but why didn't they address in 10.3.3? Why wait for 11 and a new phone?
I've been on your side from the beginning of this saga
What if Apple just wanted to go back and fix the so-fast-that-it's-messing-up-the-double-click-multi-task-animation home button on the 7's? I tried a 7+ on ios 11, and the slower response reminds me of a experience where the system doesn't do anything until I "release" the home button instead of responding when the home button is "down".
I'm kind of leaning towards Apple just wanted to "fix" this behavior of the "down" position response because that isn't how the physical home buttons function.
I dunno..... But, yeah, I also subscribe to the idea that Apple doesn't give a flip about last years' phones and optimizing for them....
Apple had been tweaking animations relating to home button since 10.0 apparently and they didn’t slow it down all the way till 8 betas of 10.3.3 . I just find it convenient how the slow down solution is applied when the phone in question is no longer a flagship.I agree it's a fix for the animation double click jiggle, but why didn't they address in 10.3.3? Why wait for 11 and a new phone?
I've been on your side from the beginning of this saga
What if Apple just wanted to go back and fix the so-fast-that-it's-messing-up-the-double-click-multi-task-animation home button on the 7's? I tried a 7+ on ios 11, and the slower response reminds me of a experience where the system doesn't do anything until I "release" the home button instead of responding when the home button is "down".
I'm kind of leaning towards Apple just wanted to "fix" this behavior of the "down" position response because that isn't how the physical home buttons function.
I dunno..... But, yeah, I also subscribe to the idea that Apple doesn't give a flip about last years' phones and optimizing for them....
Yeah, it is conveeeeeeeenient (Church Lady) that it changed to coincide with a flagship release.
This has already been addressed but maybe bears reiterating. Apple may keep it open for its own reasons; you have no knowledge of their rationale or process and are only tilting at windmills.
Is your position that you don't care what Apple's rationale is? Just wondering.... Can't remember your posts.
They did read it. That’s how they said engineering has DETERMINED that the bug is a duplicate of another bug. If they had put in a delay as a bug fix, they would have recognised it and closed the entry then and there.
Determining that a bug is a duplicate of another doesn't mean making a call as to what's brought up in the bug, just that that the same kind of thing was already reported.
Reading to see what was mentioned to make a call on whether it's something new or something that has been brought up before is not the same as looking into the actual and making a call on what it is, what needs to be done about it or something else of that nature.
Okay, thanks. Yeah, I don't think we'll know for sure their thinking, so we can only make assumptions and propose theories. Which, I'm pretty sure is your thinking.
If it's true that Apple intentionally slowed the button down so that they could push people towards upgrading to newer devices, is that enough to turn someone away from buying Apple. I mean, even if I was so distraught over their nefarious planned obsolescence, I still couldn't go buy an Android device. - One Big Shrug, "Eh"
I almost got the Pixel this year. Played with it at the store and the device is screaming fast. Instant response at everything and 5 minutes in I felt that device blows away my 7 Plus with snappy animations and responsiveness. And let me say Android Oreo had zero stutters and was more fluid than iOS 11 on my iPhone. Instead of bothering with fancy blur and pizzaz Google seems to have a laser focus on performance these days. Having used Android lollipop,marshmallow, kitkat on my Nexus I know where the laggy areas lie on Android and they weren’t there on the Pixel.
Google had the perfect phone but they blew it on the most fundamental aspect, the screen. I used to think my 7 Plus has muted colours but it’s like the Pixel told the iPhone “Hold my beer” and proceeded to show an even more muted display. Screen felt lifeless to me. Such an excellent phone marred by an LG panel. LG is nowhere close to Samsung when it comes to OLED and Apple should think 10 times before even thinking about putting them in an IPhone.
I don’t think the saturation update is going to help although it may fix it somewhat.
If Samsung actually manages to correct their biometrics to make them less annoying I would go there in a heartbeat as I personally find the Note 8 and outstanding piece of hardware otherwise.[/QUOTE]
- Status