| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ACTION_GET_CONTENT is to simply read/import data.ACTION_OPEN_DOCUMENT
is to have long term, persistent access to documents owned by a
document provider. When user select music as alarm ringtone from
external storage, the music file is possible to be a document provider
file. DeskClock will lose access to document provider file after reboot.
DeskClock need long term, persistent access to documents owned by
document provider. So Take persistable uri permission for document
provider.
Change-Id: I110873d4c49eed34d9cabc8bd457e12eba9ced1f
CRs-Fixed: 1046238
|
|
|
|
|
|
|
|
| |
Enter clock setting activity, change the value of "silence after", and then
add a new alarm, the alarm do not auto silence after the given time.
Change-Id: I93fbc0424ad3fb094868e886768f5e66b0fcb641
CRs-Fixed: 1052745
|
|
|
|
|
|
|
|
| |
World clock can select the same city&timezone pair multiple times,which
results in duplicate records in cities list.
Change-Id: Idf97e85061b61548a026698bf73269477c3efdc9
CRs-Fixed: 1046190
|
|
|
|
|
|
|
| |
Sets the default value for the Alarm Snooze Duration.
Change-Id: I9834028d17ab0e196076ade31d6982c25ba0a979
CRs-Fixed: 1043367
|
|
|
|
|
|
|
| |
Set Ringtone fail switching between Landscape and Portrait.
Change-Id: I94fb81c9104e84b00a7fcf3d798a3914b7736d26
CRs-Fixed: 1043304
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RTC_POWEROFF_WAKEUP is a new alarm type introduced by framework
to perform poweroff alarm. The time (RTC_WAKEUP) set to framework
is not the same as the alarm time set in deskclock. In this case
the RTC register might not be correctly set. So both RTC_WAKEUP
and RTC_POWEROFF_WAKEUP types need to be set at the same time:
RTC_WAKEUP type will handle the normal alarm process, and
RTC_POWEROFF_WAKEUP is used to set the correct alarm time to RTC
register.
Change-Id: Ic03f87018e163adf6f6e6013963a497d340fbec7
|
|
|
|
|
|
|
|
|
|
|
| |
(1) When enter the deskclock at first time, and can see + in actionBar
in short time. this is a flicker issue.
(2) Change the items in SettingsActivity and then exit, you can see flick
or blackscreen in short time.
Change-Id: Id02318cd9562367bf8b5daec4d54b3a7bb6bca21
CRs-Fixed: 1032811
|
|
|
|
|
|
|
| |
When tapping worldclock image button, clock will FC.
Change-Id: I8a2852cb8c8e3478eb604dc2585cef835e19bc2f
CRs-Fixed: 1031529
|
|
|
|
|
|
|
|
| |
Setting the flip and shake action when during alarm alerting, and in fact, no
action executed
Change-Id: I4207bdb7e14eb66559f7d0fbad0702a1725ace39
CRs-Fixed: 1022134
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) when one alarm alert ringtone has been deleted, and its ringtone
should be fallback to default ringtone
(2) when ringtone need storage runtime permission, but the permission
is denied, and should fallback too
(3) optimize the ringtone title display for such as audio ringtone type
(4) during setting ringtone and if user denied permission, fail current
settting and give user toast prompt
Change-Id: I310ad9c81657f6b1a09a1bc53098e9c204bb3bae
CRs-Fixed: 1021348
|
|
|
|
|
|
|
|
| |
click the ringtone setting in alarm tab, and select the RingTone, the item is
not selected when exist at the first time
Change-Id: Ic0a33e2f2c2cd00b4476eeaca35ffa0915b4caf4
CRs-Fixed: 1019997
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) support delay alarm feature when phone_hook state
(2) support force alarm alert when device volume is zero
(3) support missed the alarm feature when phone_hook state
(4) Ux enhance feature: support audio media in SDCard as the alarm alert feature
(5) Ux enhance feature: add default alarm alert setting item to Setting Actitiy
(6) Ux enhance feature: support manual add city&timezone pair to City DB
(7) Ux enhance feature: shake do specified action when alarm alerting
(8) Ux enhance feature: flip do specified action when alarm alerting
CRs-Fixed: 1014635
Change-Id: I8b027479025e535248dd3e575bc062cedb7c33ae
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support for add user-defined cities to the world clock
Patchset 2: Added GPS query
Patchset 3: Added GPS drawables
Call requestGpsLocation in background
Patchset 4: Added timezone resolution through Google Api
Added Marco suggestions
Rebased
Patchset 5: Remove trailing whitespaces
Patchset 6: Moved cm strings to the end of the file
Rebased
Patchset 7: Export DbCityProvider. Enforce write permission to DeskClock only
Patchset 8: Fix FC when there is no default timezone
Add content description to GPS button
Don't create a new city record of city name + city tz already exists
Patchset 9: Rebased
Patchset 10: Rebased (Moved string to cm_string)
Patchset 11: Cleanup
Patchset 12: Use localized time zone names
Patchset 13: Fix online timezone lookup
Patchset 14: CleanUp. Save dialog state
Patchset 15: Kill of async tasks when closing dialog
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
Conflicts:
AndroidManifest.xml
res/menu/cities_menu.xml
res/values/cm_strings.xml
src/com/android/deskclock/Utils.java
src/com/android/deskclock/worldclock/CitiesActivity.java
src/com/android/deskclock/worldclock/CityObj.java
CRs-Fixed: 1014635
Change-Id: I99de103ce18dd009846689f5f2018072fd0e91bb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cherry-picked and ported from:
* http://review.cyanogenmod.org/#/c/29894/
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
Conflicts:
res/xml/settings.xml
src/com/android/deskclock/SettingsActivity.java
src/com/android/deskclock/alarms/AlarmService.java
CRs-Fixed: 1014635
Change-Id: I9be82187559ccd483b8e4da068890f532e60b8f7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Customize the default auto silience value and alarm behavier in a
call.
- Ring alarm in all user profiles even in silent and meeting mode.
Conflicts:
res/values/config.xml
src/com/android/deskclock/alarms/AlarmService.java
src/com/android/deskclock/provider/AlarmInstance.java
CRs-Fixed: 1014635
Change-Id: I1b617f8f97ab6e271dcaaf854800aaae083e8b1e
|
|
|
|
|
|
|
|
|
|
|
|
| |
While the previous clean-up was necessary, it no longer meets the spec.
This feature needs to trigger the alarm immediately after the call finishes.
Conflicts:
src/com/android/deskclock/alarms/AlarmStateManager.java
CRs-Fixed: 1014635
Change-Id: I27056d12f3b65c9c01329891623c38b0bbb4b107
|
|\ |
|
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | |\ |
|
| | | | | |\ |
|
| | | | | | |\ |
|
| | | | | | | |\ |
|
| | | | | | | | |\ |
|
| | | | | | | | | |\ |
|
| | | | | | | | | | |\
| | | | | | | | | | |/
| | | | | | | | | |/| |
|
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Auto-generated-cl: translation import
Bug: 29169863
Change-Id: Icd6e1972a63c0bcebe6a058ce144b6c6d9d5b664
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Change-Id: I36f204193c291475ebbd837f5a71b6f0677f259d
Auto-generated-cl: translation import
|
|/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Auto-generated-cl: translation import
Bug: 28857042
Change-Id: I9b8353b0806efcfe0d593590c365aa99cb7de3f0
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Auto-generated-cl: translation import
Bug: 28463229
Change-Id: Ic7faf9c327ba94baa4bf686ac777be3a9cf1db65
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Change-Id: I23f14c0fe8982b4e1bed150fcf2e4ed08d799e61
Auto-generated-cl: translation import
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 27531029
Change-Id: I1abfb08f8bcef310d25840101e92a237eccccceb
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 27350753
The build system will inject the correct targetSdkVersion.
Change-Id: I4473336d02d1421c19c425899af1fd7b8b2af767
(cherry picked from commit c45787fae0a3e016c2b1cc87042266d323a9a3f6)
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* goog/ub-deskclock-dazzle_nyc: (122 commits)
Add android.support.design proguard flags
Use ACTION_LOCKED_BOOT_COMPLETED on API 24+ - DO NOT MERGE
Teach DeskClock about file-based encryption. - DO NOT MERGE
Refactoring SharedPreferences to common location. - DO NOT MERGE
Use AppCompat's imageButtonStyle attribute - DO NOT MERGE
Use SimpleItemAnimator - DO NOT MERGE
Bump version to 4.5.0 - DO NOT MERGE
Do not assume current stopwatch lap has positive duration
Avoid IndexOutOfBounds when deleting timer - DO NOT MERGE
Fix snooze event tracking
Rebuild notifications after app upgrade
Fire timers as scheduled after app upgrade
Create AlarmObserverPreL in onCreate
Handle deleted timers gracefully
Fix alarm not firing in memory-pressure situations
Promote TimerService to the foreground while expired timers exist
Match firing alarms for SEARCH_MODE == alarm.next
Fix alarm icon cut off in 1x4 digital widget on nexus 5
Import translations. DO NOT MERGE
Attempt to avoid early death of AlarmService
...
Change-Id: I422291e92ca76a901aba0d192749789916495711
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ib56c2edf4f37eaf90b442e0e2c4342046fe839c1
(cherry picked from commit 581aa2ea147f49b1fd7292ba07aa893429ac5de3)
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
am: f8e562f69d
* commit 'f8e562f69dd6547f7386956eea2edab361913cc0':
Do not assume current stopwatch lap has positive duration
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 27171498
After a device reboot the realtime clock is reset. Because of this, the
app is notified of the BOOT_COMPLETE and resets the stopwatch.
There exists about a 10 second window of opportunity before the
BOOT_COMPLETE broadcast in which the app may be opened and
the realtime clock information may be used to compute stopwatch
laptimes which would be negative. This case is now handled gracefully
rather than crashing on a sanity check.
Change-Id: I0eb4da0a9a55b5abc8d6abaa5a2e046821d39a2e
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 25860525
Change-Id: I96a502fe08ffc6ac77be25f62f6ae019c7f88280
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 25860525
When running on a device that supports FBE, all persisted data is
stored in the device-encrypted area. Also mark core components as
being encryption-aware so we can schedule and trigger alarms while
the user is still locked.
Change-Id: I7517be716468b09eed0c007600abd1937e203449
(cherry picked from commit 4a025d30d308222b78ed68897da89e2b264a5fb8)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 25860525
Change-Id: I20a012be5aadcd743a03481a72fea7f3d4750fdd
(cherry picked from commit 942b3a3956221969c77f9abc447444505eea6929)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 25896454
Change-Id: I17b82001b1e0da7b7c642f95e96e406d58a77e00
(cherry picked from commit aacfcd67c7236a766a75325017e68f19c3b2ce19)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 27203822
Change-Id: I64739aef740620c9a894f599622f679ec4fdf977
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 27203822
- Set targetSdkVersion to 24.
Change-Id: I72e3452c69b151a09d4f83d222b59ed862a0d537
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 26902786
This fix was already made downstream; no need to merge.
Change-Id: I9cf0d983963b2ab5b900b10b28ef8e013b56081a
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ibc77f169c16e4bff109c8d213e607a500765b228
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 26676584
Change-Id: If6e905328265ad626ad9cc19b0ff6f128bdfe3a4
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 26484535
Change-Id: I32e8f1c5f8620109affc25e3bb4a826856759eec
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 26591272
Prior to dazzle, timers could inhabit a state of "DELETED" (value = 5).
In dazzle and beyond there is no reason to preserve such a state, but
it is possible for timers to exist in SharedPreferences in such a state,
so it must be handled gracefully.
Change-Id: I1754ef898dfff84c0a3e807c4bd0dd1473f87aad
|