Wednesday, September 26, 2012

iPhone 5 Battery life and Google Voice/Facebook

The iPhone 5 is a great phone. I really was disappointed with the battery life. I would loose 20% of my battery over night. Throughout the day, I would end up needing to charge it more frequently. I figured out the culprits to be Google Voice and Facebook after following all of the tips on the other sites.

For Facebook, it would be best to logout when not using it to avoid frequent data usage  Don't worry, it will still save the username and password for next use.

For Google Voice, it constantly uses data to check for new messages which will drain battery life. I ended up switching to my mobile number and experienced far better battery life.

Here are the commonly used tips floating around on the Internet that help immensely in addition to Facebook and Google Voice:


1. Set the screen brightness low as possible.
2. Turn off location services.
3. Disable as many notifications as possible.
4. Under mail preferences, turn off Fetch new data.
5.Change fetch interval to manual.
6. Disable LTE
7. Turn off Wireless
8. Turn off Bluetooth

Friday, July 6, 2012

New GUI for MephistoBackup v1.16

This is the new GUI currently in development for the next release of MephistoBackup in February. More screen shots will be added as more development happens.

If you would like to build it from source from Netbeans and try the new GUI now, please watch this video:

Tuesday, March 27, 2012

How to generate a crash dump on Redhat Linux

This is a guide on how to gather a crash dump on RHEL systems.

First, install the following packages:
# yum install kexec-tools crash kernel-debuginfo kernel-debuginfo-common system-config-kdump 

In graphical mode:
# system-config-kdumpIn the target settings tab:
Select the appropiate Path: and Partition Values.
Click Apply.
Reboot the system.

In console mode:
Edit the /boot/grub/menu.lst file:

Add "crashkernel=128M" to the kernel line:
kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M

Modify the config file: /etc/kdump.conf

Modify these values for where the core file should be stored:

ext3 /dev/sda4
path /var/core


Capture the core: (This will panic the system and may take a long time to complete)

# echo c > /proc/sysrq-trigger Locate the core:
# ls /var/crash Analyze the core:

# crash /var/crash/2012-03-29/vmcore /usr/lib/debug/lib/modules/`uname -r`/vmlinux

Available Commands:
crash> sys
crash> bt -a
crash> mod
crash> log
crash> sys