[Defy Android Development] [] AL []:
OK Guys, this is an old thread, but I think it should be deleted or at least people should read this before registering this thread in their mind:

The battery drain 'issues' were almost always due to two things:

1- For the beta 6 version or older of CM7- there was a bug with the auto-brightness which was heavily stressing the cpu and making the system lag badly - hence: the battery drain. To fix this: you have to stay on auto-brigthness. So just make sure that the auto-brightness box is checked and ON. Additional info: some users also complained about the 4 action buttons (menu, home, back and search) not lighting up ---> fix: un-check auto-brightness and re-select it: done!

2- Users did not set their Network baseband properly. Fix: use the Defy Baseband Switcher application and select the newtwork that applies to you. If you don't do this, your phone might have signal reception (phone and sms) but it will use more power to communicate and get a proper lock to your phone service provider.

I don't know what is the exact build # that brought the Defy Baseband Switcher (as far as I can remember, CM7 beta 4.1 had it) but all the 'newest' CM7 will have it anyway.

And if you want to further decrease your battery consumption, you can still do it like this:

- use the bootloader cpu settings: OC'ing and governernor type to change the cpu speed. [From CM7 default 1000MHz to the Defy's stock 800MHz] and change the governor type from "interactice" default to "on demand" [OK: I'm not sure about governor change will improve or not but that is the Froyo's default I believe].

- install SetVsel to underclock --> by lowering cpu Vsel upon the 3 cpu frequencies. Do some reading; you might need to uncheck its "Apply@Boot" option AND also have Milestone Overclock installed for it to work properly.

- USE a recent nightly (post May 29th: there was a possible problem with custom recovery backup restoring prior to that) and you will be able to set your screen display brightness as low as you want [fix the bug described in point 1- above].

- use DroidWall and/or the CM7 built-in applications' permissions control to block some apps' access to internet and networks. BE WARNED though: changing permissions CAN make an application stop working or create problems - don't submit bug reports if you do that.

- Avoid high usage of apps that drain battery quickly (TuneIn radio is power-thirsty one that comes to my mind...) and apps that have to create catalogs and thumbnails (ex: Photoshop, Titanium Backup, Gallery, ...)

- If possible: use 2G network only, disable data synch, auto updates of apps and social networks.

- set your WiFi sleep policy to "Never" [while in Wi-Fi settings, press menu button/ Advanced] and avoid frequent Wi-Fi ON/OFF switching.

- Lower your display brightness and switch that screen off at any chance you got!

There are many other ways I'm sure, but those are the main ones anyway...

I've seen high temps yesterday on my Defy, but I later realized that I forgot to re-set my Baseband after a CM7 nightly install... It 'could' also happen when a (background) service goes "beserk" and overload the cpu: absolutely not necessarily related to CM7 --> faulty apps and bugs happen... Just stop and clear the cache of that app and/or reboot your phone and problem should be gone.

CM7 is now really stable; a VERY FEW little hickups remaining still (like with the camera, but negligeable), but the large amount of new user controls that it brings clearly overcomes the 1 or 2 minor bugs left --> IMO, just having control over each and every applications' permissions justifies forgetting about using Eclair and Froyo. Problems in CM7 are being actively sorted out and new user controls and other useful options are added in almost daily manner through the nightly builds.

I'm categoric: on CM7, I now have more control over where my battery juice goes that I've ever had on Froyo....

So please stop alarming people with high battery usage drainage on CM7 and

give it a try by following the right proper steps

; I'm sure that you won't regret it. ;)