I am having an issue that I am posting here only on the off chance that someone may have a suggestion. This issue only happens when I have V1Driver running but I really do not think it is a V1Driver issue. I have been using V1Driver since it came to Android with a Google Pixel 1 and have been very happy with the performance. At first I was using a legacy V1C but with V1Driver quickly switched to V1C LE with no issues. I just switched to a new Pixel 3 and now I am having an issue with Bluetooth audio streaming in my car. I am using the built in vehicle Bluetooth exactly as before but now I get very annoying skipping and stuttering in the audio stream. The only thing that has changed is the Pixel 1 -> 3. I did some troubleshooting this weekend. I tried streaming without the V1Driver app running and the audio is perfect. As soon as I connect the app, the skipping starts. Then I tried the JBV1 app which I don't normally use but it also created the skipping so this is not specific to V1Driver. I then added a long extension cable to the V1C LE and moved its location around the cabin hoping to find a sweet spot. I switched the V1C LE with my old V1C and that created the skipping as well. Nothing worked... I also tried unplugging the V1C LE with the V1Driver app running. I found it interesting that the skipping continued for a few seconds even with the V1C LE un-powered until the app reported "V1 Disconnected". That got me thinking to another possible cause. I have read some early complaints with the Pixel 3 having memory management issues that most commonly manifested themselves as crashing background streaming apps. So while I have been focused on Blue tooth interference, a memory management issue also seems plausible. Could the V1Driver app running cause a memory management issue resulting in audio skipping? Again this would be a Google issue... I plan to call Google and see what they say but since this is Bluetooth related, and removing the other Bluetooth device stops the issue, I feel there is a high chance they will blame it on Bluetooth interference. Does anyone have any other suggestions on what I could test to solve this problem?