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" > android:name=".MyAccessibilityService" > android:enabled="@bool/is_jellybean_or_higher" > android:permission="android.permission.BIND_ACCESSIBILITY_SERVICE" > > > <intent-filter> > <action > android:name="android.accessibilityservice.AccessibilityService" /> > </intent-filter> > </service> > > I can see that this service is being used since the name in Android > accessibility settings is correct. > > However, I'm still getting the problem described here: > > http://code.google.com/p/android/issues/detail?id=33934 > > Don't see any security exceptions in the log. Are others still getting > this 'must turn accessibility off and on after a reboot' problem with > the BIND permission specified ? > > 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 > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
