App Quality Dashboard

Police Lights

0.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 9.30 Sec
  • Launch time: Icon 3.00 Sec
  • Application size: Icon 3.20 MB
  • Last tested on : 18/03/2017
  • Build ID
    :   v2.1
  • Chhi Score
    :   0.5
  • Change Rate
    :   -28.57 %

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 19 CPU risks.

Zenfone 2 Laser crashed at android.hardware.Camera.native_setParameters(Native Method) View details

Oops!, The app crashed on Zenfone 2 Laser , Samsung Duos Galaxy J7 & more devices. View details

Fixing Network risks could drastically improve Chhi Score. There are 12 Network risks.

Potential risk in CPU: Utilization has gone up by 11.76% compared to build v2

Potential risk in Network: Utilization has gone up by72.73% compared to build v2

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

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

12 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Build v2 did better in Memory . Spikes in Memory contributed to score drop by 26.92%

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

Samsung Duos Galaxy J7 crashed at android.hardware.Camera.native_setParameters(Native Method) View details

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-27900 Process: com.chic.policelights PID: 19948 java.lang.RuntimeExcept... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

The app has a high performance risk for the phone manufacturer(s) LYF, Samsung, YU, Lenovo, Panasonic, Motorola, Asus, Karbonn. 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.

Consider re-merging the code from build v2, Memory score was 2.6

Consider re-merging the code from build v2, Network score was 4.4

Utilization of Memory is close to the threshold.

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

19 tests need immediate attention. View performance graph.

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

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

5 apps having similar CPU load have low Chhi Scores

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

App makes 3471.51 KB of network requests. Moving this to a background thread will improve load speed. View details

70.44 MB of App Dalvik utilized by activity com.chic.colorfulpartyligths.MainActivity. View details

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

Total Network data consumed was 3471.51KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

17 Tests crashed out of 20 Tests. Check where the app crashed. View details

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

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

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

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

Screen coverage

Test Flows YU Yuphoria Panasonic P55 LYF Karbonn Titanium Machfive Zenfone 2 Laser Lenovo VIBE K4 Note Samsung Duos Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

  • Risk

Scenario 1

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

  • Risk

Scenario 2

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

  • Risk

competition benchmark

This app is ranked #18 in Events

13
14
15
16
17
back-to-top