Coretelephony trace file error что значит

My Macbook get a message “CoreTelephony Trace File error” on each profile I login to just start a few days ago. When I’m playing Football Manager on Google Chrome, it crashes, freezes and shuts down suddenly, and when I’m rebooting I get this message before starting up: Coretelephony trace file error. Now I also can’t open the parallels desktop. What can I do? Why do I get this error? Please help to repair my Mac book, thank you in advance.

Picture presentation about “CoreTelephony Trace File error”

Why did I got “Coretelephony trace file error”? How to repair?

If you get Coretelephony trace file error, the main problem is the/tmp directory permissions. Electronic products always have problems when using for a long time. Some errors are produced in your improper operation. In order to fix this error on your Mac, there are several kinds of methods:

Method one:

Close SIP protection, and then modify the permissions. Inspection of /tmp directory showed only contents a subdirectory “/tmp/notifcations”. It could not be removed and remained on rebooted system. After trying numerous suggestions including running disk utility and resetting permissions while in recovery mode, the following remedied. Turn off System Integrity Protection and reboot to clear unwanted files in /tmp and restore needed file /tmp/ct.shutdown. Problem gone when rebooted. “/tmp/notifications” was removed. Error message gone. Reenabling System Integrity Protection did not bring back problem. Thinking El Capitan upgrade had failed to clean up after itself. Specific instructions as follows:

1. Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on your screen, and then go to Recovery Mode.

2. Click Utilities > Terminal.

3. In the Terminal window, type in ‘csrutil disable’ and press Enter.

4. Restart your Mac.

5. If error message gone, success!

6. Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on your screen.

7. Click Utilities > Terminal.

8. In the Terminal window, type in ‘csrutil disable’ and press Enter.

9. Restart Mac.

Method two:

1. You need to fully boot your Mac. It needs took about 12-20 Minutes for the desktop to populate with icons. Waiting it out was a key issue because we wanted to the Users folder to check those permissions. Once the drive icon mounted, no problem at all. Normal boot, not Safe Boot although that should work too. Safe Boot just didn’t offer any advantages in this case.

2. Get Info on each admin user account. Check those permissions. Any that have “wheel” are problematic.

3. Create a new admin user account and boot into that for the next step.

4. Boot into the admin user account. Choose the first option: Save the home directory as a .dmg file in the Deleted Users folder that will then be created. (Once created, that can be substituted so nothing is lost.)

5. Create a new Admin user matching the same name as the one you just deleted. Reboot into each new Admin account to confirm that the problem has gone away.

6. Once confirmed, substitute the previous (deleted) home directories to replace the new blank one in the newly-created-but-with-the-old-name admin user’s directory. It’s a drag and drop of the whole user directory. You can then delete the (“Tech”) admin account you used to resolve the issue, or just leave it for another day.

Note: Repair this error is supposed to have a certain level of tech skill. If you are not sure how to start and are afraid of making any critical mistakes damaging your Mac, please live chat with YooCare/Yoosecurity Expert now.

Published by Tony Shepherd & last updated on October 19, 2016 12:07 pm

I think this is the problem

A little background

Traceview is a graphical viewer for execution logs that you create by using the Debug class to log tracing information in your code. Traceview can help you debug your application and profile its performance. Enabling it creates a .trace file in the sdcard root folder which can then be extracted by ADB and processed by traceview bat file for processing. It also can get added by the DDMS.

It is a system used internally by the logger. In general unless you are using traceview to extract the trace file this error shouldnt bother you. You should look at error/logs directly related to your application

How do I enable it:

There are two ways to generate trace logs:

1. Include the Debug class in your code and call its methods such as startMethodTracing() and stopMethodTracing(), to start and stop
   logging of trace information to disk. This option is very precise
   because you can specify exactly where to start and stop logging trace
   data in your code.

2. Use the method profiling feature of DDMS to generate trace logs. This option is less precise because you do not modify code, but rather
   specify when to start and stop logging with DDMS. Although you have
   less control on exactly where logging starts and stops, this option is
   useful if you don’t have access to the application’s code, or if you
   do not need precise log timing.

But the following restrictions exist for the above

If you are using the Debug class, your application must have
permission to write to external storage (WRITE_EXTERNAL_STORAGE).

If you are using DDMS: Android 2.1 and earlier devices must have an SD
card present and your application must have permission to write to the
SD card. Android 2.2 and later devices do not need an SD card. The
trace log files are streamed directly to your development machine.

So in essence the traceFile access requires two things

1.) Permission to write a trace log file i.e. WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE for good measure

2.) An emulator with an SDCard attached with sufficient space. The doc doesnt say if this is only for DDMS but also for debug, so I am assuming this is also true for debugging via the application.

What do I do with this error:

