New Emby for Android 3.5.45 Released

[Emby Releases 150]

Emby for Android 3.5.45 Released

Changes

3.5.45

• Core UI Update Only

Core UI Changes from 26.0.7 to 26.0.10

• Fix positioning of video OSD brightness slider
• Show live tv guide filters in tv display mode
• Fix alignment of live tv guide time indicator
• Support swipe left and right gestures on now playing bar to advance tracks
• Fixes related to position of center play/pause buttons in mobile layouts
• Fix display of recording start time when pre-padding is applied

 

[Lutzif3r 2]

With this version when it starts up there's a brief message saying... Attempting to connect to server, please wait.

Noticed it on my main Google TV, then in my other Google TV which had gotten this update, and 1 phone. Then checked my other Android phone that had been off, turn it on and opened Emby and got no message, then updated Emby and now I get the message, so obviously is an issue with this new release.

[Luke 42976]

50 minutes ago, Lutzif3r said:

With this version when it starts up there's a brief message saying... Attempting to connect to server, please wait.

Noticed it on my main Google TV, then in my other Google TV which had gotten this update, and 1 phone. Then checked my other Android phone that had been off, turn it on and opened Emby and got no message, then updated Emby and now I get the message, so obviously is an issue with this new release.

"Obviously an issue" ? What is the issue?

[FrostByte 5587]

2 hours ago, Luke said:

"Obviously an issue" ? What is the issue?

When it first happened, I was wondering what it said because it was very quick and had to reread some threads in the forum to find out what it was.  I think people will be curious when they first see it.

IF there was a way to make it not show until after X seconds that would be nice because then only the people with slow connections would see it.  Otherwise, I see its purpose.

[Lutzif3r 2]

Well it's basically a flash on any device. It took me many many times on one of my phones just to figure out what it even said on the popup. But it's still annoying ** ****, even a 1 second flash of some sort of popup ain't good. I've never seen anything like that ever.

Edited August 19 by seanbuff
profanity

[Lutzif3r 2]

4 hours ago, FrostByte said:

My connection definitely ain't slow.

 

[FrostByte 5587]

16 minutes ago, Lutzif3r said:

 

Mine neither, which is why I think it shouldn't even pop up for several seconds after which it determines the connection is slow.  Even a 5 second delay would mean I would never see it.

[Luke 42976]

It's delayed by 600ms. So one second after that means it took 1.6 seconds to connect. That is long enough that if you don't put up some kind of feedback it will have users mashing and clicking things a second time.

[FrostByte 5587]

It comes up and disappears so fast I can't even read it.  Don't know how anyone could be mashing any keys in that short of time.

Edited August 19 by FrostByte

[Lessaj 547]

I think that it should delay a bit longer before appearing, it is very brief yes but probably a 1.5 delay would be the max that is reasonable (on top of the 1 second), likely 2 seconds overall is a fair target.

[chrisrobbins1970 87]

What about not showing at all??

[Lutzif3r 2]

3 hours ago, chrisrobbins1970 said:

What about not showing at all??

Exactly.

[Luke 42976]

4 hours ago, chrisrobbins1970 said:

What about not showing at all??

Then if your server is unreachable you have no opportunity to cancel the attempt to connect and must wait 30 seconds for it to time out.

[chrisrobbins1970 87]

Ok.... understood... just saw if before the update 

[FrostByte 5587]

Sounds like there is a lot of wiggle room between .6 and 30 seconds.  A delay of somewhere between 2000 to 3000ms before showing it, while trying to connect, would probably allow most of us who are connected via wire to never see it and still not cause people with a slow connection to panic.

[Lutzif3r 2]

5 hours ago, Luke said:

Then if your server is unreachable you have no opportunity to cancel the attempt to connect and must wait 30 seconds for it to time out.

What we're getting at is that why is this just happening as of this update?

My connection definitely didn't all of a sudden get bad, it's super fast. Awhile ago I had a crappy connection and I had no problems with Emby whatsoever, and no popup message like now.

[Luke 42976]

1 minute ago, Lutzif3r said:

What we're getting at is that why is this just happening as of this update?

