[android-developers] Digest for android-developers@googlegroups.com - 1 update in 1 topic

Comments: (0)
trans <transfire@gmail.com>: Aug 31 02:21PM -0700

On Monday, August 10, 2009 at 2:12:10 PM UTC-4, Jason Proctor wrote:
> great day when i discovered this class), more as an example of
> one-use objects, which always seemed like kinda bad form to me. does
> it not seem like bad form to anyone else?
 
I agree.
 
Truth be told, the Android API is full of poor design decisions. It appears
to me that much of it was done in a rush just to get something out there to
compete with Apple. That may have allowed Google to compete, but
unfortunately we developers have paid the price in time and headaches.
 
(P.S. That's why I had such high hopes for webOS, b/c it was so much more
developer friendly. I will never forgive HP for what they did -- though I
suspect M$ might have had a hand in that.)
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 3 updates in 3 topics

Comments: (0)
luca <luca.frammolini@gmail.com>: Aug 30 10:31AM -0700

I am developing an app with in app purchases. I have uploaded a signed apk
to the *beta version* and created two products. Everything seems to work,
but the inventory returned by queryInventoryAsync is always empty, that is,
its sku map is empty. I know that, as the developer of the app i can't buy
none of my products, but it seems to me that i should be able to query
google play services for available products. Since many hours have passed,
i think that i am doing something wrong, but i really have no idea of what
could be. I have already checked skus (they are the same), app key and so
on: everything seems ok.
How can I fix it?
Anton Persson <don.juanton@gmail.com>: Aug 30 07:57AM

A simple reboot of the Nexus 9 solved the issue...
 
张斌 <kimichangsign@gmail.com>: Aug 30 12:24AM -0700

I want to make a app about cell infomation.
 
I had new a TelephonyManager (tm) inorder to getNeighboringCellInfo.
 
*List<NeighboringCellInfo>
neighboringCellInfoList=tm.getNeighboringCellInfo();*
*new
ArrayAdapter(XXXX.this,R.layout.celllistlayout,neighboringCellInfoList);*
 
 
then,set this adapter to the ListView and notifyDataSetChanged.
 
The backgroud data is changing,but the ListView never.
 
What should i do to fresh the UI automatically?
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 2 updates in 2 topics

Comments: (0)
Anton Persson <don.juanton@gmail.com>: Aug 29 07:54PM

