[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Jonathan S]

Problem is Android 2.2 SDK build. You can built it on 4.0 and keep minimum 
API level. Just be very careful.

On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>
> I uploaded a new APK for one of my apps on Friday. There was no change 
> to the manifest or build settings for the app, but some of my 
> customers using tablets like the Note 10 and Nexus 10 tell me that the 
> new APK is marked as incompatible in the Google Play store, whereas 
> they were happily using the previous version on those devices. 
>
> In my Android Developer Console, the APK is marked as being compatible 
> with those tablets (in fact it is marked as compatible with over 2000 
> devices, and incompatible with 0 (zero)). 
>
> So I am very puzzled what has happened, and would really appreciate 
> some help :-) 
>
> Here is the Manifest. I build with the Android 2.2 SDK. 
>
>  
> http://schemas.android.com/apk/res/android"; 
>   package="com.xxx.xxx.xxx" 
>   android:installLocation="auto" 
>   android:versionCode="76" android:versionName="5.9.2"> 
> android:name="android.permission.RECORD_AUDIO"/> 
> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
> 
>  android:label="@string/app_name" 
> android:theme="@android:style/Theme.NoTitleBar" > 
>android:label="@string/app_name"> 
>  
>  
>  android:name="android.intent.category.LAUNCHER" /> 
>  
>  
>  
>  
>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[jjbunn]

I don't think it has anything to do with the 2.2 build (what makes you 
think it does?) as I already tried a version targeting 4.0 and the result 
was the same.

My users report that there are several other apps in the Play Store that 
are now marked as incompatible for their tablets, which were compatible a 
few days ago.

So, my impression is that the problem is in the Play Store, but I'd love to 
be wrong, because then I could fix it myself!

Julian


On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>
> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep minimum 
> API level. Just be very careful.
>
> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>
>> I uploaded a new APK for one of my apps on Friday. There was no change 
>> to the manifest or build settings for the app, but some of my 
>> customers using tablets like the Note 10 and Nexus 10 tell me that the 
>> new APK is marked as incompatible in the Google Play store, whereas 
>> they were happily using the previous version on those devices. 
>>
>> In my Android Developer Console, the APK is marked as being compatible 
>> with those tablets (in fact it is marked as compatible with over 2000 
>> devices, and incompatible with 0 (zero)). 
>>
>> So I am very puzzled what has happened, and would really appreciate 
>> some help :-) 
>>
>> Here is the Manifest. I build with the Android 2.2 SDK. 
>>
>>  
>> http://schemas.android.com/apk/res/android"; 
>>   package="com.xxx.xxx.xxx" 
>>   android:installLocation="auto" 
>>   android:versionCode="76" android:versionName="5.9.2"> 
>>> android:name="android.permission.RECORD_AUDIO"/> 
>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
>> 
>> > android:label="@string/app_name" 
>> android:theme="@android:style/Theme.NoTitleBar" > 
>> >   android:label="@string/app_name"> 
>>  
>>  
>> > android:name="android.intent.category.LAUNCHER" /> 
>>  
>>  
>>  
>>  
>>
>>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Rudolf Hornig]

Probably those users set a custom DPI on their tablet? ask them. This is a 
common reason for such a case.

On Monday, 20 May 2013 21:15:43 UTC+2, jjbunn wrote:
>
> I don't think it has anything to do with the 2.2 build (what makes you 
> think it does?) as I already tried a version targeting 4.0 and the result 
> was the same.
>
> My users report that there are several other apps in the Play Store that 
> are now marked as incompatible for their tablets, which were compatible a 
> few days ago.
>
> So, my impression is that the problem is in the Play Store, but I'd love 
> to be wrong, because then I could fix it myself!
>
> Julian
>
>
> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>>
>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
>> minimum API level. Just be very careful.
>>
>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>>
>>> I uploaded a new APK for one of my apps on Friday. There was no change 
>>> to the manifest or build settings for the app, but some of my 
>>> customers using tablets like the Note 10 and Nexus 10 tell me that the 
>>> new APK is marked as incompatible in the Google Play store, whereas 
>>> they were happily using the previous version on those devices. 
>>>
>>> In my Android Developer Console, the APK is marked as being compatible 
>>> with those tablets (in fact it is marked as compatible with over 2000 
>>> devices, and incompatible with 0 (zero)). 
>>>
>>> So I am very puzzled what has happened, and would really appreciate 
>>> some help :-) 
>>>
>>> Here is the Manifest. I build with the Android 2.2 SDK. 
>>>
>>>  
>>> http://schemas.android.com/apk/res/android"; 
>>>   package="com.xxx.xxx.xxx" 
>>>   android:installLocation="auto" 
>>>   android:versionCode="76" android:versionName="5.9.2"> 
>>>>> android:name="android.permission.RECORD_AUDIO"/> 
>>>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
>>> 
>>> >> android:label="@string/app_name" 
>>> android:theme="@android:style/Theme.NoTitleBar" > 
>>> >>   android:label="@string/app_name"> 
>>>  
>>>  
>>> >> android:name="android.intent.category.LAUNCHER" /> 
>>>  
>>>  
>>>  
>>>  
>>>
>>>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Rudolf Hornig]

