Apple confirms iOS 17 fix for overheating iPhones is on the way

There has been much speculation that this could be down to the new
titanium material that is one of the big updates on the iPhone 15 Pro
and iPhone 15 Pro Max. This never made sense to me

Apple has already blamed about a dozen (two dozen?) entities
for the overheating that you repeatedly insisted didn't exist.
About the only thing Apple did not blame - was the titanium.
The real problem is so obvious that even you should figure it out.
*Apple forgot to test the iPhone 15 with iOS 17 on it.*
Again. And again. And again. And again... Apple forgot to test it.
*It's really that simple.*

So you were completely wrong about it being a defect in the iPhone 15
itself, right?

Jolly Roger

2023-09-30 19:21:24 UTC

There has been much speculation that this could be down to the new
titanium material that is one of the big updates on the iPhone 15
Pro and iPhone 15 Pro Max. This never made sense to me

Apple has already blamed about a dozen (two dozen?) entities for the
overheating that you repeatedly insisted didn't exist.

Blatant lie. Apple hasn't blamed anyone, and in fact this is their first
public statement about the issue.

[the rest of your weak drivel ignored]

Your trolls are as weak as your feeble mind, Arlen.

Post by Alan
So you were completely wrong about it being a defect in the iPhone 15
itself, right?

Squirm, Arlen... Squirm.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Alan

2023-09-30 19:24:55 UTC

There has been much speculation that this could be down to the new
titanium material that is one of the big updates on the iPhone 15
Pro and iPhone 15 Pro Max. This never made sense to me

Apple has already blamed about a dozen (two dozen?) entities for the
overheating that you repeatedly insisted didn't exist.

Blatant lie. Apple hasn't blamed anyone, and in fact this is their first
public statement about the issue.
[the rest of your weak drivel ignored]
Your trolls are as weak as your feeble mind, Arlen.

Post by Alan
So you were completely wrong about it being a defect in the iPhone 15
itself, right?

Squirm, Arlen... Squirm.

Isn't it amazing how the "man" who claims he only writes facts...

...so often writes bullshit...

...and then crawls away?

:-)

Wally J

2023-09-30 19:33:10 UTC

Post by Jolly Roger
Apple hasn't blamed anyone, and in fact this is their first
public statement about the issue.

Hi Jolly Roger,

What's consistent isn't so much Apple is incompetent at design, but that
Apple is so insecure about their incompetence that they blame everyone.

You yourself just said Apple blamed Instagram, Apple blamed iOS 17, Apple
blamed indexing, Apple blamed everything except the titanium, Jolly Roger.

It's _always_ the same with Apple... blaming everyone but Apple.
"You're holding it wrong!"

The real problem is the same today as it was in all the years past.
*Apple has never sufficiently tested _anything_ that they sell*

It's a proven fact now given Apple themselves clearly stated they forgot to
test the iPhone for the dozen or so things that they blamed caused it.

--
What's consistent isn't so much Apple is incompetent at design, but that
Apple is so insecure about their incompetence that they blame everyone.

Alan

2023-09-30 19:34:24 UTC

Post by Jolly Roger
Apple hasn't blamed anyone, and in fact this is their first
public statement about the issue.

Hi Jolly Roger,
What's consistent isn't so much Apple is incompetent at design, but that
Apple is so insecure about their incompetence that they blame everyone.
You yourself just said Apple blamed Instagram, Apple blamed iOS 17, Apple
blamed indexing, Apple blamed everything except the titanium, Jolly Roger.
It's _always_ the same with Apple... blaming everyone but Apple.
"You're holding it wrong!"
The real problem is the same today as it was in all the years past.
*Apple has never sufficiently tested _anything_ that they sell*
It's a proven fact...

That you claimed it was a defect with the phone.

Do you deny it, Arlen?

Jolly Roger

2023-09-30 20:10:43 UTC

Apple hasn't blamed anyone, and in fact this is their first public
statement about the issue.

Hi Jolly Roger,

Eat shit, Arlen. 🙂

Post by Wally J
You yourself just said Apple blamed Instagram

Actually, the record shows I *never* said that. i
You did, though.

Post by Wally J
Apple blamed iOS 17

I also never said that.
You did, though.

And was it wrong of Apple to identify a bug in its on operating system
that contributed to excess heat generation in your dimwit opinion? 🤣

Post by Wally J
Apple blamed indexing

I never said that either.
You did, though.

Post by Wally J
Apple blamed everything except the titanium, Jolly Roger.

Explaining the cause of the problem and promising a software update to
fix the software defect isn't "blaming", little Arlen.

Post by Wally J
It's _always_ the same with Apple... blaming everyone but Apple.
"You're holding it wrong!"

Apple *literally* said the issue is a software defect in iOS along with
software defects in certain popular third-party apps.

Your lies are both weak and boring, little Arlen.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-09-30 20:23:53 UTC

Post by Jolly Roger
Eat shit

Such an adult response to the fact that Apple forgot to test it (again).

Post by Jolly Roger
Explaining the cause of the problem and promising a software update to
fix the software defect isn't "blaming"

Only badgolferman noticed (so far) that Apple blamed everyone but
Apple - and worse - Apple's blame was so sweeping it spanned the gamut
of possibilities - from the operating system to the apps on the phone.

All of which existed _before_ Apple sold the defective phone to customers.

Post by Wally J
It's _always_ the same with Apple... blaming everyone but Apple.
"You're holding it wrong!"

Apple *literally* said the issue is a software defect in iOS along with
software defects in certain popular third-party apps.

Everything Apple blamed existed _before_ Apple sold the defective device.
*That's a fact*, Jolly Roger... is it not?

Post by Jolly Roger
Your lies are both weak and boring

It's always the case that iKooks call all facts about Apple, lies, JR.

Jolly Roger

2023-09-30 20:37:14 UTC

Post by Jolly Roger
Eat shit

Such an adult response

Your personal insults don't count, huh? Yeah, nah.

Post by Jolly Roger
Explaining the cause of the problem and promising a software update
to fix the software defect isn't "blaming"

Apple blamed everyone but Apple

That's a lie. Apple *literally* listed a bug in iOS 17 as one of the
causes in its official statement. The reason you are harping on this
"blame everyone else" false narrative is you *desperately* want to
deflect from the FACT that you and your little troll gang wrongly
claimed it was a *hardware* defect.

You're all a bunch of *clowns*. 🤣

Post by Jolly Roger
Apple *literally* said the issue is a software defect in iOS along
with software defects in certain popular third-party apps.

Everything Apple blamed

Apple didn't blame. They simply explained the cause and promised a fix.

Eat the shit you spew, Arlen. 🙂

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 06:10:44 UTC

Post by Wally J
Everything Apple blamed

Apple didn't blame. They simply explained the cause and promised a fix.

I'm going to ask _adult_ questions of you, Jolly Roger... is that OK?

I wonder if it ever occurs to you that Apple clearly never sufficiently
tested the defective iPhone 15 until the shit hit the fan in the news.

When Apple was forced to test the defective iPhone 15 sufficiently...
Then Apple found a ton of things that were causing the overheating problem.

It doesn't even occur to you, Jolly Roger... that this is what happened?

Wally J

2023-09-30 19:43:21 UTC

I never said this issue didn't exist.

The real problem is the same today as it was in all the years past.
*Apple has never sufficiently tested _anything_ that they sell*

I wonder if it occurs to you, Jolly Roger, that Apple _blamed_ about a
dozen (or so) entities - all of which existed prior to the release.

