[Developer Preview Android P] Many issues with Android Auto stability, music playback apps [110974825]

Fixed

Bug

Platform

Status Update

No update yet.

Description

re...@gmail.com

created issue #1

Jun 29, 2018 12:16PM

Since I updated to Android P I have had continuous issues with Android Auto. The android auto app seems to crash regularly and proceeds to auto re-load. If I have maps running, the screen swipes away left, remains black for maybe 5 seconds, then re-loads to the home screen. Maps continues to run.

I'm also having issues with all streaming music playback since updating. Google Music and Pandora have continuous issues. If I select a recent playlist or station on google music it will not play. It attempts to play a song for a few seconds then jumps to the next and fails again. Eventually it says 'unable to play song' or something of that nature. I'm unable to get Pandora to even play music.

Oddly if I ask Google Music to play a station using voice it works. However once playing it seems to stop the song in places where I have even a very short lapse in coverage. If I hit play again it starts the same song over from the beginning. Not sure if this is a buffering issue?

Running Android P, latest build on my Pixel XL
Android auto issues are happening in my 2016 VW GTI
Prior to updating I had zero issues with Android Auto in the GTI

This form is for issues and requests related to the Android P Developer Preview only. Please only report issues that are regressions from the behavior in Android P. For all other issues that also reproduce on other versions of Android, please file it in the AOSP issue tracker at

https://goo.gl/TbMiIO

If the issue is not due to a platform bug, we will do our best to notify the developer. However, note that it is the up to the the developer to actually address reported issues.

Before logging your issue, check to see whether it is a known issue described in the current release notes at:

https://developer.android.com/preview/release-notes.html

or has already been reported at:

https://goo.gl/Wn5g65

If the issue has already been reported, you can "star" or comment on the existing report if it corresponds to the issue you are seeing.

To expedite resolution of your issue, please provide as much relevant and specific information as possible. This will probably require some work from you. Most reports should include at least the following:

* Which Developer Preview build are you using? See Settings > About phone > Build number (for example OPP5.170921.005).

* Is this a regression from O to P?

* What device are you using? (for example, Pixel XL)

* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc

* What was the expected result?

* Can you provide the API document where this expected behavior is explained?

* What was the actual result?

* Relevant logcat output.

* Link to captured Android bug report (shared privately in Drive.)

* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)

To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.

Comments

dn...@google.com <dn...@google.com> #2Jun 29, 2018 12:41PM

Assigned to dn...@google.com.

Project: platform/frameworks/support
Branch: androidx-main
Author: Daniel Santiago Rivera <danysantiago@google.com>
Link: https://android-review.googlesource.com/3453829

Use Context.getDatabasePath() when a driver is configured.

Expand for full commit details

Use Context.getDatabasePath() when a driver is configured. 
 
This helps users migrating to driver APIs that use simple database names and expect Room to figure out the directory to store the database, for which the SupportSQLiteOpenHelper is responsible off when no driver is used. 
 
Since getDatabasePath() does some IO, a hook for the driver wrapper in the base connection manager was added so that the file name could be resolved, lazily and in the background thread where the connection is being opened. 
 
Lastly, if a bad path is used, a more proper error will be thrown instead of an obscure 'can't create file lock' since creating a file lock will first be attempted before actually creating / opening the actual database. 
 
Bug: 377830104 
Test: BuilderTest 
Change-Id: I833154e2855a38520e5a0e8c802964bd455000e8

Files:

M room/integration-tests/multiplatformtestapp/src/androidInstrumentedTest/kotlin/androidx/room/integration/multiplatformtestapp/test/BuilderTest.kt
M room/room-runtime/src/androidMain/kotlin/androidx/room/RoomConnectionManager.android.kt
M room/room-runtime/src/commonMain/kotlin/androidx/room/RoomConnectionManager.kt
M room/room-runtime/src/commonMain/kotlin/androidx/room/concurrent/ExclusiveLock.kt

