Skip to content
Snippets Groups Projects
Select Git revision
  • test
  • fifteen-qpr0-new
  • fifteen default
3 results
Search by author
  • Any Author
  • Farzin Kazemzadeh Farzin Kazemzadeh itisFarzin
1 author
  1. Nov 18, 2019
    • Jerome Gaillard's avatar
      Use Metalava to get SDK metadata for devtools · 326fce2e
      Jerome Gaillard authored 
      Metalava, not Doclava, should be used to extract the metadata used in
devtools. The files created then need to be copied into the SDK.

Bug: 142480924
Test: m sdk
Change-Id: I7eb15341fde9520d51a696a6416a63e6c19c71f9
Merged-In: I7eb15341fde9520d51a696a6416a63e6c19c71f9
      326fce2e
  3. Nov 13, 2019
  5. Nov 12, 2019
  7. Nov 11, 2019
  9. Nov 09, 2019
  11. Nov 08, 2019
    • Joshua Baxter's avatar
      docs: fix typo · 9c69b40e
      Joshua Baxter authored 
      bug: 119479852

Change-Id: I5c2c31432446ef6fccf3ac80e44a1660654375c0
Test: make ds-docs
      9c69b40e
    • Joshua Baxter's avatar
      Merge "docs: remove incorrect (default) identifiers" into qt-dev · 2c7d94c7
      Joshua Baxter authored
      2c7d94c7
    • Evan Laird's avatar
      [automerger skipped] Force FGS notifications to show for a minimum time am: 3692a6d2 -s ours · 13be3108
      Evan Laird authored 
      am: 663d3d79 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 3b8c4743 is in history

Change-Id: I74620297e68c2bfd6664ed903f912e5e25d575be
      13be3108
    • Evan Laird's avatar
      [automerger skipped] Force FGS notifications to show for a minimum time · 663d3d79
      Evan Laird authored 
      am: 3692a6d2 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 3b8c4743 is in history

Change-Id: I575817ba777d7212391d75a6163c28e75c7ccbc4
      663d3d79
    • Evan Laird's avatar
      Force FGS notifications to show for a minimum time · 3692a6d2
      Evan Laird authored 
      It's possible for a service to do a start/stop foreground and cause a
couple of things to happen:

NotificationManagerService will enqueue a EnqueueNotificationRunnable,
post a PostNotificationRunnable (for the startForeground), and then also
enqueue a CancelNotificationRunnable. There is some racy behavior here
in that the cancel runnable can get triggered in between enqueue and
post runnables. If the cancel happens first, then
NotificationListenerServices will never get the message.

This behavior is technically allowed, however for foreground services we
want to ensure that there is a minmum amount of time that notification
listeners are aware of the foreground service so that (for instance) the
FGS notification can be shown.

This CL does two things to mitigate this problem:

1. Introduce checking in the CancelNotificationRunnable such that it
will not cancel until after PostNotificationRunnable has finished
executing.

2. Introduce a NotificationLifetimeExtender method that will allow a
lifetime extender to manage the lifetime of a notification that has been
enqueued but not inflated yet.

Bug: 119041698
Test: atest NotificationManagerServiceTest
Test: atest ForegroundServiceLifetimeExtenderTest
Change-Id: I0680034ed9315aa2c05282524d48faaed066ebd0
Merged-In: I0680034ed9315aa2c05282524d48faaed066ebd0
      3692a6d2
    • TreeHugger Robot's avatar
      Merge "docs: Clarified behavior of TypedArray.getBoolean()" into qt-dev · de21a30c
      TreeHugger Robot authored
      de21a30c
  13. Nov 06, 2019