There is a bug, the iPhone XS is randomly shutting off !
How is your battery? Could it be the battery not able to hold the iPhone up if you force the max performance?
No problems here on XS Max
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.
All Devices iOS 13.1 Beta 1 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
How is your battery? Could it be the battery not able to hold the iPhone up if you force the max performance?
No problems here on XS Max
Lol
Charles and I compared notes over Twitter (really) on Thursday after his Medium post. He has definitely fleshed out the idea I posted about an hour after launch. Quite plausible.
I will bet that no one here actually knows. How’s that for a bet?
If my theory about 13.0/13.1 is correct (short version: 13.1 is the REAL 13.0 due to need to ship iPhones early*), perhaps a more useful way to view what has happened is to think of 13.1 as 13.0+.
Unlike a traditional x.1 , which is released (even as a beta) after the x.0 version is released and usually contains as many bug fixes or more than new features, 13.1 seem more like a “continuation” of 13.0. Hence, my thinking that it really is the version that will be released
Consider:
-13.1 beta 1 was released before release of final 13.0. Unprecedented.
-Apple issued no cautionary “don’t download this beta if you want to be able to restore a backup to the release version of 13.0 on iPhone 11 launch” - type warning. They could easily have explained themselves, and told anyone who is not using a dedicated development device not to install 13.1.
-There is no (current) feasible way to get 13.1 beta testers (which are now both developers and the public) back onto a track that will make “switching tracks” to a putative 13.0 GM (not impossible, but practically so without playing with build numbers or creating some sort of new profile).
-To all appearances, 13.1 doesn’t do anything that would indicate a break with 13.0, but rather just further development and refinement of 13.0 (adding back in previously disabled features, primarily). It is the latter (the re-added features) that require the x.1 (vs x.0.1) designation, as some have argued.
-If this is the case, you can throw out the normal beta development cycle as an analog. In fact, the quick release of a public beta argues for this point.
Using the principle of “the simplest solution is most frequently the correct solution”, the most likely interpretation is that Apple intends to release 13.1 to the public on existing devices and will offer it as a launch day upgrade to the new iPhones. If we get a 2nd DB/PB this week, that would largely confirm this theory.
*The need to “fork” the development of iOS 13 is probably necessitated by a need to produce and ship phones early due to tariff considerations. Those phones have to have iOS 13 installed when they leave China. iOS 13.0 is that version. But the state iOS 13 it was in when these phones needed to have it installed was not the state Apple wanted to have ready for iPhone launch.
What to do?
Install the best available portions of iOS 13 on the shipped phones and continue development from that point under the aegis of iOS 13.1. That would then be ready to install ecosystem wide on iPhone launch day.
Problem solved!
It would be very interesting to go back and review Trump’s China tweets in the week or 2 preceding the removal of Shortcuts Automation features and Answer with AirPods and see if there were any telltale ones that might have panicked Apple into this move.
Unlike a traditional x.1 , which is released (even as a beta) after the x.0 version is released and usually contains as many bug fixes or more than new features, 13.1 seem more like a “continuation” of 13.0. Hence, my thinking that it really is the version that will be released
Consider:
-13.1 beta 1 was released before release of final 13.0. Unprecedented.
-Apple issued no cautionary “don’t download this beta if you want to be able to restore a backup to the release version of 13.0 on iPhone 11 launch” - type warning. They could easily have explained themselves, and told anyone who is not using a dedicated development device not to install 13.1.
-There is no (current) feasible way to get 13.1 beta testers (which are now both developers and the public) back onto a track that will make “switching tracks” to a putative 13.0 GM (not impossible, but practically so without playing with build numbers or creating some sort of new profile).
-To all appearances, 13.1 doesn’t do anything that would indicate a break with 13.0, but rather just further development and refinement of 13.0 (adding back in previously disabled features, primarily). It is the latter (the re-added features) that require the x.1 (vs x.0.1) designation, as some have argued.
-If this is the case, you can throw out the normal beta development cycle as an analog. In fact, the quick release of a public beta argues for this point.
Using the principle of “the simplest solution is most frequently the correct solution”, the most likely interpretation is that Apple intends to release 13.1 to the public on existing devices and will offer it as a launch day upgrade to the new iPhones. If we get a 2nd DB/PB this week, that would largely confirm this theory.
*The need to “fork” the development of iOS 13 is probably necessitated by a need to produce and ship phones early due to tariff considerations. Those phones have to have iOS 13 installed when they leave China. iOS 13.0 is that version. But the state iOS 13 it was in when these phones needed to have it installed was not the state Apple wanted to have ready for iPhone launch.
What to do?
Install the best available portions of iOS 13 on the shipped phones and continue development from that point under the aegis of iOS 13.1. That would then be ready to install ecosystem wide on iPhone launch day.
Problem solved!
It would be very interesting to go back and review Trump’s China tweets in the week or 2 preceding the removal of Shortcuts Automation features and Answer with AirPods and see if there were any telltale ones that might have panicked Apple into this move.
There was no credit to you in the article I read I’m afraid.
It was in praise of him and his theory.
Let's stipulate that Apple has to accelerate production and shipment of iPhones because of uncertainty regarding tariffs and that these devices all require iOS 13. They would ship with a GM equivalent to a late beta, warts and all.
Why would Apple not just continue development of iOS 13.0 to address bugs and offer a 13.0.x update quickly, rather than releasing 13.1? I haven't installed 13.1 beta 1, but it wouldn't surprise me if the added features introduced yet more bugs. Wouldn't it be safer to just to stay with the usual sequence?
That’s ok. I’m sure he and I were not the only ones to think of this.
Here’s our exchange
As someone (and I apologize for not recalling but it might have been @TimFL1) said over in the Speculation thread, the sheer change in features would require the point, rather than minor, update nomenclature.
Must be a pro only option. Not seeing that in iPad mini 4.
Last edited:
It does but I am finding that to also be inconsistent.
[doublepost=1567388132][/doublepost]
After a full day, Lin the eve I’m down in the pow 20’s instead of 60’s like normal.
The post you quoted was from before the release of the public beta.
This is something that has occurred for myself and my friend since the first betas.
When tapping on a link (for example from a text message), links open in Safari instead of the proper app (Twitter, Reddit, Facebook, etc). I searched and Apple suggests nuking the phone (no thanks), and that was the only response.
Is this happening for anyone else and if so, how’d you fix it?
When tapping on a link (for example from a text message), links open in Safari instead of the proper app (Twitter, Reddit, Facebook, etc). I searched and Apple suggests nuking the phone (no thanks), and that was the only response.
Is this happening for anyone else and if so, how’d you fix it?
For me, this seems somewhat random. I think this is just the beta thing. There was a beta when no link opened the app, it was always Safari. Now, almost always it is the proper app if installed. Rarely does it go to Safari. So I preliminarily conclude this is just random beta thing. Nothing to worry I fancy.
I am not sure what the name of the feature was but in the previous versions if I selected a photo for example to share I was able to see the latest or most used contacts to simply click on to text the photo to. It was basically the first line of the sharing options. Was this taken off in 13.1?
It's broken. If you tried to randomly tap that area, you'll notice the selected preview image shakes. You just have to do it the long way by tapping Messages and type in the contact name.
My thoughts exactly! Say Apple shipped the phones early with “half-baked” iOS 13 (DB6-8) or whatever. It would make more sense (to me) if they just continued improving iOS 13.0 betas, released iOS 13.0 GM on 10 Sep and then everyone getting a new iPhone in late September could just update it straight away to the latest iOS 13.0 variant (which would have been very stable by then). So why create this software confusion late in iOS 13.0 beta cycle?
I was on 13.1 and then I went back to iOS 12.4. Am I going crazy or the brightness is stronger on iOS 13? I always have it on 50% untill I need more, depending where I am, inside or outside, and I swear when I had 13, brigtness 50% its brighter than iOS 12.4 50%