search

theothernt / AerialViews

A screensaver for Android TV devices including Nvidia Shield, Fire TV, and Chromecast with Google TV. Inspired by Apple TV's video screensaver.
GNU General Public License v3.0
418 stars 32 forks source link

Exiting screensaver closes Kodi #104

Closed peat80 closed 1 year ago

peat80 commented 1 year ago

What were you trying to do...

I noticed when i set the kodi screensaver to none it uses the system screensaver and starts as expected.

And what actually happened (ie. describe the bug)...

The problem is if i exit the screen saver kodi restarts. If for example you have paused a movie and then kodi restarts you will loose your progress. If i change the screensaver to the build in pictures one i can get back to kodi without restarting and resume watching. Is this something that could be fixed for AerialViews too?

What kind of device do you have? (eg. Nvidia Shield, Sony TV, etc)...

Nvidia Shield

theothernt commented 1 year ago

This issue was reported previously (via Reddit, I think) and I think it's an issue with Kodi and how it handles being suspended and/or being asked to free up memory.

Aerial Views does use a decent amount of RAM due to video playback being expensive (4K HDR frame buffers) but there's not much I can do about that.

Out of curiosity, what happens if you use the lower resolution, SDR videos - does the issue still occur?

peat80 commented 1 year ago

Tried 1080p h.264 and tunneling disabled and Kodi keeps resuming fine. Have to try more when i have more time but probably the problem is the tunneling. 🤔

peat80 commented 1 year ago

Tunneling seems no problem at all. 🤔

Works: 1080p without hdr h264 and HEVC

Reboots Kodi: 1080p with hdr 4k with and without hdr

theothernt commented 1 year ago

Is this still happening?

peat80 commented 1 year ago

As stated above. HDR and 4K video content closes KODI.

Normal 1080p videos keeps KODI opened.

Tested with version 1.43.

theothernt commented 1 year ago

Thanks, I did remove the option to configure buffering in the current update (1.4.3 vs 1.4.1 on GitHub) which means the player will use a little more memory for local and SMB playback but I don't think that's enough to cause the issue.

I wonder if the issue should be reported to the Kodi devs?

peat80 commented 1 year ago

I think this is a long time issue that exists since a shield firmware update if i remer correctly. I do not know exactly sice when this occurs. Also not really shure if kodi is to blame or the firmware / os of the shield.

Version 1.41 probably also was affected. 🤔

theothernt commented 1 year ago

If there's anything you'd like me to try in the app, let me know, but in the meantime I'll close the issue until there's an update.