Do you actually use your home button at a rate of 408 times per minute (80 words per minute at an average of 5.1 letters per word)? I’m guessing not. So dramatic lol
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
Feenician
macrumors 603
It's not input lag. Let's same time by not having a conversation we already had.
The thing about human perception is that there's a human brain involved.
Yes, it's true that if your mind has been trained to perceive something many people have not been trained to recognize (or if your biological senses are more acute than most others), that you indeed can be perceiving something real. However, your mind can also "perceive" things that are not real.
So, that brings us to the question of, "What is reality?" Maybe this is real, maybe it's imagined, maybe it's mis-attributing a localized performance issue (software conflicts, memory/storage issues, non-standard parameter settings, etc.) as a universal flaw, maybe it's a true conspiracy, maybe it's paranoia...
If this is real, it can be tested and quantified. Anything else is speculation. 1,500+ posts worth of speculation.
I7guy
macrumors Westmere
I type at 100 wpm but click the home button at one click per minute. Typing any lag is disruptive, while clicking the home button any lag (if present) is irrelevant.
JM
macrumors 601
I like your thinking, except there have been videos on this thread showing the difference between 10 and 11 on the iOS reaction to a home button press. It's not speculation.
Do you have that lag as well when you double-press? Because when I double-press on the 8+, Multitasking view comes up instantly. This is intended.
Yeah, this is by Design.
Not idea why this thread is so long.
The split second delay gives you a chance to get the second press in to initiate multitasking.
Same as the iPhone X power button when you press it to put the phone to sleep, it has a split second delay which allows you get in a second press to initiate Apple Pay.
Really simple design, really simple to understand. Again, the length of this thread baffles me.
Not idea why this thread is so long.
The split second delay gives you a chance to get the second press in to initiate multitasking.
Same as the iPhone X power button when you press it to put the phone to sleep, it has a split second delay which allows you get in a second press to initiate Apple Pay.
Really simple design, really simple to understand. Again, the length of this thread baffles me.
If this was how it had been from the start it may not have bothered me as I wouldn't have noticed it then. What Apple did was give us a very fast home button on iOS 10 which responded instantly and took it away. Now I notice the delay every time I use the phone and I also alternate between using my iPad running iOS 10 and the 7 which makes the effect that much more noticeable. The iPad home button is faster. I have a Moto G as well and even that bargain phone closes apps faster than my 7 Plus. And even that has double tap on home button for switching home screens. So this waiting for second click ******** is just an excuse
No that is instant. Stopping the opening animation before the app opens is also instant. Try quitting the app switcher using the home button and compare it with the time it takes to activate app switcher. You will see the delay. It's really obvious once you do this.
[doublepost=1510048726][/doublepost]
You can call it whatever you want. The end result to me the user is the same. I press a button and there is a delay in response to my input. Delay is lag. The End
[doublepost=1510048891][/doublepost]
This delay was not on iOS 10.
[doublepost=1510049045][/doublepost]
I am not imagining a faster home button on my Android and my iPad. It's very clearly there. Also for the record my Air 2 is on iOS 11 has the same delay as my iPhone 7.
Last edited:
I7guy
macrumors Westmere
It doesn’t matter what you call it. In iOS 10 it was a bug and now it’s fixed(for you, for me it’s still instant). Apple didn’t take anything away. If your benchmark is app opening and closing an is the Moto g, please feel free to use that phone as your daily driver.
JM
macrumors 601
The repetition of your beliefs is starting to make me question my beliefs. Can you post a video? I am now interested in your experience.
(That may sound sarcastic... It's not. I would really like to see your instant home button press on an iphone 7 on ios 11.)
I7guy
macrumors Westmere
Yes, I’ll see if I can figure out how to do one.
[doublepost=1510065635][/doublepost]
The poster above me made a great
Observation; I can’t prove that it is a bug and you can’t prove it isn’t. Hence the title of thread is not provable resulting in mostly debating people’s definitions of proofs.
Here's a video of my iPhone 8 Plus opening and closing safari at various speeds. I'm on 11.2 beta 2. There is no delay. I can have the transition less than half way completed and still close the app.
https://www.dropbox.com/s/kua7l07usfxu9ge/File Nov 07, 9 48 15 AM.mov?dl=0
https://www.dropbox.com/s/kua7l07usfxu9ge/File Nov 07, 9 48 15 AM.mov?dl=0
simonmet
Cancelled
I don’t recall anyone complaining that the home button responsiveness in iOS 10 was “too fast” or in any way problematic. What was the problem that required this change?
The delay to some is very noticeable and annoying. We prefer and would like the option to reinstate iOS 10’s responsiveness, since Apple deems us unworthy or incapable of deciding which version of their operating system we’d prefer to use on our own device.
I don’t care if the new slow home button is the new default. Why are you telling us we shouldn’t have the option or ability to downgrade if it bothers us that much?
You clearly haven’t understood the thread at all. The delay we are talking about is when you press the home button there is a slight delay before going to home screen. You need to post a video of you pressing the home button, not a recording of the OS. That’s not going to reveal anything
[doublepost=1510067048][/doublepost]
As stated earlier if it was a bug fix Apple wouldn’t have kept the feedback entry open. Apple themselves know what has been fixed and what’s hasn’t. They closed my feedback entry after fixing 3DT stutter.
[doublepost=1510067152][/doublepost]
They have already given us the ability to customise the speed of the home button in accessibility. They just need to add a Faster setting to it. All the options there are for slowing it down.
JM
macrumors 601
Yes. All my feedback entries on bugs were closed after Apple fixed them. I had posted a minor animation issue that when you press the edit button in messages and press cancel the messages instantly jump to the left without any animation. They fixed it and closed my entry 10 days later.
JM
macrumors 601
If you try to close the app in transition it’s instant. The delay we are talking about is after the app has fully loaded and you try to quit.
I7guy
macrumors Westmere
As stated earlier you have no proof that Apple isn’t keeping the feedback entry open for reasons of their own choosing. A sample size of one turning into “proof” is not the way things work. And this is (part of) the reason this thread is so long.
[doublepost=1510067772][/doublepost]
Yes, I need to find a site that allows anonymous posting.
Why did Apple close all my bug entries and keep only this one open? All bug fixes were closed.
Post it here
http://www.videosprout.com/
I will point out the delay to you.
simonmet
Cancelled
This video is not terribly informative without knowing when you’re pressing the home button. An external camera with microphone near the home button would be better.
For the record I tried replicating your video. The delay is not present or very minimal when opening apps if you click to go home very quickly and before it’s zoomed to full-screen (actually about 3/4 full screen). Once the opening animation reaches 2/3-3/4 complete, the home button is delayed while the animation commits to opening fully, pauses, and then closes again. I believe you can see evidence of this in your video, but again knowing the precise timing of your button presses would be better.
Let me be clear however. I and I think others are not complaining about this particular use case. I’d prefer if no delay existed at all but I’m not terribly bothered because having to close an app so quickly after launching it is a rare action for me.
What does bother me is in general use when closing applications from the full-screen state, an action most of us perform dozens if not hundreds of times a day. In this case I expect the button to respond instantly as it did in iOS 10 and when it doesn’t the delay is even more noticeable and frustrating.
I believe there was evidence posted here that the delay, or animation speeds (or both) which contribute to the overall feeling of responsiveness or sluggishness is even worse on the iPhone 7 than the iPhone 8 for no logical reason whatsoever. The timings are completely artificial. I’m skeptical about Apple’s intentions here. They haven’t come out and given us a single good reason for the change.
I’m glad some or perhaps even most don’t notice it or care, but I do. It’s very annoying to me, to the point that I’d downgrade if I could even if that meant additional security threats. As someone who’s very security and privacy conscious that is telling about the degree to which it annoys me.
I’m going to visit the Apple shop tomorrow to do some testing of my own.
Last edited:
Certainly no less proof than has been provided to say that it's a deliberate issue that was introduced just to sell more new phones.
[doublepost=1510070093][/doublepost]
And as stated before simply because it's still open doesn't mean that any decisions about it have been made or that it has been looked at and reviewed on a level beyond simply initial review of it.
simonmet
Cancelled
I know right. How hard is it to put in an extra option somewhere deep in accessibility settings to keep a few of us happy? Probably only a couple of lines of code required! 🙁
- Status