Oh and probably you need to provide the supports-screen element in your 
manifest and declare explicitly the tablet support:



Maybe PlayStore started to enforce this to go ahead and push the developers 
to update their apps to correctly support tablets.

On Tuesday, 21 May 2013 10:18:17 UTC+2, Rudolf Hornig wrote:
>
> Probably those users set a custom DPI on their tablet? ask them. This is a 
> common reason for such a case.
>
> On Monday, 20 May 2013 21:15:43 UTC+2, jjbunn wrote:
>>
>> I don't think it has anything to do with the 2.2 build (what makes you 
>> think it does?) as I already tried a version targeting 4.0 and the result 
>> was the same.
>>
>> My users report that there are several other apps in the Play Store that 
>> are now marked as incompatible for their tablets, which were compatible a 
>> few days ago.
>>
>> So, my impression is that the problem is in the Play Store, but I'd love 
>> to be wrong, because then I could fix it myself!
>>
>> Julian
>>
>>
>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>>>
>>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
>>> minimum API level. Just be very careful.
>>>
>>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:

 I uploaded a new APK for one of my apps on Friday. There was no change 
 to the manifest or build settings for the app, but some of my 
 customers using tablets like the Note 10 and Nexus 10 tell me that the 
 new APK is marked as incompatible in the Google Play store, whereas 
 they were happily using the previous version on those devices. 

 In my Android Developer Console, the APK is marked as being compatible 
 with those tablets (in fact it is marked as compatible with over 2000 
 devices, and incompatible with 0 (zero)). 

 So I am very puzzled what has happened, and would really appreciate 
 some help :-) 

 Here is the Manifest. I build with the Android 2.2 SDK. 

  
 http://schemas.android.com/apk/res/android"; 
   package="com.xxx.xxx.xxx" 
   android:installLocation="auto" 
   android:versionCode="76" android:versionName="5.9.2"> 
>>> android:name="android.permission.RECORD_AUDIO"/> 
>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
 
 >>> android:label="@string/app_name" 
 android:theme="@android:style/Theme.NoTitleBar" > 
 >>>   android:label="@string/app_name"> 
  
  
 >>> android:name="android.intent.category.LAUNCHER" /> 
  
  
  
  



-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[bob]

I agree that *it probably does not have to do with the 2.2 build*.

I was having the same problem and was using the 2.2 build.

However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
problem.

However, I was able to "sort of remedy" the problem by setting

minSdkVersion=15
targetSdkVersion=15

You might want to try that as an experiment.

Thanks.


