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 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: >> >> On Mon, Jul 16, 2012 at 5:00 PM, Streets Of Boston >> > 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 only way this would have an impact is if they are only checking >> that permission for apps with targetSdkVersion 16 or higher. That's >> entirely possible, but it is not documented either way. >> >> Though I should have thought of that -- thanks, Streets! >> >> -- >> Mark Murphy (a Commons Guy) >> http://commonsware.com | http://github.com/commonsguy >> http://commonsware.com/blog | http://twitter.com/commonsguy >> >> Android Training in NYC: http://marakana.com/training/android/ >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
