Exactly why it's a problem when they up date Bluetooth File Transfer app and it disappears for pre android 2 devices....
This only affects updates. On Jul 14, 5:26 pm, "Jonas Petersson" <[email protected]> wrote: > On 07/14/2010 10:54 AM, Joe wrote: > > > I can see why Google wouldn't want to complicate the permissions for a > > user. I am not suggesting they let the user choose which permissions > > to allow. An obvious issue with doing that is that users could "break" > > your app by crippling the permissions, and then complain it doesn't > > work and give you a bad rating on the market. That is really a > > separate topic/argument. > > I think you misunderstood what I asked for: what I'm after is that the > DEVELOPER should have the ability to flag a particular permission as > optional. Market can use this for filtering - in your case an optional > BlueTooth permission would allow users with no bluetooth library > (theoretically 1.x) to install the application. For a user who installs > it on a device WITH bluetooth, the normal installation warning screen > would allow that option to be deselected. The application will have to > check whether it actually got the optional permission - if it doesn t it > deserves a bad rating. > > Although this is not exactly your problem at the moment it certainly is > closely related. IMHO. > > > Any way back to my issue: > > > Apps are (or were) filtered from the market based on screen size and > > android version. > > > They were not filtered based on permissions. > > I wouldn't place any bets on that one. I'm pretty sure that for instance > the Barcode Scanner program is filtered out for devices that lack auto > focus for instance. This may not exactly be permissions, but rather a > device profile (I've noted that new/prerelease phones often see a lot > less of the apps on Market), but exactly how it works may be something > that we really shouldn't know too many details of since I would expect > it to change (hopefully improve) over time. > > > It seems some confusion > > has crept in. When i say in my app is android:minSdkVersion="3" - i > > mean it :) > > > The bluetooth permissions have been around since the start, they are > > nothing new. > > > This is obviously a mistake recently introduced on the Android > > Market. > > > Anyone coding a bluetooth app should have made it backwards compatible > > (as mine was) OR have set their minSdkVersion="5" > > Well, the good old Bluetooth File Transfer app seems to work. I've not > got a 1.6 device handy, but the one installed on my Milestone has target > sdk set to 4 and it asks for BT admin plus create BT connections. > > > On Jul 14, 10:39 am, DonFrench<[email protected]> wrote: > >> Ok, I clicked the star and added my support. > > Excellent! Anyone else? > > Best / Jonas -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
