# Phone overheating. Connecting to Navidrome 0.53.3 **URL:** \ **Category:** Support\ **Tags:** handled\ **Created:** [November 21, 2024, 12:14pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951 "2024-11-21T12:14:16Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 21, 2024, 12:14pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/1 "2024-11-21T12:14:16Z")
## Issue description: After playing any music files via Symfonium for a short period of time my phone overheats and becomes hot to the touch. I’ve tried with default configuration and trying to enable and disable various options, but can’t seem to prevent this issue. I’ve attached my debug logs. ## Logs: Upload description: Dshawn ## Additional information:   Phone is a Samsung Galaxy S23 FE   ## Reproduction steps:   Nothing specific. Just using the app with default or custom settings overheats the phone.   ## Media provider: Subsonic ## Screenshots:       ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 21, 2024, 7:00pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/2 "2024-11-21T19:00:20Z")
I do not see anything special in the logs. Try to disable prefer internal decoder in case ffmpeg have some issues with your files. ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 22, 2024, 1:12am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/3 "2024-11-22T01:12:57Z")
I’ve disabled the internal decoder. Doesn’t seem to have made a difference. I ran the Ultrasonic client for 5 mins and captured the temperature for comparison. I did the same for Symfonium. There’s more than a 10 degree running difference as per CPU-Z. Anything else I could try? ![Symfonium](http://support.symfonium.app/uploads/default/original/2X/8/8f8c1ca0f86f4ab16a00415c273f415aa8a2e9e0.jpeg) ![Ultrasonic](http://support.symfonium.app/uploads/default/original/2X/c/cb595aaa30c9f8189caea0975738a7f9350cbde2.jpeg) ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 22, 2024, 7:33am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/4 "2024-11-22T07:33:17Z")
Provide a full bug report [Capture and read bug reports  |  Android Studio  |  Android Developers](https://developer.android.com/studio/debug/bug-report) and upload it to [https://upload.symfonium.app](https://upload.symfonium.app). Do you have some other apps like panoscrobbler or tasker that could try to react to something Symfonium do and cause this ? ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 23, 2024, 5:23am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/5 "2024-11-23T05:23:13Z")
I don’t have anything else that interacts with Symfonium or other apps. Full bug report has been submitted. ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 23, 2024, 9:23am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/6 "2024-11-23T09:23:45Z")
```auto CPU usage from 237139ms to 117480ms ago (2024-11-22 17:51:00.545 to 2024-11-22 17:53:00.205): 5.5% 1576/system_server: 3% user + 2.5% kernel / faults: 3866 minor 6 major 3.2% 4261/app.symfonik.music.player: 1.4% user + 1.8% kernel / faults: 139 minor ``` This is a little higher than normal, but very far from being able to overheat a device. ```auto 11-22 15:49:54.774 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service app.symfonik.music.player/app.symfonik.core.playback.service.PlayerService in 9491ms for mem-pressure-event 11-22 15:49:54.774 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 29491ms for mem-pressure-event 11-22 15:49:54.774 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service com.android.vending/com.google.android.finsky.contentfilterui.ContentFiltersService in 49491ms for mem-pressure-event 11-22 15:49:54.775 1000 1576 1647 W UsageStatsService: Unexpected activity event reported! (app.symfonik.music.player/app.symfonik.ui.StartActivity event : 23 instanceId : 161892821) 11-22 15:49:54.778 1000 1576 1647 W UsageStatsService: Unexpected activity event reported! (com.android.vending/com.google.android.finsky.activities.MainActivity event : 23 instanceId : 179884986) 11-22 15:49:54.784 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service app.symfonik.music.player/app.symfonik.core.playback.service.PlayerService in 481ms for mem-pressure-event 11-22 15:49:54.786 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 10481ms for mem-pressure-event 11-22 15:49:54.786 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service com.android.vending/com.google.android.finsky.contentfilterui.ContentFiltersService in 20481ms for mem-pressure-event 11-22 15:49:54.786 1000 1576 1647 W ActivityManager: Rescheduling restart of crashed service com.samsung.android.rubin.app/com.samsung.android.rubin.controller.KeepAliveService in 37602822ms for mem-pressure-event ``` Is interesting seems that some Samsung logger intercept things between Symfonium and the Play Store and causes issues. > What is Samsung Rubin? Samsung Rubin is the **customization service available on newer Samsung devices that can log valuable data which can be lawfully accessed using a mobile device forensic tool during a digital investigation**. You can maybe try to disable PlayStore or that Samsung service if it’s possible and see if it happens again. ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 23, 2024, 10:50am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/7 "2024-11-23T10:50:49Z")
I uninstalled the com.samsung.android.rubin.app via adb shell. I also disabled the Google Play store and Google Play services and ran Symfonium again. Hasn’t made a difference. Anything else I could try? ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 23, 2024, 11:11am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/8 "2024-11-23T11:11:42Z")
Enable logs in Symfonium and provide a new bug report when the app is playing and the phone is hot. ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 23, 2024, 11:21am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/9 "2024-11-23T11:21:46Z")
Done. Uploaded Symfonium logs and full bug report ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 23, 2024, 5:00pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/10 "2024-11-23T17:00:50Z")
Ok so this time it’s visible in the logs in the bug report. ```auto CPU usage from 235509ms to 89678ms ago (2024-11-23 20:14:48.231 to 2024-11-23 20:17:14.062): 106% 2373/app.symfonik.music.player: 83% user + 22% kernel / faults: 18605 minor 1496 major 18% 2129/com.android.bluetooth: 11% user + 7.7% kernel / faults: 519 minor 363 major 15% 999/audioserver: 14% user + 0.9% kernel / faults: 2 minor 200 major 10% 1320/system_server: 5.2% user + 5.4% kernel / faults: 69271 minor 6622 major ``` Symfonium use way too much tons of faults that should not happen and BT+Audio server use way too much too. One thing I can see is insanely slow queries, you can usually fix those in Settings/Advanced/ Cleanup internal states and wait at least 30 seconds. ```auto 2024-11-23 20:15:44.922 Error QueryBuilder Query: SELECT songs.file FROM playlists_entries INNER JOIN songs ON (playlists_entries.provider_id = songs.provider_id and playlists_entries.file = songs.file) WHERE playlists_entries.playlist_id = 1 AND songs.resume_point>0 ORDER BY songs.last_played DESC LIMIT 1 ('') [0 in 48416.05ms (RAW/false)] 2024-11-23 20:16:46.581 Error QueryBuilder Query: SELECT songs.file FROM playlists_entries INNER JOIN songs ON (playlists_entries.provider_id = songs.provider_id and playlists_entries.file = songs.file) WHERE playlists_entries.playlist_id = 2 AND songs.resume_point>0 ORDER BY songs.last_played DESC LIMIT 1 ('') [0 in 61656.89ms (RAW/false)] 2024-11-23 20:17:39.140 Error QueryBuilder Query: SELECT songs.file FROM playlists_entries INNER JOIN songs ON (playlists_entries.provider_id = songs.provider_id and playlists_entries.file = songs.file) WHERE playlists_entries.playlist_id = 3 AND songs.resume_point>0 ORDER BY songs.last_played DESC LIMIT 1 ('') [0 in 52558.19ms (RAW/false)] ``` Another thing is maybe related to Samsung FaceWidgetMusic maybe you can try to disable it ? And seems there was network issue at some point and retries. ```auto 2024-11-23 20:18:20.477 Error MusicPlayer DataSource: Error reading source (1/10/false), retrying [java.net.SocketException: Socket closed] 2024-11-23 20:18:21.479 Error MusicPlayer DataSource: Error reading source (2/10/false), retrying [java.net.SocketException: Socket closed] ``` Should be unrelated but at this time I lack ideas. Can you do some tests to try find if there’s something specific to repro? Like not play on BT. Play local file or cached files only. An last thing maybe try to disable the fade in / fade out in Settings/Playback/Transitions in case this is broken on some devices ? ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 24, 2024, 12:26am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/11 "2024-11-24T00:26:32Z")
I cleaned up internal states and disabled fade in and fade out. This seems to have resolved the issue. Thanks for the support. Will raise a new case if the issue re-occurs. Yeah I had a networking issue earlier which I resolved. Two other unrelated questions related to usage if you don’t mind. I have playlists that are greater than 6,000, however when I shuffle a large playlist, 6,000 is the max size. Any chance I can increase this? Also, can I force Symfonium to look at the original album directory for some type of image file? If the metadata is not correct and shows unknown album and unknown artist, a default image often appears for these songs. All my albums have an image in the same folder as the mp3s. ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 24, 2024, 8:29am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/12 "2024-11-24T08:29:08Z")
Can you try to enable back fade to the default values and see if it’s back and it’s some OS bug ? > [@Dshawn](#): > > Also, can I force Symfonium to look at the original album directory for some type of image file? If the metadata is not correct and shows unknown album and unknown artist, a default image often appears for these songs. All my albums have an image in the same folder as the mp3s. You said you use Subsonic in that case Symfonium only display the data send by the server you need to see with it. ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [November 24, 2024, 8:40am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/13 "2024-11-24T08:40:56Z")
> [@Dshawn](#): > > fade in and fade out Re-enabled fade in and fade out. Seems OK. Guessing cleaned up internal states fixed it. ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [November 24, 2024, 9:26am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/14 "2024-11-24T09:26:21Z")
Yes that’s strange that it impacts CPU and heat that much when it’s supposed to be just slow disk access to the database. But glad it was just that. Still need to find a way to detect why some devices triggers the need to rebuild the database. Have you checked [https://dontkillmyapp.com/](https://dontkillmyapp.com/) ? Maybe the device kills the app often leading to some corruption or something. ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [December 13, 2024, 5:03pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/15 "2024-12-13T17:03:26Z")
Seems like this issue resurfaced after upgrading to 11.5.0. Phone is overheating and quickly draining battery. Cleanup internal states and disabling fade in and fade out didn’t fix it this time. Uploaded debug logs and full log report. ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [December 13, 2024, 5:19pm UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/16 "2024-12-13T17:19:04Z")
```auto 48% 14261/app.symfonik.music.player: 38% user + 10% kernel / faults: 186201 minor 4964 major 28% 2290/com.android.bluetooth: 14% user + 14% kernel / faults: 2544 minor 1082 major 25% 967/audioserver: 24% user + 0.9% kernel / faults: 350 minor 566 major 20% 1016/surfaceflinger: 13% user + 6.8% kernel / faults: 2891 minor 311 major 15% 2607/irq/180-1084000: 0% user + 15% kernel 11% 9835/com.google.android.apps.photos: 6.6% user + 5% kernel / faults: 298735 minor 1801 major 10% 1325/system_server: 5.8% user + 4.1% kernel / faults: 61079 minor 17909 major 9.7% 925/android.hardware.bluetooth@1.0-service-qti: 1.7% user + 8% kernel 6.9% 930/android.hardware.graphics.composer@2.4-service: 3.2% user + 3.7% kernel / faults: 5 minor 5 major 5.8% 924/android.hardware.audio.service: 2% user + 3.7% kernel / faults: 2 minor 14 major ``` Everything takes too much CPU and triggers faults. Have you tried to reboot the phone? ---
**Author:** ![Dshawn](http://support.symfonium.app/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@Dshawn](http://support.symfonium.app/u/Dshawn)\ **Post date:** [December 14, 2024, 12:50am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/17 "2024-12-14T00:50:52Z")
Yes, have rebooted. Also uninstalled and reinstalled. ---
**Author:** ![Tolriq](http://support.symfonium.app/user_avatar/support.symfonium.app/tolriq/32/726_2.png) [@Tolriq](http://support.symfonium.app/u/Tolriq)\ **Post date:** [December 14, 2024, 8:11am UTC](http://support.symfonium.app/t/phone-overheating-connecting-to-navidrome-0-53-3/5951/18 "2024-12-14T08:11:39Z")
There’s nothing in the logs that could explain that and nothing changed too. The fact that it disappeared last time after doing things and is now backs, seems to indicate there’s something specific that triggers this. Tried reboot and not playing to BT? Or any idea what you could do that is specific?