[android-developers] Re: Bug in minSdkVersion or what?

[noriato]

Hi,
i also have the suspicion that the carriers filter out certain apps
based on the requested permission.
I have a app that requests permission for RECORD_AUDIO, and since i
use admob i also need INTERNET and ACCESS_COARSE_LOCATION.

And with request for RECORD_AUDIO permission i can't see my app in the
"newest" list but as soon as i remove the permission it shows up.
However, I can always search for the name of the app and find it, even
if it would not show up in the "newest" list.

My explanation would be that either google or the carriers filter out
completely or partly apps that either would be suitable for voip calls
( INTERNET + RECORD_AUDIO ) or in your case just plain phone apps
(CALL_PHONE) - but could just be the regular paranoia ;)

~Peter


On 9 Sep., 04:02, Lance Nanek  wrote:
> The version of aapt you are using, from Android 2.1, appears to be too
> old to show the uses-feature entries, by the way. Example:
>
> $ platforms/android-8/tools/aapt dump badging test.apk
> package: name='com.mytest' versionCode='1' versionName='1.0'
> application: label='myTest' icon='res/drawable-mdpi/icon.png'
> launchable activity name='com.mytest.MyTest'label='myTest' icon=''
> uses-permission:'android.permission.READ_CONTACTS'
> uses-permission:'android.permission.INTERNET'
> uses-permission:'android.permission.ACCESS_NETWORK_STATE'
> uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
> uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
> uses-permission:'android.permission.READ_PHONE_STATE'
> uses-permission:'android.permission.CALL_PHONE'
> sdkVersion:'4'
> targetSdkVersion:'8'
> uses-feature:'android.hardware.location'
> uses-feature:'android.hardware.location.network'
> uses-feature:'android.hardware.telephony'
> uses-feature:'android.hardware.touchscreen'
> main
> supports-screens: 'small' 'normal' 'large'
> locales: '--_--'
> densities: '120' '160' '240'
>
> $ platforms/android-7/tools/aapt dump badging test.apk
> package: name='com.mytest' versionCode='1' versionName='1.0'
> application: label='myTest' icon='res/drawable-mdpi/icon.png'
> launchable activity name='com.mytest.MyTest'label='myTest' icon=''
> uses-permission:'android.permission.READ_CONTACTS'
> uses-permission:'android.permission.INTERNET'
> uses-permission:'android.permission.ACCESS_NETWORK_STATE'
> uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
> uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
> uses-permission:'android.permission.READ_PHONE_STATE'
> uses-permission:'android.permission.CALL_PHONE'
> sdkVersion:'4'
> targetSdkVersion:'8'
> main
> supports-screens: 'small' 'normal' 'large'
> locales: '--_--'
> densities: '120' '160' '240'
>
> They don't look particularly relevant in this case anyway, but just so
> you know in the future. I suppose maybe it could matter here if
> carriers are capable of specifying the Market shouldn't show things
> like telephony apps on devices on their network and some did so and
> some didn't?
>
> On Sep 3, 8:04 pm, Gustavo  wrote:
>
>
>
> > Thanks for the quick reply Lance,
>
> > So I read that post and seems that my app is perfectly fine.
>
> > gust...@gustavo-desktop:/opt/android/platforms/android-2.1/tools$ ./
> > aapt dump badging /home/gustavo/android_app/test_app.apk
> > package: name='com.test.android' versionCode='1' versionName='1.0'
> > application: label='Test' icon='res/drawable-mdpi/icon.png'
> > launchable activity name='com.test.android.MainActivity'label=''
> > icon=''
> > uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
> > uses-permission:'android.permission.READ_PHONE_STATE'
> > uses-permission:'android.permission.CALL_PHONE'
> > uses-permission:'android.permission.INTERNET'
> > uses-permission:'android.permission.ACCESS_NETWORK_STATE'
> > uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
> > uses-permission:'android.permission.READ_CONTACTS'
> > sdkVersion:'4'
> > main
> > other-activities
> > other-services
> > supports-screens: 'small' 'normal' 'large'
> > locales: '--_--'
> > densities: '120' '160' '240'
>
> > I don't think there's nothing wrong with it.
>
> > manifest.xml:
>
> >          > android:name="android.permission.ACCESS_COARSE_UPDATES"
> > android:required="false"/>
> >          > android:required="false"/>
> >          > android:required="true"/>
> >          > android:required="true"/>
> >          > android:name="android.permission.ACCESS_NETWORK_STATE"
> > android:required="false"/>
> >          > android:name="android.permission.ACCESS_COARSE_LOCATION"
> > android:required="false" />
> >          > android:required="false" />
>
> >          >                 android:normalScreens="true" android:smallScreens="true"
> >                 android:anyDensity="true" />
>
> >         
>
> > default.properties:
> > target=android-8
>
> > I really don't understand what's going on with just a simple
> > publishing... and this is not even the first time I'm doing this =(
>
> > Any other ideas?
>
> > - Gus
>
> > On Sep

Re: [android-developers] Re: Bug in minSdkVersion or what?

[David Linse]

same here..
shows up under "Just Testing" running Froyo on a HTC Rhodium (de)..

regards


On Wed, Sep 8, 2010 at 9:59 PM, Mark Murphy  wrote:
> On Wed, Sep 8, 2010 at 3:52 PM, Gustavo  wrote:
>> My apologies for not saying the app name, I named it "Just testing".
>
> It shows up on my Nexus One. And my Droid X. Both running 2.2.
>
> --
> Mark Murphy (a Commons Guy)
> http://commonsware.com | http://github.com/commonsguy
> http://commonsware.com/blog | http://twitter.com/commonsguy
>
> Android Training in London: http://skillsmatter.com/go/os-mobile-server
>
> --
> 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

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Lance Nanek]

The version of aapt you are using, from Android 2.1, appears to be too
old to show the uses-feature entries, by the way. Example:

$ platforms/android-8/tools/aapt dump badging test.apk
package: name='com.mytest' versionCode='1' versionName='1.0'
application: label='myTest' icon='res/drawable-mdpi/icon.png'
launchable activity name='com.mytest.MyTest'label='myTest' icon=''
uses-permission:'android.permission.READ_CONTACTS'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
uses-permission:'android.permission.READ_PHONE_STATE'
uses-permission:'android.permission.CALL_PHONE'
sdkVersion:'4'
targetSdkVersion:'8'
uses-feature:'android.hardware.location'
uses-feature:'android.hardware.location.network'
uses-feature:'android.hardware.telephony'
uses-feature:'android.hardware.touchscreen'
main
supports-screens: 'small' 'normal' 'large'
locales: '--_--'
densities: '120' '160' '240'

$ platforms/android-7/tools/aapt dump badging test.apk
package: name='com.mytest' versionCode='1' versionName='1.0'
application: label='myTest' icon='res/drawable-mdpi/icon.png'
launchable activity name='com.mytest.MyTest'label='myTest' icon=''
uses-permission:'android.permission.READ_CONTACTS'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
uses-permission:'android.permission.READ_PHONE_STATE'
uses-permission:'android.permission.CALL_PHONE'
sdkVersion:'4'
targetSdkVersion:'8'
main
supports-screens: 'small' 'normal' 'large'
locales: '--_--'
densities: '120' '160' '240'

They don't look particularly relevant in this case anyway, but just so
you know in the future. I suppose maybe it could matter here if
carriers are capable of specifying the Market shouldn't show things
like telephony apps on devices on their network and some did so and
some didn't?

On Sep 3, 8:04 pm, Gustavo  wrote:
> Thanks for the quick reply Lance,
>
> So I read that post and seems that my app is perfectly fine.
>
> gust...@gustavo-desktop:/opt/android/platforms/android-2.1/tools$ ./
> aapt dump badging /home/gustavo/android_app/test_app.apk
> package: name='com.test.android' versionCode='1' versionName='1.0'
> application: label='Test' icon='res/drawable-mdpi/icon.png'
> launchable activity name='com.test.android.MainActivity'label=''
> icon=''
> uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
> uses-permission:'android.permission.READ_PHONE_STATE'
> uses-permission:'android.permission.CALL_PHONE'
> uses-permission:'android.permission.INTERNET'
> uses-permission:'android.permission.ACCESS_NETWORK_STATE'
> uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
> uses-permission:'android.permission.READ_CONTACTS'
> sdkVersion:'4'
> main
> other-activities
> other-services
> supports-screens: 'small' 'normal' 'large'
> locales: '--_--'
> densities: '120' '160' '240'
>
> I don't think there's nothing wrong with it.
>
> manifest.xml:
>
>          android:name="android.permission.ACCESS_COARSE_UPDATES"
> android:required="false"/>
>          android:required="false"/>
>          android:required="true"/>
>          android:required="true"/>
>          android:name="android.permission.ACCESS_NETWORK_STATE"
> android:required="false"/>
>          android:name="android.permission.ACCESS_COARSE_LOCATION"
> android:required="false" />
>          android:required="false" />
>
>                          android:normalScreens="true" android:smallScreens="true"
>                 android:anyDensity="true" />
>
>         
>
> default.properties:
> target=android-8
>
> I really don't understand what's going on with just a simple
> publishing... and this is not even the first time I'm doing this =(
>
> Any other ideas?
>
> - Gus
>
> On Sep 3, 8:19 pm, Lance Nanek  wrote:
>
> > Two other things you can check are if you enabled copy protection, and
> > if any uses-feature entries are getting added for you by the build
> > tools. There's a aapt dump badging command you can run to check the
> > latter:http://android-developers.blogspot.com/2010/06/future-proofing-your-a...
>
> > On Sep 3, 4:31 pm, Gustavo  wrote:
>
> > > Hi guys,
>
> > > I've just published my app on the android market but something weird
> > > happened, this is not my first time publishing an app so I'm almost
> > > sure I'm not doing anything wrong here, so would like to know if
> > > anyone had this same issue before.
>
> > > 1st Attempt:
>
> > > Manifest.xml file
>
> > >  > > android:normalScreens="true" android:smallScreens="true"
> > > android:anyDensity="true" />
>
> > > 
>
> > > default.properties:
>
> > > # Indicates whether an apk should be generated for each density.
> > > split.density=false
> > > # Project target.
> > > target=android-4
>
> > > 2nd Att

[android-developers] Re: Bug in minSdkVersion or what?

[Lance Nanek]

"Just testing" is showing up fine here on a Nexus One, Evo 4G, Droid,
and G1. All running 2.2 except the G1, which is running 1.6.

Are you running custom ROMs on your phones instead of official
updates? I've heard some users of custom ROMs say they have paid apps
in the Market. Paid apps are only available to certain white listed
software versions, so the version of Market run on these custom ROMS
must be getting false data as to what it is running on somehow. Maybe
that false data has the Android version wrong. Just Googling around I
see the release notes on some custom ROMs saying things like
"identifies itself as either T-Mobile G1", for example. So if you are
running a custom ROM that is pretending to be an old Android 1.5
version G1 to get paid apps, maybe that would also result in not
seeing apps with certain API level restrictions, for example.

On Sep 8, 4:31 pm, Gustavo  wrote:
> Thank you very much for saying that at least I know that some people
> are still able to see that app on the market.
>
> I took that permission off but the problem persists... now I even
> tried resetting my Milestone and signed in with a different gmail
> account but still nothing...
> I have no more questions about what to do, this has gone out of my
> knowledge. =/
>
> - Gus
>
> On 8 set, 16:59, Mark Murphy  wrote:
>
> > On Wed, Sep 8, 2010 at 3:52 PM, Gustavo  wrote:
> > > My apologies for not saying the app name, I named it "Just testing".
>
> > It shows up on my Nexus One. And my Droid X. Both running 2.2.
>
> > --
> > Mark Murphy (a Commons 
> > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> > Android Training in London:http://skillsmatter.com/go/os-mobile-server

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Thank you very much for saying that at least I know that some people
are still able to see that app on the market.

I took that permission off but the problem persists... now I even
tried resetting my Milestone and signed in with a different gmail
account but still nothing...
I have no more questions about what to do, this has gone out of my
knowledge. =/

- Gus

On 8 set, 16:59, Mark Murphy  wrote:
> On Wed, Sep 8, 2010 at 3:52 PM, Gustavo  wrote:
> > My apologies for not saying the app name, I named it "Just testing".
>
> It shows up on my Nexus One. And my Droid X. Both running 2.2.
>
> --
> Mark Murphy (a Commons 
> Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> Android Training in London:http://skillsmatter.com/go/os-mobile-server

-- 
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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Mark Murphy]

On Wed, Sep 8, 2010 at 3:52 PM, Gustavo  wrote:
> My apologies for not saying the app name, I named it "Just testing".

It shows up on my Nexus One. And my Droid X. Both running 2.2.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in London: http://skillsmatter.com/go/os-mobile-server

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Mark,

My apologies for not saying the app name, I named it "Just testing".
by the way, I'll try taking that non-existent permission off my code.

Many thanks.

- Gus

On 8 set, 16:33, Mark Murphy  wrote:
> On Wed, Sep 8, 2010 at 3:21 PM, Gustavo  wrote:
> >    
> >        
> >         > android:name="android.permission.ACCESS_NETWORK_STATE" />
> >         > android:name="android.permission.ACCESS_COARSE_LOCATION" />
> >         > android:name="android.permission.ACCESS_COARSE_UPDATES" />
> >        
> >        
>
> There is no ACCESS_COARSE_UPDATES permission in Android.
>
> > as soon as I published it I went to check on
> > my three android devices and the app was only visible (and still) for
> > the Tattoo on Android Market! what is going on???
>
> Among other things, "what is going on" is that you're not telling us
> the name of the app, so we can see if we can see it on the Market.
>
> --
> Mark Murphy (a Commons 
> Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> Android Training in London:http://skillsmatter.com/go/os-mobile-server

-- 
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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Mark Murphy]

On Wed, Sep 8, 2010 at 3:21 PM, Gustavo  wrote:
>    
>        
>         android:name="android.permission.ACCESS_NETWORK_STATE" />
>         android:name="android.permission.ACCESS_COARSE_LOCATION" />
>         android:name="android.permission.ACCESS_COARSE_UPDATES" />
>        >
>        

There is no ACCESS_COARSE_UPDATES permission in Android.

> as soon as I published it I went to check on
> my three android devices and the app was only visible (and still) for
> the Tattoo on Android Market! what is going on???

Among other things, "what is going on" is that you're not telling us
the name of the app, so we can see if we can see it on the Market.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in London: http://skillsmatter.com/go/os-mobile-server

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Hi everyone, I'm back again.

This is getting kind of serious for me, I wish someone could give me
some explantion of what's going on (specially if Google people are
reading this).

