Macbook Pro Battery

-
One thing I realized with my last Macbook (White) is that putting your macbook to sleep all the time and never shutting it down (especially overnight) is not good for your battery. By doing that I've had consumed more battery cycles and now the battery discharge time has come down to just over 2 hours. Last week I got a new macbook pro. And this time I figured out how to make it hibernate (not sleep) upon closing the lid. With that, I've managed to do only 3 cycles of battery recharge in last one week.

Here's how to put your macbook to deep-sleep (hibernate):
Put these two lines in your ~/.bash_profile:

alias hibernateoff='sudo pmset -a hibernatemode 0'
alias hibernateon='sudo pmset -a hibernatemode 5'

And whenever you are about to close your lid (like before you go to bed), just turn hibernate on by invoking hibernateon in terminal. At other times, when you don't want it to go to deep-sleep, just turn hibernate off. This is useful when you close your lid while moving between meeting rooms etc in office.

Also, I realized that these new batteries don't need to be discharged and recharged regularly as they don't have the "memory" problem like the older technology batteries did. So I use battery only when I need to and stay on power adaptor when I can. This way I can keep my battery cycle count low.

Here's my battery info for future (self-) reference:
+-o AppleSmartBattery  
    {
      "ExternalConnected" = Yes
      "TimeRemaining" = 0
      "InstantTimeToEmpty" = 65535
      "ExternalChargeCapable" = Yes
      "CellVoltage" = (4189,4189,4190,0)
      "PermanentFailureStatus" = 0
      "BatteryInvalidWakeSeconds" = 30
      "AdapterInfo" = 0
      "MaxCapacity" = 5573
      "Voltage" = 12568
      "Quick Poll" = No
      "Manufacturer" = "DP"
      "Location" = 0
      "CurrentCapacity" = 5573
      "LegacyBatteryInfo" = {"Amperage"=226,"Flags"=5,"Capacity"=5573,"Current"=5573,"Voltage"=12568,"Cycle Count"=3}
      "BatteryInstalled" = Yes
      "FirmwareSerialNumber" = 9626
      "CycleCount" = 3
      "AvgTimeToFull" = 0
      "DesignCapacity" = 5450
      "ManufactureDate" = 15124
      "BatterySerialNumber" = "xxxxxxxxxxxx"
      "PostDischargeWaitSeconds" = 120
      "Temperature" = 3099
      "InstantAmperage" = 0
      "ManufacturerData" = <000000000000000000000000xxxxxxxxxx000000000000000>
      "MaxErr" = 1
      "FullyCharged" = Yes
      "DeviceName" = "xxxxxxxxx"
      "IOGeneralInterest" = "IOCommand is not serializable"
      "Amperage" = 226
      "IsCharging" = No
      "DesignCycleCount9C" = 1000
      "PostChargeWaitSeconds" = 120
      "AvgTimeToEmpty" = 65535
    }

As this battery is deigned to last 1000 cycles I'm hoping this battery will give me 6hrs backup when I need it for a long long time - at least 3 years.

Popular posts from this blog

Linux IPC and Limits

-
Note: POSIX implementation provides better and cleaner api to IPC compared to System V. Prefer using POSIX api if you are known to be running on 2.6 or later kernel. System V IPC implementation on Linux includes Shared memory, Semaphores and Message queues. There are system imposed limits that are important to keep in mind when developing application/services in Linux. To know the limits use ipcs command. For example on my system: [root@f7 ~]# ipcs -l ------ Shared Memory Limits -------- max number of segments = 4096 max seg size (kbytes) = 32768 max total shared memory (kbytes) = 8388608 min seg size (bytes) = 1 ------ Semaphore Limits -------- max number of arrays = 128 max semaphores per array = 250 max semaphores system wide = 32000 max ops per semop call = 32 semaphore max value = 32767 ------ Messages: Limits -------- max queues system wide = 16 max size of message (bytes) = 8192 default max size of queue (bytes) = 16384 Or via sysctl interface: kernel.shmmni = 4096 kernel.shmal...
Read more

htop: more than top. pstree: ps with tree.

-
Image
I'm a big fan of procexp and other sysinternals tools on Windows. Many people who use those and then come to Linux complain that there are no such tools in Linux. Most people are familiar with top and ps commands. I would like to introduce you to a bunch of utilities on Linux that are very useful while debugging issues. Lets start with htop, a better alternative to top. You can install htop on a yum based system like Fedora, Redhat, CentOS etc with "yum -y install htop" or with "apt-get install htop" on systems that are debian apt based like Ubuntu. htop is much better in displaying the process and resource information than top. It gives a more accurate and clearer picture of process memory usage than top. A screenshot of htop in action: It has many interesting features. It's display layout is refreshing different and nice. It can show tree view, a very important feature to understand the ancestry of a process. In the size column, the MB part is hig...
Read more

Access Apache WebDAV from Windows XP

-
This is a work-in-progress. This is not complete, may be never will be. It is purely for my own reference. Use at your own risk. Here I try to remember how to configure Apache and Windows XP so that WebDAV on Apache is accessible from Windows XP clients. Links: http://www.thrrrust.com/~pclark/blog/2005/03/fun-with-windows-xp-and-webdav.html http://www.hss.caltech.edu/help/unix/admin/web/apache-webdav-xp http://support.microsoft.com/?kbid=909423 http://www.greenbytes.de/tech/webdav/webdav-redirector-list.html Registry changes required to support large files and many files: http://support.microsoft.com/default.aspx/kb/900900/ http://support.microsoft.com/?kbid=912152 Automatic Protocol Driver Selection for MSDAIPP http://msdn2.microsoft.com/en-us/library/ms691698.aspx http://msdn2.microsoft.com/en-us/library/ms691696.aspx http://msdn2.microsoft.com/en-us/library/ms691722.aspx DHTML Behaviors for making webfolder open automatically. http://dean.edwards.name/moz-behaviors/ http://msdn.micr...
Read more