Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by InFocus might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Build 1.1.4 did better in Network . Spikes in Network contributed to score drop by 22.73%

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by Panasonic 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.

Build 1.1.4 did better in Memory . Spikes in Memory contributed to score drop by 36.67%

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

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

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.

Lenovo A6000, Spice Mi-498 Dream Uno, Panasonic P55 has moved from Good to Medium risk due to RISK . View details

Consider re-merging the code from build 1.1.4, Memory score was 3.0

App size increased by 36.04% See how to optimize.

29 tests need immediate attention. View performance graph.

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

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

Total Network data consumed was 1319.07KB 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

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

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

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

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

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

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

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

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

Network utilization on Micromax Canvas A1 AQ4502 exceeded 1024 KB, you might want to consider bringing it down

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

Your average App Dalvik usage surged by 11.7%, Your memory score is 1.9

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

144 apps having similar CPU load have low Chhi Scores

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

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

41.35 MB of App Dalvik utilized by activity com.surpax.ledflashlight.FlashlightActivity. View details

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

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

4 Tests crashed out of 33 Tests. Check where the app crashed. View details

Caching: Use LruCache for data caching to optimize memory usage

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

Test Flows	YU Yuphoria	Spice Mi-498 Dream Uno	InFocus	Panasonic P55	LYF	Karbonn Titanium Machfive	Micromax Canvas A1 AQ4502	Lenovo A6000
Install app	Risk	Risk	Risk	Risk	Risk		Risk	Risk
Scenario 1	Risk	Risk	Risk	Risk	Risk		Risk	Risk
Scenario 2	Risk	Risk	Risk	Risk	Risk	Crash	Risk	Risk
Scenario 3	Risk			Risk		Risk
Scenario 4	Risk	Risk	Crash	Crash	Crash	Risk	Risk	Risk

App Quality Dashboard

Flashlight

#

---

TEST COVERAGE INDEX

Build ID

Chhi Score

Change Rate

Get app performance trends

33%

67%

Current Plan | Basic

40%

80%

18%

17.5%

20%

25%

40%

80%

18%

17.5%

20%

25%

Network on 3G

13.1%

13.1%

13.1%

13.1%

45.1%

15.1%

14.1%

13.1%

By RAM

By Version

By Display

0

0

0

0

Functional Test Coverage

Run tests in

Run tests with

competition benchmark

1071

1072

1073

1074

1075

Dive Deeper With Performance

App Speed Report

Memory Report

Network Report