Ga door naar hoofdinhoud

Repareer je spullen

Recht op reparatie

Winkel

Help

Deze versie is geschreven door: Malcolm Hall ,

Tekst:

I don’t believe this is the same issue as the CPU throttling Apple have admitted to. In this case the lagging is so bad the phone is essentially unusable, can’t launch apps and can’t even make phone calls, and if any audio plays it can be scrambled.
 
In this case the CPU is still at maximum frequency but the reason for the lagging is the CPU is at 100%.
 
I’ve noticed it on my 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time.
 
You can use Lirium Info Lite to see the CPU usage (CPU Dasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose. That is my current theory that when the battery goes low iOS begins to try to read info from the battery or read it more frequently and since the 3rd party battery does not support whatever it is doing the kernel goes to 100% cpu. I’ve seen a similar behaviour with the Blackberry email app when it is trying to write to disk in the background and drains the battery down.

if you read its reviews you’ll see.
You can use Lirium Info Lite to see the CPU usage (CPU Dasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose. That is my current theory that when the battery goes low iOS begins to try to read info from the battery or read it more frequently and since the 3rd party battery does not support whatever it is doing the kernel goes to 100% cpu. I’ve seen a similar behaviour with the Blackberry email app when it is trying to write to disk in the background and drains the battery down.

if you read its reviews you’ll see.
 
[image|1588633]

Status:

open

Bewerkt door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to seeI don’t believe this is the same issue as the CPU usage (CPU Dasher X does not showthrottling Apple have admitted to. In this case the total CPU usagelagging is so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The momentbad the phone is connected to the Macessentially unusable, can’t launch apps and can’t even make phone calls, and if any audio plays it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I supposescrambled.
Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to seeI don’t believe this is the same issue as the CPU usage (CPU Dasher X does not showthrottling Apple have admitted to. In this case the total CPU usagelagging is so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The momentbad the phone is connected to the Macessentially unusable, can’t launch apps and can’t even make phone calls, and if any audio plays it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I supposescrambled.
 
In this case the CPU is still at maximum frequency but the reason for the lagging is the CPU is at 100%.
 
I’ve noticed it on my 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time.
 
You can use Lirium Info Lite to see the CPU usage (CPU Dasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose. That is my current theory that when the battery goes low iOS begins to try to read info from the battery or read it more frequently and since the 3rd party battery does not support whatever it is doing the kernel goes to 100% cpu. I’ve seen a similar behaviour with the Blackberry email app when it is trying to write to disk in the background and drains the battery down.
 
 
I’ll update this if I figure it out but right now I believe that Apple’s new logging system is the culprit. As the battery gets low then more processes start outputting log data, which grinds the system to a halt. Apple added a new log system called unified logging system in iOS 10 which writes all the messages to a database, I think this is the problem, too much disk writing.
 
[image|1588633]

Status:

open

Bewerkt door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usage (CPU Dasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose.
 
 
 
I’ll update this if I figure it out but right now I believe that Apple’s new logging system is the culprit. As the battery gets low then more processes start outputting log data, which grinds the system to a halt. Apple added a new log system called unified logging system in iOS 10 which writes all the messages to a database, I think this is the problem, too much disk writing.
 
[image|1588633]

Status:

open

Bewerkt door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usage (CPU DasheDasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issueissue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose.
Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usage (CPU DasheDasher X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issueissue, however enabling network in the Devices window allows it, and can use Instruments to view the process list with CPU usage. It’s hard to tell because the monitoring processes consume a lot of cpu but it seems the culprit is the kernel, which usually means high disk access but it could be an issue with reading info from a 3rd party battery I suppose.
 
[image|1588633]

Status:

open

Bewerkt door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usageusage (CPU Dashe X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue.

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usageusage (CPU Dashe X does not show the total CPU usage so don’t use that). I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue.

 
[image|1588633]

Status:

open

Bewerkt door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usage. I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue.
 
 
 
[image|1588633]

Status:

open

Origineel bericht door: Malcolm Hall ,

Tekst:

Same here, 6s on iOS 12.1, when battery goes under 20% and I go on an area of no mobile data (or turn off mobile data to simulate) then CPU goes to 100% and battery drains down to zero in no time. You can use Lirium Info Lite to see the CPU usage. I’m a developer so trying to figure out what process is responsible for this. The moment the phone is connected to the Mac it isn’t possible to debug the problem because it also starts charging which immediately resolves the issue.

Status:

open