On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:
>
> I don't think it has anything to do with the 2.2 build (what makes you 
> think it does?) as I already tried a version targeting 4.0 and the result 
> was the same.
>
> My users report that there are several other apps in the Play Store that 
> are now marked as incompatible for their tablets, which were compatible a 
> few days ago.
>
> So, my impression is that the problem is in the Play Store, but I'd love 
> to be wrong, because then I could fix it myself!
>
> Julian
>
>
> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>>
>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
>> minimum API level. Just be very careful.
>>
>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>>
>>> I uploaded a new APK for one of my apps on Friday. There was no change 
>>> to the manifest or build settings for the app, but some of my 
>>> customers using tablets like the Note 10 and Nexus 10 tell me that the 
>>> new APK is marked as incompatible in the Google Play store, whereas 
>>> they were happily using the previous version on those devices. 
>>>
>>> In my Android Developer Console, the APK is marked as being compatible 
>>> with those tablets (in fact it is marked as compatible with over 2000 
>>> devices, and incompatible with 0 (zero)). 
>>>
>>> So I am very puzzled what has happened, and would really appreciate 
>>> some help :-) 
>>>
>>> Here is the Manifest. I build with the Android 2.2 SDK. 
>>>
>>>  
>>> http://schemas.android.com/apk/res/android"; 
>>>   package="com.xxx.xxx.xxx" 
>>>   android:installLocation="auto" 
>>>   android:versionCode="76" android:versionName="5.9.2"> 
>>>>> android:name="android.permission.RECORD_AUDIO"/> 
>>>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
>>> 
>>> >> android:label="@string/app_name" 
>>> android:theme="@android:style/Theme.NoTitleBar" > 
>>> >>   android:label="@string/app_name"> 
>>>  
>>>  
>>> >> android:name="android.intent.category.LAUNCHER" /> 
>>>  
>>>  
>>>  
>>>  
>>>
>>>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Julian Bunn]

Thanks, Rudolf.

The tablets in question a) are marked as compatible with the APK in Dev 
Console, b) had downloaded and were running the app before the APK update, 
so were compatible then. The update changed nothing in the manifest, so 
there should be no change in which devices are compatible.

I don't think that the supports-screen element is necessary - tablets are 
supported without explicitly using that element.

My conclusion is that there is a change or problem in the Play Store.

Julian

On Tuesday, May 21, 2013 1:23:34 AM UTC-7, Rudolf Hornig wrote:
>
> Oh and probably you need to provide the supports-screen element in your 
> manifest and declare explicitly the tablet support:
>
>  android:anyDensity="true" android:largeScreens="true" 
> android:smallScreens="true" android:xlargeScreens="true">
>
> Maybe PlayStore started to enforce this to go ahead and push the 
> developers to update their apps to correctly support tablets.
>
> On Tuesday, 21 May 2013 10:18:17 UTC+2, Rudolf Hornig wrote:
>>
>> Probably those users set a custom DPI on their tablet? ask them. This is 
>> a common reason for such a case.
>>
>> On Monday, 20 May 2013 21:15:43 UTC+2, jjbunn wrote:
>>>
>>> I don't think it has anything to do with the 2.2 build (what makes you 
>>> think it does?) as I already tried a version targeting 4.0 and the result 
>>> was the same.
>>>
>>> My users report that there are several other apps in the Play Store that 
>>> are now marked as incompatible for their tablets, which were compatible a 
>>> few days ago.
>>>
>>> So, my impression is that the problem is in the Play Store, but I'd love 
>>> to be wrong, because then I could fix it myself!
>>>
>>> Julian
>>>
>>>
>>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:

 Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
 minimum API level. Just be very careful.

 On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>
> I uploaded a new APK for one of my apps on Friday. There was no change 
> to the manifest or build settings for the app, but some of my 
> customers using tablets like the Note 10 and Nexus 10 tell me that the 
> new APK is marked as incompatible in the Google Play store, whereas 
> they were happily using the previous version on those devices. 
>
> In my Android Developer Console, the APK is marked as being compatible 
> with those tablets (in fact it is marked as compatible with over 2000 
> devices, and incompatible with 0 (zero)). 
>
> So I am very puzzled what has happened, and would really appreciate 
> some help :-) 
>
> Here is the Manifest. I build with the Android 2.2 SDK. 
>
>  
> http://schemas.android.com/apk/res/android"; 
>   package="com.xxx.xxx.xxx" 
>   android:installLocation="auto" 
>   android:versionCode="76" android:versionName="5.9.2"> 
> android:name="android.permission.RECORD_AUDIO"/> 
> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
> 
>  android:label="@string/app_name" 
> android:theme="@android:style/Theme.NoTitleBar" > 
>    android:label="@string/app_name"> 
>  
>  
>  android:name="android.intent.category.LAUNCHER" /> 
>  
>  
>  
>  
>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Julian Bunn]

Hi Bob ... thanks for the input. I really don't want to set such a high 
minSdk as then I would lose many of my >10,000 customers, who are running 
older versions of the OS.

It's been a few days since this tablet problem appeared so I'm going to 
check back with those customers to see if the app availability in the Play 
Store has changed in the meantime. 



On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:
>
> I agree that *it probably does not have to do with the 2.2 build*.
>
> I was having the same problem and was using the 2.2 build.
>
> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
> problem.
>
> However, I was able to "sort of remedy" the problem by setting
>
> minSdkVersion=15
> targetSdkVersion=15
>
> You might want to try that as an experiment.
>
> Thanks.
>
>
> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:
>>
>> I don't think it has anything to do with the 2.2 build (what makes you 
>> think it does?) as I already tried a version targeting 4.0 and the result 
>> was the same.
>>
>> My users report that there are several other apps in the Play Store that 
>> are now marked as incompatible for their tablets, which were compatible a 
>> few days ago.
>>
>> So, my impression is that the problem is in the Play Store, but I'd love 
>> to be wrong, because then I could fix it myself!
>>
>> Julian
>>
>>
>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>>>
>>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
>>> minimum API level. Just be very careful.
>>>
>>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:

 I uploaded a new APK for one of my apps on Friday. There was no change 
 to the manifest or build settings for the app, but some of my 
 customers using tablets like the Note 10 and Nexus 10 tell me that the 
 new APK is marked as incompatible in the Google Play store, whereas 
 they were happily using the previous version on those devices. 

 In my Android Developer Console, the APK is marked as being compatible 
 with those tablets (in fact it is marked as compatible with over 2000 
 devices, and incompatible with 0 (zero)). 

 So I am very puzzled what has happened, and would really appreciate 
 some help :-) 

 Here is the Manifest. I build with the Android 2.2 SDK. 

  
 http://schemas.android.com/apk/res/android"; 
   package="com.xxx.xxx.xxx" 
   android:installLocation="auto" 
   android:versionCode="76" android:versionName="5.9.2"> 
>>> android:name="android.permission.RECORD_AUDIO"/> 
>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
 
 >>> android:label="@string/app_name" 
 android:theme="@android:style/Theme.NoTitleBar" > 
 >>>   android:label="@string/app_name"> 
  
  
 >>> android:name="android.intent.category.LAUNCHER" /> 
  
  
  
  



-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[Fredrik Hyttnäs-Lenngren]

I got the feeling that this is the same issue that happened to the Google 
Hangout upgrade from Google Talk, where many users stated that it was 
unavailable on tablets for them, and Google fixed that. Now I want to know 
what it was that they fixed so I can fix it for my apps as well.

// Fredrik 

On Wednesday, 22 May 2013 17:56:30 UTC+2, Julian Bunn wrote:
>
> Hi Bob ... thanks for the input. I really don't want to set such a high 
> minSdk as then I would lose many of my >10,000 customers, who are running 
> older versions of the OS.
>
> It's been a few days since this tablet problem appeared so I'm going to 
> check back with those customers to see if the app availability in the Play 
> Store has changed in the meantime. 
>
>
>
> On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:
>>
>> I agree that *it probably does not have to do with the 2.2 build*.
>>
>> I was having the same problem and was using the 2.2 build.
>>
>> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
>> problem.
>>
>> However, I was able to "sort of remedy" the problem by setting
>>
>> minSdkVersion=15
>> targetSdkVersion=15
>>
>> You might want to try that as an experiment.
>>
>> Thanks.
>>
>>
>> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:
>>>
>>> I don't think it has anything to do with the 2.2 build (what makes you 
>>> think it does?) as I already tried a version targeting 4.0 and the result 
>>> was the same.
>>>
>>> My users report that there are several other apps in the Play Store that 
>>> are now marked as incompatible for their tablets, which were compatible a 
>>> few days ago.
>>>
>>> So, my impression is that the problem is in the Play Store, but I'd love 
>>> to be wrong, because then I could fix it myself!
>>>
>>> Julian
>>>
>>>
>>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:

 Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
 minimum API level. Just be very careful.

 On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>
> I uploaded a new APK for one of my apps on Friday. There was no change 
> to the manifest or build settings for the app, but some of my 
> customers using tablets like the Note 10 and Nexus 10 tell me that the 
> new APK is marked as incompatible in the Google Play store, whereas 
> they were happily using the previous version on those devices. 
>
> In my Android Developer Console, the APK is marked as being compatible 
> with those tablets (in fact it is marked as compatible with over 2000 
> devices, and incompatible with 0 (zero)). 
>
> So I am very puzzled what has happened, and would really appreciate 
> some help :-) 
>
> Here is the Manifest. I build with the Android 2.2 SDK. 
>
>  
> http://schemas.android.com/apk/res/android"; 
>   package="com.xxx.xxx.xxx" 
>   android:installLocation="auto" 
>   android:versionCode="76" android:versionName="5.9.2"> 
> android:name="android.permission.RECORD_AUDIO"/> 
> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
> 
>  android:label="@string/app_name" 
> android:theme="@android:style/Theme.NoTitleBar" > 
>    android:label="@string/app_name"> 
>  
>  
>  android:name="android.intent.category.LAUNCHER" /> 
>  
>  
>  
>  
>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[al]

