iPod touch Interesting alert after syncing w/ itunes after customizing

[csmitty]

"Your ipod contains diagnostic information which may help apple improve its products. "

Anyone else get that? Of course i hit don't send. Everything appears to be syncing just fine.

This is the coolest device now. I liked it when i had a wk 36, but took it back, and once i saw they got it open i went and got another 38. screen is great and got all the apps and more i wanted. Palm TX, meet ebay 🙂

now once i get my icons changed and rearranged, good to go.

 

[kinchee87]

I got that message a few hours after getting my iPod Touch (which was before any sort of jailbreaking was released).

 

[REBELinBLUE]

I got it within hours of getting my iPod, it is just the crash reporter, similar to the one on OS X.

If you view the data you can see what info it will send, for me it has always been crash logs for Safari.

 

[csmitty]

ah, gotcha, that makes sense.

 

[Cleverboy]

ah, gotcha, that makes sense.

To find your iPhone's crash log, sync your iPhone using iTunes and then check the following location on your computer:

Mac users:
/Library/Logs/CrashReporter/MobileDevice/[Your iPhone's Name]

Windows users:
Application Data\Apple Computer\Logs\CrashReporter\MobileDevice
\[Your iPhone's Name]

Using the dialog that pops up, you may choose to automatically send this information to Apple, to help them improve the phone, or deny this behavior. If you've jailbroken your device, you might want to choose the latter, as a quick review of your logs will probably indicate that these aren't the type of "reports" you want to send to Apple (if you have NOT, on the other hand, its probably useful to do). 🙂

Baseband
BTServer-2007-07-06-130025.crash
BTServer-2007-07-28-003742.crash
Exited process-2007-09-04-132913.crash
Exited process-2007-09-15-133112.crash
Exited process-2007-09-21-053427.crash
iFlickr-2007-09-16-215530.crash
iFlickr-2007-09-16-215723.crash
Installer-2007-09-11-233817.crash
LowBatteryLog-2007-09-19-094548.crash
LowBatteryLog-2007-09-19-094633.crash
mediaserverd-2007-09-08-001336.crash
mediaserverd-2007-09-22-181958.crash
MobileCast-2007-10-05-201859.crash
MobileCast-2007-10-05-201859.plist
MobileMail-2007-06-30-160055.crash
MobileMail-2007-07-13-034219.crash
MobileMail-2007-07-30-143350.crash
MobileMail-2007-08-03-215853.crash
MobileMail-2007-08-11-185844.crash
MobileMail-2007-10-06-080924.crash
MobileMail-2007-10-06-080924.plist
MobileMusicPlaye-2007-07-03-061126.crash
MobileMusicPlaye-2007-07-03-061140.crash
MobileMusicPlaye-2007-07-03-065843.crash
MobileMusicPlaye-2007-08-01-063518.crash
MobileMusicPlaye-2007-08-25-185956.crash
MobileMusicPlaye-2007-09-08-084426.crash
MobilePhone-2007-09-07-061409.crash
MobileSafari-2007-06-30-014845.crash
MobileSafari-2007-06-30-015114.crash
MobileSafari-2007-06-30-140057.crash
MobileSafari-2007-07-04-065856.crash
MobileSafari-2007-07-06-053827.crash
MobileSlideShow-2007-08-15-191134.crash
MobileToDoList-2007-09-12-110124.crash
MobileToDoList-2007-09-12-183631.crash
NES-2007-09-10-000206.crash
NES-2007-09-10-053546.crash
NES-2007-09-10-203829.crash
NES-2007-09-11-161454.crash
NES-2007-09-11-162122.crash
NES-2007-09-11-213743.crash
ResetCounter.crash
ResetCounter.plist
SpringBoard-2007-09-14-160428.crash
SpringBoard-2007-09-15-002712.crash
SpringBoard-2007-09-19-185139.crash
Term-vt100-2007-09-10-234108.crash
Term-vt100-2007-09-21-053426.crash
vnsea-2007-09-16-161631.crash
vnsea-2007-09-16-161857.crash
YouTube-2007-07-01-171629.crash

Doh. Crashes can be so subtle on the iPhone (when its not a full-blown freeze-up), often you may not know they've happened. You may be in a completely different application, only to return to one you'd thought was still running, and be none-the-wiser that it had shut-down while you were away.

~ CB