New issue
Advanced search Search tips

Issue 788549 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Modify SimpleAlarmTimer to take any clock id instead of implicitly using CLOCK_BOOTTIME_ALARM

Project Member Reported by abhishekbh@google.com, Nov 26 2017

Issue description

The instance opens clocks of type CLOCK_BOOTTIME_ALARM and                                                               
CLOCK_REALTIME_ALARM. However, it uses only CLOCK_BOOTTIME_ALARM to set                                                  
wake up alarms. At this point, it's okay to pretend the host supports                                                    
CLOCK_REALTIME_ALARM instead of returning an error.

Modify SimpleAlarmTimer to take a custom clock in the constructor.                              
 
Status: WontFix (was: Assigned)
Tracked here b/69759087

Sign in to add a comment