F/art (12936): art/runtime/check_jni.cc:65] JNI DETECTED ERROR IN APPLICATION: input is not valid Modified UTF-8: illegal start byte 0x82
F/art (12936): art/runtime/check_jni.cc:65] string: 'Magnetic Uncalibra ��'
F/art (12936): art/runtime/check_jni.cc:65] in call to NewStringUTF
F/art (12936): art/runtime/check_jni.cc:65] from int android.hardware.SystemSensorManager.nativeGetNextSensor(android.hardware.Sensor, int)
F/art (12936): art/runtime/check_jni.cc:65] "main" prio=5 tid=1 Runnable
F/art (12936): art/runtime/check_jni.cc:65] | group="main" sCount=0 dsCount=0 obj=0x72b79000 self=0xab411418
F/art (12936): art/runtime/check_jni.cc:65] | sysTid=12936 nice=0 cgrp=default sched=0/0 handle=0xf71d1bec
F/art (12936): art/runtime/check_jni.cc:65] | state=R schedstat=( 92824149 73577839 562 ) utm=4 stm=5 core=0 HZ=100
F/art (12936): art/runtime/check_jni.cc:65] | stack=0xff034000-0xff036000 stackSize=8MB
F/art (12936): art/runtime/check_jni.cc:65] | held mutexes= "mutator lock"(shared held)
F/art (12936): art/runtime/check_jni.cc:65] native: #00 pc 00004e64 /system/lib/libbacktrace_libc++.so (UnwindCurrent::Unwind(unsigned int, ucontext*)+23)
F/art (12936): art/runtime/check_jni.cc:65] native: #01 pc 00003665 /system/lib/libbacktrace_libc++.so (Backtrace::Unwind(unsigned int, ucontext*)+8)
F/art (12936): art/runtime/check_jni.cc:65] native: #02 pc 00256409 /system/lib/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+84)
F/art (12936): art/runtime/check_jni.cc:65] native: #03 pc 00238fc7 /system/lib/libart.so (art::Thread::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) const+158)
F/art (12936): art/runtime/check_jni.cc:65] native: #04 pc 000b199b /system/lib/libart.so (art::JniAbort(char const*, char const*)+610)
F/art (12936): art/runtime/check_jni.cc:65] native: #05 pc 000b20d5 /system/lib/libart.so (art::JniAbortF(char const*, char const*, ...)+68)
F/art (12936): art/runtime/check_jni.cc:65] native: #06 pc 000b468f /system/lib/libart.so (art::ScopedCheck::Check(bool, char const*, ...) (.constprop.129)+922)
F/art (12936): art/runtime/check_jni.cc:65] native: #07 pc 000be1bd /system/lib/libart.so (art::CheckJNI::NewStringUTF(_JNIEnv*, char const*)+44)
F/art (12936): art/runtime/check_jni.cc:65] native: #08 pc 0005f8b7 /system/lib/libandroid_runtime.so (???)
F/art (12936): art/runtime/check_jni.cc:65] native: #09 pc 000a4a1d /system/lib/libandroid_runtime.so (???)
F/art (12936): art/runtime/check_jni.cc:65] native: #10 pc 00086fbd /data/dalvik-cache/arm/system@framework@boot.oat (Java_android_hardware_SystemSensorManager_nativeGetNextSensor__Landroid_hardware_Sensor_2I+104)
F/art (12936): art/runtime/check_jni.cc:65] at android.hardware.SystemSensorManager.nativeGetNextSensor(Native method)
F/art (12936): art/runtime/check_jni.cc:65] at android.hardware.SystemSensorManager.<init>(SystemSensorManager.java:73)
F/art (12936): art/runtime/check_jni.cc:65] - locked <0x283935e7> (a java.lang.Object)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ContextImpl$31.createService(ContextImpl.java:540)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ContextImpl$ServiceFetcher.getService(ContextImpl.java:298)
F/art (12936): art/runtime/check_jni.cc:65] - locked <0x26728594> (a java.util.ArrayList)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ContextImpl.getSystemService(ContextImpl.java:1838)
F/art (12936): art/runtime/check_jni.cc:65] at android.view.ContextThemeWrapper.getSystemService(ContextThemeWrapper.java:113)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.Activity.getSystemService(Activity.java:5045)
F/art (12936): art/runtime/check_jni.cc:65] at com.toolkits.kamoflage.SensorHandler.<init>(SensorHandler.java:49)
F/art (12936): art/runtime/check_jni.cc:65] at com.holidaystudios.satan.vuKNOB.onCreate(vuKNOB.java:268)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.Activity.performCreate(Activity.java:5990)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ActivityThread.access$800(ActivityThread.java:151)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
F/art (12936): art/runtime/check_jni.cc:65] at android.os.Handler.dispatchMessage(Handler.java:102)
F/art (12936): art/runtime/check_jni.cc:65] at android.os.Looper.loop(Looper.java:135)
F/art (12936): art/runtime/check_jni.cc:65] at android.app.ActivityThread.main(ActivityThread.java:5254)
F/art (12936): art/runtime/check_jni.cc:65] at java.lang.reflect.Method.invoke!(Native method)
F/art (12936): art/runtime/check_jni.cc:65] at java.lang.reflect.Method.invoke(Method.java:372)
F/art (12936): art/runtime/check_jni.cc:65] at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
F/art (12936): art/runtime/check_jni.cc:65] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
F/art (12936): art/runtime/check_jni.cc:65]
luca <luca.frammolini@gmail.com>: Aug 29 02:05AM -0700

You are right: only production apks can be made public.
 
Il giorno venerdì 28 agosto 2015 20:52:44 UTC+2, TreKing ha scritto:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 4 updates in 2 topics

Comments: (0)
luca <luca.frammolini@gmail.com>: Aug 28 03:52AM -0700

I want to add that the app informations, like main icon, images and so on
are only for testing purpose, not the right ones!
luca <luca.frammolini@gmail.com>: Aug 28 03:49AM -0700

I have uploaded to the google developer console a 90% finished app in the
beta channel. The app Store There is not even a production APK. By mistake,
i hit the publish button! Now there is a message saying something like:
updating in progress.
 
What will happen now?
Will my unfinished app be accessible on google play by everyone??
If so, can i unpublish it, finish it and republish again??
Thank you.
TreKing <trekingapp@gmail.com>: Aug 28 01:29PM -0500


> What will happen now?
> Will my unfinished app be accessible on google play by everyone??
 
