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).
supports-screens android:smallScreens=true
android:normalScreens=true
android:largeScreens=true
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
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
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
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
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.
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
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
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
Oh and probably you need to provide the supports-screen element in your
manifest and declare explicitly the tablet support:
supports-screens android:resizeable=true android:normalScreens=true
android:anyDensity=true android:largeScreens=true
android:smallScreens=true
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
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
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
13 matches
Mail list logo
