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 -~----------~----~----~----~------~----~------~--~---
