Hi Ken,
These are the settings that have been blocked as listed in the file :
[platform/frameworks/base.git] / core / java / android / provider /
Settings.java
private static final HashSet<String> MOVED_TO_SECURE;
static {
MOVED_TO_SECURE = new HashSet<String>(30);
MOVED_TO_SECURE.add(Secure.ADB_ENABLED);
MOVED_TO_SECURE.add(Secure.ANDROID_ID);
MOVED_TO_SECURE.add(Secure.BLUETOOTH_ON);
MOVED_TO_SECURE.add(Secure.DATA_ROAMING);
MOVED_TO_SECURE.add(Secure.DEVICE_PROVISIONED);
MOVED_TO_SECURE.add(Secure.HTTP_PROXY);
MOVED_TO_SECURE.add(Secure.INSTALL_NON_MARKET_APPS);
MOVED_TO_SECURE.add(Secure.LOCATION_PROVIDERS_ALLOWED);
MOVED_TO_SECURE.add(Secure.LOGGING_ID);
MOVED_TO_SECURE.add(Secure.PARENTAL_CONTROL_ENABLED);
MOVED_TO_SECURE.add(Secure.PARENTAL_CONTROL_LAST_UPDATE);
MOVED_TO_SECURE.add(Secure.PARENTAL_CONTROL_REDIRECT_URL);
MOVED_TO_SECURE.add(Secure.SETTINGS_CLASSNAME);
MOVED_TO_SECURE.add(Secure.USB_MASS_STORAGE_ENABLED);
MOVED_TO_SECURE.add(Secure.USE_GOOGLE_MAIL);
MOVED_TO_SECURE.add
(Secure.WIFI_NETWORKS_AVAILABLE_NOTIFICATION_ON);
MOVED_TO_SECURE.add
(Secure.WIFI_NETWORKS_AVAILABLE_REPEAT_DELAY);
MOVED_TO_SECURE.add(Secure.WIFI_NUM_OPEN_NETWORKS_KEPT);
MOVED_TO_SECURE.add(Secure.WIFI_ON);
MOVED_TO_SECURE.add
(Secure.WIFI_WATCHDOG_ACCEPTABLE_PACKET_LOSS_PERCENTAGE);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_AP_COUNT);
MOVED_TO_SECURE.add
(Secure.WIFI_WATCHDOG_BACKGROUND_CHECK_DELAY_MS);
MOVED_TO_SECURE.add
(Secure.WIFI_WATCHDOG_BACKGROUND_CHECK_ENABLED);
MOVED_TO_SECURE.add
(Secure.WIFI_WATCHDOG_BACKGROUND_CHECK_TIMEOUT_MS);
MOVED_TO_SECURE.add
(Secure.WIFI_WATCHDOG_INITIAL_IGNORED_PING_COUNT);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_MAX_AP_CHECKS);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_ON);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_PING_COUNT);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_PING_DELAY_MS);
MOVED_TO_SECURE.add(Secure.WIFI_WATCHDOG_PING_TIMEOUT_MS);
}
Ken Kelly - available for contract work..
On Jan 3, 9:45 pm, Kent <[email protected]> wrote:
> After looking at the "roadmap" closely, there's a lot of good stuff in
> there. But I'm concerned over this tibit listed as a bugfix:
>
> http://source.android.com/roadmap/cupcake
> "A number of settings in android.provider.Settings.System were moved
> to Android.provider.Settings.Secure. Only system software can modify
> these settings ... additionally, a new permission,
> WRITE_SECURE_SETTINGS, is required to access these settings".
>
> This "bugfix" has the potential to cripple any settings manager
> application currently listed in the AndroidMarket. This includes:
> ToggleSettings, aSettings, usefulSwitchers, toggleAir, etc. Some of
> these developers have download counts in the tens of thousands. This
> seems to be an elimination of stable (and documented) functionality -
> not really fixing bugs.
>
> Does anyone know which system parameters will no longer be settable -
> or is the entire android.provider.Settings.System class to become read-
> only? Are these capabilities reimplemented in a different public
> library that is not obvious by reviewing the roadmap?
>
> Also, will "Support [for] third party updates of system applications"
> allow installation from user selected sources (can we distribute
> system applications through the AndroidMarket or our own sites) - or
> is this a euphemism for a higher-tier of applications that public
> developers are not able to produce?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
