At this point it might be useful if you manage to create a very small
sample app that has this problem, so that you can share that source code
and I/we can try it and figure out what's going on.
I'm sorry I can't be more helpful...
On Sun, Feb 26, 2012 at 2:15 AM, Jim Graham
On Sun, Feb 26, 2012 at 11:11:25AM +0100, YuviDroid wrote:
At this point it might be useful if you manage to create a very small
sample app that has this problem, so that you can share that source code
and I/we can try it and figure out what's going on.
This is the book example I've been
So, I played a bit with this Snapshot project. First of all, I'm using the
Motorola Xoom with ICS (4.0.3).
I tried following your steps (side load, press home, start from app drawer,
press back) and indeed I got the crash. What's really odd is that in this
scenario when you press 'back' it doesn't
On Sun, Feb 26, 2012 at 02:42:19PM +0100, YuviDroid wrote:
Anyway, I tried adding a different launchMode to the Snapshot
activityandit worked! I used 'singleTop'.
Funny...I tried that yesterday. I must have made a typo or something.
Anyways, I downloaded the new apk, and it worked.
No problem :)
Unfortunately I don't really know what's happening..it seems like the
Installer launches apps in some 'strange' way, while the app drawer uses a
different way and...dunno something odd happens :S
(lol not really useful! eheh)
If someone could explain that it would be great.
Yuvi
On Sun, Feb 26, 2012 at 03:13:00PM +0100, YuviDroid wrote:
No problem :)
Unfortunately I don't really know what's happening..it seems like the
Installer launches apps in some 'strange' way, while the app drawer uses a
different way and...dunno something odd happens :S
(lol not really
Launcher starts activites with:
Flags = Intent.FLAG_ACTIVITY_NEW_TASK |
Intent.FLAG_ACTIVITY_RESET_TASK_IF_NEEDED
Action = Intent.ACTION_MAIN
Category = Intent.CATEGORY_LAUNCHER
You can see it in the logcat:
02-26 18:55:39.863 I/ActivityManager( 273): Starting: Intent {
On Sun, Feb 26, 2012 at 07:06:28PM +0400, Kostya Vasilyev wrote:
Market and Eclipse use intents with slightly different flags.
So in this case, side-loading using the tablet's installer, would
that be considered as the same as launching via the market?
Thanks,
--jim
--
THE SCORE: ME: 2
On 02/26/2012 07:15 PM, Jim Graham wrote:
On Sun, Feb 26, 2012 at 07:06:28PM +0400, Kostya Vasilyev wrote:
Market and Eclipse use intents with slightly different flags.
So in this case, side-loading using the tablet's installer, would
that be considered as the same as launching via the
Sorry for the delay...didn't hear (or see) the announcement about
the incoming message
On Sun, Feb 26, 2012 at 07:23:28PM +0400, Kostya Vasilyev wrote:
On 02/26/2012 07:15 PM, Jim Graham wrote:
On Sun, Feb 26, 2012 at 07:06:28PM +0400, Kostya Vasilyev wrote:
Market and Eclipse use
On Sun, Feb 26, 2012 at 11:36 AM, Jim Graham spooky1...@gmail.com wrote:
Sorry for the delay...didn't hear (or see) the announcement about
the incoming message
On Sun, Feb 26, 2012 at 07:23:28PM +0400, Kostya Vasilyev wrote:
On 02/26/2012 07:15 PM, Jim Graham wrote:
On Sun, Feb 26, 2012
On Sun, Feb 26, 2012 at 01:01:41PM -0500, Kristopher Micinski wrote:
Ah, the package manager, you mean,
Yeah, that's it. :-)
Later,
--jim
--
THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4)| Now what *you* need is a proper pint of
spooky1...@gmail.com| porter poured in a
Hi,
Add code / try catch block to check if camera connects OK. If not
indicate to user camera is busy, exit and restart app.
Regards
On Feb 25, 10:33 am, Jim Graham spooky1...@gmail.com wrote:
One more detail
On Fri, Feb 24, 2012 at 05:12:47PM -0600, Jim Graham wrote:
What I'm seeing is
On Sat, Feb 25, 2012 at 05:45:09AM -0800, gjs wrote:
Add code / try catch block to check if camera connects OK. If not
indicate to user camera is busy, exit and restart app.
No change. Keep in mind, this happens when exiting from the app.
AND, it *ONLY* happens if the app is run from the
Hey,
I'm not sure as to what is going wrong exactly...but you might want to
check the launchMode of your activity/ies.
http://developer.android.com/guide/topics/manifest/activity-element.html#lmode
I remember I had a similar issue in the past (not with the camera though)
when I launched an app
On Sun, Feb 26, 2012 at 01:31:08AM +0100, YuviDroid wrote:
I'm not sure as to what is going wrong exactly...but you might want to
check the launchMode of your activity/ies.
http://developer.android.com/guide/topics/manifest/activity-element.html#lmode
I will...thanks.
I remember I had a
On Sat, Feb 25, 2012 at 06:35:06PM -0600, Jim Graham wrote:
On Sun, Feb 26, 2012 at 01:31:08AM +0100, YuviDroid wrote:
I'm not sure as to what is going wrong exactly...but you might want to
check the launchMode of your activity/ies.
On Sat, Feb 25, 2012 at 06:44:31PM -0600, Jim Graham wrote:
On Sat, Feb 25, 2012 at 06:35:06PM -0600, Jim Graham wrote:
On Sun, Feb 26, 2012 at 01:31:08AM +0100, YuviDroid wrote:
I'm not sure as to what is going wrong exactly...but you might want to
check the launchMode of your
One more detail
On Fri, Feb 24, 2012 at 05:12:47PM -0600, Jim Graham wrote:
What I'm seeing is a Force Close of my camera app in only one of four
situations:
1) side-load app, open via installer, pause using Home button,
resume using Honeycomb's active apps display (don't know
19 matches
Mail list logo