So tell us all, Jolly Roger... since you seem to know so much about Apple.

*Why do _you_ think Apple forgot to test it in the real world?*

Again.

Alan

2023-09-30 19:45:03 UTC

I never said this issue didn't exist.

The real problem is...

...that you're nothing but a little weasel?

:-)

Jolly Roger

2023-09-30 20:11:39 UTC

I never said this issue didn't exist.

The real problem

is that your lies are *easily* disproved.

Your trolls are weak.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-09-30 20:27:40 UTC

Post by Wally J
The real problem

is that your lies are *easily* disproved.

It's no longer shocking iKooks call all facts about Apple, lies.

Only badgolferman noticed (so far) that Apple blamed everyone but
Apple - and worse - Apple's blame was so sweeping it spanned the gamut
of possibilities - from the operating system to the apps on the phone.

All of which existed _before_ Apple sold the defective phone to customers.

Everything Apple blamed existed _before_ Apple sold the defective device.
*That's a fact*, Jolly Roger... is it not?

Would Apple have sold the defective iPhone 15 had they fully tested it?

Alan

2023-09-30 20:30:10 UTC

Post by Wally J
The real problem

is that your lies are *easily* disproved.

Apple admitted that there was a bug in iOS 17...

...so you're just lying again.

Post by Wally J
All of which existed _before_ Apple sold the defective phone to customers.

And you've just lied by pretending you don't know the defect wasn't in
the phone.

Post by Wally J
Everything Apple blamed existed _before_ Apple sold the defective device.
*That's a fact*, Jolly Roger... is it not?
Would Apple have sold the defective iPhone 15 had they fully tested it?

And again, and again.

Jolly Roger

2023-09-30 20:40:17 UTC

Post by Wally J
The real problem

is that your lies are *easily* disproved.

facts about Apple

You have a proven track record of an inability to discern opinion from
fact, Arlen. Your trolls are weak.

Post by Wally J
the defective iPhone 15

Still repeating that obvious lie. God, you're boring.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-09-30 21:42:09 UTC

Post by Wally J
facts about Apple

You have a proven track record of an inability to discern opinion from
fact

And yet, it's obvious that Apple did not sufficiently test the defective
iPhone 15 under the rather common circumstances you said Apple blamed.

Jolly Roger

2023-09-30 22:01:28 UTC

Post by Wally J
facts about Apple

You have a proven track record of an inability to discern opinion
from fact

the defective iPhone 15i

False.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 06:15:01 UTC

the defective iPhone 15i

False.

Hmmmm... if Apple sold it... and if someone bought it... and if it
overheats simply when that someone uses it or even just charges it...
then it's defective.

The fact it's overheating is what makes what they bought defective.

Alan

2023-10-01 07:27:21 UTC

the defective iPhone 15i

False.

Hmmmm... if Apple sold it... and if someone bought it... and if it
overheats simply when that someone uses it or even just charges it...
then it's defective.
The fact it's overheating is what makes what they bought defective.

Not the phone...

...which is what you claimed (while also claiming that you only write
facts).

Wally J

2023-09-30 19:49:44 UTC

The vague description of the problem will lead to a vague description of
the solution.
iOS 17 has been installed on my work iPhone 11 and I haven¢t noticed any
problems, but then I only use Outlook to view email.
iOS 16.7 has been installed on my personal iPhone 14 and I will hold out
for the vague solution to be released.

Hi badgolferman,

If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...

*A pattern emerges*

Do you see the pattern?
I do.

What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).

Right?
That's a fact as had they tested it, this never would have happened.

So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.

Need I elaborate?
I hope not.

Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.

It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.

Apple just blamed a dozen (or so) entities for the problem, right?

Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*

The answer is zero, right?
Right?

Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.

This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*

It's really that simple, is it not?
Do you agree?

Or disagree?
Why or why not?

badgolferman

2023-09-30 20:07:12 UTC

The vague description of the problem will lead to a vague description of
the solution.
iOS 17 has been installed on my work iPhone 11 and I havenąt noticed any
problems, but then I only use Outlook to view email.
iOS 16.7 has been installed on my personal iPhone 14 and I will hold out
for the vague solution to be released.

Hi badgolferman,
If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...
*A pattern emerges*
Do you see the pattern?
I do.
What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).
Right?
That's a fact as had they tested it, this never would have happened.
So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.
Need I elaborate?
I hope not.
Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.
It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.
Apple just blamed a dozen (or so) entities for the problem, right?
Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*
The answer is zero, right?
Right?
Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.
This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Why should they put all those resources into testing their software when
there are millions of people available to do it for free? It’s not like
anyone is going to stop using the iPhone if they found a bug. The only way
most people would drop Apple is if they started losing trust in them…

Alan

2023-09-30 20:24:04 UTC

Hi badgolferman,
If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...
*A pattern emerges*
Do you see the pattern?
I do.
What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).
Right?
That's a fact as had they tested it, this never would have happened.
So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.
Need I elaborate?
I hope not.
Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.
It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.
Apple just blamed a dozen (or so) entities for the problem, right?
Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*
The answer is zero, right?
Right?
Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.
This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

You have it precisely backwards.

It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

badgolferman

2023-09-30 20:46:57 UTC

Hi badgolferman,
If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...
*A pattern emerges*
Do you see the pattern?
I do.
What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).
Right?
That's a fact as had they tested it, this never would have happened.
So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.
Need I elaborate?
I hope not.
Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.
It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.
Apple just blamed a dozen (or so) entities for the problem, right?
Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*
The answer is zero, right?
Right?
Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.
This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

You have it precisely backwards.
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

Thank you for admitting out loud Apple doesn’t test their software.

Jolly Roger

2023-09-30 20:54:44 UTC

Post by badgolferman
Why should they put all those resources into testing their software
when there are millions of people available to do it for free? It’s
not like anyone is going to stop using the iPhone if they found a
bug. The only way most people would drop Apple is if they started
losing trust in them…

You have it precisely backwards.
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

Thank you for admitting out loud Apple doesn’t test their software.

He very clearly didn't say they don't test.

Your trolls are weak.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 19:06:20 UTC

Thank you for admitting out loud Apple doesn¢t test their software.

He very clearly didn't say they don't test.

*Apple themselves openly admitted they didn't test it, JR*

An actual adult would instantly cognate that the iPhones are overheating,
and, when Apple was forced to look at why - Apple found myriad reasons.

The sheer astoundingly huge plethora of reasons Apple provided shows rather
clearly that there is zero chance Apple had ever sufficiently tested them.

Add that obvious fact to the fact that this happens all the time with Apple
such that it's clear Apple did NOT sufficiently test the defective iPhones.

Again.

Alan

2023-10-01 19:07:05 UTC

Thank you for admitting out loud Apple doesn┤ test their software.

He very clearly didn't say they don't test.

*Apple themselves openly admitted they didn't test it, JR*

No, they did not, Clown.

Alan

2023-09-30 21:07:21 UTC

Hi badgolferman,
If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...
*A pattern emerges*
Do you see the pattern?
I do.
What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).
Right?
That's a fact as had they tested it, this never would have happened.
So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.
Need I elaborate?
I hope not.
Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.
It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.
Apple just blamed a dozen (or so) entities for the problem, right?
Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*
The answer is zero, right?
Right?
Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.
This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

You have it precisely backwards.
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

Thank you for admitting out loud Apple doesn’t test their software.

I didn't say anything like that.

