Root [Boost Mobile] What speed is your warp stable at and what do you run it at?

[Blyss]

My warp is stable up to 1.6 ghz and I set the max in setcpu at that. It seems stable at 1.8 ghz but if you run anything like a game with those settings it gets really hot to the touch around the camera lens and will shutdown after about 15 mins. I imagine it's the heat. On that note, two questions. Is there really no cpu temperature sensor on the warp? All any app will tell me is the battery temp. And what's a safe temp for a cpu like the snapdragon s2? My old warp wasn't really stable above 1.4 which was interesting because it rebooted itself a lot less. This one reboots about twice a day for random reasons. These warps are quirky devices for sure but I still love mine. I paid 200 dollars at the boost store for my first. Got this one on eBay for 40! It's in great shape. No scratches on the screen and only a few minor places on its body which I never see since I have mine in one of those kickstand cases.

 

[Slaiyen]

Mine runs rock steady at 1.8/smartassv2/sio.

There doesn't really seem to be any thermal sensor after a quick google but the shut down is almost certainly heat related as you suspect.

As for your random reboots that may very much depend on the ROM/kernel setup your using.

 

[jimsmith80]

I've found that they become unstable if ran over 1.6 for a prolonged period of time. I believe that the recommended Max is 1.4

 

[LilBit]

Mine runs pretty solid Maxed out at 1.8,Ghz I've had temps at 115 F for prolonged periods with no probs.

Gaming is a different story altogether though.

 

[Skinnyjeans21]

Same here, I used to have dead space on my warp, I couldn't get past the part where Isaac gets the Planet Cracker a few minutes into the game because my warp was at full 1.8 the entire time so it overheated and burned my hand.

 

[mercury0x000d]

My warp is stable up to 1.6 ghz and I set the max in setcpu at that. It seems stable at 1.8 ghz but if you run anything like a game with those settings it gets really hot to the touch around the camera lens and will shutdown after about 15 mins. I imagine it's the heat. On that note, two questions. Is there really no cpu temperature sensor on the warp? All any app will tell me is the battery temp. And what's a safe temp for a cpu like the snapdragon s2? My old warp wasn't really stable above 1.4 which was interesting because it rebooted itself a lot less. This one reboots about twice a day for random reasons. These warps are quirky devices for sure but I still love mine. I paid 200 dollars at the boost store for my first. Got this one on eBay for 40! It's in great shape. No scratches on the screen and only a few minor places on its body which I never see since I have mine in one of those kickstand cases.

The Warp does have a CPU temperature sensor which is monitored by the thermald process. The configuration file (/system/etc/thermald.conf) tells Android the temperature at which to scale down the clock speed.

 

[Blyss]

The Warp does have a CPU temperature sensor which is monitored by the thermald process. The configuration file (/system/etc/thermald.conf) tells Android the temperature at which to scale down the clock speed.

So why does it overheat and shutdown? Is the setting in setcpu overriding the thermald process?

 

[mercury0x000d]

So why does it overheat and shutdown? Is the setting in setcpu overriding the thermald process?

I've wondered that too, but I'm not sure. Either that, or maybe it's the fact that the thermald variables were set appropriately to dissipate heat from a CPU running at 1GHz... not 1.8

Since we have our CPU speeds higher now, I'm thinking the stock numbers are too liberal to be effective anymore and the chip's built-in thermal safety has to kick in and do the job, causing the overheat and shutdown. This is one of the many things on the to-do list for my ROM, but I haven't had time to look into yet lol

 

[LilBit]

I've wondered that too, but I'm not sure. Either that, or maybe it's the fact that the thermald variables were set appropriately to dissipate heat from a CPU running at 1GHz... not 1.8

Since we have our CPU speeds higher now, I'm thinking the stock numbers are too liberal to be effective anymore and the chip's built-in thermal safety has to kick in and do the job, causing the overheat and shutdown. This is one of the many things on the to-do list for my ROM, but I haven't had time to look into yet lol

You can, and will get it done, We have complete faith in you. Lets Rock Merc!

 

[Blyss]

The Warp does have a CPU temperature sensor which is monitored by the thermald process. The configuration file (/system/etc/thermald.conf) tells Android the temperature at which to scale down the clock speed.

Bringing this back up but I found this in the conf:

sampling 1000

[PMIC_THERM]
sampling 500000
thresholds 25 30 50
thresholds_clr 20 28 48
actions none none none
action_info 768000 368640 245760

Looks to me like the thresholds are probably in degrees Celsius, and at those thresholds it says to do...nothing.At least mine does. In action_info those are certainly cpu frequencies, but in action it says none. Maybe if it says like reduce frequency or something similar it would stop it from overheating? Not that I really want it to, the cpu own thermal shutdown probably is good enough.

 

[Blyss]

I looKed into it. Apparently if it said "cpu" instead of "none" then it would scale back the cpu at those temps IF the warp obeys thermald.conf, if not then the kernel apparently interfaces directly with the thermal process. A lot of devices don't even have the conf it seems, but some do like the nexus phones and some HTC points and of course the warp.

 

[mercury0x000d]

Bringing this back up but I found this in the conf:

sampling 1000

[PMIC_THERM]
sampling 500000
thresholds 25 30 50
thresholds_clr 20 28 48
actions none none none
action_info 768000 368640 245760

Looks to me like the thresholds are probably in degrees Celsius, and at those thresholds it says to do...nothing.At least mine does. In action_info those are certainly cpu frequencies, but in action it says none. Maybe if it says like reduce frequency or something similar it would stop it from overheating? Not that I really want it to, the cpu own thermal shutdown probably is good enough.

I looKed into it. Apparently if it said "cpu" instead of "none" then it would scale back the cpu at those temps IF the warp obeys thermald.conf, if not then the kernel apparently interfaces directly with the thermal process. A lot of devices don't even have the conf it seems, but some do like the nexus phones and some HTC points and of course the warp.

So, in theory we could lower the values to some ridiculously low number to force a thermal trap, just to test if the Warp (or kernel) obeys the file. If so, we could make the necessary changes so that it works better without having to resort to the CPU's built-in temp panic. If not, we could eliminate the file completely as a piece of leftover which ZTE should've removed, but neglected to in their wisdom... or the lack thereof.

 

[Blyss]

So, in theory we could lower the values to some ridiculously low number to force a thermal trap, just to test if the Warp (or kernel) obeys the file. If so, we could make the necessary changes so that it works better without having to resort to the CPU's built-in temp panic. If not, we could eliminate the file completely as a piece of leftover which ZTE should've removed, but neglected to in their wisdom... or the lack thereof.

Yeah I already thought of this, but we'd probably have to disable any apps like setcpu and also in some cases the one that comes with the Rom. Also I think the values threshold-clr are probably when the process releases the cpu, i.e. the max one at 50c and the clr at 48c.

One thing though, if those values are degrees c and they have to be, doesn't it seem ridiculous the way that default conf is? Look at the first value 25c. I'm not a matter of converting temperatures in my head but I know 37.5 or so is human body temperature. 98.6, would you really want to cut the cpu back to 768 mhz at what's probably room temp? I know it could be changed but that really makes me think it's a relic.

Unless it's not an internal cpu thermistor. The only temp any app will read from my warp is battery temp. It seems top max out at 113F. And I know it's been a LOT hotter than that on the cpu, I've felt it be at least 130 on the camera metal part. So maybe that's what's going on.

I know one time it was horribly hot down here(Alabama, remember). I had my prevail with me in the car with no a/c and it kept shutting its screen of and ending it's own charging prematurely complaining that the battery was hot and normal operation would resume when it cooled sufficiently.

I've got an errand to run now, but later I may try to force it to throttle the cpu with the conf. If it works I'll try to come up with more sane values and post them, I don't think anyone will use them but hey.... something to do!

 

[Blyss]

I edited the file and told it too drop the cpu to 768 mhz when the temp breached 15c which is around 60f so obviously that should have taken immediate effect. Also disabled the apply on boot setting in setcpu and cpu speed. Rebooted. Stayed at 1.4 ghz for 5 minutes without moving.

So at the very least the thermald conf is being ignored in roms using alien kernel. That is what alliance uses right?

 

[Blyss]

I only renamed mine just to be safe but I'm pretty sure it's a relic thaT can be done away with.

 

[mercury0x000d]

Yeah I already thought of this, but we'd probably have to disable any apps like setcpu and also in some cases the one that comes with the Rom. Also I think the values threshold-clr are probably when the process releases the cpu, i.e. the max one at 50c and the clr at 48c.

One thing though, if those values are degrees c and they have to be, doesn't it seem ridiculous the way that default conf is? Look at the first value 25c. I'm not a matter of converting temperatures in my head but I know 37.5 or so is human body temperature. 98.6, would you really want to cut the cpu back to 768 mhz at what's probably room temp? I know it could be changed but that really makes me think it's a relic.

Unless it's not an internal cpu thermistor. The only temp any app will read from my warp is battery temp. It seems top max out at 113F. And I know it's been a LOT hotter than that on the cpu, I've felt it be at least 130 on the camera metal part. So maybe that's what's going on.

I know one time it was horribly hot down here(Alabama, remember). I had my prevail with me in the car with no a/c and it kept shutting its screen of and ending it's own charging prematurely complaining that the battery was hot and normal operation would resume when it cooled sufficiently.

I've got an errand to run now, but later I may try to force it to throttle the cpu with the conf. If it works I'll try to come up with more sane values and post them, I don't think anyone will use them but hey.... something to do!

I agree with your line of thought here... definitely worth looking into!

I edited the file and told it too drop the cpu to 768 mhz when the temp breached 15c which is around 60f so obviously that should have taken immediate effect. Also disabled the apply on boot setting in setcpu and cpu speed. Rebooted. Stayed at 1.4 ghz for 5 minutes without moving.

So at the very least the thermald conf is being ignored in roms using alien kernel. That is what alliance uses right?

I only renamed mine just to be safe but I'm pretty sure it's a relic thaT can be done away with.

Sounds good, I think we can safely do away with the file then. Nice work!

And yep, Alliance uses Alien.