Our app uses GPS. We don't have <uses-feature> specified, but even tablets that don't have built in GPS can load it from the Play store. Now, admittedly, CM9 etc have an option to get GPS data from external receivers, so maybe that option is fooling the Play Store into thinking the device has GPS capability.
On Tuesday, September 11, 2012 4:55:14 AM UTC-4, falcon74 wrote: > > > > On Tuesday, September 11, 2012 11:37:22 AM UTC+5:30, RichardC wrote: >> >> Does <uses-feature> with require=false, cover your use-case? >> >> http://developer.android.com/guide/topics/manifest/uses-feature-element.html >> > > Yes, "android.hardware.location.gps" for instance. > > >> On Tuesday, September 11, 2012 6:56:40 AM UTC+1, falcon74 wrote: >>> >>> Wondering if anyone has come across an official (or unofficial) >>> statement/stand regarding Android (SDK) and Google-Play, regarding apps >>> using external sensors, e.g. bluetooth or USB based ones. >>> >>> My experience based on attempt at installing several apps, that require >>> GPS, is that Google-play refuses the apps to be installed on devices, that >>> it recognizes as not having in-built GPS. I faced the similar problem with >>> magnetic field-strength sensor apps, when device doesn't have the >>> capability. However, I see lot of practical situations where such >>> capabilities can be brought by external sensors. >>> >>> >>> -- 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
