[android-developers] Re: putInt force closes

2012-03-26 Thread dmanpearl
JP, You must use the permission request WRITE_SETTINGS, not WRITE_SETTING. uses-permission android:name=android.permission.WRITE_SETTINGS/ - David On Sunday, July 25, 2010 11:11:14 PM UTC-7, scadaguru wrote: I am trying to write the system setting using:

Re: [android-developers] Re: putInt force closes

2012-03-26 Thread Dianne Hackborn
And if you were to look at the log, you would see an error message explicitly saying the problem is that you don't have that permission. On Tue, Mar 27, 2012 at 1:44 AM, dmanpearl dmanpe...@gmail.com wrote: JP, You must use the permission request WRITE_SETTINGS, not WRITE_SETTING.

[android-developers] Re: putInt force closes

2010-07-26 Thread Maps.Huge.Info (Maps API Guru)
Is the value is null? What device does this user have? Does it even have a wifi? There could be lots of reasons, you should make your app bullet proof, or at least resistant by testing the value to make sure you have what you think before using putInt. -John Coryat -- You received this message

[android-developers] Re: putInt force closes

2010-07-26 Thread scadaguru
John, Thanks for the reply. I am trying this app on Nexus One so it has WiFi. Your question about value being null is that you are referring that getApplicationContext() or getContentResolver() returns null? I will check out the values before passing to putInt. This fails on AVD also but I can