Posts: 13
Joined: Dec 2019
Reputation:
0
I noticed when I updated my Nvidia Shields from 21.0 to 21.1, when I go to my PVR recordings and press the Ok/Select button, it just starts playing the recorded show now where as in 21.0 and prior it would bring up the "info" screen first and then you can hit play (or whatever other function is in that menu). Was this changed on purpose and if so, is there a way I can make it show the info screen first on pressing the ok button again instead of it just playing the recording? I realize I can just press the info button to get to the info screen as well, but I'm used to it being that way with the ok button and it's been bugging me.
Thanks!
Posts: 2,028
Joined: Jan 2015
Reputation:
149
ksooo
Team-Kodi Developer
Posts: 2,028
2024-12-19, 00:44
(This post was last modified: 2024-12-19, 00:45 by ksooo. Edited 1 time in total.)
You should set "Settings -> Media -> Videos -> Default select action" to "Show information".
Posts: 13
Joined: Dec 2019
Reputation:
0
Thanks for the reply, I just checked this and it already was/is set to show information but it still just plays automatically. Minor bug for PVR section maybe?
Posts: 2,028
Joined: Jan 2015
Reputation:
149
ksooo
Team-Kodi Developer
Posts: 2,028
2024-12-19, 10:01
(This post was last modified: 2024-12-19, 10:04 by ksooo. Edited 1 time in total.)
Okay, please post a debug log. Then we can have a look at details. Kodi version, installed addons, skin used etc.
Do you use a custom key map? If so, please post it here .
Posts: 1,975
Joined: Jul 2012
Reputation:
71
I suspect it is this but I need to see why you are losing a resume point.
2024-12-19 19:33:03.579 T:30308 error <general>: AddOnLog: pvr.nextpvr: Duration set to 0
Martin
Posts: 2,028
Joined: Jan 2015
Reputation:
149
ksooo
Team-Kodi Developer
Posts: 2,028
What habens if you disable the custom key mapping?
Posts: 2,028
Joined: Jan 2015
Reputation:
149
ksooo
Team-Kodi Developer
Posts: 2,028
I can reproduce the issue. Confirming it is actually a regression that slipped in with 21.1. I will come up with a fix for 21.2.