The application that causes the phone to heat up

I receive complaints from several users who, after they installed my application, the phone heats up there (sometimes even when the application does not work).

  • What are the reasons this could happen?
  • What can I do to solve this problem?
  • Is there a way my app can warm up the phone even if it doesn't work?

Edit: How does the white background of the application compare with the black or dark background of the application in terms of battery usage? (assuming that overuse of the battery may heat up the phone)

Edit: let's say I have a service that works indefinitely, but does work with the processor very rarely, how expensive, in terms of processor / battery / memory, does it support maintenance? (I know the best way is to implement it using the alarm manager, but before I change the implementation, I need to know how big the difference is.)

+5
source share
2 answers

First of all, your application cannot heat the phone when your application does not work (at least in the background). Now that your application is running, there are many reasons why your application heats up your phone,

  • Calculations - especially floating point calculations. This cause of heat
  • heavy or endless cycles
  • ( ). .
  • , ,

, , - , , . . - , , , , , . , , , . , , .

+5

, , - , , ...

, .

0

All Articles