+2
Player randomly stopped after turning off the screen
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
Servicio de atención al cliente por UserEcho
I have the same issue! I'm using xiialive pro on a samsung galaxy s4 and ever since the last firmware update the app keeps closing if the screen is off!
Can you create a bug report when it happens again and send it here? i wanna check your issues
You can go to Settings in Xiialive and select "bug report" to create a bug report file
I don't know what caused the app to close. I hope the developer will see this because the developers understand more logcat than me
Thanks for the logs. This issue could be caused by various things but since you are running Android 5.0.1 you might be having issues with a memory leak bug on Android.
This bug is causing Android to leak memory and after various days of your device usage the OS thinks it doesn't have memory so it starts killing apps running in the background without any warning.... I'm wondering if you are noticing anything similar to the user post here:
http://android.stackexchange.com/questions/93545/apps-are-automatically-closing-restarting-and-phone-is-running-slow
This is not true. Memory leaks was been fixed 2 years ago and the stopped bug was been fixed for lollipop after 3.3.1.3 release. The stopped bug still present on Android 4.1.2 ~ 4.4.4 and all useless apps are uninstalled and disabled
My device leaking? NO, your app leaking 130 MB of RAM. My device always have 1 GB free space no matter how long it was running
Stop lying to me and trying to get me to upgrade to 6.0.1, just to avoid fixing this bug. I have seen some developers telling me like that and no longer got any replies. I'll keep an eye on you.
Happened for me in Marshmallow too.Turning off battery optimization didn't help.
Hmm... this is very strange. Could you create a Bug report from Xiialive settings once it happen again?
Go to Settings -> Bug report and upload it to your free cloud service and share the link here. Also, tell your device model here. That would be helpful for developers
Didn't like Marshmallow, so sadly I cannot send any log.
ok, but can tell me your device model?
Samsung S5 G900F. Ran a custom rom based of an early stock which wasn't made for my region, so...
Ok, Thanks, so the devs don't have to tell me to reduce cache size to whatever...
That device is powerful and have 2 GB RAM, like my Sony Z3 Compact, running stock ROM and it has the same problem with screen off
Z3 is a nice powerful phone yes. Marshmallow too? Turning off battery optimization should make doze turn off when running that app, so it must be the app or Marshmallow then.
Anyway, I'm using VLC until the question is answered about the app being connected to a Facebook ip all the time.
No, my device is running Lollipop 5.1.1, because MM 6.0.1 just officially released and it has a lot of bugs and some features are missing.
This issue appear on any version above Android 4.1. The app is working perfectly on my low-end mini tablet running 4.0.4, have 512 MB RAM, and single-core, and never got any issues. I know this is very strange... but i have no idea why it never happen on 4.0.4. I will use my old mini tablet for now and maybe use Wi-Fi tether until it gets fixed.
To reply, click on the right-arrow button, instead post a new comment.
On my Samsung it has worked perfectly fine running Kitkat and Lollopop. Only Marshmallow that has caused problems. Cannot be easy for developers making apps for Android!
Okay
I have the same problem with my LG G3 running Android 5.1.1. i have contacted the devs about that and i hope they will wake uo
Could you create a Bug report from Xiialive settings once it happen again?
Go to Settings -> Bug report and upload it to your free cloud service and share the link here.
Update: Xiialive app instantly stopped while i switch to other apps on Nox Player. My PC is powerful and had enough RAM. Xiialive only cached 10 minutes...
https://drive.google.com/open?id=0BwHAZoD_DYAcOVNMNGkwdmE0b1U
@Ralph (support)
Update 2: This bug only happen when i play any station with 128kbps MP3 format. The player never stopped when i play station with 64kbps AAC
Update 3: I have listen to the 128 kbps station that does not have metadata for a week and have not got this bug yet.
Update 4: The player just stopped after i pressed the home button
bugreport.txt
Update 5: 4 weeks later, it happen again. I always reboot my device everyday. Devs and supporters, do not ignore me!