Welcome to the official XiiaLive support forum! You can ask questions and get direct support from the developer.

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:
  1. What device do you have?
  2. What OS version is it running?
  3. What happened?
  4. What did you expect to have happened?
  5. What steps reproduce the issue?

Don't have the app yet? Get XiiaLive or XiiaLive Pro now for Android! Or get XiiaLive for iOS!
+2

How can I stop XIIA from stating up during my phone power on sequence?

jetrcmsp hace 7 años 0

XIIA starts up and runs down my battery when I power up my phone. it uses more power than any other app...even when I have not started it to listen.


How can I disable this function?

+2

https stream does not working in iOS.

Víctor hace 7 años 0

I have free iOS app, I tried to stream a link https doesn't work?

Do I need to buy the pro app?

My friend have Android App it works.


Thanks in advance.

+2

Use custom station name

Alex Zammar hace 8 años actualizado por Barry George hace 7 años 3

Hi, I'd like to also add to this topic. When I edit a name in the Favourites tab to show the actual name of the station, it still shows me the stream name when sharing and in the main screen. Is there any chance the custom name could be displayed here instead of the stream name?

Image 124

+2

where is the link to conservative talk radio that was there before?

alinmontreal hace 8 años 0

it seems you have taken away the conservative talk radio links. That's why I got your radio

+2
En revisión

please remove flashing / blinking ads

nonospam0 hace 8 años actualizado por Ralph hace 8 años 1

You provide a wonderful app. Understand you want revenue from adverts - but please remove flashing / blinking ads. I use your service at night and these ads are very intrusive - shows disrespect for your users.

+2
En revisión

Widget Favorite fails with INVALID URL on some stations.

Slow Loris hace 8 años actualizado hace 8 años 9

Device: Minix X8H-Plus

Android: 4.4.2


I create a favourite widget for the home screen, but when I click on it, it says, "INVALID URL"

The same channel listed in the favourites INSIDE the XiiaLive application can be started/played without any problems/errors.

The odd thing is, it's not all stations/play lists for example:


http://stream.16bit.fm:8000/cafe_mp3_128 plays fine in XiiaLive or as a home screen favourite widget. However,

http://stream.16bit.fm:8000/wine_channel_192 says "INVALID URL" as a favourite widget, but plays fine if selected from the favourite list within XiiaLive


+2
En revisión

Xiialive Pro version for older Android 2.3 systems

Thomas Wagner hace 8 años actualizado hace 8 años 2

Can I download / get the latest Xiialive Pro version (e.g. APK file), which works on older Android 2.3 systems? I assume the latest working Xiia version is 3.3.0.4, right?

P.S.: i bought the Pro version on Google Play.

+2

Player randomly stopped after turning off the screen

Nanren hace 9 años actualizado hace 8 años 24

it happen again after i turned off the screen 5 minutes later. I'm using Xiialive Pro 3.3.1.6


The player does randomly stop, no matter how long is the cache. the player also stopped at 5 minutes!


My device had enough RAM to remember up to 60 minutes


XiiaLive Pro=3.3.1.6 (30047) google
ANDROID_SDK_INT=17
ANDROID_SDK_RELEASE=4.2.2
MODEL=TAD-10063 MK2
MANUFACTURER=unknown
DEVICE=nuclear-inet
PRODUCT=nuclear_inet
CPU_ABI=armeabi-v7a
SETTINGS_DUMP={screen_timeout_option=0, notification_recovery_volume=0.0, ignore_audio_focus_enabled=true, alarm_fade_enabled=false, animation_enabled=false, connect_timeout=60000, notification_volume=0.0, headset_unplug_stop_enabled=false, stream_engine=1, media_remote_control_enabled=true, unlimited_retries_enabled=true, stream_cache_length=3000000, skin_theme=0, scan_random_enabled=false, player_next_prev_ctrl=1, scan_preview_duration=15000, bt_avrcp_hack_enabled=true, lock_screen_ctrls_enabled=false}


04-23 15:19:31.212 E/ActivityManager( 480): ANR in com.android.DroidLivePlayer:RemoteMediaService
04-23 15:19:31.212 E/ActivityManager(  480): Reason: Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }
04-23 15:19:31.212 E/ActivityManager(  480): Load: 3.72 / 3.3 / 3.24
04-23 15:19:31.212 E/ActivityManager(  480): CPU usage from 5433ms to 253ms ago:
04-23 15:19:31.212 E/ActivityManager(  480):   48% 480/system_server: 41% user + 6.5% kernel / faults: 15117 minor 20 major
04-23 15:19:31.212 E/ActivityManager(  480):   16% 89/mediaserver: 15% user + 1.5% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   12% 781/com.android.systemui: 11% user + 0.9% kernel / faults: 4361 minor 54 major
04-23 15:19:31.212 E/ActivityManager(  480):   3.5% 7258/zygote: 2.9% user + 0.5% kernel / faults: 3 minor
04-23 15:19:31.212 E/ActivityManager(  480):   2.7% 59/nandd: 0% user + 2.7% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   2.3% 60/nfmtd: 0% user + 2.3% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0.7% 914/com.kingroot.kinguser:service: 0.5% user + 0.1% kernel / faults: 511 minor 5 major
04-23 15:19:31.212 E/ActivityManager(  480):   0.3% 21/kswapd0: 0% user + 0.3% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0% 1//init: 0% user + 0% kernel / faults: 24 minor
04-23 15:19:31.212 E/ActivityManager(  480):   0.1% 6/rcu_kthread: 0% user + 0.1% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0% 57/usb-port-power-: 0% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0.1% 146/kuInotify: 0.1% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0.1% 2461/com.android.DroidLivePlayer: 0.1% user + 0% kernel / faults: 185 minor
04-23 15:19:31.212 E/ActivityManager(  480):   0% 7512/RTW_CMD_THREAD: 0% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   0% 15816/kworker/0:2: 0% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):  +0% 16050/procrank: 0% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480): 100% TOTAL: 77% user + 21% kernel + 0.7% iowait + 0.9% softirq
04-23 15:19:31.212 E/ActivityManager(  480): CPU usage from 1733ms to 2305ms later:
04-23 15:19:31.212 E/ActivityManager(  480):   65% 781/com.android.systemui: 61% user + 3.6% kernel / faults: 4600 minor
04-23 15:19:31.212 E/ActivityManager(  480):     65% 7287/Binder_3: 61% user + 3.6% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   16% 89/mediaserver: 16% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):     16% 246/AudioOut_2: 16% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   8.7% 60/nfmtd: 0% user + 8.7% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   5.3% 480/system_server: 1.7% user + 3.5% kernel / faults: 2 minor
04-23 15:19:31.212 E/ActivityManager(  480):     5.3% 511/ActivityManager: 3.5% user + 1.7% kernel
04-23 15:19:31.212 E/ActivityManager(  480):   3.7% 7258/com.android.DroidLivePlayer:RemoteMediaService: 3.7% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480):     1.8% 8101/oteMediaService: 1.8% user + 0% kernel
04-23 15:19:31.212 E/ActivityManager(  480): 100% TOTAL: 81% user + 18% kernel
04-23 15:19:31.212 W/ActivityManager(  480): Killing ProcessRecord{415670e8 7258:com.android.DroidLivePlayer:RemoteMediaService/u0a10058}: background ANR
04-23 15:19:31.292 D/dalvikvm(  781): GC_FOR_ALLOC freed 0K, 5% free 35236K/36720K, paused 109ms, total 109ms
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): stopOutput() output 2, stream 3, session 19
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): changeRefCount() stream 3, count 0
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): getNewDevice() selected device 0
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): setOutputDevice() output 2 device 0000 delayMs 190
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): setOutputDevice() prevDevice 0002
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): setOutputDevice() setting same device 0000 or null device for output 2
04-23 15:19:31.412 V/AudioPolicyManagerBase(   89): releaseOutput() 2
04-23 15:19:31.432 V/MediaPlayerService(   89): Client(10) destructor pid = 7258
04-23 15:19:31.432 V/MediaPlayerService(   89): disconnect(10) from pid 7258
04-23 15:19:31.442 D/dalvikvm(  781): GC_FOR_ALLOC freed 0K, 4% free 35722K/37208K, paused 142ms, total 142ms
04-23 15:19:31.482 V/AudioSink(   89): close
04-23 15:19:31.482 V/MediaPlayerService(   89): Client(11) destructor pid = 7258
04-23 15:19:31.482 V/MediaPlayerService(   89): disconnect(11) from pid 7258
04-23 15:19:31.482 V/AudioSink(   89): close
04-23 15:19:31.482 V/MediaPlayerService(   89): Client(12) destructor pid = 7258
04-23 15:19:31.482 V/MediaPlayerService(   89): disconnect(12) from pid 7258
04-23 15:19:31.492 V/AudioSink(   89): close
04-23 15:19:31.492 V/MediaPlayerService(   89): Client(13) destructor pid = 7258
04-23 15:19:31.492 V/MediaPlayerService(   89): disconnect(13) from pid 7258
04-23 15:19:31.492 V/AudioSink(   89): close
04-23 15:19:31.492 V/MediaPlayerService(   89): Client(14) destructor pid = 7258
04-23 15:19:31.492 V/MediaPlayerService(   89): disconnect(14) from pid 7258
04-23 15:19:31.492 V/AudioSink(   89): close
04-23 15:19:31.492 V/MediaPlayerService(   89): Client(15) destructor pid = 7258
04-23 15:19:31.492 V/MediaPlayerService(   89): disconnect(15) from pid 7258
04-23 15:19:31.492 V/AudioSink(   89): close
04-23 15:19:31.552 D/dalvikvm(  781): GC_FOR_ALLOC freed 0K, 4% free 36209K/37696K, paused 92ms, total 92ms
04-23 15:19:31.562 W/AudioService(  480):   AudioFocus   audio focus client died
04-23 15:19:31.562 D/dalvikvm(  480): GC_FOR_ALLOC freed 250K, 9% free 42209K/46276K, paused 278ms, total 279ms
04-23 15:19:31.562 I/dalvikvm-heap(  480): Grow heap (frag case) to 41.621MB for 393236-byte allocation
04-23 15:19:31.652 D/dalvikvm(  781): GC_FOR_ALLOC freed 0K, 4% free 36695K/38184K, paused 98ms, total 98ms
04-23 15:19:31.712 D/dalvikvm(  480): GC_FOR_ALLOC freed 257K, 10% free 42336K/46664K, paused 145ms, total 145ms
04-23 15:19:31.712 I/AudioService(  480):  AudioFocus  abandonAudioFocus(): removing entry for android.media.AudioManager@41249318com.vblast.xiialive.service.MediaService@4124f380
04-23 15:19:31.762 D/dalvikvm(  781): GC_FOR_ALLOC freed 0K, 4% free 37182K/38672K, paused 101ms, total 101ms
04-23 15:19:31.862 D/dalvikvm(  781): GC_FOR_ALLOC freed <1K, 4% free 37668K/39160K, paused 88ms, total 88ms
04-23 15:19:31.912 W/JavaBinder(  480): Binder has been finalized when calling linkToDeath() with recip=0x20100005)
04-23 15:19:31.912 D/dalvikvm(  480): GC_FOR_ALLOC freed 777K, 11% free 41816K/46664K, paused 196ms, total 196ms
04-23 15:19:31.912 I/ActivityManager(  480): Start proc com.google.android.gms.persistent for service com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService: pid=16057 uid=10008 gids={50008, 3003, 1007, 1028, 1015, 1006, 3002, 3001, 2001, 3006}
04-23 15:19:31.912 I/ActivityManager(  480): Process com.android.DroidLivePlayer:RemoteMediaService (pid 7258) has died.
04-23 15:19:31.912 W/ActivityManager(  480): Scheduling restart of crashed service com.android.DroidLivePlayer/com.vblast.xiialive.service.MediaService in 48193ms
+2
En revisión

An option to make choice what data wil be displayed via Bluetooth AVRCP

Michal Ochodlo hace 9 años actualizado por yaptichko hace 8 años 3

it will be fine to make choice what AVRCP data will display on cars audio. Now i can only see which song is playing on my cars audio. But i will better see the radiostations name. I have much of them in my list and switch between them also with the cars audio system but on the screen i dont see which station im listen. Only what song is now playing.

+2
En revisión

Bluetooth streaming broken on latest release (3.01 on ATT SGS3)

Peter Fischer hace 12 años en Bluetooth / Controls actualizado por Jona (Lead Developer) hace 12 años 0

When the stream finishes buffering, I heard audio for 2-3 seconds, before the audio stream cuts out.  XiiaLive continues to play through the active stream, but no audio is heard.  On previous versions, this was fine.


The audio seems to cut out right as the stream meta data rolls across the Android notification bar.  I'm not sure if this has anything to do with the newly added AVRCP support or not, but the timing looks very suspicious.  This problem does not occur when using headphones.


Additional Information:

Samsung Galaxy S3 

Android Version 4.04 - Stock/Unrooted

XiiaLive Pro version 3.01

Vehicle Subaru Legacy 2012



Respuesta
Jona (Lead Developer) hace 12 años

Sorry for the super delayed reply! 


First let's see if possibly the new AVRCP 1.3 hack broke BT streaming.

- Turn off the Icy-metadata option under Settings->Stream and try starting a new stream. Let me know if the issue still happens. This should cause AVRCP not to be used by the app since no metadata will be active.


After that test regardless if an issue still occurs try collecting the logs right after the issue happens when streaming. This hopefully will allow me to see a possible cause.

http://support.xiialive.com/topic/38494-how-to-collect-error-logs/