Verified
Status Update
Comments
cc...@google.com <cc...@google.com> #2
This possibly also affects Linux users. When I start an android emulator my system sound quality drops significantly.
This seems to affect audio output through HDMI but not when I switch to internal speakers - strange!
SDK Version: “Android SDK Tools” Rev., 25.0.7
Host CPU Model: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Device name:hw.device.name =Nexus 5
This seems to affect audio output through HDMI but not when I switch to internal speakers - strange!
SDK Version: “Android SDK Tools” Rev., 25.0.7
Host CPU Model: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Device name:
tw...@googlemail.com <tw...@googlemail.com> #3
I notice the same behavior. For me. it started yesterday, not sure what changed.
Emulator version 25.2.2-3096464
Android version 7.0 (Nougat) - API 24.
I just updated to the latest images to see if it would fix the issue: it didn't. I'm now on image x86 Atom_64 revision 7
Mac os Sierra
Emulator version 25.2.2-3096464
Android version 7.0 (Nougat) - API 24.
I just updated to the latest images to see if it would fix the issue: it didn't. I'm now on image x86 Atom_64 revision 7
Mac os Sierra
tw...@googlemail.com <tw...@googlemail.com> #4
Even I am facing this issue since I installed mac OS Sierra and also updated to Android Studio 2.2.1.
cc...@google.com <cc...@google.com> #5
It appears to be the case for every heavy processing software. When I run a heavy game on my macOS Sierra, the Bluetooth audio quality dips significantly.
tw...@googlemail.com <tw...@googlemail.com> #6
Yup, same issue here using Sony MDR-1000X on Sierra. Typical tropical dr oid.
tw...@googlemail.com <tw...@googlemail.com> #7
Same issue, using Sony MDR-XB950BT.
cc...@google.com <cc...@google.com> #8
I have noticed this as well. What happens is that my headphones are connected using the AAC codec, and then sometime during the initialization of the AVD, it changes the codec to a lower-quality one, that is used for old-style bluetooth headsets on phones (possibly SBC, possibly something else). This happens with my Sony MDR-ZX770BT. You can find out what codec you're currently using by option-clicking on the bluetooth menu item, and hovering over your headphones in the list. More about Mac bluetooth audio quality here: http://www.theghostbit.com/2015/03/force-mac-os-x-to-use-aptx-with-your.html
cc...@google.com <cc...@google.com> #9
I believe the issue here is that Bluetooth switches to a lower (shitty) quality codec (SBC) when the Bluetooth mic is activated.
On my Mac I can simulate the problem by simply opening Sound Preferences while listening to music. This activates the Bluetooth mic and trashes the sound quality. According to my friend this is in the Bluetooth spec but I haven't verified that.
So if the an droid emulator could disable input there would be no problem. I've never used sound input in the emulator but others probably have.
On my Mac I can simulate the problem by simply opening Sound Preferences while listening to music. This activates the Bluetooth mic and trashes the sound quality. According to my friend this is in the Bluetooth spec but I haven't verified that.
So if the an droid emulator could disable input there would be no problem. I've never used sound input in the emulator but others probably have.
cc...@google.com <cc...@google.com> #10
I am to join to this annoying issue. Experiencing it using bluetooth Bose buds. Anybody came up with any workaround solution so far?
Description
Version used:all versions
Devices/Android versions reproduced on: all versions
Hi,
thanks for the great work.
I use a slightly modified version of the PagingSample. Instead of just adding one item when tapping on the "Add" button, I add 20 copies of the same item:
fun insert(text: CharSequence) = ioThread {
dao.insert(listOf(
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString()),
Cheese(id = 0, name = text.toString())))
}
When adding items which will be pre-pended to the list, the PositionalDataSource fails to re-load the visible items. This is a general problem.
My guess:
The PositionalDatasource doesn't know if newly inserted items will be pre-pended by the query or appended. Let's say we have the following scenario:
- initially loading items from position 20
- pre-pending 50 new items
- results in datasource invalidation and new initial load from position 20
- now there are completely different items at position 20
- async diff sees changes and triggers animations
Somehow this happens to be related to the page size used. When increasing the page size, it happens after more inserts. When decreasing the page size, this behavior happen after just the first inserts.
My question is:
How to handle pre-pending inserts with the PositionalDataSource?