Bagpuss
17-04-2006, 12:32 AM
My friend and I have both starting using the new AKU2 iMate rom recently.
We both had exactly the same software installed, live in the same place, and use the same network. The only problem being, his battery life was dramatically reduced, whereas mine was just the same as with the old o2 software.
For him, reverting back to the o2 software fixed the battery drain problem, so it was definitely a software issue.
After much head scratching, and comparing we've discovered the problem.
It all comes down to the fact that he uses WiFi at least once a day to check for traffic information on our route home. This in itself isn't the cause of the problem, but his use of WiFi is.
We've discovered that the new Comm Manager application does not properly turn off radio comms, even though it claims that it has.
To see the problem, try the following:
1) Fully charge your XDA.
2) Before you go to bed, turn on WiFi using Comm Manager and connect to your access point.
3) Turn WiFi off using Comm Manager.
4) Leave XDA in standby.
Leave the XDA overnight, and the battery will probably be completely discharged by morning.
It appears that the Comm Manager does not properly turn WiFi (or any of the other radios) off, even though it says it has.
WiFi causes the problem to manifest most obviously, as it consumes the most power, but the same is true for all of the other wireless in the XDA.
We tried another test where we fully charged the XDA, switched on all the radios (GSM, bluetooth and WiFi). We then switched them all off, and left the XDA overnight. By morning, the unit was completely dead.
We then repeated the same experiment, but did a soft reset after switching the radios off. When we came back to the XDA in the morning, the battery was still showing 99%.
If he never turns the WiFi on, then his battery performance is the same as with the current o2 rom.
This seems like a major bug, especially as this seems to indicate that putting the unit into 'flight mode', doesn't actually turn the radios off.
We've also tried reverting back to the 1.06 radio rom, and this doesn't fix the problem.
If anyone else out there can test this, please let us know if you see the same thing.
Bagpuss.
We both had exactly the same software installed, live in the same place, and use the same network. The only problem being, his battery life was dramatically reduced, whereas mine was just the same as with the old o2 software.
For him, reverting back to the o2 software fixed the battery drain problem, so it was definitely a software issue.
After much head scratching, and comparing we've discovered the problem.
It all comes down to the fact that he uses WiFi at least once a day to check for traffic information on our route home. This in itself isn't the cause of the problem, but his use of WiFi is.
We've discovered that the new Comm Manager application does not properly turn off radio comms, even though it claims that it has.
To see the problem, try the following:
1) Fully charge your XDA.
2) Before you go to bed, turn on WiFi using Comm Manager and connect to your access point.
3) Turn WiFi off using Comm Manager.
4) Leave XDA in standby.
Leave the XDA overnight, and the battery will probably be completely discharged by morning.
It appears that the Comm Manager does not properly turn WiFi (or any of the other radios) off, even though it says it has.
WiFi causes the problem to manifest most obviously, as it consumes the most power, but the same is true for all of the other wireless in the XDA.
We tried another test where we fully charged the XDA, switched on all the radios (GSM, bluetooth and WiFi). We then switched them all off, and left the XDA overnight. By morning, the unit was completely dead.
We then repeated the same experiment, but did a soft reset after switching the radios off. When we came back to the XDA in the morning, the battery was still showing 99%.
If he never turns the WiFi on, then his battery performance is the same as with the current o2 rom.
This seems like a major bug, especially as this seems to indicate that putting the unit into 'flight mode', doesn't actually turn the radios off.
We've also tried reverting back to the 1.06 radio rom, and this doesn't fix the problem.
If anyone else out there can test this, please let us know if you see the same thing.
Bagpuss.