XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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.*

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 11:56, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 12:21, Jolly Roger wrote:

On 2023-09-30, Alan <nuh-uh@nope.com> wrote:

On 2023-09-30 11:56, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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.

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?

:-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Alan <nuh-uh@nope.com> wrote:

On 2023-09-30 11:56, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 12:33, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Wally J <walterjones@invalid.nospam> wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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

Hi Jolly Roger,

Eat shit, Arlen. 🙂

You yourself just said Apple blamed Instagram

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

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? 🤣

Apple blamed indexing

I never said that either.
You did, though.

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Wally J <walterjones@invalid.nospam> wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 12:43, Wally J wrote:

Jolly Roger<jollyroger@pobox.com> wrote

I never said this issue didn't exist.

The real problem is...

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

:-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

Eat shit

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

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.

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?
--

Your lies are both weak and boring

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 13:27, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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.

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

...so you're just lying again.

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.

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Wally J <walterjones@invalid.nospam> wrote:

Jolly Roger <jollyroger@pobox.com> wrote

Eat shit

Such an adult response

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

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*. 🤣

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Wally J <walterjones@invalid.nospam> wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30, Wally J <walterjones@invalid.nospam> wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

Jolly Roger <jollyroger@pobox.com> wrote

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: misc.phone.mobile.iphone, comp.sys.mac.system

On 2023-09-30 23:15, Wally J wrote:

Jolly Roger <jollyroger@pobox.com> wrote

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).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)