You're either a liar, or your an idiot...

...and that's not a XOR.

:-)

Jolly Roger

2023-09-30 20:51:06 UTC

You have it precisely backwards.
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

It's very obvious neither badgolferman or Arlen (Wally) have ever worked
professionally in a software team in charge of deploying software to
massive numbers of heterogeneous clients.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 19:09:57 UTC

Post by Alan
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

It's very obvious neither badgolferman or Arlen (Wally) have ever worked
professionally in a software team in charge of deploying software to
massive numbers of heterogeneous clients.

Hehhehheh... ah... but we have.

Both of us have.

With extremely complicated software, Jolly Roger.

It's _you_ who hasn't ever worked with software as complicated as the
military grade stuff both badgolferman and I worked on for decades.

the most complex software you've ever touched, JR, is the toy Apple
operating systems - which have a millionth of the lines of code of teh
stuff badgolferman and I worked on for decades.

It's funny though that you think because we understand what happened, and
because you _hate_ what happened, that you blame us for what Apple did.

More to the point - you blame us for what Apple did NOT do.
*HINT: Apple forgot to sufficiently test the defective iPhones*

Again.

Jolly Roger

2023-10-01 20:14:20 UTC

Post by Alan
It is because there are "millions of people" using their iPhones in
millions of different ways that there is no possible way that Apple
could test for all possible problems.

It's very obvious neither badgolferman or Arlen (Wally) have ever
worked professionally in a software team in charge of deploying
software to massive numbers of heterogeneous clients.

Hehhehheh... ah... but we have.
Both of us have.

No, you very clearly haven't.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 21:13:44 UTC

Post by Jolly Roger
No, you very clearly haven't.

Well, both badgolferman and I have said we've worked on military grade
software for decades but you can choose to disbelieve what we say.

What you can't say is that we don't understand what happened, which is
a. Apple forgot to test the iPhone 15 for causes of overheating
b. When the shit hit the fan - only then did Apple bother to test it
c. After testing - Apple said it was tons (and tons!) of things that did it

Meaning...

*Apple forgot to sufficiently test the iPhone*

Again.

Worse...

*Apple is almost certainly going to decrease performance*

Because... (you fill in the blanks, Jolly Roger)...

ADULT QUESTION FOR JOLLY ROGER:

*How will Apple lower heat output from a CPU running too fast?*

Alan

2023-10-01 21:38:12 UTC

Post by Jolly Roger
No, you very clearly haven't.

Well, both badgolferman and I have said we've worked on military grade
software for decades but you can choose to disbelieve what we say.

That's convenient, Clown...

...because we do so choose.

Alan Browne

2023-10-01 21:50:21 UTC

Post by Jolly Roger
No, you very clearly haven't.

Well, both badgolferman and I have said we've worked on military grade
software for decades but you can choose to disbelieve what we say.

That's convenient, Clown...
...because we do so choose.

Using terms like "military grade software" is a red flag.

There is a way to say what he desperately wants to convey but since he
said it the way he said it we know it is poppycock (at best).

--
“Markets can remain irrational longer than your can remain solvent.”
- John Maynard Keynes.

Dorper

2023-10-01 23:36:51 UTC

Post by Jolly Roger
No, you very clearly haven't.

Well, both badgolferman and I have said we've worked on military grade
software for decades but you can choose to disbelieve what we say.

That's convenient, Clown...
...because we do so choose.

Using terms like "military grade software" is a red flag.
There is a way to say what he desperately wants to convey but since he
said it the way he said it we know it is poppycock (at best).

Military Grade software does exist. VHDL (MIL-STD-454N) and Ada
(MIL-STD-1815) are examples. But just because something is military grade
doesn't mean it is good. Military grade means it is the cheapest made while
still meeting minimum contract specifications.

Jolly Roger

2023-10-02 00:59:04 UTC

Post by Dorper

Post by Jolly Roger
No, you very clearly haven't.

Well, both badgolferman and I have said we've worked on military
grade software for decades but you can choose to disbelieve what
we say.

That's convenient, Clown...
...because we do so choose.

Using terms like "military grade software" is a red flag.
There is a way to say what he desperately wants to convey but since
he said it the way he said it we know it is poppycock (at best).

Military Grade software does exist. VHDL (MIL-STD-454N) and Ada
(MIL-STD-1815) are examples. But just because something is military
grade doesn't mean it is good. Military grade means it is the cheapest
made while still meeting minimum contract specifications.

The reason Arlen (Wally) is mentioning military grade software is
because he desperately wants to deflect from the original point which is
that Apple deploys complex system and app software to hundreds of
millions of heterogeneous devices regularly, where it is not uncommon
for bugs that affect numerous devices (albeit a relatively small number
of the total deployment base) to be found after release. Arlen and
other regular trolls in the Apple newsgroups repeatedly claim that the
fact that bugs exist in Apple software supposedly means "Apple never
tests their software" (yes, that's a direct quote), which is an
idiotic and baseless claim and completely ignores that Apple's
software teams, like many other large software teams, hold and manage
bug databases and go through traditional alpha and beta testing
phases, including public betas. They claim to know all about software
development, but turn around and claim bugs shouldn't exist. And this
says way more about them than Apple.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

candycanearter07

2023-10-01 21:39:24 UTC

Post by Wally J
It's _you_ who hasn't ever worked with software as complicated as the
military grade stuff both badgolferman and I worked on for decades.

You've coded operating systems?? That's awesome!

--
user <candycane> is generated from /dev/urandom

Jolly Roger

2023-10-02 00:59:38 UTC

Post by Wally J
It's _you_ who hasn't ever worked with software as complicated as the
military grade stuff both badgolferman and I worked on for decades.

You've coded operating systems?? That's awesome!

In his (and your) fevered dreams.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

candycanearter07

2023-09-30 20:28:41 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

--
user <candycane> is generated from /dev/urandom

Alan

2023-09-30 20:44:25 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

Except you have yet to demonstrate that any significant fraction of the
"millions of people" have been impacted by this issue.

Your Name

2023-09-30 23:01:40 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

No computer company on the planet does, nor can, terst their devices
against every single piece of third-party made software and hardware.
It's not remotely sensible for anyone to expect them to either.

badgolferman

2023-09-30 23:33:10 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

Do they test them against the most popular apps as rated on their own App
Store?

Alan

2023-10-01 00:46:06 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

Do they test them against the most popular apps as rated on their own App
Store?

In every possible use case? Probably not.

How could they?

sms

2023-10-01 00:48:50 UTC

Post by badgolferman
Do they test them against the most popular apps as rated on their own App
Store?

That is a good point. This is different than a "computer company" trying
to test "every single piece of third-party made software." The only
software for the iPhone is what is on the App Store. You'd think that
they'd at least test the most-used apps, including Instagram.

--
“If you are not an expert on a subject, then your opinions about it
really do matter less than the opinions of experts. It's not
indoctrination nor elitism. It's just that you don't know as much as
they do about the subject.”—Tin Foil Awards

Alan

2023-10-01 00:55:44 UTC

Post by badgolferman
Do they test them against the most popular apps as rated on their own App
Store?

Who says they didn't?

Jolly Roger

2023-10-01 01:56:48 UTC

Post by badgolferman
Do they test them against the most popular apps as rated on their
own App Store?

That is a good point. This is different than a "computer company"
trying to test "every single piece of third-party made software." The
only software for the iPhone is what is on the App Store. You'd think
that they'd at least test the most-used apps, including Instagram.