I have downloaded the SDK and Eclipse for another windows machine we
have here (I was using linux on my previous attempts), so I installed
the SDK, oppened Eclipse and created a brand new android project and
only add these few lines in my manifest (seriously, that was all I
did!):











So I went to publish my application and also decided to create a new
keystore file just to make sure. everything seemed to be going well
and I was doing everything just like it was my first time creating and
publishing an android application. I mean.. another PC, new SDK, new
Eclipse, new keystore and new Android project... what could go wrong,
right? but once again... as soon as I published it I went to check on
my three android devices and the app was only visible (and still) for
the Tattoo on Android Market! what is going on??? I have two developer
accounts one personal and companys, and neither of them worked. =(

I don't know what else to try I've pretty much tried everything! if
any of you would be willing to create just a simple app like mine and
add those few lines on the manifest just to see if this is really just
happening with me I would be really appreciated... or just a
reasonable explanation why is this happening would also be great.

Thanks for the great support so far!

- Gus

Devices:
HTC Tattoo - Firmware version: 1.6 - Model HTC Tattoo A3232
Motorola Milestone (AKA Droid) - Firmware version: 2.0.1 - Model A853
HTC G1 - Firmware version: 2.01 - Model T-Mobile G1



On 4 set, 07:31, San Zhang  wrote:
> Hi Dianne Hackborn，
>
> Your mention is very helpful for me, Thanks.
>
> I have an another question: If android:minSdkVersion is "3" and
> android:targetSdkVersion is "8", how to manager it? Or, is there a priority
> between both attributes?
>
> 2010/9/4 Dianne Hackborn 
>
> > Also on that page:
>
> >  Default values for attributes
>
> > The default values for the  attributes differs,
> > depending on the value of 
> > theandroid:minSdkVersion
> >  attribute
> > in the application's manifest, as well as on the value of
> > android:targetSdkVersion, if declared:
>
> >- If android:minSdkVersion or android:targetSdkVersion is "3" (Android
> >1.5) or lower, the default value for everything except 
> > android:normalScreens
> >is false. If you are primarily targeting pre-Android 1.6 platforms but
> >also want to support other densities/screen sizes, you need to set the
> >appropriate attributes to true.
> >- If android:minSdkVersion or android:targetSdkVersion is "4" (Android
> >1.6) or higher, the default value for everything is true. If your
> >application requires Android 1.6 features, but does not support these
> >densities and/or screen sizes, you need to set the appropriate attributes
> >to false.
> >- Note that android:normalScreens always defaults to true.
>
> > But um yeah if you want to be uber-pedantic...  wait, no, not even in that
> > case.  "This gun lets me kill the bunny."  That doesn't imply to me that the
> > gun is the only way I have to kill the bunny. :)
>
> > On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis 
> > wrote:
>
> >> I take your word for this, that it really is true. But I must point
> >> out: strictly speaking that contradicts
> >>http://developer.android.com/guide/practices/screens_support.html
> >> which reads in part:
>
> >> "The platform also provides a  manifest element,
> >> whose attributes android:largeScreens, android:normalScreens, and
> >> android:smallScreens let you specify what generalized screen sizes
> >> your application supports. "
>
> >> By the rules of English grammar, this means that this manifest element
> >> ALONE lets you specify it, minSdkVersion has NO part in it.
>
> >> On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> >> > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> >> > >  >> > > android:normalScreens="true" android:smallScreens="true"
> >> > > android:anyDensity="true" />
>
> >> > > 
>
> >> > Note that these two lines are redundant.  Making the minSdkVersion 4
> >> implies
> >> > you support different screens.
>
> >> > --
> >> > 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 

Re: [android-developers] Re: Bug in minSdkVersion or what?

[San Zhang]

Hi Dianne Hackborn，

Your mention is very helpful for me, Thanks.

I have an another question: If android:minSdkVersion is "3" and
android:targetSdkVersion is "8", how to manager it? Or, is there a priority
between both attributes?

2010/9/4 Dianne Hackborn 

> Also on that page:
>
>  Default values for attributes
>
> The default values for the  attributes differs,
> depending on the value of 
> theandroid:minSdkVersion
>  attribute
> in the application's manifest, as well as on the value of
> android:targetSdkVersion, if declared:
>
>- If android:minSdkVersion or android:targetSdkVersion is "3" (Android
>1.5) or lower, the default value for everything except 
> android:normalScreens
>is false. If you are primarily targeting pre-Android 1.6 platforms but
>also want to support other densities/screen sizes, you need to set the
>appropriate attributes to true.
>- If android:minSdkVersion or android:targetSdkVersion is "4" (Android
>1.6) or higher, the default value for everything is true. If your
>application requires Android 1.6 features, but does not support these
>densities and/or screen sizes, you need to set the appropriate attributes
>to false.
>- Note that android:normalScreens always defaults to true.
>
>
> But um yeah if you want to be uber-pedantic...  wait, no, not even in that
> case.  "This gun lets me kill the bunny."  That doesn't imply to me that the
> gun is the only way I have to kill the bunny. :)
>
> On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis wrote:
>
>> I take your word for this, that it really is true. But I must point
>> out: strictly speaking that contradicts
>> http://developer.android.com/guide/practices/screens_support.html
>> which reads in part:
>>
>> "The platform also provides a  manifest element,
>> whose attributes android:largeScreens, android:normalScreens, and
>> android:smallScreens let you specify what generalized screen sizes
>> your application supports. "
>>
>> By the rules of English grammar, this means that this manifest element
>> ALONE lets you specify it, minSdkVersion has NO part in it.
>>
>> On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
>> > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
>> > > > > > android:normalScreens="true" android:smallScreens="true"
>> > > android:anyDensity="true" />
>> >
>> > > 
>> >
>> > Note that these two lines are redundant.  Making the minSdkVersion 4
>> implies
>> > you support different screens.
>> >
>> > --
>> > 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
>>
>
>
>
> --
> 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
>

