andreasgal/gaia — Issue #683: Some different results when calling into B2G phone, when in different phone apps/states
Author: jhammink
Created: 2012-02-29 20:55:18+00:00
State: open

Latest pull (gonk/gaia 2/28)

For each scenario, I called into the B2G phone, with it in the following state. There was some inconsistencies in which dialogs were then presented; also the * scenarios were where the call couldn't be answered/rejected at all.

Question: why is series of dialogs needed (e.g. homescreen, blackscreen, dialer, call-in)? Why not just call-in dialog or background notification? Also, if this series of dialogs are necessary, why the inconsistencies?

1. Lockscreen - dialer, then call in screen launched; can answer, returns to dialer on call end
2. Homescreen - dialer, call in screen launched; can answer, returns to dialer on call end

*3. Dialer (first launch) - call in screen never launched; cannot answer
*4. Dialer (First Launch, Call Log) - Call in screen is never launched; cannot answer
*5. Dialer (First Launch, Contacts) - Call in screen is never launched; cannot answer
*6. Dialer (First Launch, Contacts=> specific contact) - Call in screen is never launched; cannot answer

~HOWEVER~ - if dialer is the one launched after call termination then dialer, as per scenarios 3,4,5,6 can then handle incoming call event, and call in screen is launched; can answer/terminate calls

7. App Switching Menu (Dialer=>Contacts=>Specific Contact, Browser open) Dialer Launched in background, Dialer open in context menu switches to call in dialog. After switching to dialer in call-in state, can answer/terminate call.

*8. App Switching Menu (Browser, Gallery open) Dialer launches in background; interestingly enough, selecting browser actually invokes the Call in dialog for the incoming call, which can then be answered/terminated accordingly.

*9. Messages (main Screen) homescreen is invoked; but dialer/call in dialog does not come up. (Note: this was a performance issue, after rebooting the phone then call-in dialog invoked as in all other scenarios).

10. Messages (new message) blank screen, dialer, callin. Can be answered/terminated.

11. Messages (specific thread) Homescreen, dialer, call in screen. Can be answered/terminated.

12. Maps - dialer, then call in screen launched; can answer, returns to dialer on call end

*13. Camera - homescreen is invoked; but dialer/call in dialog does not come up. (Note: NOT a performance issue, same thing happens after reboot)

14. Browser - homescreen, blankscreen, dialer, call-in. Can be answered/terminated

15. Gallery - (main view) homescreen, blankscreen, dialer, call-in. Can be answered/terminated

16. Gallery (swiping through pics) homescreen, blankscreen, dialer, call-in. Can be answered/terminated

*17. Video (main view) - homescreen; no dialer, no call-in. Call Cannot be answered/terminated

* 18. Video (playing video) - Video stopped - homescreen; no dialer, no call-in. Call Cannot be answered/terminated

19. Facebook - homescreen, blankscreen, dialer, call-in. Can be answered/terminated

20. Marketplace - omescreen, blankscreen, dialer, call-in. Can be answered/terminated

21. Music (main screen) - homescreen, blackscreen, (no dialer), call-in. Can be answered terminated.

22. Music (playing specific song) - homescreen, blackscreen, dialer, call-in. Can be answered terminated.

23. Settings (main view) - homescreen, blackscreen, dialer, call-in. Can be answered terminated.

~haven't tested lower-level settings; as these will likely change and are equivalence classes anyway~

24. Clock (main view) - homescreen, blackscreen, call-in. can be answered/terminated.

25. Tower Jelly (loading animation) - homescreen, blackscreen, dialer, call-in. can be answered/terminated.

25. Tower Jelly (game in progress) - homescreen, blackscreen, dialer, call-in. can be answered/terminated.