Hash: 35ddf21c6ede1af577d2d20b96107e04988b04e0
Date: Fri Jan 17 15:42:06 2025

dn...@google.com <dn...@google.com> #3Jul 9, 2018 05:32AM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.room:room-runtime:2.7.0-alpha13
androidx.room:room-runtime-android:2.7.0-alpha13
androidx.room:room-runtime-iosarm64:2.7.0-alpha13
androidx.room:room-runtime-iossimulatorarm64:2.7.0-alpha13
androidx.room:room-runtime-iosx64:2.7.0-alpha13
androidx.room:room-runtime-jvm:2.7.0-alpha13
androidx.room:room-runtime-linuxarm64:2.7.0-alpha13
androidx.room:room-runtime-linuxx64:2.7.0-alpha13
androidx.room:room-runtime-macosarm64:2.7.0-alpha13
androidx.room:room-runtime-macosx64:2.7.0-alpha13

de...@gmail.com <de...@gmail.com> #4Jul 12, 2018 01:36AM

2 Major drops-outs this morning (Music Stops, Head Unit Screen goes Black, and then AA Comes back). Still also getting smaller drop-outs where Music Stops and I have to click play again, but maps continues to function.
Bug Check in the following Location:

https://drive.google.com/drive/folders/1N-dWQtQ4eavO7rISLkw2NQmO26l-z-Zi?usp=sharing

File is: bugreport-taimen-PPP4.180612.004-2018-07-11-10-10-55

The errors occured between 7.30am and 8.00am (Australian EST)

*******************************
Uploaded another one as well, same link as above, another 4 or 5 big drop-outs/crashes of Android Auto.

File Name: bugreport-taimen-PPP4.180612.004-2018-07-11-19-24-42

Crashes occured between 7.00pm and 7.24pm (Australian EST)

de...@gmail.com <de...@gmail.com> #5Jul 12, 2018 01:38AM

