I've patched APK Expansion library so it can download additional .obb files
from my server and store in shared-storage/Android/obb/package-name
with main and patch files.
At http://developer.android.com/google/play/expansion-files.html you can
read strong limitation: do not save other data
If no one can answer, the normal assumption would be everyone's clueless.
In any case, I did not assert that everyone's clueless, only asking if that
were so. As it is, I have pointed out that the exact same question on Stack
Overflow remains unanswered, and he wasnt rude.
I am no longer
*If you are such a fragile and sensitive being, I suggest that you stop
reading.*
I am neither fragile nor sensitive. You were being rude, were called out on
it, and then got belligerent. I was simply giving you some advice if you
really wanted to have a chance at getting an answer.
*In fact, I
Good point. I will have to start updating my apps now. :-)
On Tue, May 12, 2015 at 8:59 AM Jose_GD jose.gonzale...@gmail.com wrote:
+1.
Google wouldn't take the effort to make AppCompat if they didn't intend to
get Material Design on older devices.
Cheers
José
Sorry if you don't like the truth, but you were being rude and impatient.
When you post in this forum is it expected that somebody who knows the
answer will enlighten you, not that people will search for the solution for
you. It is also expected that if you should happen to solve the problem
Glad you found the solution to your problem. :-)
On Wed, May 13, 2015 at 9:57 AM Ristar rista...@gmail.com wrote:
If no one can answer, the normal assumption would be everyone's clueless.
In any case, I did not assert that everyone's clueless, only asking if that
were so. As it is, I have
I can see that you are keeping up your trolling effort. Again, how do you
explain a question that remained unanswered on StackOverflow for years? You
can not. While I do not expect people to be at my beck and call, you
insufferable troll, I do expect no one to know what the code means and how
For the millionth time, before I posted the question, I have already tried
searching for the answer, and all I found was an unanswered StackOverflow
question. Do not try to make it sound like I expect anyone to do my work
for me, and no one here did anything worth a damn for me.
You people can
*For the millionth time, before I posted the question, I have already
tried searching for the answer, and all I found was an unanswered
StackOverflow question.*
I've already addressed that. That just adds to the reason that you should
be patient and wait a little longer. It also does nothing to
*Everyone works within time constraints. Do not assume that I have
unlimited time to wait.*
That is true, but no one made that assumption. Flip that around and you
can't assume that people on this forum are here at your beck and call.
*I have already done my due diligence.*
Great. But that
@Marina
Thank you for that information. I had never encountered that problem
before. If I encounter it in the future I will know how to start figuring
out the root cause of the problem.
On Wed, May 13, 2015 at 2:21 PM Justin Anderson magouyaw...@gmail.com
wrote:
*Everyone works within time
Just in case anyone else encounters this kind of error: usually the
actual error is somewhere upstream the Gradle Console log
messages.
Scroll up and you might find the answer or at least the root of your
generic error.
As the task is dexDebug, in this case I think it could be a repeated
/
Everyone works within time constraints. Do not assume that I have unlimited
time to wait.
I have already done my due diligence. As it is, there were no helpful links
and no one here helped, and you can get off your high horse because you did
nothing but derail the damn thread.
Your link is
Hello.
The latest version of Google Play Services (7.3) on the Play Store
indicates in What's new : Maps API v2 for Android Wear.
However, it still doesn't seem to work.
Can we expect an update of Android Wear to support this soon?
Thank you.
Le mercredi 4 février 2015 09:27:24 UTC+1,
14 matches
Mail list logo
