I've setup a new accessibility service with the BIND permission:
service
android:label=Tasker - JB
android:name=.MyAccessibilityService
android:enabled=@bool/is_jellybean_or_higher
I find it works, but only if declaring the settings in xml and not in code.
On 30 Jul 2012 10:57, Pent supp...@apps.dinglisch.net wrote:
I've setup a new accessibility service with the BIND permission:
service
android:label=Tasker - JB
I find it works, but only if declaring the settings in xml and not in code.
Oh no... the user needs to be able to specify the settings...
Thanks for the info in any case.
Pent
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
I know it's not ideal for my app either and means there's lots of
additional activity taking place because I can't restrict the package
monitoring as much as i would like.
On 30 Jul 2012 12:30, Pent supp...@apps.dinglisch.net wrote:
I find it works, but only if declaring the settings in xml and
Another alternative would be to set up a pair of boolean resources
(bools.xml). One, is_jelly_bean, would be set to true in -v16 and
false in the default set. The other, is_not_jelly_bean, would be set
to false in -v16 and true in the default set. Then, have two service
elements in the
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 is enabled even though talkback is off
and I don't use any TTS in the app.
In case you didn't see it:
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
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
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
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 the same service class
I'm just guessing here: What if you set thee android:targetSdkVersion to a
value less than 16?
On Monday, July 16, 2012 2:43:47 PM UTC-4, 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
I think that would have been ok, but I wanted to use some new features from
v16
On Monday, July 16, 2012 7:51:07 PM UTC+1, Streets Of Boston wrote:
I'm just guessing here: What if you set thee android:targetSdkVersion to
a value less than 16?
On Monday, July 16, 2012 2:43:47 PM UTC-4,
That should not be a problem. You can set the android:targetSdkVersion to a
different (lower or higher) version that the one you are compiling/building
against.
E.g. you can setup your developement/Eclipse environment to compile and
build against api-level 16 and set targetSdkVersion to 15 (or
On Mon, Jul 16, 2012 at 5:00 PM, Streets Of Boston
flyingdutc...@gmail.com wrote:
The targetSdkVersion value only determines the compatibility mode of your
app (depending on the device it is running on), which influences the default
theme or your app, default behavior of permissions, etc.
The
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:
Ah, I guess that's how the compatibility is done for accessibility features
of v16 running on lower-versioned Android devices...
It was worth a try :-)
Back to Mark's solutions :-)
On Monday, July 16, 2012 6:23:51 PM UTC-4, Andy dev wrote:
I tried setting back to a targetSdkVersion of 15, but
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.
17 matches
Mail list logo
