top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Does MediaServer process every reboot volntarily on Android

0 votes
207 views

What if MediaServer's main thread is kept busy during MediaPlayerService::instantiate.I Mean what if there was a while loop in one of them.Will android be able to trigger a watchdog or reboot only that process ?

posted Jun 6, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

mediaserver process, which contains media player service and other media-related services,is forked by init. If init notices that mediaserver process has exited, then it re-forks it.
As far as I know, init does not do anything if mediaserver process is still running, but is not behaving properly(for example, one of it's threads is in a CPU-bound infinite loop). In other words, there is no watchdog on mediaserver process.

answer Jun 6, 2013 by anonymous
Similar Questions
+1 vote

For my project I need to know that - is there a way to log or capture the cause of android reboot, whether user manually powered off / rebooted the devices or wether system_server got restarted by adb kill or it was watchdog who restarted the device.

0 votes

I made an app (Java based, without JNI stuff), to stress our android device. It does some intensive work and /sdcard IO writes (They are 60 threads) all of them are with FOREGROUND priority.

After a couple of minutes appeared crashes in different places (system_server - FinalizerDaemon timeouts) and then the Watchdog rebooted the device with message Watchdog killing system process: null.

I tested it also on Nexus 7 and other android devices in production, the behavior is the SAME. It seems that some apk, can overload the system and to reboot the user-space.

Is this behavior (under high pressure/load from FOREGROUND threads) is by design in android Jelly-Bean and are there any plans for some remedy for this situation.

+1 vote

Who controls putting process pids in different cgroups? Kernel or Userspace/Framework?

+1 vote

I was studying golocker application and I found some weird property on its application tag:
ANDROID:PROCESS="ANDROID.PROCESS.ACORE"

So they are running their app on the main android process.Does anyone know the reason for that and what are the consequences? I also realized that they are running their lock screen service in foreground state but not showing the notification on status bar (likely using some hack).

0 votes

We have tried to do build with the normal user, but it failed after some time without giving any permission issue. I have made compilation directory permission as 777 and the same code has been compiled successfully with sudo or root user.

...