Power Battery

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 11.41 Sec
  • Launch time: Icon 2.43 Sec
  • Application size: Icon 5.15 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v1.8.5.1
  • Chhi Score
    :   3.9
  • Change Rate
    :   +56 %

What to fix?

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

Fixing CPU risks could drastically improve Chhi Score. There are 14 CPU risks.

14 Risk(s) are due to Threads in CPU exceeding the threshold.

Utilization of CPU is close to the threshold.

14 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

The app's CPU score has improved by 46.15% compared to build v1.8.1! Good job!

The app has a high performance risk for the phone manufacturer(s) LYF, Lava, Asus, Karbonn, Panasonic, Lenovo. Check coverage report for more details.

There is high probability of identifying risks running the apps with conditions

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Testability: Providing login / sign-up details could very well improve depth of bot clicks

Caching: Use LruCache for data caching to optimize memory usage

44.20 MB of App Dalvik utilized by activity com.lionmobi.battery.activity.MainActivity. View details

Printing logs on callbacks would make debugging easy for tests run in our platform

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

The app's Memory score has improved by 2.5% compared to build v1.8.1! Good job!

The app's Network score has improved by 58.62% compared to build v1.8.1! Good job!

Well done, Network consumption has come down by 83.29 % compared to build v1.8.1

Screen coverage

competition benchmark

This app is ranked #703 in Tools

698
699
700
701
702
back-to-top