Moderator Note:
This is a warning, the thread will be shut down if the personal bickering continues.
This is a warning, the thread will be shut down if the personal bickering continues.
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
you mean, you'll keep at it until you get what you want, even if that's not possible? what if you're (gasp) wrong? seems it's all about you, and not the issue at all. sigh...
No I wont. I just meant the thread should remain open for those suiffering from the issue. I am getting the X in a few weeks which should sort out all my problems. I will probably keep my 7 Plus as a backup for when I want to consume media or trade it if I like the X a lot. If there are 2 things I am OCD about, its performance and displays on smartphones. I just dont like the fact that a 1k phone feels more sluggish due to home button delays than a Moto G5s. This is unacceptable to me. I would rather spend money and get the experience I want than deal with a slow device all day. I notice this home button lag every time I use my phone and my iPad home button being instant doesnt help any. It drives me up the wall when I pick up my phone. Apple has ruined the experience for me on iOS 11.
Last edited:
or you're obsessing over a minute detail, when there are other qualities with your iphone that you could be enjoying. nothing's perfect... so there will always be things you like (and don't like) about whatever phone/os you use. maybe that's something to consider, and you can let this go (since you're not converting anyone to your viewpoint, and we all just go around in circles in this thread).
Yeah I am eager to find out too. Will report my opinion once I get it hopefully on Nov 4.
Don't you guys think it will be instant? I mean as soon as it detects you swiping up it should be instantly responsive and closing the app. I don't see it any other way really. There will be no reason for it to wait for anything since you will slide up slightly and hold to enter multitasking.
The delay will be in switching to multitasking since it will have to wait and see if you just wanted to go home (swipe up) or go to multitasking (swipe up and pause). Same "problem" (sic) but other way around.
Hmmm. The way i saw it when demoed on stage was where Craig just smoothly closed the app and there was no waiting going on. Only if he held the animation half way through the close then multitasking popped up. But it will be interesting to see.
That's already slower than the button to actually enter multitasking.
[doublepost=1508784053][/doublepost]
Yes, exactly. Closing will be faster, multitasking will have to pause long enough to see if you just let your finger linger a little too long or actually want to enter multitasking. If it doesn't wait long enough to make the distinction then it will do the wrong thing.
It used to be slower before they removed it but lately I find it faster to enter multi tasking that way because I don't need to stretch my thumb to the button. Also I can switch to my previous app much faster than with the app switcher. Thats just me though.
I always thought it was an intentional delay because the iPhone’s listening in to see if you’re going to click the Home Button a second time to enter the multitasking switcher. Try this out as proof:
1. Make sure that you have no accessibility shortcuts enabled.
2. Double-click the Home Button and note how quickly it enters the switcher.
3. Now enable an accessibility shortcut that’s activated by triple-clicking the Home Button.
4. Double-click the Home Button and note how long it takes to enter the multitasking switcher.
You’ll probably find that there is now a ~1 second delay added when double-clicking the Home Button. This is because iOS expects you to possibly click the Home Button a third time and so it gives you a small delay for that to happen.
1. Make sure that you have no accessibility shortcuts enabled.
2. Double-click the Home Button and note how quickly it enters the switcher.
3. Now enable an accessibility shortcut that’s activated by triple-clicking the Home Button.
4. Double-click the Home Button and note how long it takes to enter the multitasking switcher.
You’ll probably find that there is now a ~1 second delay added when double-clicking the Home Button. This is because iOS expects you to possibly click the Home Button a third time and so it gives you a small delay for that to happen.
I am OCD about these things. The display and performance. I have the money but don't have the patience to deal with it. If X is the only way to solve the home button lag I will get it. I can even tolerate stuttering and battery drain somewhat. But I cannot tolerate input lag.
[doublepost=1508824396][/doublepost]Look at the Pixel 2's home button especially in the second round below. Then look at the iPhone. It's really abysmal.
Look at how snappy the Pixel is with those animations. Now that's what I call speed.
Last edited:
Yeah. Although Pixel could have easily won the overall test if it had 6GB RAM like the Note 8. I bet the Pixel 2 has a chance at beating the non Plus iPhone 8 as it comes with 2GB RAM and will need to reload more apps in the background. The video makes it clear 3GB RAM iPhones are faltering on iOS 11. This is also replicated in EvrythingApplePro’s Pixel 2 XL vs iPhone 8 Plus tests. Makes me wonder if the 8 and 8 Plus and X are getting the iPhone 6 treatment and when iPhones with 4GB RAM launch next year they will become obsolete in the same way Apple did the 6
Apple has done a lot of cost control even on the X by not fitting it with 4GB RAM, not including a fast charger or giving it 128GB base storage. Also in typical Apple fashion, watch the X Plus next year get exclusive features which the X won’t get next year despite its high price point because it is a smaller device.
This purposely holding back of features is a hallmark of Apple engineering. We are all familiar with it and have almost got used to it. I skipped iPad 3, iPad Air 1, iPhone 4, iPhone 6 because of reading comments on MacRumors. We members here can foresee what John Doe salivating in Apple store cannot see.
Just like new teething problems are coming out almost on daily basis regarding Pixel 2 devices, I wouldn't be surprised about random problems with iPhone X. I always skip first generation products like iPhone X and I suggest you to skip it too since even you have pointed out the 3GB RAM problem in it.
But purposely slowing down an existing home button by Apple is taking things to next level. This thread is the best we can do to get Apple's attention. Instead we get some stupid GPU benchmark to prove that PO does not exist. Welcome to the circus!
you said 'we' but am sure you meant 'I', since you, of course, don't speak for everyone on these forums. welcome to the circus... agreed!
Apple had 1gb of ram for 3 generations, I expect 3gb to be here for at least another iPhone next year.
As far as holding back I suppose it’s better than the “include it and obsolete it” the next year mentality of android of which Samsung leads the pack with that philosophy.
As far as slowing down the home button, I’m trying hard to see where to slow at all but so far the response is fast.
Maybe Apple will fix it for you, maybe they won’t.
I would pay money to be back on the "obsolete" last version of iOS without the home button delay, battery drain and stuttering. Also Apple just dropped a useful feature on the iPhonme AKA TouchID
Last edited:
What stuttering are you getting? 11.1 Beta 5 is pretty damn smooth on my 7 +.
- Status