It doesn't matter what minSdkVersion you specify. As of 1.6 (and every version there-after, including any devices running 2.0, 2.1, and later versions), you need to have this permission to be able to write to the SD card. You can get this permission (and thus have the warning shown to the user) either one of two ways:
1) by specifying minSdkVersion or targetSdkVersion < 4, in which case the platform treats you as an old application that didn't know it needed to request the permission and thus is given it automatically. 2) by explicitly requesting the permission, with any SDK version, so you will be explicitly granted the permission. Your significant concern over this is... strange... given that everyone running 1.6 or later probably sees this permission a lot since ANY APPLICATION WRITTEN BEFORE 1.6 IS GRANTED IT FOR COMPATIBILITY. You are no a unique and special flower in this regard. Just do the right thing for your app. If your app writes to the SD card, then take the permission, and do it. The permission is just there to show users what an application will do, and if that is what you do, then it makes sense for you to have the permission. On Sun, Jan 24, 2010 at 9:07 PM, Carlo <ca...@hyperdevbox.com> wrote: > Thank you for your feedback, I rather not based my business on guess > or bet but on fact, we got 25 emails from users about this issue on > launch day 1, i think we should listen to them. I believe we have a > quality app and soon people will know about those permission, however > in the meantine, we are going to see if we can convert to MinSdk3 and > support more customers and erase this local trouble until it is a > common and accepted fact among the users. Btw, 1.6 is not really > supported by phone makers, most of them don't provide the update and > wait to go directly to 2.0 or even 2.1 so it might not be a so > bad...move..after all. > > > On Jan 25, 1:02 pm, SizzlingSkizzorsProgrammer <cbo...@gmail.com> > wrote: > > Honestly, I hardly think average users actually look at the > > permissions... > > > > On average, people don't care too much. If they want the app, they > > will install it anyways. The best way is to build a quality app and > > build dev reliability/a dev brand, and that way people will trust you. > > > > On Jan 24, 2:11 pm, "Maps.Huge.Info (Maps API Guru)" > > > > > > > > <cor...@gmail.com> wrote: > > > I think you may be over reacting. Users are most likely not going to > > > care if you write to the SD card. I would bet that 99 out of 100 users > > > don't even read or care about what permissions you're asking for, the > > > 100th person is probably searching the skies for black helicopters > > > anyway, so it's highly unlikely you'll be able to please that person > > > regardless of what you do. > > > > > You have a choice, use the SD card or not. If you do, you'll have to > > > have permission. I don't see that as a problem. > > > > > -John Coryat > > > > > "Radar Now!" > > > > > "What Zip Code?" > > -- > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
