Please note that we are a team with one developer and one graphics designer. We like to personally answer posts but aren't always able to do so as quickly as we would like to. In order to help us become more efficient, please follow the steps below when posting new questions, ideas or bugs.
Please post under one of the following:
QUESTIONS OR IDEAS
If you have a question or idea, start by typing it in the box provided and search below under similar topics to see if you can find an answer. If you don’t find an answer then simply post a new question or idea.
BUGS
If you spotted a bug and you want to let us know about it, first try searching for OPEN bug posts with similar issues and add any details you think might help us with it. Also, make sure to up vote the OPEN bug post so we know how critical it is. If no OPEN bug posts are found simply post a new one.
Posting new bugs
When you post new bugs please give us as many details as you can! This will help us resolve issues quickly and easily.Common details we need:
- What device do you have?
- What OS version is it running?
- What happened?
- What did you expect to have happened?
- What steps reproduce the issue?
Don't have the app yet? Get XiiaLive or XiiaLive Pro now for Android! Or get XiiaLive for iOS!
Mark XiaaLive/Pro notifications as not sensitive
I use XiaaLive Pro on a Samsung Galaxy S4 (SCH-I545) running Android 5.0.1 (build I545VRUGOF1). I allow XiaaLive to show notifications on my (stock) lock screen, which is useful because I can use the controls while the phone is locked. However, when I set lock screen notifications to "Hide sensitive content", the controls on the XIaaLive Pro notification are hidden and a message to the effect of "content hidden" appears instead.
The controls for XiaaLive Pro and the name of the current stream are generally not sensitive information. Can you please modify the application so that the controls and stream name are not hidden regardless of whether the "Hide sensitive content" option is enabled in a device's Settings?
Thank you.
Hello Matt,
We've already fixed it. It will be included in next release.
Thanks for your help.
Best,
[XiiaLive Beta] Constant force closes with the latest beta on Nook Tablet
Notification sounds are delayed
Currently the notification sound is delayed for 2-3 seconds when skipping to the next track. If not looking at the screen, it's easy for user to think that the press was not registered.
I believe the notification sound in this case notifies of starting to download data but it would be nice if if it is played as soon as the button is pressed for an immediate feedback to avoid confusion. This is especially important while driving or using a headset and not looking at the screen.
Thanks,
Skipping to the next track we have a set delay before we actually trigger to play it. We added this delay to be able to see the next station name before it is played. This is useful for car stereos for example. It kinda let's you surf the tracks without changing the station.
I will set this request as planned since I'm thinking to add an option to turn off or change the delay time.
Hope this answers your question. :)
lower minimum alarm volume
Thanks
Release 3.3.1.7 now allows you to set alarm value to 5%.
Samplerate seems to be wrong for streams
I've been listening to an online radio station that has a 128k MP3 stream, and 32k and 64k AAC+ streams. The 128k stream shows a sample rate of 44.1kHz, while the 32 and 64k streams show a sample rate of 22.0kHz.
However, in iTunes, and Foobar players on a computer, all streams show as 44.1kHz. Is there something going on with the AAC+ streams in Xiia to reduce their sample rates, or are they simple being reported wrong on the screen?
The radio station I'm looking at is A Reason To Dance - Radio G!, but this seems to be true for any radio station streaming in AAC+ format that I've tested.
Buffer issues
The only way I found to really increase the buffer size (have a larger grey status bar) and avoid skips when driving is to setup my own icecast server and change the buffer in the server itself. But with that, I have another problem I'll try to explain you.
1/ I set the burst size (buffer) of my icecast server to :
<burst-size>393216</burst-size> (= 384 kb)
If the connection is lost during some seconds (which you can do with setting wifi off 5 seconds then on), everything works fine with the smart recovery ON : the stream continues
2/ I set the burst size to something bigger :
<burst-size>524288</burst-size> (= 512 kb)
Now the light grey bar is larger and buffer is good enough for me.
BUT if the connection is lost during some seconds, when the datas come back, the smart recovery will load again the whole buffer size. This will result in hearing once again a part of a song I just heared before the data connection was lost.
I don't know if it's clear enough as my english isn't perfect :)
To resume : how can I have a better buffer (= a bigger light grey bar)
and why when setting the server buffer size to something larger than 384 kb the smart recovery plays a part of a song 2 times when connection is back ?
If you want I can give you my server adresses to test
This was made on galaxy s3 with your last beta on a 48kbps aac+ stream
Thanks
Changed the look back recovery time to be larger. The fix will be part of the next release.
pocket change more than 6 minutes reward
Volume slider in favorites screen
I would love to see a volume slider at the bottom of the favorite screen, allowing the user convenient single touch access while staying in the quick station change view.
separately, it would be nice to have an option to keep the mode tabs open when in landscape mode rather than auto hiding it .Samsung devices that have a multi-view option also use the slide in from right gesture to access that menu and ithe two can conflict with each other.
great work on this app! It is one of the best!
Hello Simon,
thanks for sharing these suggestions. We will keep them in mind for next releases.
Thanks, again.
We think that having two separate volumes was very inconvenient for a lot of users. Essentially if the volume was too low you had to unlock the screen and raise the volume and at the same time lower the phones's volume.
**Update, we will add the separate volume control as an option under settings on the next update.
UPDATE:
Update v2.1.7 added new option to switch back to independent volume control.
Служба підтримки клієнтів працює на UserEcho