Who says they didn't?

These Big Brain clowns clearly think that all bugs are always readily
evident with minimal testing.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Patrick

2023-10-01 19:16:02 UTC

Post by badgolferman
Do they test them against the most popular apps as rated on their own App
Store?

You'd think they'd test not only Instagram, but their own iOS 17 too.
They didn't.

sms

2023-10-01 19:32:26 UTC

Post by badgolferman
Do they test them against the most popular apps as rated on their own App
Store?

That is a good point. This is different than a "computer company"
trying to test "every single piece of third-party made software." The
only software for the iPhone is what is on the App Store. You'd think
that they'd at least test the most-used apps, including Instagram.

You'd think they'd test not only Instagram, but their own iOS 17 too.
They didn't.

iOS 17 has been out for a while. I'm on the Beta program so I've been
running it for quite a while. There haven't been any issues, that I have
heard of, with Instagram running on iOS 17 on earlier iPhone models.

There are definitely some apps out there that will max out the CPU if
they are allowed to do so, even when they are not performing what would
appear to be CPU intensive tasks. Instagram is one such app and it has
the same issue on Android devices.

Apparently there are ways for iOS to prevent excessive CPU usage and
ways to design the app to prevent excessive CPU usage, see
<https://developer.apple.com/forums/thread/123975>. These come at the
expense of performance.

Since it's not possible to check over 1.6 million apps for using
excessive resources the solution is to stop the A17 Bionic from getting
so hot in the first place. Modifying the throttling temperature points
would do this. There's also the issue of the titanium frame having
poorer thermal conductivity which means more heat is being conducted out
through the glass back.

Frankie

2023-10-01 19:59:18 UTC

These come at the expense of performance.

The only way Apple can reduce overheating is at the expense of performance.

Jolly Roger

2023-10-01 20:16:03 UTC

Post by Frankie

These come at the expense of performance.

The only way Apple can reduce overheating is at the expense of
performance.

Yes, yes. Fixing the bug that is causing excess resource usage is not an
option, guys. Frankie says so.

The pure idiocy on display here is staggering.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

sms

2023-10-01 05:32:04 UTC

On 9/30/2023 4:33 PM, badgolferman wrote:

<snip>

Post by badgolferman
Do they test them against the most popular apps as rated on their own App
Store?

What is odd about the "fix" to iOS 17 to address the overheating issue
in the iPhone 15 Pro/Pro Max is that if there really is some kind of a
problem with some of the apps that causes overheating by "overloading
the iPhone CPU" then why isn't the same issue occurring with the iPhone
14 Pro/Pro Max with the A16 Bionic?

It's likely that these apps, whatever they are, are causing the A17
Bionic to run at maximum power which is too much for the thermal
solution in the iPhone 15 Pro/Pro Max to deal with.

It was also odd to see that claim that the titanium frame will conduct
heat out the phone better than the stainless steel frame in the iPhone
14 Pro/Pro Max since titanium is a poorer thermal conductor. And if it
did conduct heat better then the outside of the phone would get even
hotter but the inside would be cooler.

Wally J

2023-10-01 17:40:10 UTC

Post by sms
It's likely that these apps, whatever they are, are causing the A17
Bionic to run at maximum power which is too much for the thermal
solution in the iPhone 15 Pro/Pro Max to deal with.

Apparently no issue that can't be fixed in both iOS and some 3rd party
apps.

We can't count the number of times Apple has released a defective product
which Apple only looked at well _after the shit hit the fan_ in news.

Take the Facetime bugs that a mere kid found. Remember that? When Apple
finally looked at Facetime for the first time - they found scores of holes.

Same thing when Apple finally looked at their defective power-delivery
(where they tried to hide their design incompetence & got caught doing it).

It's no different here in that it's the _same pattern_ Apple always uses.

1. First Apple releases an untested (defective in this case) product.
2. Then, _after_ people pay for it, the shit hits the fan (in the news).
3. Only then does Apple even _bother_ to think about testing the product.

Once Apple takes a quick look at the product, Apple finds issues
_everywhere_ (from Instagram to indexing to iOS 17 to charging, etc.).

Can you believe that?

Everything causes this defective iPhone to overheat according to Apple.
a. Instagram
b. Indexing
c. Charging
d. Gaming
e. Updating
etc.

If _that_ many diverse things cause these defective iPhones to overheat,
then it's pretty darn clear Apple did not sufficiently test the device.

A. Apple belatedly only tested it _after_ the shit hit the fan, and,
B. even then, Apple *blamed everyone but themselves* for the defects.

To an intelligent adult, the source of the defect is patently obvious.
*Apple forgot to test the defective iPhone 15 before selling it*

candycanearter07

2023-10-01 02:55:25 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship
now, fix later is hated by consumers for a reason.

Isn't there only 5-10 models of iphones supported?

--
user <candycane> is generated from /dev/urandom

Alan

2023-10-01 02:59:09 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship
now, fix later is hated by consumers for a reason.

Isn't there only 5-10 models of iphones supported?

You missed half of that sentence:

"against every single piece of third-party made software and hardware"

It's not just the number of iPhones that matters.

Your Name

2023-10-01 04:46:58 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

No computer company on the planet does, nor can, test their devices
against every single piece of third-party made software and hardware.
It's not remotely sensible for anyone to expect them to either.

Isn't there only 5-10 models of iphones supported?

Maybe, and only a couple of models that a few people reporting the heat
problem with ... but there are millions of apps which Apple cannot
possibly test nor be expected to.

Patrick

2023-10-01 19:20:29 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

Isn't there only 5-10 models of iphones supported?

Maybe, and only a couple of models that a few people reporting the heat
problem with ... but there are millions of apps which Apple cannot
possibly test nor be expected to.

Damn Instagram.

Why is it always the app that nobody uses that makes the iPhone overheat.

sms

2023-10-01 20:38:40 UTC

On 10/1/2023 12:20 PM, Patrick wrote:

<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

LOL, here are the iOS apps that are downloaded the most:
1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram

I did see a complaint that Instagram causes Android phones to heat up as
well. It seems like Instagram will just use as much CPU power as it can
get. This is not really a bug in Instagram, the operating system should
be limiting the amount of resources that an app can consume.

Alan Browne

2023-10-01 21:36:00 UTC

Post by sms
<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram
I did see a complaint that Instagram causes Android phones to heat up as
well. It seems like Instagram will just use as much CPU power as it can
get. This is not really a bug in Instagram, the operating system should
be limiting the amount of resources that an app can consume.

Not at all. The OS cannot tell if badly written software is doing
something useless driving up power consumption.

Simple example - if there is a loop that goes

double x = 33333;

while (1) {
x = 4 * atan(1) / (44.7777 / x);
if (x < 0.002) {
x = 33333;
}
}

The OS would not know it was doing useless work and the app would run
until pre-emption ... and resume the endless loop when the thread was
re-turned. This is an over-simplified example but gets to the gist of it.

So a good app would not hog thread time if it had no real work to do,
but instead would call for a Thread Sleep.

In C: usleep(10000); // 10 msec

(Note there are a lot of "sleep" variants depending on platform.

eg: This would likely be: "Thread.sleep(forTimeInterval: 0.010)" in
Swift 2 the iOS "preferred" language)

So, you're talking out of your hat. Again.

--
“Markets can remain irrational longer than your can remain solvent.”
- John Maynard Keynes.

candycanearter07

