[HD2 Android SD Development] vinnie06:
heavy battery use

Hi, i have been using android (sd) for daily use and tried this build since this new year. It is a great build, because it is stable and smooth, but...

I have the same setup as the TS, but i had to apply the modified system.ext2 to get data to work. After this, data worked perfectly, but it became somewhat sluggish and laggy. After a few reboots this seemed to get better, it was still very usable anyway.

The battery life is the only real problem i have with this build. It shows about 56ma on standby with sync on background and BT and WiFi off. Below a short list from current widget log.

Could this be because of the system.ext2 i replaced or what could it be?

Currentwidget log: (3% in 20 min, 10 min standby)

2011/01/03 18:10:36,-151mA,48%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.manor.currentwidget;com.htc.launcher;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.tni.TasKiller;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

57mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.htc.launcher;com.manor.currentwidget;com.tni.TasKiller;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:13:33,-63mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.htc.launcher;com.manor.currentwidget;com.tni.TasKiller;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:14:26,-56mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.htc.launcher;com.manor.currentwidget;com.tni.TasKiller;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:15:19,-56mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.google.android.apps.maps;com.htc.launcher;com.manor.currentwidget;com.tni.TasKiller;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:16:12,-56mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.google.android.apps.maps;com.htc.launcher;com.manor.currentwidget;com.tni.TasKiller;com.htc.RosieUtility;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:16:42,-56mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.manor.currentwidget;com.qo.android.htc:Quickword;com.qo.android.htc;com.htc.bg;com.htc.launcher;com.google.android.apps.maps;com.tni.TasKiller;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:16:55,-56mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.manor.currentwidget;com.htc.bg;com.htc.launcher;com.google.android.apps.maps;com.tni.TasKiller;com.qo.android.htc;com.android.mms;com.htc.bgp;com.google.process.gapps;com.google.android.apps.genie.geniewidget;de.schaeuffelhut.android.openvpn;

2011/01/03 18:17:20,-171mA,47%,android.process.acore;com.android.phone;com.htc.android.htcime;system;com.manor.currentwidget;com.google.android.apps.genie.geniewidget;com.htc.launcher;com.htc.bg;com.qo.android.htc;de.schaeuffelhut.android.openvpn;com.tni.TasKiller;com.htc.bgp;com.google.process.gapps;

2011/01/03 18:17:54,-

EDIT: Tried the 'fix' from the other SuperRAM thread ([Dec 18][RAM] darkstone SuperRAM FroYo v1.5 [kernel: Hastarin custom]) for high usage and it seems to work, 5ma in standby and 150-200ma in use.

You might want to put the suggestion in this thread as well :) , although i do use it when using maps, but it does not have to be on all the time.