I don't think so. Betas are controlled by access. So it will be available
to anyone in the Google Group, Community (or most recently anyone with the
link you choose to distribute).
 
If you want to share the app package name, we can check if it's visible.
 
If so, can i unpublish it, finish it and republish again??
 
Sure.
 
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
luca <luca.frammolini@gmail.com>: Aug 28 03:55AM -0700

I have uploaded to the google developer console a 90% finished app in the
beta channel. I have not configured any type of test. The app form is not
even the final one (the main icon, the screen shots and so on are only test
images). There is not even a production APK. By mistake, i hit the publish
button! Now there is a message saying something like: updating in progress.
 
What will happen now?
Will my unfinished app be accessible on google play by everyone??
If so, can i unpublish it, finish it and republish again??
Thank you.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 4 updates in 3 topics

Comments: (0)
Steve Gabrilowitz <steveg1701@gmail.com>: Aug 27 01:25PM -0400

You don't instantiate it directly, you don't instantiate it at all,
therefore you can not extend it in the conventional sense. What you can do
is to create a class that acts that acts as a wrapper for the methods of TM
that you want it to expose directly. If you tell us what sort of
extensions you want to make you will get better suggestions!
张张斌 <kimichangsign@gmail.com>: Aug 28 09:49AM +0800

Want to override some member methods,like toString.
 
 
--
如果邮箱有问题,请转至kimichangsign@163.com <kimichangsign@sina.com>
Jags <jagatm@gmail.com>: Aug 27 02:14AM -0700

hi all,
 

 
I have inherited a legacy code which works well, but i need to implement
sqlcipher into in. my app is for both android and ios, hence sqlite part is
written in c++ which is also used by nadroid using JNI.
 

 
hence i am unable to use ready to use library for ios and android as i use
functions like sqlite3_open, sqlite3_exec.
 

 
do i need to add all c++ files for sqlcipher and compile and use it ?
 
is there a tutorial how to use it in c++ code ?
 

 
regrds
Jags <jagatm@gmail.com>: Aug 27 02:19AM -0700

hi all,
 
i use webview in my android app to be used later (on click of menu)
 
the problem is, when i do loadurl, there is a flicker and delay.
 
i wanted to load the url in the beginning, and only show the ebview when
required (on click)
 
when i do objWebView.loadUrl("help.html");
 
inside oncreate of mainactivity, it does not load the page.
 
if i do it on button click it loads properly, doing runOnUiThread also does
not help.
 
what is the correct way to load a page in the beginning and display later ?
webview is not my initial contentview.
 
thanks in advance
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 3 updates in 2 topics

Comments: (0)
"yvesliu@gmail.com" <yvesliu@gmail.com>: Aug 26 03:30PM -0700

I had an app on the play store market for awhile now, and i recently fixed
a couple of problems and I ran into this problem.
 
I am not sure if this problem is related to the app package name starts
with an upper case letter. Here is the problem:
 
Before I was using Eclipse to build the app and sign the package, and I can
update the app on the play store and my customers are able to download and
install the app. Now, I changed my system to use Android Studio, and I can
build and sign the installer, uploaded the app to the play store. Now,
nobody can install it. They either got error code 504 during install or a
message saying malformed manifest. I contacted play store support and got
answers which is not helpful at all.
 
Since to update an app, we can't change the package name, I don't know if
the package name was the issue. If I change my system back to Eclipse,
rebuild/sign the package, will that work? Any ideas on what to do? Or
anyway for me to change the package name in play store?
 
Thanks
 
 
Yves
TreKing <trekingapp@gmail.com>: Aug 26 09:46PM -0500

On Wed, Aug 26, 2015 at 5:30 PM, yvesliu@gmail.com <yvesliu@gmail.com>
wrote:
 
> Since to update an app, we can't change the package name, I don't know if
> the package name was the issue.
 
 
Your package name cannot be changed and should not be an issue. I and I'm
sure thousands of other developers have migrated published apps from being
built in Eclipse to Android Studio without this issue, so it's not likely a
problem with using the same package name.
 
 
> If I change my system back to Eclipse, rebuild/sign the package, will that
> work?
 
 
Maybe? Try it?
 
 
> Any ideas on what to do?
 
 
Double check your set up. Make sure your signing certificate is set up
correctly and try again. If the error persists, try building the release
app manually via the command line, outside of Android Studio and see if
that helps.
 
 
> Or anyway for me to change the package name in play store?
 
 
Not unless you like the idea of abandoning your existing app and all of its
stats and starting over from scratch.
 
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
Chris <crebstock@gmail.com>: Aug 26 09:52AM -0700

