[mythtv-users] FireTV 4K stick

John Pilkington johnpilk222 at gmail.com
Tue Aug 27 16:37:59 UTC 2019

On 27/08/2019 15:13, Peter Bennett wrote:
> On 8/26/19 4:54 PM, John Pilkington wrote:
>> On 26/08/2019 16:54, Peter Bennett wrote:
>>> On 8/26/19 7:35 AM, John Pilkington wrote:
>>>> I've just gone through the setting backend process again, and got as 
>>>> far as the blue left-hand bar with a lens and an android green logo; 
>>>> then got the Android home screen again...
>>>> ''''''''
>>>> I've tried some more, but even after clearing the app data (272KB), 
>>>> restarting is unpredictable and using the on-screen keyboard to 
>>>> enter the IP address gets discouraging.  This system has 409 
>>>> recordings.
>>> Possibly a problem with more that 128 titles as David Engel had 
>>> encountered. See the other email.
>>> If you can capture a full logcat when the application exits 
>>> unexpectedly I should be able to find the root cause.
>>>> I have had good full-screen playback of DVB-T2 HD content with 
>>>> stereo - but then the picture froze while the audio continued; 
>>>> behaviour seen earlier with frontend and mediacodec.  Playback of HD 
>>>> recordings with multichannel sound just gives the rotating arrow, 
>>>> or, later, an active but non-functional playback-control screen.
>>>> It's difficult to make connections between the logs and events. At 
>>>> one stage the JavaBinder reported that:
>>>> BinderProxy is being destroyed but the application did not call 
>>>> unlinkToDeath to unlink all of its death recipients beforehand. 
>>>> Releasing leaked death recipient 
>>>> com.amazon.whisperlink.android.transport.messenger.TMessengerTransport
>>> This message looks unrelated to the problems with leanback frontend.
>> https://drive.google.com/open?id=1llzEU9b37okqiiNSNvm-JCuOrKZCOKqD
>> was created with 'adb logcat | grep -i myth' and starts before I 
>> expected it to.  It has several false starts and then a few sections 
>> of playback including the HD news where the video freezes.  It might 
>> help...
>> John
> Thanks for that. However giving me the results of grep mythtv does not 
> help to diagnose the problem, since the relevant error lines do not have 
> mythtv in them. Can you send the full log (zipped if necessary)?


This covers only attempts to access the recordings.  They didn't work.

I have a 40 MB clip of the HD with multichannel audio if that would be 


More information about the mythtv-users mailing list