Closed
Bug 1085285
Opened 10 years ago
Closed 10 years ago
[Loop] "Firefox Hello call in progress" notification doesn't disappear when a call is in progress and Loop application is closed
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lolimartinezcr, Unassigned)
References
Details
(Whiteboard: [Test-Run1][tef-triage])
Attachments
(4 files)
fireE (firee-kk-v2.0-SW2E3-1) Loop version: 1.1 , 2168965 Prerequisites: Device A has a contact saved. Device B has a contact saved. Device A has a loop call to device B in "Calls" tab. STRs: 1. Device A makes a call to device B through "Calls" tab. 2. (While device A calls to Device B) in device A, the user makes long-press in "home" button. 3. (While device A calls to Device B) in device A, the user press in "clear all" button -> loop application is closed 4. Device A continues calling to device B, user answers the call in device B. Actual result: In device A, "Firefox Hello call in progress" notification is showed but device A hasn't a call in progress. Device B is "connecting" the call. See attached images. Expected result: When Loop application is closed in Device A the call is finished.
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Comment 2•10 years ago
|
||
Reporter | ||
Comment 3•10 years ago
|
||
Comment 4•10 years ago
|
||
What I've checked is that the feature of showing the "Clear all" option does is not shown in flame devices, this seems to be a task-switcher issue introduce by partner customization. The “Clear All” button should not kill apps using the Attention Screen, as this is not allowed in the regular task-switcher, otherwise this could also affect the GSM dialer too. Besides I am afraid that this could be a certification blocker, Beatriz can you have a look at it and check it with TCL?
Flags: needinfo?(beatriz.rodriguezgomez)
Whiteboard: [mobile app][Test-Run1] → [Test-Run1]
Comment 5•10 years ago
|
||
I have tested GSM calls and they are not killed when pressing the "Clear All" button. IMHO, it seems a Loop issue but if you think vendor is doing something wrong, please let me know and I will double check with them.
Flags: needinfo?(beatriz.rodriguezgomez)
Comment 6•10 years ago
|
||
After doing some tests with Fire E build and this "Clear all" option with GSM and Loop application ongoing, I've seen that the attention screen is not killed in both types of calls but Loop call after clearing all the sheets in the task manager is not working as expected, it's hung in different screens, when you try to hang up, in the feedback screen... The worst is that for recovering the normal behavior of the devive is necessary to restart the device After talking with Borja, he has confirmed that partner customization is not working as expected. They are not killing the Attention screen, as it's part of system and killing system will kill the device, what it's fine but they are allowing to kill the application which has launched the Attention screen (Loop in this case)so all the communication with the Loop and his attention screen is cut and that it makes the app to crash in that fatal way (The changes in the handling of the attention screen for certified applications were introduced in bug 988212) The partner customization should NOT allow killing either the attention screen or the application that has launched that attention screen (with the "Clear all" option or just the single kill of the Loop app) Beatriz, could you communicate to the partner this issue? Thanks a lot!
Flags: needinfo?(beatriz.rodriguezgomez)
Comment 7•10 years ago
|
||
Dear Maria and Beatriz, We will check and modify it, thanks a lot.
Comment 8•10 years ago
|
||
Loli, we got new build where partner seemed to have modified the task manager to avoid the issue. Could you please check it? I can help you to find the new build.
Flags: needinfo?(beatriz.rodriguezgomez) → needinfo?(lolimartinezcr)
Reporter | ||
Comment 9•10 years ago
|
||
(In reply to Beatriz Rodríguez [:brg] from comment #8) > Loli, we got new build where partner seemed to have modified the task > manager to avoid the issue. > Could you please check it? I can help you to find the new build. I have tested with new build and it is working. Scenario: 1. Device A makes call to device B 2. While A is calling and B hasn't picked up, device A tries to close all application in background (long-press in home button and press in "Clear all" button). Actual result: Device A can't close Loop application
Flags: needinfo?(lolimartinezcr)
Comment 10•10 years ago
|
||
Closing the bug as FIXED, thanks a lot to all of you!
Severity: normal → blocker
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [Test-Run1][mobile] → [Test-Run1][tef-triage]
You need to log in
before you can comment on or make changes to this bug.
Description
•