We fixed this for Settings in 7ccfa0614c,
but @sonymobile.com point out that it's still broken for SetupWizard.
Change-Id: I59348200105246f3ed7c0892e5f19b901d3e95ac
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
The first fixes the bug, the second was something I noticed
while debugging. We're no longer locking setup wizard orientation
for anything screen size, and so no activities it calls needs
to do that any more, either.
bug: 5642402
Change-Id: I5911223112a19841f6b4754a70148f28a753f736
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
Note: this entailed locking datetime settings not into portrait
like everything else in the setup process, but landscape, because
the existing xlarge layout wasn't rearranging itself into a portrait
alignment very well. I can give it another try later if I can have
some help from UE.
Change-Id: Ia8ce8e8292ed768bd117beedf3d94a287e658f4b
We support sensorLandscape for a moment.
See also I45e30c652feab1d30c4f0379379f8ca4e455fa02
- Use sensorLandscape instead of default
- Modify paddings in default xmls to layout landscape stuffs
correctly
Change-Id: Ife03de69e4d1d2d898cd0e8de3cefd733aea8f19
Basically set text size to 18sp and change layouts
along with the new design.
- Add custom list item xml for Wi-Fi security field
rename existing "custom_list_item.xml" to appropriate
name so that we won't be confused with their naming.
- Use the custom xml just in SetupWizard.
Bug: 3364731
Change-Id: I014903277a03c359ea193dd0f0a37c84ade19fa1
- Use Popup instead of bare fragment.
- Expose Adapters in ZonePicker.java so that it can be used
outside the fragment.
- Fix layout
Bug: 3175603
Change-Id: I2726fde4fa1a9aea1ecb29b6aa2d23dbc54232b9
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.
