Closed
Bug 1119724
Opened 11 years ago
Closed 11 years ago
[Flame][Gallery]The device will back to Home page after you tap power key to lock and then unlock screen in Gallery.
Categories
(Firefox OS Graveyard :: Gaia::Gallery, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
INVALID
People
(Reporter: liuke, Unassigned)
Details
Attachments
(2 files)
[1.Description]:
[Flame][v2.2][Gallery]When you shot screen in Gallery app, lock screen and then unlock screen, device will back to Homescreen view.
Found time:15:06
See attachment:1506.mp4 and logcat_1506.txt
[2.Testing Steps]:
1.Launch Gallery.
2.When device loading images, long tap power key and volume down key at same time for a screenshot.
3.Then press power key twice.
4.Unlock screen.
[3.Expected Result]:
4.The device should still in Gallery app.
[4.Actual Result]:
4.The device will back to Home page.
[5.Reproduction build]:
Gaia-Rev d4dac29613076bdba3cb8adc217deadb08a2ac20
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/70de2960aa87
Build-ID 20150108010221
Version 37.0a1
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150108.044406
FW-Date Thu Jan 8 04:44:17 EST 2015
Bootloader L1TC000118D0
[6.Reproduction Frequency]:
occasionally Recurrence,2/6
[7.TCID]
Free Test
| Reporter | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
Hi Lance, Could you also check this v2.1 and v2.0, thanks.
Flags: needinfo?(liuke)
| Reporter | ||
Comment 3•11 years ago
|
||
(In reply to Eric Chang [:ericcc] [:echang] from comment #2)
> Hi Lance, Could you also check this v2.1 and v2.0, thanks.
Hi Eric,
This bug has been verified to fail on latest Flame 2.0, 2.1 build.
Steps:
1.Launch Gallery.
2.When device loading images, long tap power key and volume down key at same time for a screenshot.
3.Then press power key twice.
4.Unlock screen.
Expected Result:
4.The device should still in Gallery app.
Actual Result:
4.The device will back to Home page.
Fail rate:2/5
Flame 2.0 version:
Gaia-Rev 2989f2b2bd12fcc0e9c017d2db766e76a55873b8
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/ffb9925dd084
Build-ID 20150125000204
Version 32.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150125.033105
FW-Date Sun Jan 25 03:31:16 EST 2015
Bootloader L1TC000118D0
Flame 2.1 version:
Gaia-Rev 54d92cc0755e5102223276ab23063b5eee74b514
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/522d6c980917
Build-ID 20150125001312
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150125.035903
FW-Date Sun Jan 25 03:59:13 EST 2015
Bootloader L1TC000118D0
Flags: needinfo?(liuke) → needinfo?(echang)
| Reporter | ||
Updated•11 years ago
|
Comment 4•11 years ago
|
||
Legacy functional issue, but reproduce rate not high, it seems to be working well in music, ni RD for comment
Flags: needinfo?(echang) → needinfo?(dflanagan)
Comment 5•11 years ago
|
||
This is not a bug. It is an intentional feature we landed to fix a blocking bug for a previous release.
When there are a lot of photos to scan, the gallery app scans them in the background, and on low-end devices this slows down the entire system. The Gallery code base was not able to pause its metdata scanning process while in the background, so on devices with less than 512mb of RAM, if we are scanning photos and we go to the background we intentionally exit so we don't slow down other apps.
See the "doNotScanInBackgroundHack()" function in gallery.js. You can remove it if you want.
I recommend resolving this as INVALID
Flags: needinfo?(dflanagan)
Comment 6•11 years ago
|
||
Thanks David.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•