-- 
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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Adal]

That's right.

On Mon, Sep 6, 2010 at 4:54 AM, Dianne Hackborn  wrote:

> the Tattoo (which I think doesn't have an auto-focus camera...  though of
> course I may be wrong).

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Indicator Veritatis]

Well, you got one thing right: you do not understand. You have been
too close to Android for too long, you simply do not understand how
the documentation is read by people who are not so close (or even by
those as close who are more careful readers). That is why you
underestimate how bad this one spot in the documentation is. For the
section I quoted, when read alone, really does read as if the issue of
those values is settled by those few lines. This is, after all, all on
the topic at that 'node' in the Javadoc, the node on .

So it is a surprise to the reader to find out that no, it is not
settled: the values are set by minSDKversion as well (in the default
case). By no means is the latter section "clearly there to expand upon
that material" as you say, since it is so far away, being a separate
and apparently unrelated node. Nor is this the only spot in the
documentation with such unexpected expansion in an even more
unexpected place. Why, the former is under  and the
latter is under . These are effectively two different
documents, since each gets its own distinct node in Javadoc. Nor is
there even a cross-reference suggesting to the reader of the one that
he needs to see the other for the 'expansion'.

Now I will admit there are bigger problems in the documentation. But I
haven't seen those get fixed in between 1.5 and 2.2 either. It seems
everyone at Google is as cavalier about it as you are. This does not
bode well for the future of Android.

On Sep 4, 5:56 pm, Dianne Hackborn  wrote:
> Okay, look at it another way: the documentation you are quoting says that
> those control the different screen sizes you support.  And let's say it
> states: "these attributes, and nothing else, determine the screen sizes you
> support."  It doesn't say anything about what the values are if you don't
> specify them.  That is covered *in the same document* only a couple
> paragraphs down (in the sections that are clearly there to expand upon that
> material) in the text I pointed to.
>
> I mean...  there are a lot of places I could point to in the documentation
> that are not so good or outright bad.  To have a problem with this
> particular part...  I don't understand.
>
> On Sat, Sep 4, 2010 at 4:11 PM, Indicator Veritatis wrote:
>
> > It is not "being uber-pedantic". And your example of guns killing
> > bunnies is irrelevant. It would have been relevant if you had followed
> > the wording of the citation a little more closely, and said,
> > "this gun lets me specify whether the bunny will live or die". But of
> > course, you did not say that, since that does not support your
> > position.
>
> > The truth is that as happens all too often, the online documentation
> > says one thing in one place, and contradicts that one thing in another
> > place.
>
> > On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> > > Also on that page:
>
> > > Default values for attributes
>
> > > The default values for the  attributes differs,
> > depending
> > > on the value of
> > > theandroid:minSdkVersion<
> >http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>
> > > attribute
> > > in the application's manifest, as well as on the value of
> > > android:targetSdkVersion, if declared:
>
> > >    - If android:minSdkVersion or android:targetSdkVersion is "3" (Android
> > >    1.5) or lower, the default value for everything except
> > android:normalScreens
> > >    is false. If you are primarily targeting pre-Android 1.6 platforms but
> > >    also want to support other densities/screen sizes, you need to set the
> > >    appropriate attributes to true.
> > >    - If android:minSdkVersion or android:targetSdkVersion is "4" (Android
> > >    1.6) or higher, the default value for everything is true. If your
> > >    application requires Android 1.6 features, but does not support these
> > >    densities and/or screen sizes, you need to set the appropriate
> > attributes
> > >    to false.
> > >    - Note that android:normalScreens always defaults to true.
>
> > > But um yeah if you want to be uber-pedantic...  wait, no, not even in
> > that
> > > case.  "This gun lets me kill the bunny."  That doesn't imply to me that
> > the
> > > gun is the only way I have to kill the bunny. :)
>
> > > On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis  > >wrote:
>
> > > > I take your word for this, that it really is true. But I must point
> > > > out: strictly speaking that contradicts
> > > >http://developer.android.com/guide/practices/screens_support.html
> > > > which reads in part:
>
> > > > "The platform also provides a  manifest element,
> > > > whose attributes android:largeScreens, android:normalScreens, and
> > > > android:smallScreens let you specify what generalized screen sizes
> > > > your application supports. "
>
> > > > By the rules of English grammar, this means that this manifest element
> > > > ALONE lets you specify it, minSdkVersion has NO part in it.
>
> > > > On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> > > > > On Fri,

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Dianne Hackborn]

CALL_PHONE won't effect the visibility on any of those devices.

Using CAMERA without specifying that auto-focus is optional will, I believe,
hide it from the Tattoo (which I think doesn't have an auto-focus camera...
 though of course I may be wrong).

And of course not supporting small screens will hide it from the Tattoo.

Also you can use "aapt dump badging " to see the exact info
Market uses to classify your app.

On Sun, Sep 5, 2010 at 5:07 PM, Gustavo  wrote:

