The com.android.server.telecom app is present in all Android devices(Samsung, Huawei, etc). If you have seen this app in your Activity Log or Google Activity and don’t know what it does then you have come to the right place.
In this article, I’ll explain what is com.android.server.telecom, what does it do, why does it stop working, and how to fix this issue.
What does com.android.server.telecom mean?
- 1 What does com.android.server.telecom mean?
- 2 How does Android Telecom Framework Work?
- 3 com.android.server.telecom has Stopped
- 4 How to Fix “com.android.server.telecom has stopped” issue?
- 5 com.android.server.telecom more_vert
- 6 com.android.server.telecom.overlay.common
- 7 What is the Difference Between Android IncallUI and Android Server Telecom?
- 8 Conclusion
com.android.server.telecom is the Android Package(APK) file of the Android Telecom framework that manages audio calls and video calls. The SIM-based calls are managed using the telephony framework and Voice-Over Internet Protocol(VOIP) calls are managed using the ConnectionService API or using a third-party VOIP connection service.
The Android Telecom framework has two different Package names com.android.telecom and com.android.server.telecom.
The com.android.telecom package is stored in a special virtual memory section of the Android Operating System known as User Space where application software and some device drivers are executed.
The com.android.server.telecom is stored in another virtual memory section called Kernal Space where the main kernel extensions and device drivers are stored.
How does Android Telecom Framework Work?
The Android Telecom framework is made up of three important components:
- Telepony API which includes the dialer app.
- The phone Modem.
com.android.server.telecom acts as the medium between the dialer app and the phone modem.
When a call is made on the dialer app, the information is sent to the Telecom framework where com.android.server.telecom receives the information and initiates the setDialing system process. This process informs the Telecom framework to connect to the phone modem and dial the call.
Similarly, when you disconnect the call, the com.android.server.telecom initiates the setDisconnected system process and instructs the Telecom framework to disconnect the call from the phone modem.
The Android Telecom framework manages two important components: ConnectionService and InCallService.
ConnectionService uses VOIP to connect calls. It is mainly used for the telephony ConnectionService that is used to connect calls with mobile carrier networks.
InCallService provides a User Interface for users to interact and manage calls. An example of InCallService is the Dialer app that provides different functions like Dial call, Disconnect call, Hold Call, etc. The InCallService works together with InCallUI whose APK file is com.android.incallui.
The most basic functions of the Android Telecom API include Outgoing calls, Incoming calls, Hold calls, Resume calls, and Disconnect calls.
com.android.server.telecom has Stopped
The problem with the com.android.server.telecom app is that often there are some malfunctions that cause the app to stop working properly especially when you’re making or receiving a call and you get an error message “Unfortunately, com.android.server.telecom has stopped.”
This error occurs mostly because the app cache becomes corrupted or overloaded. If you don’t clear the app cache for a long time then the cache files become corrupted and as the size of the cache files increases the app cache becomes overloaded. This means lower memory is available for the app which causes it to malfunction and you get such errors.
The “Unfortunately, com.android.server.telecom Has Stopped” issue is mostly seen in Android devices running on older Android versions because the system apps have lower memory due to a lot of bloatware.
How to Fix “com.android.server.telecom has stopped” issue?
The best method to fix this issue is to clear the cache of the com.android.server.telecom app and the Dialer app. If that doesn’t fix the issue then you can try other solutions mentioned below.
1. Clear com.android.server.telecom App Cache
- Go to Settings.
- Tap on Apps.
- Tap on the Ellipsis icon(three vertical dots) in the upper right corner.
- Tap on Show System Apps.
- Find the com.android.server.telecom app from the list and tap on it.
- Tap on Storage.
- Tap on the Clear Cache button.
2. Clear the Dialer App Cache
- Go to Settings.
- Tap on Apps.
- Find the Dialer app from the list and tap on it.
- Tap on Storage.
- Tap on the Clear Cache and Clear data buttons.
3. Boot Android Device In Safe Mode
Booting your device in Safe mode helps you identify if the issue is caused by a pre-installed app on your device or a third-party app that you installed from Google Play Store.
In Safe mode, only pre-installed apps like Settings, Contacts, Messages, etc. can be accessed. You cannot access any third-party apps.
In most cases, this issue is caused by a third-party app so you can easily find out which app is causing the problem and you can just uninstall that app.
Follow the steps mentioned below to boot your device in Safe Mode.
- Turn off your device.
- Press and hold the Power button until it vibrates and lights up the screen.
- Release the Power button and instantly press and hold the Volume Down button until you see the logo of your device manufacturer.
If you followed the steps correctly then you will see “Safe mode” on the bottom right-hand corner of your screen.
After entering into Safe Mode, wait for some time to check if the “Unfortunately, com.android.server.telecom has stopped” error is there or it’s gone. If the issue is gone then there is a problem with one of your pre-installed apps. You will need to disable the particular pre-installed app manually to solve this issue.
If the error notification is still there then it means that the problem is caused by a third-party app and not by any of your pre-installed apps. In such a case, you have to manually identify the third-party app that’s causing the problem and uninstall that third-party app.
Make sure to download third-party apps from trusted developers only.
4. Wipe Cache Partition
If the reason behind the error is due to overloaded temporary cache files then wiping the cache partition can fix this error. Wiping Cache Partition removes all the temporary cache files but doesn’t erase app data. It is totally safe. You can wipe the Cache Partition by following the steps below.
- Turn Off your Android device.
- Press and hold the Power button, Volume Up button and Volume Down button together to boot your device in Recovery Mode.
- Press the Volume Down button to navigate below to the Wipe Cache Partition option and press the Power button to select Wipe Cache Partition.
- Press the Volume down key to highlight “Yes” and press the Power button to select it.
- Wait for the process to complete. Once it is completed, use the Volume buttons to navigate to the Reboot or Restart option and press the Power button to restart your device.
After your phone restarts check if the error message is gone. If it’s still there try the next solution.
5. Check for Software Update
Sometimes, this error can occur if you are using outdated software on your device. Updating your software to the latest version of Android can fix bugs and errors appearing on your Android device.
You can check for Software Updates on your device by following the steps mentioned below:
- Go to Settings.
- Tap on About Phone.
- Tap on Check for Updates.
- If a new update is available, tap on Download and Install.
If a new update isn’t available, it means your phone is up to date. In that case, this fix won’t help you solve the problem. You’ll have to try the next solution mentioned below.
6. Flash Stock ROM(Firmware)
Flashing the Stock ROM(Firmware) can help you get rid of this error message. It is a complicated process so use it only if the other methods didn’t work for you.
You’ll need to download the Stock Firmware files for your device and you’ll need a flashing tool to flash the stock ROM.
Flashing the Stock ROM will totally fix the issue and the best part is that you can do it yourself using firmware flashing tools. If you’re using a Samsung device then you can fix the error by flashing Stock ROM using the Samsung Odin flashing tool.
Here is a video that shows how to flash Stock ROM on Samsung smartphones using the Samsung Odin flashing tool.
more_vert is a static constant variable which you will find in the source code of the com.android.server.telecom APK file. The more_vert constant represents the material icon which is part of the IconData class in the source code.
Below is an example of the implementation of the more_vert constant.
static const IconData more_vert = IconData(0xe404, fontFamily: ‘MaterialIcons’);
com.android.server.telecom.overlay.common allows the com.android.server.telecom app to display content over another app with the help of the SYSTEM_ALERT_WINDOW permission. This feature of an app is called Android Screen Overlay.
For example, If you’re playing a game on your device and you receive a call then the call screen is displayed over the game screen because of com.android.server.telecom.overlay.common.
What is the Difference Between Android IncallUI and Android Server Telecom?
Android IncallUI (com.android.incallui) contains the User Interface (UI) data of your phone’s Call dialer app. The elements you see in the call screen for user interaction like the Call button, Disconnect button, Hold button, Speaker button, etc. are stored in the com.android.incallui app.
Android Server Telecom manages audio calls for mobile SIM carrier networks using telephony service framework and video calls using VOIP with the ConnectionService API by connecting to the phone modem.
com.android.server.telecom is the Android Package(APK) file of the Android Telecom framework that manages audio calls and video calls including SIM carrier network and VOIP.
com.android.server.telecom uses the Android Telecom framework that is made up of com.android.server.telecom, telephony API(Dialer app), and Phone Modem.
Sometimes this app stops working unexpectedly due to corrupted cache and other problems. This error can be fixed using the solutions mentioned in this article.