App Quality Dashboard

Dog Monitor

1.0 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 33.92 Sec
  • Launch time: 0.59 Sec
  • Application size : 27.31 MB
  • Last tested on : 10/06/2017
  • Build ID
    :   v1.0.2
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

Oops!, The app crashed on Zenfone 2 Laser , Motorola Moto E (2nd gen) & more devices. View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Motorola Moto E (2nd gen) crashed at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4731) -- FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor:sipStack PID: 20753 java.lang.RuntimeException: Unable to create application com.bipfun.babymonitor.global.App: java.lang.SecurityException: getDeviceId: Neither user 12406 nor current process has android.permission.READ_PHONE_STATE. at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4731) View details

Zenfone 2 Laser crashed at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4744) View details

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

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

10 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 10 High Risk(s).

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.reservoirdev.dogmonitor PID: 17805 java.lang.RuntimeExceptio... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

2 Risk(s) are due to App Total in Memory exceeding the threshold.

Utilization of CPU is close to the threshold.

The app's memory score is 2.0 due to high memory utilization. Needs to be fixed as priority.

Utilization of Memory is close to the threshold.

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

14 tests need immediate attention. View performance graph.

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

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

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

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

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

47.37 MB of App Dalvik utilized by activity com.bipfun.babymonitor.ui.activities.ATutorial. View details

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

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

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

12 Tests crashed out of 26 Tests. Check where the app crashed. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen coverage

competition benchmark

This app is ranked #1833 in Tools

1828
1829
1830
1831
1832
back-to-top