Closed Bug 1082511 Opened 10 years ago Closed 10 years ago

UI Screen becomes blank after call disconnects

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1081528

People

(Reporter: poojas, Unassigned)

References

Details

(Whiteboard: [CR 737916])

We are seeing few App UI issues regarding MO and MT call.
I feel both the issues have same root cause so have mentioned in same Bugzilla.
If necessary will split them in two.

With MT Call
STR:
1. Open any app say settings
2. Make a call on DUT from other device.
3. Disconnect the call by either way
4. As soon as call disconnects , the background app i.e setting will comes in foreground

Actual Behavior:
  Setting app UI will be a white blank screen. It wont restored back until we 
  long press the home key.

Expected Behavior:
  Settings app UI should get restored to its previous state and it 
  should not be blank.

Note: Issue doesn't come with homescreen i.e if we don't have any app on background

Issue with MO call:
STR:
1. Make a MO call from DUT to reference device.
2. Attend the call from reference device.
3. Disconnect it by either way.

Actual result:
 Observe the green blank screen on DUT as soon as call disconnects.
 Similar to above issue, just change in screen color instead of white it will be 
 green
Expected Result:
 Device should show proper Homescreen.

Gaia and Gecko info:
Gaia "f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1"
Gecko "db7fce920e7d782d9f601384dc95924abcdaeeb8"
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
Whiteboard: [CR 735765] → [CR 737916]
Summary: background app UI becomes blank(white screen) after MT call disconnects → UI Screen becomes blank after call disconnects
Looks like a duplicate of bug 1081528. Can you confirm Pooja?
Flags: needinfo?(poojas)
Yes its similar to bug 1081528
Flags: needinfo?(poojas)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
blocking-b2g: 2.1? → ---
You need to log in before you can comment on or make changes to this bug.