Related
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.
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.
Been experiencing a high battery drain past few days on both VirusROM and BAMF 1.6.3. According to CurrentWidget it keeps at 260-270mA most of the time with screen off. On it jumps up to 400-500mA pretty much right away.
The strage thing is that I haven't really changed anything and have seen 40-60mA draw while idle before.
Partial wake usage mainly lists Android System, everything else has really short duration times.
Any idea how I could track down what's using so much power during idle? Have very few apps installed and all that are installed are pretty standard I think.
Here's a list of what I have:
Where's my droid
Appstore (amazon)
ShootMe
Solo Lite
Facebook
Fandango
Go Launcher EX (maybe this? was updated recently)
Calendar (widget for EX) as well as two themes for EX
Google Maps
Gmail
GO SMS Pro and a theme
Foursquare
Screen Off and Lock widget
ROM Manager
CurrentWidget
SoundHound
Ginger keyboard
Shush!
ColorNote
gTabSiMiClock
Ringer Volume
Retro Cam+
SMS Backup
As far as general settings, Wifi and GPS are always on as well as syncfor gmail and FB, but then again they were since day one and I've seen idle draw at 40-60mA always before.
Thanks for the help.
Have you changed your wallpaper recently?
Mine used to be orange with flames, and it used to do the same thing. Since then, I changed it to a space themed wallpaper that's mostly black and dark blue . My current power usage has gone down significantly to idling at 30 unless I use it!! Try that!!
You could also recalibrate your battery if you haven't done that since ROMing, I did that at the same time too, but I don't think that did it.
Darker wallpaper hmm. Well I changed it to something darker though it doesn't make sense that it would drain battery differently while screen is off, but I guess it doesn't have to make sense heh.
I did use all kinds of wallpapers before even live ones and never really seen such high idle use before. Will try to drain battery and recharge as I haven't done that in a while.
Going to try and wipe everything and just install bamf 1.6.3 along with currentWidget and see what happens I guess. And if issue is fixed will slowly add apps one at a time to try and find which one causes the problem. It also possible that TitaniumBackUp is causing the issue as lately I was using it to reinstall all apps instead of going to the market and doing it that way.
make sure you re calibrate your battery after ROMing, if you haven't done that already. That fixed all my idling power consumption (and charging) problems
Try applying airplane mode. That will help you see if your radios are eating battery.
Reinstalled the rom and while I didn't want to install any apps market restored everything I had, but I did not use TitaniumBackup this time and so far everything is fine. Idle is back down to 40s mA.
I guess was some glitch in the backups. Because everything else is the same.
Hello,
I've been flashing a bunch of AOSP roms and with all of them, i tend to get terrible battery life while idling. I've narrowed it down to my phone not sleeping while the screen is off. In the battery chart menu awake seems to be almost the same as the battery up time and the bar graph is almost a full solid blue. while i was searching i came across a post in cm forums blaming this on something to do with the gps and that disabling it and rebooting would fix it but this does not seem to work for me. Does anyone else have this and has anyone found a way to fix it?
I've also discovered a post whereby someone was running advanced task killer on an sgs2 to fix the same issue i'm having but i would rather not rely on a task killer if i don't need to. Any info, ideas, help, links etc are greatly appreciated!!
Your friendly neighbourhood Spiderman.
So, to narrow things down, I started off fresh
- Flashed stock 1.11 hboot from Telus RUU
- relocked then RUU
- unlocked, flashed TWRP 2.4.4
- Wiped SD, Cache, Dalvik, System, Factory Reset
- Flashed PA 2.54/Gapps (my fave ROM)
- Installed few apps. Friendcaster, Tunein Radio and Swiftkey
- Left it at 60% over night not charging
Low and behold, Awake time and screen on time were almost on par. However, I used it on the bus to listen to some tune in radio, browse the web etc and it seems as though one of the apps or maybe multiple are keeping the phone awake more than it has to be and it started draining again. not as bad as before, mind you. Most likely due to there being less apps. So at this point if I want to continue using AOSP ROMS it seems as though I will need to set up a task killer so nothing keeps my phone awake.
Tonight I will set it up and see what happens with my awake/screen on bars. I am fairly certain they will sync up afterwards. I tried to avoid a Task Killer but it seems as though I cannot! I will post my findings after for anyone else in this same boat though it seems very few are!
Get a program like better battery stats or Gsam battery monitor to tell you what your wake locks are
Sent from my VENOMized HoxL
the title says it all, but not to leave them with later doubts, I tell you: I have installed Cyanogenmod with Android 5.1, which of course I'm going for luxury. The detail is that I currently use Kernel Adiutor for CPU / GPU settings and the extras it has. the detail is that I do adjustment after adjustment and then ... it comes to work, unfortunately I have problems with other applications and I must be making adjustments every so often. I have some settings (at the moment) so I can use it for PUBG (which gives in some cases flaws in sound and after some time the application fails completely forcing the phone lock (S3 Neo)). I must resort to the application to give a half solution that finally does that, solve the problem halfway .. Because of the "half solution" I've been doubting if the application itself runs the changes above (a placebo effect), this is because the device once in even with the minimum CPU / GPU settings the phone starts to behave slowly (as is normal) but also consumes a large amount of battery, in the afternoon watching streaming (through medium settings in the application) the battery It drops quickly, from 52% to 9% in an average time of 10 minutes, I was finding out if I changed the application for an at least more durable alternative to Kernel Adiutor (like SetCPU or similar) but I doubt that they are compatible with the version of Android that I own or, if it will also apply placebo effect, as I am beginning to notice.
And if in case of mentioning the battery, it is better not to say anything about it since it is not battery failure. It's the same one that I've always owned, plus, unlike this one, it worked better via Stock for obvious reasons.