App Quality Dashboard

Loving Lockets Photo Frames

0.8 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 11.76 Sec
  • Launch time: 2.10 Sec
  • Application size : 5.08 MB
  • Last tested on : 19/02/2017
  • Build ID
    :   13.2.6
  • Chhi Score
    :   0.8
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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

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

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

Oops!, The app crashed on Zenfone 2 Laser , Lava Iris X8 & more devices. View details

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at android.os.Parcel.readException(Parcel.java:1620) View details

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 4943): FATAL EXCEPTION: main 4943): Process: com.pixoplay.lovinglocketsphotoframes PID: 4943 49... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Lava Iris X8 crashed at android.view.ViewRootImpl.setView(ViewRootImpl.java:637) View details

11 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Utilization of Memory is close to the threshold.

27.06 MB of App Dalvik utilized by activity com.pixoplay.lovinglocketsphotoframes.MainActivity. View details

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

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.

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

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

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

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

Screen coverage

competition benchmark

This app is ranked #2325 in Entertainment

2320
2321
2322
2323
2324
back-to-top