[Bug] cannot access app floating dialog with DPAD on TV

[Catfriend1]

To Reproduce Steps to reproduce the behavior:

1. Open app
2. Go to app Downloads where apps to update appear
3. Click on one entry with the dpad middle button
4. App flyout/floating dialog with details to that app appears , including the "update" button
5. Try accessing that dialog with the dpad controls on your remote - all input will go below the dialog to the main screens, e.g. you can move left/right through the underlying tabs while the dialog in front of you does nothing.

Expected behavior Dpad controls the app floating dialog when it is shown on top of the main gui.

Screenshots

Relevant information:

• Device: Amazon FireTV Stick 4K
• Android Version: 7.1.1
• ROM: stock amazon
• App's Version: 1.0.5
• Disabled battery optimization for Neo Store? Not possible on tv
• What is your selected installer? Default

Thank you.

[boognish-rising]

I'm surprised this issue hasn't been seconded by anyone, especially given how garbage the Play Store is on Android TV devices. Let this comment serve as a second voice in support of the suggested fix. Currently, one needs either a connected mouse or a mouse emulator app in order to reach the secondary menus that OP speaks of. Even if available, it's far from ideal to require either for simply navigating the app, but many users have neither and are simply unable to use Neo Store, which would be a shame considering ATV devices arguably stand to benefit most from it and despite this shortcoming (bug), it seems well optimized for TVs. In any event, it's still the best F-Droid client to date.

Thanks for your consideration in addressing this issue and of course, thanks to the devs and contributors for providing Neo Store! Your dedication to making it the best F-Droid client is evident immediately upon launch.

Edit - it probably goes without saying, but despite only mentioning Fire TV devices, the issue affects all Android TV devices. Also, for (non-FireTV) aTV devices running 12+, battery optimization can be disabled and has no impact on this issue.

[ghost]

please delete issue

[boognish-rising]

Why does simply closing the issue not suffice here? Ideally, all issues eventually fail to pass the relevancy test (provided the issue they raise was addressed and fixed or the dev/contributor, etc. explained why it wouldn't be addressed), but keeping a record of them is helpful for a number of reasons, e.g., new users to the project can search issues for X regardless of status, or to prevent wasted effort on either side with a clear indicator that Issue #Y was already raised and tackled, etc., but most importantly, for the sake of transparency it is highly discouraged to delete an issue and/or its content (as you've have already done) as a means of indicating relevancy (or lack thereof).

Undoubtedly you attempted to delete the issue yourself and in doing so, discovered it wasn't possible. Now you know why.

Edit - oh, I see. You're looking to nuke all traces of your GitHub persona and its activity entirely. Seems a tad dramatic, but either way, if you no longer have want or need of GitHub, it's well within your rights to delete your account - but for reasons stated, your right to do so should not supercede the right of the projects on which you contributed, documented issues, etc., from maintaining a record (and I take given the value of the one thing you didn't zero out, i.e., follower count (likely bc one can't), you probably touch'd a lot of projects in some capacity (as in the command, not sentimental mushiness). A bit of practical advice, if you do have legitimate reasons for not only deleting your account but for wiping any/all record of it from the platform, I'd contact support. They're probably sympathetic to that sort of thing.