Funny, you seem to ask for help but don't want to try the suggestions 
insisting it's Googles problem and thinking they would solve it...

Looking at your manifest, I think there may be problems regarding screen 
compatibility mode. See 
http://developer.android.com/guide/practices/screen-compat-mode.html and 
http://android-developers.blogspot.de/2011/07/new-mode-for-apps-on-large-screens.html.

Now, why does the problem occur without changes to the manifest? Yes, there 
may have been changes made by Google. However, I would not wait until 
Google fixes the problem. That's not necessarily Googles strength. It may 
even be the case that Google does not think it does something wrong.

Instead, I would add a supports-screens element and set 
android:targetSdkVersion.
 
The values you should use depend on your app. I also would use a current 
sdk version to build the app.

Achim

Am Mittwoch, 22. Mai 2013 17:56:30 UTC+2 schrieb Julian Bunn:
>
> Hi Bob ... thanks for the input. I really don't want to set such a high 
> minSdk as then I would lose many of my >10,000 customers, who are running 
> older versions of the OS.
>
> It's been a few days since this tablet problem appeared so I'm going to 
> check back with those customers to see if the app availability in the Play 
> Store has changed in the meantime. 
>
>
>
> On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:
>>
>> I agree that *it probably does not have to do with the 2.2 build*.
>>
>> I was having the same problem and was using the 2.2 build.
>>
>> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
>> problem.
>>
>> However, I was able to "sort of remedy" the problem by setting
>>
>> minSdkVersion=15
>> targetSdkVersion=15
>>
>> You might want to try that as an experiment.
>>
>> Thanks.
>>
>>
>> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:
>>>
>>> I don't think it has anything to do with the 2.2 build (what makes you 
>>> think it does?) as I already tried a version targeting 4.0 and the result 
>>> was the same.
>>>
>>> My users report that there are several other apps in the Play Store that 
>>> are now marked as incompatible for their tablets, which were compatible a 
>>> few days ago.
>>>
>>> So, my impression is that the problem is in the Play Store, but I'd love 
>>> to be wrong, because then I could fix it myself!
>>>
>>> Julian
>>>
>>>
>>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:

 Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
 minimum API level. Just be very careful.

 On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>
> I uploaded a new APK for one of my apps on Friday. There was no change 
> to the manifest or build settings for the app, but some of my 
> customers using tablets like the Note 10 and Nexus 10 tell me that the 
> new APK is marked as incompatible in the Google Play store, whereas 
> they were happily using the previous version on those devices. 
>
> In my Android Developer Console, the APK is marked as being compatible 
> with those tablets (in fact it is marked as compatible with over 2000 
> devices, and incompatible with 0 (zero)). 
>
> So I am very puzzled what has happened, and would really appreciate 
> some help :-) 
>
> Here is the Manifest. I build with the Android 2.2 SDK. 
>
>  
> http://schemas.android.com/apk/res/android"; 
>   package="com.xxx.xxx.xxx" 
>   android:installLocation="auto" 
>   android:versionCode="76" android:versionName="5.9.2"> 
> android:name="android.permission.RECORD_AUDIO"/> 
> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
> 
>  android:label="@string/app_name" 
> android:theme="@android:style/Theme.NoTitleBar" > 
>    android:label="@string/app_name"> 
>  
>  
>  android:name="android.intent.category.LAUNCHER" /> 
>  
>  
>  
>  
>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_ou

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[jjbunn]

On Wednesday, May 22, 2013 10:18:29 AM UTC-7, Fredrik Hyttnäs-Lenngren 
wrote:
>
> I got the feeling that this is the same issue that happened to the Google 
> Hangout upgrade from Google Talk, where many users stated that it was 
> unavailable on tablets for them, and Google fixed that. Now I want to know 
> what it was that they fixed so I can fix it for my apps as well.
>
> // Fredrik 
>

