When I publish an app to the Play store then it will tell me which devices
will be able to download my App based on the features (uses-feature) that
my app requires. Would it be possible to access that API in another way so
that can sift through a list of devices that support a certain feature
Here are the facts:
- When you upload you app to the Google Play Market google currently
looks inside your ApplicationManifest.
- Your application manifest also contains all of you Intent Filters
which google could also parse.
Is there a plan in the works for google to make use of
Fair enough. That makes sense to me. I had not considered different
behaviour based on extras passed into the intent but it only makes sense.
It is good to know though that it has been considered.
Thanks for your time and the good response.
--
You received this message because you are
Here is where you should start:
http://developer.android.com/guide/basics/what-is-android.html
Follow that and it gives you everything that you need to know.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email
I think you are failing to understand (or ignoring) the standard workflow of
and Android App; you are treating it a little too much like a Desktop
application. Why do you feel like you do even need to close it forever?
--
You received this message because you are subscribed to the Google
This is sort of a Dev community FYI based on the post I made here on
reddit: http://redd.it/i0slo
Essentially when most Tegra 2 based tablets, like the Xoom or Samsung Galaxy
Tab 10.1 are put in any mode other than standard rotation then fps chokes.
The Android issue is
For the game that I am currently making if you look at it upside down or
from any other perspective it does not affect your ability to play the game.
Similar to how you can put a board game on a table and anybody from any
direction can still play it. So, for me, it actually makes perfect sense
You are right in that I would have locked them into the slow case, but I
guess I just find it odd that there is a slow case at all when it comes to
orientation. So yes, I will re-consider not locking the orientation based on
your advice. However, what would you suggest if you game should have
I also realise that in my last email I forgot to say thank you for
responding with what the actual issue was about overlays not
being rotatable. So thank you very much for taking the time to let me know
what the root cause was.
--
You received this message because you are subscribed to the
I was wondering how much of the HTML5 spec a Honeycomb Tablet supports. So
could somebody with 3.0 or 3.1 please go to this page and tell me what
results you get? http://html5test.com/index.html
I hereby swear that this is not a spam link. I really want to know what
HTML5 features I can use.
Actually I just found this from browser scope (
http://www.browserscope.org/results?category=summaryv=3):
Android 0.5 7/100 7/10 1
Android 0.6 5/100 5/10 2
Android 1.0 63/100 8/17 99.3% 10/16 93/100 80 37
Android 1.1 25/100 3/8 10/14 72/100 15
Android 1.5 60/100 5/17 97.8% 10/16 93/100 79 127
This just happened to me too. Really frustrating... My code:
http://pastebin.com/FRXQB9tY
--
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
Why do you feel that you have to request to join this group? If you have
questions ask them. Personally I prefer asking all of my Android questions
on Stack Overflow and leave this for discussions.
--
You received this message because you are subscribed to the Google
Groups Android Developers
For the record I think you would be better off with the Simple XML
Library:
http://massaioli.homelinux.com/wordpress/2011/04/21/simple-xml-in-android-1-5-and-up/
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
I know it has been a while but in case you wanted a JAXB replacement in
Android you should use the Simple
library:
http://massaioli.homelinux.com/wordpress/2011/04/21/simple-xml-in-android-1-5-and-up/
--
You received this message because you are subscribed to the Google
Groups Android
It all depends on how you actually write your programs that you will get
better performance. However, in general, if you game really needs to eek out
speed then going the OpenGL route, done well, should result in better
performance than the Canvas method. Though I have not actually tested it
Annoying that they would make a blog post about statistics and not even let
us know the nuances of how they are gathered. If a google android dev reads
this then please spend some time to let us know how every statistic that we
get is calculated. (Infact every statistic should have a More Info
Actually I made that comment a little flippantly; 10% still translates to a
whole bunch of users when you are talking about an OS like Android. I have
changed my mind and I will suffer a little bit of that
Backwards Compatibility pain in order to cater for every user.
--
You received this
Well, this really is not the right place for this I do not think but I will
help you out by pointing you to this article on general game improvement by
improving your game mechanics:
http://www.gamasutra.com/view/feature/5901/evaluating_game_mechanics_for_depth.php?print=1
--
You received
Use reflection or check the build version to determine if you can use newer
APIs.
If I simply update the application with a new min SDK version, will
1.5 and 1.6 users be prompted to uninstall? Or will they just not see
the update?
I assume they will not see the update. There's no
Thanks for the response. That makes sense, in that case I was considering
releasing my app so that it supported version 3 of the SDK because that
would be easy to do, however I really want the android.accounts package so
maybe I will just make the min SDK level be 5 and ignore those on old
Well that is annoying, cannot even trust the statistics pages. Now I
actually have to debate what to do. Not as fun as I was planning. Ah well, I
guess that is the price that people pay for newer and better versions of
Android. Though Google really needs to get ontop of those statistics then; I
Thankyou, these are really useful statistics though it is really confusing
that they tell different stories. However it does say that everything below
v7 of the SDK is only about ten percent of the market which I think means
that app developers will ditch those platforms in the future. (If not
Actually, about the emulator being single core, I was just looking
into this. As I understand it, the Android emulator runs on top of
QEMU (according to Wikipedia) and since QEMU is not multi-core neither
is the emulator. Well Wikipedia has an interesting comment on that, in
says:
For full system
It would be cool if Google released their performance results and started
showing us the progress they were making. I know that I would be excited
about any and all improvements. Of course, and I posted this in another
thread, I think that an easily possible win might be to use COREMU ontop of
25 matches
Mail list logo
