New Emby for Android 3.5.45 Released

[FrostByte 5579]

1 hour ago, Luke said:

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.

Thanks

[CBers 7678]

5 hours ago, Luke said:

What exactly do you mean by won't load?

It sat with a grey screen for 5 minutes until I force closed it, then I saw the java io error in the app log. 

Tried it again later and it did load to the hone screen, but it was very slow. 

This is one of the main reasons I can't use the app, as it is too slow to load and unreliable. 

Does the app not use the same connection methodology as the ATV app? 

If not, why not? 

 

Edited 6 hours ago by CBers

[Luke 42928]

1 hour ago, CBers said:

It sat with a grey screen for 5 minutes until I force closed it, then I saw the java io error in the app log. 

Tried it again later and it did load to the hone screen, but it was very slow. 

This is one of the main reasons I can't use the app, as it is too slow to load and unreliable. 

Does the app not use the same connection methodology as the ATV app? 

If not, why not? 

 

What was on the gray screen?

[CBers 7678]

4 hours ago, Luke said:

What was on the gray screen?

Nothing.