Now the error is essentially a fall out of either not having the sdcard path to create a tracefile or not having permission to access it. This is an old thread, but the dev behind the bounty, check if are meeting the two prerequisites. You can then go search for the .trace file in the sdcard folder in your emulator. If it exists it shouldn’t be giving you this problem, if it doesnt try creating it by adding the startMethodTracing to your app.
I’m not sure why it automatically looks for this file when the logger kicks in. I think when an error/log event occurs , the logger internally tries to write to trace file and does not find it, in which case it throws the error.Having scoured through the docs, I don’t find too many references to why this is automatically on.
But in general this doesn’t affect you directly, you should check direct application logs/errors.
Also as an aside Android 2.2 and later devices do not need an SD card for DDMS trace logging. The trace log files are streamed directly to your development machine.

Additional information on Traceview:

Copying Trace Files to a Host Machine

After your application has run
and the system has created your trace files .trace on
a device or emulator, you must copy those files to your development
computer. You can use adb pull to copy the files. Here’s an example
that shows how to copy an example file, calc.trace, from the default
location on the emulator to the /tmp directory on the emulator host
machine:

adb pull /sdcard/calc.trace /tmp Viewing Trace Files in Traceview To
run Traceview and view the trace files, enter traceview
. For example, to run Traceview on the example files
copied in the previous section, use:

traceview /tmp/calc Note: If you are trying to view the trace logs of
an application that is built with ProGuard enabled (release mode
build), some method and member names might be obfuscated. You can use
the Proguard mapping.txt file to figure out the original unobfuscated
names. For more information on this file, see the Proguard
documentation.

I think any other answer regarding positioning of oncreate statements or removing uses-sdk are not related, but this is Android and I could be wrong. Would be useful to redirect this question to an android engineer or post it as a bug

More in the docs

I think this is the problem

A little background

Traceview is a graphical viewer for execution logs that you create by using the Debug class to log tracing information in your code. Traceview can help you debug your application and profile its performance. Enabling it creates a .trace file in the sdcard root folder which can then be extracted by ADB and processed by traceview bat file for processing. It also can get added by the DDMS.

It is a system used internally by the logger. In general unless you are using traceview to extract the trace file this error shouldnt bother you. You should look at error/logs directly related to your application

How do I enable it:

There are two ways to generate trace logs:

1. Include the Debug class in your code and call its methods such as startMethodTracing() and stopMethodTracing(), to start and stop
   logging of trace information to disk. This option is very precise
   because you can specify exactly where to start and stop logging trace
   data in your code.

2. Use the method profiling feature of DDMS to generate trace logs. This option is less precise because you do not modify code, but rather
   specify when to start and stop logging with DDMS. Although you have
   less control on exactly where logging starts and stops, this option is
   useful if you don’t have access to the application’s code, or if you
   do not need precise log timing.

But the following restrictions exist for the above

If you are using the Debug class, your application must have
permission to write to external storage (WRITE_EXTERNAL_STORAGE).

If you are using DDMS: Android 2.1 and earlier devices must have an SD
card present and your application must have permission to write to the
SD card. Android 2.2 and later devices do not need an SD card. The
trace log files are streamed directly to your development machine.

So in essence the traceFile access requires two things

1.) Permission to write a trace log file i.e. WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE for good measure

2.) An emulator with an SDCard attached with sufficient space. The doc doesnt say if this is only for DDMS but also for debug, so I am assuming this is also true for debugging via the application.

What do I do with this error:

Now the error is essentially a fall out of either not having the sdcard path to create a tracefile or not having permission to access it. This is an old thread, but the dev behind the bounty, check if are meeting the two prerequisites. You can then go search for the .trace file in the sdcard folder in your emulator. If it exists it shouldn’t be giving you this problem, if it doesnt try creating it by adding the startMethodTracing to your app.
I’m not sure why it automatically looks for this file when the logger kicks in. I think when an error/log event occurs , the logger internally tries to write to trace file and does not find it, in which case it throws the error.Having scoured through the docs, I don’t find too many references to why this is automatically on.
But in general this doesn’t affect you directly, you should check direct application logs/errors.
Also as an aside Android 2.2 and later devices do not need an SD card for DDMS trace logging. The trace log files are streamed directly to your development machine.

Additional information on Traceview:

Copying Trace Files to a Host Machine

After your application has run
and the system has created your trace files .trace on
a device or emulator, you must copy those files to your development
computer. You can use adb pull to copy the files. Here’s an example
that shows how to copy an example file, calc.trace, from the default
location on the emulator to the /tmp directory on the emulator host
machine:

adb pull /sdcard/calc.trace /tmp Viewing Trace Files in Traceview To
run Traceview and view the trace files, enter traceview
. For example, to run Traceview on the example files
copied in the previous section, use:

traceview /tmp/calc Note: If you are trying to view the trace logs of
an application that is built with ProGuard enabled (release mode
build), some method and member names might be obfuscated. You can use
the Proguard mapping.txt file to figure out the original unobfuscated
names. For more information on this file, see the Proguard
documentation.

I think any other answer regarding positioning of oncreate statements or removing uses-sdk are not related, but this is Android and I could be wrong. Would be useful to redirect this question to an android engineer or post it as a bug

More in the docs