A while ago i installed iOS 26 beta 2 on my iPhone 12 mini with an unrecognised battery, and after updating, the battery percentage was stuck at 1%. so I tired different things, but never worked if not downgrading to iOS 18, now iOS 26 is out and i don't know if it now safe to update. i don't have the time now to troubleshoot so if someone can help me or tell me if this bug is fixed

I have a iPhone 16 pro for two months and since have put 26 beta my batTrey is draining much quicker

Hi , since I've been trying out this latest beta, my battery life has dropped dramatically. I have an iPhone 16 Pro. It doesn't last until the evening. I didn't have any problems with version 4 before. Thanks

I Downloaded new beta 7 iOS 26 update and i have issues with my iPhone 15 pro

Hello, when I got it, I updated it, but the battery life has decreased. Please advise. My battery health is 99%. It's been a few months since I bought the phone.

Hello, I have a question regarding the new battery usage interface in iOS 26. As shown in the attached screenshot, the system displays battery usage per app as a percentage (%). I’m curious about how this percentage is calculated. From what I can tell, it doesn’t seem to reflect the actual battery consumption per process, excluding the device’s base standby power. It rather appears to be calculated as a relative percentage based on total battery drain, possibly including system idle power. Is there any way to understand or estimate the actual battery usage per app, excluding the device’s inherent standby power consumption? Thank you.

Hi all, Is there a standard, good intuition about RealityKit battery drain vs how the Xcode profiler tends to display things? I have a realitykit ARview that i have permanently in my view hierarchy and the profiler is saying constantly 40% CPU spin, ~160mb increase of memory usage compared to when not using this view, and battery increased from Low to middle of the yellow bar for "high". Yet the actual battery drain attributed to my app is basically an order of magnitude lower than the battery drain of something like Tiktok for the same amount of foreground time (15% vs 2%) So I'm a little confused whether or not to trust the Xcode battery profiler when working with RealityKit and ARViews (unless Tiktok is in very high usage all the time!). Is this a largely ignorable signal, and more generally, how useful is this profiler? Doesn't seem immediately intuitive to me at first use. Thanks!

I’m currently experiencing a concerning battery issue on my MacBook Pro and wanted to share it here in case others are facing something similar or if it’s possibly tied to a software-level behavior. Device & Software Info: • MacBook Pro 14” (2023) • macOS 26.0(25A5316i) • Battery Cycle Count: 307 • Battery Health: 91% (as of today) • Condition: Normal Issue: • Battery health has dropped from 96% to 91% in less than a week. • For the last week each day, the maximum capacity seems to decline by 1%, even when usage is light and the Mac is plugged in most of the time with Battery Health Management enabled. • When the battery drops below 10%, it drains extremely fast — the percentage decreases nearly second by second, which doesn’t feel normal.

I have bought iphone 16 pro max on October 28, ( 9 months ago) and rarely dropped by battery health below 20%. I also set limit to 80% so I can preserve my Battery Health. I am not a multitasking user. I used fan to keep the phone cool during charging. But today I update to iOS26 public beta, It dropped to 99% at 88 Cycle which is quite low cycle. Many other user are getting their battery health dropped to 99% after 120, 130+ cycle with daily usage. Why mine got dropped after updating. I am quite unhappy with it, and iOS 26 is so jittery in my phone

Since updating to iOS 18.6 beta on my iPhone 13 ProMax, my battery usage has well over doubled. Also, my phone has become noticeably sluggish and unresponsive. For instance, after being charged to 100% my phone has dropped to 26% with only 1 hr 2m screen on time and 49m of screen off time. My phone gets noticeably warm to the touch, even through the case. Any ideas on the cause or any remedy?

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.