on the new .5 kernel whats thermal managment mean??? sorry im still noobish
in most roms is a service called thermald - this service, as any service - uses memory and resources. on your windows pc, do start/run and type services.msc and press enter.. that is a list of services running on your pc to make it work - the phone has almost the same thing..
what i did for my sensation sense 4.0 kernel is move that service from the rom, into the kernel as part of general thermal management, to an existing kernel process, not an additional one like thermald. - less resources, no additional ram used, etc
what this service (or mod) does is adjust cpu clock according to the temp of the phone - the hotter the phone, the lower the clock - to prevent overheating, etc...
so, in theroy - you can delete the thermald service if it is managed by the kernel ***BUT DONT DO THIS QUITE YET***
the stock thermal service in the HTC kernel has issues finding zone 0 sometimes (not all the time, but yes, sometimes)
when i personally ported this linux 3 feature to my 2.6.38 kernels a few weeks ago - i still had issues w/ the sensor finding zone 0
if the thermal management kernel process cant find the zone, it cant see the temps, or manage cpu speed correctly. I know for the sensation this mod required a change to the shooter-board.c file as well, and i dont see that change in this kernel, nor have i tested it to see if it is working in this kernel.
if you run a kmsg and see:
<3>[ 1637.034361] msm_thermal: Unable to read TSENS sensor 0
anywhere in your log - do not delete or disable the thermald service
if you dont see that, feel free to delete/disable
**what you should see is msm_thermal: blah blah, temp = blah
its kinda hard for me to get it working, when the stock thermal service never worked correctly for me - dont know if it is my phone cause its hw001 or if it is the kernel - even the stock kernel in the RUU have issues reading zone 0 for me.
i have been playing with this specific modification for a few weeks for the evo 3d, and im hoping soon
i DIFFed the code from this kernel to mine, and it is close, not exact - so this mod for this kernel may work - like i said, only way to know is look @ ur kmsg logs
