Hi, I just got a TMO Wing. Thanks for many threads here, I downloaded Statusbattery and overclocked my wing to 247. It works great. I have a question regard the accuracy of batterystatus. I underclocked to 156Mhz just to save battery yesterday so it can last a bit longer until I can recharge it at home. However, I found that the current drain shown in batter status is 177mA. I changed it back to 201 MHz, it show 112 mA, but if I overclocked it to 247mA, it showed 64mA. What just happened? Is something wrong with my phone? I thought that the lower the clock goes, the less current it drains. And all the cases were when Wifi and bluetooth disable. Only the phone option is on. No other background app is running.
Best regards
it's called batterystatus, first of all
anyway. Its possible that the amperage meter refreshes at a different rate than the clock speed. Or it could just be that it's wrong.
Its also possible that the processor is being actively used, even if nothing else is running.
It also could be that a slower clocked processor needs more power to get things done than a faster one because it takes a longer. The faster clockspeed finishes quickly, so it can idle at 64mA.
Your guess is as good as mine. Try setting it low, then waiting a while
748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority
Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse
Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.
@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.
What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.
Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90
I've been running CM11 (feb 14 build) now for about 2 weeks with terrible battery drain during use. The phone gets really hot when i'm just browsing facebook or reading a news app.
I looked at the CPU usage and it seems it's either at max cpu, min cpu or deep sleep. That is strange first of all, it never or rarely uses the frequenceis in between. Then i took a look at the battery graph. When the phone is sleeping, the battery is holding really steady, but as soon as I start using it all hell breaks loose and the graph looks like an olympic downhill slope. The strange thing is that the main battery source is the screen which is odd beause on stock (With better battery life compared to this) Android System was the main battery killer.
I then took a look at BetteryBatteryStats. First thing i noticed: 50-50 deepsleep and awake which is pretty astounding.
The wakelocks are msm_hsic_host and PowerManagerService.Wakelocks. But this is strange because it's still pretty much a clean install.
So my theory is that the CPU governor is not functioning propperly and blasts to max cpu as soon as a wakelock is requested and when the phone is in use it also blasts max cpu. I don't know.. that's just what I think is happening with the data i have.
Any ideas?
Updated section:
After clearing cache through recovery and doing a hard reset, the uAh has gone back to 3142000. Standby time seems good with the battery losing 7% overnight. It does charge quite quickly from 0-100 in about 2h. The previous heating issue remains with cpu monitors showing that the cpu jumps to high clock when I touch the screen. I don't see any change in which apps use the most battery with the screen taking up the most as before the problem started.
The heat appears to be what is draining the battery but I can't find any single app that causes it to ramp to max.
Pictures:
No-frills is set to stock settings to see how the phone handles the actions
2nd picture is when phone is idle
3rd picture is immediately after swiping through a few tabs and scrolling through some pages in the app which causes cpu clock and load to increase
Old sectionFor when battery uAh was low)
I've had this Z1 for about 11 months. I can only get around 2.5h on screen time with regular usage. The battery uAh was only 1848000 Recently it fell to the 1700s. Calibration appears to reduce the value further. The phone seems to heat up in about a minute or two no matter what app is running.
The phone is rooted on stock 4.4.2
I have tried updating to Lollipop before but received an error due to rooting, so I don't think anything changed.
bump
alantay11 said:
bump
Click to expand...
Click to collapse
sounds like it's time for you to replace your battery.
You may try to disable the "input boost frequency"
By default when you toch the screen, cpu frequency of two cores instantly jumps to around 1400 to preventing any lag but it seems to use more power and causing heat
I have disables this and since then I'm no longer have any heat issue and also the battery life is so much better now but you may exprience a little lag while scrolling on heavy web pages but thats all
Btw i'm on .157 and using Kernel Adiutor for cpu tweaks
You may disable this by the app mentioned above or by editing sys.somc.touch_perf_kick=1 from 1 to 0 in buid.prop or adding this line
A month ago or so, i had this random period of time where perfZ started to show "-" for temperature ( i assume its gpu temperature because it doesnt match with battery or cpu temp from another app) and my phone was heating up much more in games but so was the performance was way better.
Normally after thermal throttling kicks in and device reaches heat equilibrium, my battery would sit around 38-39C, cpu at 42-43C. But in that time period where it showed "-", my equilibrium was battery sitting at 44C, cpu at 47-48C. Phone was considerably hotter to touch but you could still game on it. And performance was way better, it would fall to 50fps min instead of 40fps, which is very noticable. (Dont have exact numbers maybe a bit better)
Idk how this happened as it randomly happened one day but does anyone know how to make this work? My device isnt rooted. (s10+ exy)
(Small note: Using game plugins at max performance or custom doesnt help, maybe they arent optimised for dead by daylight, because thats the only game i play)