6
Acknowledged

Use an Android TV Oreo Conditional Detection to apply "workaround" for HUGE UI bug when accessibility is turned on in AutoInput AND Tasker

I'm referencing this:

https://tasker.helprace.com/i426-android-tv-oreo-accessibility-problems-with-tasker

and this

https://tasker.helprace.com/i245-android-tv-oreo-accessibility-problems

Your case for reverting the fix was that it messed with the UI of the Volume Up / Down Indicator. Which, is a good point. BUT - that's only inconvenient on mobile, not on Android TV (it still happens but it's not that inconvenient - though Aaron has a fix for that as well below). Turning Accessibility on for Android TV basically breaks the Homescreen and is not even usable making any accessibility features almost useless on any app.

BUT BUT BUT - here is the fix to that: https://cloudup.com/cnBPalSffz7

AND - you can conditionally only apply the fix to Android TV on Oreo because you can detect that.

So, this SOLVES all of the problems. What do you think?

Follow

5 replies

Votes Newest Oldest
MA

Yes I am dying to use Tasker and Button Mapper on my Nvidia Shield. Button Mapper works with no issues now, I would love for the fix to be included on Tasker too.

Comment
LM

But I've tried that "fixed" apk and there's no difference. It works with the same navigation bug

Comment

I think the one that is floating around, the fix wasn't fully implemented. I remember installing it and it didn't fix the navigation bug. But, there was more to the fix that  either fixed and then reverted or missed. But my outline above should get him through what he needs to fix all Android TV's, he just needs to detect them and apply the fix "on-the-fly."

LM

Hi! Any news? I'm suffering here without autoinput on my mi box) 

Comment

Unfortunately, the fix I outlined above only half-works on the Mi Box (but fully works with the Shield TV) and  explicitly only wants to support FULLY working solutions so we'd need to get him a Mi Box if we wanted that.

Personally, I think a half-fix is better than a no-fix (such as, detect if you're on the Shield TV and conditionally implement the FULL fix, but for all other Android TV's detect that and implement the half fix - since the caveat of the volume indicator staying on the screen 3x longer is almost a non-issue on Android TV...in fact, it might even be preferred).

Is this still being considered, I think it's pretty important to at least acknowledge - especially since you already marked the other two tickets about this as solved, when there is a real solution provided by Aaron that fixes this and everything else caused by Android TV's issue with accessibility. 

If you need a beta tester, I can help with that. :)

Comment

Sorry for the delay. Will need to try and make it work!

Reply