Share your analytics logs.

[humpbacktwale]

Curious what logs everyone is getting in ios 15 now that it's been out for a while. Usually a good indicator of what's common or not. Outside of the usual analyics-90day/journal/daily/never, after 2 weeks on 15.2, I have:

• wifiLQMMetric- which seems to be empty
• apfs_iosd.cpu_resource, seems to happen only while charging, and only sometimes
• Jetsam event caused by promotedcontentd, no clue what that is
• ExcUserFault_webbookmarksd- an odd one given I have no bookmarks or syncing enabled.

So what has everyone else gotten since the update?

 

[Taz Mangus]

• backboardd.wakeups_resource - Indicates that there was excessive wakeups within a time frame (e.g. 45001 wakeups over the last 169 seconds). Could indicate excess CPU usage which might lead to excess battery drain.
• dasd.cpu_resource - Indicates excess CPU usage.
• duetexpertd.cpu_resource - Indicates excess CPU usage.
• ExcUserFault_CMFSyncAgent
• ExcUserFault_webbookmarksd
• JetsamEvent
• PerfPowerServivesSignpostReader.cpu_resource
• securityd.diskwrites_resouce
• spotlightknowledged.cpu_resource
• wifiLQMMetric is a binary file. It won't show anything from the iOS file viewer.

 

[humpbacktwale]

Is the backboardd one constant for you? Only ever seen that once just after I turned my phone on the first time. Shouldn't cause too much of an issue if it isn't.

Yeah ExcUserFault_webbookmarksd is an odd one. I can't remember having ever seen it before iOS 15, but it occurred just after I updated. Maybe a new bug?

What was the cause of the JetsamEvent in your case?

wifiLQMMetric is a binary file

Strange they'd even bother to include it at all then. Another one I think might be new as I can't recall it either from before iOS 15

 

[Cursed & Cussing in Texas]

So. I’ve had some aggregated.diskwrite_resource logs this month, as well as these two new ones the last week:

Analytics-Never-Date
Assetsd.cpu_resource-Date

Am I as screwed as I think I am? Anyone else seeing these?

 

[drak22]

and creates the log-aggregate where the load cycles came out? I haven't for a long time, and not if it's a mistake or something intentional ?

 

[ph.rei]

My Camera App froze two times today. Fixed by swiping up on it.
IPhone 13 Pro 15.2.1
I checked and i have two interesting logs. They are very long, this is just a really really small part of it.
Log - "stacks ..... ips"
Bug type 288
"reason" : "Timed out waiting for the capture graph to stop. Please file a radar against (null).",
"frontmostPids" : [
63
],
"exception" : "0xda593521",
"absoluteTime" : 158078972144,
"memoryStatus" : {"compressorSize":13249,"compressions":161978,"decompressions":51765,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":103282,"throttled":0,"fileBacked":129128,"wired":54122,"purgeable":4626,"inactive":87280,"free":73886,"speculative":19389}},
"processByPid" : {
"0" : {
"pid" : 0,
"residentMemoryBytes" : 5160960,
"timesDidThrottle" : 0,
"systemTimeTask" : 36072.031361583002,
"pageIns" : 0,
"pageFaults" : 4097,
"userTimeTask" : 5.5166e-05,
"procname" : "kernel_task",
"copyOnWriteFaults" : 0,
"threadById" : {
"330" : {
"continuation" : [
0,
19167352
],
"userTime" : 0,
"systemTime" : 0.094574915999999995,
"id" : 330,
"basePriority" : 81,
"name" : "AppleGen2SPMIController",
"user_usec" : 0,
"schedPriority" : 81,
"system_usec" : 94574,
"state" : [
"TH_WAIT",
"TH_UNINT"
],
"waitEvent" : [
1,
11646574708535692019
]
},
"552" : {
"continuation" : [
0,
19167352
],
"userTime" : 0,
"systemTime" : 3.083e-06,
"id" : 552,
"basePriority" : 81,
"name" : "AppleT8110DART",
"user_usec" : 0,
"schedPriority" : 81,
"system_usec" : 3,
"state" : [
"TH_WAIT",
"TH_UNINT"
],
"waitEvent" : [
1,
11646574708535777779
]

 

[humpbacktwale]

So. I’ve had some aggregated.diskwrite_resource logs this month, as well as these two new ones the last week:

Analytics-Never-Date
Assetsd.cpu_resource-Date

Am I as screwed as I think I am? Anyone else seeing these?

Why would you be screwed? I've seen aggregated every few months since I got this phone. There are plenty of people who have them.
Analytics-never-date is something everyone has. Your iphone generates them for a certain period of time after you update.

 

[humpbacktwale]

and creates the log-aggregate where the load cycles came out? I haven't for a long time, and not if it's a mistake or something intentional ?

What do you mean by this?

 

[drak22]

What do you mean by this?

Well, if you have this log generated on your device, because I haven't been for months, and I can no longer see the load cycles that I have directly, without using third-party apps on the computer.

 

[Feyl]

The important question is why are these logs even created if I turned off the analytics.

 

[humpbacktwale]

Well, if you have this log generated on your device, because I haven't been for months, and I can no longer see the load cycles that I have directly, without using third-party apps on the computer.

You mean the aggregated one, or something else? I haven't seen it since updating to 15.2.

 

[humpbacktwale]

The important question is why are these logs even created if I turned off the analytics.

That just stops it being shared. I don't think you can disable analytics entirely from a non-jailbroken device.

 

[humpbacktwale]

Seems someone else also has apfs_iosd.cpu_resource as well

 

[cynics]

The important question is why are these logs even created if I turned off the analytics.

"Technically" you have "Share analytics" off.

Double semantics there for your annoyance. Collecting =/= sharing. Analytics =/= logs.

7 days of specific logs that would be used for diagnostics are retained. You should only see, awdd, log power, log sessions, etc. You or a tech can use this information in real life or using the share menu online to diagnose problems your device is having. Without it

I get people have a privacy concern with "analytics" but its incredibly important information. With so many devices, specs, versions of iOS (in the wild), use cases etc analytic data is why an app can get fixed in days vs months/years or more likely never. Plus you can see the data. You won't find a way to specifically identify you in it without specifically already knowing you. What you will find is your iPhones general info, generic location data that can probably narrow you down to 100,000 people and every time your iPhone wasn't behaving perfectly with a way to suss out the issue. Personally in my line of work I'm a huge fan as long as I can't see private info but again I respect peoples right to privacy and even their false perception of it if it makes them happier...