I don't see a way to prevent the user from controlling number of copies/etc
from the standard android print API. Is anyone aware of whether this is
possible?
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 2 updates in 1 topic

Comments: (0)
Bram Stolk <b.stolk@gmail.com>: Aug 25 12:04PM -0700

What worked two days ago, no longer worked yesterday or today:
Linking an app to Game Services.
 
I reported the issue
here: https://github.com/playgameservices/android-basic-samples/issues/153
But I have a feeling that this repo is no longer monitored, all the reports
I made in the last weeks are ignored on github.
 
Can someone inside Google please investigate this?
Two other users reported the same issue, as they responded on my
stackoverflow
question: http://stackoverflow.com/questions/32194513/create-android-oauth-client-fails-with-an-unexpected-error-occurred-please-tr
 
thx,
 
Bram
Bram Stolk <b.stolk@gmail.com>: Aug 25 07:02PM -0700

This got fixed today:
https://github.com/playgameservices/android-basic-samples/issues/153#issuecomment-134749998
 
Thanks, Google.
 
On Tuesday, August 25, 2015 at 12:04:35 PM UTC-7, Bram Stolk wrote:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 9 updates in 3 topics

Comments: (0)
Paulo Cesar <puelocesar@gmail.com>: Aug 24 03:11PM -0700

I'm mainly a iOS developer, and I have this app that applies a series of
transformations and blend filters on images, all using Apple Core Image
library. And I now that I have to port it to Android, is there any
equivalent to Core Image in Android?
Justin Anderson <magouyaware@gmail.com>: Aug 24 10:18PM

I would imagine you can do similar things, but not knowing kinds of
transformations and filters you are wanting to do, not sure how we can
help...
 
Paulo Cesar <puelocesar@gmail.com>: Aug 24 04:47PM -0700

Well, I translate, scale and crop one image according to user gestures and
then blend it (CILightenBlendMode) with another image.
 
It seems that Android officially doesn't have anything remotely similar to
Core Image, but I found some thirty party libraries,
like chrisbatt/AndroidFastImageProcessing. I'm only a bit concerned because
it's last commit was one year ago, so if it has bugs, it will continue
having...
 
Anyone with experience with OpenCV? Is it viable for this kind of workflow,
or is it a overkill?
TreKing <trekingapp@gmail.com>: Aug 24 06:54PM -0500


> is there any equivalent to Core Image in Android?
 
 
I don't know what Core Image is or what it entails, but if you want to
manipulate images, this is a good place to start:
http://developer.android.com/guide/topics/graphics/2d-graphics.html
 
Then follow all of the links (Canvas, Bitmap, OpenGL, etc).
 
Good luck.
 
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
Paulo Cesar <puelocesar@gmail.com>: Aug 24 05:32PM -0700

Thanks for the link. I'm familiar with Canvas drawing on Android. I have
some apps using it, but when using high resolution images it throws a lot
of out of memory errors, that's why I was asking if there's something more
robust.
 
In Core Image for example, I can get a CIImage with 2160x2160 pixels,
translate, rotate it, and blend it with another image with same resolution
all with constant 60fps. In my experience with Canvas, only one image with
that size can already crash many android devices.
 
But well, maybe I can limit the image size like I did on other Android
apps.
 
Em segunda-feira, 24 de agosto de 2015 21:04:59 UTC-3, TreKing escreveu:
TreKing <trekingapp@gmail.com>: Aug 24 08:25PM -0500

> translate, rotate it, and blend it with another image with same resolution
> all with constant 60fps. In my experience with Canvas, only one image with
> that size can already crash many android devices.
 
 
Yeah, the fragmentation is going to be your biggest hurdle. I've not needed
to anything this crazy with images, but from reading this forum, SO, and
assorted blog posts, image manipulation to that degree is non-trivial, to
say the least. There is no built-in library to such things either, as far
as I know.
 
But well, maybe I can limit the image size like I did on other Android apps.
 
 
Probably your best bet. Generally you would create a small copy of the
image you want to manipulate, let the user fiddle, then record all the
transformations the user has applied to the sample, then "commit" them back
to the original.
 
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
张斌 <kimichangsign@gmail.com>: Aug 24 05:48PM -0700

I want to create a new class extends TelephonyManager which can not
instantiate directly.TelephonyManager can be instantiate through
Context.getSystemService(Context.TELEPHONY_SERVICE).
 
 
Are there anyone know sth about it?
 
