I have a legitimate reason for wanting to kill the JVM. There appears to be a bug when instantiating the TextToSpeech class. You can read about it here:
http://stackoverflow.com/questions/4819330/texttospeech-oninitlistener-oninitint-being-called-continuously The listener is repeatedly called (thousands of times until the user Force Stops the app). I imagine the app slows the system down to a crawl (because these calls are made on the UI thread). I've tried various things like calling shutdown on the TextToSpeech class but none of it helps. The only workaround I can think of is to, when it happens, disable TTS (within the app) in future and then kill the JVM. The question is, which approach is better, System.exit() or Process.kill()? On Jan 11, 1:04 pm, Stephan Wiesner <[email protected]> wrote: > > It comes back to designing Apps that do not need to be stopped. > > Let me guess, you do not own a Samsung Galaxy S I9000? > I was constantly switching to the taskmanager trying to kill > processes, uninstalling all apps that ran in the background, etc until > the 2.2.1 patch. . . Android might kill a process/app sooner or > later, but I don't want to lag-wait on a 600$ phone. > The Galaxy is (was) veryyyy slow when a few apps ran. And it is the > phone that most of my users own. > > Sorry, had to let that out :-) > > Greetings from Lucerne, > Stephan -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