> Hi, it's me again.
>
> So I think I've found a very serious problem here... This has nothing
> to do with supports screens or sdk versions. I have built an app just
> for testing this kind of behaviour and I realized that the problem is
> on uses permission (weird!).
>
> My tests:
>
> I published a very simple hello world app and decided just to change
> the manifest file.
>
> This was tested not just 4 times but I would say like up to 30 times
> to make sure, in every way possible... spent the whole day testing
> this since the CALL_PHONE permission is the most important feature in
> my app. I even tried with a different developer account, different
> projects, package name and most of the times had to wait for like 15 -
> 20 minutes after publishing the app to make sure it's really not
> showing on the other devices.
>
> Devices I've tested:
>
> HTC Tattoo - Firmware version: 1.6 - Model HTC Tattoo A3232
> Motorola Milestone (AKA Droid) - Firmware version: 2.0.1 - Model A853
> HTC G1 - Firmware version: 2.01 - Model T-Mobile G1
>
> 1st attempt (VISIBLE ON ANDROID MARKET FOR ALL OF MY 3 ANDROID
> DEVICES):
>
>
>
> android:name="android.permission.ACCESS_NETWORK_STATE" />
> android:name="android.permission.ACCESS_COARSE_LOCATION" />
> android:name="android.permission.ACCESS_COARSE_UPDATES" />
> /
> >
>
>
>
> 2nd attempt (VISIBLE ON ANDROID MARKET ONLY FOR HTC TATTOO):
>
>
>
>
>
> android:name="android.permission.ACCESS_NETWORK_STATE" />
> android:name="android.permission.ACCESS_COARSE_LOCATION" />
> android:name="android.permission.ACCESS_COARSE_UPDATES" />
> /
> >
>
> 3rd attempt (VISIBLE ON ANDROID MARKET ONLY FOR HTC TATTOO):
>
>
>
>
>
>
> 4th attempt with a new project (VISIBLE ON ANDROID MARKET ONLY FOR HTC
> TATTOO):
>
>
>
>
>
>
> In conclusion, I realized that there's got to be something wrong with
> the CALL_PHONE permission. does anyone have an idea why is this
> happening? is that only with me? how to deal with it? any workaround?
>
> Many thanks,
>
> - Gus
>
> On Sep 4, 10:43 pm, Gustavo  wrote:
> > Thank you very much for all your help guys.
> >
> > I'm not at work today so tomorrow I'll try taking those redundant
> > lines off my manifest file and upload the app to see if I'm finally
> > able to get my app visible for all android versions (1.6 and later,
> > because now it's only being shown to 1.6 androids).
> >
> > Thanks again for the great support!
> >
> > - Gus
> >
> > On Sep 4, 9:56 pm, Dianne Hackborn  wrote:
> >
> > > Okay, look at it another way: the documentation you are quoting says
> that
> > > those control the different screen sizes you support.  And let's say it
> > > states: "these attributes, and nothing else, determine the screen sizes
> you
> > > support."  It doesn't say anything about what the values are if you
> don't
> > > specify them.  That is covered *in the same document* only a couple
> > > paragraphs down (in the sections that are clearly there to expand upon
> that
> > > material) in the text I pointed to.
> >
> > > I mean...  there are a lot of places I could point to in the
> documentation
> > > that are not so good or outright bad.  To have a problem with this
> > > particular part...  I don't understand.
> >
> > > On Sat, Sep 4, 2010 at 4:11 PM, Indicator Veritatis  >wrote:
> >
> > > > It is not "being uber-pedantic". And your example of guns killing
> > > > bunnies is irrelevant. It would have been relevant if you had
> followed
> > > > the wording of the citation a little more closely, and said,
> > > > "this gun lets me specify whether the bunny will live or die". But of
> > > > course, you did not say that, since that does not support your
> > > > position.
> >
> > > > The truth is that as happens all too often, the online documentation
> > > > says one thing in one place, and contradicts that one thing in
> another
> > > > place.
> >
> > > > On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> > > > > Also on that page:
> >
> > > > > Default values for attributes
> >
> > > > > The default values for the  attributes differs,
> > > > depending
> > > > > on the value of
> > > > > theandroid:minSdkVersion<
> > > >
> http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>
> > > > > attribute
> > > > > in the application's manifest, as well as on the value of
> > > > > android:targetSdkVersion, if declared:
> >
> > > > >- If android:minSdkV

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Shawn Brown]

> the app name is "my
> test".

I see it via market on adp2 running Froyo (CynogenMod 6.0).


DO NOT DOWNLOAD THIS APP X6 right!

Shawn

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Thank you for the quick reply Mark.

I also tried to look for some apps that require the CALL_PHONE and
you're right, they're up and running but why is it not working with my
apps? firstly I thought it had something to do with my manifest,
source code or something... but when I built a very simple hello world
app with just the CALL_PHONE on the manifest file, it also didn't work
so I got really confused about what's going on.

I'm running out of ideas on how to make this work... maybe I'll try
building and publishing it from another computer or something. =S

