Quick Bars 1.3.3 Remote Mapping stopped working

[AlanMW]

I noticed today my quick bars were not responding to my mapped keys, when I dove into the settings to try and set them again I noticed I was unable to set them to anything. I tried adjusting every setting I could and when through the troubleshooting steps on https://quickbars.app/troubleshooting, but none of them ended up fixing it.

What did was making a backup, and reinstalling the app.

Not sure if this was a bug on my end or an issue with QuickBars, just wanted to post this for awareness. I am using an Onn 4k with the latest remote firmware (2.44).

[Trooped]

Hey @AlanMW,
What do you mean by this? What settings? I really need more information:

when I dove into the settings to try and set them again I noticed I was unable to set them to anything.

Did it happen right after the update to v1.3.3?

If yes - it's something that I've heard about for a while - that QuickBars has these bug with some Android TV devices after a software update.
This could be an interesting workaround, but I don't want it to ruin the experience for most of the users, which definitely don't experience this bug.

If not - I'm really not sure what could cause it - but I've been mostly hearing this reports from Nvidia Shields (which I'm also an owner of, and I don't encounter this problem).

I'd love if more people could chime in with their experiences, and if anyone else has a suggestion - I'm all ears.

[AlanMW]

By that I meant I would go into the button remap setting and I was unable to create a new one or edit my existing ones. None of the buttons on my remote were registering.

And yes, it appeared to happen right after the update, but I can't say for sure.

[VGrol]

As per request, I'll merge my initial thread here. I initially thought this was a seperate issue, so apologies.
In terms of hardware, I've seen one other instance, beside my own, where the issue seems to occur in a CCWGTV.

It's quite likely it is tied to updates, as my last 2 instances have been around ~mid november and just earlier in march, though 1.3.2 definitely did not cause any issues for me. Though I almost want to say my current 'reset' happened a few days before 1.3.3 was released.
Regardless it warrants more investigation/keeping track.

What do you mean by this? What settings? I really need more information:

In my case this was the remapping menu, where quickbars prompts you to press the key you want to bind. No key will end up being bindable. No errors happen, it just doesn't register anything when you press the keys.

Original Post: Quickbar stops functioning - requiring reinstall #28

Android TV Hardware

Chromecast CCWGTV 4k

QuickBars Version

atleast from 1.3 onwards through 1.3.3

Home Assistant Core Version

2026.3.2

What is happening?

There appears to be a rather odd bug that seems to randomly appear after having a successful, functioning setup of Quickbars.
I haven't found a particular trigger, I'm not sure if it coincides with the 1.30 release or this is just a coincidence, but around this release the app has stopped functioning for me entirely. I've not had any issues until 1.3 at least.

In particular this means; The app is still launchable, I can still interact with it like normal but the button mapping no longer works and any previously mapped buttons will still be visible in the app, though they will perform their 'old' function.
It becomes impossible to bind any new buttons in the binding menu.

So far I've attempted to kill the app, reenable the accessibility service, reboot the device, disable all other accessibility services but nothing seems to fix it. Battery saving is also disabled.
I'm now on the fourth 'iteration' of this bug. Sometimes it buys me a few months, other times it's a matter of days.
I cannot seem to find a trigger, power cycling doesn't seem to be it. It just happens 'randomly' and at that point the only solution is a reinstall.

Adding a second button corresponding to a second bar results in both being affected at the same time.
The app does not complain about missing accessibility settings or anything of the sort when this happens either.
Reloading a backup does work, even if the backup was made after the 'bug' goes 'active'.

System details
And I'm using Projectivity Launcher as my Launcher V4.68. (Though disabling it didn't seem to fix anything)
I've bound button 4 (the Netflix button), but when the issue arrises I can no longer bind any of the remote buttons.
Android OS Sec pstch: Oct 1st, 2025
Kernel Version: 5.15.170-android14-11-gf4a1f03072af
Android TV OS build: UTTC.250917.004.14193937

Screenshots or Video

No response

Upload Configuration or Logs

No response

Relevant Logs

No response

Final Checks

• I have checked the entire troubleshooting section on the website, and tried all relevant steps.
• I have searched in the Q&A discussions if someone asked this question
• I have restarted both my Android TV and Home Assistant instance.

[KF042020]

I've experienced the same on my Nvidia Shield 2017. Tried all tips with zero success. Had to reinstall and restore settings from backup. Even clearing data (not cache) didn't help. Now it's working again. I've got 2019 version remote and successfully remapped Netflix button.