wait, was this mentioned somewhere?
anyway, some homescreen customizations are more than welcomed...
You are never going to see anything as radical as changing the home screen set up in a point release. Add that to your wish list for next June.
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.
iOS 17 Speculation Thread
- Thread starter Kylo83
- Start date
- Sort by reaction score
You are never going to see anything as radical as changing the home screen set up in a point release. Add that to your wish list for next June.
Definitely not a .x update... Apple would want to show that off on stage as if it was something revolutionary for a brand new iOS release.
Thought it was just me and my internet connection at work. mine went from 4 hours to 6 hours.
My internet is slow. Cellular data doesn’t take as long but still slow.
It is, it’s in the code, just not enabled for Devs in B1, and MKBHD has a version of WatchOS 10.1 beta that’s got the code enabled, so he can test and review it.
Yeah, my point is that we can't try it yet. Who cares if some of the code is in the beta? If you want to try Double Tap, don't both loading 10.1 beta 1.
The entire code is in there, and seeing as a version of the beta given out to certain people has it enabled, means it’s coming as part of 10.1 - various outlets also confirm this.
So, we’ll see it enabled for devs in one of the next betas.
I never specified it was enabled in beta 1 in my OP, so make sure you hear my post in mind in the right context, instead of your misdirected context. Thanks.
We can agree that 10.1 is slated to bring Double Tap. Your first post saying "10.1 brings double tap to new watches", makes it sound like it's here. My first reply simply clarified that it's not here yet, so people wouldn't download Beta 1 thinking they would get Double Tap.
There's nothing to argue about here. Beta 1 doesn't have Double Tap. In later beta's, 10.1 will probably enable Double Tap. For folks that don't want to risk a Beta 1 release, for no reason, there are no cool functions worth upgrading for yet.
My post never specified that it came with Beta 1, just that 10.1 brings it, so without a suffix, my post is clear that it’s public release.
You’ve misrepresented my post by adding the implication that I’m saying it’s with Beta 1, i don’t take kindly to people that do that to me.
Yes considering the iPhone 15 and 15 Pro are a week old as of tomorrow and there are still numerous unpatched bugs I think it would be prudent of apple to issue a 17.0.3. Not a good look for your brand new flagship device to have so many problems, and have them completely unaddressed/unacknowledged for a week straight.
People apparently can’t even get ringtones to work after they’ve been working fine for years? Ringtones! On a phone!
I remember a time when cellphones ONLY did ringtones and you were lucky if it was even capable of doing that. Somehow they managed to screw up the most basic core functionality of a phone, the part where it rings. Go figure.
Yup, saw some users trying to downgrade from 17.1. Try to get the MobileDevice.pkg from latest Xcode and try again
The original iPhone 15 17.0.2 yes, but the all iphone release 17.0.2 was two days ago.