Operating room android system, which now stands on most gadgets, works well and is quite welcoming to its users. But still, there are times when an unexpected error appears that interferes with the operation of the device or prevents the program from starting. Now we will consider five main problems that android users can overtake.
Phonebook problems
Usually a mistake android process acore occurs when working with phone book. When you try to display a contact list or save a new number, nothing comes out. And if it has already occurred and the application is stopped, then you can solve such a problem with your device by the cardinal method - make a complete reboot of the gadget and return it to the factory settings. But this method is not suitable for those who have many important programs. After all, after a hard reset, all settings get lost, which means that applications need to be installed in a new way.
Fix problems with Android-based software
If the first way to solve the android acore process does not suit you, then try another. First you need to see what applications are in your gadget.
Quite often, when users install additional utilities on Android that are responsible for wi-fi and configuration wireless network, this unexpected error occurs.
Before installing such applications, make sure that your device is compatible with the program. The android process acore error itself is due to problems with the display of widgets for these applications.
To fix the problem, go to "settings - applications - application management - all applications" and check there are programs for working with the wi-fi network. Try to remove them and install a version that works compatible with your device. Do not be scared if you see the inscription “application stopped: Android Phone Com error”. We will consider this problem below.
Android does not start
If the android does not want to turn on, then there may be a software error, or problems with the iron part. In the first case, most likely, after installing the next software, the system files were damaged. And ultimately operating system flew off. There is nothing left to do but to reflash your gadget. To do this, find the firmware on the Internet for the model of your gadget, upload it to the memory card and reflash the gadget.
It is worth remembering that each model of a phone or tablet requires a special approach. So the process of reinstalling the system should begin by looking for information about your device. Error and system shutdown is the most common among users, and therefore it is worth looking for firmware that will work on the device.
Gadget Lock Issues
In addition to the android acore process, there are other problems that can cause the device to stop working. If the user forgets the password from his gadget, the system blocks the device after incorrect data entry and does not allow to use the functions. Here you need to take measures to unlock.
This is not very difficult to do. Can sometimes help special utilities to unlock gadgets. Typically, these utilities are made by the developers themselves for their devices. Often, even a password-protected tablet can not resist the onslaught of such programs.
If such utilities do not help, then get out of this situation - phone hard reset. You can read about how this is done in the description of your gadget. But it is worth remembering that after a complete reboot all settings, programs and contacts fly off. The programs you downloaded will stop functioning. It won’t touch the memory card.
Android multimedia issues
If you supply your device with various programs for a long time that have not passed the Google Market test, you can easily get an unexpected error called android process media. If in the case of the android process acore, everything is difficult to solve, then everything is simple. We need to go into the settings - applications - all applications. We find there a multimedia storage. Click "erase data." Now we are looking for a "multimedia storage" and again we delete everything. We reboot the gadget and enjoy quality work. To prevent the appearance of android process acore and android process media, you need to download tested applications and check whether your device is compatible with them.
Failure with “Foun.com” - what to do?
If your unexpected gadget Android Phone Com crashed on your gadget, it means that there was a serious stop in the software. It will help either full reset, or change the firmware of your device. Usually everything is decided after a hard reset, but if this does not help, then only the installation of a new firmware remains.
Android Phone Com error can also occur due to malware software. So do not skimp on antivirus software, unless of course you do not want to see the message “Android Phone Com Error” on your screen at one point. It may also be that this error occurred due to the removal of important system fileswho are responsible for the communication and operation of the program.
In any case, there are no fatal errors, and Android Phone Com is no exception. And if it's not hardware, then everything is decided by a variety of antiviruses, full reset or firmware (this is an emergency). So do not worry about Android Phone Com or about the android process acore. We also recommend using antiviruses so that an unpleasant situation does not occur and the program is not stopped at the most inopportune moment.
The Android operating system is quite flexible and versatile, but unfortunately there are various unpleasant roughnesses, such as fast battery consumption.
One of the articles on the site described in detail how to reduce battery consumption, but there is such a MediaServer Android process that can drain a tablet or smartphone in a few hours. Why this is happening and how to deal with it, this article has been written specifically for this.
Having a problem with MediaServer Android
The MediaServer process in Android is responsible for scanning and detecting media files on internal memory or memory card. Ideally, the process should stop from detection, but if any file is damaged, then MediaServer will loop and consume more energy, as the system tries to “solve the problem” and allocate additional resources for it.
How to solve MediaServer Android problem?
If you use Android as external storage, then always perform “Safely Remove” from the computer. As stated above, the MediaServer Android problem occurs due to file corruption. 
If you do not correctly disconnect Android from the PC, then you damage the flash memory and, accordingly, the files on it.
Use a high-quality microSD memory card, firstly they are reliable, and secondly they work faster.
How to choose the right memory card and what you should pay attention to, read the article - All about MicroSD.
Never, under any circumstances, do not defragment flash drives and memory cards - this is certain death for them.
If you have a plentiful amount of music files on Android, then 80% confidence that it is in them! In order to accurately understand whether this is so, you have to do this:
If on your Android there are doubtful video files - not fully downloaded files or they are broken, try deleting them.
Delete or copy all all files (backup) from the internal and external memory and format the drives using standard Android tools.
In order to format the drive go to Memory -\u003e Clear SD 
After that, return all the files to the place.
Check for bad sectors memory flash drives. To do this, connect Android to your computer as a Drive and select the right mouse button - Properties - Tools - Run the check: 
Perform the two proposed tests in turn. If errors are found, they will be automatically corrected.
If you couldn’t solve the problem with the above methods, then you should try the special MediaServer Killer application.
This application requires the presence of Root rights, if they do not exist, then it will not work. The purpose of MediaServer Killer is to stop the MediaServer process if it takes a long time.
If you have “your own ringtone” set, discard it and set the standard ringtone to the call. Fast charge should disappear.
That's all! Read more articles and instructions in the section. Android Hacks and Articles . Stay with the site, then it will be even more interesting!
Developers of the Android platform spend a lot of money and effort on optimizing and finalizing their platform, but, despite all the efforts, situations are quite common when users of Android devices complain of various kinds of errors that prevent them from fully using the device. Android error process media is one of these, but fortunately it is easily solved and how to eliminate it, if it appears, we will find out today.
It should be noted that this is a fairly common problem, and as practice shows, many Android users have already encountered this problem or heard about it from friends.
The error can occur absolutely on any device and, as a rule, due to a failure in one of the two running services - “Download Manager” and “Media Storage”. It also happens that it happens when you try to install programs from Play marketthat are not compatible with your device and have not been tested on the service.
To continue to avoid the occurrence of such an error, install programs from trusted sources (sites), as well as check them with antivirus software.
What to do if an error has already appeared? How can I fix it, and is it possible to do everything on my own? You should not panic and quickly run to the service center, since you can solve this problem yourself and this will not make you any special difficulties. The methods described below help to effectively defeat the emergence of android process media, so grab your device and repeat the steps.
Methods for resolving android process media error
The first method is “Removing the cache and data”
The second method is “Checking Google’s synchronization and multimedia storage”
The third method - "Reset to factory settings"
Use this method only in extreme cases, as well as before performing a reset on the computer, as they will be completely deleted and it will be impossible to restore them.
- Go to the "Settings" menu section and find the "Restore and Reset" item.
- Highlight the “Reset Settings” submenu and select “Reset Phone Settings”. Click the Erase All button.
- Now we reboot the phone and the error should disappear.
To make sure that the device is working and not displaying such an error, after the manipulations have been done, launch the Task Manager and Gallery applications, and also restore synchronization with your Google account.
In almost 95% of cases, these methods help completely get rid of the android process media error, but still it happens that these actions do not lead to a solution to the problem. In this case, I still recommend contacting a repair shop, as the problem hides much deeper than it actually is.
Let's be honest: most of the interesting options for setting up Droid devices are hidden and require rooting the device. Nevertheless, not everyone prefers to get root - some out of fear of losing the guarantee, others because of banal laziness. We decided to consider alternative methods acceleration of devices on the platform from Google, for which you do not need superuser rights.
Introduction
Google is constantly improving the performance of its system. But "clean" Android is now quite rare - manufacturers, as a rule, modify firmware, which does not always positively affect performance. In addition, besides it, it would be nice to take care of energy conservation, and these are often mutually exclusive things. Nevertheless, such opportunities exist even in untreated Android, although there are not many of them.
Removing / disabling embedded and unnecessary applications
Prior to the release of the fourth version of Android, it was impossible to disable embedded applications without root rights. This brought buyers of branded gadgets inconvenience, because each manufacturer strives to shove as many programs as possible that the end user simply does not need and in total eat a decent amount of resources. In the fourth version of Google’s axis, such an opportunity appeared. To disable a built-in application, go to "Settings -\u003e General -\u003e Applications -\u003e All", select the desired software and in the "Application Information" click the "Disable" button (or "Delete Updates", and then "Disable" "). To enable it, go to the "Disabled" tab and perform a similar procedure.
However, not everything is as rosy as it seems at first glance. Firstly, disabling does not affect the permanent memory - the application, as it was installed, remains. Secondly, not all can be disabled. Only a few applications allow you to do this trick. I will not give many specific tips for disabling applications, since on each device their list is different. Here is a short list of what most users don’t need, but constantly hang on the system and take up memory:
- “Browser” - why, if there are more convenient and easier alternatives?
- "Calendar" and "Calendar memory" - did not notice that someone actively used them.
- "Email" and "Exchange Services" - it seems everyone is already sitting on Gmail.
- “Google Search” is a rather useless function if you have a browser (carefully, it also disables Google Now).
- "Google Keep", "Google+" and others are not always desired applications from google.
In addition, I recommend turning off (deleting) widgets and live wallpapers. In addition to the fact that this functionality requires memory and processor time, it also eats up the battery. So to increase speed it is better to cut down such things. You can turn off the effects on the lock screen. In my case (Samsung with standard firmware) they are located in “Settings -\u003e Device -\u003e Lock screen -\u003e Effect when unlocking”.
Leaders: INFO
How application shutdown works. After clicking on the “Disable” button, the setApplicationEnabledSetting () method of the PackageManager class is called, which changes the state of the application to COMPONENT_ENABLED_STATE_DISABLED_USER (by the way, it appeared in the first Android).
Set up energy saving and use developer options
To speed up the work of the gadget, you can also adjust the energy saving parameters. Of course, this will reduce battery life, but it can speed up quite significantly. To do this (in my case), you need to go to "Settings -\u003e General -\u003e Energy Saving" and either move the switch located in the upper right corner, or remove the necessary checkboxes.
This works on different platforms in different ways, and there is no public API - of course, there is a PowerManager API, but this has only a very indirect relation to energy saving. However on Samsung Galaxy Note 10.1 (however, as for the other South Korean giant Droid devices), energy saving is controlled via DVFS - Dynamic Voltage and Frequency Scaling, the very one with which Samsung “falsified” the benchmark results (I note in brackets that this was not a real falsification - just for some benchmarks and applications, the device worked to the limit of its capabilities).
To disable system animation (animation remains in applications), go to the developer options menu, which is hidden by default. To access it, tap seven times on the “Build number” item, which is located in the “About device / About phone” menu. Then go to the menu that appears and turn off the entire animation: the parameters “Window animation scale”, “Transition animation scale” and “Transition duration scale” are set to “Animation is disabled” (in the firmware of other manufacturers these options may have a slightly different name).
In the same menu, you can limit the number of background processes. The latter, however, should be done with caution - instead of speeding up, it is possible to slow down due to the fact that frequently used processes will be beaten and restarted. Therefore, by the way, all sorts of task killers are not recommended.
Application Acceleration
To speed up individual applications, you can clean their cache. This is done in the same place where they can be disabled / deleted, that is, "Settings -\u003e General -\u003e Application Manager -\u003e All", select the application you need and click the "Clear Cache" button.
It also makes sense to install less resource-intensive applications - for example, in my case, Smart Launcher takes less memory than the native Samsung TouchWiz does. Specific tips will be provided in the sidebar, but I don’t recommend particularly following them, since it all depends on your needs. The main thing in this case is to choose the right size / functionality ratio.
To determine the memory consumption, you can use this method: install some terminal with Busybox, determine the PID of the desired process (using ‘ps w’) and look at the file / proc // status. In this case, however, you need to consider the architecture of Android - the application can be posted in several processes.
If this method is too difficult for you and you do not want to bother with each application, there are several graphical analogues of the top utility in the market. I liked one of them, called Process Explorer, the implementation of which, however, seemed incomprehensible - why use a browser to view the list of processes?
By the way, the service Google play there is a habit of suddenly updating a bunch of applications, which, of course, eats up resources. Disable this service It’s not possible, but you can disable the update itself. To do this, go to the Play Store, call up the menu (hint: if it doesn’t come out, use the soft keys to “pull” from the left edge), select “Settings” and set “Never” to “Auto-update applications”.
In the same way, it makes sense to disable account synchronization (which, in addition to a possible increase in performance, will amuse your paranoia). To do this, go to “Settings” and look for where the item “Accounts” is located, then select account and turn off synchronization (as an option, you can disable only individual and unnecessary types of synchronization, such as, for example, google contacts+ or calendar. - Note Ed.).
Disable Media Scan
By default, Android scans all external storage devices (SD cards) for multimedia files. This function, although useful, slows down the system quite a lot. You can disable it. For new drives, create an empty .nomedia file in the root. But to disable the display of existing files in Android 4.0 and later, you need, in addition to creating this file in the folder you need, clear the data and cache for the Gallery and Multimedia Storage applications and force them to stop. After the next launch, all multimedia files are indexed already taking into account the created .nomedia files.
Here are some tips on the most famous brands. It is worth noting that these tips are only suitable for official firmware, so if you have modified firmware, you can safely skip the section.
Samsung
If you are the owner of any of the devices of this brand, you probably noticed that switching to the main screen by pressing the Home button slows down a bit. This is due to the fact that double-clicking starts S Voice - a speech recognition system. If you do not use it, you can disable this function by unchecking the “Open. Home button. ” In addition, if you accidentally turned on the wake-up command, it is better to turn it off - using this option affects the battery power quite strongly.
In addition, on some Samsung devices it is possible to disable the effects of the launcher. To do this, make a long tap on an empty spot on the home screen, select “Home screen settings” and in the “Transition effect” submenu choose “None”.
HTC
In some cases, on HTC devices, the error message service may slow down. Although it’s not recommended to touch such things, you can disable this option by going to “Settings -\u003e About phone -\u003e Send HTC” (Tell HTC) and removing the corresponding checkboxes there.
Sony
On Sony Xperia SP there is a situation when the phone suddenly starts to slow down. You can try to fix the problem by uninstalling updates for Google chrome: "Settings -\u003e Applications -\u003e Chrome -\u003e Uninstall Updates."
Greenify
The Greenify application allows you to forcibly euthanize unnecessary processes (which you can choose) while the device is sleeping, and prohibit their calling from third-party processes. In this, it differs from task killers, which in no way prevent the restart of background applications from external events (by timer, by the demand of another application or by a system event). Unfortunately, some of the functionality is available only on rooted phones - in particular, the most important function of falling asleep applications a few minutes after falling asleep.
The reason is that the forceStopPackage () method, which allows Greenify to put applications in an inactive state, is internal and is available only to system applications or those that work with root privileges. In non-root mode, it remains to use only the killBackgroundProcesses () method, which does not completely unload the process from memory, so system events continue to come and wake it up, which does not correspond to the Greenify ideology.
Therefore, to implement the functionality in non-root mode, the Greenify developer took a completely different and very inventive path. During installation, the application is registered as an Accessibility Service, thus gaining access to the system interface, and then simply calls the application manager and clicks on the necessary buttons to kill the application through the standard menu android settings. Unfortunately, this operation is not possible during sleep mode, therefore Greenify can euthanize applications on non-rooted smartphones only after the user clicks the appropriate button.
ART
Android 4.4 introduced a replacement for Dalvik - ART, Android Runtime. It provides AOT compilation. In order to understand what it is and what is the advantage of ART, you will have to take a brief excursion into history.
At the time when the foundation was laid for Android, Java was chosen as the programming language - to the greatest extent due to the fact that it was supposed to use the OS on a variety of platforms. And for all he was good, except for one thing - the speed of Java-based applications was quite low. This happened because the code was actually interpreted.
Time passed. In Android 2.2, a JIT compilation was added to the Dalvik virtual machine. This made it possible to achieve a rather significant increase in speed, but did not solve all the problems. And in the KitKat version, ART appeared, which allows you to compile applications not even at runtime - during installation. You can enable it in the same developer menu where we turned off the effects. This, on the one hand, increases installation time and size, and also at the first start-up, it takes considerable time to convert all already installed applications into the native code. On the other hand, the speed increase after turning it on is 50% on average, and even more for individual applications (in particular, scrolling has become much smoother).
But there are also disadvantages to ART. Some of them are obvious - for example, incompatibility with individual obfuscators and applications. On the other hand, they simply do not concentrate attention, although it would be worth it. To those I will attribute possible security problems. Experiments conducted relatively recently (at the HITB conference in May) show that if a specially crafted DEX file is poked, the translator (dex2oat) crashes. In addition, if you find vulnerabilities in the ART itself, it will be possible to create user-mode rootkits. In addition, the boot.oat image generated by the translator has a fixed base address (0x700000), which allows circumventing ASLR under certain conditions.
At the same time, from the point of view of reverse engineering, the static analysis of OAT files is still difficult - for the reason that there are simply no familiar method names in the code. It is understandable. But, since the OAT file format is actually ELF, you can use tools designed for the latter, such as GDB. As for the dynamic ... There is no toolkit for it as such.
ART will be enabled by default in the fifth version of the OS from Google (and Dalvik, accordingly, will be removed). In my opinion, given the potential security problems, it’s too early to completely abandon Dalvik, so here I disagree with Google’s policy. However (with this in mind), it is all the more worth including ART on KitKat to test the necessary applications.
Conclusion
Despite the flexibility of the Android platform, it is difficult to speed up your device without using custom and / or root firmware. But not impossible, as evidenced by this article. Finally, I will give you universal advice: install only those applications that you really will use, all the rest say a solid "No."
Lightweight Android
I will give a short list of lightweight analogues necessary programs for Android. This list is minimal, including only the most, in my opinion, necessary:
- Instead of Google Maps, you can use RMaps. Not only is this application lighter, it is also much more functional.
- Bulky Adobe Reader can replace Mupdf.
- There are a lot of readers. From lightweight I can advise AlReader and FBReader.
- From browsers you can put Lighthing Browser, de facto representing a lightweight standard.
- It is better to replace the extremely heavy Feedly RSS reader client with the light FeedMe (carefully, only for smarts).
What gives root? (editor's word)
About a year ago I wrote an article about accelerating the work of new android versions on obsolete devices. In it, I talked about several root-requiring tricks with which you can increase the performance of a smartphone by unloading from random access memory all non-critical system components for operation. In short, the article described five main methods:
- Tuning the Low Memory Killer mechanism to teach the system to unload background applications from the device’s memory faster than it does by default. The trick requires modification of the kernel parameters, and therefore is available only on a rooted device. Used applications: Auto Memory Manager or MinFree.
- Removing all unnecessary system applications from the / system / app and / system / priv-app directories. It can be done using any file manager with root support.
- Disabling unnecessary system applications using Bloatware Freezer, disabling their startup using Autostarts.
- Installing an optimized custom kernel and activating the Zram mechanism, as well as the TCP westwood saturation control algorithm. Overclocking the processor.
- Tuning the kernel virtual memory subsystem in order to provide faster unloading of data from caches.
Problem : The battery on the Samsung Galaxy is very quickly discharged, and in "Settings - Battery" it is displayed that 40-50% is eating the MediaServer process
What is it all about : The MediaServer process in Android is responsible for scanning and detecting media files on the internal memory or memory card.
Decision
:
Most fully disclosed
- MediaServer Android or fast battery drain problem
- If android device If it is used as an external drive, then always perform “Safely Remove” from the computer. As stated above, the MediaServer Android problem occurs due to file corruption.
- Use a quality microSD memory card (well, that’s understandable)
- Do not defragment flash drives and memory cards - this is certain death for them. (???)
- Fix multimedia files (connect the device as a drive, run the utility to fix errors in MP3 files - then scan and FIX)
- If on the device there are doubtful video files - incomplete or broken, delete.
- Add an empty file to the root of the music folder (and to all folders and subfolders with media content) .nomedia that would not be indexed content, and then always use a player that can scan the folders indicated to it itself and not use the system library. For example - PowerAMP
- Remove from the names of .mp3 files and from their tags all characters, including “unwanted ones” (such as “&” and “_”)
- Clear media storage: "Settings\u003e Application Manager\u003e All\u003e Media Storage\u003e Clear data (+ Clear Cache)"
- Change the melody of the alarm clock to “basic”, instead of the .mp3 file
- Edit the build.prop file by adding lines:
pm.sleep_mode \u003d 1
ro.ril.disable.power.collapse \u003d 0
media.stagefright.enable-player \u003d false
- Use program " Rescan Media ROOT"
- Use program " App to Kill Mediaserver"
- Disable Media Storage via Autostarts
- Use Mediaserver Killer (requires root, it is doubtful, because if there is root, it is easier to freeze / delete)
- Check media for errors.
- Format the media by first making a backup.
Another recipe
:
I continued to study the problem, and found out that the problem is not in the mediaserver process, but in the so-called “wakelocks”, which the programs “ Wakelock detector”And“ BetterBatteryStats”.
In the morning the following evil “wakelocks” surfaced: Alarmmanager (processes Google Maps, Viber, etc.) and Audio_out2 (process 1013), which for 9 hours of loading statistics worked 8.5 (!) hours. Mr. told the world in detail about them. [email protected]$
.
Quote: “ ... AudioOut_2 ... To fix: open the settings, select a sound. Turn off keyboard sounds, touch sounds, screen locks and touch vibrations. It's a matter of habit, but the extra battery life that you get only by solving this ridiculously simple problem is more than worth it ...”
The sounds of clicks and vibration feedback were always turned off, but lock screen vibration feedback - not. This is the reason I have been looking for so long. After turning off the vibration response "gone" mediaserver and Audio_out2 , and with them the problem of "night zhora".
