Android MiniClient 1.4.0

[sacrament055]

Originally Posted by stuckless

No... In the minicliet app, there is a settings, before you connect to sagetv. In there you control the media key mappings and remote behviour (see my earlier post when someone asked me to explain how remote/key mappings work in the ANdroid client).

Ok, I found the option you mentioned but I don't see anything showing up when I press my select button. It does however function as a select. If I hold it down for 2 seconds it does not initiate the select until I let go. If I tap it it behaves the same way.

I appreciate your looking into it. It appears something has changed from the releases prior to this one.

I also tried turning off the smart remote function as someone else said helped with them but I see no difference.

I can go back to FLIRC with an actual sage remote for full functionality but I think I'll wait until I move to 64bit windows sage. (I currently get random lockups when displaying fanart)

[gclayto]

All of the mmc/encoder/ tuner /never_stop_encoding is set to false. The non-stopping issue only occurs with 1.4 the previous version available in the Amazon store 1.2.8 works as expected.

[stuckless]

Originally Posted by sacrament055

Ok, I found the option you mentioned but I don't see anything showing up when I press my select button. It does however function as a select. If I hold it down for 2 seconds it does not initiate the select until I let go. If I tap it it behaves the same way.

I appreciate your looking into it. It appears something has changed from the releases prior to this one.

I also tried turning off the smart remote function as someone else said helped with them but I see no difference.

I can go back to FLIRC with an actual sage remote for full functionality but I think I'll wait until I move to 64bit windows sage. (I currently get random lockups when displaying fanart)

The behaviour of a long press select will depend on how you configure mini client settings.

First off, unless you are using the limited remote that ships with the Shield/MiBox, don't use "Enable Smart Remote Mappings". ie, if you are using a "normal" remote with media keys, etc, then smart remote should be disabled. Smart Remote is enabled by default, since, it is assumed that this the first remote you'd use with the box.

"Long Press select shows navigation overlay" is by default, on. When enabled a long press on the "SELECT", typically after about 1 second, will show the OSD key overlay. This is used in a pinch to get access to some keys like menu, info, home, etc. Again, if you are using a full remote, you likely don't need this, but it is enabled by default.

Can only test this using the 2 different AndroidTV boxes that I have (Shield and MiBox) with their remotes, and the remote that is emulated in the Android Emulator. All of those function as designed.

Originally Posted by gclayto

All of the mmc/encoder/ tuner /never_stop_encoding is set to false. The non-stopping issue only occurs with 1.4 the previous version available in the Amazon store 1.2.8 works as expected.

I did ask previous (not answered) if this behaviour ONLY happens on LiveTV or does it happen on pre recorded content as well. The miniclient has no concept of LiveTV, so, the behaviour of LiveTV and non LiveTV should be exactly the same. If they are not, then, it could be the MiniClient, possibly sending multiple command when it should only be sending 1... but, it would likely be sending STOP multiple times. Does pressing stop twice cause video to replay??

I don't know what a "CEC" remote is. Is this a brand, can I go somewhere to look at the specs?

As for changes since 1.2.8... lots of have changed. 1.2.8 didn't support key maps, it didn't support key repeats, etc. The entire key handling was rewritten, because in 1.2.8 while it supported smart remote behaviour, it was all over the place, and then when key mapping was added the entire long press / repeat was all over the place, and in tracking down a number of other issues, I decided to consolidate key handing into a 1 place, and extensively take advantage of the key mapping that Josh added. 1.2.8 supported a bug/feature whereby the key press could start in one handler but be completed in a completely different handler. This could result in keys lost or keys being handled in a way that the code didn't expect. It could be, that this "bug" dropped keys that your CEC remote would send, but, now they are being processed, since, I'm not changing key handlers for the same button press.

I also asked if you looked in the sagetv log to see if you can see what it is doing there. Maybe it's showing that the miniclient is sending a "play" or some other command. We might be able to use that to track this down.

I also can't discount that Amazon is doing something here in their version of Android.

If you enable sound effects and you press stop.. do you hear two clicks? (that would signify two commands are being processed, even though you pressed 1 key). The sound effects could be used here to help troubleshoot. It is quite possible that your remote is sending multiple commands for the STOP.

