App Quality Dashboard

Bass Booster

1.4 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 5.75 Sec
  • Launch time: Icon 7.97 Sec
  • Application size: Icon 2.25 MB
  • Last tested on : 01/05/2017
  • Build ID
    :   v1.1.6
  • Chhi Score
    :   1.4
  • Change Rate
    :   0%

What to fix?

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

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

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

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 Network risks could drastically improve Chhi Score. There are 1 Network risks.

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

App launch time went up by 245.02% initlizate network calls after few seconds of loading the resources. View details

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: audio.sound.effect.bass.virtrualizer.equalizer PID: 32062 java... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

The app took 7.97 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

The app'sNetwork score has improved by25%!

3 tests need immediate attention. View performance graph.

The app has a high performance risk for the phone manufacturer(s) Panasonic, 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.

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

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

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

The app has crashed on few device(s)! View details

Caching: Use LruCache for data caching to optimize memory usage

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

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!

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

22.18 MB of App Dalvik utilized by activity net.coocent.eq.bassbooster.MainActivity. View details

Total Network data consumed was 2744.38KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Well done, Network consumption has come down by 20.08 % compared to build v1.2.3

Screen Coverage

competition benchmark

This app is ranked #833 in Music & Audio

828
829
830
831
832
back-to-top