2023-10-01 21:43:06 UTC

Post by sms
<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram
I did see a complaint that Instagram causes Android phones to heat up
as well. It seems like Instagram will just use as much CPU power as it
can get. This is not really a bug in Instagram, the operating system
should be limiting the amount of resources that an app can consume.

Not at all. The OS cannot tell if badly written software is doing
something useless driving up power consumption.

The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

--
user <candycane> is generated from /dev/urandom

Alan Browne

2023-10-01 21:59:28 UTC

Post by sms
<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram
I did see a complaint that Instagram causes Android phones to heat up
as well. It seems like Instagram will just use as much CPU power as
it can get. This is not really a bug in Instagram, the operating
system should be limiting the amount of resources that an app can
consume.

Not at all. The OS cannot tell if badly written software is doing
something useless driving up power consumption.

The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

Some apps justifiably need a lot of CPU so the OS cannot do more that
allow the app / thread to run its time slice until the slice is over or
pre-empted by something with higher priority for which no other core is
available.

Could one design an OS that applies the rule as you say? Sure. But
that is not the case in general purpose OS'.

Could the OS detect race conditions and kill a thread (or several)?
Probably. My example has no such possible state.

And while my example might be trivial, there are cases where converging
on a solution with many variables can take a hell of a lot of CPU and
time. And it's a very valid thing for a program to do.

The main point is that OS' don't arbitrarily kill processes (or throttle
them) just because a given process is using a lot of CPU.

--
“Markets can remain irrational longer than your can remain solvent.”
- John Maynard Keynes.

candycanearter07

2023-10-01 22:05:14 UTC

Post by sms
<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram
I did see a complaint that Instagram causes Android phones to heat
up as well. It seems like Instagram will just use as much CPU power
as it can get. This is not really a bug in Instagram, the operating
system should be limiting the amount of resources that an app can
consume.

Not at all. The OS cannot tell if badly written software is doing
something useless driving up power consumption.

The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage,
or outright kill it.

Some apps justifiably need a lot of CPU so the OS cannot do more that
allow the app / thread to run its time slice until the slice is over or
pre-empted by something with higher priority for which no other core is
available.
Could one design an OS that applies the rule as you say? Sure. But
that is not the case in general purpose OS'.
Could the OS detect race conditions and kill a thread (or several)?
Probably. My example has no such possible state.
And while my example might be trivial, there are cases where converging
on a solution with many variables can take a hell of a lot of CPU and
time. And it's a very valid thing for a program to do.
The main point is that OS' don't arbitrarily kill processes (or throttle
them) just because a given process is using a lot of CPU.

At the very least, it should warn the user if a program is using a lot.

--
user <candycane> is generated from /dev/urandom

Your Name

2023-10-01 23:54:57 UTC

Post by sms
<snip>

Post by Patrick
Damn Instagram.
Why is it always the app that nobody uses that makes the iPhone overheat.

1. TikTok
2. Instagram
3. Facebook
4. WhatsApp
5. Telegram
I did see a complaint that Instagram causes Android phones to heat up
as well. It seems like Instagram will just use as much CPU power as it
can get. This is not really a bug in Instagram, the operating system
should be limiting the amount of resources that an app can consume.

Not at all. The OS cannot tell if badly written software is doing
something useless driving up power consumption.

The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

Some apps justifiably need a lot of CPU so the OS cannot do more that
allow the app / thread to run its time slice until the slice is over or
pre-empted by something with higher priority for which no other core is
available.
Could one design an OS that applies the rule as you say? Sure. But
that is not the case in general purpose OS'.
Could the OS detect race conditions and kill a thread (or several)?
Probably. My example has no such possible state.
And while my example might be trivial, there are cases where converging
on a solution with many variables can take a hell of a lot of CPU and
time. And it's a very valid thing for a program to do.
The main point is that OS' don't arbitrarily kill processes (or
throttle them) just because a given process is using a lot of CPU.

At the very least, it should warn the user if a program is using a lot.

At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

candycanearter07

2023-10-02 00:09:20 UTC

Post by candycanearter07
At the very least, it should warn the user if a program is using a lot.

At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

While I don't disagree, they should still have some safeguards against
rouge apps.

--
user <candycane> is generated from /dev/urandom

Wolf Greenblatt

2023-10-02 03:48:50 UTC

Post by Your Name
At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

While I don't disagree, they should still have some safeguards against
rouge apps.

Apple marketing has started the new campaign to solve the problem the way
they always have solved any bad press in the news about Apple's product.

First Apple will only admit to "slight warming" of the iPhone 15 series.
Then Apple will "assure the safety" of the new iPhones so rest at ease.

Apple will issue new guidelines explaining not only how to hold it,
but also the types of Apple-approved fire-safe asbestos-free gloves to use.

These new fire-safe iPhone gloves will be called the iGlove, and will
retail for $79.99 USD if you wait outside in line at the Apple Store.

In addition, users will have the opportunity to beta test the new ten-foot
iPole that Apple is selling in various new bold colors like red & yellow.

The new iPoles will be sold for only $39.99 USD so get them now before the
bold color of your choice sells out (Sorry. Not available in plain white.)

Patrick

2023-10-02 03:33:26 UTC

Post by candycanearter07
At the very least, it should warn the user if a program is using a lot.

At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

This idea from Your Name is great as it will instantly solve all of Apple's
overheating iPhone 15 problems while still allowing sales to proceed.

Apple should instantly remove TikTok, Instagram, Facebook, WhatsApp &
Telegram from the App Store (and Apple should remove those installed).

That way Apple doesn't have to do anything else to fix the overheating
phones. Well, there is the problems of indexing and iOS 17 bugs too.

For that, Apple should turn off indexing (what does it do anyway?).
And Apple should allow the overheating iPhones to backport to iOS 16.

Problem solved thanks to Your Name!

Oscar Mayer

2023-10-02 03:42:47 UTC

Post by Your Name
At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

This idea from Your Name is great as it will instantly solve all of Apple's
overheating iPhone 15 problems while still allowing sales to proceed.
Apple should instantly remove TikTok, Instagram, Facebook, WhatsApp &
Telegram from the App Store (and Apple should remove those installed).
That way Apple doesn't have to do anything else to fix the overheating
phones. Well, there is the problems of indexing and iOS 17 bugs too.
For that, Apple should turn off indexing (what does it do anyway?).
And Apple should allow the overheating iPhones to backport to iOS 16.
Problem solved thanks to Your Name!

Good idea. Apple also needs to remove Uber and Asphalt 9 Legends games.
And Apple has to figure out how to turn off charging the iPhone 15 too.

As a side note, Apple has made the unusual admission that their iPhone may
feel slightly warmer but if you stop holding it - you won't feel it at all.

Apple suggests you lay the phone on a flat fire-proof surface and that you
interact with it remotely - they even sell a ten-foot long iStick for that.

Your Name

2023-10-02 05:43:19 UTC

Post by Your Name
At the very least the user should have enough brains not to use utter
crap "Social Media" apps like Instagram. :-p

This idea from Your Name is great as it will instantly solve all of
Apple's overheating iPhone 15 problems while still allowing sales to
proceed.

People not using crappy "Social Media" would solve lots of the world's
problems in one go!

sms

2023-10-02 00:22:58 UTC

Post by candycanearter07
The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

Actually the OS _can_ stop the app from consuming excessive resources by
shutting it down. There have been complaints by developers of this
happening when the app has a legitimate need for those resources.

