-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wakelock parsing #75
Wakelock parsing #75
Conversation
Wait on merging this... I think I've found more wakelocks to parse :) |
Now parsing more wake locks, there are still some double wakelocks that we're not parsing shown in the logs like so:
I think we can probably look at merging this, and opening a bug for it. We should also review CPU usage, and CPU usage per proc to see if it's correct, they've "re-appeared" after fixing a related parsing bug. |
Reviewed CPU/ CPU per proc, they look correct (at a glance). Also added parsing of FG time which is in the same lines... |
Some graphs have quite long scales, in these cases it is better with a day time stamp instead of hours.
Get a much longer log then we get from the event log battery events.
@edsj-sony any more comments on this one? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just nit-picks. I realised after posting the first comment that I could create a review with multiple comments...
Improve wakelock parsing. Also bump revision since we have recovered more functionality.