-
Notifications
You must be signed in to change notification settings - Fork 964
How to see individual app battery status when batterystats are taken for specific package? #36
Comments
Seems you are using Historian 1.0 |
It is 2.0. I have configured 2 days back on Windows. |
I did'nt try to generate bug report for some specific package uptil now. adb bugreport > bugreport.txt On Tue, Oct 6, 2015 at 4:51 PM, Gaurav504 [email protected] wrote:
-------- Muhammad Farhan Khan Arbisoft (Pvt.) Ltd. |
And i following this tutorial for windows. On Tue, Oct 6, 2015 at 5:04 PM, Muhammad Farhan Khan <
-------- Muhammad Farhan Khan Arbisoft (Pvt.) Ltd. |
That's working for me as well. But I'm more interested more in App level information. As mentioned, with this command we can generate the report for specific package also That's what i'm looking for. |
You still can see wakelocks, service, network and power consumption stats But i have not generated the chart for one app. I think you are looking for that, that would be great to see, let me know Happy Analyzation! On Wed, Oct 7, 2015 at 3:28 PM, Gaurav504 [email protected] wrote:
-------- Muhammad Farhan Khan Arbisoft (Pvt.) Ltd. |
Sure. |
hi sir, I am new in battery historian actually. I have problem in battery historian installation on Windows operating system. because it cannot shows the chart like this: I follow this tutorial: and have an error like this: do you have any idea to solve my errors? please help me. Thanks a lot. |
then performed operations after disconnecting the device to power source/USB.
Generated the bug report:
2. adb shell dumpsys batterystats --charged/unplugged {package_name} > bugreport.txt
Created HTML:
3. python historian.py bugreport.txt > battery.html
This does not create 'battery.html' for a specific package.
if I don't give the package name. it works fine.
But my requirement is to generate battery.html file only for specific packages.
Are there suggestions on how should I do it?
Thanks in Advance.
The text was updated successfully, but these errors were encountered: