Hi!
I was dash charging my phone when I noticed it was a bit hot to touch. I went to browse Facebook for a while and it was SO laggy that it was barely usable... I went to check the max clock speed in kernel adiutor and it was just 1440mHz!
I attempted to change the governor and it started freaking out, the max clock speed is constantly going up and down, it rises to 2000mHz then sinks back to 1440mHz and it keeps doing this over and over again.
I tried a restart but it's still doing it...
I'm running the OOS4.0 beta
What the hell is this thing doing?
Related
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
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
I honestly don't think anyone has been messing with the CPU until the CM ROM is released.
hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
As far as I've seen, the Revo's CPU does automatically speed scale to the necessary load.
If you're running lots of apps in the background, with the screen on Android will keep the cpu at full throttle to provide a smooth experience for you.
As soon as you turn off the screen, it will throttle it down as much as it can.
If the phone's rebooting on you, that's because whatever cpu tuner is doing may be keeping the cpu speed too low for the demand of the OS, then the watchdog kicks in when it thinks the cpu is stuck in a loop. (watchdog wants to be petted every 30 seconds, if the cpu misses that, the watchdog reboots the phone)
I use setcpu and have no reboot issues.
Sent from my VS910 4G using XDA App
throttle
I use android system info to show the CPU speed. It shows the % of time my revolution is running at each speed. W/o using a 3rd party app it always shows 100% at 1Ghz. W CPU tuner running it shows 50% at 122Mhz, 25% at 1Ghz, and 25% in between.
I don't think I'm running any apps thats sucking up a lot of CPU. I'm rooted w most of bloat removed.
Am I the only one not seeing any CPU throttle on stock?
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Exactly Im much happier with my phone now. I had the same issue when I received a call but set up the profile as u did and have no problems at all
newkick said:
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
I am using setCPU as well with no issues. I have mine set were the screen is off it goes to 124 and clocks back up to full 1GHz when it is on. Helps greatly improve my battery.
So what settings do you use? I get really bad lag when waking my Revo. Sometimes it will reboot after waking too.
Sent from my VS910 4G using XDA App
I don't know if this is a CPU throttling issue, or a general REVO issue, but I get horrible horrible lag sometimes trying to get any programs to respond. Like press the home key, or click send, or anything like that. I'm running Decrap 1.1, I don't know if I have too many processes running or what.
Interesting. The Thunderbolt has the same issue. Is it the same CPU in that phone?
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?
So I've been hearing that people are experiencing unexpected shutdowns to their ROG Phone 2. It happens to me when I'm gaming or doing something intensive like benchmarking. Weird thing is that I have the Tencent edition (8GB, 128GB), and it worked absolutely fine for the first year on Android 9 and 10. However around this start of this year, it unexpectedly shuts down on its own after gaming for the first 5 minutes. I thought it was some weird glitch/bug but it occurred frequently, so I reverted back to Android 9, or even threw a custom firmware, and it still shuts down on its own.
Turns out that Armory Crate says that the system temps are at a cool 34°C, GPU at 50°C, but the CPU is at a whopping 70°C!! Whenever it hits 70 or close, it just shuts the phone down entirely, and the device itself doesn't even feel like it's burning in my hands at all!
Could it be the hardware is being faulty? Or the thermals are incredibly bad? I don't even have the cooling fan, tho I ain't sure if that'll make a difference. Note that it was just working fine for the first year. I'm not entirely sure what's up, but generally it would thermal throttle and lower the clock speeds (I'm not even using X-mode!), but I just get a full shutdown. Does anybody else experience a similar problem or unexpected shutdowns in general?
(It is not always running at 2.96 GHz! It just happens to spike up to that when I took a screenshot haha)
Some people claim that the thermal paste might be old and the cooling is getting worse. I noticed it myself on my ROG 2. Play a lot of pubg, when the phone reached 43 degrees C, it would shut down.
What fixed it for me:
1. Use the standard armory crate profile on level 3 (It will shut down more often if I use the custom pubg profiles)
2. Buy a cooling fan, like black shark cooler. I have a wish cooler but it works, phone is around 37-38 degrees even in long gaming sessions.
No shut downs or problems since
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)