[mythtv-users] Android Mythrontend on Firestck 4K

Peter Bennett pb.mythtv at gmail.com
Mon Sep 25 20:06:07 UTC 2023


On 9/25/23 12:16, Will Dormann wrote:
> (responding to list this time)
>
> I just today installed Leanfront on a Fire Stick 4k, and it worked 
> fine, requiring no more than entering the host name of the backend.
>
> And like you, the full mythfrontend app is failing to connect. The 
> fact that Leanfront works, and that I can also remotely use the normal 
> mysql client remotely makes me wonder what the problem might be.
>
> I too am running mysql as the database server, but from what I can 
> tell the MariaDB client protocol is binary compatible with that of 
> MySQL, so that could be a red herring...
>
> Anyway, I've heard that Leanfront may be better than the full MythTV 
> client as it uses hardware video acceleration (and the full does not? 
> Still?).  But I'd like to test out both, as I've found that the 
> Leanfront interface leaves a touch to be desired.  At least for 
> someone used to the full client.
>
> If you figure anything out, please report back here, and I'll do the 
> same.
>
> Addendum: Looking at adb logcat info, I see:
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE , attempt 0, status dbAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE , attempt 1, status dbAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 2, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 3, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 4, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 5, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 6, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 7, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 8, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 9, status beAwake, Delay: 2000
> mythcontext.cpp:887:TestDBconnection  Start up testing connections. DB 
> <hostname>, BE 127.0.0.1, attempt 10, status beAwake, Delay: 2000
> mythcontext.cpp:1010:TestDBconnection  Start up failure. host 
> <hostname>, status beAwakeFail
>
> The fact that the BE (backend, I presume) starts out blank, and then 
> falls back to 127.0.0.1 is a touch suspicious. Though perhaps it 
> defaults to using the same host as the DB?
>
> I noticed a message from Peter saying that "The prompt for database 
> credentials causes the program to crash." in the last-built Android 
> version, but I'll note that I see no visible crash.  Unless "the 
> program" is referring to a separate helper app that isn't visible?
>
>
What was happening is that if your DB machine is down, it would display 
a screen that says "waiting for database", and if you tabbed to the 
Setup button (to fix database settings) and pressed enter, the program 
exited and returned you to the fire stick home screen. That is fixed in 
the new version.


> Thanks
> -WD
>
>
> On 9/24/23 2:10 PM, Ken Mandelberg wrote:
>> I'm trying to run the Android Mythfrontend on a Firestick 4K without 
>> any luck. Has anyone succeeded at this? It fails the initial 
>> authentication against the Mysql database on the backend.
>>
>> This is against Peter's latest build of the 32 bit version. Peter had 
>> some suggestions, but nothing has worked.
>>
>> Some notes:
>>
>> Mysql sees sees the query and the mysql log shows
>>
>> 2023-09-23T20:02:39.007635Z     7975 Connect mythtv at fire4k.kmhome on 
>> mythconverg using TCP/IP
>> 2023-09-23T20:02:39.007719Z     7975 Connect    Access denied for 
>> user 'mythtv'@'fire4k.kmhome' (using password: NO)
>>
>>
>> I have several Linux machines with mythfrontend running against the 
>> same mysql database successfully and the mysql log shows
>>
>> 2023-09-23T20:04:17.913574Z      7979 Connect mythtv at kmnuc-w.kmhome 
>> on mythconverg using SSL/TLS
>> 2023-09-23T20:04:17.915495Z      7979 Init DB   mythconverg
>>
>> The problem is not based on a permission error on the mysql server. 
>> The other clients had no problem, but at Peter's suggested I opened 
>> it even wider for a test adding a "mythtv'@'%" user with a wide open 
>> grant of permissions. It's not permissions.
>>
>> I also snooped the wire to see what the firestick was sending in its 
>> authentication dialog. I won't post all the voluminous details, but 
>> in decoding the mysql transaction I noticed
>>
>>         Username: mythtv
>>          Schema: mythconverg
>>          Client Auth Plugin: dummy_fallback_auth
>>          Connection Attributes
>>              Connection Attributes length: 113
>>              Connection Attribute - _os: Android
>>              Connection Attribute - _client_name: libmariadb
>>                  ...
>>                  Connection Attribute Value: libmariadb
>>
>> The reference to mariadb caught my eye since the backend uses mysql, 
>> as well as the Auth Plugin.
>>
>> Any help?
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


More information about the mythtv-users mailing list