The above is on a Pixel 2 XL and is only happening on DP3/4 (AA Didn't work at all on DP2)
Head Unit is a Kenwood DDX917WS.

I've been posting in a related thread with no google response...

https://issuetracker.google.com/issues/79496344

re...@gmail.com <re...@gmail.com> #6Jul 12, 2018 10:47AM

Issue sounds similar to what I'm having on my Pixel XL. Maps seems to run OK, but AA seems to crash intermittently, screen goes black, reboots to home screen and navigation resumes. Music playback is almost completely non-functional with Google Play music. Pandora works occasionally, but crashes regularly and I playback stops every few songs and I have to go hit play again.

de...@gmail.com <de...@gmail.com> #7Jul 12, 2018 11:27AM

Definitely upload a bug report, the more data they have, the better.

st...@gmail.com <st...@gmail.com> #8Jul 13, 2018 12:34AM

Bug report below. Experiencing same issues as OP on Pixel 2 XL DP4. Additionally still seeing pixelation issue which we have not received an update on for months and resolution deadline was missed.

https://drive.google.com/file/d/1nNeGje5Wvk4j_kyYJFy5RkQDfCfB6ssl/view?usp=drivesdk

ur...@gmail.com <ur...@gmail.com> #9Jul 15, 2018 03:56AM

Same thing is happening with me since yesterday. While navigation, screens goes black and comes back after a few seconds. Sometimes shows the same route as before blackout, sometimes I need to get directions again.
Android Auto Version: 3.4.582534-release
Pixel XL
Android Version: 9
Car Model : Acura TLX 2018
Google Play Version: 10.6.08-all [0] [PR] 200628961
Google Maps: 9.81.1 (#981100244)
Waze Version: 4.40.0.4

ka...@buildingbetterbonds.com <ka...@buildingbetterbonds.com> #10Jul 15, 2018 12:01PM

I am new with this as I just got a new base Impreza, but despite working at the dealership yesterday, on driving home, siriusxm, which launched automatically, kept crashing and restarting on phone as well...Is this an app issue? Or might it have to do with availability of data in rural Vermont?

gu...@gmail.com <gu...@gmail.com> #11Jul 15, 2018 08:56PM

Appears to be an issue with the P beta. People running the beta, with different versions of AA, are reporting the same issue in the Google plus group.

ja...@gmail.com <ja...@gmail.com> #12Jul 17, 2018 01:13AM

Having that same exact issue as described by op. Please advise if there is any information we can provide.

ja...@gmail.com <ja...@gmail.com> #13Jul 17, 2018 03:41PM

Attached bug reports for reported issue -

https://drive.google.com/file/d/1tFctpEefVkh8DEypbTeG_UK-ei4l26yP/view?usp=sharing

https://drive.google.com/file/d/1W33ttDDgf74u4v-lgl3ZeJg1KLMk61SK/view?usp=sharing

de...@gmail.com <de...@gmail.com> #14Jul 17, 2018 10:18PM

It was definitely less prevalent in the Android Auto release before this one (3.4.54?), but I've always had random dropouts with DP3/DP4 on the Pixel 2 XL (Didn't work at all on DP1/DP2)

cb...@gmail.com <cb...@gmail.com> #15Jul 18, 2018 04:12PM

It sounds like my issue is similar to this one, but I'm adding the attached information and photo to assist.

The AA display flickers off and on every few minutes, with no apparent cause. Bluetooth audio through AA almost always continues uninterrupted.

One troubleshooting detail I can add to this issue is that I know it is not a phone hardware or cable issue. I replaced the cable, but I also replaced my Pixel 2 XL due to a bad charging port (which was causing overall connection issues with AA and all chargers). I thought that the issue was the bad port, but this flickering and restarting was happening before the replacement and is still happening on the new (refurb) handset I received.

Error message: "Android Auto route guidance started. Honda Navigation route guidance cancelled." - I don't always get this message, but usually do.

Car / head unit make & model: 2018 Honda CR-V Touring; factory head unit (note my vehicle has built in nav, which I do not use)

Phone make & model: Pixel 2 XL

Android OS version: 9 (Build PPP4.180612.004)

Android Auto app version:3.4.582534-release

Google Play services version: 12.8.72 (100400-202717283)

Google Maps version: 9.81.1

deleted

Restricted

0 B

dn...@google.com <dn...@google.com> #16Jul 23, 2018 12:34PM

We have passed this to the development team and will update this issue with more information as it becomes available.

be...@gmail.com <be...@gmail.com> #17Jul 23, 2018 11:34PM

Same issue here - VW - MIB II Entertainment Unit - constantly flipping to black.

su...@gmail.com <su...@gmail.com> #18Jul 24, 2018 01:43AM

+1 here Pixel XL on DP4 with 2018 Crosstrek screen blanks out as well. I've noticed that the location services icon pops up as reboots screen on radio. And is more prevalent when using Google maps or Waze.

deleted

Restricted

0 B

em...@gmail.com <em...@gmail.com> #19Jul 25, 2018 01:02PM

Same issue...

Kenwood ExCelon DDX9903S, ApplicationVersion: 2.7.0008.0600
Google Pixel 2, Android Version 9, Build number PPP4.180612.004
Android Auto version: 3.4.582534-release
Waze version: 4.41.1.0
Google Maps version: 9.82.2

I've only noticed it with the navigation apps (Google Maps and Waze). I haven't experienced any other apps resetting/crashing.

mi...@gmail.com <mi...@gmail.com> #20Jul 25, 2018 10:38PM

Same here with Kia Soul 14 head unit, pixel 2XL, PPP4 with latest Waze and Google maps.

de...@gmail.com <de...@gmail.com> #21Jul 26, 2018 01:24AM

Keen to see if Today's DP5 release has any effect on this...

mp...@gmail.com <mp...@gmail.com> #22Jul 26, 2018 10:43AM

Started Google maps with directions to work, cancelled directions but kept map running, screen went black and when it came back directions started again.

https://drive.google.com/file/d/1FSMe4CFUv5jHCMlnwMYnKM4KUbIqbRxE/view?usp=drive_web (bugreport-taimen-PPP5.180610.010-2018-07-26-06-23-55.zip)

de...@gmail.com <de...@gmail.com> #23Jul 26, 2018 11:00AM

I'll give new logs tomorrow for this, but still busted on Pixel 2 XL with Preview 5, 5 black screen crashes/resets in the first few minutes of driving, plus more the way home...

re...@gmail.com <re...@gmail.com> #24Jul 26, 2018 12:06PM

Same here. Installed DP5 on Pixel XL, no change to android auto behavior. Google play music plays erratically, randomly skips songs, and gets stuck in loops of constantly skipping songs without playing. Constant crashes to black screen, mostly during maps.
Pandora seems to work fine.

Will upload bug report later today

qa...@gmail.com <qa...@gmail.com> #25Jul 26, 2018 12:58PM

I've gathered some data from several other forums where this is being discussed. The only two consistent elements are: Android P, and Android Auto 3.4. Someone above mentions that it seems to not matter which version of Android Auto, but I haven't seen any evidence of that. I'm not sure where he's seen reports of other versions experiencing the same behavior, but in my combing through forums I'm not seeing that. Always 3.4. I can reliably have it happen on every single drive with 3.4, but as soon as I go back to AA 3.3 (using an APK posted on APKMirror), the crashing on maps completely vanishes. Changing no other variable (maps version, build of Android P, etc) makes a difference. I've been driving for over a week now with AA 3.3 and not a single crash. The crashing actually started for me right when 3.4 was first released. Hopefully enough people have starred this to get attention because it looks like there are a sizeable block of people experiencing this problem, but they're unfortunately scattered across many different issue tickets and support message board postings and other forums.

If I had time, I'd go register on all of them and post a "please go star it here" link, but I'm pretty busy this week.

em...@gmail.com <em...@gmail.com> #26Jul 26, 2018 01:21PM

I've rolled back to AA 3.3 and will give it a test in a few hours. I'll post the results later today.

ja...@gmail.com <ja...@gmail.com> #27Jul 26, 2018 05:02PM

When did the AA 3.4 come out? I want to say that I experienced the issue as soon as I went to Preview 4, and was on AA 3.3 first, and then AA upgraded to 3.4, and I thought that would fix the issue. It made it marginally worse for me. (IE, Preview 4 AA 3.3, issue occurred sporadically, Preview 4 AA 3.4, issue occurred much more frequently.) I could be wrong on the timing however, and don't know for sure if I was on 3.3 or some other version, but I am currently running 3.4 and Preview 5. I haven't been able to test, but based on previous responses I am not hopefully. I will say I experience no issues with AA and audio/navigation streaming if I don't use the screen mirroring to my HUD in the car. Issues only occur for me if screen mirroring is happening. That's why I assume its an issue more OS (USB/HCI/Bluetooth) related and less application related. Albeit that's a complete assumption and it could be 100% apps fault for either problem.

de...@gmail.com <de...@gmail.com> #28Jul 27, 2018 12:06AM

I'm pretty sure I had the issue with DP3 with 3.3, then upgraded to 3.4 hoping it would fix it. It has become significantly worse with 3.4 and DP4/DP5 However.... Given Google has only just acknowledged this officially and its been open for almost a Month, the best you can do is get as many people as possible to STAR the issue and to provide logs to fix it.

da...@gmail.com <da...@gmail.com> #29Jul 27, 2018 12:50AM

Pixel 2 XL - 17 Accord Hybrid Touring

This issue was present on DP3, DP4, and remains on DP5.

em...@gmail.com <em...@gmail.com> #30Jul 27, 2018 12:56PM

I rolled back Android Auto from 3.4 to 3.3 and didn't experience any resets/crashes with Waze navigation on my 30 minute commute yesterday afternoon. Obviously not conclusive, but worth trying if, like me, this bug was driving you nuts.

de...@gmail.com <de...@gmail.com> #31Jul 27, 2018 01:27PM

My rollback to Android Auto 3.3 got rid of all crashes other than my Music stopping periodically and I have to press play again (Cloud Player), still better than a constantly dying Maps screen :)