Yes, me too ... it's a little difficult to debug because it involves 
modifying then deploying an app to Play before you can tell if it's fixed 
or not!

Julian

 

>
> On Wednesday, 22 May 2013 17:56:30 UTC+2, Julian Bunn wrote:
>>
>> Hi Bob ... thanks for the input. I really don't want to set such a high 
>> minSdk as then I would lose many of my >10,000 customers, who are running 
>> older versions of the OS.
>>
>> It's been a few days since this tablet problem appeared so I'm going to 
>> check back with those customers to see if the app availability in the Play 
>> Store has changed in the meantime. 
>>
>>
>>
>> On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:
>>>
>>> I agree that *it probably does not have to do with the 2.2 build*.
>>>
>>> I was having the same problem and was using the 2.2 build.
>>>
>>> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
>>> problem.
>>>
>>> However, I was able to "sort of remedy" the problem by setting
>>>
>>> minSdkVersion=15
>>> targetSdkVersion=15
>>>
>>> You might want to try that as an experiment.
>>>
>>> Thanks.
>>>
>>>
>>> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:

 I don't think it has anything to do with the 2.2 build (what makes you 
 think it does?) as I already tried a version targeting 4.0 and the result 
 was the same.

 My users report that there are several other apps in the Play Store 
 that are now marked as incompatible for their tablets, which were 
 compatible a few days ago.

 So, my impression is that the problem is in the Play Store, but I'd 
 love to be wrong, because then I could fix it myself!

 Julian


 On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>
> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
> minimum API level. Just be very careful.
>
> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>
>> I uploaded a new APK for one of my apps on Friday. There was no 
>> change 
>> to the manifest or build settings for the app, but some of my 
>> customers using tablets like the Note 10 and Nexus 10 tell me that 
>> the 
>> new APK is marked as incompatible in the Google Play store, whereas 
>> they were happily using the previous version on those devices. 
>>
>> In my Android Developer Console, the APK is marked as being 
>> compatible 
>> with those tablets (in fact it is marked as compatible with over 2000 
>> devices, and incompatible with 0 (zero)). 
>>
>> So I am very puzzled what has happened, and would really appreciate 
>> some help :-) 
>>
>> Here is the Manifest. I build with the Android 2.2 SDK. 
>>
>>  
>> http://schemas.android.com/apk/res/android"; 
>>   package="com.xxx.xxx.xxx" 
>>   android:installLocation="auto" 
>>   android:versionCode="76" android:versionName="5.9.2"> 
>>> android:name="android.permission.RECORD_AUDIO"/> 
>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
>> 
>> > android:label="@string/app_name" 
>> android:theme="@android:style/Theme.NoTitleBar" > 
>> >   android:label="@string/app_name"> 
>>  
>>  
>> > android:name="android.intent.category.LAUNCHER" /> 
>>  
>>  
>>  
>>  
>>
>>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[jjbunn]

On Thursday, May 23, 2013 2:52:26 AM UTC-7, al wrote:
>
> Funny, you seem to ask for help but don't want to try the suggestions 
> insisting it's Googles problem and thinking they would solve it...
>

I'm not insisting on anything, I'm just trying to find out what has 
changed. Uninformed speculative suggestions are not super helpful since 
implementing them risks screwing up things for many users.
 

>
> Looking at your manifest, I think there may be problems regarding screen 
> compatibility mode. See 
> http://developer.android.com/guide/practices/screen-compat-mode.html and 
> http://android-developers.blogspot.de/2011/07/new-mode-for-apps-on-large-screens.html
> .
>

Thanks for the links.
 

>
> Now, why does the problem occur without changes to the manifest? Yes, 
> there may have been changes made by Google. However, I would not wait until 
> Google fixes the problem. That's not necessarily Googles strength. It may 
> even be the case that Google does not think it does something wrong.
>

By definition, Google can not do anything "wrong" since it's their system - 
I'm just trying to work with it. All I need to know is what to change to 
comply with whatever is new. I'm certainly not going to wait for them to 
revert back.
 

>
> Instead, I would add a supports-screens element and set 
> android:targetSdkVersion.
>  
> The values you should use depend on your app. I also would use a current 
> sdk version to build the app.
>
> Achim
>

