Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 15 Speculation Thread

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.
Everyone but one of my friends uses Spotify, and the one that does use Apple Music has this bug, and his phone gets warm when he streams music. It's inexcusable that the company that owns the entire stack (service, software, hardware) can't get it working correctly. My brother also uses Apple Music and has this issue as well. Since the only two people I know that use Apple Music have this issue, it's widespread to me.
 
  • Like
Reactions: Sharkoneau, nortonandreev and Pro_the_legend
ouimetnick said:
Everyone but one of my friends uses Spotify, and the one that does use Apple Music has this bug, and his phone gets warm when he streams music. It's inexcusable that the company that owns the entire stack (service, software, hardware) can't get it working correctly. My brother also uses Apple Music and has this issue as well. Since the only two people I know that use Apple Music have this issue, it's widespread to me.
Click to expand...

I use Apple Music…no issues here.
 
  • Like
Reactions: SaguaroSeven, Ansath, biker74 and 1 other person
aleeexz03 said:
Okay, I hit the wrong topic again, sorry. But I have an iPhone 11, so unfortunately my latest official version is iOS 15.1, and I don't run on beta because there are no stable versions from my point of view.
I hope things return to normal in IOS 15.2, just as they did in IOS 14.
Click to expand...
15.1.1 has been available for a while.

Edit: or is that the one that was released just for the 12 and 13 models? If so, I apologize. It slipped my mind.
 
ouimetnick said:
Everyone but one of my friends uses Spotify, and the one that does use Apple Music has this bug, and his phone gets warm when he streams music. It's inexcusable that the company that owns the entire stack (service, software, hardware) can't get it working correctly. My brother also uses Apple Music and has this issue as well. Since the only two people I know that use Apple Music have this issue, it's widespread to me.
Click to expand...
and it's also there since beta 2.

So like they known the issue for 4 weeks, but they couldn't get to fix it? :eek:
 
ouimetnick said:
Everyone but one of my friends uses Spotify, and the one that does use Apple Music has this bug, and his phone gets warm when he streams music. It's inexcusable that the company that owns the entire stack (service, software, hardware) can't get it working correctly. My brother also uses Apple Music and has this issue as well. Since the only two people I know that use Apple Music have this issue, it's widespread to me.
Click to expand...
No issue here. So it's not as widespread as you claim
 
gwhizkids said:
But that doesn’t equate to having all the developers you need to fix every last little bug.
Click to expand...
In what capacity do you decide what is a “little bug”? You might never use the Music App and it might never be an issue for you and then there’s people like me who listen to music all day and such bug ruins it. Not to mention the long-lasting impact overheating has on the device and its battery.

-
I’m hoping for a final release soon so that the next beta cycle can start.
 
Last edited:
nortonandreev said:
In what capacity do you decide what is a “little bug”? You might never use the Music App and it might never be an issue for you and then there’s people like me who listen to music all day and such bug ruins it. Not to mention the long-lasting impact overheating has on the device and its battery.

-
I’m hoping for a final release soon so that the next beta cycle can start.
Click to expand...

I have a brain. And I use it.

A bug that affects many or affects a major functionality is a “big bug”.

A bug that affects a few or has a relatively low impact equals “little bug”.

You’re a developer, I believe. Do you fix every bug with the same level of urgency?

I don’t think so.
 
  • Like
Reactions: MozMan68
gwhizkids said:
A bug that affects many or affects a major functionality is a “big bug”.

A bug that affects a few or has a relatively low impact equals “little bug”.
Click to expand...
The phone overheating and battery draining faster when listening to music seems like a major bug that affects a major functionality. As of 2019, there were 60M Apple Music subscribers. It’s clear that there are more now, no matter how you look at it - Apple Music is a core service. When the iPhone was announced, it was introduced as a phone, browser, and a player. Currently, the player bit is flawed and I think it’s a big deal in that sense.

gwhizkids said:
You’re a developer, I believe. Do you fix every bug with the same level of urgency?
Click to expand...
I don’t, however, I try to prioritise wisely. If I have a know bug that potentially affects millions of users and could damage the hardware - I will fix this with a priority over introducing new features. However, it’s the new features that matter more when it comes to attracting new users and thus bring more money.
 
Last edited by a moderator:
  • Like
Reactions: Knowlege Bomb and Channelsurfer63
pw5a29 said:
and it's also there since beta 2.

So like they known the issue for 4 weeks, but they couldn't get to fix it? :eek:
Click to expand...

Our dev devices, of which we have about 30, varying iPads & iPhones, only 1 is experiencing the bug. That’s 3% of the devices. Even then, it’s not always happening.

So, they’re aware of it and will fix it, but it’s not a high priority, in comparison to other issues.

Some people are so self centred on here and unaware, or willingly belligerent about how it works in regards to development & bug fixing priorities.
 
  • Like
Reactions: Spocky, Bobout and Pearsey
So back on track….. I’m thinking if it is public release this week, it will come early week. If it is another beta or RC, I’m thinking Weds / Thurs this week.
 
  • Like
Reactions: Pearsey and Robeckhard
Ansath said:
Our dev devices, of which we have about 30, varying iPads & iPhones, only 1 is experiencing the bug. That’s 3% of the devices. Even then, it’s not always happening.

So, they’re aware of it and will fix it, but it’s not a high priority, in comparison to other issues.

Some people are so self centred on here and unaware, or willingly belligerent about how it works in regards to development & bug fixing priorities.
Click to expand...
This is an interesting take.. now it makes me wonder if Apple looks at it this way.. at what percentage of complaints Apple says oh s*it we have an issue and need to fix asap versus its only like above mentioned 3 percent or so we will get around to it ???..I think beta 4 is ready for RC so I speculate RC this week and final release before they go on Holiday break
 
  • Like
