Nvm my last mail. I figured out that a Runtime.getRuntime().exec() call was blocking my first process and that the second process is the command that I try to execute. But I still have no idea why this call is blocking.
Peter On Sep 30, 11:07 am, Peter <[email protected]> wrote: > Hello, > > I created my own android build for a device together with a custom > home application. Let's call the the HomeApp. This HomeApp is the > first application that is started on my device. > > Somehow I get the following problem: In 50% of the boots my screen > remains black. When I enter a ps command on the console I see that my > HomeApp is running twice. (When everything goes correct it only runs > once). When I check what the parent process is of the second HomeApp > process, I see that it's the first HomeApp. So it looks like it's > forked. But I have no idea why. There is no code inside this > application that does a fork, nor is there any reason why I would want > this. Next to that when I kill the second process the first one > becomes visable and runs as normal. So, I don't want that second > process and everything should be fine. > > One important note is that when I view the logcat I see that the first > HomeApp is started. However there is not a single trace found in the > logcat about the second instance. > > Anybody has any idea what could have cause the creation of the second > process of the HomeApp? I have no clue where to start looking. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