Thanks for the advice - I think what I may do is try your suggestion with 
one of my other less well used apps, to see if it fixes the problem for 
that app.

Julian
 

>
> Am Mittwoch, 22. Mai 2013 17:56:30 UTC+2 schrieb Julian Bunn:
>>
>> Hi Bob ... thanks for the input. I really don't want to set such a high 
>> minSdk as then I would lose many of my >10,000 customers, who are running 
>> older versions of the OS.
>>
>> It's been a few days since this tablet problem appeared so I'm going to 
>> check back with those customers to see if the app availability in the Play 
>> Store has changed in the meantime. 
>>
>>
>>
>> On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:
>>>
>>> I agree that *it probably does not have to do with the 2.2 build*.
>>>
>>> I was having the same problem and was using the 2.2 build.
>>>
>>> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
>>> problem.
>>>
>>> However, I was able to "sort of remedy" the problem by setting
>>>
>>> minSdkVersion=15
>>> targetSdkVersion=15
>>>
>>> You might want to try that as an experiment.
>>>
>>> Thanks.
>>>
>>>
>>> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:

 I don't think it has anything to do with the 2.2 build (what makes you 
 think it does?) as I already tried a version targeting 4.0 and the result 
 was the same.

 My users report that there are several other apps in the Play Store 
 that are now marked as incompatible for their tablets, which were 
 compatible a few days ago.

 So, my impression is that the problem is in the Play Store, but I'd 
 love to be wrong, because then I could fix it myself!

 Julian


 On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>
> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
> minimum API level. Just be very careful.
>
> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>
>> I uploaded a new APK for one of my apps on Friday. There was no 
>> change 
>> to the manifest or build settings for the app, but some of my 
>> customers using tablets like the Note 10 and Nexus 10 tell me that 
>> the 
>> new APK is marked as incompatible in the Google Play store, whereas 
>> they were happily using the previous version on those devices. 
>>
>> In my Android Developer Console, the APK is marked as being 
>> compatible 
>> with those tablets (in fact it is marked as compatible with over 2000 
>> devices, and incompatible with 0 (zero)). 
>>
>> So I am very puzzled what has happened, and would really appreciate 
>> some help :-) 
>>
>> Here is the Manifest. I build with the Android 2.2 SDK. 
>>
>>  
>> http://schemas.android.com/apk/res/android"; 
>>   package="com.xxx.xxx.xxx" 
>>   android:installLocation="auto" 
>>   android:versionCode="76" android:versionName="5.9.2"> 
>>> android:name="android.permission.RECORD_AUDIO"/> 
>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
>> 
>> > android:label="@string/app_name" 
>> android:theme="@android:style/Theme.NoTitleBar" > 
>> >   android:label="@string/app_name"> 
>> 

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[jtoolsdev]

For one app I have two APKs, one for 10" tablets and another for everything 
else.  To get that working properly I uploaded a draft "hello world" app 
testing two different manifest settings to see the supported devices.  Now 
they have implemented  BETA and ALPHA version APKs you can test that way 
too.  For the two APKs to work properly I had to do things just a little 
differently than described in the documentation due to higher density 
smaller tablets.  Then I had a customer with a 10" tablet with too low a 
resolution.  Turns out this tablet though it came with Play isn't even 
listed as a supported device.

