Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
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:
il...@google.com
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
Description
Version used: 1.0.0-beta01
Devices/Android versions reproduced on:
This is a feature request.
TL;DR: Please make exact URI matches the highest priority for deep link resolution.
Currently, the navigation library places higher priority on the deep link matches with the highest number of placeholders.
Example:
Given deep links:
* deep link 1: uri="hostname/page.html"
* deep link 2: uri="hostname/{username}"
The second deep link will match even when the uri is actually "hostname/page.html".
Ian Lake suggested (in ASG) that the following might be a further refinement of the deep link resolution algorithm: "exact matches > multiple placeholders > single placeholder > partial match". This would make it possible to resolve the URIs correctly in the above example.