Hello Apple team and community, I’m reporting a critical issue affecting iPhone 13 (128 GB) on iOS 26 Public Beta 3. Problem Summary: • Device stays stuck at 1% battery, even while charging • Battery Health shows 0% in Settings • Phone reboots every 5 minutes while unplugged • Only works when connected to power • Cannot update, charge properly, or maintain uptime Additional Context: • The issue appeared immediately after installing iOS 26 beta 3 • Affected devices often have a replaced battery (even official or high-quality replacements) • Seems to be a software validation bug related to battery firmware • Reported by many users across Reddit, Apple Forums, and Twitter — but not listed in Known Issues What Has Been Tried: • Recovery Mode / Safe charging / Clean install (same version) – no effect • Third-party repair tools (ReiBoot, 3uTools) — partial workaround • Jailbreak with Nugget or iCleaner to disable crash daemons – temporarily helps • Apple Support suggested full device replacement (!) ⸻ Request: Please investigate and acknowledge this issue. This bug renders devices unusable for users with legitimate battery replacements — we need a fix in an upcoming beta.

We are experiencing abnormal battery drain during sleep on several machines that installed our product. The affected devices appear to enter and exit sleep repeatedly every few seconds, even though the system logs show no new wake request reasons or changes in wake timers. Symptoms: Battery drops ~1% every ~15–20 minutes overnight. pmset -g log shows repeated "Entering Sleep" and "Wake Requests" events every few seconds. Wake requests remain unchanged between cycles and are scheduled far into the future (i.e. 20+ minutes later), yet the log lines keep repeating. On healthy machines, the same wake request entries appear only once every 20–30 minutes as expected, with minimal battery drop during sleep (~1% in 9 hours). What we've checked: No user activity (system lid closed, device idle). No significant pmset -g assertions; only powerd and bluetoothd are holding expected PreventUserIdleSystemSleep. pmset -g on affected machines shows sleep set to 0, likely due to sleep prevented by powerd, bluetoothd. No third-party daemons are holding assertions or logging excessive activity. Sample Logs from Affected Machine: 2025-06-28 21:57:29 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:76%) 3 secs 2025-06-28 21:57:31 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:29 ...] 2025-06-28 21:57:38 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:76%) 3 secs 2025-06-28 21:57:40 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:38 ...] 2025-06-28 21:57:47 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:75%) 3 secs 2025-06-28 21:57:49 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:47 ...] The only change in logs is the wakeAt timestamp being slightly updated . The wake requests themselves (process, type, deltaSecs) remain identical. Yet, the system keeps entering/exiting sleep every few seconds, which leads to power drain. We would appreciate your help in identifying: Why the sleep/wake cycles are repeating every few seconds on these machines. Whether this behavior is expected under certain conditions or indicates a regression or misbehavior in power management. How we can trace what exactly is triggering the repeated wake (e.g., a subsystem, implicit assertion, etc.). Whether there are unified log predicates or private logging options to further trace the root cause (e.g., process holding IO or waking CPU without explicit assertion). We can provide access to full logs, configuration profiles, and system diagnostics if needed.

After installing iOS 26 Developer Beta on my iPhone 13 mini, I encountered a critical battery issue. The battery percentage was stuck at 1%, and the phone could only be used while continuously plugged in. Despite the low reading, the device remained fully functional — I could use apps, navigate, and perform tasks normally. However, the battery indicator never rose above 1%, and the Battery Health section in Settings showed 0% Maximum Capacity, which is inaccurate. I did not allow the phone to fully discharge, out of fear that it might not turn back on. Restarting the phone and changing cables or chargers had no effect. After restoring the device to iOS 18.7.2 using DFU mode, the issue disappeared entirely — the battery percentage behaved normally again and the health section showed the correct value (about 100%). Observed behavior: • Battery percentage frozen at 1% • Maximum Capacity reported as 0% • Device only functional while connected to power • Issue resolved immediately after restoring to iOS 18 Temporary solution: A DFU restore to iOS 18 (18.5 22F76) immediately resolved the issue. The battery percentage and health readings returned to normal. Additional information: • Charger used: Official Apple 20W USB-C charger • Cable used: Apple USB-C to Lightning cable • Battery health after restore: 100% (replaced)

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design, hoping for the best. Thanks. My FB-FB18327769

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design,hoping for the best. Thanks.

I have installed WATCHOS 26 Developers Beta in my Apple Watch 6 after installation I found that the battery drains after two hours Now i can not remove 26 and go back to earlier version any ideas

When developing an iOS app that monitors or transmits the battery percentage (using UIDevice.current.batteryLevel), often expect to get updates for every 1% change in battery. However, on iOS, the batteryLevel property only updates in steps of approximately 5%. For example, the value jumps from 1.0 (100%) to 0.95 (95%), then to 0.90 (90%), and so on. It does not report intermediate values like 0.99, 0.98, etc.

On iOS17, UIDevice.current.batteryLevel is returning values rounded to 0.05, such as 1, 0.95, 0.9.

Hello, Can anyone tell me what this means? Or if it's normal? I'm seeing about 10% battery drain per day on sleep, and pmset -g log shows wakes nearly every minute. 2025-06-10 17:10:35 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 5 secs 2025-06-10 17:10:43 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:13:49 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 8 secs 2025-06-10 17:14:01 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:14:10 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:15:01 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:16:31 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs 2025-06-10 17:18:07 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:94%) 6 secs Looking at one section of them: 2025-06-10 22:00:46 -0700 DarkWake DarkWake from Deep Idle [CDNP] : due to smc.70070000 wifibt SMC.OutboxNotEmpty/ Using BATT (Charge:90%) 6 secs 2025-06-10 22:00:46 -0700 WakeDetails DriverReason:smc.70070000 - DriverDetails: DriverReason:wifibt - DriverDetails: DriverReason:SMC.OutboxNotEmpty - DriverDetails: 2025-06-10 22:00:46 -0700 HibernateStats hibmode=3 standbydelaylow=0 standbydelayhigh=0 35177 2025-06-10 22:00:46 -0700 WakeTime WakeTime: 0.094 sec 2025-06-10 22:00:46 -0700 Kernel Client Acks Delays to Sleep notifications: [Port-USB-C driver is slow(msg: SetState to 0)(60 ms)] 2025-06-10 22:00:46 -0700 Kernel Client Acks Delays to Wake notifications: [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(121 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(59 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(120 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(123 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(116 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [powerd is slow(5915 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(64 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(78 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(78 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(119 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(122 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(117 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(76 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(76 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(119 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [Codec Output driver is slow(msg: DidChangeState to 1)(76 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(118 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(121 ms)] [Port-USB-C driver is slow(msg: SetState to 0)(58 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(77 ms)] [Codec Output driver is slow(msg: WillChangeState to 1)(77 ms)] [AppleConvergedIPCOLYBTControl driver is slow(msg: SetState to 1)(117 ms)] [AppleMultiFunctionManager driver is slow(msg: SetState to 1)(120 ms)] [RTBuddy(ANS2) driver is slow(msg: SetState to 2)(68 ms)] [AppleCS42L84Audio driver is slow(msg: DidChangeState to 1)(76 ms)] 2025-06-10 22:00:48 -0700 com.apple.sleepservices.sessionTerminated SleepService: window has terminated. 2025-06-10 22:00:52 -0700 Assertions PID 323(powerd) Released InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:05 id:0x0xd00009032 [System: PrevIdle] 2025-06-10 22:00:52 -0700 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:90%) 14 secs 2025-06-10 22:00:53 -0700 Assertions Summary- [System: PrevIdle] Using Batt(Charge: 90) 2025-06-10 22:00:53 -0700 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=6474 wakeAt=2025-06-10 23:48:48 info="DHCP lease renewal"] [*process=dasd request=SleepService deltaSecs=979 wakeAt=2025-06-10 22:17:13 info="com.apple.dasd:501:com.apple.intelligenceplatform.IntelligencePlatformCore.Pipeline.FastPass"] [process=powerd request=TCPKATurnOff deltaSecs=227969 wakeAt=2025-06-13 13:20:22] [process=powerd request=CSPNEvaluation deltaSecs=2005 wakeAt=2025-06-10 22:34:18] [process=powerd request=UserWake deltaSecs=7086 wakeAt=2025-06-10 23:59:00 info="com.apple.alarm.user-visible-com.apple.donotdisturb.server.ScheduleLifetimeMonitor.timer,619"]

Clearly not percentage, but the units don't seem to be specified... The real problem we have right now is that, with macOS 15.5, our suite gets a huge amount of "energy impact" points, even though diving into it, it doesn't seem to do that. The most telling example I have of that is: I ran each of our daemons from Terminal, unplugged my laptop, closed the lid, and let it stay there for 8 or 9 hours. When I woke it back up, Activity Monitor claimed it had 2,000 units or so, but after opening all of the disclosure triangles, none of the processes (including the hand-started daemons) used anything close to that. Also, the battery had almost no drain on it. We're getting complaints about this, so I'm trying to figure out what, exactly is going on, but I never looked at the power stuff internally so I don't know how to read the diagnostic files.

Hello. We have several apps, that use battery information, such as charge level and battery charge events. Since iOS 17, instead of report every 1% of charge, all API return an approximate within 5% value of the real value. As a result, that created a lot of issues with our users. Most of them, and at this point its around of million plus users, are not happy, because they will have to wait for the app to return information for literally hours... Please fix this, and even if you wont allow us access to real time data, like in Android devices, please at least return it back to be precise and at 1% of precision.

I am reaching out to inquire about the implementation of an energy monitoring solution similar to Xcode's Energy Impact tool for iOS apps. Specifically, I would like to understand the following aspects to address issues like overheating and rapid battery drain: How can we achieve monitoring and calculation of CPU, GPU, and network usage over a period of time within an app? How is the current energy consumption level of an app determined? Additionally, how are the weights for various factors like CPU, GPU, network, and location usage allocated when calculating the overall energy impact? Any guidance or resources you could provide regarding these questions would be greatly appreciated. Thank you for your assistance.

Dear Apple Support Team, I am reaching out to inquire about the implementation of an energy monitoring solution similar to Xcode's Energy Impact tool for iOS apps. Specifically, I would like to understand the following aspects to address issues like overheating and rapid battery drain: How can we achieve monitoring and calculation of CPU, GPU, and network usage over a period of time within an app? How is the current energy consumption level of an app determined? Additionally, how are the weights for various factors like CPU, GPU, network, and location usage allocated when calculating the overall energy impact? Any guidance or resources you could provide regarding these questions would be greatly appreciated. Thank you for your assistance.

Since running 18.4 beta 3 my phone doesn’t stop charging at its pre determining % it’s set at 80% and until now has always held at that percentage but since installing beta 3 it’s gone to 100% and held at that when charging overnight anyone else experiencing this?

I just bought my iphone 15 128gb last august 2024 and it’s already in 93% battery health. Whenever my battery percentage drop to 29% my battery health will also drop 1%. For example, i forgot to charge my phone, the battery health percentage is 94%, because i forgot to charge it, it is currently in 29% battery percentage. When i look up the battery health percentage, it is now 93% Btw, i use 30% - 80% charging tech. Sorry for my english. English is not my first language.

It looks like, for some reason, our apps are using a bunch of power sometimes. sysdiagnose has this in the power log: Never mind. Including the output of sysdiagnose has "sensitive language," and it won't tell me what is sensitive, making this a waste of my time. ETA: Ok, I I can attach the file: power.log I've gone through the energy documentation, but it seems geared towards embedded, not macOS, so I'm not sure how I can figure this out more. The extra problem, of course, is that we have a network extension, two daemons, and a GUI app. 😄

So the battery level value is in accurate returns the battery percentage in multiple of 5 values e.g. battery percentage is 42 but the api returns it as 40. So please fix the issue if possible because i checked that the devices running iOS versions below 17 appear to be working fine.

Currently i am using an iphone 15 pro which is just 7 months old but it was good till this month it was at 97% even after using more than 6 months, but in recent fews days it is regularly dropping by 1% every day and now it is at 89% only with 10 to 12 days it dropped by 8% . Is my battery defective or something is wrong with my phone . bcoz of this i am very upset because of this bad decrease of battery health . i have heard it is normal to degrade by 1% monthly but mine is dropping daily its soo frustrating. and if my battery reaches under 80% within the warrenty period? will get a free battery replacement from apple or not ? I don’t have apple care+ . But its under 1 year standard warrenty . please reply apple as its soo frustrating

Battery health reduced to 89 from 98 within 2 months on iPhone 15 Pro and Cycle Count is just 314. Is it the software update doing this?

what do i do is it going down too fast?