Battery drain question

Hi All,
I have a question about my battery drain. I just want to check and see if it is rather normal.
Last evening I unplugged my iPad after its first full charge (wore the battery down to like 6% the previous night). Took it with me on a car ride, turned it on on occasion in the car, just seeing wifi hotspots and such. Then played around with it for a while. By the time I got home the battery was at like 98/97%. Then used it a moderate amount later on, and while browsing the web I noticed the battery dropped a good 1+% every couple minutes while simply browsing the web.
I noticed that trend last night while browsing, then stopping and browsing again (turning the device from a locked state to working).
Is the 1/2% drop every we shall say 10-15 minutes of web surfing good or bad. Sorry for the paranoid question, just curious.
Terry

Lets say the iPad drops 2% every 10 minutes while browsing. So at a rate of 2% you will be able to use the ipad for 100%/2%*10minutes=500 minutes
divide that by 60 minutes in an hour and you get 8 hours and 20 minutes which isn't that far off of up to 10 hours of usage. I think that's pretty good considering I used the worst case scenario from the numbers you provided.
There are plenty of factors including distance from the router, brightness level, temperature etc.
Message was edited by: enderx

Similar Messages

First off, i think it's sad that i have to use my non apple device to post this question... Why has my iPad become absolutely useless after updating to iOS 8.1? I am unable to use my mini because it crashes, slow performance, major battery drain.

First off, i think it's sad that i have to use my non apple device to post this question... Why has my iPad become absolutely useless after updating to iOS 8.1? I am unable to use my mini because it crashes, slow performance, major battery drain.

Restore iPad to Factory Default; do not restore from backup. It may be the cause of the problem.
Settings>General>Reset>Erase all content and settings

Battery drain problem - question if auto lock is problem

Just upgraded from iPad2 to Retina iPad. Went smoothly with cloud backup and download but experiencing sever battery drain. Went to use it 2 days ago after limited use prior evening (taking minutes in Evernote for 2 hr meeting) and had shut off. Restarted and had 2% battery and totally useless. Recharged overnight to 100% but had no demands yesterday. That evening opened up and found I had 21% remaining.
Did battery problem search at this site, made some adjustments, and recharged to 100% for this AM. Two primary adjustments were stopping Bluetooth and Autolock changed from never (iPad2 setting) to 10 minutes and wondering if the autolock feature is the problem as discussed in the next paragraph. Others I didn't change, gmail set to fetch/manual and Cloud is push. WiFi on and disabling like suggested in some threads would be a royal PITA having to turn it back on every time and counter to the Apple vision of useability. App Store is set to advise of updates. Each of those were like on the iPad2 where had no battery problem, except I didn't activate cloud until just prior to the upgrade. IOS on both machines fully upgraded to IOS 6.01.
Interesting discovery this AM. While I set the Auto-Lock to 10 minutes last evening, the the iPad Cover lock/unlock is set "ON". It appears that the 10 minute Auto Lock is working, however, the automatic lock/unlock is not which would explain the battery drain when set autolock was set to never. This AM as I opened it, had to manually unlock it as opposed to having the cover unlock it for me. As I close the cover and peek under the edge can still see the iPad illuminated until the 10 minutes kicks in...then manually unlock it again. The cover I am using is the heavy duty RooCase with magnetic clip and had no problem when using it with the iPad2. (Great case by the way!) Any suggestions? Thanks.

Check this out...
http://support.apple.com/kb/TS1297
It worked great for me.

IPhone hot, Battery draining fast, dataaccessd crashing repeatedly

I have been having problems where I find my iPhone battery has drained more quickly than normal, and I find it warmer than normal. Digging into it, I found that 'dataaccessd' and 'ReportCrash' are starting and stopping in the pid list. I am using a $2.99 iTunes Store program called System Activity Monitor to see the pids & CPU load. The CPU load is spiking every few seconds, which I guess correlates with the heat and battery drain.
I followed the recommendation below exactly with this afternoon's episode, and it is still running the processor and burning battery, looping through 'dataacessd' and 'ReportCrash' afterwards.
+Have you tried this simple tip?+
+1) Hit home button twice to bring up active applications+
+2) click and hold down mail until the red minus sign appears+
+3) click on the red minus sign to quit the application+
+4) hit the home screen and re-launch the mail application+
+This has always fixed my mail issues. Note restarting the phone does+
+not help, you need to do the above procedure.+
I also cycled power, and it came back up with dataaccessd still crashing & cycling with repetitive spiking CPU loads. I also turned 'push' off earlier today (Fetch New Data / Push -> Off), apparently with no effect.
I have the EAS profile installed per http://support.apple.com/kb/TS3398 with the DefaultEASTaskTimeout at 240. And it doesn't seem to matter whether the phone is on 3G or WiFi when this condition happens.
As usual, the "fix" was to delete my Exchange e-mail account and re-install it. After that, I don't see 'dataaccessd' and 'REportCrash' coming and going in the pid list. This "fix" works, but going through this procedure 3-4 times per week is getting old, not to mention the unpleasant surprise of finding my battery has unexpectedly drained when I need to use my device.
This is the first log entry (earliest) today at 13:39, when dataaccessd started crashing, before a slew of 4-6 entries per minute in the log directory on my Mac (after syncing) - see below.
Question - any ideas how to fix this ? It was happening before the latest iOS upgrades so I don't think the standard "reload the os" answer is the fix....
From: dataaccessd2010-12-01-133956ssherrats-iPhone.crash
Incident Identifier: 23D8E941-7243-4C7D-BB52-F9641813E031
CrashReporter Key: bf083330b2bcfde06f73366c5025c8bc7d298440
Hardware Model: iPhone2,1
Process: dataaccessd [23]
Path: /System/Library/PrivateFrameworks/DataAccess.framework/Support/dataaccessd
Identifier: dataaccessd
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2010-12-01 13:39:56.277 -0800
OS Version: iPhone OS 4.2.1 (8C148a)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 Crashed:
0 libSystem.B.dylib 0x311de2d4 0x31165000 + 496340
1 libSystem.B.dylib 0x311de2c4 0x31165000 + 496324
2 libSystem.B.dylib 0x311de2b6 0x31165000 + 496310
3 libSystem.B.dylib 0x311f2d72 0x31165000 + 580978
4 libstdc++.6.dylib 0x301dea20 0x3019a000 + 281120
5 libobjc.A.dylib 0x319a2594 0x3199c000 + 26004
6 libstdc++.6.dylib 0x301dcdf2 0x3019a000 + 273906
7 libstdc++.6.dylib 0x301dce46 0x3019a000 + 273990
8 libstdc++.6.dylib 0x301dcf16 0x3019a000 + 274198
9 libobjc.A.dylib 0x319a14c4 0x3199c000 + 21700
10 CoreFoundation 0x314d07c2 0x31430000 + 657346
11 Foundation 0x31d16242 0x31cc4000 + 336450
12 DADaemonEAS 0x35d817e0 0x35d75000 + 51168
13 DADaemonEAS 0x35d88046 0x35d75000 + 77894
14 DADaemonEAS 0x35d83b22 0x35d75000 + 60194
15 DADaemonEAS 0x35d8968e 0x35d75000 + 83598
16 DADaemonEAS 0x35d80f7e 0x35d75000 + 49022
17 DADaemonEAS 0x35d7694e 0x35d75000 + 6478
18 DADaemonEAS 0x35d794ea 0x35d75000 + 17642
19 DADaemonEAS 0x35d85ab8 0x35d75000 + 68280
20 DAEAS 0x3430c2d6 0x342d1000 + 242390
21 DAEAS 0x3431bec6 0x342d1000 + 306886
22 DAEAS 0x3431cab8 0x342d1000 + 309944
23 Foundation 0x31cf6806 0x31cc4000 + 206854
24 Foundation 0x31cf6788 0x31cc4000 + 206728
25 CFNetwork 0x3465047e 0x34641000 + 62590
26 CFNetwork 0x346451f2 0x34641000 + 16882
27 CFNetwork 0x3464537a 0x34641000 + 17274
28 CFNetwork 0x346450e4 0x34641000 + 16612
29 CFNetwork 0x34645096 0x34641000 + 16534
30 CFNetwork 0x34645014 0x34641000 + 16404
31 CFNetwork 0x34644f92 0x34641000 + 16274
32 CoreFoundation 0x314867d6 0x31430000 + 354262
33 CoreFoundation 0x314585b0 0x31430000 + 165296
34 CoreFoundation 0x31457e54 0x31430000 + 163412
35 CoreFoundation 0x31457c80 0x31430000 + 162944
36 CoreFoundation 0x31457b88 0x31430000 + 162696
37 dataaccessd 0x00001ca6 0x1000 + 3238
38 dataaccessd 0x00001b38 0x1000 + 2872
Thread 1:
0 libSystem.B.dylib 0x31192974 0x31165000 + 186740
1 libSystem.B.dylib 0x3123c704 0x31165000 + 882436
2 libSystem.B.dylib 0x3123c174 0x31165000 + 881012
3 libSystem.B.dylib 0x3123bb98 0x31165000 + 879512
4 libSystem.B.dylib 0x311e024a 0x31165000 + 504394
5 libSystem.B.dylib 0x311d8970 0x31165000 + 473456
Thread 2:
0 libSystem.B.dylib 0x31166268 0x31165000 + 4712
1 libSystem.B.dylib 0x31168354 0x31165000 + 13140
2 CoreFoundation 0x31458648 0x31430000 + 165448
3 CoreFoundation 0x31457ed2 0x31430000 + 163538
4 CoreFoundation 0x31457c80 0x31430000 + 162944
5 CoreFoundation 0x31457b88 0x31430000 + 162696
6 Foundation 0x31cc88e4 0x31cc4000 + 18660
7 Foundation 0x31cc87fc 0x31cc4000 + 18428
8 AppSupport 0x309ee822 0x309e4000 + 43042
9 Foundation 0x31cc8242 0x31cc4000 + 16962
10 libSystem.B.dylib 0x311df886 0x31165000 + 501894
11 libSystem.B.dylib 0x311d4a88 0x31165000 + 457352
Thread 3:
0 libSystem.B.dylib 0x31166268 0x31165000 + 4712
1 libSystem.B.dylib 0x31168354 0x31165000 + 13140
2 CoreFoundation 0x31458648 0x31430000 + 165448
3 CoreFoundation 0x31457ed2 0x31430000 + 163538
4 CoreFoundation 0x31457c80 0x31430000 + 162944
5 CoreFoundation 0x31457b88 0x31430000 + 162696
6 Foundation 0x31cf15f6 0x31cc4000 + 185846
7 Foundation 0x31ccf192 0x31cc4000 + 45458
8 Foundation 0x31cc8242 0x31cc4000 + 16962
9 libSystem.B.dylib 0x311df886 0x31165000 + 501894
10 libSystem.B.dylib 0x311d4a88 0x31165000 + 457352
Thread 4:
0 libSystem.B.dylib 0x3118a68c 0x31165000 + 153228
1 CoreFoundation 0x3148f662 0x31430000 + 390754
2 libSystem.B.dylib 0x311df886 0x31165000 + 501894
3 libSystem.B.dylib 0x311d4a88 0x31165000 + 457352
Thread 5:
0 libSystem.B.dylib 0x311e09e0 0x31165000 + 506336
1 libSystem.B.dylib 0x311e0364 0x31165000 + 504676
2 libSystem.B.dylib 0x311d8970 0x31165000 + 473456
Thread 6:
0 libSystem.B.dylib 0x311e09e0 0x31165000 + 506336
1 libSystem.B.dylib 0x311e0364 0x31165000 + 504676
2 libSystem.B.dylib 0x311d8970 0x31165000 + 473456
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x3e1a82e8
r4: 0x00000006 r5: 0x301dc989 r6: 0x001afa8c r7: 0x2fdfe1b4
r8: 0x001af560 r9: 0x00000065 r10: 0x33bb3910 r11: 0x00139890
ip: 0x00000025 sp: 0x2fdfe1b4 lr: 0x311de2cb pc: 0x311de2d4
cpsr: 0x00000010
Binary Images:
0x1000 - 0x1fff dataaccessd armv7 <cb2dfcefb43430f4550f0187890de64a> /System/Library/PrivateFrameworks/DataAccess.framework/Support/dataaccessd
0x23000 - 0x24fff dns.so armv7 <fcefecb2d5e095ba88127eec3af57ec0> /usr/lib/info/dns.so
0x2fe00000 - 0x2fe27fff dyld armv7 <06e6959cebb4a72e66c833e26ae64d26> /usr/lib/dyld
0x30122000 - 0x30177fff libvDSP.dylib armv7 <9365fc6cae1bff737257e74faf3b1f26> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib vDSP.dylib
0x3019a000 - 0x301e4fff libstdc++.6.dylib armv7 <53a6e7239c3908fa8c2915b65ff3b056> /usr/lib/libstdc++.6.dylib
0x3024e000 - 0x302fdfff WebKit armv7 <644a1c6120578f896bed7121307aa2af> /System/Library/PrivateFrameworks/WebKit.framework/WebKit
0x30319000 - 0x30320fff libbz2.1.0.dylib armv7 <2989ea7a5cad2cfe91bd632b041d0ff4> /usr/lib/libbz2.1.0.dylib
0x30569000 - 0x3056afff CoreSurface armv7 <f7caaf43609cfe0e475dfe83790edb4d> /System/Library/PrivateFrameworks/CoreSurface.framework/CoreSurface
0x30746000 - 0x3074ffff CoreVideo armv7 <2092d5deb6b234e04678b7c1878ccd81> /System/Library/Frameworks/CoreVideo.framework/CoreVideo
0x30750000 - 0x3075bfff libz.1.dylib armv7 <fabaddbcbc8c02bab0261df9d78e0e25> /usr/lib/libz.1.dylib
0x3075f000 - 0x30761fff MobileInstallation armv7 <8e6b0d9f642be06729ffdaaee97053b0> /System/Library/PrivateFrameworks/MobileInstallation.framework/MobileInstallati on
0x30792000 - 0x3079cfff AccountSettings armv7 <19c79f81d5d55fe2e6b618fcdc28258e> /System/Library/PrivateFrameworks/AccountSettings.framework/AccountSettings
0x3079d000 - 0x307a3fff liblockdown.dylib armv7 <5bbd9b3f5cfece328f80c403a8805ce9> /usr/lib/liblockdown.dylib
0x30853000 - 0x30854fff DataMigration armv7 <babbc72d4d48325de147d5103d7bc00d> /System/Library/PrivateFrameworks/DataMigration.framework/DataMigration
0x309e4000 - 0x30a16fff AppSupport armv7 <47c8055ac99f187174ca373b702ffa68> /System/Library/PrivateFrameworks/AppSupport.framework/AppSupport
0x30a1d000 - 0x30a54fff Security armv7 <cd28e102950634ae7167ddee9c686d36> /System/Library/Frameworks/Security.framework/Security
0x30a5d000 - 0x30b0bfff QuartzCore armv7 <83a8e5f0033369e437069c1e758fed83> /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x30c3d000 - 0x30c5afff AppleAccount armv7 <e3833276f8877499c8dd76b3b3d88501> /System/Library/PrivateFrameworks/AppleAccount.framework/AppleAccount
0x30c7e000 - 0x30caafff DataAccess armv7 <6b9b5235b449335ce5c66d53f32004cd> /System/Library/PrivateFrameworks/DataAccess.framework/DataAccess
0x30d3c000 - 0x30d3ffff ActorKit armv7 <f5d038591e564646e9237a59c6c14293> /System/Library/PrivateFrameworks/ActorKit.framework/ActorKit
0x30d54000 - 0x30d61fff libbsm.0.dylib armv7 <0f4e595e6eb2170aceb729f32b5de8c2> /usr/lib/libbsm.0.dylib
0x30e16000 - 0x30e16fff liblangid.dylib armv7 <83e91e0930ee03bc33604f1a85ecf402> /usr/lib/liblangid.dylib
0x30faf000 - 0x30feefff libGLImage.dylib armv7 <a7c117c92607a512823d307b8fdd0151> /System/Library/Frameworks/OpenGLES.framework/libGLImage.dylib
0x3101d000 - 0x3101ffff CrashReporterSupport armv7 <30a5f1edcdb9ffe868a620199a4cbe12> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/CrashReporterS upport
0x31020000 - 0x3102cfff SpringBoardServices armv7 <137b75e19b2450c234dec88d538798ff> /System/Library/PrivateFrameworks/SpringBoardServices.framework/SpringBoardServ ices
0x31077000 - 0x3115ffff libGLProgrammability.dylib armv7 <1f478a71783cd7eb4ae9ef6f2dcea803> /System/Library/Frameworks/OpenGLES.framework/libGLProgrammability.dylib
0x31160000 - 0x31163fff IOSurface armv7 <deff02882166bf16d0765d68f0542cc8> /System/Library/PrivateFrameworks/IOSurface.framework/IOSurface
0x31165000 - 0x31276fff libSystem.B.dylib armv7 <138a43ab528bb428651e6aa7a2a7293c> /usr/lib/libSystem.B.dylib
0x31324000 - 0x31336fff PersistentConnection armv7 <cd2a699aa5036bdad0517603ba4db839> /System/Library/PrivateFrameworks/PersistentConnection.framework/PersistentConn ection
0x31337000 - 0x31371fff IOKit armv7 <eb932cc42d60e55d9a4d0691bcc3d9ad> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x313fa000 - 0x3140dfff libmis.dylib armv7 <855aefc263c6c20e6cf8723ea36125a2> /usr/lib/libmis.dylib
0x31430000 - 0x31516fff CoreFoundation armv7 <01441e01f5141a50ee723362e59ca400> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x31517000 - 0x31519fff IOMobileFramebuffer armv7 <1040629f37795146c9dcac8ab1a868fc> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/IOMobileFramebu ffer
0x3151b000 - 0x3151efff CertUI armv7 <5f37446c6b65a8c38ab6233c2e33da66> /System/Library/PrivateFrameworks/CertUI.framework/CertUI
0x3151f000 - 0x3153afff DADaemonSupport armv7 <019523c36bd94fd3dd5a98bb110dc33a> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DADaemonSuppo rt.framework/DADaemonSupport
0x31549000 - 0x3154cfff CaptiveNetwork armv7 <a2af7147f5538d7669b14fa7b19b5a7c> /System/Library/PrivateFrameworks/CaptiveNetwork.framework/CaptiveNetwork
0x3155c000 - 0x3167cfff CoreGraphics armv7 <2d7b40a7baca915ce78b1dd9a0d6433b> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x3167d000 - 0x3168dfff DataAccessExpress armv7 <6767a1e2afbc86a1ec63dd784f5d3677> /System/Library/PrivateFrameworks/DataAccessExpress.framework/DataAccessExpress
0x316cf000 - 0x31702fff iCalendar armv7 <6eb50e720d642f5ac510a36989b276b2> /System/Library/PrivateFrameworks/iCalendar.framework/iCalendar
0x31703000 - 0x31705fff libgcc_s.1.dylib armv7 <e66758bcda6da5d7f9b54fa5c4de6da2> /usr/lib/libgcc_s.1.dylib
0x317f9000 - 0x3183cfff ManagedConfiguration armv7 <27ac7f05482a8aa9977150f34f9be6eb> /System/Library/PrivateFrameworks/ManagedConfiguration.framework/ManagedConfigu ration
0x3186b000 - 0x3187afff Notes armv7 <7d7a3d10a349471cd2757a479d131b31> /System/Library/PrivateFrameworks/Notes.framework/Notes
0x3187b000 - 0x31991fff libicucore.A.dylib armv7 <e7fbb2ac586567e574dc33d7bb5c4dc9> /usr/lib/libicucore.A.dylib
0x31992000 - 0x3199bfff WebBookmarks armv7 <9f1760206eaef20c605c5d98e45c823e> /System/Library/PrivateFrameworks/WebBookmarks.framework/WebBookmarks
0x3199c000 - 0x31a5dfff libobjc.A.dylib armv7 <aaf5671a35f9ac20d5846703dafaf4c6> /usr/lib/libobjc.A.dylib
0x31a7d000 - 0x31a8afff OpenGLES armv7 <a12565ffb5bb42e3019f1957cd4951d0> /System/Library/Frameworks/OpenGLES.framework/OpenGLES
0x31ae0000 - 0x31ae3fff libGFXShared.dylib armv7 <3a385ed495379116abbe50bc8cd5a612> /System/Library/Frameworks/OpenGLES.framework/libGFXShared.dylib
0x31b29000 - 0x31b52fff MobileCoreServices armv7 <54484a513761868149405df7fc29b5c0> /System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x31b58000 - 0x31b5ffff AggregateDictionary armv7 <71372c95d4af7af787d0682a939e40ac> /System/Library/PrivateFrameworks/AggregateDictionary.framework/AggregateDictio nary
0x31bcc000 - 0x31be1fff libresolv.9.dylib armv7 <ea156820997ae9a2baf664d0f79f18d7> /usr/lib/libresolv.9.dylib
0x31cc4000 - 0x31de3fff Foundation armv7 <81d36041f04318cb51db5aafed9ce504> /System/Library/Frameworks/Foundation.framework/Foundation
0x31e18000 - 0x31e63fff libBLAS.dylib armv7 <251c5ac7380802a16e30d827c027c637> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib BLAS.dylib
0x33856000 - 0x33884fff MIME armv7 <1989502ce4da514314647c6a0098d8e7> /System/Library/PrivateFrameworks/MIME.framework/MIME
0x33886000 - 0x3389cfff EAP8021X armv7 <36659ec2b9def7b5798a05327e369247> /System/Library/PrivateFrameworks/EAP8021X.framework/EAP8021X
0x33c5e000 - 0x33ce7fff Message armv7 <69cb7cb1d1d7865fc04dc341544174b6> /System/Library/PrivateFrameworks/Message.framework/Message
0x33ce8000 - 0x342d0fff WebCore armv7 <d6bd9cf88ee82ab6b0e33e0ae1190772> /System/Library/PrivateFrameworks/WebCore.framework/WebCore
0x342d1000 - 0x34341fff DAEAS armv7 <4d331bcf15c2b452aa3c02d21b99067a> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DAEAS.framewo rk/DAEAS
0x34342000 - 0x3436bfff ContentIndex armv7 <247576cb4f1ff8e92650ae3cb4973760> /System/Library/PrivateFrameworks/ContentIndex.framework/ContentIndex
0x3438c000 - 0x343e5fff EventKit armv7 <037c4bb5e2529e6004d0e1f3d95a84cc> /System/Library/Frameworks/EventKit.framework/EventKit
0x343e6000 - 0x34405fff Bom armv7 <0f5fd6057bad5e1677869500d636821f> /System/Library/PrivateFrameworks/Bom.framework/Bom
0x344ea000 - 0x34623fff AudioToolbox armv7 <657b327f2ceee9f22f9474f2f9bddbe6> /System/Library/Frameworks/AudioToolbox.framework/AudioToolbox
0x34628000 - 0x34628fff Accelerate armv7 <29dd5f17440bbb6e8e42e11b6fceda9a> /System/Library/Frameworks/Accelerate.framework/Accelerate
0x34641000 - 0x34700fff CFNetwork armv7 <02fe0e30e54fffdcbbbd02e8cb812c3a> /System/Library/Frameworks/CFNetwork.framework/CFNetwork
0x3471b000 - 0x3473cfff MobileSync armv7 <cff20dfe818febca9f3232426d59a42d> /System/Library/PrivateFrameworks/MobileSync.framework/MobileSync
0x34941000 - 0x34944fff ApplePushService armv7 <9d1eb7b11f0f146c941efbab2c055606> /System/Library/PrivateFrameworks/ApplePushService.framework/ApplePushService
0x34952000 - 0x3495afff MobileWiFi armv7 <b29d4c5e300ef81060e38f72bb583c02> /System/Library/PrivateFrameworks/MobileWiFi.framework/MobileWiFi
0x3495b000 - 0x34bf5fff libLAPACK.dylib armv7 <2e77d87e96af938aacf0a6008e6fb89d> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib LAPACK.dylib
0x34bf6000 - 0x34c36fff CoreAudio armv7 <f32e03ee4c68f0db23f05afc9a3cc94c> /System/Library/Frameworks/CoreAudio.framework/CoreAudio
0x35227000 - 0x3532efff CoreData armv7 <29b1ab7d339e42a6ff6923e54cf43e7b> /System/Library/Frameworks/CoreData.framework/CoreData
0x35336000 - 0x353dffff libxml2.2.dylib armv7 <b3d82f80a777cb1434052ea2d232e3df> /usr/lib/libxml2.2.dylib
0x353e1000 - 0x3548efff JavaScriptCore armv7 <3f2df600942dc72aad312b3cc98ec479> /System/Library/PrivateFrameworks/JavaScriptCore.framework/JavaScriptCore
0x354b4000 - 0x354bcfff libkxld.dylib armv7 <854e82fe66feef01e54c7c8a209851ac> /usr/lib/system/libkxld.dylib
0x354fa000 - 0x3553cfff CoreTelephony armv7 <96d3af505b9f2887e62c7e99c157733e> /System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x3553d000 - 0x3558afff libsqlite3.dylib armv7 <55038e5c1d4d0dbdd94295e8cad7a9a4> /usr/lib/libsqlite3.dylib
0x35a37000 - 0x35a3cfff MobileKeyBag armv7 <cec3f3271fc267c32c169ed03e312d63> /System/Library/PrivateFrameworks/MobileKeyBag.framework/MobileKeyBag
0x35a95000 - 0x35a95fff vecLib armv7 <e53d234e808c77d286161095f92c58cf> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/vec Lib
0x35bcc000 - 0x35bfbfff SystemConfiguration armv7 <3f982c11b5526fc39a92d585c60d8a90> /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x35d62000 - 0x35d6efff GraphicsServices armv7 <0099670dccd99466653956bf918d667a> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x35d75000 - 0x35d98fff DADaemonEAS armv7 <a6c7e0fc1fbee8494bf605c5ec0bee6f> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DAEAS.framewo rk/DADaemonEAS.bundle/DADaemonEAS
0x35db1000 - 0x35e44fff ImageIO armv7 <5b5a294d4250eff866fdbf891b1e8b34> /System/Library/Frameworks/ImageIO.framework/ImageIO
0x35e52000 - 0x35e85fff AddressBook armv7 <7c87e0175c8649d6832419da8a1cfac1> /System/Library/Frameworks/AddressBook.framework/AddressBook
0x35f4a000 - 0x35f4ffff libMobileGestalt.dylib armv7 <5f73c7138ee1cb7103a98aec99f9ed88> /usr/lib/libMobileGestalt.dylib
0x35f86000 - 0x35fbcfff CoreText armv7 <b9b5c21b2d2a28abc47842c78c026ddf> /System/Library/Frameworks/CoreText.framework/CoreText
0x3607f000 - 0x3608efff MobileDeviceLink armv7 <8f2fc7e811bc57f7a09d7df81c329e1a> /System/Library/PrivateFrameworks/MobileDeviceLink.framework/MobileDeviceLink

dataaccessed crashing repeatedly here as well, only when syncing with Exchange Calendar, regardless of push/fetch setting. Disabling calendar on this account stops the crashes. Re-creating account doesn't help. Problems started 2 days ago. More info on the crash from iPhone console below, collected using Configuration Utility, in case it can help someone. I suppose Apple automatically receives crash dumps for their own applications through iTunes ?
Fri Mar 4 07:02:38 iPhone dataaccessd[24] <Warning>: EAS|Have an exception with no start date or exception start date. Results are undefined, event is <ASEventException: [(null)] [(null)] [(null)] [(null)]>: exceptionStartTime (null) isDeleted NO
Fri Mar 4 07:02:39 iPhone dataaccessd[24] <Error>: * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]: attempt to insert nil key'
* Call stack at first throw:
0 CoreFoundation 0x33ac0987 __exceptionPreprocess + 114
1 libobjc.A.dylib 0x3347b49d objcexceptionthrow + 24
2 CoreFoundation 0x33ac07c9 +[NSException raise:format:arguments:] + 68
3 CoreFoundation 0x33ac0803 +[NSException raise:format:] + 34
4 CoreFoundation 0x33a445e5 -[__NSCFDictionary setObject:forKey:] + 244
5 DAEAS 0x339df2cb -[ASEvent eventByMergingInLosingEvent:account:] + 974
6 DAEAS 0x339db2cb -[ASEvent eventByMergingInEvent:account:] + 46
7 DADaemonEAS 0x324665bb -[ASAgent(FolderContentsSync) _syncResultForFolder:newTag:previousTag:actions:results:changeIdContext:isIniti alSync:moreAvailable:dataclass:resultingChangeActionsForServer:pushedCalendarAct ions:rejectedServerIds:eventsWithPendingInvitationEmails:] + 2070
8 DADaemonEAS 0x324656cd -[ASAgent(FolderContentsSync) _wrapperSyncResultForFolder:dataclass:newTag:previousTag:actions:results:change IdContext:isInitialSync:moreAvailable:pushedCalendarActions:rejectedServerIds:] + 848
9 DADaemonEAS 0x32462121 -[ASAgent(FolderContentsSync) syncResultForEventsFolder:newTag:previousTag:actions:results:changeIdContext:is InitialSync:moreAvailable:pushedActions:rejectedServerIds:] + 60
10 DAEAS 0x339c6d59 -[ASAccount folderItemsSyncTask:completedWithStatus:error:newSyncKey:added:removed:modified :addedResponse:modifiedResponse:removedResponse:fetchedResponse:] + 960
11 DAEAS 0x339e7b41 -[ASFolderItemsSyncTask finishWithError:] + 1332
12 DAEAS 0x339f9ecd -[ASTask didProcessContext:] + 16
13 DAEAS 0x339faabf -[ASTask connectionDidFinishLoading:] + 650
14 Foundation 0x3364b80d -[NSURLConnection(NSURLConnectionReallyInternal) sendDidFinishLoading] + 68
15 Foundation 0x3364b78f _NSURLConnectionDidFinishLoading + 78
16 CFNetwork 0x30ca7485 ZN19URLConnectionClient23_clientDidFinishLoadingEPNS26ClientConnectionEventQueueE + 136
17 CFNetwork 0x30c9c1f9 _ZN19URLConnectionClient26ClientConnectionEventQueue33processAllEventsAndConsum ePayloadEP20XConnectionEventInfoI12XClientEvent18XClientEventParamsEl + 100
18 CFNetwork 0x30c9c0eb _ZN19URLConnectionClient13processEventsEv + 70
19 CFNetwork 0x30c9c09d _ZN13URLConnection24multiplexerClientPerformEP18RunLoopMultiplexer + 36
20 CFNetwork 0x30c9c01b _ZN17MultiplexerSource7performEv + 126
21 CFNetwork 0x30c9bf99 ZN17MultiplexerSource8performEPv + 8
22 CoreFoundation 0x33a767dd _CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION_ + 12
23 CoreFoundation 0x33a485b7 __CFRunLoopDoSources0 + 382
24 CoreFoundation 0x33a47e5b __CFRunLoopRun + 230
25 CoreFoundation 0x33a47c87 CFRunLoopRunSpecific + 230
26 CoreFoundation 0x33a47b8f CFRunLoopRunInMode + 58
27 dataaccessd 0x00001cad 0x0 + 7341
28 dataaccessd 0x00001b40 0x0 + 6976
Fri Mar 4 07:02:39 iPhone com.apple.dataaccess.dataaccessd[24] <Notice>: terminate called after throwing an instance of '
Fri Mar 4 07:02:39 iPhone com.apple.dataaccess.dataaccessd[24] <Notice>: NSException
Fri Mar 4 07:02:39 iPhone com.apple.dataaccess.dataaccessd[24] <Notice>: '
Fri Mar 4 07:02:39 iPhone ReportCrash[98] <Notice>: Formulating crash report for process dataaccessd[24]
Fri Mar 4 07:02:40 iPhone com.apple.launchd[1] (com.apple.dataaccess.dataaccessd[24]) <Warning>: (com.apple.dataaccess.dataaccessd) Job appears to have crashed: Abort trap

Verizon iPhone 4 Battery Draining issue (continued)

This is not a question or help topic but more of an announcement. Here's my story:
I preordered the phone on it's February 3rd date and recieved the phone on February 7th. I did as Apple instructs when you get a new idevice (drain the battery down till it dies then recharge it to 100%.) I did that and began to use it, and keep in mind this was not heavy usage at all. I didn't have any app store apps installed at all, I set all settings in the phone to the best configuration for battery saving (truning off push notifications, turning off location services for apps you do not need, no bluetooth, no VPN, brightness at 33%, ect.) Now I thought the battery was strange as I had made my first phone call on 100% battery and it was a 5 minute call. I kid you not I lost 10% battery from one phone call. I thought that was rediculous so I went into my local verizon store and had it replaced. I did the same as I did last time and let the battery drain till it died and filled it to 100%. Tried the phone out and still had the same issue. I went back in and got my 3rd iphone 4. Did the same steps as before and drained then filled it. Yet again, I still had troubles with 3 phones in a row. I cantacted apple and got in contact with an apple engineer named Andrew. He sent me a file that they created that monitors what all is being used by the battery and monitors background processes and applications. I let that run for 24 hours and sent the battery loggin file back to Andrew. They reviewed the log and gave me a call the next day. They told me they did find some very significant battery draining and advised me to go to the nearest apple store ASAP and have the phone checked out. I drove 2 hours to the nearest store for them to just tell me the phone is fine (yotta yotta yotta) and they did a hard reset and restore on the phone (which I could have done from home on my computer and save the gas they made me waste driving for a total of 4 hours!) I tried contacting Andrew agiain but Andrew did not reply to any email sent to him nor return my calls. I got the point that he didn't want to deal with me anymore so I then decided to go the Verizon route. I called Verizon tech support and was transferred to a teir 2 representative. I told her my story, how many replacements I had, and how bad the battery life was. I told how my grandmother has an iphone 4 and I sat down comparing the 2 (battery life wise) and she chewed me out saying things like, "How dare you compare AT&T and Verizon!" I didn't want to listen to her chewing me out so I hung up. The next day I gave apple a call once again and they told me things I had already heard several times so I hung up. I called Verizon back and they said ok let's send you a replacement phone. Well the replacement phone came and wouldn't ya know it? The phone still had the same problem and on top of that they only sent me a phone. No box, no headphones, no USB cable, no charger. I called Verizon about this and asked why they only sent me a phone and they said, "Well you get to keep the phone but we want the other things back. The box, headphones, charger, USB cable, ect." I told them no and that they could have their refurbished phone back. This phone was not even refurbished. the reason I kow that is because it had someone's name written in the phone and it was still on 4.2.5. Had it been refurbished they would have done a fresh restore and update as 4.2.5 was deemed obsolete. That was very insulting in my opinion. So I sent that back and contacted apple one last time. I asked what other options I had as I was stressed and did not want to hear the same things I have already heard. they said they could send me a new phone free of charge and have me send back my current phone. I agreed to give it one last shot but I am still not confident that this phone will be any different.
Now that's my story. Now let me go into a discussion. I have been doing my own litle "investigation on this phone to see what is making this phone drain so bad. I took a look at a report from iFixit.com and they revealed some pretty interesting things built into the Verizon iPhone. I am not going into detail about it but you can google it and see for yourself and read the article about the components. They built the phone with not only CDMA tech but also GSM. Now what purpose would that serve? Honestly? That is a big battery drainer right there. Secondly, they found that the phone contained a different model battery that was lighter and had less capacity than the GSM version of the iPhone 4. That's a second red flag. My mission right now is to get Apple's attention that these phones do indeed have aproblem and they need to be looked at because this just aint workin'. I have had several replacements done (all have the same issue), several thousands of people are reporting the same results with their battery on the web, and Apple chooses to ignore it. Something needs to be done and I encourage any Verizon iPhone user to take action and make this issue known. I have a website with contact information of people who work high up in the chain of Apple along with Scott Forstall's contact info. Go to http://idevicesupport.webs.com/apps/blog/show/6441029-update and find a contact you like and call it and deman that apple investigate these phones. We can get this issue resolved if we make it known. Don't be mean or nasty to them. They are very nice people but at the sametime don't let them talk over you. Make your voice heard. Thanks for listening guys. Take care. - Joe

Some Users have Reported that a Restore as New has helped Resolve issues...
Backup and Set Up as New Device
http://support.apple.com/kb/HT4137

IPhone 5s IOS 8.1.1 battery drain using mail

Problem: battery drain is unacceptably high with -1% per five minutes
Description: after upgrading from IOS 7 to 8 the battery drain on my iPhone 5s (32GB) has hugely increased. Several tips on the internet have been tried from turning off several services to reinstalling the IOS none with no improvement. After reinstallation the drain was acceptable only to result in again a -1% drain per five minutes after a week.
Expected: using IOS 7 I could easily use the iPhone throughout the whole day with -1% per fifteen minutes. After installing an improved IOS one would expect similar or lower battery drain
Tests: as said, severals tips found on the internet have been tested none with any improvement. Deleting all accounts under "Settings->Mail, Contacts, Calendars" proved to be the only solution for this problem (a non-functional solution I must add since I'm using this iPhone for communication...). Even keeping the iCloud account but disabling all iCloud services did not improve the situation, only a real account deletion worked.
Question: do you know how to get battery drain back to -1% per fifteen minutes whilst maintaining my iCloud and Exchange account using IOS 8.1.1 on an iPhone 5s (32GB)?
Kind regards,
Ronald

Since upgrading my iPhone 6 to iOS 8.1, my battery has not been the same. I was able to get 9-10 hours of usage before and am lucky to get 6-7 hours. AppleCare thought that was on the low side and told me to visit my local Apple Store for a thorough diagnostic testing of the battery. My appointment is tomorrow. Will report back.

Possible solution to iOS 7.0.3 battery drain issue (iPhone 5).

Not a question as such, but for anyone who's having battery drain issues on iOS 7.0.3 and doesn't want to attempt upgrade to iOS 7.0.4 revision yet...
I was having some problems with battery drain with my iPhone 5 since updating to 7.0.3. The device is only about 5 weeks old so I was quite annoyed that I had issues with it.
This morning after a full charge I did a hard reset. Now the problem seems to have gone. I've had the phone on for several hours (about 4.5hrs) and it's only just dropped to 99% moments ago. This is a massive improvement (on even the battery life of the device when I got it, and it had 6.1.3 factory installed).
I hope that this helps anyone who doesn't want to risk 7.0.4 until it's had a chance to cool off and for people to identify/resolve any issues (as I am waiting too).

The update isn't the problem. It was a problem with your update process. millions of others have updated without any issue at all.
Also resetting has been discussed many times in the never ending battery draining threads.

WiFi loss & battery drain a software issue, not hardware

I wrote the commentary below after installing IOS 7 on a 4S and resultantly losing WiFi entirely and enduring major battery drain issues. After two trips to the Apple store and meeting with their techs at the "genius" bar, I was emphatically told that the issues were entirely hardware related and the only solution was to purchase a new phone. I was told there was nothing more to be done because the hardware was defective... either just use the not-so-smart phone as it is or buy a new smart one.
Well, here's an update on that story. I installed 7.0.4 last night and instantly my WiFi was back on and working. So far today, the battery seems to be back to normal as well, not draining like a giant hole in the levee. I don't know if this will be the same story for anyone else with similar problems. But I can say that the hardware-caused-storyline was bogus. Entirely time coincident with a software update (IOS 7), I lost WiFi and battery. And equally relative to the 7.0.4 update I immediately regained WiFi and battery.
I'm curious if others have experienced this same thing? And if Apple has an official explanation?
Oct 14, 2013 12:37 PM
I had a perfectly functioning iPhone 4S (64 GB) that I have been very   happy with and has always been glitch-free, good battery time, no   complaints. Until installing IOS 7.
Among other things, immediately upon "upgrading" to IOS 7 I have lost WiFi entirely (button greyed out).
Next, I found the battery drains to the point where I have to keep it   charging 2-3 times per day with extremely small phone usage. In a normal day, with 2-3 text messages, checking email 3-4 times and no phone calls, I am down to 30% battery by 3pm. Two days ago I turned airplane mode on at 9am with 98% battery and by 4pm batter was at 45% with airplane mode still on.
There are other problems, but those are the two primary issues.
I   went to the Apple store two times. The first time the technician   verified my problem, said there was nothing that could be done because   it's a hardware problem now and I would have to buy a new phone at full   price (my current cell contract isn't up until March 2014). He suggested a complete phone reset to "new phone" which I did and which solved nothing whatsoever. Same issues exist.
On my second trip to Apple just yesterday the technician looked it over, checked the battery function, etc. and I was told that the battery is fine but that the processor or something in the phone is working overtime and draining the battery. And again, I was told there is nothing Apple can do other than swap out the phone, though, this time they would replace it for $199.
I was tempted to pay the $199 for a new 4S that the technician said would come with IOS 6. But so far I have refused that offer without some assurance that future IOS upgrades wouldn't harm that phone as well. Also, if I paid this now, then I wouldn't upgrade when my contract ended with Verizon and I was looking forward to perhaps getting a 5S then. I know that it's impossible to assure that these upgrade issues won't happen again to the next phone, which finally leads me to my questions...
Considering   the options I've been given thus far, what would someone more in the   know suggest I do? Is there any possibility of a software fix or did the "upgraded" software probably ruin the hardware?
As   a longtime Apple fan and someone who has owned the first Mac laptop and early desktops, I don't understand why Apple doesn't have better   customer service policies regarding their own software directly   affecting their own hardware adversely.

I have the same problem with WiFi and off, the issue was Google Play services, this is what I did settings > apps > all > google play services > clear data > uninstall updates > restart the phone > update the app > check again .

Severe battery drain after AT&T sim card replacement.

Up to a point, my wife's original iPhone worked fine. A week ago, it stopped connecting to the AT&T network, and after a call, we found out that someone at a retail store made an error when registering an upgrade to a 3g, and somehow started the process on my wife's account, which killed the sim card. I ran to the local AT&T store and they replaced the sim card for free, and all seemed well.
However, since then, her phone has been suffering from a severe battery drain. I have made sure that wi-fi, bluetooth, and location services are turned off, but it will not last 10 hours in standby mode after a full charge anymore (she makes no calls during the day - just leaves it in her purse on standby). I have tried a full restore of the software/firmware, and she is running the latest 2.02. Is there anyone who can help?

Sorry, no, that's not the issue. First, it's a 1st gen iPhone. Second, as I said in the question, I've already turned off every other unnecessary service on the phone. Basically, it's sitting in her purse on standby during the day, just as a phone, and draining from a full charge to nothing in about 9 hours. The problem only started after getting a new AT&T sim card. I'm wondering if anyone else has heard of this problem.

IOS7 Palattes: Why default to max brightness and battery drain?

After upgrading to iOS7 today my brightness slider was set to its maximum setting. I didn't think anything of it until I reduced it to 1/2 which is where I normally keep it to save on battery. I typically never have to change it even when outdoors. Today I received the surprise of a lifetime: It needs to be at near maximum just to see details like the call status bar. The WHITE text on the BRIGHT green bar is absolutely horrible and near impossible to read. I was hoping that I could change the color scheme of the status bar palettes but no luck. The best I could manage was to change the background wallpaper to a near black color that helped out only a tiny bit. What a waste of Retna display.
I can no longer use product this in an airplane cockpit for flight planning. I will have to abandon my planned purchase of an iPAD mini with Retna unless I can get iOS 6 on it
In the day light these new white screen backgrounds require loads more brightness to be able to see details and therefore causing unexpected battery drain not to mention creating a hazard of a night blindess (old scheme had dark backgrounds light text instead of other way around)..
Questions:
- How do we get rid of the white screens that require max brightness to see detail?
- How do we get customizable palattes? Customer knows better than Apple -- my eyesight can't handle white text and bright backgrounds for status bars.
- Will Apple see this as a priority one issue and give us CHOICES on the PALATTE schemes?

Hello,
I am currently an owner of an Ipod Touch 4th generation.
I have had battery drain problem on the Ipod Touch 4th generation.
But, I found a solution that works for me:
Do the IOS update (the one that is the latest, or if you already did, then proceed to step 2)
Reset All Settings: SETTINGS>GENERAL>RESET>RESET ALL SETTINGS
Use it until it dies (automatically shuts off)
Plug into Charge
Leave it 1.5 hours or longer after it reaches 100% --> Undisturbed (preferably overnight)
Give it a few days to Calibrate
This has helped me on my Ipod Touch 4th generation, running IOS 6.0.1
The battery seems to give me 2 days 30 hours of standby, and 10 hours and 15 minutes of usage.
Thats pretty good!

Nokia Lumia 920 potential battery drain issue?

Can you Nokia confirm this? http://reach.jdbpocketware.com/topic/128305-to-nokia-ref-lumia-920/
The issue illustrated in detail:
Nature of Windows Phone buttons
Pressing either the power button or the camera button will cause the device screen to turn on, even when the proximity sensor detects proximity.
[IMAGE http://i.imgur.com/M2to9.png]
The lockscreen behavior
Upon power on, screen lights up and shows the lockscreen (or camera), which runs a timeout to auto power off the device if screen is not touched in X seconds.
But if screen is touched, the timeout counter is restarted, so continuous touching could lead into a loop, the "death loop" which won't let the device to power off (standby) and will consume battery life.
[IMAGE http://i.imgur.com/2HNdV.png]
New touchscreen technology
The Nokia Lumia 920 comes with a touchscreen that reacts to touch from pretty much any material such as metal or clothes. This can be dangerous.
[IMAGE http://i.imgur.com/4tbyY.png]
So here is a theory
When the phone is inside a pocket or bag it can be touched by other objects. These objects can press buttons and can touch/rub the screen. This will initiate the "death loop" for who knows how much time, could be minutes or hours, depends on how active the user is since body movement will produce friction between objects/clothes and touchscreen:
[IMAGE http://i.imgur.com/XMT0y.png]
The "death loop" will drain battery and battery is precious.
Solution?
Should be simple: screen must not power on if the proximity sensor detects proximity. Current version of Windows Phone does not take care of this. The big question is: will Windows Phone 8 take care of this? Is the Lumia 920 a potential battery drainer?

I don't understand why we have to spend our valuable time in the forums for days and nights to FIND HOW TO FIX THAT CRAB!! NOKIA company did not handout these devices FOR CHARITY.All of us had paid around a thousand dollars to buy this Phone. They have got to work overtime to fix it and publish a solution otherwise recall the devices back.

Resolving battery drain with iOS 5 (not 5.0.1)

Hi
New iPhone user (first iPhone). Unlocked 4s 64Gb. iOS 5 United Kingdom
NOT impressed with battery drain so far and reluctant to "upgrade" to iOS 5.0.1 On standby (most services set to "off") phone has decent life (looking at about a week bofore the battery dies) but as soon as I start using the phone - eg browsing over WiFi, battery drops like a stone (4% in 20 minutes).
I can see lots of folks upgrading to 5.0.1 and doing a full battery drain, full reset & set-up as a new phone and this seems to resolve some issues.
My question is, does this same technique work with iOS 5??
Hopefully 5.0.2 (or whatever it is called when released next week) will sort this out - otherwise the 4s goes back to store for a refund.
Any comments gratefully received.
Cheers
RB

I have also noticed what appears to be decreased battery life after the upgrade, though not this bad. Seems many people are noticing problems.
I noticed and changed a couple of settings that seem to have helped.
- first, fully shut off the phone and then turn it back on - i read online this helped some, immediately after the update.
- in mail settings, for the icloud account (I dont use this but it was configured by default) check the sync settings . it defaults to push, which takes more power. you might want to disable push and set to fetch for this and any other accounts you have, for additional power savings
- in settings, location services, scroll to the bottom and tap system services : All of them are defaulted to on. I turned off location-based iads and setting time zone since i dont need those. (I also opted out of the diagnostics and usage as part of the setup, but it was set to on in this screen - i left it on for the time)
- also in settings -- location settings: check the list of apps and verify that only the ones you want, are enabled
These few settings seem to have improved things

IPhone 5 battery drain since iOS 8.2 update

hello,
my name is Udi, from Israel.
i have an iPhone 5 which i purchased in June 2013.
since the beginning, i have always kept the battery saving "rules", including correct charging of a lithium ion battery, auto-brightness off, reduce motion on, push notifications off, background app refresh off, cellular data off when not in use, etc. etc.
since updating to iOS 8, my battery life has decreased a little. but since updating to iOS 8.2 a few days ago, i have experienced, what is in my standards, a serious battery drain. e.g. when i sleep, with my iPhone on airplane mode at night battery decreases by ~15%.
i have tried everything, including restoring the phone and using a backup.
what can i do?
will a restore from scratch (without using a backup) help?
thanks in advance =)

If this does not help, get your phone checked by visiting an Authorized Apple Service Provider or Apple Store next to your place, or contact Apple Support and talk to them. They can check the battery online.
You can also visit this page to do that: iPhone - Contact Support - Apple Support
Click on Apple Support, then on ->Battery, Power &Charging ->Battery questions and troubleshooting, and follow the instructions.

Upgrade to OS4.1 causes fast battery drain with WiFi on

I've just upgraded the software on my 3G Pod to 4.1, only to find that it has led to a much quicker battery drain with the WiFi on. Is there a fix for this or can I revert to the previous OS?

Owen Glyndwr wrote:
Thanks llaass, but the discussion that you direct me to does not really address the issue of why a very recent upgrade should make such a significant difference. I had already realised that turning off WiFi makes a difference. Perhaps my question should have been addressed to Apple, since it appears that it is their so called 'upgrade' that has led to a deterioration.
I'm using iOS 4.1 on my iPod Touch 3 gen with no battery drain problem. This suggests that there is another factor at play which must be present to provoke this problem between the iPod and iOS (i.e., a specific App, a router type, or ?).

Zen Micro 2.20.05 (Audible) firmware has "battery drain" f

Since nobody responded to my questions about whether or not the "Audible firmware" for the Zen Micro (2.20.05) also applied the long-awaited "battery drain" fix for MTP/Janus users, I decided to test it myself by upgrading the firmware (even though I'm not an Audible user), then shutting it down and waiting 4 hours. I'm happy to report that my Micro "cold-booted" from the Creative copyright screen, just like ..0. So those of us that need subscription support (or Audible support, for that matter) no longer have to deal with the "battery drain" problem!!!
Since Creative still hasn't posted this firmware here, I'm reposting the link to it on the Audible site (as posted in an earlier thread):
http://download.audible.com/creative...le_2_20_05.zip
Download the file, then connect your Micro, open the file, and run the EXE file inside.
Audible users should also download and install the latest AudibleManager, as described in this thread (this step isn't necessary for non-Audible users):
http://forums.creative.com/creativel...ssage.id=88333
Since I have a third-party charger, I'll test it with my Micro later on to see if ..0's "locked charging" feature works with 2.20.05 as well. (It won't work right now because my Micro is fully charged.) I may also test to make sure it doesn't have the "super-drain" problem .0.02 had.Message Edited by RBBrittain on 09-9-2005 07: AM

luvmyrescuedogs wrote:
A big Thank You!!! for letting us know about the firmware upgrade for the Zen Micro. I just downloaded the firmware upgrade and upgraded my Audible Manager. No problems. It warned me that all my music would be wiped out, but it is all still there. Playing great. Wonder why Creative didn't announce it here before Audible did?
luvmyrescuedogs
I think the warning is for upgrading from .x firmware in general. Changing between the .x and 2.x families wipes out the hard dri've; minor upgrades within each family don't. (I didn't lose any of my music while going from 2..02 to 2.20.05 either.)
It's hard to say why Audible beat Creative to the punch; my best guess is that Creative is applying EU volume limits to the European version before releasing it anywhere. (Audible's UK site doesn't list the Micro yet.)

Battery drain question

Similar Messages

Maybe you are looking for