| commit | a21a311d051856e4fe9d2f43d144953535749ddf | [log] [tgz] |
|---|---|---|
| author | James Lemieux <jplemieux@google.com> | Wed Jan 20 16:30:58 2016 -0800 |
| committer | James Lemieux <jplemieux@google.com> | Wed Jan 20 16:38:21 2016 -0800 |
| tree | 926e219a1028b8add5c8327e586e3fe59823315f | |
| parent | f93d6c754b0b511f36c12997e498df8d3efe4e71 [diff] |
Fire timers as scheduled after app upgrade Bug: 26676588 Timer refactoring has removed TimerReceiver, however, timers scheduled in 4.2.1 and prior use TimerReceiver as the entry point for expiring a timer. TimerReceiver must be kept in place for at least one release cycle in order to correctly fire legacy timers at their scheduled time. Change-Id: I0e3a751fce981fc22911d869f375b0cd40dde438