I've published a simple app that contains all of uses permissions that
is required in my app. would you (or anyone who's reading this) mind
telling me if you can see it from your android? the app name is "my
test".
If any of you guys have any idea on how to make this work I would be
really grateful with your support.

Thanks again.

- Gus

On Sep 5, 9:20 pm, Mark Murphy  wrote:
> On Sun, Sep 5, 2010 at 8:07 PM, Gustavo  wrote:
> > In conclusion, I realized that there's got to be something wrong with
> > the CALL_PHONE permission. does anyone have an idea why is this
> > happening? is that only with me?
>
> Possibly. I can certainly see apps that require CALL_PHONE on the
> Market with a Nexus One running 2.2:
>
> -- Advanced Call Manager
> -- recordAcall
> -- QuickCall
> -- Big Call
> -- etc.
>
> (note: I am not recommending any of these, I am merely pointing out
> that they are visible to me on the Market and use CALL_PHONE)
>
> --
> Mark Murphy (a Commons 
> Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
>
> _The Busy Coder's Guide to Android Development_ Version 3.1 Available!

-- 
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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Mark Murphy]

On Sun, Sep 5, 2010 at 8:07 PM, Gustavo  wrote:
> In conclusion, I realized that there's got to be something wrong with
> the CALL_PHONE permission. does anyone have an idea why is this
> happening? is that only with me?

Possibly. I can certainly see apps that require CALL_PHONE on the
Market with a Nexus One running 2.2:

-- Advanced Call Manager
-- recordAcall
-- QuickCall
-- Big Call
-- etc.

(note: I am not recommending any of these, I am merely pointing out
that they are visible to me on the Market and use CALL_PHONE)

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.1 Available!

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Hi, it's me again.

So I think I've found a very serious problem here... This has nothing
to do with supports screens or sdk versions. I have built an app just
for testing this kind of behaviour and I realized that the problem is
on uses permission (weird!).

My tests:

I published a very simple hello world app and decided just to change
the manifest file.

This was tested not just 4 times but I would say like up to 30 times
to make sure, in every way possible... spent the whole day testing
this since the CALL_PHONE permission is the most important feature in
my app. I even tried with a different developer account, different
projects, package name and most of the times had to wait for like 15 -
20 minutes after publishing the app to make sure it's really not
showing on the other devices.

Devices I've tested:

HTC Tattoo - Firmware version: 1.6 - Model HTC Tattoo A3232
Motorola Milestone (AKA Droid) - Firmware version: 2.0.1 - Model A853
HTC G1 - Firmware version: 2.01 - Model T-Mobile G1

1st attempt (VISIBLE ON ANDROID MARKET FOR ALL OF MY 3 ANDROID
DEVICES):










2nd attempt (VISIBLE ON ANDROID MARKET ONLY FOR HTC TATTOO):










3rd attempt (VISIBLE ON ANDROID MARKET ONLY FOR HTC TATTOO):






4th attempt with a new project (VISIBLE ON ANDROID MARKET ONLY FOR HTC
TATTOO):






In conclusion, I realized that there's got to be something wrong with
the CALL_PHONE permission. does anyone have an idea why is this
happening? is that only with me? how to deal with it? any workaround?

Many thanks,

- Gus

On Sep 4, 10:43 pm, Gustavo  wrote:
> Thank you very much for all your help guys.
>
> I'm not at work today so tomorrow I'll try taking those redundant
> lines off my manifest file and upload the app to see if I'm finally
> able to get my app visible for all android versions (1.6 and later,
> because now it's only being shown to 1.6 androids).
>
> Thanks again for the great support!
>
> - Gus
>
> On Sep 4, 9:56 pm, Dianne Hackborn  wrote:
>
> > Okay, look at it another way: the documentation you are quoting says that
> > those control the different screen sizes you support.  And let's say it
> > states: "these attributes, and nothing else, determine the screen sizes you
> > support."  It doesn't say anything about what the values are if you don't
> > specify them.  That is covered *in the same document* only a couple
> > paragraphs down (in the sections that are clearly there to expand upon that
> > material) in the text I pointed to.
>
> > I mean...  there are a lot of places I could point to in the documentation
> > that are not so good or outright bad.  To have a problem with this
> > particular part...  I don't understand.
>
> > On Sat, Sep 4, 2010 at 4:11 PM, Indicator Veritatis 
> > wrote:
>
> > > It is not "being uber-pedantic". And your example of guns killing
> > > bunnies is irrelevant. It would have been relevant if you had followed
> > > the wording of the citation a little more closely, and said,
> > > "this gun lets me specify whether the bunny will live or die". But of
> > > course, you did not say that, since that does not support your
> > > position.
>
> > > The truth is that as happens all too often, the online documentation
> > > says one thing in one place, and contradicts that one thing in another
> > > place.
>
> > > On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> > > > Also on that page:
>
> > > > Default values for attributes
>
> > > > The default values for the  attributes differs,
> > > depending
> > > > on the value of
> > > > theandroid:minSdkVersion<
> > >http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>
> > > > attribute
> > > > in the application's manifest, as well as on the value of
> > > > android:targetSdkVersion, if declared:
>
> > > >    - If android:minSdkVersion or android:targetSdkVersion is "3" 
> > > > (Android
> > > >    1.5) or lower, the default value for everything except
> > > android:normalScreens
> > > >    is false. If you are primarily targeting pre-Android 1.6 platforms 
> > > > but
> > > >    also want to support other densities/screen sizes, you need to set 
> > > > the
> > > >    appropriate attributes to true.
> > > >    - If android:minSdkVersion or android:targetSdkVersion is "4" 
> > > > (Android
> > > >    1.6) or higher, the default value for everything is true. If your
> > > >    application requires Android 1.6 features, but does not support these
> > > >    densities and/or screen sizes, you need to set the appropriate
> > > attributes
> > > >    to false.
> > > >    - Note that android:normalScreens always defaults to true.
>
> > > > But um yeah if you want to be uber-pedantic...  wait, no, not even in
> > > that
> > > > case.  "This gun lets me kill the bunny."  That doesn't imply to me that
> > > the
> > > > gun is the only way I have to kill the bunny. :)
>
> > > > On 

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Thank you very much for all your help guys.

I'm not at work today so tomorrow I'll try taking those redundant
lines off my manifest file and upload the app to see if I'm finally
able to get my app visible for all android versions (1.6 and later,
because now it's only being shown to 1.6 androids).

Thanks again for the great support!

- Gus

On Sep 4, 9:56 pm, Dianne Hackborn  wrote:
> Okay, look at it another way: the documentation you are quoting says that
> those control the different screen sizes you support.  And let's say it
> states: "these attributes, and nothing else, determine the screen sizes you
> support."  It doesn't say anything about what the values are if you don't
> specify them.  That is covered *in the same document* only a couple
> paragraphs down (in the sections that are clearly there to expand upon that
> material) in the text I pointed to.
>
> I mean...  there are a lot of places I could point to in the documentation
> that are not so good or outright bad.  To have a problem with this
> particular part...  I don't understand.
>
> On Sat, Sep 4, 2010 at 4:11 PM, Indicator Veritatis wrote:
>
>
>
> > It is not "being uber-pedantic". And your example of guns killing
> > bunnies is irrelevant. It would have been relevant if you had followed
> > the wording of the citation a little more closely, and said,
> > "this gun lets me specify whether the bunny will live or die". But of
> > course, you did not say that, since that does not support your
> > position.
>
> > The truth is that as happens all too often, the online documentation
> > says one thing in one place, and contradicts that one thing in another
> > place.
>
> > On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> > > Also on that page:
>
> > > Default values for attributes
>
> > > The default values for the  attributes differs,
> > depending
> > > on the value of
> > > theandroid:minSdkVersion<
> >http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>
> > > attribute
> > > in the application's manifest, as well as on the value of
> > > android:targetSdkVersion, if declared:
>
> > >    - If android:minSdkVersion or android:targetSdkVersion is "3" (Android
> > >    1.5) or lower, the default value for everything except
> > android:normalScreens
> > >    is false. If you are primarily targeting pre-Android 1.6 platforms but
> > >    also want to support other densities/screen sizes, you need to set the
> > >    appropriate attributes to true.
> > >    - If android:minSdkVersion or android:targetSdkVersion is "4" (Android
> > >    1.6) or higher, the default value for everything is true. If your
> > >    application requires Android 1.6 features, but does not support these
> > >    densities and/or screen sizes, you need to set the appropriate
> > attributes
> > >    to false.
> > >    - Note that android:normalScreens always defaults to true.
>
> > > But um yeah if you want to be uber-pedantic...  wait, no, not even in
> > that
> > > case.  "This gun lets me kill the bunny."  That doesn't imply to me that
> > the
> > > gun is the only way I have to kill the bunny. :)
>
> > > On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis  > >wrote:
>
> > > > I take your word for this, that it really is true. But I must point
> > > > out: strictly speaking that contradicts
> > > >http://developer.android.com/guide/practices/screens_support.html
> > > > which reads in part:
>
> > > > "The platform also provides a  manifest element,
> > > > whose attributes android:largeScreens, android:normalScreens, and
> > > > android:smallScreens let you specify what generalized screen sizes
> > > > your application supports. "
>
> > > > By the rules of English grammar, this means that this manifest element
> > > > ALONE lets you specify it, minSdkVersion has NO part in it.
>
> > > > On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> > > > > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> > > > > >  > > > > > android:normalScreens="true" android:smallScreens="true"
> > > > > > android:anyDensity="true" />
>
> > > > > > 
>
> > > > > Note that these two lines are redundant.  Making the minSdkVersion 4
> > > > implies
> > > > > you support different screens.
>
> > > > > --
> > > > > 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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Dianne Hackborn]

