PDA

View Full Version : Very short batterie lifetime on XDAII O2 Germany


bernhard74
13th September 2004, 12:57 PM
Hi,

anybody else here, who has problems with very short batterie lifetime on XDAII in O2-network especially in the south of Germany? I homebrewed a new ROM with radio 1.17 and 1.72.01 software and installed old homezone-application from 1.60 rom, but it didn't fix the batterie lifetime bug.
I called O2 service Germany and they said to me, it's a software issue and they're waiting for an update, but of course he couldn't give me a release date for the update :evil: :evil: !!!
I personal belive, it's an O2 Network problem, because it appeared two months ago. Before this I had no problems with batterie lifetime. It's definitly no rechargeable batterie issue, cause it happens with a new rech. batterie, too.
As a next step I will cook a rom without homezone application and hope the batteries will survive one night, please!
Has anybody here experiances with this problem?

Greetings

Bernhard

bernhard74
15th September 2004, 08:47 PM
I found a possible workaround for this problem. In my mind the homezone application OHZ.dll is the problem for the high batterie consumption.
So it's a good idea not to install the 30032install.arm.cab from the extended rom or to rename the ohz.dll in the windows directory. The application ohz.exe can be found on \windows\v2r\ohz

bernhard74
20th September 2004, 10:30 AM
As an alternative for the homezone application you can activate the homezone announcement. You can order it under 1414 "Tarfimanager" and choose the option "Tonansage".

cruisin-thru
20th September 2004, 09:26 PM
Quote: I personal belive, it's an O2 Network problem, because it appeared two months ago. Before this I had no problems with batterie lifetime.


Can you enlighten me as to how the network can affect battery life.? :?:

Xant
21st September 2004, 11:55 AM
The Homezone application, an expically broadcast cannel 221 prevents XDA2 going in to sleep, so the machine runs through, only with display off.

This is a bug/change of protocol of the german o2 network for 2 months now.