Database Info

Lock / Home screen "fizzes" out. Phone issue or rom issue?

Hey guys, searched for a quite a while and havnt been able to find a similiar problem. Heres what i did
Got the phone 3 days ago and proceeded to root it. It had the perfect SPL so i took the long route and made a goldcard and went to the 2005 SPL.
After phone was flashed i did the "daredevil" way of reverting back to 32b and flashed an appropriate rom to it (cynogens 4.1.8 is on there now)
It seems about %70 of the time when you hit the menu button to get the screen to turn on you can see it flash some lines on the screen like its "charging" the lcd than it just fizzes out, no picture what so ever is visible just weird fuzzy tv looking things than they go away. Trying again usually does the same thing. I have to try probably 5-6 times just to get the screen to turn on and work like normal.
So my question is, is this a PHONE issue, or is this something that could be rom / radio / spl related.
If this is a phone issue i need to take this to unroot and take to the tmobile store asap and get it replaced with another under warranty.

I got the same thing in my G1... send to HTC warranty, they changed the main board. Got it back and it happened again. Then I rooted and installed cyanogen mod, now I never see it again. So I thought it was a hardware issue, but after ROM upgrade I never see it again, so now I really don't know...

The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612

notxel21 said:
The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612
Click to expand...
Click to collapse
ok so this could possibly be both rooted / non rooted boards? Thanks for that link i appreciate it, i'll put my few good words in there. I dont think i can use this phone for business with it doing this.

This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.

Apollo_316 said:
This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.
Click to expand...
Click to collapse
That's what were refering to the screen wake issue. Same problem just called different things. I will try to set my phone at or below 245MHZ for my low and post results!!
Because I've came across both issues depending on the rom. Some give me blur, and some give me the screen wake issue, and some give me both, but I will try you're suggestion.
Thank you for this.

Yeah the JacX hero rom is the only hero rom I have found for the *well at least my* MyTouch3g that *does not* give me the blurry screen issue so that's what I'm running. Then last night I played with my clock settings and went to bed, only to find that my screen was now having this distorted/not waking up issue not like the blur issue of other roms and when I retraced my steps and clocked the processor back down the screen not waking up issue went the way of the dinosaur! I really wish the blurry screen issue could get solved already because I want to try some other hero roms and especially cyanogens experimental rom really bad but I need my phone to work too lol...well I have spare phones so that's not entirely true but I just love my android so much lol!
And you're welcome! I figure that I've learned so much from this forum over the years and had so many helpful and friendly people that it's the least I can do to provide help back!
I'd still love to know if this works for you *I'm confident it will* if you wouldn't mind posting your results as well!

I just updated to 4.1.8 and it hasnt did it in quite some time now. Didnt get the overclock widget yet but im going to wait till it does this again to see if thats the issue. Which more then likely it is.

Not as much of an issue with wake screen on 4.1.9.2 but its still there.
Guess i'll try the overclock widget also.

Yeah the devs (most anyway) are now incorporating built-in cpu clocking settings in the user.conf file for their roms and this allows the rom to do dynamic cpu clocking from the stock rom, which also allows them to push the speeds of the phones the roms are installed on without additional software. The downside to this is when the clock starts above what it's default is, or at least above 245mhz the screen has a tendacy to not wake up properly. If the clock is started at 245mhz and then gradually moved up to 528mhz based on demand on the cpu then the problem goes away. The cpu widget is free and works great to allow you to control the cpu clocks, not the rom. There's another one I'd recommend called SetCPU on the market but it costs like $2 or $3 which also works nicely but doesn't really add anything over the free widget available other than some profile options for low battery and such.
*I'm still learning alot every day about all this android modding stuff so if I've stated anything incorrectly please PM me or let me know here and I'll edit my posts acordingly*
~*Apollo*~

still no dice
im running 4.1.10.1 and it is still not waking up properly. Even with the overclock widget installed and working. Im not sure what else to do. Im updating to 4.1.11.1 right now but i have a feeling this isnt going to fix anything.

I haven't seen this.
This issue has been addressed more thoroughly in the Dream section. Follow up with stories and details there. Otherwise, I haven't seen this problem in any of the most recent ROM ports.
Everyone's device is different regardless of matching statistics. Lol.
Best of luck to you fellas.

Battery Problem [CM7]

Hi everybody!
So I am using CyanogenMod 7 Beta5.1 And I'm having huge battery problems...
It's draining abnormally fast (30% lost during night).
It started to happen when I got problems with my Defy and flashed 3.4.3-11
And now updated to 3.4.2-117.
Before these problems it usually drains only 3% during night!!
Also everytime I boot my phone, when it's completely booted I hear the camera sound (when you open camera app,it makes a physical sound).. It never happened before...
I overclocked my phone to 1100Mhz but I don't think it really affects the battery (when screen off it's set to 500Mhz)
Please help me!....

I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App

schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
fast boot? The one from setvsel?

schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
how can u shutdown fastboot? wanna give this a try...

schultzy001 wrote
"Sent from my Desire HD"

um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.

Hi guys,
I'm having this issue too, and i note since a few days ago. I don't know why, but my Defy is sucking his battery too fast. Could it be a bug ?

it's a little bit difficult to follow the bugs and the solutions in a huge thread like the other one. so i think that this that could be a mayor problem for all of us should be treated in a differente thread.
I use Motocharge since 1 day to follow how it discharge during the day.
I say it in the other thread, the phone loose a lot of battery when i don't touch it. sometimes it loose like 5% in 15mins and i don't touch it. maybe it doesnt sleep well, i don't know..
I hope that Quarx can solve this, because in the other betas of him i don't have the problem. only in the 5.1.

battery draining
I think It´s a bug, because I used before BETA 5.0 and without any battery life was almost 3 days in normal use, bur now with BETA 5.1 only two days or less.
By the way I´d proved with 3 or 4 diferent roms, but the same result.
But I´m sure Quarx will deleted this bug in the next version

same problem for me,but b3 and b4 is ok
Sent from my MB525

apart from low battery life.....i noticed substantial increase in battery temp..normally its 32-34 deg cel.....but wid CM7 it raises to 42-45 deg cel.....waiting for a solution so that i can come back to CM7...

I use Toggle 2G/3G to switch to 2G when phone goes to sleep. I set wifi to never sleep and use it as much as possible over 3G. I also set brightness levels long time on 16 so that in the shadow I always use just a little energy. This way I almost get double battery live.
+ it's better for battery to charge every night, empty or not, and let it go lower just occasionally.
Link to Toggle app:
http://forum.xda-developers.com/showthread.php?t=739530

yes, this issue is really annoying, 30% battery drain overnight.
something is definitely running unreasonably... hope find it.

I think it depends upon what "type" of defy u have. My battery that only used to last for 12-14 hours in eclair now went for 2 days last 2 charges.
Also depends upon how many widgets and apps u running... hard with mobile phones to judge battery as so many independent variables.
Sent from my MB525 using XDA App

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 "[email protected]" 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.

marhensa said:
um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.
Click to expand...
Click to collapse
Display instead of cell standby showing up first in battery consumption means that Froyo (or CM7) uses less battery. The display just stayed the same of course, unless it's tuned brighter, the percentage increased because it's a relative measurement.

Why is my battery life so bad?

ROM: CM9 latest nightly
Kernel: CM9's own
Radio: T-Mobile's UVLC8 (yes, I'm on T-Mobile)
Brightness: Auto (shown in screenshot)
Synced Gmail accounts: 3
Accounts in Email app: 0
My battery drops 20% in 42 minutes, which means it will be depleted in 3.5 hours. And this is mostly due to the screen. Why? I use the phone moderately and ALWAYS press the Power button to turn the screen off whenever I'm done replying to a text or doing anything with it.
Any suggestions?

Well judging from your notification bar you have bluetooth, WiFi, fb sync all on and you aren't even connected to a WiFi network or Bluetooth device. Try turning those off when they are not needed. Also go into the Facebook app and go to settings and change you sync time to a little longer than an hour (if you can stand it). Try that for now and see what happens
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Some info on screen on time would help, 3.5hrs screen on time is barely below average. I would expect that if FB is always syncing and blue tooth.
Also I would verify you don't have a wake lock going from charging. You can check with CPU Spy, better battery stats, as well as some others. Cpu spy is likely the easiest way.
Sent from my SGH-I727 using Tapatalk 2

Every once in a while I'll get a flash that does this, the battery just seems to be losing its will to live. I don't understand it myself but I restore my last nandroid backup, and then flash again. After that all goes back to normal.