Okay, look at it another way: the documentation you are quoting says that
those control the different screen sizes you support.  And let's say it
states: "these attributes, and nothing else, determine the screen sizes you
support."  It doesn't say anything about what the values are if you don't
specify them.  That is covered *in the same document* only a couple
paragraphs down (in the sections that are clearly there to expand upon that
material) in the text I pointed to.

I mean...  there are a lot of places I could point to in the documentation
that are not so good or outright bad.  To have a problem with this
particular part...  I don't understand.

On Sat, Sep 4, 2010 at 4:11 PM, Indicator Veritatis wrote:

> It is not "being uber-pedantic". And your example of guns killing
> bunnies is irrelevant. It would have been relevant if you had followed
> the wording of the citation a little more closely, and said,
> "this gun lets me specify whether the bunny will live or die". But of
> course, you did not say that, since that does not support your
> position.
>
> The truth is that as happens all too often, the online documentation
> says one thing in one place, and contradicts that one thing in another
> place.
>
> On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> > Also on that page:
> >
> > Default values for attributes
> >
> > The default values for the  attributes differs,
> depending
> > on the value of
> > theandroid:minSdkVersion<
> http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>
> > attribute
> > in the application's manifest, as well as on the value of
> > android:targetSdkVersion, if declared:
> >
> >- If android:minSdkVersion or android:targetSdkVersion is "3" (Android
> >1.5) or lower, the default value for everything except
> android:normalScreens
> >is false. If you are primarily targeting pre-Android 1.6 platforms but
> >also want to support other densities/screen sizes, you need to set the
> >appropriate attributes to true.
> >- If android:minSdkVersion or android:targetSdkVersion is "4" (Android
> >1.6) or higher, the default value for everything is true. If your
> >application requires Android 1.6 features, but does not support these
> >densities and/or screen sizes, you need to set the appropriate
> attributes
> >to false.
> >- Note that android:normalScreens always defaults to true.
> >
> > But um yeah if you want to be uber-pedantic...  wait, no, not even in
> that
> > case.  "This gun lets me kill the bunny."  That doesn't imply to me that
> the
> > gun is the only way I have to kill the bunny. :)
> >
> > On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis  >wrote:
> >
> >
> >
> > > I take your word for this, that it really is true. But I must point
> > > out: strictly speaking that contradicts
> > >http://developer.android.com/guide/practices/screens_support.html
> > > which reads in part:
> >
> > > "The platform also provides a  manifest element,
> > > whose attributes android:largeScreens, android:normalScreens, and
> > > android:smallScreens let you specify what generalized screen sizes
> > > your application supports. "
> >
> > > By the rules of English grammar, this means that this manifest element
> > > ALONE lets you specify it, minSdkVersion has NO part in it.
> >
> > > On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> > > > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> > > > >  > > > > android:normalScreens="true" android:smallScreens="true"
> > > > > android:anyDensity="true" />
> >
> > > > > 
> >
> > > > Note that these two lines are redundant.  Making the minSdkVersion 4
> > > implies
> > > > you support different screens.
> >
> > > > --
> > > > 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
> >
> > --
> > 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-de

[android-developers] Re: Bug in minSdkVersion or what?

[Indicator Veritatis]

It is not "being uber-pedantic". And your example of guns killing
bunnies is irrelevant. It would have been relevant if you had followed
the wording of the citation a little more closely, and said,
"this gun lets me specify whether the bunny will live or die". But of
course, you did not say that, since that does not support your
position.

The truth is that as happens all too often, the online documentation
says one thing in one place, and contradicts that one thing in another
place.

On Sep 4, 12:36 am, Dianne Hackborn  wrote:
> Also on that page:
>
> Default values for attributes
>
> The default values for the  attributes differs, depending
> on the value of
> theandroid:minSdkVersion
> attribute
> in the application's manifest, as well as on the value of
> android:targetSdkVersion, if declared:
>
>    - If android:minSdkVersion or android:targetSdkVersion is "3" (Android
>    1.5) or lower, the default value for everything except 
> android:normalScreens
>    is false. If you are primarily targeting pre-Android 1.6 platforms but
>    also want to support other densities/screen sizes, you need to set the
>    appropriate attributes to true.
>    - If android:minSdkVersion or android:targetSdkVersion is "4" (Android
>    1.6) or higher, the default value for everything is true. If your
>    application requires Android 1.6 features, but does not support these
>    densities and/or screen sizes, you need to set the appropriate attributes
>    to false.
>    - Note that android:normalScreens always defaults to true.
>
> But um yeah if you want to be uber-pedantic...  wait, no, not even in that
> case.  "This gun lets me kill the bunny."  That doesn't imply to me that the
> gun is the only way I have to kill the bunny. :)
>
> On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis wrote:
>
>
>
> > I take your word for this, that it really is true. But I must point
> > out: strictly speaking that contradicts
> >http://developer.android.com/guide/practices/screens_support.html
> > which reads in part:
>
> > "The platform also provides a  manifest element,
> > whose attributes android:largeScreens, android:normalScreens, and
> > android:smallScreens let you specify what generalized screen sizes
> > your application supports. "
>
> > By the rules of English grammar, this means that this manifest element
> > ALONE lets you specify it, minSdkVersion has NO part in it.
>
> > On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> > > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> > > >  > > > android:normalScreens="true" android:smallScreens="true"
> > > > android:anyDensity="true" />
>
> > > > 
>
> > > Note that these two lines are redundant.  Making the minSdkVersion 4
> > implies
> > > you support different screens.
>
> > > --
> > > 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
>
> --
> 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

Re: [android-developers] Re: Bug in minSdkVersion or what?

[Dianne Hackborn]

Also on that page:

Default values for attributes

The default values for the  attributes differs, depending
on the value of
theandroid:minSdkVersion
attribute
in the application's manifest, as well as on the value of
android:targetSdkVersion, if declared:

   - If android:minSdkVersion or android:targetSdkVersion is "3" (Android
   1.5) or lower, the default value for everything except android:normalScreens
   is false. If you are primarily targeting pre-Android 1.6 platforms but
   also want to support other densities/screen sizes, you need to set the
   appropriate attributes to true.
   - If android:minSdkVersion or android:targetSdkVersion is "4" (Android
   1.6) or higher, the default value for everything is true. If your
   application requires Android 1.6 features, but does not support these
   densities and/or screen sizes, you need to set the appropriate attributes
   to false.
   - Note that android:normalScreens always defaults to true.


