Thanks for the info. It's clear now. "enable adb by hand": I don't want to deliver the device with adb enabled, because I don't want the end-user to be able to do anything with adb.
Scenario is that my client (very non-technical) does the data sync between PC application and Android device (using adb in the background), so all he needs to do is plug in the device and sync from within the Android application. In fact, he cannot even leave the application. So everything should be handled from the application, incl. enabling adb end disabling adb when the data sync is completed. This non-technical client will hand/rent out the device to other people for daily usage. I don't want those people to be mess around with adb in any way. On Aug 12, 7:03 pm, Kostya Vasilyev <kmans...@gmail.com> wrote: > "Ordinary" applications can't change Secure settings. > > The built-in settings application can change secure settings because it > has a special key that the firmware knows about. Unless you create your > own firmware, you can't give your application the same functionality. > > Now, any reason why you couldn't enable adb "by hand", before handing > over the device with the application to the customer? > > - Kostya > > 12.08.2010 5:37, Mathias Lin : > > > > > Thanks for the info. But as I understand it, the settings are read > > only: > > > "Secure system settings, containing system preferences that > > applications can read but are not allowed to write. These are for > > preferences that the user must explicitly modify through the system UI > > or specialized APIs for those values, not modified directly by > > applications." > > > .. or could you please tell me about the special key - couldn't find > > any information about where to get or register such key. With > > 'platform knows about' you mean the key needs to be registered with > > the device first outside the app? > > (Since I'm in full control of the devices and bundle the app together > > with a device for distribution, that would be doable). > > > On Aug 12, 4:49 am, Kostya Vasilyev<kmans...@gmail.com> wrote: > >> ... but that is a Secure setting and, as such, can only be manipulated by > >> applications signed with a special key (that the platform knows about). > > >> -- > >> Kostya Vasilyev --http://kmansoft.wordpress.com > > >> 12.08.2010 0:26 "QR"<qro...@gmail.com> : > > >> usb debugging is another name for the Android Debug Bridge (ADB). The > >> item you're looking for is > >> here:http://developer.android.com/reference/android/provider/Settings.Secu... > > >> On Aug 11, 5:39 am, Mathias Lin<m...@mathiaslin.com> wrote:> Is it > >> possible to enable usb debuggi... > >>> I was looking at Permission.WRITE_SETTINGS andhttp:// > >> developer.android.com/reference/android/provider/Settings.Syst... > > >>> but couldn't find any appropriate setting there. > >> -- > >> You received this message because you are su... > > -- > Kostya Vasilev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
