auto resume
xiialive pro dose not resume stream after loosing it during car driving even with all retry setings on. Why ?
Svar
Hello Rafal,
could you please say me the XiiaLive version? Also, which error did you receive?
Thanks,
i have the same problem. after i lose the connection, it does not resume i'm using Xiialive 3.3.1.3 Pro
I'm using Xiialive 3.3.1.3 Pro. The error shows - No network access. But after that there is no auto resume even with full network. Why ?
Thanks Rafal and Evildog for the answers,
please let me check what is wrong on it. I'll back soon with some response.
The "No network access" happens when you try to connect to a station and there is no network access. There will be no retry after that error.
So what is happening in your case is that the network connection is lost while you are streaming. Then the connection never returns and the stream engine times out trying to reconnect because the network was never restored. This causes the retry logic to kick in. It tries to connect again and "No network access" is returned causing the retry logic to end.
The smart recovery waits a generous 2 minutes and while it waits for it you will see "Waiting for network access".
I'll look into adding a setting to make the smart recovery timeout customizable.
Hope that helps!
Thank you for your explanation. Unfortunately this won't solve my problem. I paid for Pro version only because "auto retry" option was there. And for me it does not do the job. The stream engine should keep trying until network is available during driving like i.e. "TuneIn Radio" does on my old iPhone - this one got no problem. So from my point of view Xiialive Pro was a waste of my money. Don't you think ?
Kundesupport af UserEcho
The "No network access" happens when you try to connect to a station and there is no network access. There will be no retry after that error.
So what is happening in your case is that the network connection is lost while you are streaming. Then the connection never returns and the stream engine times out trying to reconnect because the network was never restored. This causes the retry logic to kick in. It tries to connect again and "No network access" is returned causing the retry logic to end.
The smart recovery waits a generous 2 minutes and while it waits for it you will see "Waiting for network access".
I'll look into adding a setting to make the smart recovery timeout customizable.
Hope that helps!