813872 - Receiving calls would crash the system

Status: RESOLVED DUPLICATE of bug 813357

(Firefox OS Graveyard :: General, defect)

Description

[Walter Chen[:ypwalter][:wachen]]

*Environment:
Phone - Unagi
https://releases.mozilla.com/b2g/
2012-11-20 build

*How to reproduce:
  0. Flash your phone
  1. Lock your screen
  2. Call your unagi by other cell phones
  3. After few seconds, hang up the phone.

*Expected Result:
  Nothing happened. And, it would leave a missed call log

*Actual Result:
  The phone showed message of "just crashed" and the touch screen wouldn't work

*Sidenote:
  There was one time when I called out and hung up. Someone called me back. The whole screen turn white and the screen lock come out with dailer, but the touch screen wouldn't work at that time.

Comment 1

[Walter Chen[:ypwalter][:wachen]]

Another different way to crash it with different result:
    If I dialed to unagi and before the unagi respond, turn off the phone power and wait for the phone call, the phone would crash with only one green bar up there. In this case, the touch screen works, but there is no way you hang up or pick up the phone

Comment 2

[Gregor Wagner [:gwagner]]

This happened because the current nightly build was created after the mc->aurora merge. 
The regression comes from bug 810427 and we have a fix in bug 810427.
Bug 810427 was not supposed to land on aurora without the fix but the mc->aurora merge pushed 810427 to aurora and to the nightly build :(

Comment 3

[Tony Chung [:tchung]]

walter, can you also include a logcat in the future?   It is always helpful to record your activities while connected via USB to logcat, and reproduce the issue.  Especially if it's things like crashes, hangs, etc..

Gregor, lets please be more careful please!

Comment 4

[Walter Chen[:ypwalter][:wachen]]

Attachment: logcat

Sure, will do.
attached the logcat log.

Comment 5

[Gregor Wagner [:gwagner]]

Please reopen if you still see it with a new nightly.

Comment 6

[Walter Chen[:ypwalter][:wachen]]

Hi, 

This bug is fixed.
Verified in 11/22/2012 nightly build