Closed Bug 867649 Opened 11 years ago Closed 11 years ago

Switch the SMS app from using the high-priority wake lock to the CPU wake lock

Categories

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

defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.1 fixed)

RESOLVED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: justin.lebar+bug, Unassigned)

References

Details

(Whiteboard: QARegressExclude)

Attachments

(1 file)

Julien pointed out to me yesterday that if we don't hold the CPU wake lock when we receive an incoming SMS, the device might not stay awake long enough to notify the user.

This is a simple patch; I'll send a PR in a sec.
Pointer to Github pull-request
Attachment #744184 - Flags: review?(etienne)
Blocks: 865429
tef? because not notifying the user of a new SMS is bad.
blocking-b2g: --- → tef?
I would like to request a test, but since there is no activity_handler_test now I don't want to ask you the overhead of creating that file.

Would you please file a bug about writing a test for this and assigning it to me ?
Comment on attachment 744184 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9499

stealing, r=me
Attachment #744184 - Flags: review?(etienne) → review+
I wonder if that could fix the bug "sometimes sms take a very long time to be 'received'" that we saw in the feedbacks.
Thanks for not making me write a test.  :)

I merged this despite Travis failures, which seem totally unrelated.  I hope that's the right thing to do.

https://github.com/mozilla-b2g/gaia/commit/e9b649b29602e571ef96892f62fc52fb19364639

> I wonder if that could fix the bug "sometimes sms take a very long time to be 'received'" that we 
> saw in the feedbacks.

Could be; perhaps you could make those bugs (are there bugs?) depend on this one.
Depends on: 867885
Comment on attachment 744184 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9499

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): -
User impact if declined: we might not get the new SMS notification
Testing completed: yes
Risk to taking this patch (and alternatives if risky): low, this won't change any core functionality
String or UUID changes made by this patch: none
Attachment #744184 - Flags: approval-gaia-v1?(21)
tef+ so that you don't need approval. Thanks!

btw, should not we mark this as FIXED?
blocking-b2g: tef? → tef+
I guess we mark things as FIXED when they land in Gaia master?  I don't land patches there very often, so I don't know.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Uplifted e9b649b29602e571ef96892f62fc52fb19364639 to:
v1-train: 50ccc9363e6bd7f124f2febba11d1b3cd570570e
v1.0.1: 9d7408aa8320ff40aefd598a9b7aac9dc110a874
Attachment #744184 - Flags: approval-gaia-v1?(21)
(In reply to Justin Lebar [:jlebar] from comment #9)
> I guess we mark things as FIXED when they land in Gaia master?  I don't land
> patches there very often, so I don't know.

Yep, just like moz central :)
Can you please provide steps to verify this fix - as we can perform blackbox testing from the UI?
Can you please provide steps to verify this fix - as we can perform blackbox testing from the UI?
Flags: needinfo?
quite difficult to verify, sorry.
Flags: needinfo?
Whiteboard: QARegressExclude
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: