I am facing issue with my android app.
If a user installs my app through apk file. After installation a window
appears with two buttons *open* and *done* which is part of android os.
When user taps on *open,* it opens my launcher activity. Which is great...
After landing to Launcher
Dianne, did you have any luck with that sample APK and reproducing the
issue?
Thanks
On Friday, July 27, 2012 12:47:17 PM UTC+1, Kostya Vasilyev wrote:
2012/7/27 Jim Graham spook...@gmail.com javascript:
On Thu, Jul 26, 2012 at 10:35:18PM -0700, Andy dev wrote:
Anyone made any progress
Anyone made any progress with this issue, I still cannot pinpoint what
causes it?
On Tuesday, July 24, 2012 3:03:41 PM UTC+1, Larry Meadors wrote:
This is at the bottom of EVERY post to the list:
You received this message because you are subscribed to the Google
Groups Android Developers
!
On Mon, Jul 23, 2012 at 10:40 PM, Andy dev andrewpmo...@gmail.com wrote:
Dianne, I've created a very cut down version of my app where I'm still
getting the issue. I've uploaded it to google drive here:
https://docs.google.com/open?id=0B9RsW3kcQ9jPem9PLVIxdWdlQlU
Basically, build
with, and if you can't recover when it
is restarted then that is something that needs to be fixed in the app.
On Sat, Jul 21, 2012 at 4:01 PM, Andy dev andrewpmo...@gmail.com wrote:
Ok, I've found out a little more information. It seems that the crash
doesn't happen when the task is swiped away, it's
, Andy dev wrote:
Thanks. I'll keep looking for a solution then!
On Friday, July 20, 2012 11:04:13 PM UTC+1, Kostya Vasilyev wrote:
Yep, I can confirm this with my own foreground service on 4.1.1
(Galaxy Nexus).
-- K
2012/7/21 Andy dev andrewpmo...@gmail.com
Anyone at least confirm what
:48 PM UTC+1, Kostya Vasilyev wrote:
2012/7/22 Andy dev andrewpmo...@gmail.com
Kostya, after tracking mine down more, it seems to be exactly the same.
It doesn't actually get killed until I get a broadcast. I'm not sending
them I'm receiving them from things like the SMS service
service com.example.android.app/.service.MainRunningService in 5000ms
To be honest, I've tried to read about the TransactionTooLargeException,
but I don't feel any wiser!
On Friday, July 20, 2012 11:23:11 PM UTC+1, Andy dev wrote:
Thanks. I'll keep looking for a solution
Anyone at least confirm what I'm doing looks ok - even if you don't know
the reason why. Just as a sanity check?
On Thursday, July 19, 2012 10:19:22 PM UTC+1, Andy dev wrote:
I've got a service running (an accessibility service called
MainRunningService) and also use an alarmmanager within
Thanks. I'll keep looking for a solution then!
On Friday, July 20, 2012 11:04:13 PM UTC+1, Kostya Vasilyev wrote:
Yep, I can confirm this with my own foreground service on 4.1.1 (Galaxy
Nexus).
-- K
2012/7/21 Andy dev andrewpmo...@gmail.com
Anyone at least confirm what I'm doing looks
I've got a service running (an accessibility service called
MainRunningService) and also use an alarmmanager within my app.
On ICS when a user pulled up the task list and swiped the app away the
service kept running, but the user interface was cleared from the stack.
On jelly bean I'm
Thanks, I'm aware of that. Is was me who raised it :-)
On Tuesday, July 17, 2012 7:42:15 AM UTC+1, Pent wrote:
Now if I could only find out the reason why since ice cream sandwich
accessibility has caused some phones to start talking to them as soon as
the accessibility service of my app
There's no harm trying :-)
On Tuesday, July 17, 2012 9:53:52 AM UTC+1, Pent wrote:
Ah, you were subtly side-promoting, very good :-)
Pent
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
in the app.
On Sunday, July 15, 2012 11:51:22 PM UTC+1, Andy dev wrote:
I've got an app in the market which uses the accessibility service. For it
to work correctly in Jelly bean I need to add
the android.permission.BIND_ACCESSIBILITY_SERVICE permission to the service
declaration
, Andy dev wrote:
Thanks Mark, your answer was perfect!
After playing around the solution that worked for me was to use the bool
flags with the values-v16 directory and subclassing the service with with a
MainRunningServicePreJellyBean class.
Although compiling didn't complain with using
I tried setting back to a targetSdkVersion of 15, but when I've got that
and my app directs to the accessibly settings page, my app isn't listed in
the accessibility list. As soon as I change it to 16 it shows up.
On Monday, July 16, 2012 11:04:33 PM UTC+1, Mark Murphy (a Commons Guy)
wrote:
I've got an app in the market which uses the accessibility service. For it
to work correctly in Jelly bean I need to add
the android.permission.BIND_ACCESSIBILITY_SERVICE permission to the service
declaration in the android manifest file.
Doing this is fine and gets things working for jelly
Forgot to say my versions in the manifest are set as follows:
android:minSdkVersion=8
android:targetSdkVersion=16
Plus I've updated to the latest android-support-v13.jar file in the project
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
18 matches
Mail list logo