sa...@gmail.com <sa...@gmail.com> #32Jul 28, 2018 12:02AM

Rolling back to to AA 3.3 has stopped Waze from restarting but my SiriusXM app continues to have issues. It will play for a few minutes then it restarts and I have to manually start my downloaded show again. Pixel XL DP5/Hyundai Sonata.

de...@gmail.com <de...@gmail.com> #33Jul 30, 2018 12:32AM

Head Unit: Kenwood DDX917WS
Phone: Pixel 2 XL
Android: Android 9 DP5
Media Player: Cloud Player / Double Twist / Google Play Music

Tried rolling back to Android Auto 3.3, this seemed to fix Map stability to an extent, but this morning I had multiple restarts where it wasn't a black screen, but all the Maps/Media/Home buttons disappeared and music stopped (had to press play to start he same song again).

See log name below:
bugreport-taimen-PPP5.180610.010-2018-07-30-08-32-52

I then upgraded Android Auto back to 3.4, and back to major black screen issues and Music Dropouts, see log below:
bugreport-taimen-PPP5.180610.010-2018-07-30-09-00-30

Google Drive Location:

https://drive.google.com/drive/folders/1N-dWQtQ4eavO7rISLkw2NQmO26l-z-Zi

ci...@gmail.com <ci...@gmail.com> #34Jul 30, 2018 12:16PM

