UTC+2 schrieb bergstr:
yeah, I can see it now, too. So, to summarize:
a tablet app with only one decl like this:
supports-screens android:requiresSmallestWidthDp=600/
will NOT be visible in the on-device Play app, but it WILL be visible and
installable in the web store.
an app
as I posted earlier, the uses-permission element can be repeated, and all
will be used, as in
uses-permission android:name=android.permission.INTERNET /
uses-permission android:name=android.permission.ACCESS_WIFI_STATE /
uses-permission
that wasn't the reason. I am lost. Spent one year to develop this app, and
cant get it onto this #?='* store.
--
--
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
thanks for all sympathies so far..
Heres the package name: com.byterefinery.mediasteersman
Heres the app name: MediaSteersman UPnP
Heres all the relevant stuff from the manifest:
uses-sdk
android:minSdkVersion=14
android:targetSdkVersion=17 /
uses-feature
First thing first, you should go to the console and check your app
settings. It will also tell you what devices are being filtered and why...
thats what I did. All my devices (currently, a Nexus 7 and Nexus 10) show
up in the compatibility list. BUT the app doesn't show up when searched
Am Dienstag, 2. April 2013 19:35:35 UTC+2 schrieb RichardC:
It will install on my Vodafone HTC HTC Sensation Z710e
.. which it shouldn't. The app is really only designed for tablets, I added
the largeScreens=true because I hoped it would fix this issue.
You mean you can search for it from
użytkownik bergstr napisał:
First thing first, you should go to the console and check your app
settings. It will also tell you what devices are being filtered and why...
thats what I did. All my devices (currently, a Nexus 7 and Nexus 10)
show up in the compatibility list. BUT the app
schrieb bob:
I can see your app now.
That change seems to have worked.
Thanks.
On Tuesday, April 2, 2013 1:26:37 PM UTC-5, bergstr wrote:
just changed that and uploaded. Now the number of compatible devices has
been REDUCED from 1204 to 315, but they're all tablets, so this may be ok
Hello,
I have just released a new tablet-only app to the Play store. I can search
from a desktop browser, and use the URL to see the market entry and install
the app from my tablet devices (Nexus 7 and 10). However, when I open the
play store on one of the tablets and do a search for any of
the app cannot be found through the name, or by any other means, if you
search from within the Play app. It can be found only from the play store
in the web.
I think the reason is that I use the supports-screen qualifier with an *
android:requiresSmallestWidthDp* attribute. Somewhere down in
ok, I have changed the code such that the frequent calls into native code
(in method validateKey) don't happen any longer. They were unneeded anyway,
as the internal cleanup thread can safely assume that the keys are valid.
With this change, I can no longer reproduce this issue.
However, I am
Hello Kostya,
havent tried to reproduce yet, so I cannot say whether its always in the
same place. Will try that next. However, you will agree that even seeing it
once is enough reason for an emergency call.
I am considering all options, really. But before I delve into speculative
Hello,
I have a rather complex app that runs on tablets only. The complexity stems
from the fact that the app allows navigation in a tree to an arbitrary
depth, where each node in the tree may have a different appearance
(depending on the node type). In addition, I have 3 tabs, that allow
you should have close()d the PrintWriter, instead of the IOStream. Thats all
Am Sonntag, 27. Februar 2011 23:17:29 UTC+1 schrieb davemac:
Both of these classes have a dump() method which looks useful for
debugging. I tried to use them in a sample application, but I'm not
getting any output
closing the PrintWriter instead of the IOStream would do, too
--
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
This byzantine menu / dialog interface is typical of Eclipse's poor UI
design.
what exactly do you find byzantine about Eclipse's UI design?
Remember, it's not made for iFanboys, but for software development
experts. Thats a huge difference.
I dont think the emulator supports NFC properly.
16 matches
Mail list logo
