On a lighter note it's nice we don't have these two:
or
On Jul 16, 6:32 am, Robert Green wrote:
> Thank you guys for posting this! I dropped my first game with
> bluetooth controller support which is designed to go back to 1.5 and I
> freaked out for a minute when it didn't show up. All i
Thank you guys for posting this! I dropped my first game with
bluetooth controller support which is designed to go back to 1.5 and I
freaked out for a minute when it didn't show up. All is well now.
On Jul 15, 9:31 am, Pent wrote:
> > Of course make sure you test on the the minimum SDK you defi
> Of course make sure you test on the the minimum SDK you define - to
> check your app behavior and check you haven't used any APIs that were
> introduced in later versions.
That is an advantage of working with the matching SDK version of
course...
But anyway, looks like it's going to work, thank
Actually it is nicely explained here:
http://developer.android.com/guide/topics/manifest/uses-sdk-element.html
On Thu, Jul 15, 2010 at 10:08 PM, Samuel Lawson wrote:
> When you compile you won't be able to use any APIs introduced after
> your target SDK.
>
> It won't prevent your app from appear
When you compile you won't be able to use any APIs introduced after
your target SDK.
It won't prevent your app from appearing on earlier devices, that's
purely down to the your minimum SDK chosen.
Of course make sure you test on the the minimum SDK you define - to
check your app behavior and chec
> Why don't you just set your target sdk higher?
>
I think this may be a 'doh' moment and going slightly off topic. I've
been building the cupcake version of my app with the project target 3
because if I build it with a higher target eclipse shows a big red
cross there when going to install it on
Why don't you just set your target sdk higher?
On Jul 15, 6:38 pm, Pent wrote:
> > At any rate, the correct thing for an app developer to do is
> > explicitly state which features they care about, and you can there use
> > android:required="false" to tell Market not to filter your app based on it
Why don't you just set your target sdk higher?
On Thu, Jul 15, 2010 at 6:38 PM, Pent wrote:
>> At any rate, the correct thing for an app developer to do is
>> explicitly state which features they care about, and you can there use
>> android:required="false" to tell Market not to filter your app b
> At any rate, the correct thing for an app developer to do is
> explicitly state which features they care about, and you can there use
> android:required="false" to tell Market not to filter your app based on it.
I put this in my manifest:
Building against the cupcake or donut SDK in
Also the bluetooth documentation does not mention "features" at all -
only permissions:
http://developer.android.com/guide/topics/wireless/bluetooth.html#Permissions
Could also do with an update, thanks
On Jul 15, 3:41 am, Dianne Hackborn wrote:
> Market does not filtering based on permission.
It would help if the documented list of features included bluetooth:
http://developer.android.com/guide/topics/manifest/uses-feature-element.html
On Jul 15, 3:41 am, Dianne Hackborn wrote:
> Market does not filtering based on permission. There is no need to follow
> that line of thought (an
Thanks for the solution!
On Jul 15, 3:41 am, Dianne Hackborn wrote:
> Market does not filtering based on permission. There is no need to follow
> that line of thought (and it is no argument for wanting the feature that was
> brought up here).
>
> The aapt tool is starting to infer features based
On 07/15/2010 12:37 AM, Dianne Hackborn wrote:
We are not having optional permissions any time soon.
Oh well, at least I know now what to tell those who keep nagging me
about it.
And no, these are not the same thing, permissions are about security and
the other tags are about compatibility.
We are not having optional permissions any time soon.
And no, these are not the same thing, permissions are about security and the
other tags are about compatibility.
And hey... "5 new stars in the last 24 hours..." You've been telling
people to star this bug because you associated it with a co
On 07/14/2010 09:41 PM, Dianne Hackborn wrote:
[...] At any rate, the correct thing for an app developer to do
is explicitly state which features they care about, and you can there
use android:required="false" to tell Market not to filter your app based
on it.
Let's see, to summarize the mani
Just to (hopefully!) help others out here (I don't really post, but as
Diannes comments on messages in the past have saved me *lots* of time
- thankyou!), here is what the majority of you are probably looking
for:
If your app doesn't need Bluetooth to work, but it is a nice feature,
then you'll
Market does not filtering based on permission. There is no need to follow
that line of thought (and it is no argument for wanting the feature that was
brought up here).
The aapt tool is starting to infer features based on permissions, to prevent
old applications from being delivered on devices th
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" wrote:
> On 07/14/2010 10:54 AM, Joe wrote:
>
> > I can see why Google wouldn't want to complicate the permiss
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 co
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
Ok, I clicked the star and added my support.
On Jul 13, 12:17 pm, "Jonas Petersson" wrote:
> On 07/13/2010 09:05 PM, DonFrench wrote:
> > > [Joe's app ]
>
> > So Bluetooth is not necessary to benefit from using your app but those
> > whose phones support it can reap the additional Bluetooth bene
To original poster:
I am guessing you are already using reflection to use Android 1.5
Bluetooth APIs vs. 2.0 APIs, similar to this:
http://code.google.com/p/backport-android-bluetooth
If that's the case, seems like you don't have to rely on Market to only
make your app available to phones w
Seems like a work-around for that would be to have a base app that only
requests the base permissions, and have it on-demand install an optional
add-on that requests the additional permissions. The base app calls
into the add-on to do the additional functionality.
On 07/13/10 15:17, Jonas Peterss
On 07/13/2010 09:05 PM, DonFrench wrote:
> > [Joe's app ]
So Bluetooth is not necessary to benefit from using your app but those
whose phones support it can reap the additional Bluetooth benefits
that you so thoughtfully added, is that it?. Since your app is still
valuable even without Bluetoot
So Bluetooth is not necessary to benefit from using your app but those
whose phones support it can reap the additional Bluetooth benefits
that you so thoughtfully added, is that it?. Since your app is still
valuable even without Bluetooth functionality, people with pre-2.0
phones should not be pr
I posted on this week or so ago, guess it will affect more and more
developers with time.
Pent
--
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 thi
Actually even though pre 2.0 devices don't support bluetooth fully -
you can make your apps backward compatible. Which of course my apps
are. It's a mistake by Google to now filter them from the market for
1.5 and 1.6 devices.
The apps require the bluetooth permissions - they do not require the
bl
I guess the lack of API support for Bluetooth is the reason Google
doesn't show Bluetooth-capable apps for pre-2.0 devices? Out of
curiosity, what are you doing to get around the lack of Bluetooth
support in the APIs prior to 2.0?
On Jul 10, 5:33 am, Joe wrote:
> Hi
>
> I released updates of my
28 matches
Mail list logo
