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.
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 bugsWhen 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!
To summarize this post:
Previous release of XiiaLive we decided to disable the Bluetooth AVRCP metadata "HACK" for Android versions 4.3 and greater. The reason was that since Android 4.3 Android OS made some APIs available to send metadata over Bluetooth using a legit API. However, it seems that some devices fail to properly support the new APIs and for that reason we have re-enabled the "HACK" on the latest release.
The "HACK" can be enabled if not already enabled here:
XiiaLive->Settings->App control->AVRCP metadata
When XiiaLive can't connect to a station, it would be nice to update the AVRCP data to indicate that.
It is a very neat idea. I have added this to our ideas/future features. Thanks for sharing!
since upgrading to CM 10.2 (Android 4.3) AVRCP has not worked, anyone else is having this issue? it works fine with Apollo Music player or other apps supporting AVRCP just not Xiialive. using the latest Pro version.
Since Android 4.3 bluetooth AVRCP metadata is sent via the same APIs used to update the lock screen player. Turning [OFF] lock screen controls will most likely cause metadata to stop being sent over AVRCP.
Please note that after Android 4.3 having lock screen controls and AVRCP metadata hack turned [ON] could cause issues. Please experiment with those two settings to see how your device behaves.
It works with other apps, just not XiiaLive Pro. Any Ideas?
Customer support service by UserEcho