Fixed
Status Update
No update yet.
Comments
ja...@google.com
ph...@google.com
ph...@google.com
The issue is reproducible with core-ktx 1.2.0 and 1.3.0-rc01.
ph...@google.com
ha...@gmail.com
The Typeface.weight is not a weight of the underlying font file. It is a display style. On older APIs, the display style is adjusted if the Typeface is created from single font. However, after moving to CustomFallbackBuilder, that adjustment is removed since it can crate Typeface from multiple style font files.
Looks like it is good to set display style by ResourcesCompat.getFont for backward compatibility.
bu...@gmail.com
Hi Nona,
Can you please schedule a release after you merge the fix?
Description
There was a regression in RQ1A that was sent as an OTA in November of 2020.
It can cause some apps to stop producing audio when a headset is plugged in or unplugged.
It affects AAudio SHARED LOW_LATENCY streams on devices that support MMAP.
The problem is that the error callback is now called with AAUDIO_ERROR_TIMEOUT (-885)
instead of AAUDIO_ERROR_DISCONNECTED (-899). So if an app is checking for that
error code it may not close the old stream and reopen the new stream.
If an app fails to close the stream properly then it can prevent streams opened by
other apps from working.
Apps can WORKAROUND this issue by ignoring the error code parameter in their
error callback function.
Note that apps written using Oboe will close the stream regardless of the error code.
REPRODUCE
Launch recent version of OboeTester, v1.5.30 or later
Tap TEST DISCONNECT
Follow instructions, plugging and unplugging a headset.
EXPECT
All PASS
ACTUAL
Tests involving SHARED MMAP streams will FAIL.
Note message "onErrorCallback error = -885, expected -899"
This issue is tracked internally as
A fix has been found and will be in a future release.