ckck543 said:
Well judging from your notification bar you have bluetooth, WiFi, fb sync all on and you aren't even connected to a WiFi network or Bluetooth device. Try turning those off when they are not needed. Also go into the Facebook app and go to settings and change you sync time to a little longer than an hour (if you can stand it). Try that for now and see what happens
Click to expand...
Click to collapse
I always keep WiFi and Bluetooth on. I thought neither one of those really used a lot of power unless actually connected. I use BT only in my car and WiFi only at home (evenings). My FB refresh interval is set to 1h. I hardly think this is draining my battery.
lnfound said:
Some info on screen on time would help, 3.5hrs screen on time is barely below average. I would expect that if FB is always syncing and blue tooth.
Also I would verify you don't have a wake lock going from charging. You can check with CPU Spy, better battery stats, as well as some others. Cpu spy is likely the easiest way.
Click to expand...
Click to collapse
Better Battery Stats wasn't free, so I installed CPU Spy and Battery Spy, I am letting the phone charge to 100% and then, I'm going to unplug it and report after about 30 minutes.
meet2x4 said:
Every once in a while I'll get a flash that does this, the battery just seems to be losing its will to live. I don't understand it myself but I restore my last nandroid backup, and then flash again. After that all goes back to normal.
Click to expand...
Click to collapse
I will flash last night's CM9 nightly and see if I notice a difference.
Thank you all!

Razor1973 said:
I always keep WiFi and Bluetooth on. I thought neither one of those really used a lot of power unless actually connected. I use BT only in my car and WiFi only at home (evenings). My FB refresh interval is set to 1h. I hardly think this is draining my battery.
Click to expand...
Click to collapse
Might want to think of picking up some NFC tags and setting profiles so stuff like Bluetooth will automatically turn on when in your car, and off when you leave. And BT and Wifi do drain power when not connected because they are searching for connections.
Better Battery Stats wasn't free, so I installed CPU Spy and Battery Spy, I am letting the phone charge to 100% and then, I'm going to unplug it and report after about 30 minutes.
Click to expand...
Click to collapse
It's free to XDA members: http://forum.xda-developers.com/showthread.php?t=1179809

dakpluto said:
Might want to think of picking up some NFC tags and setting profiles so stuff like Bluetooth will automatically turn on when in your car, and off when you leave. And BT and Wifi do drain power when not connected because they are searching for connections.
It's free to XDA members: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
But wouldn't WiFi and Bluetooth show in the battery usage screen with a high percentage? They would show by themselves or under radio and those aren't high at all. It's all on the screen. That's the problem, it seems. And what I explained earlier is that I don't use it much. I will get a text message, I'll reply and automatically turn the screen off before I set the phone down. I never forget this. I'm actually anal about it. LOL
I just installed Better Battery Stats (thanks for the tip!!!) and will test with all 3 apps as soon as I unplug my phone to go to lunch. I haven't been able to do this yet. Crazy day here at work.
Thanks again.

Razor1973 said:
But wouldn't WiFi and Bluetooth show in the battery usage screen with a high percentage? They would show by themselves or under radio and those aren't high at all. It's all on the screen. That's the problem, it seems. And what I explained earlier is that I don't use it much. I will get a text message, I'll reply and automatically turn the screen off before I set the phone down. I never forget this. I'm actually anal about it. LOL
I just installed Better Battery Stats (thanks for the tip!!!) and will test with all 3 apps as soon as I unplug my phone to go to lunch. I haven't been able to do this yet. Crazy day here at work.
Thanks again.
Click to expand...
Click to collapse
that's covered under android system I believe. Most important, it causes wake locks that keeps your phone from deep sleeping.

Flash Instigators Kernel with Smartass/Badass scripts (not a joke....)
It will help you tremendously. You must reflash with every nightly update you do.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

OK, so 4.5 hours and battery discharged 38%. I guess that's not terrible, but my screen was only on for 26 minutes of that time and the phone is reporting 55% of the battery drain came from screen use. I feel battery life could be a lot better just because of this.
What else do these screenshots tell you guys?
I noticed KIK Messenger and MailDroid there. They both sync a lot. I do have a couple of IMAP accounts on MailDroid that I forgot to mention in my OP. But, still, I go back to the fact that most of the drain comes from the screen. These aren't related.

onealvideo said:
Flash Instigators Kernel with Smartass/Badass scripts (not a joke....)
It will help you tremendously. You must reflash with every nightly update you do.
Click to expand...
Click to collapse
Oh, true!!! I flashed InstigatorX's kernel when I first started flashing the nightlies, but, since I flash them every 2-3 days, I completely forgot to reflash the kernel. OK, it's more like I didn't know it was getting overwritten and I had to reflash it. Thanks for the reminder!!! By the way, do you go with stable (4.0b) or the latest experimental (5.3.2)? Also, do you just flash the kernel? What are those scripts and what do you do with them? I did not understand his instructions. Maybe I should be asking there, but since I already have you here... LOL

