982545 - [Tarako][Dialer][Camera][Gallery][Video][Message]After hang up phone, cannot resume to some apps

Status: RESOLVED WORKSFORME

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

Description

[Mike Lien[:mlien]]

[Device]
  Tarako
---------------------------------------------
[Reproduction build] - V1.3T
  Gaia      1f00cb5e533e698c5607bfce668a945270e79944
  Gecko     N/A
  BuildID   20140312075534
  Version   28.0
---------------------------------------------
[Reproduce Steps]
  1. Launch Camera/Gallery/Video/Message app
  2. Make a phone call to Tarako and pick it up
  3. After few seconds,hang up the phone

---------------------------------------------
[Expected Result]
  After hang up phone, resume to previous app normally

---------------------------------------------
[Actual Result]
  It back to home screen and previous app was killed

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Please provide the logcat for this as well as the adb shell dmesg

If you believe that it is due to OOM please look at :
https://wiki.mozilla.org/B2G/Debugging_OOMs#Step_1:_Verify_that_it.27s_actually_an_OOM
and
https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Debugging_OOMs

Comment 2

[Mike Lien[:mlien]]

Attachment: logcat.txt

Comment 3

[Mike Lien[:mlien]]

Attachment: dmesg.txt

check with dmesg, this problem is due to OOM

Comment 4

[Mike Lien[:mlien]]

My concern is if user want to send a message and on editing phase, this situation will never leave any draft to let user resume to edit
This is not make sense

Comment 5

[Joe Cheng [:jcheng] (please needinfo)]

Marvin, this is likely to be platform limitation on tarako. FYI
we will minus this bug

Comment 6

[Marvin Khoo [:Marvin_Khoo]]

Hi Joe,
thanks for info. noted. agreed minus.
Will add request to corresponding PM to plan auto save to Draft feature when platform intent to kill app in background.

Need UX to jump in for Gallery editing, i will initiate mail for discussion,
when platform intent to kill half edited image, what should we do.

Hi Mike Lien,
Consider low end device, the expectation result needs to be revised correspondingly.
1. if platform encounter OOM, activities such as composing msg, editing image, half edited emails (with attachements), half edited calendar event, half edited Contacts, shall consider to save in draft or recover.
2. for 3rd parties apps such as Marketplace apps, or whatsoever should not be our consideration here.

1.3T is our fist low end device, will try our best to close all these UX issue.
Thanks!

Comment 7

[Jason Smith [:jsmith]]

(In reply to Marvin Khoo [:Marvin_Khoo] from comment #6)
> Hi Joe,
> thanks for info. noted. agreed minus.
> Will add request to corresponding PM to plan auto save to Draft feature when
> platform intent to kill app in background.
> 
> Need UX to jump in for Gallery editing, i will initiate mail for discussion,
> when platform intent to kill half edited image, what should we do.
> 
> Hi Mike Lien,
> Consider low end device, the expectation result needs to be revised
> correspondingly.
> 1. if platform encounter OOM, activities such as composing msg, editing
> image, half edited emails (with attachements), half edited calendar event,
> half edited Contacts, shall consider to save in draft or recover.
> 2. for 3rd parties apps such as Marketplace apps, or whatsoever should not
> be our consideration here.
> 
> 1.3T is our fist low end device, will try our best to close all these UX
> issue.
> Thanks!

I think this is the wrong direction to go down. The problem here is this will require implementation in every single app to handle session state individually in the app itself in case the app gets killed by the LMK. Introducing session state handling for every single app would be a lot of feature work to implement, which is likely going to pose a lot of risk to the Tarako schedule right now. The simpler solution is to handle this at the system level by ensuring that the mostly recently used app retains in the background, especially in cases where a different app took priority outside of the user's control (e.g. phone call, alarm goes off).

Marvin - Does that make sense?

Comment 8

[Marvin Khoo [:Marvin_Khoo]]

Hi Jason,
I'm not sure if system has such ability / permission to save such status. I would say the proper way is each app shall consider such error handling. 

Platform has its limitation, and apps (including native and Marketplace apps) shall have ability to know the constraint. if kernal/LMK be able tell apps that a killing session is being triggered, apps shall save its status before get killed / self-terminated, so apps knows where to get data and be able to retrieves its necessary info when relaunch.

For Tarako v1.3T, I agree we should do whatever we could to improve this. if engineers have not much time to fix this, I would say this is 1.3T platform constraint.

BR,
Marvin

Comment 9

[John Hammink]

Can we please recheck this on latest version?

Comment 10

[Mike Lien[:mlien]]

verify with today's daily build, these apps won't be killed and can be used after hang up a phone call
Gaia      1177a857a3caeb8fd1feae94c83298a9144c2ff5
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/d28bb1e73b91
BuildID   20140504014000
Version   28.1