On 2023-10-02 21:37, Frankie wrote:
> On 2/10/2023, sms wrote:
>
>>> 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.
>
> Given there are many disparate excuses Apple has provided for why the
> defective iPhones are overheating, do you think the "fix" will involved
> Apple lowering the performance?
>
> I'm not speaking of the CPU speed since Apple will be clever to blame the
> apps and not the processor - so the wording of Apple's public apology will
> likely be just as much a Doozy as the last one was that Apple issued.
>
> Do you think there's any chance Apple can decrease the disparate
> overheating (happens during charging!) without lowering performance?

Yes. Bugs that cause excessive CPU consumption w/o contributing useful
work are very possible. This has been explained to you. But you lack
the knowledge to understand it. That's okay - when Apple (and some app
writers) implement their changes you'll see it for what it is (or more
likely go off on some other bizarre tangent).

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

On 2023-10-02 21:33, Frankie wrote:
> On 2/10/2023, Alan Browne wrote:
>
>> There are user settings in Unix to lower the priority of a program, but
>> it will still get all the CPU it can that is available. Not sure if
>> there are internal calls in iOS so an app can have its priority lowered.
>
> Apple has to lower performance, where that's one way they might do it.

It's clear you have no idea how pre-emptive OS's work.

Because, in fact, even when a thread or process has the lowest priority,
it will still get all the CPU time it craves when other processes of
higher priority don't need the CPU.

So Apple just need to fix the offending processes (bugs) and there will
be no need to throttle performance to resolve this issue.

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

On 3/10/2023, Alan wrote:

>> How can someone be _that_ ignorant when NOBODY who races and NOBODY who
>> owns a bimmer or a beemer (I own both) would be _that_ completely clueless.
>
> Sorry... ...I never heard a distinction made about those two terms.

https://www.google.com/search?q=bimmer+versus+beemer

On 3/10/2023, Alan Browne wrote:

> So Apple just need to fix the offending processes (bugs) and there will
> be no need to throttle performance to resolve this issue.

Apple already said they have to reduce the performance "of certain apps."

On 3/10/2023, Alan Browne wrote:

>> Do you think there's any chance Apple can decrease the disparate
>> overheating (happens during charging!) without lowering performance?
>
> Yes. Bugs that cause excessive CPU consumption w/o contributing useful
> work are very possible. This has been explained to you. But you lack
> the knowledge to understand it. That's okay - when Apple (and some app
> writers) implement their changes you'll see it for what it is (or more
> likely go off on some other bizarre tangent).

Apple already said they have no choice but to reduce the performance of the
apps they claim are causing the system to overheat.

Apple said they hope, "long term", that this short-term temporary
performance reduction will not greatly affect the iPhone 15 user base.

It was very clear that Apple said that.

Since you claim to know so much about Apple's solution, what do you make of
those public Apple statements from yesterday?

On 2023-10-02 18:49, Peter wrote:
> sms <scharf.steven@geemail.com> wrote:
>>> It was a conscious decision not to test these iPhones for overheating.
>>
>> It was likely the belief that since the apps all ran fine on iOS 17 on
>> the iPhone 14 Pro/Pro Max that there was no operating system issue with
>> those apps. They didn't take into account the higher power consumption
>> and higher thermals of the A17 Bionic or the change from a metal with a
>> higher thermal conductivity to one with a lower thermal conductivity.
>
> You are correct because the causes are so mundane that the only way Apple
> could have not known about (charging & Instagram & common games) causing
> the iPhone overheating is that Apple thought they didn't need to test it.

In your utterly uninformed and uneducated opinino...

....right?

Opinions are like assholes: everybody's got one.

On 2023-10-03 14:04, Frankie wrote:
> On 3/10/2023, Alan Browne wrote:
>
>> So Apple just need to fix the offending processes (bugs) and there will
>> be no need to throttle performance to resolve this issue.
>
> Apple already said they have to reduce the performance "of certain apps."

Cite.

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

On 2023-10-03 14:07, Frankie wrote:
> On 3/10/2023, Alan Browne wrote:
>
>>> Do you think there's any chance Apple can decrease the disparate
>>> overheating (happens during charging!) without lowering performance?
>>
>> Yes. Bugs that cause excessive CPU consumption w/o contributing useful
>> work are very possible. This has been explained to you. But you lack
>> the knowledge to understand it. That's okay - when Apple (and some app
>> writers) implement their changes you'll see it for what it is (or more
>> likely go off on some other bizarre tangent).
>
> Apple already said they have no choice but to reduce the performance of the
> apps they claim are causing the system to overheat.

Cite.

>
> Apple said they hope, "long term", that this short-term temporary
> performance reduction will not greatly affect the iPhone 15 user base.

Cite.

> Since you claim to know so much about Apple's solution, what do you make of
> those public Apple statements from yesterday?

Cite.

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

On Oct 2, 2023, Wally J wrote
(in article <uffpbs$6toj$1@paganini.bofh.team>):

