Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
iOS 13.1 is a battery killer on my iPhone XR.

With iOS13 I have to charge my iPhone once in the night. With iOS13.1 I have to charge my iPhone three times a day.

I know it‘s a Beta and there are a lot of debug routines in the background with extrem high battery consumption.
 
  • Like
Reactions: iL15hts
iOS 13.1 is a battery killer on my iPhone XR.

With iOS13 I have to charge my iPhone once in the night. With iOS13.1 I have to charge my iPhone three times a day.

I know it‘s a Beta and there are a lot of debug routines in the background with extrem high battery consumption.

I actually downgraded to 13.0 beta 8 for this reason.
 
  • Like
Reactions: lancastor
iOS 13.1 is a battery killer on my iPhone XR.

With iOS13 I have to charge my iPhone once in the night. With iOS13.1 I have to charge my iPhone three times a day.

I know it‘s a Beta and there are a lot of debug routines in the background with extrem high battery consumption.

My XR is going on 24hrs and at 72%. Not exactly being killed by 13.1b1.
 
  • Like
Reactions: mofoliar
Not sure what apple is doing, but this far into the summer with GM supposed to be out in 2-3 weeks it is worrisome how unready IOS13 appears to be (and yes I understand it is a beta).
iOS 13 and iPadOS 13 are the worst updates ever. So many bugs. It’s also hard to use the keyboard because it’s always changing the words into strange ones.
 
  • Like
Reactions: Premium1
iOS 13 and iPadOS 13 are the worst updates ever. So many bugs. It’s also hard to use the keyboard because it’s always changing the words into strange ones.


I wouldn’t say they’re the worst updates ever.. Bugs are to be expected in beta software. There’s extra bits included for testing that won’t be present in an official build for the masses. It’s like this every year, albeit this year WAY worse than I can remember. What I’m bummed about is the placement of selections in core apps like Mail. And I know many many people have filed their radars, and nothing’s changed in iOS 13.1, and to me that’s the worst. Or removing the option to have the Temperature from a Hue Motion Sensor as a Favorite in HomeKit- just the whole accessory now instead. Lame. Unless that’s due to Philips not being able to submit for a fix due to their being beta stuff in it. But the mail app, tho.. I like the new Share Sheet style one tap for all type of thing. Just seems weird having all that wasted space in the bottom left. Definitely not the worst update, just how poorly it’s still behaving is the worst. Bugs are things that have to be fixed. The placement of icons or newly introduced behaviors aren’t changing any time soon unfortunately.
 
I wouldn’t say they’re the worst updates ever.. Bugs are to be expected in beta software. There’s extra bits included for testing that won’t be present in an official build for the masses. It’s like this every year, albeit this year WAY worse than I can remember. What I’m bummed about is the placement of selections in core apps like Mail. And I know many many people have filed their radars, and nothing’s changed in iOS 13.1, and to me that’s the worst. Or removing the option to have the Temperature from a Hue Motion Sensor as a Favorite in HomeKit- just the whole accessory now instead. Lame. Unless that’s due to Philips not being able to submit for a fix due to their being beta stuff in it. But the mail app, tho.. I like the new Share Sheet style one tap for all type of thing. Just seems weird having all that wasted space in the bottom left. Definitely not the worst update, just how poorly it’s still behaving is the worst. Bugs are things that have to be fixed. The placement of icons or newly introduced behaviors aren’t changing any time soon unfortunately.

Ive been beta testing since iOS 7 and this is definitely one of the worst years. Normally there's pretty big fixes and reliability one beta to the next. I haven't really seen that much improvement since beta 2 or 3. Same type of bugs still present. Unless they aren't giving us the newest builds where this stuff has been fixed already I hate to see what builds are going to be put into the new devices and what people get updated to once iOS 13 drops for the public masses.
 
Ive been beta testing since iOS 7 and this is definitely one of the worst years. Normally there's pretty big fixes and reliability one beta to the next. I haven't really seen that much improvement since beta 2 or 3. Same type of bugs still present. Unless they aren't giving us the newest builds where this stuff has been fixed already I hate to see what builds are going to be put into the new devices and what people get updated to once iOS 13 drops for the public masses.

Oh I agree! I’ve been beta testing since around that time, too, and this years betas have been way worse, things not getting addressed that you’d expect to be ironed out pretty quick that aren’t. I don’t build apps, but I work in IT at a large hospital and I am REALLY not looking forward to when this is released. Too many changes that need explaining that just shouldn’t need to be explained, let alone all of the issues that still remain after all this time submitting bug reports with seemingly nothing being addressed (other than being able to edit the options in Share Sheet).
 
You're warned to not install betas on primary / critical devices. Take heed next time.

True. However, I was running IOS 13.0 Beta 7. It updated to IOS 13.1 on its own. Had I known, I would have uninstalled the beta profile and waited for the GM. I didn't install 13.0 on my phone until Beta 5.

