Alright, allow me to respond:After a couple of days of using this on my 2019 pro here is what doesn't work
Menu button (hamburger icon) on any controller/gamepad
Recents (double click home button) on any controller/gamepad
AI Upscaling (this should not be expected anyways, it's proprietary nvidia code)
If I remember correctly, reading through the requirements to get a build marked as official something simple as the 3 primary buttons used to navigate working correctly is a primary consideration. I'm confused as to how this build was allowed in, this is clearly not usable in it's current form. No multitasking and no way to enter settings without exiting your current app makes this completely unusable. I thought at first it was because I was using my gamepad but even using the stock controller has the same problems. Other than the very debilitating input issues everything else seems to work flawlessly.
I would not recommend this to anyone until these input issues are addressed.
thanks for the reply and thanks for the work yall have done.Alright, allow me to respond:
Menu button - it's in progress, even just merged a KeyInterceptor for ATV devices recently.
Recents - Google has disabled and enabled this on ATV repeatedly over it's lifetime - in the case of Android 10, we haven't gone to the effort to re-enable it when, even the generic AOSP TV targets don't!
AI upscaling - proprietary as hell - if someone gets it working, I applaud them, truly.
Charter: - this meets charter in it's entirety. Not being able to overlay settings over the current app is not at all a "required feature" - you can still use all of settings, and multitasking on a TV device? idk, my Nexus Player builds haven't had that for... years, and no one has ever brought it up.
This meets charter, and it perfectly stable usable.
Now, do we plan to make the settings button work? Yes.
Will we probably enable recents once the UI works again? Probably.
Charter doesn't really say any of that - it has specific requirements of support. Which we meet.thanks for the reply and thanks for the work yall have done.
the page i read said the build has to work like or better than stock, regardless of what other devices are doing, but i understand the issue with recents on android 10. i didn't know that. im just frustrated because i expected this to work better than stock because it's official but it is lacking in what i consider basic navigation that stock has, regardless of why. it's a hassle getting this thing out and flashing it and now i have to go back to stock.
nvidia has lazy developers, it's amazing someone not getting paid has had more development into their product more than they have. im excited to see these features implemented, or maybe updated to android 11 where recents has been reimplemented (if it has)?
That's news to me. The remotes can sometimes take a while to reconnect, but I've had the exact same reconnect lag on stock, so I don't consider that a regression. Might even be the remote itself. Is that the issue or something else?
When you say 'pair', you mean the remote paired during first boot doesn't reconnect after a reboot? Or new accessories can't be paired? Or both.
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: