Tus comentarios

Hey thanks for the info. I have merged your post together with another post of the same related issue. Are you using a custom ROM or unofficial release ROM? Please do let me know what you find out. Thanks!

Is your device running Android 4.3? If it is it might be worth trying to install an older version of XiiaLive where the BT metadata hack was enabled. The latest release now automatically disables the hack for devices running Android 4.3 and higher. The reason is that Android has now provided proper ways to send the metadata via legit API calls.

Alarms feature is available on the FREE and PRO versions. The set alarms and settings will need to be reprogramed when updating to PRO unfortunately. Hope that answers your questions.

Thanks for sharing. On Android 4.3 I started using the new Android APIs to send BT data properly. I have updated the app to use that on the last update. Previous older version I was using a hack to get metadata sent over BT. I'm wondering if the hack is still required... :/


Please let me know if the "Lock screen controls" is ON under settings->App control.

Thanks for your feedback. I think it would be a nice and interesting feature to have to allow setting how the metadata should be sent over BT. I will set this idea on our feature request list.


About surfing between favorites, Currently PREV/NEXT buttons on BT device move between favorite stations. It will show you the title of the favorite for 2 seconds before playback starts so you can actually keep pressing the PREV/NEXT until you find the favorite you want to play. It is not the best but tends to be useful.

Have you changed any settings on the app? Make sure "Lock screen controls" is ON under App control. The station name, song and artist information should be sent over AVCRP. Please check if the device music player bluetooth metadata works with your car stereo.

Thanks for the details about this issue. I'll take a look and see what is going on. Thanks!

Thanks for the image. It helped! I was able to resolve the issue but on our latest stream engine. The fix will possibly be released next month... I hope you can wait till then for the fix. Thanks!

Thanks for the details about this issue. I'll take a look and see what is going on. Thanks!