Looking at all the diff links inside this page:
https://android.googlesource.com/platform/frameworks/base/+/0e3328fbdd3845b0e2bec364e951498eaee6b079
you can guess all the files responsible for the meminfo display function.
For eg:
This could be the target of meminfo's source of data:
I have my in-app subscription working using a second test account. Now when
I check inventory using queryInventoryAsync the subscription shows up as
expected.
So now I want to do some more testing. I want to cancel the subscription
and then when I know that works, I want to test again.
Over on StackOverflow I'm getting no answers to any of my posts with
in-app-billing or in-app-purchase tags. I checked other posts and found
that nobody else is getting any answers to posts with those two tags
either.
I'm not getting any answers on this forum either.
As far as I know it
I have implemented Google Play subscriptions in an unpublished version of
one of my apps.
I purchased a monthly subscription (against the phony credit card ending in
0999) on December 24th and it showed up in my merchant account. Also when
my app did a queryInventoryAsync, the subscription
These new APIs seem to be fun to try but is there any reason as to why
the plug-in service is not distributed through play store just like google
play services?
Based on what i read, any updates, bug fixes in the plug-in service would
be restricted by the OEM like amazon in this case, isn't
is this your app url
https://play.google.com/store/apps/details?id=com.cleanmaster.security
On Sat, Jan 4, 2014 at 11:07 PM, Kristopher Micinski krismicin...@gmail.com
wrote:
Oh, no, I'm wrong, it turns out you also work for that company too,
reading the comments on your Google+ link.
6 matches
Mail list logo