My connection definitely didn't all of a sudden get bad, it's super fast. Awhile ago I had a crappy connection and I had no problems with Emby whatsoever, and no popup message like now.

Because the ability to cancel that process was recently added.

[dirkgent 0]

Will this version (or later) be released on Google play or only as APK? Wonder as the latest version available on Play is 3.5.36 and that was released in may.

How often do you release on Google play vs only as APK?

[jyeomans 2]

I get the reason, but the implementation is very poor.

You have created more of an annoyance than was caused by the problem you were trying to fix.

Give the thing time to load first!

[FrostByte 5587]

@Luke I think the new server 4.10.0.27 and app 3.5.47 only made things worse.

It used to show the splash screen and then a quick flash of the connection screen (which was unreadable because it was so fast) and then the home screen.  It was a real quick.

Now I see the splash screen a spinning circle shows up and the connection screen is visible for a short period of time before I get the home screen.  The whole process is slower.

It's looks like it's not even trying to connect before the connection screen pops up.  What it looks like to me is that there was time added AFTER the connection screen pops up and then it connects.  What I was hoping for is that it would try to connect and then ONLY IF it didn't connect in X seconds the pop up would be displayed.

Edited August 22 by FrostByte

[Luke 42976]

4 hours ago, FrostByte said:

@Luke I think the new server 4.10.0.27 and app 3.5.47 only made things worse.

It used to show the splash screen and then a quick flash of the connection screen (which was unreadable because it was so fast) and then the home screen.  It was a real quick.

Now I see the splash screen a spinning circle shows up and the connection screen is visible for a short period of time before I get the home screen.  The whole process is slower.

It's looks like it's not even trying to connect before the connection screen pops up.  What it looks like to me is that there was time added AFTER the connection screen pops up and then it connects.  What I was hoping for is that it would try to connect and then ONLY IF it didn't connect in X seconds the pop up would be displayed.

It is trying to connect before it comes up. The delay was bumped up to 800ms before you see it.

[CBers 7686]

I've never understood why the Universal Android app takes so long to connect. 

The ATV app is so much quicker. 

I'm still on 3.4.45, but still over 30 seconds to get to the home screen. 

App log attached. 

Why does it try to connect to my server using the remote address? 

v3.5.47 won't load for me, as getting a java.io.IOException error. 

2nd log attached. 

Sat Aug 22 20:43:29.374 GMT+01:00 2026 Error sending request to https://remote_addr/emby/system/info/public?format=json: Canceled
java.io.IOException
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:72)
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
java.lang.Thread.run(Thread.java:923)

 

emby_android_1787426987435.txt

emby_android_1787427739587.txt

Edited Saturday at 07:56 PM by CBers

[FrostByte 5587]

.47 is slower for me, so seems fitting you can't even connect now since mine was really fast before

[Luke 42976]

2 hours ago, CBers said:

I've never understood why the Universal Android app takes so long to connect. 

The ATV app is so much quicker. 

I'm still on 3.4.45, but still over 30 seconds to get to the home screen. 

App log attached. 

Why does it try to connect to my server using the remote address? 

v3.5.47 won't load for me, as getting a java.io.IOException error. 

2nd log attached. 

Sat Aug 22 20:43:29.374 GMT+01:00 2026 Error sending request to https://remote_addr/emby/system/info/public?format=json: Canceled
java.io.IOException
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:72)
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
java.lang.Thread.run(Thread.java:923)

 

emby_android_1787426987435.txt 70.5 kB · 0 downloads

emby_android_1787427739587.txt 5.63 kB · 0 downloads

What exactly do you mean by won't load?

[Luke 42976]

53 minutes ago, FrostByte said:

.47 is slower for me, so seems fitting you can't even connect now since mine was really fast before

The difference is that the loading dialog is delayed by 800ms, but in order to avoid it looking like a flicker, it will stay up for at least 300ms even if the operation completes sooner than that. So if your connection succeeds at 900ms, it will wait to 1100ms.

Now that we have the 300ms hold, maybe we can bring the dialog delay back down to 600ms, because it is less likely that the connection will complete that fast, so therefore the hold will be less likely to occur.