Jump to content

Issues with emby Android TV


Recommended Posts

thor2002ro
Posted

I have an issue any version newer than Android TV 2.0.48g the app just freezes at login or startup with logo.... Tried different servers versions either beta or stable work... 

If I get app version 2.0.48g from apkmirror works fine 

Tried it on Google TV / mibox 3/mibox 4 /mibox stick 4k all behave the same with clean installs

Posted

Hi.  Exactly which server versions did you try?

How are you connecting to your server?  Is it local or remote?  http or https?

Can we please see a server log from when one of these freezes occurred and also tell us exactly what time that happened?

Thanks.

thor2002ro
Posted (edited)

here is the log.....

first try at 2022-08-15 19:42:41.294

second 2022-08-15 19:44:13.378 

third 2022-08-15 19:45:39.113

i see nothing suspicions.....

 

emby_Server.log

Edited by thor2002ro
Posted
19 hours ago, thor2002ro said:

Tried it on Google TV / mibox 3/mibox 4 /mibox stick 4k all behave the same with clean installs

I see a Mibox 4 happily playing content in that log so it isn't all of your devices, correct?

You say the app "freezes".  How do you get out of that situation? Does the back key work?  Exactly what is on the screen when it "freezes"?

After this has happened, can you get to a manual login screen where the users are shown?  On that screen is a "Send logs" button.  If you can make the freeze occur and then get to that screen and send the log, please tell me exactly what time you did that.

Thanks.

thor2002ro
Posted (edited)

Mibox4 was another user using 2.0.48 app that works fine(I don't have to tell you can see the app version at login 😅) .... In that log only mi stick 4k was using the latest app(but all the devices I mentioned behave the same from inside the network or from outside) (I mentioned multiple devices because some are android tv 7, some are android tv 9 and some are android tv 11 so I cover a big spectrum... ) .... And it's unuseble it just freezes after user select nothing works after... Just force close and it just goes trough it again..... I can't get trough it and see logs.... I even tried adb logcat I didn't see any usefull error.... There must be something different after the 48 version.... And doesn't seam to be server side issue.... 

Maybe it's usefull but not all machines in my network have full internet access some its filtered... 

Edited by thor2002ro
Posted
15 hours ago, thor2002ro said:

Maybe it's usefull but not all machines in my network have full internet access some its filtered... 

If you temporarily disable whatever is doing that, does this issue go away?

thor2002ro
Posted
3 minutes ago, ebr said:

If you temporarily disable whatever is doing that, does this issue go away?

What issue would that be  if older version works and newer doesn't? 

Posted
2 minutes ago, thor2002ro said:

What issue would that be

The issue of the app not starting.

thor2002ro
Posted
58 minutes ago, ebr said:

The issue of the app not starting.

Yes.... What's the issue if my android box is isolated from internet and can only access my network? Is the app startup linked to a call home function on my private server? I don't trust these android boxes so I isolate them from the internet.... 

FrostByte
Posted

ATV is not free so it will need to validate you own premiere or purchased an unlock every so many days.  Allow the app to connect and validate you own it then unplug if you want. 

thor2002ro
Posted
20 minutes ago, FrostByte said:

ATV is not free so it will need to validate you own premiere or purchased an unlock every so many days.  Allow the app to connect and validate you own it then unplug if you want. 

i dont need premiere..... starting to understand .... guess after 2.0.48 app you implemented some new malware thats unhappy it cant call the mothership...

 

30 minutes ago, Luke said:

Can you try side loading our standard Android app on the same device and let us know how that compares:

https://emby.media/emby-for-android.html

Thanks.

this works but it looks really weird....

FrostByte
Posted (edited)
10 minutes ago, thor2002ro said:

i dont need premiere..... starting to understand .... guess after 2.0.48 app you implemented some new malware thats unhappy it cant call the mothership...

 

this works but it looks really weird....

You don't need premiere.  You can also purchase an unlock for a minimal fee so that ebr can feed his family.  It will still need to call the "mothership" as you call it once in a while to verify.  It's more like a hole was plugged from what I understand.

 

Edited by FrostByte
Posted
25 minutes ago, thor2002ro said:

i dont need premiere..... starting to understand .... guess after 2.0.48 app you implemented some new malware thats unhappy it cant call the mothership...

 

this works but it looks really weird....

Looks weird how?

thor2002ro
Posted
2 minutes ago, Luke said:

Looks weird how?

the interface doesnt have the correct layout for a tv interface...

Posted
6 minutes ago, thor2002ro said:

the interface doesnt have the correct layout for a tv interface...

Try going into the app display settings, setting it to TV mode, and then restarting the app.

This is detected automatically for most devices, but occasionally for some third party tv boxes it won't be.

Posted
3 hours ago, thor2002ro said:

Yes.... What's the issue if my android box is isolated from internet and can only access my network? Is the app startup linked to a call home function on my private server? I don't trust these android boxes so I isolate them from the internet.... 

I'm just trying to troubleshoot what the issue may be.  If the problem goes away when you eliminate your blocking filter, then we'll have a good idea where to look.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...