Waiting for your reply!
catafest <catalinfest@gmail.com>: Aug 24 01:36AM -0700

... try make all settings for your Android Studio ( most Project Settings
and if don't working take a look at build.gradle file).
also , Genymotion use VirtualBox settings and it is just one android
emulator.
 
On Monday, August 24, 2015 at 12:59:37 AM UTC+3, Phil Gibbs wrote:
Justin Anderson <magouyaware@gmail.com>: Aug 24 11:59AM

I am on Win 10 and have not had problems like this. I do not use GenyMotion.
 
I also found this:
http://stackoverflow.com/questions/31709084/genymotion-problems-in-windows-10
 
The underlying problems may very well not even be GenyMotion, but
VirtualBox... As of last night the latest version is not fully supported on
Win 10.
 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 4 updates in 2 topics

Comments: (0)
gjs <garyjamessilva@gmail.com>: Aug 22 11:47PM -0700

Hi,
 
Maybe try again but without installing via ES File Explorer ?
 
I just tried the a similar test - downloading & installing by 'sideloading'
a (properly signed) apk via a gmail attachment to Nexus 7 (2012) with
Android v5.1.1 & it installed (using the default Android installer - NOT ES
File Explorer) without error & worked OK.
 
(My apk was created in Eclipse however, no AS...)
 
Also if you are attempting to download & install from a Web page you also
need to set the correct content type in your web server, eg -
 
<mime-mapping>
 
<extension>apk</extension>
 
<mime-type>application/vnd.android.package-archive</
mime-type>
 
</mime-mapping>
 
Regards
 
On Sunday, August 23, 2015 at 2:04:31 AM UTC+10, cookdav wrote:
cookdav <David.Hubert.Cook@gmail.com>: Aug 23 05:38AM -0700

Ok, I got past the problem of "Parse Error..", by SIGNING the app.
(That wasn't necessary a year ago.)
 
So, now the installer runs, but at the end, the installer says:
 
 
X App not installed.
 
[ Sigh. No reason given. What...we're supposed to be mind-readers??? ]
 
 
 
 
 
On Sunday, August 23, 2015 at 2:47:42 AM UTC-4, gjs wrote:
cookdav <David.Hubert.Cook@gmail.com>: Aug 23 05:21PM -0700

Ok, I've now figured out why the app won't install...it;s
because Android requires that the SIGNING KEYS match
the previously installed app's key.
 
But, it's not like I changed the key. The previous instance
from a year or so ago did NOT have a key and now it MUST
have a key. So, there's NO POSSIBLE WAY to make no-key
match a new-key. (Sigh.)
 
I figured this out, because my wife just got a new Android-based
phone, and the app installed just fine there, since the earlier
instance of the app was never installed on it previously.
 
Once that indicated what the problem was, I did a factory-reset
on my Nexus-7(2012), and then the new app installed just fine.
 
 
 
On Sunday, August 23, 2015 at 8:38:36 AM UTC-4, cookdav wrote:
Phil Gibbs <javabiker52@gmail.com>: Aug 23 02:59PM -0700

After installing Win 10 I'm getting many lock-ups when using AS. Not sure how much Genymotion is involved.
Downgraded to Win 7 and problems disappeared. So now I'm reluctant to try 10 again.
Anyone seen this issue?
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 3 updates in 2 topics

Comments: (0)
cookdav <David.Hubert.Cook@gmail.com>: Aug 22 09:04AM -0700

After doing a successful assembleRelease in AndroidStudio (version 1.3.1),
I can use the
debugger to download and install my app, via a USB-cable, and it installs
(and runs) fine.
 
But, if I put the APK file onto my webpage, and download it (using Chrome)
onto the tablet,
when I try to install it (using ES File Explorer), I immediately get
"Parse error ...there was a problem parsing the package".
 
The target tablet(s) are Nexus 7(2012) and Nexus 10, running Android v5.1.1.
 
This all worked fine, back a year ago, when I was running beta copy of
AndroidStudio.
(I have imported this year-old app's project tree, into AndroidStudio 1.3.1)
 
So, I repeated this experiment, after creating a NEW boiler-plate app in
AndroidStudio
and I get the same behavior...i.e. it installs this generic TestProject via
USB-cable via
the Androidstudio's debugger just fine, but I get the "Parse error" if I
try to install
a downloaded copy (either via Chrome or via the USB-cable) residing in the
Download folder.
 
Is there some 'debugging' method of installing Android APKs that will give
a more specific
error-code, to provide specifics of what the problem is???
[ When I google this 'Parse error' symptom, there are at least a DOZEN
different reasons
mentioned that can cause this error, but none of them apply. ]
 
Yes, I have developer options enabled on the tablets including
allow-from-unknown-sources,
and yes, I've verified the exact file-sizes using ES FIle Explorer, etc,
etc.
 
Ideas? Or should I just give up trying to develop native Android apps
using AndroidStudio?
hyc <hyc@highlandsun.com>: Aug 22 05:19AM -0700

Seems the output I tried to attach vanished. Pasting it here:
 
 
Linux gamba 4.1.5-1-ARCH #1 SMP PREEMPT Tue Aug 11 15:41:14 CEST 2015
hyc <hyc@highlandsun.com>: Aug 22 05:17AM -0700

LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
emulator: found SDK root at /home/software/android-sdk-linux
emulator: Android virtual device file at: /home/hyc/.android/avd/test2.ini
emulator: virtual device content at /home/hyc/.android/avd/test2.avd
emulator: virtual device config file: /home/hyc/.android/avd/test2.avd/config.ini
emulator: using core hw config path: /home/hyc/.android/avd/test2.avd/hardware-qemu.ini
emulator: Found AVD target API level: 23
emulator: Read property file at /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//build.prop
emulator: No boot.prop property file found.
emulator: 'magic' skin format detected: 480x800
emulator: autoconfig: -skin 480x800
emulator: autoconfig: -skindir (null)
emulator: keyset loaded from: /home/hyc/.android/default.keyset
emulator: trying to load skin file '/home/software/android-sdk-linux/tools/lib/emulator/skins/dynamic//layout'
emulator: loaded dynamic skin width=480 height=800 bpp=16
 
emulator: autoconfig: -kernel /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//kernel-qemu
emulator: Auto-detect: Kernel image requires legacy device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: autoconfig: -ramdisk /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//ramdisk.img
emulator: Using initial system image: /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img
emulator: autoconfig: -data /home/hyc/.android/avd/test2.avd/userdata-qemu.img
emulator: autoconfig: -initdata /home/hyc/.android/avd/test2.avd/userdata.img
emulator: autoconfig: -cache /home/hyc/.android/avd/test2.avd/cache.img
emulator: autoconfig: -sdcard /home/hyc/.android/avd/test2.avd/sdcard.img
emulator: Physical RAM size: 1024MB
 
emulator: GPU emulation enabled using 'host' mode
emulator: WARNING: CPU acceleration only works with x86/x86_64 system images.
Content of hardware configuration file:
hw.cpu.arch = arm
hw.cpu.model = cortex-a8
hw.ramSize = 1024
hw.screen = touch
hw.mainKeys = yes
hw.trackBall = yes
hw.keyboard = yes
hw.keyboard.lid = no
hw.keyboard.charmap = qwerty2
hw.dPad = no
hw.gsmModem = yes
hw.gps = yes
hw.battery = yes
hw.accelerometer = yes
hw.audioInput = yes
hw.audioOutput = yes
hw.sdCard = yes
hw.sdCard.path = /home/hyc/.android/avd/test2.avd/sdcard.img
disk.cachePartition = yes
disk.cachePartition.path = /home/hyc/.android/avd/test2.avd/cache.img
disk.cachePartition.size = 66m
hw.lcd.width = 480
hw.lcd.height = 800
hw.lcd.depth = 16
hw.lcd.density = 240
hw.lcd.backlight = yes
hw.gpu.enabled = yes
hw.gpu.mode = host
hw.initialOrientation = portrait
hw.camera.back = none
hw.camera.front = none
vm.heapSize = 32
hw.sensors.proximity = yes
hw.sensors.magnetic_field = yes
hw.sensors.orientation = no
hw.sensors.temperature = yes
hw.useext4 = yes
kernel.path = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//kernel-qemu
kernel.parameters = androidboot.hardware=goldfish android.checkjni=1
kernel.newDeviceNaming = no
kernel.supportsYaffs2 = no
disk.ramdisk.path = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//ramdisk.img
disk.systemPartition.initPath = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img
disk.systemPartition.size = 1536m
disk.dataPartition.path = /home/hyc/.android/avd/test2.avd/userdata-qemu.img
disk.dataPartition.size = 550m
avd.name = test2
.
QEMU options list:
emulator: argv[00] = "tools/emulator64-arm"
emulator: argv[01] = "-android-hw"
emulator: argv[02] = "/home/hyc/.android/avd/test2.avd/hardware-qemu.ini"
Concatenated QEMU options:
tools/emulator64-arm -android-hw /home/hyc/.android/avd/test2.avd/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: Using kernel serial device prefix: ttyS
emulator: Ramdisk image contains fstab.goldfish file
emulator: Found format of system partition: 'ext4'
emulator: Found format of userdata partition: 'ext4'
emulator: Found format of cache partition: 'ext4'
emulator: system partition format: ext4
emulator: Mapping 'system' partition image to /tmp/android-hyc/emulator-eUjF6r
emulator: nand_add_dev: system,size=0x60000000,file=/tmp/android-hyc/emulator-eUjF6r,initfile=/home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img,pagesize=512,extrasize=0
emulator: userdata partition format: ext4
emulator: nand_add_dev: userdata,size=0x22600000,file=/home/hyc/.android/avd/test2.avd/userdata-qemu.img,pagesize=512,extrasize=0
emulator: cache partition format: ext4
emulator: nand_add_dev: cache,size=0x4200000,file=/home/hyc/.android/avd/test2.avd/cache.img,pagesize=512,extrasize=0
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '32m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '240'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '1'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none'
emulator: Initializing hardware OpenGLES emulation support
emulator: OpenGL Vendor=[Google (X.Org)]
emulator: OpenGL Renderer=[Android Emulator OpenGL ES Translator (Gallium 0.4 on AMD ARUBA)]
emulator: OpenGL Version=[OpenGL ES 2.0 (3.0 Mesa 10.6.4)]
emulator: Adding boot property: 'ro.opengles.version' = '131072'
emulator: Kernel parameters: qemu.gles=1 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1
^C^Z
[1]+ Stopped LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$ kill -9 %1
 
[1]+ Stopped LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$
[1]+ Killed LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$ DRI_PRIME=1 LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
emulator: found SDK root at /home/software/android-sdk-linux
emulator: Android virtual device file at: /home/hyc/.android/avd/test2.ini
emulator: virtual device content at /home/hyc/.android/avd/test2.avd
emulator: virtual device config file: /home/hyc/.android/avd/test2.avd/config.ini
emulator: using core hw config path: /home/hyc/.android/avd/test2.avd/hardware-qemu.ini
emulator: Found AVD target API level: 23
emulator: Read property file at /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//build.prop
emulator: No boot.prop property file found.
emulator: 'magic' skin format detected: 480x800
emulator: autoconfig: -skin 480x800
emulator: autoconfig: -skindir (null)
emulator: keyset loaded from: /home/hyc/.android/default.keyset
emulator: trying to load skin file '/home/software/android-sdk-linux/tools/lib/emulator/skins/dynamic//layout'
emulator: loaded dynamic skin width=480 height=800 bpp=16
 
emulator: autoconfig: -kernel /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//kernel-qemu
emulator: Auto-detect: Kernel image requires legacy device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: autoconfig: -ramdisk /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//ramdisk.img
emulator: Using initial system image: /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img
emulator: autoconfig: -data /home/hyc/.android/avd/test2.avd/userdata-qemu.img
emulator: autoconfig: -initdata /home/hyc/.android/avd/test2.avd/userdata.img
emulator: autoconfig: -cache /home/hyc/.android/avd/test2.avd/cache.img
emulator: autoconfig: -sdcard /home/hyc/.android/avd/test2.avd/sdcard.img
emulator: Physical RAM size: 1024MB
 
emulator: GPU emulation enabled using 'host' mode
emulator: WARNING: CPU acceleration only works with x86/x86_64 system images.
Content of hardware configuration file:
hw.cpu.arch = arm
hw.cpu.model = cortex-a8
hw.ramSize = 1024
hw.screen = touch
hw.mainKeys = yes
hw.trackBall = yes
hw.keyboard = yes
hw.keyboard.lid = no
hw.keyboard.charmap = qwerty2
hw.dPad = no
hw.gsmModem = yes
hw.gps = yes
hw.battery = yes
hw.accelerometer = yes
hw.audioInput = yes
hw.audioOutput = yes
hw.sdCard = yes
hw.sdCard.path = /home/hyc/.android/avd/test2.avd/sdcard.img
disk.cachePartition = yes
disk.cachePartition.path = /home/hyc/.android/avd/test2.avd/cache.img
disk.cachePartition.size = 66m
hw.lcd.width = 480
hw.lcd.height = 800
hw.lcd.depth = 16
hw.lcd.density = 240
hw.lcd.backlight = yes
hw.gpu.enabled = yes
hw.gpu.mode = host
hw.initialOrientation = portrait
hw.camera.back = none
hw.camera.front = none
vm.heapSize = 32
hw.sensors.proximity = yes
hw.sensors.magnetic_field = yes
hw.sensors.orientation = no
hw.sensors.temperature = yes
hw.useext4 = yes
kernel.path = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//kernel-qemu
kernel.parameters = androidboot.hardware=goldfish android.checkjni=1
kernel.newDeviceNaming = no
kernel.supportsYaffs2 = no
disk.ramdisk.path = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//ramdisk.img
disk.systemPartition.initPath = /home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img
disk.systemPartition.size = 1536m
disk.dataPartition.path = /home/hyc/.android/avd/test2.avd/userdata-qemu.img
disk.dataPartition.size = 550m
avd.name = test2
.
QEMU options list:
emulator: argv[00] = "tools/emulator64-arm"
emulator: argv[01] = "-android-hw"
emulator: argv[02] = "/home/hyc/.android/avd/test2.avd/hardware-qemu.ini"
Concatenated QEMU options:
tools/emulator64-arm -android-hw /home/hyc/.android/avd/test2.avd/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: Using kernel serial device prefix: ttyS
emulator: Ramdisk image contains fstab.goldfish file
emulator: Found format of system partition: 'ext4'
emulator: Found format of userdata partition: 'ext4'
emulator: Found format of cache partition: 'ext4'
emulator: system partition format: ext4
emulator: Mapping 'system' partition image to /tmp/android-hyc/emulator-U3HPAQ
emulator: nand_add_dev: system,size=0x60000000,file=/tmp/android-hyc/emulator-U3HPAQ,initfile=/home/software/android-sdk-linux/system-images/android-23/google_apis/armeabi-v7a//system.img,pagesize=512,extrasize=0
emulator: userdata partition format: ext4
emulator: nand_add_dev: userdata,size=0x22600000,file=/home/hyc/.android/avd/test2.avd/userdata-qemu.img,pagesize=512,extrasize=0
emulator: cache partition format: ext4
emulator: nand_add_dev: cache,size=0x4200000,file=/home/hyc/.android/avd/test2.avd/cache.img,pagesize=512,extrasize=0
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '32m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '240'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '1'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none'
emulator: Initializing hardware OpenGLES emulation support
emulator: OpenGL Vendor=[Google (X.Org)]
emulator: OpenGL Renderer=[Android Emulator OpenGL ES Translator (Gallium 0.4 on AMD CAPE VERDE)]
emulator: OpenGL Version=[OpenGL ES 2.0 (3.0 Mesa 10.6.4)]
emulator: Adding boot property: 'ro.opengles.version' = '131072'
emulator: Kernel parameters: qemu.gles=1 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1
^Z
[1]+ Stopped DRI_PRIME=1 LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$ kill -9 %
 
[1]+ Stopped DRI_PRIME=1 LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$
[1]+ Killed DRI_PRIME=1 LD_LIBRARY_PATH=tools/lib64 tools/emulator64-arm -avd test2 -verbose
[hyc@gamba android-sdk-linux]$
[hyc@gamba android-sdk-linux]$
[hyc@gamba android-sdk-linux]$ tools/emulator64-arm -avd test1 -gpu off
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 3 updates in 1 topic

Comments: (0)
gc <gcstang@gmail.com>: Aug 21 06:24AM -0700

Just updating, if anyone can help it would be appreciated. If you need
more information please ask.
 
I think this should be similar if you're using an Activity and showing
video but not sure, how do you programmatically shut it down so the finish
can occur and return to the prior Activity.
 
Thank you for any help.
 
 
On Monday, August 17, 2015 at 4:29:38 PM UTC-5, gc wrote:
Gustavo Oliveira <gus512@gmail.com>: Aug 21 01:34PM -0300

Activity.finish() should be called from the UI thread. Try doing that and
post the result.
 
Cheers,
Gus
 
gc <gcstang@gmail.com>: Aug 21 12:33PM -0700

That was the issue, I was hoping it was something simple.
 
Thank you, very much!
 
 
 
 
 
On Friday, August 21, 2015 at 11:42:10 AM UTC-5, Gus wrote:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.