[gclayto]

Sorry, about being slow to respond to some of your questions. I have a lot of different scenarios to test trying to track down the exact source and cause of this feature. I have answered inline all that I know so far.


I did ask previous (not answered) if this behaviour ONLY happens on LiveTV or does it happen on pre recorded content as well. The miniclient has no concept of LiveTV, so, the behaviour of LiveTV and non LiveTV should be exactly the same. If they are not, then, it could be the MiniClient, possibly sending multiple command when it should only be sending 1... but, it would likely be sending STOP multiple times. Does pressing stop twice cause video to replay??

I understand how Sagetv works that's what makes this problem so odd. Live video starts as a default now. When miniclient starts it will start playing "live" video, and it cannot be stopped. I have also discovered through further testing that when playing recorded video and stop it live video will then start.
When you press the stop key it will stop and then start right back up. This only happens on the FireTV. When using Miniclient on my Chromebook or pixel phone everything works normally. However, I am not able to bring up the OSD on my phone now and have never figured how to do it on the Chromebook on any of the versions.


I don't know what a "CEC" remote is. Is this a brand, can I go somewhere to look at the specs?

Consumer Electronics Control (CEC) is a standard to pass the input from the TV remote to individual devices through the HDMI connection. Eliminating the need for a universal remote. Most modern TVs support this.

As for changes since 1.2.8... lots of have changed. 1.2.8 didn't support key maps, it didn't support key repeats, etc. The entire key handling was rewritten, because in 1.2.8 while it supported smart remote behaviour, it was all over the place, and then when key mapping was added the entire long press / repeat was all over the place, and in tracking down a number of other issues, I decided to consolidate key handing into a 1 place, and extensively take advantage of the key mapping that Josh added. 1.2.8 supported a bug/feature whereby the key press could start in one handler but be completed in a completely different handler. This could result in keys lost or keys being handled in a way that the code didn't expect. It could be, that this "bug" dropped keys that your CEC remote would send, but, now they are being processed, since, I'm not changing key handlers for the same button press.

I have sideloaded the1.3 versions on the FireTV this "live" tv behavior just started with 1.4.x versions. I will sideload the latest 1.3.x version and double check, I frankly lost track of the last 1.3.x version I was using.


I also asked if you looked in the sagetv log to see if you can see what it is doing there. Maybe it's showing that the miniclient is sending a "play" or some other command. We might be able to use that to track this down.

I will attempt to capture this for you and post the logs. How do I capture them and where are they found?


I also can't discount that Amazon is doing something here in their version of Android.

Understood, this is not a deal killer, just annoying that you cannot stop the video. You can pause you just can't stop it.

If you enable sound effects and you press stop.. do you hear two clicks? (that would signify two commands are being processed, even though you pressed 1 key). The sound effects could be used here to help troubleshoot. It is quite possible that your remote is sending multiple commands for the STOP.

I only hear one click. Good idea, but I'm afraid it did not reveal anything.

[stuckless]

I've uploaded a dev build
https://bintray.com/opensagetv/saget...ient/1.4.3-dev

This dev build has 2 debug options in the media key mapping areas, debug key presses and debug sage commands. Enable both of those and then see what happens when you press stop when the video is playing.

This will at least debug what your remote is sending and what the miniclient is sending to sagetv.

FYI, when these debug options are enabled, all new information is displayed above the old. (ie, new keys/commands are logged at the top, older keys fall off at the bottom).

[stuckless]

Originally Posted by gclayto

However, I am not able to bring up the OSD on my phone now and have never figured how to do it on the Chromebook on any of the versions.

So, on a phone a swipe off the left edge to the right should bring up the OSD. This can be done with a mouse as well (at least in the emulator), so I suspect that a chromebook might work using touch/mouse off the left edge.

But, if you check out the 1.4.3-dev-2 beta, you can configure tap corner hotpots, so, you can just click in the bottom left corner of the screen and it will bring up the OSD.

https://forums.sagetv.com/forums/showthread.php?t=65815