Closed
Bug 949853
Opened 12 years ago
Closed 11 years ago
When recording from lockscreen and then tapping home button, the video would not show in the Gallery app
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1019120
People
(Reporter: pdehaan, Assigned: gweng)
References
Details
(Whiteboard: [fxos-bug-bash-1.2])
Attachments
(1 file)
6.71 MB,
video/ogg
|
Details |
B2G 1.2.0.0-prerelease (12/12/2013 build)
Steps to reproduce:
0. I have password lock homescreen, may or may not be relevant.
1. From the lock screen, press the camera icon.
2. Take a photo of ____.
3. Take a video of ____. Instead of stopping the video recording, press the home button.
4. At the login screen, enter your password and go to the gallery app.
Actual results:
Photo was saved to gallery, video was not.
Expected results:
When hitting the "home" button, the video should be saved to the SD card instead of randomly deleted.
Updated•12 years ago
|
Component: Gaia::Video → Gaia::Camera
Updated•12 years ago
|
Whiteboard: fxos-bug-bash-1.2 → [fxos-bug-bash-1.2]
Comment 1•12 years ago
|
||
In comment 0, step 0 is very likely the key: videos are recorded with a temporary filename and then renamed when recording is stopped. I suspect this isn't happening in the STR above.
Comment 2•12 years ago
|
||
Yuck. Do we still make a private copy of the camera app into the system app to handle the lockscreen case? If so, what happens to it when you tap Home? I wonder if it gets killed right away.
The fix would have to be either to stop the system app from killing the camera right away and give it some kind of signal. Or modify gecko or the camera firmware to write the desired file even if the initiating app gets killed.
Tim: are you still handling the lockscreen? Is the camera still built in to the lockscreen in 1.2? Could we modify the system app to delay killing the camera for 10 seconds or so after hiding it to give the app time to save the recorded file?
Flags: needinfo?(timdream)
Comment 3•12 years ago
|
||
(In reply to David Flanagan [:djf] from comment #2)
> Yuck. Do we still make a private copy of the camera app into the system app
> to handle the lockscreen case? If so, what happens to it when you tap Home?
> I wonder if it gets killed right away.
Yes, unfortunately we still do that. A better solution would be launching the camera app and put the frame in a <div id="locked-windows">, handled by the same AppWindowManager code in v1.4. We could make sure only certified app is allowed to be launched in the locked window layer.
> The fix would have to be either to stop the system app from killing the
> camera right away and give it some kind of signal.
Depend on the 1.3 blocking status of this bug, we might want to take this solution for now. Triage should make a decision on that.
> Or modify gecko or the
> camera firmware to write the desired file even if the initiating app gets
> killed.
>
> Tim: are you still handling the lockscreen? Is the camera still built in to
> the lockscreen in 1.2? Could we modify the system app to delay killing the
> camera for 10 seconds or so after hiding it to give the app time to save the
> recorded file?
No, Alive and Greg is handling window manager and lock screen, respectively.
blocking-b2g: --- → 1.3?
Flags: needinfo?(timdream)
Flags: needinfo?(gweng)
Flags: needinfo?(alive)
Comment 5•12 years ago
|
||
Proposed solution based on #3:
in Lockscreen: new AppWindow with specified manifestURL(camera) + config.oop = false;
and change the containerElement. before the iframe is rendered. Or have a secureWindow based on AppWindow.
BTW, if ~10 sec is really enough we could do some dirty stuff in lockscreen for v1.3..
Flags: needinfo?(alive)
Comment 6•12 years ago
|
||
This bug reproduces on the 1.1 MOZ build. When accessing the Camera app from a passcode lockscreen, the picture is saved, but the video does not get saved.
Keywords: qawanted
QA Contact: nkhristoforov
Comment 7•12 years ago
|
||
Environmental Variables for comment 6:
Device: Buri 1.1 MOZ
BuildID: 20131213041208
Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f
Gecko: bdac595a4e46
Version: 18.0
Firmware Version: V1.2_20131115
Assignee | ||
Comment 8•12 years ago
|
||
I've asked John and tried a possible solution, but it didn't work. I'll try another way to solve this ASAP.
Flags: needinfo?(gweng)
Comment 9•12 years ago
|
||
Tim,
Lets try get this fixed in 1.4 (not blocking for 1.3 -- if people feel that we need to block on it, please comment)
thanks
hema
Updated•12 years ago
|
blocking-b2g: 1.3? → 1.4?
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → gweng
Assignee | ||
Comment 10•12 years ago
|
||
John and I can't reproduce this on Inari and Unagi, all with v1.2 branch build.
This is the video.
Assignee | ||
Comment 11•12 years ago
|
||
Can QA help us to reproduce this bug, or confirm that it's disappeared?
Keywords: qawanted
Comment 12•12 years ago
|
||
The bug still reproduces on the latest 1.2 build. The video does appear in the Gallery app after unlocking the homescreen with the passcode. The video in comment 10 shows the video in the Video app, not the Gallery app. For the latest 1.2 build, the video appears in the Video app as well.
Device: Buri 1.2 COM
BuildID: 20140102004001
Gaia: b1bc88386c781148a25091bf2eeee3ba217281d0
Gecko: 0c11156c7d9b
Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version: V1.2_20131115
Keywords: qawanted
Comment 13•12 years ago
|
||
Nikolai - I don't follow what's being claimed to still reproduce here. Can you give more details? What from this bug is still present?
Flags: needinfo?(nkhristoforov)
Comment 14•12 years ago
|
||
The recurring problem is that the video does not appear in the Gallery app. After following the STR with a passcode enabled locksreen:
1. From the lock screen, press the camera icon.
2. Take a photo of ____.
3. Take a video of ____. Instead of stopping the video recording, press the home button.
4. At the login screen, enter your password and go to the gallery app.
The Gallery app shows the picture that was taken, but does not show the video. However, the video does appear in the Video app which is what the video shows in comment 10.
Flags: needinfo?(nkhristoforov)
Assignee | ||
Comment 15•12 years ago
|
||
So the problem is NOT that the video got no recorded, but it doesn't appear in the Gallery app.
I think we should change the title... it contains "Video isnt saved" which is not correct anymore.
Assignee | ||
Updated•12 years ago
|
Summary: Video isnt saved when recording from lockscreen and then tapping home button → When recording from lockscreen and then tapping home button, the video would not show in the Gallery app
Assignee | ||
Comment 16•12 years ago
|
||
John told me that the Camera app would exit normally even press home key to leave. So I would take a look to see what's the difference between these two cameras.
Comment 17•12 years ago
|
||
That's not correct in comment 16.
There is no difference between Camera app and Secured Camera. They are identical. What we need is to check the different of handling normal window and secured camera in system app.
Assignee | ||
Comment 18•12 years ago
|
||
This bug now seems because we would create a iframe to contain our own private camera, but destroy it directly without handle the leaving logic of the camera. So the correct way would be handling the leaving jobs of the camera while we want to destroy it.
(Although the most *right* way should be eliminating this private camera forever).
Assignee | ||
Comment 19•12 years ago
|
||
It seems the Camera app has the same symptom, too. The only difference is that it would hardly happen on the app, because user would take longer time to kill it from card view due to the flow (although we still can reproduce it carefully).
So right now the only thing I can do in this bug is to let the camera in the lockscreen leaving as the Camera app does (push to background or hide it while press the home key).
Assignee | ||
Comment 20•12 years ago
|
||
(The bug I mentioned: Bug 957910)
Assignee | ||
Comment 21•12 years ago
|
||
(Don't know whether it should set the dependency or not, so if I'm wrong please just remove it).
Assignee | ||
Comment 23•11 years ago
|
||
No. As I said, this issue is shared between the ordinary Camera and LockScreen. If you leave the Camera app in a very fast speed, just like what user would do in this bug, you will get the same result. So we need a solution to solve the root cause. See Bug 957910.
Flags: needinfo?(gweng)
Comment 24•11 years ago
|
||
Hema
Is LG expecting this fix? Is this needed for the camera work in 1.4?
Flags: needinfo?(hkoka)
Comment 25•11 years ago
|
||
(In reply to Preeti Raghunath(:Preeti) from comment #24)
> Hema
>
> Is LG expecting this fix? Is this needed for the camera work in 1.4?
This is an old bug - not a regression. We don't need to block on this.
Comment 26•11 years ago
|
||
(In reply to Preeti Raghunath(:Preeti) from comment #24)
> Hema
>
> Is LG expecting this fix? Is this needed for the camera work in 1.4?
I don't think so
Flags: needinfo?(hkoka)
Comment 27•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #25)
> (In reply to Preeti Raghunath(:Preeti) from comment #24)
> > Hema
> >
> > Is LG expecting this fix? Is this needed for the camera work in 1.4?
>
> This is an old bug - not a regression. We don't need to block on this.
Right, removing it from nomination
blocking-b2g: 1.4? → ---
Comment 28•11 years ago
|
||
Closing this as a duplicate of Bug 1019120 (even though its really the other way around). A patch to fix this has recently landed to master.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•