Related
Is this normal in WM5? CPU usage is 70% all the time (even after hard reset) and games are running very slowly. Is it problem in my device or is it normal. Am I doing something wrong?
Thank you for any help
Mondain said:
Is this normal in WM5? CPU usage is 70% all the time (even after hard reset) and games are running very slowly. Is it problem in my device or is it normal. Am I doing something wrong?
Thank you for any help
Click to expand...
Click to collapse
70 % remaining or used?
Not normal, which application eats the cpu?
70% used (in XCPUScalar)... when I look into DRrunning apps it shows that idle proceses are using 75-85 cpu usage.
Mondain said:
70% used (in XCPUScalar)... when I look into DRrunning apps it shows that idle proceses are using 75-85 cpu usage.
Click to expand...
Click to collapse
This is normal, it takes around 15% to show cpu usage.
Ok but it is normal that every game has really poor framerate? Even my friend with mda 1 has now better performance than me...
Mondain said:
Ok but it is normal that every game has really poor framerate? Even my friend with mda 1 has now better performance than me...
Click to expand...
Click to collapse
Nope, but which rom do you have? Have you a lot of background apps? What is the status of the memory?
dotfred said:
Nope, but which rom do you have? Have you a lot of background apps? What is the status of the memory?
Click to expand...
Click to collapse
I am using C_shekhars ROM (24 pagepool, 40 ramdisk)
As I said it is doing it even after hard reset with no apps. I have almost 50MB free program memory now. I think thats enough for a game like worms world party, so problem must be somewhere else.
why not try without XCPUScalar
maybe it's underclocking the device
I did hard reset and everything seems to be fine now... really strange because I tried hard reset several times. I'll install apps one by one and find that one which is responsible.
Thx for all help
Rudegar said:
why not try without XCPUScalar
maybe it's underclocking the device
Click to expand...
Click to collapse
Mine using c_shekhar latest ROM(24 pagepool, 40 ramdisk) & without XCPUScalar no other application running in backgroud but the CPU usage show is 70 to 85% for idle process. It is normal?
zaidam said:
Mine using c_shekhar latest ROM(24 pagepool, 40 ramdisk) & without XCPUScalar no other application running in backgroud but the CPU usage show is 70 to 85% for idle process. It is normal?
Click to expand...
Click to collapse
What tool are you using to show cpu usage ?
Most of the time, only showing the cpu usage takes around 15% of the cpu!
Cheers,
.Fred
i am using DFRunningApps (Task Manager v1.9) which is come with current
c_shekhar ROM
zaidam said:
i am using DFRunningApps (Task Manager v1.9) which is come with current
c_shekhar ROM
Click to expand...
Click to collapse
Yeap, as I mentioned earlier. Showing the CPU usage with TM takes around 15 % because it is updated every second.
Cheers,
.Fred
Rudegar said:
why not try without XCPUScalar
maybe it's underclocking the device
Click to expand...
Click to collapse
This is an excellent idea.
XCPUScalar does not properly store your settings when toggling 'dynamic' mode on or off - the process is this:
1. set dynamic on, then set up your cpu vs load speed ranges
2. EXIT xcpuscalar
3. launch it again
4. set dynamic off, then exit
5. start again
6. choose a speed for when the machine is charging on the first page (the slider above 'dynamic' mode toggle)
7. exit
8. start again, turn on dynamic mode
9. exit
10. DONE! it's now safe to run, and will remember your settings
this bit me in the ass for a long time. sometimes it would underclock so hard I couldn't answer calls - other times, it was running at 500mhz and giving me about 2 hours on a full charge.
XCPUScalar won't let you configure everything at once. it's great when you get over that.
I'm not sure if this is normal, so I thought I would ask some of the pros here at xda. When I soft reset my Fuze it generally starts out at about 37%. active sync kicks on, which by the way I've been trying to find how to keep this from coming on automatically, but no luck. This puts it at about 40%. Once I use something like sky fire, and I'm at 53%. This wouldn't bother me ,but it's at 50% after I've closed the program, and it stays there, draining my battery. is this normal? any suggestions, if it's not?
Oh ya, I forgot to mention.
Running NATF's v2.3 ROM
Stock Radio
don't know if this matter but, Fuzeberry v3.0 w/ L.S. carbon dialer skin, and Icontact contacts.
Yes when I had Touchflo enabled my memory usage was exactly as yours.
You can prevent activesync from opening up at startup by going to Settings>Personal>Phone>Timezone>uncheck Automatic change timezone and clock
behrouz said:
Yes when I had Touchflo enabled my memory usage was exactly as yours.
You can prevent activesync from opening up at startup by going to Settings>Personal>Phone>Timezone>uncheck Automatic change timezone and clock
Click to expand...
Click to collapse
nah that fix doesnt work
trust me ive tried about 6 different things nothing stops it
*posted message in the wrong board >.<
I looked right at my fuze when i read your post. I'm at 47% with mail and Windows Live messenger open. I wouldnt be that worried about your memory usage.
Im usually Hovering at 45% to 50% with nothing running and with TouchFlo Enabled... I figure this is normal but i wish i could lower it
cool. I just wasn't sure if that was normal or not. figured I'd get some user's feedback. thanks all. As far as the active sync I guess I'll give that a shot. but i guess it only uses like 1% of the CPU any way so whatever.
I believe you are referring to Memory Usage and not CPU usage. If you CPU is constantly at 47% then you should be concerned. If its just your memory I wouldn't worry too much. When I soft reset Im at 30% usage with TF3D and that creeps up to 40%. I can usually keep it at about 40% using MemMaid and Task Managers.
Keep in mind every menu you open cache's the icons and wastes memory. So if you go into the settings menu and then open you programs folder along with subfolders. Everytime you do this the icons have to load into memory and will stay there. Also some programs don't close completely and stay running as a process. I would recommend getting a task manager that can kill processes. FDCSoft Task Manager is free and works perfect.
yeah after a reset with tf3d im usually at 36 or so
after running stuff then using memaid to clean im back at 40
i have a 32 mb pagepool, and with no tf3d im at 36% 118/184 then with tf3d im at 40-43% depending on apps, and i never go above 48% when im playing a game with tf3d on
So TouchFlo takes up decent space but not crazy space
considering the amount of ram the raphael has the amount of ram TF3D takes up is very insignificant. As for CPU usage.....once its already fully loaded into ram it shouldn't use very much if any cpu at all.
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Click to expand...
Click to collapse
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Eh, this is the first I've heard this. I don't remember reading this in the various battery optimization guides.
Still is there a was to stop things short of uninstalling? For example, I want to stop using the Yahoo Mail app but don't want to install yet. I went through all the options I could to disable checking/notifications, etc but it still pops back into memory constantly.
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Sent from my HTC Magic using XDA App
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Streaker said:
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Click to expand...
Click to collapse
I leave wifi on since I'm usually in range. It's more efficient than 3g right? I alway sleep the device when I'm done. I still have huge percentages on the screen when looking at the battery usage. I'm trying a completely black screen now.
Mainly your widgets and icons and stuff still cover large portions of it, so: a black screen will help, not but alot.
Also, to keep items in RAM, to the second poster... What do you think is keeping those items in RAM?
Ummm... It's the CPU.
Task Killers won't help you on RAM usage at all (Because Android will automatically shuffle them out if it has to, or so I've read... I've yet to hit max memory). Task Killers DO help you as far as battery use goes, though... Keeping the browser killed if you aren't using it, etc.
Bjd223 said:
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Click to expand...
Click to collapse
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
asrrin29 said:
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
Click to expand...
Click to collapse
The app itself at that point may not be but the Android OS still does to maintain that suspended state.
I have some applications I rarely use or even some that I've never used but may want to in the future. I see absolutely no benefit in keeping these applications in the background. Further more, I've noticed a signficant drain on the battery when extra applications are running in the background. I'm sure it's not all of them, but I've yet to discover who exactly the culpit is. Right now I suspect it's the NPR app, perhaps due to data use?
The point is, there are perfectly good reasons to keep some apps in the background, and perfectly good reasons to kill others - or perferrably not have them start up at all unless I do it myself. Could be due to data usage (especially if you do not have unlimited data), could be due to concerns about excessive cpu usage. There really should be a clear method in which you can stop applications from opening on their own.
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Wouldn't tasker also help?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my AOSP on XDANDROID MSM using XDA App
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background.
Click to expand...
Click to collapse
Unless the background process is syncing data, it won't eat your battery. So instead of wasting your time, you should focus on other energy hogs. Things like screen brightness, bluetooth, wifi, and gps.
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I installed Advanced Task Killer from the Market. It lets you kill all running applications including itself.
durrence
jsmith8858 said:
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Click to expand...
Click to collapse
Or an auto-killer would've killed it before it killed your battery by 38% lol
Task Killings are bad, mmmkay...
Slightly off topic:
To help conserve battery power,
Use an all black desktop background since the black areas dont use battery power.
Hmm, people in this thread have said a few things that I haven't heard or seen much before. Specifically that killing apps could decrease battery life. When I first downloaded advanced task killer I tended to kill most things. I slowly backed off and now I've been watching what launches and what tends to come back and not kill those (mail apps, widgets, performance watchers, etc). The second is that not having a black background doesn't necessarily improve battery life. Makes sense considering I have icons everywhere on my screen.
@Shuggins - Thank you! That's exactly what I was looking for. I've downloaded it but now I have to, er charge my battery a bit before I can take a close look at it.
@jsmith8858 - Are you running setCPU? A couple days ago I noticed my battery running pretty hot. I stopped using setCPU and the battery cooled down a lot. I've used setCPU since them without the heat issue so I'm not sure what was going on.
Well during todays iteration I ran for about 12 hours (typical). I had a couple short phone calls, 2 email accounts syncing as well as other bg syncing processes. I did eat up 30% in an hour messing with a game. I'd probably have 13-14 hours if I didn't play anything (but if I didn't what's the point of the phone . Still, as much as I love it the screen is killing me. Guess there's nothing to do about it though (usually brightness is all the way down, turn it off when I'm not using it, using a darker background). I didn't kill any of my background processes today. I'm going to set up that Autostarts program and start auto-killing various programs tomorrow.
You can try using autokiller and art it to extreme, but I don't recommend this
Sent from my HTC Dream using XDA App
The last couple of days my battery has been draining ridiculously fast. It just went from 50% to 8%, just sitting in my pocket without otherwise being used, in the last 3 hours. Here's what the battery usage displays:
while unplugged for 3h 3m 24s:
Android OS 81%
Cell standby 10%
Phone idle 4%
Display 3%
Android System 2%
Obviously something is going on with Android OS and I suspect something I've installed is doing this. I have Watchdog installed but it hasn't given me any warnings. Is there some way to determine exactly what is causing the battery drain, other than removing apps one by one?
Thanks!
I've suspected that my display keeps coming on when my phone is in my pocket.
Both the power button, and the trackpad turn on the backlight for 15 seconds when pushed, and it's very easy to do both when the phone is in your pocket.
I stopped using the HTC weather app, there is no way to stop it from constantly searching your location and it kills the battery FAST if you are on the move. Since I stopped using it I have seen 10+ hours of battery life a day and I use it hard, internet, gps, music, twitter.
It's the suspend process.
I can't link it to you cause I'm on the phone but if you look around, you'll be able to find it.
Sent from my HTC Glacier using XDA App
I don't think it's the display because the battery usage isn't showing the display as the main battery usage (unless I'm really using it for a long time). It's definitely something belonging to "Android OS". I wish there was a way to determine specifically what process within "android OS" is to blame. I really don't know much about Android or Linux in general so "android OS" is mostly a mystery to me.
I did uninstall several programs yesterday night and was almost convinced it was behaving better but it looks like after the first hour that Android OS is creeping up and overtaking the battery usage and the battery is draining pretty fast despite not using the phone other than to occasionally check the battery usage. At the current rate I'd be lucky if the phone isn't dead before the end of my workday. It probably doesn't help that I have a rather weak signal at work but if it was increased power to the cellular radio that was the culprit, would it show up under "Android OS" or "Cell standby"? I'd suspect the latter, but maybe Android isn't so logical in how it groups processes....
I'll try removing the HTC weather widgets as suggested and look up the sleep process.
Thanks!
It is the "suspend process" like that other poster said. Here is the defect, you can read through if you like. It's a known problem and not only isolated to mt4g
http://code.google.com/p/android/issues/detail?id=11126
How did people determine it's the "suspend" process? I can't seem to find any way to determine what processes are specifically involved. Is there an app that will tell you that? I am running Watchdog Lite set to alert me at 50% cpu and have never got an alert which makes me question whether my issue is the same one described in that thread. Various people were describing 100% cpu activity by the suspend process and it doesn't seem to be the case with me.
I did have 2 weather widgets on my home screen. I deleted both and since then the problem appears to have gone away. I'll have to wait a while to see if it's truly fixed or just a coincidence. Someone in the suspend thread did mention that plugging into a charger temporarily fixed the issue and I did charge the phone for a while after deleting the widgets so I'm not convinced just yet.
One thing I did notice in the battery usage is that google maps seems to have a significant presence, despite the fact that I haven't used maps at all since last unplugging the phone. What is maps doing in the background? I wonder if it's trying to determine my location and cache map data...
Thanks!
Install Watchdog and in its settings, include, monitor, and display all phone processes.
HTC Glacier running CM7 #15
Enable system process and set thrashold to 30% and you will see the suspend process. Or when you notice the drain is happening go to the phone hidden menu. You know the #*#*3626*#*# in the dialer and then from there go to battery usage then select CPU usage, you will see the suspend process on the top or near the top.
Just use some memory management apps. I currently use ES task manager and in advanced settings, i set it to kill all processes when i power down screen. I never use any battery when phone is unplugged(i literally left my phone unplugged overnight midnight to about 7am and it stood at 73% entire time). And having it rooted, i use SetCPU and set the phone at around 768mhz powersave when i'm not messing with the phone heavily. I easily can squeeze about a day and a half out of the battery.
knaries2000 said:
Enable system process and set thrashold to 30% and you will see the suspend process. Or when you notice the drain is happening go to the phone hidden menu. You know the #*#*3626*#*# in the dialer and then from there go to battery usage then select CPU usage, you will see the suspend process on the top or near the top.
Click to expand...
Click to collapse
Is that the correct sequence/code? I put that in and didn't get anything. Is root required?
Sent from my HTC Glacier using XDA App
sorry, that was not the correct sequence at all. I was trying to do it by memory. It is *#*#4636#*#* then select battery history, in the first dropdown box select cpu usage. That menu is pretty useful for other things to like network usage breakdown per app, gps usage, etc.
el-jodio said:
Is that the correct sequence/code? I put that in and didn't get anything. Is root required?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for all the info. I particularly like that hidden menu. I had no idea that existed...
Since removing the HTC weather widget my battery drain issue has completely disappeared. The battery now lasts a reasonable amount of time.
Thanks!
knaries2000 said:
sorry, that was not the correct sequence at all. I was trying to do it by memory. It is *#*#4636#*#* then select battery history, in the first dropdown box select cpu usage. That menu is pretty useful for other things to like network usage breakdown per app, gps usage, etc.
Click to expand...
Click to collapse
Thanks. Are there any other secret codes that do other things? Like the *#*#checkin#*#*
Sent from my HTC Glacier using XDA App
checkin menu does exist too. Those are the only 2 I know off. If other people here know of any please post.
Actually I have removed the HTC weather widget couple of days ago and also disabled the water sync in account settings too. That seems to have help with the suspend process on my phone also.
knaries2000 said:
Actually I have removed the HTC weather widget couple of days ago and also disabled the water sync in account settings too. That seems to have help with the suspend process on my phone also.
Click to expand...
Click to collapse
What's the "water" sync? Is that a swype typo for "weather" sync? (Swype errors are annoying in that their usually not so obvious.)
I had also disabled the weather sync (forgot to mention it). Seems to be a lot of little bugs in Sense that need to get fixed.
Why don't you guys do what I did... I have profiles set on setCPU so that when the screen is off the phone runs at 368mhz max and the when the screen is on it'll go up to opp speed... That actually saves alot of battery for me.
Sent from my HTC Glacier using XDA App
Sorry it is weather sync. Yeah keyboard error. I stopped using swype recently for this very reason, but touch input isnt perfect either but still much better for me.
Ya if you are using OC based kernel then use SetCPU to scale your mCPU. Set few profiles for example my max is 1.7ghz, avg is 1.2ghz, min is 768mhz, idle is 368mhz.
Sent from my HTC Glacier
Is there any way to prevent the Surface from automatically shutting down when the battery reaches 5%?
I feel it's a waste of 5% of battery if the OS does not allow it to be utilised ...
Yeah plug in the charger
I have tried to go into settings and advance power management to try and remedy this, but no luck. It's programmed into the OS, I'm assuming, that the critical battery level is 5% and that's when the device has to shut down. (Same as in laptops as well.)
Is there anyway to bypass this though? Through registry tweaks, perhaps? I mean, the RT does have a command prompt; can we not put that to the test?
Bump.
arsi123 said:
Bump.
Click to expand...
Click to collapse
The OS thinks that you need at least that much power to finish saving your work and for it to do its background tasks before shutting down cleanly. I wouldn't want to change that.
Of course, that doesn't answer your question
I changed the low battery notification to 10%, it gives me time to plug it in when it's nearly low. Before then I'd be watching a video and it would give me the warning and shutdown almost immediately.
How did you do that?
boredtoday said:
How did you do that?
Click to expand...
Click to collapse
I've also done the same thing. Here's how (this also tells how to change auto shut-down):
1. Search battery, tap "Settings" on the searchbar.
2. Tap "change battery Settings"
3. In the following screen, tap "Change plan settings", then "change advanced power settings"
4. In that window, tap the "Battery" option
5. There are options that say "Low battery level" and "Critical battery level" you can change low battery level to change when the notification shows, and critical battery level to change the auto shut-down. I only turned critical to 4% to avoid doing a "dirty" shut-down, so as not to damage the system.
If I helped, please hit thanks!
I've not touched mine and its set to 3%....
Something done in an update perhaps?
Trig0r said:
I've not touched mine and its set to 3%....
Something done in an update perhaps?
Click to expand...
Click to collapse
ditto
So, just had to post this: it seems the Surface auto shuts down sooner if you set it below 5%. I had mine at 4%, and realized after a couple months (I don't usually hit the bottom of my battery) that it would shut down at about 7%. After re-setting it to 5%, it now ekes out a couple more minutes and goes all the way to 5%. So my recommendation is to leave it as it is.
If you make a new power plan, you can set it to below 5%, but I wouldn't do that if I were you...there's a reason it's set to 5%. You don't want those batteries to go to zero. Their life significantly reduces if you drop to to zero and full charge it constantly. It's better to let it only drop to 5%. In fact, I changed mine to 10%. The more you let your battery die, the more discharged it gets over time.