Mailing List Archive

Android frontend for FireTv cube 4k?
Hi,

I tried installing the android mythtv frontend from the mythtv wiki Android
page on an Amazon FireTV cube 4k but it does not work. The installation of
the app went well (I used the 32bit 20190124 version) but when I launch the
app, the screen displays the MythTV logo for a second and then goes black
and nothing else happens.

Is there anything I can do to make this work? Looking at the amazon page
for the device, it uses a different gpu than the firestick4k (Mali450 mp3
for the cube vs a IMG GE8300 for the stick) so maybe this will not work.

Any suggestion for things to try would be appreciated, thanks,

John
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 02/02/2019 22:19, John Lundell wrote:
> Hi,
>
> I tried installing the android mythtv frontend from the mythtv wiki
> Android page on an Amazon FireTV cube 4k but it does not work. The
> installation of the app went well (I used the 32bit 20190124 version)
> but when I launch the app, the screen displays the MythTV logo for a
> second and then goes black and nothing else happens.
>
> Is there anything I can do to make this work? Looking at the amazon page
> for the device, it uses a different gpu than the firestick4k (Mali450
> mp3 for the cube vs a IMG GE8300 for the stick) so maybe this will not work.
>
> Any suggestion for things to try would be appreciated, thanks,
>
> John

You might find the adb logging facility useful. see 'adb --help' and
this link from Peter. I suppose there perhaps should be some kind of
health warning here...

http://lists.mythtv.org/pipermail/mythtv-users/2018-November/398371.html

> As long as you have developer mode set on your android/fire device and adb on your computer, run this to see the mythfrontend log:
> adb connect <device-name-or-ip-address>
> adb logcat mfe:D *:S |& tee /tmp/android.log
> This displays it on the screen and simultaneously logs it to /tmp/android.log

John P
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
> On 02/02/2019 22:19, John Lundell wrote:
>> Hi,
>>
>> I tried installing the android mythtv frontend from the mythtv wiki
>> Android page on an Amazon FireTV cube 4k but it does not work. The
>> installation of the app went well (I used the 32bit 20190124 version)
>> but when I launch the app, the screen displays the MythTV logo for a
>> second and then goes black and nothing else happens.
>>
>> Is there anything I can do to make this work? Looking at the amazon page
>> for the device, it uses a different gpu than the firestick4k (Mali450
>> mp3 for the cube vs a IMG GE8300 for the stick) so maybe this will not
>> work.
>>
>> Any suggestion for things to try would be appreciated, thanks,
>>
>> John
>
> You might find the adb logging facility useful. see 'adb --help' and
> this link from Peter. I suppose there perhaps should be some kind of
> health warning here...
>
> http://lists.mythtv.org/pipermail/mythtv-users/2018-November/398371.html
>
>> As long as you have developer mode set on your android/fire device and
>> adb on your computer, run this to see the mythfrontend log:
>> adb connect <device-name-or-ip-address>
>> adb logcat mfe:D *:S |& tee /tmp/android.log
>> This displays it on the screen and simultaneously logs it to
>> /tmp/android.log
>

I'm having the same blank screen issue on a FireTV Pendant with
mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk

I know remote access works as I've got a couple of remote frontends.

I tried the recommended logging commands and got the following

