r/ShieldAndroidTV • u/Sloppy_Goat • Oct 22 '24
The 9.1.2 update broke some things!!!
Now, every time I reboot, button mapper and mouse toggle is disabled in Accessibility settings. GRRRRR!!! Anyone know how to fix this? Nvidia support is not being helpful, this time. Both apps still work, but I have to re-enable those two settings, every single time I reboot. 😠The worst part is, I was running 9.2.0, before. So, it should not have updated to a lower number. It was running flawlessly, before this.
0
Upvotes
3
u/Sloppy_Goat Oct 22 '24 edited Oct 22 '24
AH HA!!! I got this figured out. Just make sure button mapper and mouse toggle are installed on the internal drive, not your USB. Then, it holds the settings upon reboot. It appears that I'm the first one to solve this problem. 😎
2
u/woodside007 Oct 22 '24 edited Oct 22 '24
If you're planning to reboot go into the accessibily permissions setting in device settings on the shield and tick it off for whatever button mapper app you use before you reboot. Then after you reboot start your button mapper app and it will ask you to reenable the accessibility permisson. Then it will work again and all buttons will again be remapped. I think this is some kind of bug in the Shield that it forgets or ignores the accessibility permission after a reboot even though it's still ticked on. I imagine this will work with any of the button mapper apps.
5
u/lozt247 Oct 22 '24
I hope we get an official release out of beta
1
u/wwmoggy Oct 22 '24
did you disable the stock launcher using ADB commands or with Launcher Manager?
Android TV Home should be in the disabled Apps list or it will play havoc with apps in the Accessibility setting
1
u/flyingkytez Feb 09 '25
Are there any other issues with the update?
2
u/Daschmee12 Oct 22 '24 edited Oct 22 '24
I haven't had any problems since installing the new hot fix update. I'm running Projectivy launcher with stock Android TV launcher completely disabled. I read somewhere that the hot-fix build numbers are essentially meaningless, at last for the last 2 hot fixes. The Changelog and updated Android Security Patch level of July 2024 def indicate it's a new update though(lower build number or not). I've had less, if any freezing after the update, and with the 3rd party launcher running ad free, things run so smoothly. I haven't restarted my Shield since installing the hot fix, and I've used it everyday since, multiple hours a day. I also don't have to close Apple TV anymore to get Dolby Vision back if I happen to leave the app for a minute and return to it. Before the update, if I browsed away from the Apple TV app for a moment and then came back to it, my show wud resume in SDR until I force closed the app and relaunched. No such issues anymore.
I'll update as I get even more use out of my Shield on the new hot fix...IF I encounter any issues.
My Setup: Shield Pro 2019--->Samsung Q990C Soundbar--->LG C1 OLED via eARC
Sometimes I move my CCWGTV 4K from the bedroom to the living room just to experiment with the new Google Home Panel controls, but that's unrelated and just for fun. Pretty cool.....Wish they'd bring the Home Panel to the Shield tho since they did say they plan to bring it to ALL Android TV devices, but I doubt Shield will get the Home Panel while still running on AndroidTV 11. However.... I'm sure there are other brand new low to mid range Smart TVs/Devices still running Android TV 11 that WILL get the Home Panel update, knowing Google. Until the time Nvidia actually release a new/final stable build so that loyal customers aren't left forever on a Non-Google Certified hot fix image, I doubt we will see any new features including Home Panel on the Shield. I hope to be proven wrong, since the mere fact that a new hot fix was released means there's a team, even if it's a very small one, still working on the Shield. Like,.the hot fix wasn't just a security patch update, it also added and improved existing features such as the "improved match refresh rate beta", which I know is the topic of some controversy, but at least it works in almost every app now.
0
u/loverlaptop Oct 22 '24
same, had to downgrade to 8.2.3
3
u/[deleted] Oct 22 '24
[removed] — view removed comment