GavinAshford 1 Posted February 13, 2018 Posted February 13, 2018 I'm on the beta app on my Pixel 2 XL and since around the time implementation of PiP was released, when a video finishes playing and emby exits the media playback screen to return to the series page the screen remains 'active' and doesn't allow the screen to timeout/dim/lock. It's like it still thinks it's playing a video and so keeps the screen on. I've tried disabling the PiP permission but that doesn't make a difference. There have been a couple of instances I've fallen asleep to a video playing and woken up several hours later with my screen still on and phone unlocked, needless to say the battery has drained somewhat in that time too. Previously, on an earlier version, at the end of playback the screen would be 'released' from media playback and 'allowed' to turn off after X minutes, and the phone would lock. Is it possible to get this functionality back? Sorry if I've noticed the correct/accurate terminology to describe the issue - let me know if I can better explain!?
Luke 42078 Posted February 14, 2018 Posted February 14, 2018 Hi @@GavinAshford, does this happen if you manually stop the video by pressing the back button? Or is it only when you play the video to completion? Thanks.
GavinAshford 1 Posted February 16, 2018 Author Posted February 16, 2018 Hey @@Luke pressing the back button to exit media playback works as expected. Also the screen brightness visibly changes from whatever it was set on the video playback and dims/brightens to the system brightness. This doesn't happen when the video ends by itself, but it does change brightness on the next button input. I think this adds more evidence that it seems to still think it's playing a video after coming to the end of a video on its own.
Luke 42078 Posted February 16, 2018 Posted February 16, 2018 Ok, it's resolved for the next release of the app, thanks.
GavinAshford 1 Posted February 16, 2018 Author Posted February 16, 2018 Awesome, thanks! I'll report back after receiving the next update
GavinAshford 1 Posted February 17, 2018 Author Posted February 17, 2018 @@Luke I got the update this morning and I can confirm this is resolved. Much appreciated!
rechner123 12 Posted March 31, 2018 Posted March 31, 2018 Which version do you use? I have 2.9.92 on my Galaxy Tab A 2016 with the same problem.
rechner123 12 Posted April 10, 2018 Posted April 10, 2018 what version do you use actually? the problem still persists with my tablet?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now