candycanearter07

2023-10-02 00:41:09 UTC

Post by candycanearter07
The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage,
or outright kill it.

That's what I said?

--
user <candycane> is generated from /dev/urandom

Mickey D

2023-10-02 03:51:27 UTC

Post by candycanearter07
The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

The only way Apple can stop this problem in software is to cut performance.

Alan

2023-10-02 05:39:16 UTC

Post by Mickey D

Post by candycanearter07
The operating system controls thread scheduling and memory. They can
just lower the apps priority if its past a certain usage percentage, or
outright kill it.

The only way Apple can stop this problem in software is to cut performance.

Clown... ...stick to one nym.

Patrick

2023-10-01 19:18:56 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship
now, fix later is hated by consumers for a reason.

Isn't there only 5-10 models of iphones supported?

Not only are there a puny set of models but the software on them is limited
to the App Store where apparently Apple didn't know Instagram even existed.

Alan

2023-10-01 21:37:18 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship
now, fix later is hated by consumers for a reason.

Isn't there only 5-10 models of iphones supported?

Not only are there a puny set of models but the software on them is limited
to the App Store where apparently Apple didn't know Instagram even existed.

Arlen... ...stop changing nyms, you Clown.

Wally J

2023-10-01 19:13:59 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

*All these excuses for a defective product mean Apple forgot to test it.*
*Again*

Maybe Your Name can be excused for ignorance in that Your Name probably
didn't get a chance yet to read all the excuses Apple recently provided.

How many things did Apple blame for the overheating anyway?
*A dozen? Two dozen? Three dozen?*

*How many _different_ things did Apple again forget to test this time?*

Alan

2023-10-01 19:24:06 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

*All these excuses for a defective product mean Apple forgot to test it.*

No, clown.

It doesn't.

candycanearter07

2023-10-01 21:44:16 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

*All these excuses for a defective product mean Apple forgot to test
it.*

No, clown.
It doesn't.

Then how did so much slip through?

--
user <candycane> is generated from /dev/urandom

Alan Browne

2023-10-01 22:00:14 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

*All these excuses for a defective product mean Apple forgot to
test it.*

No, clown.
It doesn't.

Then how did so much slip through?

General purpose appliance for the masses.

It's a miracle so few bugs do.

--
“Markets can remain irrational longer than your can remain solvent.”
- John Maynard Keynes.

Alan

2023-10-01 22:25:28 UTC

Post by candycanearter07
Because people expect polish?? What kind of argument is this? Ship now,
fix later is hated by consumers for a reason.

*All these excuses for a defective product mean Apple forgot to
test it.*

No, clown.
It doesn't.

Then how did so much slip through?

There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.

Agreed?

candycanearter07

2023-10-01 23:04:06 UTC

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

--
user <candycane> is generated from /dev/urandom

Alan

2023-10-01 23:37:48 UTC

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

You're so sure of that, are you?

Your Name

2023-10-01 23:57:18 UTC

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

So far, almost all the people reporting the issue have been reviewers,
many of whom by necessity of the job would be pushing the device to the
limit. There's also the likelihood that some reviewers also got early
production models so they could review the device.

Jolly Roger

2023-10-02 01:05:46 UTC

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

Oh, it's "so many", huh? Go ahead and tell us, oh wise one, what
percentage of the 1+ billion active iPhone users have this issue. 🤡

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Peter

2023-10-02 06:06:14 UTC

candycanearter07 wrote on 02.10.2023 00:04

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

I don't think Alan is correct that Apple "forgot" to test.
Apple consciously decided not to bother wasting the money to test it.

That's different.
It was a conscious decision not to test these iPhones for overheating.

It's clear there was no testing for this widespread overheating problem.
Otherwise it wouldn't be so many situations & so many of them being common.

Anyone saying it was tested has to first read that Apple said almost
everything is causing this overheating - which means they didn't test it.

None of this would have been allowed through had there been any testing.
But there wasn't any testing. That much is clear to everyone. Even Apple.

Alan

2023-10-02 06:11:11 UTC

Post by Peter
candycanearter07 wrote on 02.10.2023 00:04

Post by Alan
There is a difference between not finding a particular issue in
particular circumstances and "forget[ting]" to test.
Agreed?

If so many people have this issue then it would've come up in testing.

I don't think Alan is correct that Apple "forgot" to test.
Apple consciously decided not to bother wasting the money to test it.
That's different.
It was a conscious decision not to test these iPhones for overheating.
It's clear there was no testing for this widespread overheating problem.
Otherwise it wouldn't be so many situations & so many of them being common.
Anyone saying it was tested has to first read that Apple said almost
everything is causing this overheating - which means they didn't test it.
None of this would have been allowed through had there been any testing.
But there wasn't any testing. That much is clear to everyone. Even Apple.

Clown:

Stick...

...to...

...one...

...nym.

sms

2023-10-01 00:11:35 UTC

On 9/30/2023 1:07 PM, badgolferman wrote:

<snip>

Post by badgolferman
Why should they put all those resources into testing their software when
there are millions of people available to do it for free?

<snip>

There is just no way that they could test all the different apps in all
the different usage scenarios. It's expected that there will be issues
that don't turn up until the devices are in the hands of a very large
number of users.

What will be interesting to see is if the A17 benchmarks change once iOS
17 is updated to address overheating. Kuo stated that they'd have to
throttle the CPU in order to address the overheating, in which case the
benchmarks could be affected. "Those who must not be named" insisted
that there is no issue because not every user has reported overheating,
though they now are aware that the issue is real. The truth will come
out soon enough.

Wolf Greenblatt

2023-10-01 19:24:22 UTC

Post by badgolferman
Why should they put all those resources into testing their software when
there are millions of people available to do it for free?

Did you count the number of things that Apple didn't test until now?

Post by sms
What will be interesting to see is if the A17 benchmarks change once iOS
17 is updated to address overheating.

Of course it will.
Apple cares so much about you that they'll again "extend the life" for you.

Post by sms
Kuo stated that they'd have to
throttle the CPU in order to address the overheating, in which case the
benchmarks could be affected.

The benchmarks are bogus.
Even more so now that the iPhone performance will require cutting.

Post by sms
"Those who must not be named" insisted
that there is no issue because not every user has reported overheating,
though they now are aware that the issue is real. The truth will come
out soon enough.

Apple already said they have identified many causes for the overheating.
Which means they are overheating.
Which means anyone saying they're not is disagreeing with Apple's findings.

Alan

2023-10-01 19:26:51 UTC

Post by Wolf Greenblatt

Post by badgolferman
Why should they put all those resources into testing their software when
there are millions of people available to do it for free?

Did you count the number of things that Apple didn't test until now?

Post by sms
What will be interesting to see is if the A17 benchmarks change once iOS
17 is updated to address overheating.

Of course it will.
Apple cares so much about you that they'll again "extend the life" for you.

Post by sms
Kuo stated that they'd have to
throttle the CPU in order to address the overheating, in which case the
benchmarks could be affected.

The benchmarks are bogus.
Even more so now that the iPhone performance will require cutting.

Apple already said they have identified many causes for the overheating.
Which means they are overheating.
Which means anyone saying they're not is disagreeing with Apple's findings.

Except no one has denied that... ...Clown.

Wally J

2023-10-01 16:30:04 UTC

Post by badgolferman
Why should they put all those resources into testing their software when
there are millions of people available to do it for free? It¡Šs not like
anyone is going to stop using the iPhone if they found a bug. The only way
most people would drop Apple is if they started losing trust in them¡K

Hi badgolferman,

I agree with what you have surmised based on current & past Apple history.

To an intelligent adult, the source of the defect is patently obvious.
*Apple forgot to test the defective iPhone 15 before selling it*
*Again*
*Then... Apple _blamed_ everyone but themselves for the defects!*
*Again*

We both own adult cognition which can recognize patterns where Apple never
changes the fact they spend their money on MARKETING & not on engineering.

I can't count the number of times Apple has released a completely defective
product which Apple only looked at _after the shit hit the fan_ in news.

Take the Facetime bugs that a mere kid found. Remember that? When Apple
finally looked at Facetime for the first time - they found scores of holes.

Same thing when Apple finally looked at their defective power-delivery
(where they tried to hide their design incompetence & got caught doing it).

It's no different here in that it's the _same pattern_ Apple always uses.

1. First Apple releases an untested (defective in this case) product.
2. Then the shit hits the fan (in the news).
3. Only then does Apple even _bother_ to think about testing the product.

Once Apple takes a quick look at the product, Apple finds issues
_everywhere_ (from Instagram to indexing to iOS 17 to charging, etc.).

Can you believe that?

Everything causes this defective iPhone to overheat according to Apple.
a. Instagram
b. Indexing
c. Charging
d. Gaming
e. Updating
etc.

If _that_ many diverse things cause these defective iPhones to overheat,
then it's pretty darn clear Apple did not sufficiently test the device.

A. Apple belatedly only tested it _after_ the shit hit the fan, and,
B. even then, Apple *blamed everyone but themselves* for the defects.

To an intelligent adult, the source of the defect is patently obvious.
*Apple forgot to test the defective iPhone 15 before selling it*

candycanearter07

2023-09-30 20:27:13 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Agreed, this does happen a lot.

--
user <candycane> is generated from /dev/urandom

Alan

2023-09-30 20:29:11 UTC

Post by Wally J
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?

Agreed, this does happen a lot.

Or the media is incredibly focused on Apple because it makes for great
headlines.

Wally J

2023-09-30 20:02:49 UTC

The vague description of the problem will lead to a vague description
of the solution.

All that matters to people who aren't trolls is that they have located
the problem and are working on a fix.

It's no longer shocking you missed the point of your own thread, JR.
You, yourself - said that Apple blamed something like a dozen things.
Right?

They blamed Instagram, for example, right?

Allow me to ask you a simple _adult_ question of your own words, JR...
*Did Instagram exist before the iPhone 15 released?* Jolly Roger?

iOS 17 has been installed on my work iPhone 11 and I haven¢t noticed
any problems

Many others echo this. The bug does not effect most people.

First off, you're calling it "the bug" because Apple clearly tried to hide
the fact that Apple simply forgot to test the iPhone 15 before selling it.

There will _always_ be "the bug" in any iOS 17 release, which badgolferman
alluded to given Apple's sweeping response was that it was _many_ bugs.

Right?
Do you even comprehend your own threads, Jolly Roger?

Seriously.
What Apple did, which badgolferman understood, was blame almost everything.

What's really the issue here - and which always was the issue with Apple is
*Apple did not sufficiently test the iPhone 15 before selling it*

That's what this thread is about.

Jolly Roger

2023-09-30 20:30:05 UTC

The vague description of the problem will lead to a vague description
of the solution.

All that matters to people who aren't trolls is that they have located
the problem and are working on a fix.

You, yourself - said that Apple blamed something like a dozen things.
Right?

I never said Apple blamed anyone.

You said that, though.

What actually happened is Apple investigated the issue and found that
the culprit was a bug in iOS (contrary to your troll gang's claim that
it's supposedly a hardware defect) combined with bugs in some popular
third-party apps. Apple also explained that it is normal for iPhones to
get warmer after operating system updates, which is true.

Post by Wally J
They blamed Instagram, for example, right?

Wrong. They identified a bug in Instagram that caused excessive resource
usage and in turn generated excessive heat.

Post by Wally J
Allow me to ask you a simple _adult_ question of your own words, JR...
*Did Instagram exist before the iPhone 15 released?* Jolly Roger?

Allow me to ask you some follow-up questions in response:

*Has Instagram been updated before and after iOS 17 was released?* Arlen?
*Do you understand that bugs can be introduced during updates?* Arlen?
*Do you know that Instagram has had previous bugs that caused excessive
resource usage in the past?* Arlen?

iOS 17 has been installed on my work iPhone 11 and I haven¢t noticed
any problems

Many others echo this. The bug does not effect most people.

First off, you're calling it "the bug"

It is a bug.

You are one of several idiot trolls here who wrongly claimed it was a
hardware defect That's on record. No way to change it now. You're just
making yourself look like the sad, little, squirming man-child you are.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-09-30 22:32:56 UTC

Post by Jolly Roger
I never said Apple blamed anyone.

Ah, but you did.
For example, you said that Apple blamed "Instagram" (among many others).

HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Jolly Roger
You said that, though.

No. You said it.
For example, you said that Apple blamed "indexing"(among many others).

Post by Jolly Roger
What actually happened is Apple investigated the issue and found that
the culprit was a bug in iOS (contrary to your troll gang's claim that
it's supposedly a hardware defect) combined with bugs in some popular
third-party apps. Apple also explained that it is normal for iPhones to
get warmer after operating system updates, which is true.

It's no longer shocking that you don't understand your own threads, JR.
You posted that Apple blamed pretty much everything that can be blamed.

BTW, the concept of _why_ Apple blamed a dozen things is too complicated
for you to comprehend - but adults know why Apple likely did that.

HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Wally J
They blamed Instagram, for example, right?

Wrong. They identified a bug in Instagram that caused excessive resource
usage and in turn generated excessive heat.

Apple blamed Instagram.

Did Instagram exist prior to Apple releasing the defective iPhone 15?
Yes? or No?

Post by Wally J
Allow me to ask you a simple _adult_ question of your own words, JR...
*Did Instagram exist before the iPhone 15 released?* Jolly Roger?

HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Jolly Roger
*Has Instagram been updated before and after iOS 17 was released?*

You're _desperate_ to blame Instagram, Jolly Roger.
Let's say it _is_ the fault of Instagram, then Jolly Roger.
OK?

Now why then did Apple provide a virtual litany of "other causes" then?
Think about that.

Post by Jolly Roger
*Do you understand that bugs can be introduced during updates?*

Again, it's clear how _desperate_ you are to blame anyone but Apple.
But let's again agree with you that "bugs were introduced", OK?

Now... why then did Apple blame one of those bugs as being in iOS 17?

Do you think maybe Apple _forgot_ to test the iPhone 15 with iOS 17?
Yes? or No?

Post by Jolly Roger
*Do you know that Instagram has had previous bugs that caused excessive
resource usage in the past?*

That's a repeat of your initial desperate attempt to blame Instagram for
Apple having forgotten to sufficiently test the defective iPhone 15.

Do you think Apple simply _forgot_ to test the iPhone 15 with Instagram?
Yes? or No?

iOS 17 has been installed on my work iPhone 11 and I haven¢t noticed
any problems

Many others echo this. The bug does not effect most people.

First off, you're calling it "the bug"

It is a bug.

Actually, your own words show clearly that Apple said it was a whole lot of
things that Apple happened to not test for before selling that iPhone 15.

An intelligent _adult_ might wonder (like badgolferman did), why exactly is
Apple so desperate to claim it was a ton of things - not just one bug?

I think I know why - because I know Apple's history of clever lies.
But time will tell why Apple said it was everything under the sun.

HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Jolly Roger
You are one of several idiot trolls here who wrongly claimed it was a
hardware defect That's on record. No way to change it now. You're just
making yourself look like the sad, little, squirming man-child you are.

I have clearly claimed that Apple themselves told us what the problem is.
*Apple did not sufficiently test the iPhone 15 on iOS 17 before selling it*
<https://groups.google.com/g/misc.phone.mobile.iphone/c/YKdktNAV7vY>

For the intelligent adults on this newsgroup, I must point out that the
mere fact Apple stooped so low as to sleazily blame pretty much everything
that they possibly could think of to blame, that the real problem is far
more embarrassing to Apple - which - I predict - we'll find out over time.

Jolly Roger

2023-09-30 22:47:13 UTC

Post by Jolly Roger
I never said Apple blamed anyone.

Ah, but you did.

No, I did not.

*You* did, though. And the reason you are repeating this obvious lie is
because you are *desperate* to try to deflect from the FACT that you
falsely claimed the iPhone 15 hardware is defective. You're a clown.

Post by Wally J
For example, you said that Apple blamed "Instagram" (among many others).

Liar. I never said that. You did, though.

Post by Jolly Roger
You said that, though.

No. You said it.

My god, you are such a weak liar.

I'm actually embarrassed for you.

[the rest of your outright lies rightfully ignored]

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 06:21:00 UTC

Post by Jolly Roger
You're a clown.

That's your response to the fact that you have no adult response to the
fact that Apple failed to sufficiently test the defective iPhone 15 for
overheating under a variety of circumstances, including Instagram?

Post by Wally J
For example, you said that Apple blamed "Instagram" (among many others).

Liar. I never said that. You did, though.

It's not just Instagram that you said Apple blamed the lack of testing on.
Apple also blamed "indexing" (among many other things Apple blamed).

Post by Jolly Roger
I'm actually embarrassed for you.

I wonder if you realize that Apple failed to sufficiently test the
defective iPhone 15 for a variety of overheating causes in iOS 17.

Then.... (just as Apple did with the Facetime bugs children found)...

When Apple was finally forced to test the defective iPhone 15 for the first
time - Apple found tons and tons and tons of causes for the overheating.

None of this occurs to you, Jolly Roger?

Jolly Roger

2023-10-01 18:36:33 UTC

Post by Jolly Roger
You're a clown.

That's your response

Yes, because you are a clown.

Post by Wally J
For example, you said that Apple blamed "Instagram" (among many others).

Liar. I never said that. You did, though.

It's not just Instagram that you said Apple blamed

Weak lies are all you have, Arlen. You're truly pathetic.

Post by Jolly Roger
I'm actually embarrassed for you.

Blah blah blah blah...

Bye now.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wally J

2023-10-01 18:58:36 UTC

Post by Wally J
That's your response

Yes, because you are a clown.

It's interesting that the adults provide facts and the iKooks can't.

The facts about Apple products are always what the iKooks can't stand.
1. Apple produced a defective iPhone.
2. The fact it's overheating is the defect.
3. Apple never even once tested the iPhone for that defect.

Then... when the shit hit the fan such that Apple had to act...
A. Apple (for the first time!) tested the defective iPhone for overheating.
B. And Apple found (much to their surprise) lots & lots of reasons for it.
C. Such that Apple instantly _blamed everyone but Apple_ for those defects.

Not only are those incontrovertible facts about what happened, but the fact
is the iKooks _hate_ that adults not only noticed - but that adults
remembered this is a classic pattern for Apple over the years.

a. Apple _never sufficiently tested_ the defective iPhones
b. Apple was eventually _forced to test_ the defective iPhones
c. Apple _blamed everyone but Apple_ for the defects in those iPhones.

Such is Apple.

Alan

2023-10-01 19:06:45 UTC

Post by Wally J
That's your response

Yes, because you are a clown.

It's interesting that the adults provide facts and the iKooks can't.

Please.

You're a clown.

That's a fact.

*Hemidactylus*

2023-09-30 23:25:39 UTC

Post by Jolly Roger
I never said Apple blamed anyone.

Ah, but you did.
For example, you said that Apple blamed "Instagram" (among many others).
HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Jolly Roger
You said that, though.

No. You said it.
For example, you said that Apple blamed "indexing"(among many others).

It's no longer shocking that you don't understand your own threads, JR.
You posted that Apple blamed pretty much everything that can be blamed.
BTW, the concept of _why_ Apple blamed a dozen things is too complicated
for you to comprehend - but adults know why Apple likely did that.
HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Wally J
They blamed Instagram, for example, right?

Wrong. They identified a bug in Instagram that caused excessive resource
usage and in turn generated excessive heat.

Apple blamed Instagram.
Did Instagram exist prior to Apple releasing the defective iPhone 15?
Yes? or No?

Post by Wally J
Allow me to ask you a simple _adult_ question of your own words, JR...
*Did Instagram exist before the iPhone 15 released?* Jolly Roger?

HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

Post by Jolly Roger
*Has Instagram been updated before and after iOS 17 was released?*

You're _desperate_ to blame Instagram, Jolly Roger.
Let's say it _is_ the fault of Instagram, then Jolly Roger.
OK?
Now why then did Apple provide a virtual litany of "other causes" then?
Think about that.

Post by Jolly Roger
*Do you understand that bugs can be introduced during updates?*

Again, it's clear how _desperate_ you are to blame anyone but Apple.
But let's again agree with you that "bugs were introduced", OK?
Now... why then did Apple blame one of those bugs as being in iOS 17?
Do you think maybe Apple _forgot_ to test the iPhone 15 with iOS 17?
Yes? or No?

Post by Jolly Roger
*Do you know that Instagram has had previous bugs that caused excessive
resource usage in the past?*

That's a repeat of your initial desperate attempt to blame Instagram for
Apple having forgotten to sufficiently test the defective iPhone 15.
Do you think Apple simply _forgot_ to test the iPhone 15 with Instagram?
Yes? or No?

iOS 17 has been installed on my work iPhone 11 and I havenąt noticed
any problems

Many others echo this. The bug does not effect most people.

First off, you're calling it "the bug"

It is a bug.

Actually, your own words show clearly that Apple said it was a whole lot of
things that Apple happened to not test for before selling that iPhone 15.
An intelligent _adult_ might wonder (like badgolferman did), why exactly is
Apple so desperate to claim it was a ton of things - not just one bug?
I think I know why - because I know Apple's history of clever lies.
But time will tell why Apple said it was everything under the sun.
HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
the real cause (which badgolferman understood) behind a long smokescreen.

I have clearly claimed that Apple themselves told us what the problem is.
*Apple did not sufficiently test the iPhone 15 on iOS 17 before selling it*
<https://groups.google.com/g/misc.phone.mobile.iphone/c/YKdktNAV7vY>
For the intelligent adults on this newsgroup, I must point out that the
mere fact Apple stooped so low as to sleazily blame pretty much everything
that they possibly could think of to blame, that the real problem is far
more embarrassing to Apple - which - I predict - we'll find out over time.

We shall see, though I hold no bias here. And people who talk down their
noses at others as if adulting aren’t. How many sockpuppets have you
wielded recently uninteresting troll?

Wally J

2023-10-01 06:24:26 UTC