But um yeah if you want to be uber-pedantic...  wait, no, not even in that
case.  "This gun lets me kill the bunny."  That doesn't imply to me that the
gun is the only way I have to kill the bunny. :)

On Fri, Sep 3, 2010 at 11:57 PM, Indicator Veritatis wrote:

> I take your word for this, that it really is true. But I must point
> out: strictly speaking that contradicts
> http://developer.android.com/guide/practices/screens_support.html
> which reads in part:
>
> "The platform also provides a  manifest element,
> whose attributes android:largeScreens, android:normalScreens, and
> android:smallScreens let you specify what generalized screen sizes
> your application supports. "
>
> By the rules of English grammar, this means that this manifest element
> ALONE lets you specify it, minSdkVersion has NO part in it.
>
> On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> > On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> > >  > > android:normalScreens="true" android:smallScreens="true"
> > > android:anyDensity="true" />
> >
> > > 
> >
> > Note that these two lines are redundant.  Making the minSdkVersion 4
> implies
> > you support different screens.
> >
> > --
> > 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
>



-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Indicator Veritatis]

I take your word for this, that it really is true. But I must point
out: strictly speaking that contradicts
http://developer.android.com/guide/practices/screens_support.html
which reads in part:

"The platform also provides a  manifest element,
whose attributes android:largeScreens, android:normalScreens, and
android:smallScreens let you specify what generalized screen sizes
your application supports. "

By the rules of English grammar, this means that this manifest element
ALONE lets you specify it, minSdkVersion has NO part in it.

On Sep 3, 5:14 pm, Dianne Hackborn  wrote:
> On Fri, Sep 3, 2010 at 1:31 PM, Gustavo  wrote:
> >  > android:normalScreens="true" android:smallScreens="true"
> > android:anyDensity="true" />
>
> > 
>
> Note that these two lines are redundant.  Making the minSdkVersion 4 implies
> you support different screens.
>
> --
> 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

[android-developers] Re: Bug in minSdkVersion or what?

[Gustavo]

Thanks for the quick reply Lance,

So I read that post and seems that my app is perfectly fine.

gust...@gustavo-desktop:/opt/android/platforms/android-2.1/tools$ ./
aapt dump badging /home/gustavo/android_app/test_app.apk
package: name='com.test.android' versionCode='1' versionName='1.0'
application: label='Test' icon='res/drawable-mdpi/icon.png'
launchable activity name='com.test.android.MainActivity'label=''
icon=''
uses-permission:'android.permission.ACCESS_COARSE_UPDATES'
uses-permission:'android.permission.READ_PHONE_STATE'
uses-permission:'android.permission.CALL_PHONE'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-permission:'android.permission.ACCESS_COARSE_LOCATION'
uses-permission:'android.permission.READ_CONTACTS'
sdkVersion:'4'
main
other-activities
other-services
supports-screens: 'small' 'normal' 'large'
locales: '--_--'
densities: '120' '160' '240'

I don't think there's nothing wrong with it.

manifest.xml:













default.properties:
target=android-8

I really don't understand what's going on with just a simple
publishing... and this is not even the first time I'm doing this =(

Any other ideas?

- Gus



On Sep 3, 8:19 pm, Lance Nanek  wrote:
> Two other things you can check are if you enabled copy protection, and
> if any uses-feature entries are getting added for you by the build
> tools. There's a aapt dump badging command you can run to check the
> latter:http://android-developers.blogspot.com/2010/06/future-proofing-your-a...
>
> On Sep 3, 4:31 pm, Gustavo  wrote:
>
> > Hi guys,
>
> > I've just published my app on the android market but something weird
> > happened, this is not my first time publishing an app so I'm almost
> > sure I'm not doing anything wrong here, so would like to know if
> > anyone had this same issue before.
>
> > 1st Attempt:
>
> > Manifest.xml file
>
> >  > android:normalScreens="true" android:smallScreens="true"
> > android:anyDensity="true" />
>
> > 
>
> > default.properties:
>
> > # Indicates whether an apk should be generated for each density.
> > split.density=false
> > # Project target.
> > target=android-4
>
> > 2nd Attempt:
>
> > Manifest.xml file
>
> >  > android:normalScreens="true" android:smallScreens="true"
> > android:anyDensity="true" />
> > 
>
> > default.properties:
>
> > # Indicates whether an apk should be generated for each density.
> > split.density=false
> > # Project target.
> > target=android-8
>
> > This is suppose to be visible for all android devices that has the
> > version 1.6 and later, right? we have 3 androids here and I can only
> > see the app in the android market with the 1.6 android phone, the
> > other ones are 2.0.1 and 2.01 and I'm not being able to see the app
> > there.
>
> > Is there anything wrong with this configurations or something is
> > really going on with apps publication lately?
>
> > Thanks you very much,
>
> > - Gus
>
>

-- 
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

[android-developers] Re: Bug in minSdkVersion or what?

[Lance Nanek]

Two other things you can check are if you enabled copy protection, and
if any uses-feature entries are getting added for you by the build
tools. There's a aapt dump badging command you can run to check the
latter:
http://android-developers.blogspot.com/2010/06/future-proofing-your-app.html

On Sep 3, 4:31 pm, Gustavo  wrote:
> Hi guys,
>
> I've just published my app on the android market but something weird
> happened, this is not my first time publishing an app so I'm almost
> sure I'm not doing anything wrong here, so would like to know if
> anyone had this same issue before.
>
> 1st Attempt:
>
> Manifest.xml file
>
>  android:normalScreens="true" android:smallScreens="true"
> android:anyDensity="true" />
>
> 
>
> default.properties:
>
> # Indicates whether an apk should be generated for each density.
> split.density=false
> # Project target.
> target=android-4
>
> 2nd Attempt:
>
> Manifest.xml file
>
>  android:normalScreens="true" android:smallScreens="true"
> android:anyDensity="true" />
> 
>
> default.properties:
>
> # Indicates whether an apk should be generated for each density.
> split.density=false
> # Project target.
> target=android-8
>
> This is suppose to be visible for all android devices that has the
> version 1.6 and later, right? we have 3 androids here and I can only
> see the app in the android market with the 1.6 android phone, the
> other ones are 2.0.1 and 2.01 and I'm not being able to see the app
> there.
>
> Is there anything wrong with this configurations or something is
> really going on with apps publication lately?
>
> Thanks you very much,
>
> - Gus

-- 
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