Re: Dangers of "hot reboot" (killing the System Server)

[Voteforpedro]

You'll live. It's there usually as a safety precaution, in the case of.apps it's just a quicker way to.reboot without seeing the splash screen.

On Jun 7, 2013 3:07 PM, "Patrick Turley" <ptu...@gmail.com> wrote:

There are a number of web pages that recommend doing a "hot reboot" by simply killing the System Server.  There's at least one app called "Hot Reboot" that does this.

On the face of it, this seems dangerous.  For all I know, the System Server could be in the middle of some vitally important work, and killing it could leave the system in an inconsistent state.

On the other hand, I'm an Android n00b, and maybe the System Server is *designed* to be able to die without harming anything.

I simply don't know, but I'd like to hear about it from someone who does.  Does anyone have an *informed* opinion about how dangerous it is to kill the System Server?

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-platfo...@googlegroups.com.
To post to this group, send email to android-...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-platform?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jeff Sharkey]

This is similar to the battery being pulled from a running device,
which the system_process is expected to gracefully recover from.
Critical data inside the system is saved using utilities like
AtomicFile and SQLite transactions to ensure recoverability.

Platform developers use "adb shell stop && adb sync && adb shell
start" daily without issue, which kills and restarts the
system_process.

j

On Fri, Jun 7, 2013 at 12:57 PM, Patrick Turley <ptu...@gmail.com> wrote:
> There are a number of web pages that recommend doing a "hot reboot" by
> simply killing the System Server. There's at least one app called "Hot
> Reboot" that does this.
>
> On the face of it, this seems dangerous. For all I know, the System Server
> could be in the middle of some vitally important work, and killing it could
> leave the system in an inconsistent state.
>
> On the other hand, I'm an Android n00b, and maybe the System Server is
> *designed* to be able to die without harming anything.
>
> I simply don't know, but I'd like to hear about it from someone who does.
> Does anyone have an *informed* opinion about how dangerous it is to kill the
> System Server?
>
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-platfo...@googlegroups.com.
> To post to this group, send email to android-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/android-platform?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
Jeff Sharkey
jsha...@android.com

[Patrick Turley]

JBirdVegas,

Thanks for your reply.  The fact that you have a million+ user base at your back means a lot.

On Saturday, June 8, 2013 11:30:24 AM UTC-5, JBirdVegas wrote:

We (AOKP) have features that require restarting the SystemUI to take effect. We have a large userbase (million+) and with the exception of the annoying delay while the system restarts have yet to see a problem.

I'm not saying its the most ideal method of applying features but it works.

Is it safe? The SystemUI is an app and as such lives the Android life cycle so killing it shouldnt be too much of a rish