Ticket #829 (new defect)
window stack confused when an app is full screen and a call comes in
|Reported by:||BillK||Owned by:||ainulindale|
If running tangogps full screen and a call comes in, the GUI window stack seems to get confused. If you are lucky, you can exit full screen on tangogps and switch to another desktop and the call screen will start.
If unlucky, a number of things might happen:
- call screen never appears
- something in phone crashes/stops working and removing the battery is the only fix (no response from screen - I suspect keypresses are being passed thru and not acted on)
- press pwr button to bring up "close" dialog doesnt seem to work on tango, but perhaps on phone gui underneath? (not sure)
The ticket http://docs.openmoko.org/trac/ticket/1881 seems to list a possible cause.
My only "mod" to tangogps in the above scenario is a script to switch to landscape using xrandr and fsoraw for display/cpu reservation before starting tangogps.
This has been there since the real early days of asu/fso through to current unstable and sporadicly referred to on the lists. I mostly experience it on tangogps, but seem to remember both ffalarms (in clock mode) and FBReader in full screen having similar problems.