And on another note, the ringer actually started working as it should. Not sure if Apple pushed an update within the last 24 hours, but it appears to be a moot point. It was odd.
 
True. However, I was running IOS 13.0 Beta 7. It updated to IOS 13.1 on its own. Had I known, I would have uninstalled the beta profile and waited for the GM. I didn't install 13.0 on my phone until Beta 5.

And on another note, the ringer actually started working as it should. Not sure if Apple pushed an update within the last 24 hours, but it appears to be a moot point. It was odd.


I find it hilarious that people in these here forums always go for the “You should not install betas on devices you need” line right away as opposed to actually providing any insight. Who’s the one wasting time here, the one pointing a problem or the one saying I told you so?
 
I find it hilarious that people in these here forums always go for the “You should not install betas on devices you need” line right away as opposed to actually providing any insight. Who’s the one wasting time here, the one pointing a problem or the one saying I told you so?

What insight are you expecting? We aren’t Apple engineers.
 
  • Like
Reactions: Codeigniter
Interesting theory from Tech Journalist Charles Arthur (
@charlesarthur) who speculates on the reason why Apple abruptly ended the iOS 13 Beta and changed to 13.1

We all know the iOS 13.x Betas have been and remain far from the finished article.

This journalist suggests the reason Apple stopped testing of iOS 13 whilst in such a poor state was due to new iPhone production timescales.

He believes, with the confusion emanating from the White House regarding tariffs, that Apple have taken the decision to manufacture far more new models than planned in order to stockpile these Stateside and potentially avoid tariffs on the units.

Apple are gambling that even though they know the iOS 13 installed on these new devices is nowhere near the standard expected, that they will be able to quickly follow it up with a more polished 13.1 release.

As I say, an interesting theory and very plausible in the current political climate.
 
Had a chance to compare 3D Touch between iPhone 7 on 12.4 and iPhone 8 on 13.1 beta.

I personally feel that 3D Touch requires more pressure on iPhone 7 on 12.4 even on the lightest setting than it does on iPhone 8 on 13.1 on the lightest setting.

I like the implementation on 13.1 more now.
 
  • Like
Reactions: adrianlondon
Interesting theory from Tech Journalist Charles Arthur (
@charlesarthur) who speculates on the reason why Apple abruptly ended the iOS 13 Beta and changed to 13.1

We all know the iOS 13.x Betas have been and remain far from the finished article.

This journalist suggests the reason Apple stopped testing of iOS 13 whilst in such a poor state was due to new iPhone production timescales.

He believes, with the confusion emanating from the White House regarding tariffs, that Apple have taken the decision to manufacture far more new models than planned in order to stockpile these Stateside and potentially avoid tariffs on the units.

Apple are gambling that even though they know the iOS 13 installed on these new devices is nowhere near the standard expected, that they will be able to quickly follow it up with a more polished 13.1 release.

As I say, an interesting theory and very plausible in the current political climate.

He must be reading these forums, that theory was suggested here last week.


My (very preliminary) theory: With the trade war between the US and China, Apple possibly has already built and shipped its launch batch of iPhones (normally, that would still be 2 weeks from now). Those had to have iOS 13 on them when they shipped, so they installed a build we've already seen. They will hit the shelves on Sept 20 and iOS 13.1 will be ready for them to update then or shortly after.

This may also explain some things, such as why items like automations were removed. If it wasn't ready for prime time during the beta prior to when they were removed, they were taken out. That way, if Apple did pull the trigger on early shipment, they wouldn't be caught with half-baked software.
 
More than 10 people submitted the same feedback so it’s less likely how it was phrased, also I gave a detailed description.

I have noticed before that certain apps (also in iOS 12) purposefully override iPhone’s brightness and bring it to the maximum. Displaying an EasyJet boarding pass is a good example.
 
I have noticed before that certain apps (also in iOS 12) purposefully override iPhone’s brightness and bring it to the maximum. Displaying an EasyJet boarding pass is a good example.

Yeah like Starbucks app too when making a payment. Howeveeer this happens to me when just checking my notifications in the middle of the night
 
Is there a way to manually refresh device’s location in the new Find My app? There used to be a refresh button in the top right corner.
 
I have noticed before that certain apps (also in iOS 12) purposefully override iPhone’s brightness and bring it to the maximum. Displaying an EasyJet boarding pass is a good example.

That’s normal!

If you are showing a boarding card to scan on a barcode/qrcode scanner the max brightness on the screen help the scanner read your screen. Otherwise if you were using low brightness you probably would have to do that manually...

Is just a way to help you and not a system bug or something
 
That’s normal!

If you are showing a boarding card to scan on a barcode/qrcode scanner the max brightness on the screen help the scanner read your screen. Otherwise if you were using low brightness you probably would have to do that manually...

Is just a way to help you and not a system bug or something

I understand this, I was just wondering if the OP had the same issue. Apparently not, as it affects his regular notifications too.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.