Reactions: Pearsey
Personally, I don't think it would release iOS 15.2 with that Apple Music bug. I mean, it's like he's going left to right. It's a service from which they make a lot of money and they wouldn't be stupid enough to lend a hand to the customers for Spotify, the direct competition of Apple Music.
 
nortonandreev said:
The phone overheating and battery draining faster when listening to music seems like a major bug that affects a major functionality. As of 2019, there were 60M Apple Music subscribers. It’s clear that there are more now, no matter how you look at it - Apple Music is a core service. When the iPhone was announced, it was introduced as a phone, browser, and a player. Currently, the player bit is flawed and I think it’s a big deal in that sense.


I don’t, however, I try to prioritise wisely. If I have a know bug that potentially affects millions of users and could damage the hardware - I will fix this with a priority over introducing new features. However, it’s the new features that matter more when it comes to attracting new users and thus bring more money.
Click to expand...

Where are you getting your “affects millions of users” info from? And the jump to the assumption that it is overheating a phone enough to damage the hardware?

The one thing you are correct about, if that was ACTUALLY happening to the point of affecting tens of millions of users to the point that hardware may be damaged, yes, there would be a fix issued immediately.

If it is NOT a major issue, you would issue a statement stating that it is a known issue and will be addressed.
 
  • Like
Reactions: Ansath
I wouldn't be surprised to see an RC version today. Apple I think we can wait for everything haha
however, it will most likely be tomorrow or the day after, if we don't have a final release directly these days.
 
MozMan68 said:
Where are you getting your “affects millions of users” info from? And the jump to the assumption that it is overheating a phone enough to damage the hardware?

The one thing you are correct about, if that was ACTUALLY happening to the point of affecting tens of millions of users to the point that hardware may be damaged, yes, there would be a fix issued immediately.

If it is NOT a major issue, you would issue a statement stating that it is a known issue and will be addressed.
Click to expand...
same happening here - and only way to keep phone Cool is using AC
 
aleeexz03 said:
Personally, I don't think it would release iOS 15.2 with that Apple Music bug. I mean, it's like he's going left to right. It's a service from which they make a lot of money and they wouldn't be stupid enough to lend a hand to the customers for Spotify, the direct competition of Apple Music.
Click to expand...
Exactly. And not with this bug before the Christmas holidays.
 
aleeexz03 said:
Personally, I don't think it would release iOS 15.2 with that Apple Music bug. I mean, it's like he's going left to right. It's a service from which they make a lot of money and they wouldn't be stupid enough to lend a hand to the customers for Spotify, the direct competition of Apple Music.
Click to expand...
They did it before so I wouldn’t be surprised. They released iOS 15.1 with the call dropping bug that was listed as a known issue, then after a few weeks they released 15.1.1 to fix it.
 
tosbsas said:
same happening here - and only way to keep phone Cool is using AC
Click to expand...
Alright! We're up to 2 users. Apple better jump on this.

I get that bugs bug people. But I also get that companies have limited resources, time being among said scarce resources. As I've said before, its a simple equation: how many affected times how serious the bug is is the rough calculation every developer, from Apple on down to the smallest indie developer, needs to use to determine when/if they are going to fix any given bug.
 
  • Haha
  • Like
Reactions: Bobout, mcvaughan, Ansath and 1 other person
gwhizkids said:
Alright! We're up to 2 users. Apple better jump on this.

I get that bugs bug people. But I also get that companies have limited resources, time being among said scarce resources. As I've said before, its a simple equation: how many affected times how serious the bug is is the rough calculation every developer, from Apple on down to the smallest indie developer, needs to use to determine when/if they are going to fix any given bug.
Click to expand...
I can see this argument from both sides. On the one hand, beta testers need to be able to run the gamut with their testing device to isolate as many bugs as possible to be effective in the program and if one application is throwing a wrench in all of that, it should receive priority.

On the other hand, this is supposed to be a testing device and if you're suffering these bugs on your daily driver then you shouldn't be complaining as the warning is right there when you install a beta.

All of that said, now that the auto-brightness bug is resolved beta 4 has been perfect on my 13 Pro and I use Apple Music regularly. No abnormal heat whatsoever.
 
  • Like
Reactions: Pearsey, gwhizkids and NBKindaGirl
Guys, I understand betatesting. Doing it for years now. But a bug in an Apple App is something they should fix fast. Although it affects Users only in certain Situations

And I don’t like those - its a Beta and it only affects a few - coments too much. As they say in German - we are all only cooking with water. So please don’t lecture about the obvious. Thanks
 
Last edited:
tosbsas said:
Guys, I understand betatesting. Doing it for years now. But a bug in an Apple App is something they should fix fast. Although it affects Users only in certain Situations

And I don’t like those - its a Beta and it only affects a few - coments too much. As they say in German - we are all only cooking with water. So please don’t lecture about the obvious. Thanks
Click to expand...
Who's lecturing?
 
  • Like
Reactions: Ansath
tosbsas said:
Guys, I understand betatesting. Doing it for years now. But a bug in an Apple App is something they should fix fast. Although it affects Users only in certain Situations

And I don’t like those - its a Beta and it only affects a few - coments too much. As they say in German - we are all only cooking with water. So please don’t lecture about the obvious. Thanks
Click to expand...
Millions of lines of code and probably thousands of literal bugs. But fix them all! Quickly!

If they did, it would be a first since complex OSes became the norm nearly 50 years ago.

OK, that's it for me on this topic. Back to speculation.
 
  • Like
Reactions: MozMan68, Bobout, mcvaughan and 3 others
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back