Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This surely has to be an Apple server side issue. People are reporting the same problem while running 13.4.1, 13.5.1, 13.6 beta, and 14 beta. Logging out of iCloud and iCloud Music Library, restarting, and logging back in has fixed the issue for some of us. For now anyway.

Update: Since doing the iCloud reset at noon things are back to normal.

IMG_1329.jpeg
 
Last edited:
  • Like
Reactions: RedBear and LizKat
I think now that I had this issue affect my iPhone SE while a large iCloud music library was getting itself sorted out onto a new MBA 2020 the past week or so (I have slow DSL and don't leave stuff running overnight so it took days once I was ready to prepare for use of Music on the new machine). I did notice that when that library update was done and allowing me to download Apple Music from my library that I knew I wanted to park on the 2020 MBA, my SE quit getting hot, which it had been doing periodically for no discernible reason. But I didn't actually think then to connect that issue to my laptop's iCloud library churn at the time. I was only wondering if the SE's battery was going bad on me, although the device was purchased as a refurb direct from Apple not all that long ago really, so doesn't have many cycles on it.

Maybe all that's a set of coincidences, but maybe not. Anyway I've turned off background refresh at the top level on all my mobile stuff now pending more info on this matter. It didn't seem to affect my iPhone XR which I only use as a WiFi device, but then I happened to have had the background refresh turned off on that one at top level anyway.
 
Same! 6s Plus has been going nuts, getting hot and apps locking up for several days, and it started before I applied the 13.5.1 update, which I had to manually download the multi-gigabyte full IPSW and apply with iTunes because the phone couldn’t complete the 299MB update after multiple tries and even leaving it to finish overnight. Kept getting stuck on “Preparing update” forever, but before that it would also take forever to try to download the relatively small update. Even applying the full update over USB cable with iTunes was a nightmare as it kept having problems getting through the part where it backs up the phone locally. I was surprised the update ever succeeded at all.

Certain apps like YouTube have been virtually unusable during this time period, acting as if I have a super bad connection but I’m on wifi and other iOS devices have no issues on the same network/internet connection. Many soft and hard reboots haven’t changed the problem. Turning Airplane Mode on and off fixed nothing. The phone even seemed to have unusual difficulty reconnecting to the wifi network while no other computers or devices in the house have any such issues. Phone so hot all the time whether it’s unplugged or charging. Only cools down when it’s completely powered off. And it all started suddenly a few days ago. There were no symptoms of battery issues or performance loss or apps locking up prior to that. Left the phone fully charged but unplugged one night and woke up to a dead phone that started charging at 1%. I assumed the battery was going bad but that kind of thing normally doesn’t just suddenly happen overnight.

If all this is fixed by something as simple as logging out of iCloud or reinstalling the Music app, I’m going to be extraordinarily irritated with Apple.
[automerge]1594229998[/automerge]


I have the issue and have iTunes Match.

Replying to myself with an update. Simply signing out of iCloud made YouTube suddenly work perfectly, streaming up to 1080p 60fps videos without so much as a stutter on a relatively slow DSL connection. Phone no longer hot. Logged back into iCloud and it started getting quite warm again, so tried also deleting Apple Music and restarting before reinstalling. Battery was rapidly waning again too. But at this point even though the phone is charging and playing YouTube full screen it’s remaining pretty cool. Even with the plastic case off I can barely feel any warmth. Before, with the case on, it was HOT right through the case.

It’s like a completely different phone. Ridiculous, Apple. I was actually on the verge of getting a new iPhone but I still have three payments left on this one, so I was holding off because I wanted to be able to keep it as a backup rather than be forced to trade it in early when it’s already 97% paid for. Thank goodness for this MacRumors article. Now I can keep waiting for the iPhone 12, or 13, or 14...
 
Because this is an issue with 13.5.1, and specifically implicates the Music app. Unless you think the Music app is using the contact tracing API?

The threads about the power drain show it's all over the place.

If the tracing code in the background doesn't have a hook for the battery and the battery app just "confused" it would explain the odd reporting
 
I'm running into this issue too.

iPhone 7 iOS 13.5.1 and iPad Mini 4 iPad OS 13.5.1

Using Music App with normal iTunes Store buyings and own Music synced via iTunes Match.
I can't download songs anymore, sometimes one or two directly after a reset finished but then downloads stuck, sometimes they begin new and new and never come to an end. In this condition the CPU load increase up to high and the device become abnormal very warm.
The bad thing is, even if I kill the Music App or Restart the Device the problem is still present. High CPU load drain battery.
The iPad Mini A8 CPU Dual Core goes up close to 100%, using other functions nearly impossible in this condition.
The iPhone 7 A10 CPU Quad Core goes up to 50%.
Both determined (permanently high CPU load) with the App System Status.

The effect looks like that the download trying still into the background (even the App is closed and seems to be not running), this keep the CPU hot and eating abnormal Battery power.

After 3 days try and error (with complete Reset of the iPad Mini 4 without any change) I found a way to get back normal CPU behavior.

1. stop any scheduled music download manually
2. kick the music app out of the memory
3. Hard reset the device
4. don't start any music download again.

Things I tried without succsess:
- turn music sync (iTunes Match) off and on
- delete Music App and reinstall it
- turn iCloud off and on
- complete erase iPad and restore from backup
- Music Download via Wifi or Cellular is equal, both stuck, but any other (Webbrowsing, App Updates, Video streaming) is no problem

If only 1-2 Song downloads manually queued then Music App stuck, CPU running hot, battery drain quickly again.

If I try music download via iTunes Store App instead, also stuck at the end of the download but message comes up "Download of titles not possible at the moment" (self translated from German) or "This title is not available in your region at the moment". Both message are definitive wrong because the same song downloads via macOS Mojave 10.14.6 (iTunes) or Catalina 10.15.5 (Music App) are possible.

Very annoying Bug :mad:
 
I experienced major battery drain with the App store app - up to 19 hours of use when it hasn't been open. I logged out of it and it seems to have resolved the issue. I'm on ios 12.4.1.
 
Maybe for you. But if you check Apple’s forum, it’s far from the only one app with troubles.

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

Data Source: Microstackshots
Shared Cache: 0x62bc000 82F111BD-756C-3998-A5C9-0C146B60A06E
Shared Cache: 0x23d94000 82F111BD-756C-3998-A5C9-0C146B60A06E

Command: healthd
Path: /System/Library/Frameworks/HealthKit.framework/healthd
Version: ??? (???)
PID: 37

Event: disk writes
Action taken: none
Writes: 1073.75 MB of file backed memory dirtied over 19052 seconds (56.36 KB per second average), exceeding limit of 12.43 KB per second over 86400 seconds
Writes limit: 1073.74 MB
Limit duration: 86400s
Writes caused: 1073.75 MB
Writes duration: 19052s
Duration: 19051.77s
Duration Sampled: 19050.94s
Steps: 1331 ( (10.49 MB/step))

Hardware model: iPhone12,5
Active cpus: 6


Heaviest stack for the target process:
105 ??? (libsystem_pthread.dylib + 14100) [0x18642f714]
105 ??? (libdispatch.dylib + 80168) [0x1863d8928]
105 ??? (libdispatch.dylib + 41668) [0x1863cf2c4]
84 ??? (libdispatch.dylib + 39004) [0x1863ce85c]
84 ??? (libdispatch.dylib + 13116) [0x1863c833c]
84 ??? (libdispatch.dylib + 7876) [0x1863c6ec4]
20 ??? (Foundation + 1176872) [0x186afe528]
20 ??? (Foundation + 1178216) [0x186afea68]
20 ??? (HealthDaemon + 2995736) [0x1ad61f618]
20 ??? (HealthDaemon + 4152476) [0x1ad739c9c]
20 ??? (HealthDaemon + 4152880) [0x1ad739e30]
20 ??? (HealthDaemon + 1771748) [0x1ad4f48e4]
20 ??? (HealthDaemon + 4153856) [0x1ad73a200]
20 ??? (HealthKit + 61820) [0x19a36117c]
20 ??? (HealthDaemon + 4154656) [0x1ad73a520]
20 ??? (HealthDaemon + 5461840) [0x1ad879750]
20 ??? (HealthDaemon + 50988) [0x1ad35072c]
20 ??? (HealthDaemon + 3094016) [0x1ad637600]
20 ??? (HealthDaemon + 1770188) [0x1ad4f42cc]
20 ??? (HealthDaemon + 5443788) [0x1ad8750cc]
20 ??? (HealthDaemon + 33464) [0x1ad34c2b8]
20 ??? (HealthDaemon + 686780) [0x1ad3ebabc]
20 ??? (HealthDaemon + 686972) [0x1ad3ebb7c]
20 ??? (libsqlite3.dylib + 38752) [0x188362760]
17 ??? (libsqlite3.dylib + 278972) [0x18839d1bc]
17 ??? (libsqlite3.dylib + 456692) [0x1883c87f4]
17 ??? (libsqlite3.dylib + 674520) [0x1883fdad8]
17 ??? (libsqlite3.dylib + 675000) [0x1883fdcb8]
17 ??? (libsqlite3.dylib + 548008) [0x1883deca8]
17 ??? (libsystem_kernel.dylib + 165896) [0x186510808]


Powerstats for: healthd [37]
UUID: 844B2434-62FE-3F1D-917E-DFD54DE82838
Path: /System/Library/Frameworks/HealthKit.framework/healthd
Architecture: arm64
Footprint: 14.12 MB -> 15.92 MB (+1840 KB) (max 21.92 MB )
Pageins: 1421 pages
Start time: 2020-07-07 07:25:57 -0700
End time: 2020-07-07 12:41:29 -0700
Num samples: 105 (8%)
CPU Time: 2368.059s
Primary state: 53 samples Non-Frontmost App, Non-Suppressed, Kernel mode, Effective Thread QoS Default, Requested Thread QoS Default, Override Thread QoS Unspecified
User Activity: 58 samples Idle, 47 samples Active
Power Source: 61 samples on Battery, 44 samples on AC
105 ??? (libsystem_pthread.dylib + 14100) [0x18642f714]
105 ??? (libdispatch.dylib + 80168) [0x1863d8928]
105 ??? (libdispatch.dylib + 41668) [0x1863cf2c4]
84 ??? (libdispatch.dylib + 39004) [0x1863ce85c]
84 ??? (libdispatch.dylib + 13116) [0x1863c833c]
84 ??? (libdispatch.dylib + 7876) [0x1863c6ec4]
20 ??? (Foundation + 1176872) [0x186afe528]
20 ??? (Foundation + 1178216) [0x186afea68]
20 ??? (HealthDaemon + 2995736) [0x1ad61f618]
20 ??? (HealthDaemon + 4152476) [0x1ad739c9c]
20 ??? (HealthDaemon + 4152880) [0x1ad739e30]
20 ??? (HealthDaemon + 1771748) [0x1ad4f48e4]
20 ??? (HealthDaemon + 4153856) [0x1ad73a200]
20 ??? (HealthKit + 61820) [0x19a36117c]
20 ??? (HealthDaemon + 4154656) [0x1ad73a520]
20 ??? (HealthDaemon + 5461840) [0x1ad879750]
20 ??? (HealthDaemon + 50988) [0x1ad35072c]
20 ??? (HealthDaemon + 3094016) [0x1ad637600]
20 ??? (HealthDaemon + 1770188) [0x1ad4f42cc]
20 ??? (HealthDaemon + 5443788) [0x1ad8750cc]
20 ??? (HealthDaemon + 33464) [0x1ad34c2b8]
20 ??? (HealthDaemon + 686780) [0x1ad3ebabc]
20 ??? (HealthDaemon + 686972) [0x1ad3ebb7c]
20 ??? (libsqlite3.dylib + 38752) [0x188362760]
17 ??? (libsqlite3.dylib + 278972) [0x18839d1bc]
17 ??? (libsqlite3.dylib + 456692) [0x1883c87f4]
17 ??? (libsqlite3.dylib + 674520) [0x1883fdad8]
17 ??? (libsqlite3.dylib + 675000) [0x1883fdcb8]
17 ??? (libsqlite3.dylib + 548008) [0x1883deca8]
17 ??? (libsystem_kernel.dylib + 165896) [0x186510808]
9 <Effective Thread QoS Background, Requested Thread QoS Background>
8 <Requested Thread QoS Background>
3 ??? (libsqlite3.dylib + 277168) [0x18839cab0]
3 ??? (libsqlite3.dylib + 338488) [0x1883aba38]
3 ??? (libsqlite3.dylib + 151952) [0x18837e190]
3 ??? (libsqlite3.dylib + 370096) [0x1883b35b0]
3 ??? (libsqlite3.dylib + 453620) [0x1883c7bf4]
3 ??? (libsqlite3.dylib + 783756) [0x18841858c]
3 ??? (libsystem_kernel.dylib + 165896) [0x186510808]
2 <Effective Thread QoS Background, Requested Thread QoS Background>
1 <Requested Thread QoS Background>

....

------


{"share_with_app_devs":1,"app_version":"","bug_type":"202","timestamp":"2020-07-08 09:55:37.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":"AB9DAC73-B6D1-474A-B2F9-235D09B84B40","app_name":"healthd","name":"healthd"}
Date/Time: 2020-07-08 09:53:50 -0700
End time: 2020-07-08 09:55:36 -0700
OS Version: iPhone OS 13.5.1 (Build 17F80)
Architecture: arm64e
Report Version: 29
Incident Identifier: AB9DAC73-B6D1-474A-B2F9-235D09B84B40

Data Source: Microstackshots
Shared Cache: 0x62bc000 82F111BD-756C-3998-A5C9-0C146B60A06E

Command: healthd
Path: /System/Library/Frameworks/HealthKit.framework/healthd
Version: ??? (???)
PID: 2524

Event: cpu usage
Action taken: none
CPU: 90 seconds cpu time over 107 seconds (84% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit: 90s
Limit duration: 180s
CPU used: 90s
CPU duration: 107s
Duration: 106.89s
Duration Sampled: 32.81s
Steps: 34

Hardware model: iPhone12,5
Active cpus: 6


Heaviest stack for the target process:
31 ??? (libsystem_pthread.dylib + 14100) [0x18642f714]
31 ??? (libdispatch.dylib + 80168) [0x1863d8928]
31 ??? (libdispatch.dylib + 41668) [0x1863cf2c4]
31 ??? (libdispatch.dylib + 39336) [0x1863ce9a8]
31 ??? (libdispatch.dylib + 13116) [0x1863c833c]
31 ??? (libdispatch.dylib + 7876) [0x1863c6ec4]
31 ??? (IDS + 487976) [0x18ceb6228]
31 ??? (IDS + 505828) [0x18ceba7e4]
31 ??? (HealthDaemon + 399968) [0x1ad3a5a60]
31 ??? (HealthDaemon + 500232) [0x1ad3be208]
31 ??? (HealthDaemon + 372552) [0x1ad39ef48]
31 ??? (HealthDaemon + 41928) [0x1ad34e3c8]
31 ??? (HealthDaemon + 42268) [0x1ad34e51c]
31 ??? (HealthDaemon + 43044) [0x1ad34e824]
31 ??? (HealthDaemon + 701792) [0x1ad3ef560]
31 ??? (libsqlite3.dylib + 277168) [0x18839cab0]
15 ??? (libsqlite3.dylib + 284276) [0x18839e674]
14 ??? (libsqlite3.dylib + 830728) [0x188423d08]
14 ??? (libsqlite3.dylib + 351072) [0x1883aeb60]
14 ??? (libsqlite3.dylib + 826536) [0x188422ca8]
9 ??? (libsqlite3.dylib + 788372) [0x188419794]
9 ??? (libsqlite3.dylib + 177948) [0x18838471c]
9 ??? (libsqlite3.dylib + 32192) [0x188360dc0]
9 ??? (libsystem_kernel.dylib + 168096) [0x1865110a0]


Powerstats for: healthd [2524]
UUID: 844B2434-62FE-3F1D-917E-DFD54DE82838
Path: /System/Library/Frameworks/HealthKit.framework/healthd
Architecture: arm64
Footprint: 11.98 MB -> 13.56 MB (+1616 KB)
Start time: 2020-07-08 09:55:03 -0700
End time: 2020-07-08 09:55:36 -0700
Num samples: 31 (91%)
CPU Time: 32.655s
Primary state: 24 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS Default, Requested Thread QoS Default, Override Thread QoS Unspecified
User Activity: 31 samples Idle, 0 samples Active
Power Source: 31 samples on Battery, 0 samples on AC
31 ??? (libsystem_pthread.dylib + 14100) [0x18642f714]
31 ??? (libdispatch.dylib + 80168) [0x1863d8928]
31 ??? (libdispatch.dylib + 41668) [0x1863cf2c4]
31 ??? (libdispatch.dylib + 39336) [0x1863ce9a8]
31 ??? (libdispatch.dylib + 13116) [0x1863c833c]
31 ??? (libdispatch.dylib + 7876) [0x1863c6ec4]
31 ??? (IDS + 487976) [0x18ceb6228]
31 ??? (IDS + 505828) [0x18ceba7e4]
31 ??? (HealthDaemon + 399968) [0x1ad3a5a60]
31 ??? (HealthDaemon + 500232) [0x1ad3be208]
31 ??? (HealthDaemon + 372552) [0x1ad39ef48]
31 ??? (HealthDaemon + 41928) [0x1ad34e3c8]
31 ??? (HealthDaemon + 42268) [0x1ad34e51c]
31 ??? (HealthDaemon + 43044) [0x1ad34e824]
31 ??? (HealthDaemon + 701792) [0x1ad3ef560]
31 ??? (libsqlite3.dylib + 277168) [0x18839cab0]
15 ??? (libsqlite3.dylib + 284276) [0x18839e674]
14 ??? (libsqlite3.dylib + 830728) [0x188423d08]
14 ??? (libsqlite3.dylib + 351072) [0x1883aeb60]
14 ??? (libsqlite3.dylib + 826536) [0x188422ca8]
9 ??? (libsqlite3.dylib + 788372) [0x188419794]
9 ??? (libsqlite3.dylib + 177948) [0x18838471c]
9 ??? (libsqlite3.dylib + 32192) [0x188360dc0]
9 ??? (libsystem_kernel.dylib + 168096) [0x1865110a0]
6 <Kernel mode>
4 ??? (libsqlite3.dylib + 787988) [0x188419614]
2 ??? (libsqlite3.dylib + 175196) [0x188383c5c]
1 ??? (libsqlite3.dylib + 1076380) [0x18845fc9c]
1 ??? (libsqlite3.dylib + 1076372) [0x18845fc94]
1 ??? (libsqlite3.dylib + 175332) [0x188383ce4]
1 ??? (libsqlite3.dylib + 1076428) [0x18845fccc]
1 ??? (libsqlite3.dylib + 175196) [0x188383c5c]
1 ??? (libsqlite3.dylib + 788540) [0x18841983c]
1 ??? (libsystem_platform.dylib + 23948) [0x18642ad8c]
1 <Kernel mode>
1 ??? (libsqlite3.dylib + 350888) [0x1883aeaa8]
2 ??? (libsqlite3.dylib + 302608) [0x1883a2e10]
2 ??? (libsqlite3.dylib + 299424) [0x1883a21a0]
1 ??? (libsqlite3.dylib + 824608) [0x188422520]
1 ??? (libsystem_platform.dylib + 22992) [0x18642a9d0]
1 ??? (libsqlite3.dylib + 391644) [0x1883b89dc]
1 ??? (libsqlite3.dylib + 391500) [0x1883b894c]
1 ??? (libsqlite3.dylib + 391340) [0x1883b88ac]
1 ??? (libsqlite3.dylib + 350844) [0x1883aea7c]
1 ??? (libsqlite3.dylib + 329160) [0x1883a95c8]
1 ??? (libsqlite3.dylib + 328892) [0x1883a94bc]
1 ??? (libsqlite3.dylib + 312312) [0x1883a53f8]
1 ??? (libsqlite3.dylib + 312288) [0x1883a53e0]
1 ??? (libsqlite3.dylib + 304604) [0x1883a35dc]
1 ??? (libsqlite3.dylib + 283336) [0x18839e2c8]
1 ??? (libsqlite3.dylib + 283240) [0x18839e268]
1 ??? (libsqlite3.dylib + 283228) [0x18839e25c]
 
My iPhone 10 died on me for the last 2 nights. Battery was over 50% at midnight. 90% battery health. It never ever happened before. I was horrified as the phone also acts as my work pager and I was on-call for ICU and trauma. Battery use showed Viber and WhatsApp as main energy users. I will put it in charger for the night from now on. Apple please fix the issue.
 
  • Like
Reactions: v3nt
This reinforces my decision, at least for now, to have uninstalled the music app from my iPhone XR. The battery drain issue, according to my observations, pre-dates 13.5.1 to some degree. I was a heavy user of Music, but the interface, after hitting a sweet spot a few months back, had become noticeably buggy and a little ragged in early spring of this year when I uninstalled it. Spotify, meanwhile, continues to improve. After a many hours of playing for the past day, Spotify battery usage is at 22% on my XR. The other ways Spotify has won me over are very good sound quality at the highest setting, increased library size, notably improved queueing, and the huge number of interesting playlists available (particularly in the classical genre, which is my main focus) which enhance discovery, the particular joy of many classical fans.
 
  • Like
Reactions: Albertomac77
Having the same issue with the Music app. The Music app keeps trying to download songs I don’t want and the Battery screen says it’s been in use 14+ hours. Force quitting Music does not help. About a week ago I started needing to charge my phone 3 times a day. This is ridiculous, hopefully Apple releases a fix soon.
 
I use iTunes Match, and I have the issue.

I believe the assumptions about a server side issue are correct. I typically manually download a couple of playlists to my iPhone for offline listening. For the past couple of days I haven't been able to download the songs in any of my playlists. It looks like the phone starts to download a song, then fails and keeps retrying. I might be able to download a few songs, but the majority won't download. They don't time out and give an error or anything, the app just keeps trying to download them, which I think is where the background utilization/hot iPhone issue is happening.

My phone got so hot one day the flash wouldn't work until I was able to cool the device down.

It's now 10:00 AM. I unplugged my iPhone at 7:00 AM with 100% charge and haven't used it much today. I'm at 57% battery. I have a iPhone SE 2020.
Same thing here; I have iTunes Match and see huge battery drain; I turn off access to songs in the cloud and the battery performance is good, as before all this; also lately (some days ago) I haven't been able to download songs (every now and then I could download some but then later it fails again and again).
 
I don't know if this is related, I checked this background activity and on my phone it showed the KMB app (only relevant to users in HK) had 19hrs of background activity within the last day. Doesn't seem to affect the battery though, as it is just an app for bus schedules.

Turning off the background refresh of that app helped a lot.
 
24 hours later and *fingers crossed* my iPhone seems to be behaving. In my case, the music app was stuck trying to download a new album onto my phone. I deleted the stuck downloads, hard reset the phone and the music app has behaved ever since.
 
Well I thought the background refresh would resolve it... Maybe it did not. I deleted and re-installed the app, let's see...
 
My iPhone 11 Pro Max is experiencing the same issue. Apple better fix it soon. Unacceptable bugs from a company that prides itself on having perfect software (and hardware too, of course).
 
Same issue here too. Apple Support aren't interested in solving. Only suggest reinstalling to factory settings!
Deleted Music app and gone to spotify, battery now working normally
 
Had this for two days running earlier this week and had already identified the Music App as being the culprit - turned off automatic updates for Music and problem seemed to go.
 
Yep, the super battery drain suddenly started four days ago when I opened the Apple Music app on my iPhone 11 Pro 13.5.1 for the first time in months to download some already purchased songs from years ago. I tried everything listed here and on the Apple discussion board, but the Music app continues to run in the background 24 hours a day. Haven't deleted the app yet, though, as I'm hoping Apple will release a fix??
Yesterday I deleted and re-installed (twice). First time it didn't seem to do anything. Second time, it seems to have fixed it.You'll have to re-download everything though.
 
hmmm...I thought my battery was dying on my older iphone, but the battery did not show any apps consuming power than my use.
 
I had this... I had deleted the free U2 album in Music - for some reason it was trying to download it again and stuck.

Problem solved.
 
A significant minority of iPhone users
Maybe if you add all the iPad users you get a significant multitude of users!😄
[automerge]1594309502[/automerge]
I’ll ask again and re-phrase. Does everyone with this issue subscribe to iTunes Match?
Yes, I'm a subscriber but for me Music wasn't the culprit
My iPad Pro 10.5" , 1 year old , it has been replaced by Apple after a diagnostic test and a senior engineer decided it was the right step to follow. Other users I know had their devices replaced as well.
Mine worked fine till beginning of June when I updated it to iPadOS 13.5.1.
I guess for someone is ruining the battery with no chance of recovery
The newer is working ok but still need a force restart to fully recharge every 2 or 3 days. Definitely is a a terrible update that need to be fixed by Apple. I wonder why it takes so long.:rolleyes:
 
Last edited:
I was wondering why my iPhone 11, which typically lasts all day, was getting below 20% by mid-afternoon while primarily being used to play downloaded Apple Music albums via bluetooth!

I agree that this is more than just Apple Music, though...my iPad mini 5 was burning up as soon as I turned it on this morning, despite not having used it for Music in over a week. I quit Google Maps and Google Earth (which I had not used since yesterday) and it cooled quickly.
 
I turned off iCloud music library. Then signed out of iCloud completely. Restarted phone. Signed back in to iCloud and iCloud music library. Let everything sync. So far that seems to have fixed the issue.
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.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.