> The software I worked on is classified as a munition

So what? These two lines of perl implementing RSA would have been considered
a munition too:

print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`

On 2023-10-03, Alan Browne <bitbucket@blackhole.com> wrote:
> On 2023-10-02 21:37, Frankie wrote:
>> On 2/10/2023, sms wrote:
>>
>>>> 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.
>>
>> Given there are many disparate excuses Apple has provided for why the
>> defective iPhones are overheating, do you think the "fix" will
>> involved Apple lowering the performance?
>>
>> I'm not speaking of the CPU speed since Apple will be clever to blame
>> the apps and not the processor - so the wording of Apple's public
>> apology will likely be just as much a Doozy as the last one was that
>> Apple issued.
>>
>> Do you think there's any chance Apple can decrease the disparate
>> overheating (happens during charging!) without lowering performance?
>
> Yes. Bugs that cause excessive CPU consumption w/o contributing
> useful work are very possible. This has been explained to you. But
> you lack the knowledge to understand it. That's okay - when Apple
> (and some app writers) implement their changes you'll see it for what
> it is (or more likely go off on some other bizarre tangent).

They'll probably just insist that "Apple is throttling" without evidence
(as usual) and repeat that lie forever. 😉

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

On 2023-10-03, Frankie <frankie@nospam.usa> wrote:
> On 3/10/2023, Alan Browne wrote:
>
>> So Apple just need to fix the offending processes (bugs) and there
>> will be no need to throttle performance to resolve this issue.
>
> Apple already said they have to reduce the performance "of certain
> apps."

Apple didn't say that. You're lying as usual.

--
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 <walterjones@invalid.nospam> wrote

> But why don't they ever show any semblance of normal adult cognition then?
> Worse than the iKooks' almost complete lack of adult cognitive skills is
> how these ignorant low-IQ uneducated iKooks react to facts about Apple.
>
> They only have 7 responses to all truths about Apple.
>
> The first few are to outright deny all facts about Apple and in doing so to
> blame Samsung for everything bad that Apple does - and then to distract and
> change the conversation to classic "whataboutism" (which they don't even
> know they're using since none of them has earned a high school GED even).
>
> HINT: Jolly Roger said he failed three times to attain his High School GED.

Dorper <usenet@dorper.me> wrote

>> Hint: No smartphone OS is anywhere nearly as insecure as iOS is.
>> (hackers don't even need to be within a thousand miles of your phone to
>> completely and fully take it over any time they want to - for years!)
>
> In other news, Android has released it's latest security update:
>
> https://www.bleepingcomputer.com/news/security/android-october-security-
> update-fixes-zero-days-exploited-in-attacks/
> Including fixes for "54 unique vulnerabilities, including two known to be
> actively exploited." Of the 54 fixes concerning Android 11 through 13, five
> are rated critical, and two concern remote code execution problems.

It's classic for Apple users to blame everyone but Apple for the flaws in
Apple devices. It's called "whataboutism" & only Apple users do it.
<https://en.wikipedia.org/wiki/Whataboutism>

I know exactly why you used whataboutism to defend against Apple's flaw.
I wonder if you do?

Probably not.
Let's just say that only Apple people do what you just did, Dorper.

Adults don't do it. Specifically...

You'll _never_ see someone on Android doing what you just did, Dorper.
Nor on Windows newsgroups.

Only Apple newsgroups.
Where almost every "excuse" for Apple's flaws is whataboutism incarnate.

This "whataboutism" of blaming everyone but Apple _starts with Apple_
and it's a hallmark of Apple users to blame others for Apple's flaws.

*Why don't we look at the zero-day holes in iOS*, Dorper.
Shall we?

I get it you are desperate to defend Apple's honor, but then you must know
how many zero-day bugs Apple had this year (and every year!) compared to
Android, right?

No?
You don't know?

Hmmmm.... classic.

Here... allow me to help you to think logically & sensibly, OK?

What you're _not_ saying is that iOS has had 17 zero-days this year alone -
which is something like two to three times the zero-days of Android last we
checked (since this happens every year).

By definition, a zero day is a bug that Apple forgot to find in testing.
Right?

So that's two to three times (every year - year after year) that Apple's
iOS has zero-day holes that Apple forgot to find in their iOS 'testing'.

HINT: That's a lot!

Why... might you ask... is iOS always two to three times less secure?
I (think I) know why.

Do you?
--
Note: We've already discussed that this doesn't even count the _exploited_
zero days, where you dispute that iOS has _ten times_ the active exploits!

On 2023-10-03, Wally J <walterjones@invalid.nospam> wrote:
>
> HINT: Jolly Roger said he failed three times to attain his High School GED.

🤣 Blatant lies only fool other fools, Arlen. Not only have I never
talked about my degrees here on Usenet, you can't show a single post
from me with these words in it. You are the King of Fools.

> Sad.

Your life is a pathetic ocean of weak lies, indeed.

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