View Single Post
Posts: 114 | Thanked: 201 times | Joined on Apr 2009
#57
If steps 1-8 outlined in my previous post actually work correctly 100% of the time for anyone on Fremantle, could you please speak up with your firmware version? (Failure reports would be appreciated as well, but success reports would be more puzzling.)

Originally Posted by jukey View Post
The problem seems to be that you are not killing the microb browserdeamon after the last microb window is closed.
Bingo. What we're supposed to see after "MicroB ready" is this:

Code:
Checking to see if we should kill MicroB
Checking to see if we should kill MicroB
Closing MicroB
(which has been observed at least once in the wild -- which makes this report rather troubling).

Originally Posted by jukey View Post
Is a system message (don't know the correct word for that) sent if the last browser windwo closed?
Is any documented signal sent when the last window closes? Not that I know of. I'm relying on behavior gleaned from tracing MicroB in the SDK to determine when the last browser window closes. Clearly, at least in your case, that behavior is not happening.

Originally Posted by jukey View Post
What is the next step I can do to help you?
Can you repeat steps 1 to 6, and this time, find the PIDs for browserd ("ps -ef | grep browserd") before step 4, after step 4, and after step 6? (In the SDK, there are two browserds after step 4, and one of them closes and is replaced after step 6; it's this change that I have several ways of looking for. If this isn't happening consistently on the device, we're back to square 1 ...)
 

The Following 2 Users Say Thank You to steven676 For This Useful Post: