Razr Maxx Battery Issues?

[avenged61973]

I would still like to see a factory battery stat shot.

Sent from my DROID RAZR using Tapatalk 2

 

[TriciaH]

Sorry if this was mentioned but did you change the mobile network from Global to LTE/CDMA? If not that can def be a battery killer.

Ohhh good point! As I have been on JB since the 24 Dec push, I forgot that I had to change that right after the installation.

 

[mcal24]

I would still like to see a factory battery stat shot.

Sent from my DROID RAZR using Tapatalk 2

A factory one usually just says screen about 45% and Android OS about 30-40%.

 

[mcal24]

I have noticed that my Phone app has been doing something, although I have yet to use it on this charge. And I just switched over from global to LTE too. Also, I disabled Google Now and Motorola Processes (not sure what those do, but it looked like it could be a problem) and now my keep awake time under Kernel is completely gone. The keep awake time under phone is up to 30+ minutes already though.

View attachment 61876

View attachment 61877

 

[aarong03]

I have noticed that my Phone app has been doing something, although I have yet to use it on this charge. And I just switched over from global to LTE too. Also, I disabled Google Now and Motorola Processes (not sure what those do, but it looked like it could be a problem) and now my keep awake time under Kernel is completely gone. The keep awake time under phone is up to 30+ minutes already though.

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=61876"/>

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=61877"/>

I'm still trying to figure out why the OS is running so much. Not sure why it is.

View attachment 61878



View attachment 61879

 

[bruben7886]

I'm still trying to figure out why the OS is running so much. Not sure why it is.

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=61878"/>

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=61879"/>

Is this screen shot right after the phone was idle for some time? If so, kernel will go down as you use the phone. JB is good at using not much else when the phone is sleeping. Kernel will show high % when you wake it up because it's pretty much the only the only thing that was running. As I mentioned in another post, it's kinda like your heartbeat being the system that most used your body's energy while you were sleeping.....after you wake up your arms, legs, etc will use a higher %, so your body's "% meter" will show your heart as using less.

 

[_skibum]

I'm still trying to figure out why the OS is running so much. Not sure why it is.

I'm looking at your stats and I think everything looks fine. Your phone has been on for 10 hours and you have used 6% of your battery. The OS is running, but it is basically just sitting there idle, running it's loop looking for something to do. I think the OS reading is high because your phone has not been doing much of anything else. It says that you are getting an average of 31 hours per charge. Does that seem correct?

The kernel (OS) runs all the time. Its job is to monitor and manage every other thing that runs on the phone. It runs in the background. It processes all input, output, system resource requests from applications, it manages all of the hardware (sensors, memory, radio, screen, GPS, etc.). In short, it does everything all the time. If you stop every other application and service on your phone, 100% of your battery usage would be used by the kernel. If you run a bunch of apps, the amount of battery used by OS will go down because you are looking at a percentage. The OS will still be doing the same amount of work, but other apps will be doing more than they are now. As the percentage of battery used by the apps goes up, the percentage used by the OS will go down.

Sorry for the long windedness. Former UNIX support geek here...

 

[GotnFX]

I'm looking at your stats and I think everything looks fine. Your phone has been on for 10 hours and you have used 6% of your battery. The OS is running, but it is basically just sitting there idle, running it's loop looking for something to do. I think the OS reading is high because your phone has not been doing much of anything else. It says that you are getting an average of 31 hours per charge. Does that seem correct?

The kernel (OS) runs all the time. Its job is to monitor and manage every other thing that runs on the phone. It runs in the background. It processes all input, output, system resource requests from applications, it manages all of the hardware (sensors, memory, radio, screen, GPS, etc.). In short, it does everything all the time. If you stop every other application and service on your phone, 100% of your battery usage would be used by the kernel. If you run a bunch of apps, the amount of battery used by OS will go down because you are looking at a percentage. The OS will still be doing the same amount of work, but other apps will be doing more than they are now. As the percentage of battery used by the apps goes up, the percentage used by the OS will go down.

Sorry for the long windedness. Former UNIX support geek here...

Awesome write up skibum! Not challenging you in anyway as I have no clue when it comes to UNIX or programing in general, but weird the tweaks put in JB has caused OS to be higher than ICS..I think this the concern.

 

[TriciaH]

Excellent explanation for the OS usage! You are going to have some keep awake time - any streaming apps you use, etc will keep the phone awake. Awake 1 hour out of 10 sure isn't excessive. With the global changed you may find that your battery is heading back towards the good side. You are definitely making progress!

I am really curious why JB changes it to global from LTE. Mine was changed at first too and I know I did not change that.

 

[aarong03]

Thanks, I just thought it was strange for the Kernal to be running so high overnight. I checked it as soon as I got up this morning and that is the percentage it was running at. But thanks again for the posts, always know I can count on the members here for advice or feedback!!!

 

[mcal24]

Battery seems back to normal today. I still have 1.5 to 2 hours of keep awake time though. No big drop offs or anything today.

View attachment 61889

 

[TriciaH]

Awesome! I always have some awake time...if you use the phone you will but mine was running like 9 hours of awake time! Your stats look good! :icon_ banana:

 

[_skibum]

Awesome write up skibum! Not challenging you in anyway as I have no clue when it comes to UNIX or programing in general, but weird the tweaks put in JB has caused OS to be higher than ICS..I think this the concern.

Challenge away. The Android OS is based on Linux, not UNIX, but the basic principles are the same. My guess is that you are looking at it backwards. JB is smoother, and snappier. To me, it seems that they optimized JB so that it makes processes get on and off of the processor more efficiently, which leaves more time for the OS to do the basic work of running the phone. My phone has been on for 31 hours and the Android OS has only used 4.5 hours of CPU time. That tells me that for about 26 hours, the CPU was free to do other things. Pretty good by most OS standards.

 

[TriciaH]

Blows Windows out of the park!!!

 

[GotnFX]

Challenge away. The Android OS is based on Linux, not UNIX, but the basic principles are the same. My guess is that you are looking at it backwards. JB is smoother, and snappier. To me, it seems that they optimized JB so that it makes processes get on and off of the processor more efficiently, which leaves more time for the OS to do the basic work of running the phone. My phone has been on for 31 hours and the Android OS has only used 4.5 hours of CPU time. That tells me that for about 26 hours, the CPU was free to do other things. Pretty good by most OS standards.

Wait..I honestly think I understand you believe it or not.lol...I remembered you had said that if everything is off on the phone..not running, then OS would be 100% of battery...but as apps are turned on or used, then the processor basically forgets about OS and focuses on the app or apps turned on, thus lowering the battery percentage used by OS and increases for the app or apps in use...then as apps turn off or are pushed aside (maybe not the best wording), then OS starts back up again..taking charge or should I say discharge of the battery..is this right or am I still way off?