Head Unit: Sony XAV-XA5000
Phone: Pixel 1
Android: Android 9 DP5
Media Player: Google Play Music
Maps: Google Maps/Waze

Same problems here. Android Auto will crash often, screen go black and sometimes restart, sometimes need to reconnect USB. On latest version of Android Auto.

Sometimes the phone will not connect and the head unit will say "USB device not supported" but not as often as the crashing

https://drive.google.com/file/d/1gY3hixTHQJ7PoTx2trfwJ5wdT4WpKM6r/view?usp=drive_web (bugreport-sailfish-PPP5.180610.010-2018-07-30-18-31-01.zip)

ra...@gmail.com <ra...@gmail.com> #35Jul 31, 2018 09:09PM

I would just like to add that this is happening on my 2017 CRV head unit with a Pixel 2 as well.

ke...@gmail.com <ke...@gmail.com> #36Aug 1, 2018 12:08PM

Same issue. Waze/Maps would reset every few minutes. Screen goes black, and come back after a few seconds.
Since I use Android 9 beta, I have issues with the song info not being displayed (there's usually the top overlay that appears for a few seconds, now nothing.)

Android Auto Version: 3.4.582534-release
Pixel XL 2
Android Version: 9 PP5
Car Model : VW e-golf 2018
Google Play Version: 10.8.50-all [0] [PR] 206058588
Google Maps: 9.83.0
Waze Version: 4.41.1.0

ke...@gmail.com <ke...@gmail.com> #37Aug 1, 2018 12:09PM

Downgrading to Android Auto 3.3 fixes the Waze/Maps issue, but not the music (song display) issue.

pa...@google.com <pa...@google.com> Aug 8, 2018 12:00AM

Reassigned to pa...@google.com.

pa...@google.com <pa...@google.com> #38Aug 8, 2018 11:23PM

we are aware of this issue, and working on this. I will get back to you once I have an update

pa...@google.com <pa...@google.com> #39Aug 10, 2018 12:04AM

Thanks for the feedback. We are aware of this issue regarding Android Auto frequently restarting during navigation after Android P update. We have rolled out a fix in the next Android Auto update (Android Auto app version: 3.5).

pa...@google.com <pa...@google.com> Aug 10, 2018 09:16PM

Marked as fixed.