Razor1973 said:
OK, so 4.5 hours and battery discharged 38%. I guess that's not terrible, but my screen was only on for 26 minutes of that time and the phone is reporting 55% of the battery drain came from screen use. I feel battery life could be a lot better just because of this.
What else do these screenshots tell you guys?
I noticed KIK Messenger and MailDroid there. They both sync a lot. I do have a couple of IMAP accounts on MailDroid that I forgot to mention in my OP. But, still, I go back to the fact that most of the drain comes from the screen. These aren't related.
Click to expand...
Click to collapse
For one, turn your screen brightness down. I use auto-brightness and never have a problem seeing it, and my battery drain is ok that way.
Two, you've got the AudioOut_1 wakelock. Turn off system sounds in the settings menu (keytones, touch sound, screen lock sound, vibrate on screen tap) and that will take care of that.
Any type of instant messenger service (Skype is well-known for doing this) will wakelock your phone while it searches for IMs. No way around it other than an uninstall. You can't control IMAP pushing, but you can control folder polling, which eats up a lot of battery. I'd set your MailDroid accounts to not poll folders automatically more than once a day.
And definitely turn Bluetooth off when you're not actively connected to something. You might as well be using your phone as a flashlight with how much power BT burns through.

I am currently on RC2. I went to the 21/22 nightly but was not liking how it was behaving so I went with the RC for now.
In INSTIGATORS forum you will see in the links to the kernel one that says <-------- works with RC2.
I used that one and I am happy. Sure you could do the newer ones but I am happy where I am at currently.
Just boot into recovery and install from zip.
(Assume u download the zip on your phone....)
Its easy as pie!
You can play with the settings if you want but the default settings work pretty freaking good!
I would for sure recommend going to that forum as Instigator himself can answer ALL your questions in depth.... I am merely a messenger and user of his kernel.... wish they would just merge it into the cm9....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

T.J. Bender said:
For one, turn your screen brightness down. I use auto-brightness and never have a problem seeing it, and my battery drain is ok that way.
Two, you've got the AudioOut_1 wakelock. Turn off system sounds in the settings menu (keytones, touch sound, screen lock sound, vibrate on screen tap) and that will take care of that.
Any type of instant messenger service (Skype is well-known for doing this) will wakelock your phone while it searches for IMs. No way around it other than an uninstall. You can't control IMAP pushing, but you can control folder polling, which eats up a lot of battery. I'd set your MailDroid accounts to not poll folders automatically more than once a day.
And definitely turn Bluetooth off when you're not actively connected to something. You might as well be using your phone as a flashlight with how much power BT burns through.
Click to expand...
Click to collapse
Screen brightness: I use auto as well. It's in one of my first screenshots in this thread.
AudioOut_1 wakelock: Done. Thanks. I'm going to miss the touch and screen lock sounds. LOL I left dial pad touch tones and volume rocker music controls in that same secton checked, by the way.
MailDroid: I went through all the settings, both general and for the e-mail accounts and couldn't find a place to specify folder polling interval. Do you have it installed? If so, could you tell me exactly where to find this please?
Bluetooth: I'll try my best to turn it on only when I needed. I could also follow dakpluto's suggestion with the NFC tags. But then, I'd have to leave NFC on. Doesn't that drain battery too?
And you see, although all of these will help, don't you agree based on my screenshots that the biggest offender here is the screen and this is the area I should really be looking at?
onealvideo said:
I am currently on RC2. I went to the 21/22 nightly but was not liking how it was behaving so I went with the RC for now.
In INSTIGATORS forum you will see in the links to the kernel one that says <-------- works with RC2.
I used that one and I am happy. Sure you could do the newer ones but I am happy where I am at currently.
Just boot into recovery and install from zip.
(Assume u download the zip on your phone....)
Its easy as pie!
You can play with the settings if you want but the default settings work pretty freaking good!
I would for sure recommend going to that forum as Instigator himself can answer ALL your questions in depth.... I am merely a messenger and user of his kernel.... wish they would just merge it into the cm9....
Click to expand...
Click to collapse
Here's what I just did:
1) Installed latest (7/23) CM9 nightly.
2) Installed InstigatorX's 5.3.2 experimental kernel using CWM.
3) Installed InstigatorX's BadAss script using CWM on top of the kernel (I guess that's how you do it).
I will see how my battery behaves. It'll be difficult to know which of the many things I did is the one that yielded the biggest improvement, however. Oh well.
Thank you all!

I'm testing aokp w/ stock kernel ondemand 192/1512 and it actually is working decently for me so far. Streamed like 1 1/2 hr of video last night and 2hr of Pandora today at the gym. :good:
Sent from my SGH-I727 using Tapatalk 2

You see? Why can't I get HALF of that?

InstigatorX CM9/AOKP Kernel - Which One?
Razor1973 said:
... do you go with stable (4.0b) or the latest experimental (5.3.2)? Also, do you just flash the kernel? What are those scripts and what do you do with them? I did not understand his instructions. Maybe I should be asking there, but since I already have you here... LOL
Click to expand...
Click to collapse
That's what I'm trying to figure out:
Which version (e.g. 4.0b or latest)?
Which script(s)?
Anything else?
(There's tons of information in these forums, but finding it buried deep in threads is like looking for a needle in a haystack.)

From the looks of that screen shot. The phone is barely being used, see how the blue isn't solid for most of the running time?
Sent from my SAMSUNG-SGH-I727

kr3w1337 said:
From the looks of that screen shot. The phone is barely being used, see how the blue isn't solid for most of the running time?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Yep I have power saving stuff such as turn off wifi when idle, I dont have GPS on 24/7 and I dont have wakelocks, I also set mine to use 3G/4G rather than LTE. If it was a solid blue that means something will be constantly on draining the battery.
I'm testing aokp w/ stock kernel ondemand 192/1512 and it actually is working decently for me so far. Streamed like 1 1/2 hr of video last night and 2hr of Pandora today at the gym.
Click to expand...
Click to collapse
Those are the two lines from the front and the end. The blanks are deep sleep over night. Remember I said "testing aokp" "stock kernel"
If you want my "light" use then here it is lol.

Trinition said:
That's what I'm trying to figure out:
Which version (e.g. 4.0b or latest)?
Which script(s)?
Anything else?
(There's tons of information in these forums, but finding it buried deep in threads is like looking for a needle in a haystack.)
Click to expand...
Click to collapse
For performance I prefer smartassv2 for power saving I would go for badass governor. With badass it doesn't jump clocks to max but goes by phases thus not aggressive and doesn't eat a lot. Test them out read the change log to see if changes pertain to you :good:
Sent from my SGH-I727 using Tapatalk 2

Ways to save battery

I've used the N5 for a few days now and I must say I'm impressed with everything except for the battery.
So the thing is, i really gave no craps about the battery on my Defy because I didn't care much for the phone either; so I'm sort of confused and out of ideas for battery saving.
I haven't rooted yet, but when I do my best guess would be just to down-clock the CPU, but how well does that really work? I use No-Frills and it works about 93% of the time, other times it just reverts. Do I need a kernel?
I keep it on about 10% brightness because I like soft lighting and screens. That works to a certain extent as well as the fact that I'm not a data user and I always turn wifi off when I'm not using it (like, immediately I will go and toggle it).
Other than turning off sync, is there anything else I'm missing? A good app maybe?

droid_<3er said:
I've used the N5 for a few days now and I must say I'm impressed with everything except for the battery.
So the thing is, i really gave no craps about the battery on my Defy because I didn't care much for the phone either; so I'm sort of confused and out of ideas for battery saving.
I haven't rooted yet, but when I do my best guess would be just to down-clock the CPU, but how well does that really work? I use No-Frills and it works about 93% of the time, other times it just reverts. Do I need a kernel?
I keep it on about 10% brightness because I like soft lighting and screens. That works to a certain extent as well as the fact that I'm not a data user and I always turn wifi off when I'm not using it (like, immediately I will go and toggle it).
Other than turning off sync, is there anything else I'm missing? A good app maybe?
Click to expand...
Click to collapse
Few things i've done is turn off wifi always scanning. set location to device only. undervolt -75 and max cpu 1575. i'm using cataclysm rom and frank r16 which was just recently released. when i was on r14 kernel i was getting about 7hour 1% drain on idle connected to wifi. I also try to monitor what I want to have push notifications for. So check what you have constantly Syncing.

cntrdctn said:
Few things i've done is turn off wifi always scanning. set location to device only. undervolt -75 and max cpu 1575. i'm using cataclysm rom and frank r16 which was just recently released. when i was on r14 kernel i was getting about 7hour 1% drain on idle connected to wifi. i also turn make sure i monitor what want to have push notifications. i hope this helps.
Click to expand...
Click to collapse
Biggest changes for me were:
-Disable Hotword detection. Turn it back on when you want to impress friends and otherwise hit the mic button manually. Increases Screen on Time.
-Disable Auto sync. Set an automation to only sync while charging instead. Increases Battery at all times, may slow charging a tad.
-Disable Locations. Enable if needed on the go. Can't automate this with Llama but I'm guessing it would work using Tasker. Many less wake locks you can go hours without a single one now.

[CM11M11, CM11nightly] Screen doesn't wake up. Buttons do.

From time to time, usually in the evening/night (?), I try to wake my screen up by either double-tapping it or by hitting the power button.
I can see the buttons back light going on, but the screen doesn't.
I have tried also to hit the power button and wait a little bit (about 5 seconds) with no luck.
I have also noticed that it takes something between 200ms and 600 ms for the screen to wake up, while for example on LG G2 d802 it took about 100ms (or even less).
My only option so far is to keep the power button pressed until I feel the rebooting vibration.

Uqbar said:
From time to time, usually in the evening/night (?), I try to wake my screen up by either double-tapping it or by hitting the power button.
I can see the buttons back light going on, but the screen doesn't.
I have tried also to hit the power button and wait a little bit (about 5 seconds) with no luck.
I have also noticed that it takes something between 200ms and 400 ms for the screen to wake up, while for example on LG G2 d802 it took about 100ms (or even less).
My only option so far is to keep the power button pressed until I feel the rebooting vibration.
Click to expand...
Click to collapse
Undervolting?
Any special settings?
Custom kernel?
Sent from my A0001 using XDA Free mobile app

DerRomtester said:
Undervolting?
Any special settings?
Custom kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
As far as "special setting" ... I don't knwo which is special and which is not.
Which setting are you talking about?
I am running the kernel that comes with the ROM itself, balanced profile, CPU "ondemand" scheduler, no overclocking, I/O "deadline" scheduler, 16bit transparencies ...
Home screen is just 1 screen handled by Apex Launcher with (again) no wallpaper.
In Settings-->Display I have enabled: touble tap wake, avoid accidetal wakes, automatic brightness with mean sensitivity.
The only "special" application I have is "Xposed framework" (Installer v2.6.1 STABLE) with one single module ("EnableCMCallRecording").
Everything else is just applications from the market.

Uqbar said:
As far as "special setting" ... I don't knwo which is special and which is not.
Which setting are you talking about?
I am running the kernel that comes with the ROM itself, balanced profile, CPU "ondemand" scheduler, no overclocking, I/O "deadline" scheduler, 16bit transparencies ...
Home screen is just 1 screen handled by Apex Launcher with (again) no wallpaper.
In Settings-->Display I have enabled: touble tap wake, avoid accidetal wakes, automatic brightness with mean sensitivity.
The only "special" application I have is "Xposed framework" (Installer v2.6.1 STABLE) with one single module ("EnableCMCallRecording").
Everything else is just applications from the market.
Click to expand...
Click to collapse
Ondemand is called unstable by some people. Could you try interactive and report back ?
I dont know if xposed is a problem but i think not.
I suggest wipe system and reinstall your rom.
And do not make any modifications in kernel settings or developments settings.
I hope this works for you.

DerRomtester said:
Ondemand is called unstable by some people. Could you try interactive and report back ?
Click to expand...
Click to collapse
I will try this. But never had issues with LG d802 w/ CM11M10 and CM11M11 there.
DerRomtester said:
I dont know if xposed is a problem but i think not.
Click to expand...
Click to collapse
I hope so. I do need the call recorder.
DerRomtester said:
I suggest wipe system and reinstall your rom.
Click to expand...
Click to collapse
That's the way I install ROMs: I never do "upgrades".
DerRomtester said:
And do not make any modifications in kernel settings or developments settings.
Click to expand...
Click to collapse
Do you think this is a device related issue or a more general one for M11/Nughtlies?
I am quite puzzled by this hint. The issue is not happening everytime the screen goes off. It happens at random, usually after long (>10 min) periods with the screen off, and never in the morning (after 6 to 7 hours of sleeping screen). Nonetheless I'll try it...
[UPDATE] As of 8:00pm my phone started with a slooow screen wakeup (~ 1000 ms).