Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
Hi,
Power values get affected by the USB connection, can you please try ADB over wifi?
Oh, sorry i forgot to mention, i've mostly used ADB over WiFi. and it never showed up.
Just connected it via Cable now to check, and doesn't change.
What kind of Log could include helpfull information?
If you can share a logcat dump we may be able to determine more. You can use logcat's filtering functionality to capture only messages from SDP: adb logcat -s SDPCore.
Unfortunately we do not have access to a Xperia XZ2 device to attempt to reproduce your problem.
Eric
Connected via ADB over WiFi. Cleared Logcat, Started logging, connected Snapdragon Profiler, did a Realtime and selected all 3 Power Values, waited 10 seconds. Disconnected. Stopped logging.
Does that help or you need anything more?
Hi,
From what I see in your logcat it all looks OK to me as far as Snapdragon Profiler's operation. Snapdragon Profiler uses the underlying sysfs nodes located in /sys/class/power_supply/battery/ to get these metrics. Could you please try accessing them manually by using 'adb shell cat'. If they report 0 even from that location then the device itself may be obfuscating the values.
Carlos
Seems like that might be the problem...
Can't access that without root it seems.
Edit:
Same Issues on the OP6.
But with root it works.
https://i.imgur.com/C5q0sll.png
Hi Haldi,
Thank you for checking this. It seems that Snapdragon Profiler is incorrectly reporting that these metrics are available when it shouldn't since the nodes are not readable. I have filed a bug against it and we'll get to it asap. In the meantime as you pointed out, as long as the node is accessible (via root) you should get valid values through Snapdragon Profiler. I apologize for the inconvenience and thank you very much for helping us debug this further.
Cheers,
Carlos