My aim is throttle sensors/GPU/CPU at a user-defined temperature. The fabled HTC Desire is my test-bed. I have monitored temperature on an early model, and it reboots at 34.7 Celcius with stock ROM and without root. Forums are full of complaints dating back to 2010, so clearly its a long-standing problem.
I don't think the issue is limited to specific devices because every phone is capable of being exposed to dangerous temperatures. I don't think a hard-coded threshold is appropriate because HTC Desire threads suggest that no two devices are identical. This could be down to variance in manufacturing processes, or each phone could also be influenced by external ambient temperature, or internal background processes, etc. On 1 August 2013 11:56, Michael Banzon <[email protected]> wrote: > Are you talking about deviced overheating from running apps using the > standard SDK/API? (no root) I am not sure I have encountered such > problems - but _warm_ devices and _rebooting_ devices are not > uncommon. > > Out of curiosity - how big a problem is this? Any specific numbers or > devices it is limited to? I am tempted to say that it clearly should > be a device maker problem - but hardware updates are a bit tricky to > deploy ;-) > > On Thu, Aug 1, 2013 at 11:41 AM, Glen Whitehead <[email protected]> > wrote: > > Hi all, > > > > I'm looking for code solutions to an overheating issue. > > > > Questions: Can an application disable specific sensors (not the same as > stop > > listening) and throttle the CPU? Can we inject false readings from the > > temperature sensor? Do Android phones have separate internal system > > temperature sensor, and external temperature sensor for user > applications? > > > > All other crazy/wacky thoughts are welcomed, with the proviso that they > can > > be coded. > > > > Thanks. > > > > -- > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en > > --- > > You received this message because you are subscribed to the Google Groups > > "Android Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > -- > Michael Banzon > http://michaelbanzon.com/ > > -- > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
