[Android S] Battery stats are still incomplete in the public release of 12 [203677543]

Bug

Status Update

No update yet.

Description

as...@gmail.com

created issue #1

Oct 20, 2021 10:16PM

* Are you an Android developer?" (Y/N)
n
* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example RPP1.200123.000).
Public release of Android 12
* Is this a regression from Android 11 to 12?
Y
* What device are you using? (for example, Pixel 3 XL)
Pixel 5
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
1. Open battery stats
2. Look for screen on time - *since last full charge*
3. Only find SOT over the last 24 hours.
* What was the expected result?
User can see SOT since last full charge, as per all previous versions of Android
* What was the actual result?
Only SOT over the last 24 hours is shown.
* Relevant logcat output.
null
* Link to captured Android bug report (shared privately in Drive.)
null

This issue was filed some time ago (

https://issuetracker.google.com/issues/188657464) and marked as fixed; however I am reopening a ticket for this issue as it is still not fixed in the public release of Android 12.

Comments

ad...@google.com <ad...@google.com> #2Dec 2, 2021 11:33AM

Assigned to ad...@google.com.

Andreas, are you the correct person to investigate here?

as...@gmail.com <as...@gmail.com> #3Dec 13, 2021 06:29AM

I'm not. Ashutosh?

ad...@google.com <ad...@google.com> #4Dec 13, 2021 04:08PM

This is interesting. The rotation vector (or any sensor for that matter) should not perform differently from the Java API at the native API. Villus, I could not access the video on the bug you linked to. Can you please attach it to this bug ?

ad...@google.com <ad...@google.com> #5Dec 20, 2021 11:59AM

Sure, no problem - attaching the videos here.

as...@gmail.com <as...@gmail.com> #6Dec 25, 2021 10:24PM

Ashutosh, have you had a chance to take a look here?

Sat Dec 25 2021 17:22:28 GMT-0500 (Eastern Standard Time).png

200 KB

View

Download

ad...@google.com <ad...@google.com> #7Dec 27, 2021 02:39PM

Status: New

On Pixel 2 `adb logcat` reports its using 200000us sampling period.
This is 5Hz (SENSOR_DELAY_NORMAL), instead of the desired/expected 50Hz (SENSOR_DELAY_GAME).

01-10 16:14:10.800 794 820 D CHRE : @ 2685.808: +: id 10, otherClientPresent 1, mode 3
01-10 16:14:10.803 794 820 D CHRE : @ 2685.811: [ImuCal] Dynamic sensor configuration: high-performance.
01-10 16:14:10.803 794 820 D CHRE : @ 2685.811: sensorType 9 allowed 1: mergedMode 3, otherClientPresent 1
01-10 16:14:10.803 794 820 I VSC : @ 2685.811: [VSC SLPI] VscSensor type 65545: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.803 794 820 I VSC : @ 2685.811: {Fusion} configure fusion 9 200000us 0us.
01-10 16:14:10.804 794 820 I VSC : @ 2685.811: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.804 794 820 I VSC : @ 2685.812: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.805 794 820 D CHRE : @ 2685.812: sensorType 11 allowed 1: mergedMode 3, otherClientPresent 1
01-10 16:14:10.807 794 820 D CHRE : @ 2685.815: sensorType 13 allowed 0: mergedMode 3, otherClientPresent 0
01-10 16:14:10.810 794 820 I VSC : @ 2685.818: [VSC SLPI] VscSensor type 65546: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.811 794 820 I VSC : @ 2685.818: {Fusion} configure fusion 10 200000us 0us.
01-10 16:14:10.811 794 820 I VSC : @ 2685.818: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.811 794 820 I VSC : @ 2685.819: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.814 794 820 I VSC : @ 2685.822: [VSC SLPI] VscSensor type 65547: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.815 794 820 I VSC : @ 2685.822: {Fusion} configure fusion 11 200000us 0us.
01-10 16:14:10.815 794 820 I VSC : @ 2685.823: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.816 794 820 I VSC : @ 2685.824: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.816 794 820 I VSC : @ 2685.824: [VSC] Request sensor 65538, sample_duration 14 ms, report_duration 0 ms

tu...@google.com <tu...@google.com> #8Jan 12, 2022 12:12PM

Assigned to tu...@google.com.

If I replace:
ASensorEventQueue_enableSensor(sSensorEventQueue, sensor);
ASensorEventQueue_setEventRate(sSensorEventQueue, sensor, 20000);
with:
success = ASensorEventQueue_registerSensor(sSensorEventQueue, sensor, 20000, 0);

in `Sensors.cpp` in the above `AndroidGyroNDK.zip` project, then sensors appear to update at the expected rate.

is...@google.com <is...@google.com> Jul 23, 2023 07:10AM

Status: New

an...@google.com <an...@google.com> Jul 27, 2023 02:03PM

Accepted by an...@google.com.

is...@google.com <is...@google.com> Oct 23, 2023 07:05AM

Status: New

Issue 203677543

Description

Issue summary

Comments

ad...@google.com <ad...@google.com> #2Dec 2, 2021 11:33AM

as...@gmail.com <as...@gmail.com> #3Dec 13, 2021 06:29AM

ad...@google.com <ad...@google.com> #4Dec 13, 2021 04:08PM

ad...@google.com <ad...@google.com> #5Dec 20, 2021 11:59AM

as...@gmail.com <as...@gmail.com> #6Dec 25, 2021 10:24PM

ad...@google.com <ad...@google.com> #7Dec 27, 2021 02:39PM

tu...@google.com <tu...@google.com> #8Jan 12, 2022 12:12PM

is...@google.com <is...@google.com> Jul 23, 2023 07:10AM

an...@google.com <an...@google.com> Jul 27, 2023 02:03PM

is...@google.com <is...@google.com> Oct 23, 2023 07:05AM

Add comment

Issue metadata