You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
In the code, Intent.ACTION_TIME_CHANGED results in TimeProfile.ADJUST_MANUAL (0x01) but for Intent.ACTION_TIMEZONE_CHANGED the adjust reason value is set as 0x04.
According to the current time specs (https://www.bluetooth.com/specifications/adopted-specifications), "If the time information on the server device was set / changed manually, the “Manual Time Update” bit shall be set.
Note: If the time zone or DST offset were changed manually, this bit shall also be set."
In the example scenario, the user is asked to changed the timezone. Shouldn't the ADJUST_TIMEZONE value be 0x05 instead of 0x04 (and shouldn't the same thing apply to DST)?
// Adjustment Flags
public static final byte ADJUST_NONE = 0x0;
public static final byte ADJUST_MANUAL = 0x1;
public static final byte ADJUST_EXTERNAL = 0x2;
public static final byte ADJUST_TIMEZONE = 0x5;
public static final byte ADJUST_DST = 0x9;
In the code,
Intent.ACTION_TIME_CHANGEDresults inTimeProfile.ADJUST_MANUAL(0x01) but forIntent.ACTION_TIMEZONE_CHANGEDthe adjust reason value is set as 0x04.According to the current time specs (https://www.bluetooth.com/specifications/adopted-specifications), "If the time information on the server device was set / changed manually, the “Manual Time Update” bit shall be set.
Note: If the time zone or DST offset were changed manually, this bit shall also be set."
In the example scenario, the user is asked to changed the timezone. Shouldn't the
ADJUST_TIMEZONEvalue be 0x05 instead of 0x04 (and shouldn't the same thing apply to DST)?