| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Fragment.getContext is available from MNC onwards.
Using getActivity instead
Change-Id: I99ef98947879ff165895fc76facb438cd4b8b414
|
| |
|
|
|
|
|
|
|
|
|
| |
The setting will not be available on a tablet, where rotation is
always enabled. On mobiles, it will be disabled when auto-rotate
is disabled in display settings.
Also removing content provider dependency from settings, as its in the
same process as launcher.
Bug: 28704055
Change-Id: Ibe6b1e67411fb0e4b2e36446710f463e4a3d6883
|
| |
|
|
|
|
| |
> Also changing the default value of preferences to true
Change-Id: I0a80d9b6b76d7210b12c952cf8e991a3eb327e5c
|
| |
|
|
|
|
|
|
| |
> Making all twoState prefs backed by content provider
> Using the stadard intent defined in N for settings
> Using SharedPrefsListener instead of LauncherProvider
Change-Id: I8272f54aa780bc0436e3d0aa89096a4bd2a9194f
|
| |
|
|
|
|
|
|
| |
> Removing cross process preference file
> Removed broadcast listener management for settings changes
> Defining content provider method to get/set laucnehr preferences
Change-Id: Ida36eac0ab17c1d48fedc9404817a53a89b36c4f
|
| |
|
|
|
|
|
|
| |
Settings observer doesn't work if a setting is modified in another
process, hence we instead register a receiver which listens for a signal
from the settings process that the rotation preference has changed.
Change-Id: I570e3c67bb64a32347e84ca00a8ac31d9010eac3
|
|
|
This CL adds a Settings activity along with the code needed to provide
a "Allow Rotation" setting to all phones and tablets. This setting is
set to false for phones and true for tablets. On changing the setting
from unlocked to locked, the launcher (and the Settings activity)
will get locked to the orientation the user was in when he disabled
"Allow Rotation". This is consistent with how the natural rotation
feature of Android works.
Change-Id: I8a1c59d1fa0bb9262530cad96e0a9bdbab0d9344
|