On Thursday, May 23, 2013 9:07:40 AM UTC-7, jjbunn wrote:
>
>
>
> On Thursday, May 23, 2013 2:52:26 AM UTC-7, al wrote:
>>
>> Funny, you seem to ask for help but don't want to try the suggestions 
>> insisting it's Googles problem and thinking they would solve it...
>>
>
> I'm not insisting on anything, I'm just trying to find out what has 
> changed. Uninformed speculative suggestions are not super helpful since 
> implementing them risks screwing up things for many users.
>  
>
>>
>> Looking at your manifest, I think there may be problems regarding screen 
>> compatibility mode. See 
>> http://developer.android.com/guide/practices/screen-compat-mode.html and 
>> http://android-developers.blogspot.de/2011/07/new-mode-for-apps-on-large-screens.html
>> .
>>
>
> Thanks for the links.
>  
>
>>
>> Now, why does the problem occur without changes to the manifest? Yes, 
>> there may have been changes made by Google. However, I would not wait until 
>> Google fixes the problem. That's not necessarily Googles strength. It may 
>> even be the case that Google does not think it does something wrong.
>>
>
> By definition, Google can not do anything "wrong" since it's their system 
> - I'm just trying to work with it. All I need to know is what to change to 
> comply with whatever is new. I'm certainly not going to wait for them to 
> revert back.
>  
>
>>
>> Instead, I would add a supports-screens element and set 
>> android:targetSdkVersion.
>>  
>> The values you should use depend on your app. I also would use a current 
>> sdk version to build the app.
>>
>> Achim
>>
>
> Thanks for the advice - I think what I may do is try your suggestion with 
> one of my other less well used apps, to see if it fixes the problem for 
> that app.
>
> Julian
>  
>
>>
>> Am Mittwoch, 22. Mai 2013 17:56:30 UTC+2 schrieb Julian Bunn:
>>>
>>> Hi Bob ... thanks for the input. I really don't want to set such a high 
>>> minSdk as then I would lose many of my >10,000 customers, who are running 
>>> older versions of the OS.
>>>
>>> It's been a few days since this tablet problem appeared so I'm going to 
>>> check back with those customers to see if the app availability in the Play 
>>> Store has changed in the meantime. 
>>>
>>>
>>>
>>> On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote:

 I agree that *it probably does not have to do with the 2.2 build*.

 I was having the same problem and was using the 2.2 build.

 However, I switched from 2.2 to 4.2 SDK, and this did not remedy the 
 problem.

 However, I was able to "sort of remedy" the problem by setting

 minSdkVersion=15
 targetSdkVersion=15

 You might want to try that as an experiment.

 Thanks.


 On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote:
>
> I don't think it has anything to do with the 2.2 build (what makes you 
> think it does?) as I already tried a version targeting 4.0 and the result 
> was the same.
>
> My users report that there are several other apps in the Play Store 
> that are now marked as incompatible for their tablets, which were 
> compatible a few days ago.
>
> So, my impression is that the problem is in the Play Store, but I'd 
> love to be wrong, because then I could fix it myself!
>
> Julian
>
>
> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote:
>>
>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep 
>> minimum API level. Just be very careful.
>>
>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote:
>>>
>>> I uploaded a new APK for one of my apps on Friday. There was no 
>>> change 
>>> to the manifest or build settings for the app, but some of my 
>>> customers using tablets like the Note 10 and Nexus 10 tell me that 
>>> the 
>>> new APK is marked as incompatible in the Google Play store, whereas 
>>> they were happily using the previous version on those devices. 
>>>
>>> In my Android Developer Console, the APK is marked as being 
>>> compatible 
>>> with those tablets (in fact it is marked as compatible with over 
>>> 2000 
>>> devices, and incompatible with 0 (zero)). 
>>>
>>> So I am very puzzle

[android-developers] Re: Some tablets marked as Incompatible in Play Store, but not in Developer Console

[jjbunn]

I solved this by adding an explicit uses-screens section to the manifest, 
and setting minsdk to 9 (required because xlargescreens is not supported in 
8).



I still don't know what Google changed to make this necessary.

Julian
On Monday, May 20, 2013 9:50:39 AM UTC-7, jjbunn wrote:
>
> I uploaded a new APK for one of my apps on Friday. There was no change 
> to the manifest or build settings for the app, but some of my 
> customers using tablets like the Note 10 and Nexus 10 tell me that the 
> new APK is marked as incompatible in the Google Play store, whereas 
> they were happily using the previous version on those devices. 
>
> In my Android Developer Console, the APK is marked as being compatible 
> with those tablets (in fact it is marked as compatible with over 2000 
> devices, and incompatible with 0 (zero)). 
>
> So I am very puzzled what has happened, and would really appreciate 
> some help :-) 
>
> Here is the Manifest. I build with the Android 2.2 SDK. 
>
>  
> http://schemas.android.com/apk/res/android"; 
>   package="com.xxx.xxx.xxx" 
>   android:installLocation="auto" 
>   android:versionCode="76" android:versionName="5.9.2"> 
> android:name="android.permission.RECORD_AUDIO"/> 
> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> 
> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> 
> 
>  android:label="@string/app_name" 
> android:theme="@android:style/Theme.NoTitleBar" > 
>android:label="@string/app_name"> 
>  
>  
>  android:name="android.intent.category.LAUNCHER" /> 
>  
>  
>  
>  
>
>

-- 
-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.