Android TV (Philips) "stop button" and "jump to/timeskip"

[josch.hh 2]

Hi,

2 questions:

1.) The stop button on the remote of my Philips 65pus8601 has no effect when using the emby android tv app.

Only the "back" button does what i was normally expecting from the "stop".

 

2.) Within the andriod tv app i would like to use the movie "progress bar" to jump to a specific point of time in the movie.

With many tv's internal usb/dlna player i can simple navigate to this "progress bar" and use the cursor left/right buttons to move to a specifc point on the bar and then press ok/enter to let the movie playback jump to this point. -> Is this possible in implement in the emby app?

 

[AaronG85 48]

Love point 2 think this would be an amazing addition. 

[ebr 16169]

The Android TV device remotes do not have a stop button on them so the app isn't currently responding to it.  If possible, map your stop button to 'back'.

[josch.hh 2]

The Android TV device remotes do not have a stop button on them so the app isn't currently responding to it.  If possible, map your stop button to 'back'.

 

Ah ok, but i don't think i can map any buttons in the Philips TV... :-(

 

What about the "time skip" request? Do you think this can be possible?

[ebr 16169]

The best suggestion I have for you right now on the time skip is to use chapters.

[ebr 16169]

Assuming your TV is sending the proper key code to the app, the next version should respond to your stop button.

[ebr 16169]

This version is now live.  Please let me know if your stop button works. 

[josch.hh 2]

This version is now live.  Please let me know if your stop button works. 

 

Thanks for the effort, but my trial period of the app is over, so i can't test it anymore.

 

... and as Luke didn't solve the DLNA issue with Philips TV's (and what i read also with many other TV's) as posted here, i will NOT spend any money in emby.

To be honest i am very disapointed because emby is the only software with DLNA server integrated that is NOT working even with basic DLNA/UPNP functions with many TV's. Even the simplest software like the Intel upnp tool kit or minidlna is able to feed nearly all TV's... and the excuse to not have a TV's of all the brands to test it can't be the point. I am sure the other coders of other DLNA server software didn't had all TV brands to test at home.

 

I hope it will be solve, because emyb is a cool piece of software... but i really dont understand why it is so weak concerning this point.

Edited June 2, 2016 by josch.hh

[Luke 42077]

Thanks for the effort, but my trial period of the app is over, so i can't test it anymore.

 

... and as Luke didn't solve the DLNA issue with Philips TV's (and what i read also with many other TV's) as posted here, i will NOT spend any money in emby.

To be honest i am very disapointed because emby is the only software with DLNA server integrated that is NOT working even with basic DLNA/UPNP functions with many TV's. Even the simplest software like the Intel upnp tool kit or minidlna is able to feed nearly all TV's... and the excuse to not have a TV's of all the brands to test it can't be the point. I am sure the other coders of other DLNA server software didn't had all TV brands to test at home.

 

I hope it will be solve, because emyb is a cool piece of software... but i really dont understand why it is so weak concerning this point.

 

because every dlna device has to be tested individually and I apologize that we don't have a philips on hand for testing.

[josch.hh 2]

because every dlna device has to be tested individually and I apologize that we don't have a philips on hand for testing.

 

and as already mentioned -> I am sure all the other coders of other DLNA server software don't have all brands as well. So this is NO excuse.

 

For exmaple:

Justin Maggard is the one coding minidlna... you think his house is full of TV's from every brand...?

Petr Nejedly is the one coding serviio.. same for him i think ;-).

Edited June 2, 2016 by josch.hh

[Luke 42077]

and as already mentioned -> I am sure all the other coders of other DLNA server software don't have all brands as well. So this is NO excuse.

 

For exmaple Justin Maggard is the one coding minidlna... you think his house is full of TV's from every brand...?

 

I'm sorry but this IS a valid reason because all of the devices has their own set of quirks and problems. Generally what happens is people step up and help identify the problem with their brand of TV. You have done a great job of providing logs but unfortunately that doesn't indicate the issue. Getting to the root of the problem is generally a case of trial and error, trying different things to find out what resolves it. When community members have been capable of doing that, it has led to many improvements for the brand of devices they own.

[josch.hh 2]

I'm sorry but this IS a valid reason because all of the devices has their own set of quirks and problems. Generally what happens is people step up and help identify the problem with their brand of TV. You have done a great job of providing logs but unfortunately that doesn't indicate the issue. Getting to the root of the problem is generally a case of trial and error, trying different things to find out what resolves it. When community members have been capable of doing that, it has led to many improvements for the brand of devices they own.

 

Thanks for your effort, but i can't image that you only get devices running with the help of the community...

For exmaple i don't think that intel for the upnp toolkit tested all possible tv's. i am sure that their upnp server implementation as part of the toolkit is a default one.

On the other side i followed the development of minidlna some years and adding new decives by the help of users was really the exception.

Edited June 2, 2016 by josch.hh