summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorShunta Sato <Shunta.Sato@sonymobile.com>2016-10-25 17:42:58 +0900
committerJeff Sharkey <jsharkey@android.com>2016-12-21 12:44:30 -0700
commitd18ffd8223282285ab5e6a576976c115e50bd509 (patch)
treed08c411006d1499db7464d62cdd6062728ebb8ea /tools/aapt2/java/JavaClassGenerator_test.cpp
parentf23ea2ca62e2e652004f538e55282c140c3813a4 (diff)
Avoid Calendar's unexpect change in snapToCycleDay()
Symptom: Calendar object's certain field is unexpectedly changed after using Calendar.add() method. Detail and sample: Following patch causes this issue. - Switch network cycle calculation to use Calendar. https://android.googlesource.com/platform/frameworks/base/+/f2bead5 Call of Calendar.add() method might make a smaller field value invariant. The smaller field means such a field of Calendar.HOUR_OF_DAY, Calendar.MINUTE, Calendar.SECOND and so on if Calendar.MONTH field is focused. According to above, sometimes correct Calendar value won't be acquired by original code. To avoid unexpected change, it requires initialization toward each smaller field after Calendar.add() call. Solutions: Calendar.DAY_OF_MONTH, Calendar.HOUR_OF_DAY, Calendar.MINUTE, and Calendar.SECOND fields is set to 0 after added value to Calendar.MONTH field. Bug: 32724903 Author: Shigeki Yokomichi <shigeki.x.yokomichi@sonymobile.com> Change-Id: I7af6391653be21786b662b2f8eaad10c413733c1
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions