For me, Apple Music never showed up under "usage," (Not sure if this matters..if its hidden and still sucking up battery life??)It’s not only the Music app, since 13.5 a lot of apps suffer of constant background activity. You can check this subject on Apple forum.
Same exact problem on my end! I noticed the battery was draining faster the past week, but it really threw up a red flag yesterday morning, even worse this morning (had alarm set, phone off charger), 30% drop in 5 1/2 hours? That has never happened.I noticed battery drain right after updating my iPhone X to 13.5.1. I haven't seen anything unusual with music app but today noticed that Dropbox had almost 9 hours of background usage even though I had disabled background app refresh for Dropbox and hadn't used it on screen either for weeks.![]()
There seem to be general issue with Core Data CPU overuse that's been happening with many apps - health, mail etc - since a while - example:
-----
{"share_with_app_devs":1,"app_version":"","bug_type":"145","timestamp":"2020-07-07 12:41:32.00 -0700","os_version":"iPhone OS 13.5.1 (17F80)","slice_uuid":"844B2434-62FE-3F1D-917E-DFD54DE82838","is_first_party":1,"build_version":"","incident_id":"E28B1E3D-D653-4A3B-A496-2CF4914609D3","app_name":"healthd","name":"healthd"}
Date/Time: 2020-07-07 07:23:58 -0700
End time: 2020-07-07 12:41:29 -0700
OS Version: iPhone OS 13.5.1 (Build 17F80)
Architecture: arm64e
Report Version: 29
Incident Identifier: E28B1E3D-D653-4A3B-A496-2CF4914609D3
This is totally unrelated and the usage shown is so low in comparison that it is probably just normal behaviour of the app.For me, Apple Music never showed up under "usage," (Not sure if this matters..if its hidden and still sucking up battery life??)
After seeing a much heavier battery drop when I would go to the store, (dropping to 85-90% within 1/2 hr. - not normal) and especially a massive battery drop of 25-30% the past 2 nights..basically 5 hrs with NO screen on, I saw that Dropbox was constantly running in the background all day/night. Even when I turned off "Background refresh." Before this 13.1.5, I never had it this bad. Maybe a 3-5% drop overnight at the most.
I deleted the Dropbox app, I'll see what happens.
View attachment 932347
[automerge]1594335334[/automerge]
Same exact problem on my end! I noticed the battery was draining faster the past week, but it really threw up a red flag yesterday morning, even worse this morning (had alarm set, phone off charger), 30% drop in 5 1/2 hours? That has never happened.
Saw a post on Reddit about Dropbox and battery on 13.1.5....also this Apple Music hangup here.
For me Dropbox looks like it was the issue running constantly in the background day/night even when I shut off "Background app refresh."
Ended up deleting the app for now.
![]()
Worked for me too - Thank you!Worked like a charm (although it's always a pain to turn off/on iCloud). Music is no longer running in the background constantly, and no further battery loss.
This is totally unrelated and the usage shown is so low in comparison that it is probably just normal behaviour of the app.
I'm so glad I got off the update train at 13.4.1.
Y'all are suckers 😂
I'm so glad I got off the update train at 13.4.1.
Y'all are suckers 😂
[automerge]1594223474[/automerge]
Download the AAAsilence song, or make your own. Problem solved. I did this 7 years ago.
[automerge]1594223879[/automerge]
Interesting no one has brought up the virus contact tracing that was added in 13.5
It's the big change from 13.4
They must have left the server rooms keys in kids hands.... 🤪everything is falling apart @ AppleThe spook is over!
Apple must have done something at the servers in the backend.
Everything is working normally again, different than a few days ago the Music Downloads putting iPhone and iPad out of action.
No more stucking at downloads via the Music app today!
iCloud synchronization (iTunes Match) works normally again.
This afternoon I could download 1350 songs from two playlists in less than a hour.
A total of 11.5 GB without any hanging or error message. No excessive CPU load, no abnormal increase of heat.
Even the iPad Mini 4 with it's old A8 CPU operating normally with other tasks during the downloads.
WTF Apple!
So it obviously had nothing to do with the update to 13.5.1 or any configuration or hardware problem.
This Annoyance was really unnecessary, I deleted and set up new my iPad completely for nothing. I should had rather just waiting a week.
I did see the improvement immediately after disconnecting/connecting from iCloud yesterday at around 9pm EST. It could be a coincidence with server fix that happened at the same time. For me too it seems like this was backend-related, more than related to the update to 13.5.1.This issue seems to have *spontaneously* stopped for me. Given how it started out of nowhere, without my using Apple Music, and it now seems to have stopped without my doing anything to fix it, I strongly believe this was a server side issue that Apple fixed. Did anyone else see this resolve itself this past weekend?
Hi Everyone,
I spent hours on the phone with a senior Apple tech and was asked to reset settings, that did not work. So I reset and erased all data. I then restored from iCloud and everything is working perfectly now. No more battery drain by Music. Hope this helps.
This issue seems to have *spontaneously* stopped for me. Given how it started out of nowhere, without my using Apple Music, and it now seems to have stopped without my doing anything to fix it, I strongly believe this was a server side issue that Apple fixed. Did anyone else see this resolve itself this past weekend?
So, I've been having this issue on and off for the past few weeks and I finally did a search to find this story. Some folks on this thread are saying that problem has stopped for them but for me it's still happening, or at least it's started again today. Has anyone else experienced it starting up again?
I subscribe to iTunes Match (because that seems to be the only danged way to get anything to sync to my phone at all anymore), and just as a test I tried disabling and reenabling library sync (again) to see if that helps anything.