| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Send ACTION_DATE_CHANGED when user change the format of the date
Change-Id: I89ef0354ae2b0825378a6e8939341c4eccf63e17
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
| |
|
|
|
|
|
|
| |
This way secondary users' settings app can request the system server to
set the time. Alarm driver cannot be opened as a secondary user.
Bug: 7459635
Change-Id: I1ae1630dc448021d35280a297c5d9960f8e8fc2e
|
| |
|
|
|
|
| |
Bug 7148283
Change-Id: If585b16f5b6ea3046e64eb9c8355fa3c9fbeeada
|
| |
|
|
|
|
|
|
|
| |
The original code was actually correct, but code calling inDaylightTime
and getDSTSavings directly is inherently suspect, so I want to clean up
this false positive along with the real abusers.
Bug: 6901488
Change-Id: I6c89e7aa29d88b81ed2c7fd6c915e0346b90a442
|
| |
|
|
|
| |
Bug: 6881640
Change-Id: I6b0d6404b0299f9efa8fd12779799f703f1c764f
|
| |
|
|
|
|
|
|
| |
Didn't have an API for this before so people used a hacked system property (ro.carrier)
to determine if the device supported mobile data. Added new API and switching callsites.
bug:5087537
Change-Id: Ibd799559be102a9e2fd552d1a23d1afbcf8f4614
|
| |
|
|
| |
Change-Id: If24d25050b3537832c3229cd84205f3b6cef1989
|
| |
|
|
|
|
|
|
|
|
|
| |
If the timezone changed too far, the example date would be "1/1/yyyy+1"
instead of "12/31/yyyy"
Move the setting of the Calendar time to where the string is calculated
to make sure we have the most up-to-date Locale.
Bug: 4596841
Change-Id: I67a253a65b1ea03ee717945c5df819beb8515662
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adjusted the screen size test to fall back to phone version of
DateTimeSettingsSetupWizard on large screens.
I made the following changes from how the phone version works:
1. Some layout changes. (Tablet look, bigger margins.)
2. Use zone picker to select time zone.
3. Added isFirstRun boolean extra to hide the pref fields
we don't need to see from setup wizard
Furthermore, I made the following fixes to the existing phone flow
(which had probably never yet been tried on a phone):
1. Added conditionals around access to some variables that only
exist in the xlarge layout.
2. Implemented PreferenceFragment.OnPreferenceStartFragmentCallback
in DateTimeSettingsSetupWizard in order to catch the user tapping
on the timezone preference and show the time zone picker popup.
(Note: for phones in ICS, we might want to launch the zone picker
preferences style, like it would have been had this been a
PreferenceActivity. Or maybe we should just create a separate
DateTimeSettingsSetupWizardPhone activity that subclasses
PreferencesActivity and doesn't need to play this trick.)
Change-Id: Ib5774a005c9f44d730d86c13746d91eb712141cc
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 3488384
Bug: 3487976
Bug: 3488381
Removed Cell standby entry from Battery use screen.
Removed Mobile signal strength from BatteryHistory screen.
Added wifi IP address to About->Status
Remove auto-timezone checkbox in Settings->Date & time
Change-Id: I228721a3613b1aeb600026e42274337886552698
|
| |
|
|
| |
Change-Id: Ic92a3de895735fc019ca506f904d63f23c82ec8f
|
| |
|
|
|
|
| |
Bug: 3173067 - Auto timezone checkbox out of sync with dependency
Bug: 3175116 - Crash when launching Manage Accounts screen
Move "Add Account" to a menu item from a button at the bottom.
|
| |
|
|
|
|
| |
User can now enable auto-time but disable auto-timezone, especially
if we don't have NITZ time from the cell network (or wifi only)
and only have NTP time that gives us date and time.
|
| |
|
|
|
|
|
|
|
| |
Some bloadcast is thrown when Activity isn't ready.
onResume() correctly update time so we don't need to
call updateTimeAndDateDisplay() when Activity is null.
Change-Id: Iea8feaa1111bb87e66462ed0f95fde9d07f2c68d
|
| |
|
|
|
|
|
|
|
|
| |
Make the orientation "behind", as XL would require landscape.
TODO:
- Automatic Time Zone should be available.
- Layout is immature: need to have better theme and layout xml.
Change-Id: Iafe141223a227643ca774f4df5e5b7fde9520d31
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- remove old ZonePicker and rename ZoneList to ZonePicker, as
the name is really confusing (see LocalePicker)
- Make the new ZonePicker fragment.
- remove dependency toward "ZoneList" class.
-- AndroidManifest.xml does not allow the other components to
access ZoneList directly, so it would be ok to remove without
using activity-alias.
-- Noticed there is a significant code duplication between
DateTimeSettings and DateTimeSettingsActivity. I'll work on it
later.
- add DateTimeSettingsSetupWizardXL class, which is not used yet,
but will be in the near future.
-- It is not recognized by AndroidManifest.xml
Change-Id: Id26152a3d560f9e0bd84afdf3e1c5101f0e166b4
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Added a base class SettingsPreferenceFragment from which the settings activities should
be derived so that they can behave like fragments. It contains some commonly called
utility methods and dialog conversion to DialogFragment.
Some of the top-level activities can be launched directly without the left pane.
Settings.java acts as a proxy activity that contains just that settings fragment without
the left pane.
There are still a lot of second and third level activities that need to be fragmentized.
This is just the first pass to test the 2-pane layout.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the two formats that have a spelled-out month, since applications
using this setting are trying to format numeric dates.
Do not forcibly set the setting the first time you go into Date & Time --
let the setting remain null if it was null before.
Add a choice corresponding to null to the list of format options. It will
look like "Normal (12-31-2009)" in the list, and will cause the system
to use whatever numeric format the locale calls for.
For the other choices, feed them to the locale-aware formatter so they
will appear with the punctuation that the locale calls for.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
