Fixed
Status Update
Comments
su...@google.com <su...@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:
ru...@gmail.com <ru...@gmail.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
an...@google.com <an...@google.com> #4
Even I am facing this issue since I installed mac OS Sierra and also updated to Android Studio 2.2.1.
ru...@gmail.com <ru...@gmail.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.
ra...@google.com <ra...@google.com> #6
Yup, same issue here using Sony MDR-1000X on Sierra. Typical tropical dr oid.
ru...@gmail.com <ru...@gmail.com> #7
Same issue, using Sony MDR-XB950BT.
Description
Version used: 2.1.0
Devices/Android versions reproduced on: 6.0
We're getting this crash on multiple devices:
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.util.ArrayMap.containsKey(java.lang.Object)' on a null object reference
at android.os.BaseBundle.containsKey + 277(BaseBundle.java:277)
at androidx.work.impl.background.systemjob.SystemJobScheduler.getPendingJobIds + 331(SystemJobScheduler.java:331)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule + 138(SystemJobScheduler.java:138)
at androidx.work.impl.Schedulers.schedule + 93(Schedulers.java:93)
at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork + 587(WorkManagerImpl.java:587)
at androidx.work.impl.utils.ForceStopRunnable.run + 82(ForceStopRunnable.java:82)
at androidx.work.impl.utils.SerialExecutor$Task.run + 75(SerialExecutor.java:75)
at java.util.concurrent.ThreadPoolExecutor.runWorker + 1113(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run + 588(ThreadPoolExecutor.java:588)
at java.lang.Thread.run + 833(Thread.java:833)
For some reason, the mMap in BaseBundle is null and getPendingJobIds doesn't catch that:
for (JobInfo jobInfo : jobs) {
PersistableBundle extras = jobInfo.getExtras();
// The map inside extras can be null, so extras.containsKey can cause a NPE
if (extras != null && extras.containsKey(EXTRA_WORK_SPEC_ID)) {
if (workSpecId.equals(extras.getString(EXTRA_WORK_SPEC_ID))) {
jobIds.add(jobInfo.getId());
}
}
}