UI Droid and shield 2019 weird behaviour

[mvallevand]

Logs?

[BrettB]

Apparently there is a one time ADB command to change permissions on the shield, to allow Button Mapper to remap those keys.
However, I can not seem to connect to my shield via ADB, and get error of 'unauthenticated ' when trying to connect over network.
From what I have read, one seemingly has to connect first via USB debugging, and then after the user authorizes that initial connection, it then works via network debugging..
I did not have a male to male USB Type A, 3.0 cable, so have not tried it as yet.

Did you try to do the authorization via a network connection? (Even if it is labeled "USB debugging".) I don't have a Shield, so it may be different. But on the Android TV devices that I've used, turning on the "USB Debugging" actually also enables network ADB connections. The first time you try to connect, the Android device pops-up an authorization window, and if you "Allow", then the network connection works. Probably worth a try before purchasing a special USB cable.

[three6zerocool]

Sorry, here are the NPVR logs.
I ran UIdroid with the 3rd party remote, and the selected each of the main menu items.

[three6zerocool]

>did you try to do the authorization via a network connection? (Even if it is labeled "USB debugging".) I don't have a Shield, so it may be different. But on the Android TV devices that I've used, turning on the "USB >Debugging" actually also enables network ADB connections. The first time you try to connect, the Android device pops-up an authorization window, and if you "Allow", then the network connection works. Probably worth a >try before purchasing a special USB cable.

I enabled developer options, then it had USB Debugging and then Network Debugging.
Apparently both need to be enabled, even tho I only wanted to connect via network.

What happens, is that via network connection, it connects, but does not prompt the user to authorize the ADB connection.
On other devices like the Fire Stick/Cube,  a prompt pops up just as you described asking you to authorize the connection attempt.

From what others are telling me, the shield now requires one to connect via USB first, and once authorized, then your good to go via network.
When you enable USB Debugging, it configures the shields first USB 3 port  for debugging purposes.
Won't know til I get a cable, but the comments I have read seem to confirm the steps.

Seemingly it has something to do with Android 11, as all the posts I could find were running earlier version Shield firmware.

[mvallevand]

Sorry, here are the NPVR logs.
I ran UIdroid with the 3rd party remote, and the selected each of the main menu items.

Good I was hoping I handled this scenario which I consider bad firmware.

2024-02-28 20:08:12.122 [DEBUG][213]   hash: NUMPAD_ENTER

In the data folder find the clientstore file for the device and edit it to  Enter Codes are here 
https://learn.microsoft.com/en-us/dotnet...esktop-8.0

You can the change the same key during video playback probably {Ctrl}O and also what happens with a long press the file will update when you press them

You will need to restart the client to reload them by clicking exit with another remote or use an air mouse if you new remote has one

[three6zerocool]

Thank you for those instructions.

Dumb question, when you say 'Data' folder, are you meaning NextPVR's  data folder 'C:\Users\Public\NPVR-data'   on the NextPVR server itself, or on the Shield?

[mvallevand]

NextPVR. In your case edit C:\Users\Public\NPVR-data\clientstore-a2d2f4c66b6aaea7.xml I was a bit lazy since I was doing this on the phone before.


Martin

[three6zerocool]

Update:

I messed around with various key codes from the site you linked to, but after editing that file, I could not seem to get anything to change.
Forgot to mention that I had Button Mapper Pro installed, so not sure if that breaks anything above?

Anyway, a USB cable I had ordered arrived, so I tried enabling USB debugging on the NVidia Shield.
Could not make that work either. It turns out that was only required up to Android version 10.

Then whilst browsing for solutions, I found out that the permissions requestor box granting permission for ADB only appears when you have the NVidia Settings menu open.

So, the Shield does not need USB Debugging turned on at all, just Network Debugging, and the trick was to have Shield settings menu open before establishing network ADB connection from computer.
(sheesh,  what an epic)

So, I managed to gain shell access, and enter the ADB command that Button Mapper needs to override write permissions on the NVidia Shield.
With that enabled, it let me use Button Mapper to remap the numpad_enter to the normal enter, and now UIDroid works perfectly with my 3rd party bluetooth remote.

So, issue resolved.
Thankyou oh so much for those who posted suggestions.

[mvallevand]

You must have down something wrong editing the file or restarting the server but glad you got is sorted out. The clientstore does work and Button Mapper is not required.

Martin