04-13 13:02:54.091 3665 3704 E mfe : mythfrontend version: fixes/30
[v30.0-28-g60cfb7c05ae] www.mythtv.org
04-13 13:02:54.092 3665 3704 E mfe : Qt version: compile: 5.10.1,
runtime: 5.10.1
04-13 13:02:54.092 3665 3704 I mfe : Enabled verbose msgs: general
04-13 13:02:54.093 3665 3704 I mfe : Setting Log Level to LOG_INFO
04-13 13:02:54.093 3665 3704 I mfe : Added logging to the console
04-13 13:02:54.094 3665 3704 I mfe : Using runtime prefix =
/data/app/org.mythtv.mythfrontend-1/lib/arm
04-13 13:02:54.094 3665 3704 I mfe : Using configuration directory =
/data/user/0/org.mythtv.mythfrontend/files
04-13 13:02:54.095 3665 3704 I mfe : Assumed character encoding:
04-13 13:02:54.096 3665 3704 W mfe : This application expects to be
running a locale that specifies a UTF-8 codeset, and many features may
behave improperly with your current language settings. Please set the
LC_ALL or LC_CTYPE, and LANG variable(s) in the environment in which this
program is executed to include a UTF-8 codeset (such as 'en_US.UTF-8').
04-13 13:02:54.196 3665 3704 I mfe : Loading en_us translation for
module mythfrontend
04-13 13:02:54.197 3665 3704 E mfe : DBHostName is not set in
config.xml
04-13 13:02:54.197 3665 3704 E mfe : DBHostName is not set in
config.xml
04-13 13:02:54.197 3665 3704 I mfe : Empty LocalHostName. This is
typical.
04-13 13:02:54.198 3665 3704 I mfe : Using a profile name of:
'android-b66c64d81c55247f' (Usually the same as this host's name.)
04-13 13:02:54.198 3665 3704 I mfe : Start up testing connections.
DB localhost, BE , attempt 0, status dbAwake, Delay: 2000
04-13 13:02:55.200 3665 3704 I mfe : Start up failure. host
localhost, status dbAwakeFail
04-13 13:02:55.300 3665 3704 E mfe : DB Error
(StorageGroup::StorageGroup()):
04-13 13:02:55.300 3665 3704 E mfe : Query was:
04-13 13:02:55.300 3665 3704 E mfe :
04-13 13:02:55.300 3665 3704 E mfe : Driver error was [1/]:
04-13 13:02:55.300 3665 3704 E mfe : Driver not loaded
04-13 13:02:55.300 3665 3704 E mfe : Database error was:
04-13 13:02:55.300 3665 3704 E mfe : Driver not loaded
04-13 13:02:55.401 3665 3704 I mfe : UDPListener: Enabling
04-13 13:02:55.402 3665 3704 I mfe : Binding to UDP 0.0.0.0:0
04-13 13:02:55.403 3665 3704 I mfe : Binding to UDP [::]:0
04-13 13:02:55.403 3665 3704 I mfe : Using Frameless Window
04-13 13:02:55.404 3665 3704 I mfe : Using Full Screen Window
04-13 13:02:55.405 3665 3704 I mfe : UI Screen Resolution: 1920 x 1080
04-13 13:02:55.405 3665 3704 W mfe : OpenGL: Could not determine
whether Sync to VBlank is enabled.
04-13 13:02:55.406 3665 3704 I mfe : OpenGL ES2 forced for Android
04-13 13:02:55.407 3665 3704 I mfe : OpenGL painter using existing
OpenGL context.
04-13 13:02:55.508 3665 3704 I mfe : OpenGL2ES: Found default
functionality.
04-13 13:02:55.508 3665 3704 I mfe : OpenGL2ES: Framebuffer Objects
available.
04-13 13:02:55.509 3665 3704 I mfe : OpenGL2ES: OES mapbuffer
available.
04-13 13:02:55.509 3665 3704 I mfe : OpenGL2ES: Vendor : ARM
04-13 13:02:55.510 3665 3704 I mfe : OpenGL2ES: Renderer: Mali-450 MP
04-13 13:02:55.510 3665 3704 I mfe : OpenGL2ES: Version : OpenGL ES 2.0
04-13 13:02:55.510 3665 3704 I mfe : OpenGL2ES: Max texture size:
4096 x 4096
04-13 13:02:55.511 3665 3704 I mfe : OpenGL2ES: Max texture units: 8
04-13 13:02:55.511 3665 3704 I mfe : OpenGL2ES: Direct rendering: Yes
04-13 13:02:55.512 3665 3704 I mfe : OpenGL2ES: Extensions
Supported: 1c09
04-13 13:02:55.512 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.513 3665 3704 E mfe : 0:5: S0032: no default
precision defined for variable
04-13 13:02:55.513 3665 3704 E mfe : #version 100
04-13 13:02:55.513 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.513 3665 3704 E mfe : precision highp float;
04-13 13:02:55.513 3665 3704 E mfe : #endif
04-13 13:02:55.513 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.513 3665 3704 E mfe : void main(void)
04-13 13:02:55.513 3665 3704 E mfe : {
04-13 13:02:55.513 3665 3704 E mfe : gl_FragColor = v_color;
04-13 13:02:55.513 3665 3704 E mfe : }
04-13 13:02:55.513 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.514 3665 3704 E mfe : 0:6: S0032: no default
precision defined for variable
04-13 13:02:55.514 3665 3704 E mfe : #version 100
04-13 13:02:55.514 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.514 3665 3704 E mfe : precision highp float;
04-13 13:02:55.514 3665 3704 E mfe : #endif
04-13 13:02:55.514 3665 3704 E mfe : uniform sampler2D s_texture0;
04-13 13:02:55.514 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.514 3665 3704 E mfe : varying vec2 v_texcoord0;
04-13 13:02:55.514 3665 3704 E mfe : void main(void)
04-13 13:02:55.514 3665 3704 E mfe : {
04-13 13:02:55.514 3665 3704 E mfe : gl_FragColor =
texture2D(s_texture0, v_texcoord0) * v_color;
04-13 13:02:55.514 3665 3704 E mfe : }
04-13 13:02:55.515 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.515 3665 3704 E mfe : 0:5: S0032: no default
precision defined for variable
04-13 13:02:55.515 3665 3704 E mfe : #version 100
04-13 13:02:55.515 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.515 3665 3704 E mfe : precision highp float;
04-13 13:02:55.515 3665 3704 E mfe : #endif
04-13 13:02:55.515 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.515 3665 3704 E mfe : varying vec2 v_position;
04-13 13:02:55.515 3665 3704 E mfe : uniform mat4 u_parameters;
04-13 13:02:55.515 3665 3704 E mfe : void main(void)
04-13 13:02:55.515 3665 3704 E mfe : {
04-13 13:02:55.515 3665 3704 E mfe : float dis =
distance(v_position.xy, u_parameters[0].xy);
04-13 13:02:55.515 3665 3704 E mfe : float mult =
smoothstep(u_parameters[0].z, u_parameters[0].w, dis);
04-13 13:02:55.515 3665 3704 E mfe : gl_FragColor = v_color *
vec4(1.0, 1.0, 1.0, mult);
04-13 13:02:55.515 3665 3704 E mfe : }
04-13 13:02:55.516 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.516 3665 3704 E mfe : 0:5: S0032: no default
precision defined for variable
04-13 13:02:55.517 3665 3704 E mfe : #version 100
04-13 13:02:55.517 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.517 3665 3704 E mfe : precision highp float;
04-13 13:02:55.517 3665 3704 E mfe : #endif
04-13 13:02:55.517 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.517 3665 3704 E mfe : varying vec2 v_position;
04-13 13:02:55.517 3665 3704 E mfe : uniform mat4 u_parameters;
04-13 13:02:55.517 3665 3704 E mfe : void main(void)
04-13 13:02:55.517 3665 3704 E mfe : {
04-13 13:02:55.517 3665 3704 E mfe : float dis =
distance(v_position.xy, u_parameters[0].xy);
04-13 13:02:55.517 3665 3704 E mfe : float rad = u_parameters[0].z;
04-13 13:02:55.517 3665 3704 E mfe : float wid = u_parameters[0].w;
04-13 13:02:55.517 3665 3704 E mfe : float mult = smoothstep(rad
+ wid, rad + (wid - 1.0), dis) * smoothstep(rad - (wid + 1.0), rad - wid,
dis);
04-13 13:02:55.517 3665 3704 E mfe : gl_FragColor = v_color *
vec4(1.0, 1.0, 1.0, mult);
04-13 13:02:55.517 3665 3704 E mfe : }
04-13 13:02:55.517 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.518 3665 3704 E mfe : 0:5: S0032: no default
precision defined for variable
04-13 13:02:55.518 3665 3704 E mfe : #version 100
04-13 13:02:55.518 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.518 3665 3704 E mfe : precision highp float;
04-13 13:02:55.518 3665 3704 E mfe : #endif
04-13 13:02:55.518 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.518 3665 3704 E mfe : varying vec2 v_position;
04-13 13:02:55.518 3665 3704 E mfe : uniform mat4 u_parameters;
04-13 13:02:55.518 3665 3704 E mfe : void main(void)
04-13 13:02:55.518 3665 3704 E mfe : {
04-13 13:02:55.518 3665 3704 E mfe : float dis =
abs(u_parameters[0].x - v_position.x);
04-13 13:02:55.518 3665 3704 E mfe : float y = u_parameters[0].y
* 2.0;
04-13 13:02:55.518 3665 3704 E mfe : float mult = smoothstep(y,
y - 0.1, dis) * smoothstep(-0.1, 0.0, dis);
04-13 13:02:55.518 3665 3704 E mfe : gl_FragColor = v_color *
vec4(1.0, 1.0, 1.0, mult);
04-13 13:02:55.518 3665 3704 E mfe : }
04-13 13:02:55.518 3665 3704 E mfe : OpenGL2: Failed to compile shader.
04-13 13:02:55.519 3665 3704 E mfe : 0:5: S0032: no default
precision defined for variable
04-13 13:02:55.519 3665 3704 E mfe : #version 100
04-13 13:02:55.519 3665 3704 E mfe : #ifdef GL_FRAGMENT_PRECISION_HIGH
04-13 13:02:55.519 3665 3704 E mfe : precision highp float;
04-13 13:02:55.519 3665 3704 E mfe : #endif
04-13 13:02:55.519 3665 3704 E mfe : varying vec4 v_color;
04-13 13:02:55.519 3665 3704 E mfe : varying vec2 v_position;
04-13 13:02:55.519 3665 3704 E mfe : uniform mat4 u_parameters;
04-13 13:02:55.519 3665 3704 E mfe : void main(void)
04-13 13:02:55.519 3665 3704 E mfe : {
04-13 13:02:55.519 3665 3704 E mfe : float dis =
abs(u_parameters[0].x - v_position.y);
04-13 13:02:55.519 3665 3704 E mfe : float x = u_parameters[0].y
* 2.0;
04-13 13:02:55.519 3665 3704 E mfe : float mult = smoothstep(x,
x - 0.1, dis) * smoothstep(-0.1, 0.0, dis);
04-13 13:02:55.519 3665 3704 E mfe : gl_FragColor = v_color *
vec4(1.0, 1.0, 1.0, mult);
04-13 13:02:55.519 3665 3704 E mfe : }
04-13 13:02:55.520 3665 3704 I mfe : OpenGL: Initialised
MythRenderOpenGL
04-13 13:02:55.520 3665 3704 I mfe : Platform name is android
04-13 13:02:55.520 3665 3704 I mfe : MythUIHelper: Pruning cache
directory: /data/user/0/org.mythtv.mythfrontend/files/cache/remotecache
04-13 13:02:55.521 3665 3704 I mfe : MythUIHelper: Kept 0 files,
deleted 0 files, stat error on 0 files
04-13 13:02:55.521 3665 3704 I mfe : MythUIHelper: Pruning cache
directory: /data/user/0/org.mythtv.mythfrontend/files/cache/thumbnails
04-13 13:02:55.522 3665 3704 I mfe : MythUIHelper: Kept 0 files,
deleted 0 files, stat error on 0 files
04-13 13:02:55.922 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.922 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 26
04-13 13:02:55.922 3665 3704 E mfe : Name: 'basemedium' Type:
'fontdef'
04-13 13:02:55.923 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.923 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 30
04-13 13:02:55.923 3665 3704 E mfe : Name: 'basemediumbold' Type:
'fontdef'
04-13 13:02:55.923 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.923 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 35
04-13 13:02:55.923 3665 3704 E mfe : Name: 'baselarge' Type:
'fontdef'
04-13 13:02:55.924 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.924 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 43
04-13 13:02:55.924 3665 3704 E mfe : Name:
'baselargenormal' Type: 'fontdef'
04-13 13:02:55.924 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.924 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 47
04-13 13:02:55.924 3665 3704 E mfe : Name: 'baseextralarge' Type:
'fontdef'
04-13 13:02:55.924 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.924 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 111
04-13 13:02:55.924 3665 3704 E mfe : Name:
'basemedium_normal' Type: 'fontdef'
04-13 13:02:55.925 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.925 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 114
04-13 13:02:55.925 3665 3704 E mfe : Name:
'basemedium_normal_selected' Type: 'fontdef'
04-13 13:02:55.926 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.926 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 117
04-13 13:02:55.926 3665 3704 E mfe : Name:
'basemedium_disabled' Type: 'fontdef'
04-13 13:02:55.927 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.927 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 120
04-13 13:02:55.927 3665 3704 E mfe : Name:
'basemedium_highlight' Type: 'fontdef'
04-13 13:02:55.927 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.927 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 123
04-13 13:02:55.927 3665 3704 E mfe : Name:
'basemedium_normal_button' Type: 'fontdef'
04-13 13:02:55.928 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.928 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 126
04-13 13:02:55.928 3665 3704 E mfe : Name:
'basemedium_selected_button' Type: 'fontdef'
04-13 13:02:55.928 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:55.928 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 129
04-13 13:02:55.928 3665 3704 E mfe : Name:
'basemedium_disabled_button' Type: 'fontdef'
04-13 13:02:56.132 3665 3704 W mfe : MythCookieJar::load() failed to
open file for reading:
/data/user/0/org.mythtv.mythfrontend/files/MythBrowser/cookiejar.txt
04-13 13:02:56.132 3665 3704 I mfe : MythUIWebBrowser: Loading css
from - file://assets/mythtv/themes/default/htmls/mythbrowser.css
04-13 13:02:56.133 3665 3704 I mfe : MythUIWebBrowser: enabling plugins
04-13 13:02:56.435 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.435 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 1178
04-13 13:02:56.435 3665 3704 E mfe : Name: 'large' Type: 'fontdef'
04-13 13:02:56.436 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.436 3665 3704 E mfe : Location:
assets:/mythtv/themes/MythCenter/base.xml @ 1184
04-13 13:02:56.436 3665 3704 E mfe : Name: 'clock' Type: 'fontdef'
04-13 13:02:56.537 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.537 3665 3704 E mfe : Location:
assets:/mythtv/themes/default/base.xml @ 68
04-13 13:02:56.537 3665 3704 E mfe : Name: 'basemediumgrey' Type:
'fontdef'
04-13 13:02:56.538 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.538 3665 3704 E mfe : Location:
assets:/mythtv/themes/default/base.xml @ 72
04-13 13:02:56.538 3665 3704 E mfe : Name:
'basemediumgreen' Type: 'fontdef'
04-13 13:02:56.538 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.538 3665 3704 E mfe : Location:
assets:/mythtv/themes/default/base.xml @ 76
04-13 13:02:56.538 3665 3704 E mfe : Name: 'basemediumred' Type:
'fontdef'
04-13 13:02:56.538 3665 3704 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 13:02:56.538 3665 3704 E mfe : Location:
assets:/mythtv/themes/default/base.xml @ 80
04-13 13:02:56.538 3665 3704 E mfe : Name:
'basemediumyellow' Type: 'fontdef'
04-13 13:02:56.742 3665 3704 E mfe : OpenGL: : 1282 @
mythrender_opengl.cpp, 557
04-13 13:02:56.742 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.742 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.743 3665 3704 E mfe : OpenGL: : 1281 @
mythrender_opengl.cpp, 557
04-13 13:02:56.743 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.744 3665 3704 E mfe : OpenGL: : 1281 @
mythrender_opengl.cpp, 557
04-13 13:02:56.744 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.744 3665 3704 E mfe : OpenGL: : 1281 @
mythrender_opengl.cpp, 557
04-13 13:02:56.745 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.745 3665 3704 E mfe : OpenGL: : 1281 @
mythrender_opengl.cpp, 557
04-13 13:02:56.746 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.747 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.747 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.748 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.748 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479
04-13 13:02:56.749 3665 3704 E mfe : OpenGL2: : 1281 @
mythrender_opengl2.cpp, 479


Any ideas on any further troubleshooting I can try.

Steven
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 13/04/2019 02:09, OpenMedia Support wrote:

>
> I'm having the same blank screen issue on a FireTV Pendant with
> mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk
>
> I know remote access works as I've got a couple of remote frontends.
>
> I tried the recommended logging commands and got the following

<long snip>

> Any ideas on any further troubleshooting I can try.
>
> Steven

I'm afraid I don't have any suggestions, but this is from my FireTVstick
4K and the same 32-bit frontend build. Mine has

OpenGL: Initialised MythRenderOpenGL

where yours has

OpenGL2: Failed to compile shader

{{{

04-13 10:57:43.677 3954 3980 I mfe : Using Frameless Window
04-13 10:57:43.677 3954 3980 I mfe : Using Full Screen Window
04-13 10:57:43.678 3954 3980 I mfe : UI Screen Resolution: 1920 x 1080
04-13 10:57:44.580 3954 3980 W mfe : OpenGL: Could not determine
whether Sync to VBlank is enabled.
04-13 10:57:44.580 3954 3980 I mfe : OpenGL ES2 forced for Android
04-13 10:57:44.681 3954 3980 I mfe : OpenGL painter using existing
OpenGL context.
04-13 10:57:44.681 3954 3980 I mfe : OpenGL2ES: Found default
functionality.
04-13 10:57:44.682 3954 3980 I mfe : OpenGL2ES: Framebuffer
Objects available.
04-13 10:57:44.682 3954 3980 I mfe : OpenGL2ES: OES mapbuffer
available.
04-13 10:57:44.682 3954 3980 I mfe : OpenGL2ES: Vendor :
Imagination Technologies
04-13 10:57:44.682 3954 3980 I mfe : OpenGL2ES: Renderer: PowerVR
Rogue GE8300
04-13 10:57:44.683 3954 3980 I mfe : OpenGL2ES: Version : OpenGL
ES 3.2 build 1.9@4893595
04-13 10:57:44.683 3954 3980 I mfe : OpenGL2ES: Max texture size:
4096 x 4096
04-13 10:57:44.683 3954 3980 I mfe : OpenGL2ES: Max texture units: 96
04-13 10:57:44.683 3954 3980 I mfe : OpenGL2ES: Direct rendering: Yes
04-13 10:57:44.684 3954 3980 I mfe : OpenGL2ES: Extensions
Supported: 1c09
04-13 10:57:44.684 3954 3980 I mfe : OpenGL: Initialised
MythRenderOpenGL
04-13 10:57:44.684 3954 3980 I mfe : Platform name is android
04-13 10:57:44.785 3954 3980 I mfe : MythUIHelper: Pruning cache
directory: /data/user/0/org.mythtv.mythfrontend/files/cache/remotecache
04-13 10:57:44.785 3954 3980 I mfe : MythUIHelper: Kept 30 files,
deleted 1 files, stat error on 0 files
04-13 10:57:44.785 3954 3980 I mfe : MythUIHelper: Pruning cache
directory: /data/user/0/org.mythtv.mythfrontend/files/cache/thumbnails
04-13 10:57:44.785 3954 3980 I mfe : MythUIHelper: Kept 25 files,
deleted 0 files, stat error on 0 files
04-13 10:57:45.487 3954 3980 E mfe : MythFontProperties: Failed to
load 'Liberation Sans', got 'Roboto' instead
04-13 10:57:45.487 3954 3980 E mfe : Location:
assets:/mythtv/themes/MythCenter-wide/base.xml @ 26
04-13 10:57:45.487 3954 3980 E mfe : Name: 'basemedium' Type:
'fontdef'
}}}

John P
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 13/04/2019 02:09, OpenMedia Support wrote:

>
> I'm having the same blank screen issue on a FireTV Pendant with
> mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk
>
> I know remote access works as I've got a couple of remote frontends.
>
> I tried the recommended logging commands and got the following

<long snip>

> Any ideas on any further troubleshooting I can try.
>
> Steven

I'm afraid I don't have any suggestions, but this is from my FireTVstick
4K and the same 32-bit frontend build. Mine has

OpenGL: Initialised MythRenderOpenGL

where yours has

OpenGL2: Failed to compile shader

<snipped>

----------------

but later you do get

04-13 13:02:55.520 3665 3704 I mfe : OpenGL: Initialised
MythRenderOpenGL

and then there are references to mythbrowser, MythCookieJar and the
MythCenter theme. I'm using MythCenter-wide and see none of these.

Since going to the March build I find startup, after the logo disppears,
is sometimes very slow and I start to get anxious, but eventually it
does usually come up.

John P
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
> On 13/04/2019 02:09, OpenMedia Support wrote:
>
>>
>> I'm having the same blank screen issue on a FireTV Pendant with
>> mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk
>>
>> I know remote access works as I've got a couple of remote frontends.
>>
>> I tried the recommended logging commands and got the following
>
> <long snip>
>
>> Any ideas on any further troubleshooting I can try.
>>
>> Steven
>
> I'm afraid I don't have any suggestions, but this is from my FireTVstick
> 4K and the same 32-bit frontend build. Mine has
>
> OpenGL: Initialised MythRenderOpenGL
>
> where yours has
>
> OpenGL2: Failed to compile shader
>
> <snipped>
>
> ----------------
>
> but later you do get
>
> 04-13 13:02:55.520 3665 3704 I mfe : OpenGL: Initialised
> MythRenderOpenGL
>
> and then there are references to mythbrowser, MythCookieJar and the
> MythCenter theme. I'm using MythCenter-wide and see none of these.
>
> Since going to the March build I find startup, after the logo disppears,
> is sometimes very slow and I start to get anxious, but eventually it
> does usually come up.
>

Just tried the Feb build and the same issues - black screen
- mythfrontend-20190216-arm-v30.0-19-g5100ef5870e.apk

Also tried this on a 2nd Gen FireStick and the same issues - I get a black
screen and no opportunity to set any database options

Steven
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
>> On 13/04/2019 02:09, OpenMedia Support wrote:
>>
>>>
>>> I'm having the same blank screen issue on a FireTV Pendant with
>>> mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk
>>>
>>> I know remote access works as I've got a couple of remote frontends.
>>>
>>> I tried the recommended logging commands and got the following
>>
>> <long snip>
>>
>>> Any ideas on any further troubleshooting I can try.
>>>
>>> Steven
>>
>> I'm afraid I don't have any suggestions, but this is from my FireTVstick
>> 4K and the same 32-bit frontend build. Mine has
>>
>> OpenGL: Initialised MythRenderOpenGL
>>
>> where yours has
>>
>> OpenGL2: Failed to compile shader
>>
>> <snipped>
>>
>> ----------------
>>
>> but later you do get
>>
>> 04-13 13:02:55.520 3665 3704 I mfe : OpenGL: Initialised
>> MythRenderOpenGL
>>
>> and then there are references to mythbrowser, MythCookieJar and the
>> MythCenter theme. I'm using MythCenter-wide and see none of these.
>>
>> Since going to the March build I find startup, after the logo disppears,
>> is sometimes very slow and I start to get anxious, but eventually it
>> does usually come up.
>>
>
> Just tried the Feb build and the same issues - black screen
> - mythfrontend-20190216-arm-v30.0-19-g5100ef5870e.apk
>
> Also tried this on a 2nd Gen FireStick and the same issues - I get a black
> screen and no opportunity to set any database options
>

Ok a fresh test on my 2nd Gen Firestick with
- mythfrontend-20181124-arm-v30-Pre-983-gca71c59e61a.apk

This on works - I can get into Setup and connect to my backend. Tested
video playback and a number of other features.

None of the release builds will work for me. Also tried updating from the
Pre build to the latest 10 March build and I get a blank screen again.

Steven

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 4/14/19 2:32 AM, OpenMedia Support wrote:
> Ok a fresh test on my 2nd Gen Firestick with
> - mythfrontend-20181124-arm-v30-Pre-983-gca71c59e61a.apk
>
> This on works - I can get into Setup and connect to my backend. Tested
> video playback and a number of other features.
>
> None of the release builds will work for me. Also tried updating from the
> Pre build to the latest 10 March build and I get a blank screen again.
>
> Steven
>
I believe this is related to the test for GL_FRAGMENT_PRECISION_HIGH as
noted in my prior email. I am waiting for a response from Mark, who
added that code recently. If I do not hear back I will try reverting
that and see if it solves the problem.

Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 4/14/19 2:32 AM, OpenMedia Support wrote:
> Ok a fresh test on my 2nd Gen Firestick with
> - mythfrontend-20181124-arm-v30-Pre-983-gca71c59e61a.apk
>
> This on works - I can get into Setup and connect to my backend. Tested
> video playback and a number of other features.
>
> None of the release builds will work for me. Also tried updating from the
> Pre build to the latest 10 March build and I get a blank screen again.
>
> Steven
I have released a new build on bintray.com to fix this problem
Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 14/04/2019 22:13, Peter Bennett wrote:
>
>
> On 4/14/19 2:32 AM, OpenMedia Support wrote:
>> Ok a fresh test on my 2nd Gen Firestick with
>>   - mythfrontend-20181124-arm-v30-Pre-983-gca71c59e61a.apk
>>
>> This on works - I can get into Setup and connect to my backend. Tested
>> video playback and a number of other features.
>>
>> None of the release builds will work for me. Also tried updating from the
>> Pre build to the latest 10 March build and I get a blank screen again.
>>
>> Steven
> I have released a new build on bintray.com to fix this problem
> Peter

Thank you Peter. Installed and it's still working for me (4K stick) :-)

One minor point I see in the log

MythUIGuideGrid: unable to open
'assets:/mythtv/themes/default/categoies.xml'

which would explain why the guide has been/is in monochrome blue.

John P


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
>
>
> On 4/14/19 2:32 AM, OpenMedia Support wrote:
>> Ok a fresh test on my 2nd Gen Firestick with
>> - mythfrontend-20181124-arm-v30-Pre-983-gca71c59e61a.apk
>>
>> This on works - I can get into Setup and connect to my backend. Tested
video playback and a number of other features.
>>
>> None of the release builds will work for me. Also tried updating from the
>> Pre build to the latest 10 March build and I get a blank screen again.
>>
>> Steven
> I have released a new build on bintray.com to fix this problem
> Peter

Peter - Many thanks.

Just upgraded to the latest build and everything appears to work again.

Out of interest how can I connect the build back to a given git checkin?
I'm not sure which branch you are building off.

Steven


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/6/19 10:04 PM, OpenMedia Support wrote:
> Out of interest how can I connect the build back to a given git checkin?
> I'm not sure which branch you are building off.
>
On frontend
Information Center -> System Status -> Listrngs Status -> Mythfrontend
version
That tells the branch, version and commit hash

You can also get the information from the log.

Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
>
>
> On 5/6/19 10:04 PM, OpenMedia Support wrote:
>> Out of interest how can I connect the build back to a given git checkin?
>> I'm not sure which branch you are building off.
>>
> On frontend
> Information Center -> System Status -> Listrngs Status -> Mythfrontend
> version
> That tells the branch, version and commit hash
>
> You can also get the information from the log.
>
> Peter

Peter - I just got a brand new FireTV 4K and tried out
- mythfrontend-20190414-arm-v30.0-43-g5a67176bf90.apk

Worked first time with no UI issues.

Are they any plans to implement frame rate switching in the Android
version of mythtv?
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/14/19 7:17 PM, OpenMedia Support wrote:
>>
>> On 5/6/19 10:04 PM, OpenMedia Support wrote:
>>> Out of interest how can I connect the build back to a given git checkin?
>>> I'm not sure which branch you are building off.
>>>
>> On frontend
>> Information Center -> System Status -> Listrngs Status -> Mythfrontend
>> version
>> That tells the branch, version and commit hash
>>
>> You can also get the information from the log.
>>
>> Peter
> Peter - I just got a brand new FireTV 4K and tried out
> - mythfrontend-20190414-arm-v30.0-43-g5a67176bf90.apk
>
> Worked first time with no UI issues.
>
> Are they any plans to implement frame rate switching in the Android
> version of mythtv?
> _______________________________________________
>
Not as far as I know, but Mark Kendall is working on improvements to the
rendering support. He may have some plans for that..

Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/15/19 5:32 PM, Peter Bennett wrote:
>
>
> On 5/14/19 7:17 PM, OpenMedia Support wrote:
>>>
>>> On 5/6/19 10:04 PM, OpenMedia Support wrote:
>>>> Out of interest how can I connect the build back to a given git
>>>> checkin?
>>>> I'm not sure which branch you are building off.
>>>>
>>> On frontend
>>> Information Center -> System Status -> Listrngs Status -> Mythfrontend
>>> version
>>> That tells the branch, version and commit hash
>>>
>>> You can also get the information from the log.
>>>
>>> Peter
>> Peter - I just got a brand new FireTV 4K and tried out
>>   - mythfrontend-20190414-arm-v30.0-43-g5a67176bf90.apk
>>
>> Worked first time with no UI issues.
>>
>> Are they any plans to implement frame rate switching in the Android
>> version of mythtv?
>> _______________________________________________
>>
> Not as far as I know, but Mark Kendall is working on improvements to the
> rendering support. He may have some plans for that..
>
> Peter
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I tried one of the latest android builds from the ticket. I can actually
get audio now, but only stereo. When I try to play a movie with digital
audio, it seems to want to convert everything to LPCM stereo. That's
what my receiver says its receiving.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 17/05/2019 17:04, mythtv wrote:
> On 5/15/19 5:32 PM, Peter Bennett wrote:
>>
>>
>> On 5/14/19 7:17 PM, OpenMedia Support wrote:
>>>>
>>>> On 5/6/19 10:04 PM, OpenMedia Support wrote:
>>>>> Out of interest how can I connect the build back to a given git
>>>>> checkin?
>>>>> I'm not sure which branch you are building off.
>>>>>
>>>> On frontend
>>>> Information Center -> System Status -> Listrngs Status -> Mythfrontend
>>>> version
>>>> That tells the branch, version and commit hash
>>>>
>>>> You can also get the information from the log.
>>>>
>>>> Peter
>>> Peter - I just got a brand new FireTV 4K and tried out
>>>   - mythfrontend-20190414-arm-v30.0-43-g5a67176bf90.apk
>>>
>>> Worked first time with no UI issues.
>>>
>>> Are they any plans to implement frame rate switching in the Android
>>> version of mythtv?
>>> _______________________________________________
>>>
>> Not as far as I know, but Mark Kendall is working on improvements to
>> the rendering support. He may have some plans for that..
>>
>> Peter

>
> I tried one of the latest android builds from the ticket. I can actually
> get audio now, but only stereo. When I try to play a movie with digital
> audio, it seems to want to convert everything to LPCM stereo. That's
> what my receiver says its receiving.

I tried the 32-bit build from #13446 comment 10 too, although I have
only stereo hardware. I managed to provoke a hang-needing-restart
during some playback/skip operation but didn't investigate further.

I too would like a 50Hz option, to match my recordings; smooth motion
does look slightly unsmooth at present. I tried the device's match
framerate option but didn't see any difference.

John P

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/17/19 12:04 PM, mythtv wrote:
> I tried one of the latest android builds from the ticket. I can
> actually get audio now, but only stereo. When I try to play a movie
> with digital audio, it seems to want to convert everything to LPCM
> stereo. That's what my receiver says its receiving.

Did you follow the instructions in the ticket?

https://code.mythtv.org/trac/ticket/13446#comment:5

See "To use AudioTrack on Android" in the comment

There is also a new build see comment 11

Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/17/19 3:10 PM, Peter Bennett wrote:
>
>
> On 5/17/19 12:04 PM, mythtv wrote:
>> I tried one of the latest android builds from the ticket. I can
>> actually get audio now, but only stereo. When I try to play a movie
>> with digital audio, it seems to want to convert everything to LPCM
>> stereo. That's what my receiver says its receiving.
>
> Did you follow the instructions in the ticket?
>
> https://code.mythtv.org/trac/ticket/13446#comment:5
>
> See "To use AudioTrack on Android" in the comment
>
> There is also a new build see comment 11
>
> Peter

Yea, I followed those instructions. I am getting similar results to
mspieth:

* In audio setup, selected 5.1 with upconvert best, then test speakers,
surround left and right come out of front left and right, and lfe comes
out of center.

When I play a movie with digital audio, my amp says it's only receiving
stereo LPCM.

I tried the build from comment 11. That's the only build I tried
actually. I have a Fire Stick 4k. I set the audio in Android to Best
Available. I set the audio output device to AudioTrack in Myth and I
checked all of the formats. My receiver is capable of decoding all of
them. It is a 7.1 receiver but I only have a 5.1 speaker setup so I set
the number of channels to 5.1.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/18/19 7:08 PM, mythtv wrote:
> When I play a movie with digital audio, my amp says it's only
> receiving stereo LPCM.
>
> I tried the build from comment 11. That's the only build I tried
> actually. I have a Fire Stick 4k. I set the audio in Android to Best
> Available. I set the audio output device to AudioTrack in Myth and I
> checked all of the formats. My receiver is capable of decoding all of
> them. It is a 7.1 receiver but I only have a 5.1 speaker setup so I
> set the number of channels to 5.1.

The fire stick 4K automatically detects what the TV can support. If it
thinks that the TV cannot support Dolby output, android will convert it
to LPCM.

Do other apps (e.g. Amazon prime) pass through Dolby digital on that TV?

I suggest trying the audio settings in Android and see if you can force
it to use Dolby output. Also compare results with Amazon Prime playback
to see if your settings work with DOlby pass through.

Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/19/19 9:25 AM, Peter Bennett wrote:
>
>
> On 5/18/19 7:08 PM, mythtv wrote:
>> When I play a movie with digital audio, my amp says it's only
>> receiving stereo LPCM.
>>
>> I tried the build from comment 11. That's the only build I tried
>> actually. I have a Fire Stick 4k. I set the audio in Android to Best
>> Available. I set the audio output device to AudioTrack in Myth and I
>> checked all of the formats. My receiver is capable of decoding all of
>> them. It is a 7.1 receiver but I only have a 5.1 speaker setup so I
>> set the number of channels to 5.1.
>
> The fire stick 4K automatically detects what the TV can support. If it
> thinks that the TV cannot support Dolby output, android will convert it
> to LPCM.
>
> Do other apps (e.g. Amazon prime) pass through Dolby digital on that TV?
>

All of the other apps play surround correctly. I have Kodi and Hulu
installed and they both work fine. I will try to force Dolby Digital
later today.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/19/19 10:49 AM, mythtv wrote:
> On 5/19/19 9:25 AM, Peter Bennett wrote:
>>
>>
>> On 5/18/19 7:08 PM, mythtv wrote:
>>> When I play a movie with digital audio, my amp says it's only
>>> receiving stereo LPCM.
>>>
>>> I tried the build from comment 11. That's the only build I tried
>>> actually. I have a Fire Stick 4k. I set the audio in Android to Best
>>> Available. I set the audio output device to AudioTrack in Myth and I
>>> checked all of the formats. My receiver is capable of decoding all of
>>> them. It is a 7.1 receiver but I only have a 5.1 speaker setup so I
>>> set the number of channels to 5.1.
>>
>> The fire stick 4K automatically detects what the TV can support. If it
>> thinks that the TV cannot support Dolby output, android will convert
>> it to LPCM.
>>
>> Do other apps (e.g. Amazon prime) pass through Dolby digital on that TV?
>>
>
> All of the other apps play surround correctly. I have Kodi and Hulu
> installed and they both work fine. I will try to force Dolby Digital
> later today.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

So I got around to trying to force Dolby Digital. Things worked pretty
well with that with a few exceptions. My amp supports all formats up to
DTS-HD and when I tried to play a movie with that, it disabled the audio
due to a reconfigure error, or something like that. When I unchecked
support for DTS-HD in audio setup, then I only got stereo sound.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 5/17/19 1:10 PM, Peter Bennett wrote:
>
>
> On 5/17/19 12:04 PM, mythtv wrote:
>> I tried one of the latest android builds from the ticket. I can
>> actually get audio now, but only stereo. When I try to play a movie
>> with digital audio, it seems to want to convert everything to LPCM
>> stereo. That's what my receiver says its receiving.
>
> Did you follow the instructions in the ticket?
>
> https://code.mythtv.org/trac/ticket/13446#comment:5
>
> See "To use AudioTrack on Android" in the comment


Hi Peter, I am finally updating to version 31 this week and had saved
this thread for when I was able to do the upgrade.  In the notes of the
ticket you noted:


To use AudioTrack on Android

In the Android setup, choose "Automatic" or "Best Available". There is
no need to force Dolby Digital in Android, it will be used automatically
if your hardware supports it.

Select "AudioTrack:" audio device. Enable all entries under "Digital
Capabilities" and set the appropriate number of speakers. Android will
detect whether your TV or sound system supports the audio format and
will either pass it through or decode it within android hardware. So for
example you can select Dolby Digital even if your sound system, TV or
display monitor does not support it and android will decode it. If you
do not select the checkbox, MythTV will decode it.

I have tested Dolby Digital (AC-3). I cannot test multi channel LPCM,
DTS, E-AC3, etc. If anybody can test these it would be appreciated. In
particular, testing multi-channel LPCM is needed to make sure the
channel mapping is correct.

Let me know if there is any feedback.


I configured my shield frontend to have all digital formats and set the
Shield to auto.   It seemed like all was working until today my wife
reported a video that has AC-3 audio that wouldn't play any sound.  If I
uncheck AC-3 in mythtvsetup, I get the audio.  Additionally, in
leanfrontend it plays with audio just fine.


According to the manual for my receiver, it does support all of the
digital audio formats in the mythtv screen.


Are these instructions still accurate?  Any thoughts on debugging further?


Michael
Re: Android frontend for FireTv cube 4k? [ In reply to ]
On 4/8/20 8:41 PM, Michael wrote:
> On 5/17/19 1:10 PM, Peter Bennett wrote:
>>
>>
>> On 5/17/19 12:04 PM, mythtv wrote:
>>> I tried one of the latest android builds from the ticket. I can
>>> actually get audio now, but only stereo. When I try to play a movie
>>> with digital audio, it seems to want to convert everything to LPCM
>>> stereo. That's what my receiver says its receiving.
>>
>> Did you follow the instructions in the ticket?
>>
>> https://code.mythtv.org/trac/ticket/13446#comment:5
>>
>> See "To use AudioTrack on Android" in the comment
>
>
> Hi Peter, I am finally updating to version 31 this week and had saved
> this thread for when I was able to do the upgrade.  In the notes of
> the ticket you noted:
>
>
> To use AudioTrack on Android
>
> In the Android setup, choose "Automatic" or "Best Available". There is
> no need to force Dolby Digital in Android, it will be used
> automatically if your hardware supports it.
>
> Select "AudioTrack:" audio device. Enable all entries under "Digital
> Capabilities" and set the appropriate number of speakers. Android will
> detect whether your TV or sound system supports the audio format and
> will either pass it through or decode it within android hardware. So
> for example you can select Dolby Digital even if your sound system, TV
> or display monitor does not support it and android will decode it. If
> you do not select the checkbox, MythTV will decode it.
>
> I have tested Dolby Digital (AC-3). I cannot test multi channel LPCM,
> DTS, E-AC3, etc. If anybody can test these it would be appreciated. In
> particular, testing multi-channel LPCM is needed to make sure the
> channel mapping is correct.
>
> Let me know if there is any feedback.
>
>
> I configured my shield frontend to have all digital formats and set
> the Shield to auto.   It seemed like all was working until today my
> wife reported a video that has AC-3 audio that wouldn't play any
> sound.  If I uncheck AC-3 in mythtvsetup, I get the audio. 
> Additionally, in leanfrontend it plays with audio just fine.
>
>
> According to the manual for my receiver, it does support all of the
> digital audio formats in the mythtv screen.
>
>
> Are these instructions still accurate?  Any thoughts on debugging further?
>
>
> Michael
>
I had some sound trouble on the Shield TV with the android mythfrontend
recently and found for me that in the Digital Capabilities setup of
setup I could not check Dolby Digital or DTS, the first 2 entries.  I
had to check E-AC-3 and the 2 below it to get 5.1 sound.  The complete
story is documented on the Mythtv Forum.  I find some things easier to
find or document over there.
https://forum.mythtv.org/viewtopic.php?f=47&t=3698

Jim A
Re: [renamed] Audio problem on Shield [ In reply to ]
On 4/8/20 8:41 PM, Michael wrote:
> On 5/17/19 1:10 PM, Peter Bennett wrote:
>>
>>
>> On 5/17/19 12:04 PM, mythtv wrote:
>>> I tried one of the latest android builds from the ticket. I can
>>> actually get audio now, but only stereo. When I try to play a movie
>>> with digital audio, it seems to want to convert everything to LPCM
>>> stereo. That's what my receiver says its receiving.
>>
>> Did you follow the instructions in the ticket?
>>
>> https://code.mythtv.org/trac/ticket/13446#comment:5
>>
>> See "To use AudioTrack on Android" in the comment
>
>
> Hi Peter, I am finally updating to version 31 this week and had saved
> this thread for when I was able to do the upgrade.  In the notes of
> the ticket you noted:
>
>
> To use AudioTrack on Android
>
> In the Android setup, choose "Automatic" or "Best Available". There is
> no need to force Dolby Digital in Android, it will be used
> automatically if your hardware supports it.
>
> Select "AudioTrack:" audio device. Enable all entries under "Digital
> Capabilities" and set the appropriate number of speakers. Android will
> detect whether your TV or sound system supports the audio format and
> will either pass it through or decode it within android hardware. So
> for example you can select Dolby Digital even if your sound system, TV
> or display monitor does not support it and android will decode it. If
> you do not select the checkbox, MythTV will decode it.
>
> I have tested Dolby Digital (AC-3). I cannot test multi channel LPCM,
> DTS, E-AC3, etc. If anybody can test these it would be appreciated. In
> particular, testing multi-channel LPCM is needed to make sure the
> channel mapping is correct.
>
> Let me know if there is any feedback.
>
>
> I configured my shield frontend to have all digital formats and set
> the Shield to auto.   It seemed like all was working until today my
> wife reported a video that has AC-3 audio that wouldn't play any
> sound.  If I uncheck AC-3 in mythtvsetup, I get the audio. 
> Additionally, in leanfrontend it plays with audio just fine.
>
>
> According to the manual for my receiver, it does support all of the
> digital audio formats in the mythtv screen.
>
>
> Are these instructions still accurate?  Any thoughts on debugging further?
>
>
> Michael
>
>
>
I will try this again and let you know. It should work, but later
changes may have introduced a problem.

Peter
Re: [renamed] Audio problem on Shield [ In reply to ]
On 4/9/20 10:47 AM, Peter Bennett wrote:
>
>
> On 4/8/20 8:41 PM, Michael wrote:
>> On 5/17/19 1:10 PM, Peter Bennett wrote:
>>>
>>>
>>> On 5/17/19 12:04 PM, mythtv wrote:
>>>> I tried one of the latest android builds from the ticket. I can
>>>> actually get audio now, but only stereo. When I try to play a movie
>>>> with digital audio, it seems to want to convert everything to LPCM
>>>> stereo. That's what my receiver says its receiving.
>>>
>>> Did you follow the instructions in the ticket?
>>>
>>> https://code.mythtv.org/trac/ticket/13446#comment:5
>>>
>>> See "To use AudioTrack on Android" in the comment
>>
>>
>> Hi Peter, I am finally updating to version 31 this week and had saved
>> this thread for when I was able to do the upgrade. In the notes of
>> the ticket you noted:
>>
>>
>> To use AudioTrack on Android
>>
>> In the Android setup, choose "Automatic" or "Best Available". There
>> is no need to force Dolby Digital in Android, it will be used
>> automatically if your hardware supports it.
>>
>> Select "AudioTrack:" audio device. Enable all entries under "Digital
>> Capabilities" and set the appropriate number of speakers. Android
>> will detect whether your TV or sound system supports the audio format
>> and will either pass it through or decode it within android hardware.
>> So for example you can select Dolby Digital even if your sound
>> system, TV or display monitor does not support it and android will
>> decode it. If you do not select the checkbox, MythTV will decode it.
>>
>> I have tested Dolby Digital (AC-3). I cannot test multi channel LPCM,
>> DTS, E-AC3, etc. If anybody can test these it would be appreciated.
>> In particular, testing multi-channel LPCM is needed to make sure the
>> channel mapping is correct.
>>
>> Let me know if there is any feedback.
>>
>>
>> I configured my shield frontend to have all digital formats and set
>> the Shield to auto.   It seemed like all was working until today my
>> wife reported a video that has AC-3 audio that wouldn't play any
>> sound.  If I uncheck AC-3 in mythtvsetup, I get the audio. 
>> Additionally, in leanfrontend it plays with audio just fine.
>>
>>
>> According to the manual for my receiver, it does support all of the
>> digital audio formats in the mythtv screen.
>>
>>
>> Are these instructions still accurate?  Any thoughts on debugging
>> further?
>>
>>
>> Michael
>>
>>
>>
> I will try this again and let you know. It should work, but later
> changes may have introduced a problem.
>
> Peter

I just tested on the Shield with mythfrontend V31.0 (same apk as on
bintray). I selected "Auto" under surround sound in the Shield Setup. I
selected AudioTrack: in MythTV,  selected Dolby Digital and DTS in
"Digital Audio Capabilities", selected 5.1 in speaker setup.

AC-3 plays fine, and displays "Dolby Digital" in the audio receiver
display.

I found, if I select "Stereo" in the Shield setup and still have Dolby
Digital selected in MythTV, that I get no sound, but that is an invalid
configuration.

Perhaps your sound system is telling the shield that it does not support
ac-3. You could try the "Manual" audio setup in shield setup and select
AC-3.

Are you sure you have selected AudioTrack: in MythTV? OpenSles does not
support any surround sound formats. Also check the number of speakers setup.

Peter

1 2  View All