Database Develop

Black screen on Intellilikn in my new Opel Astra

I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards

with me Meizu m1 note is exactly the same

barraker said:
with me Meizu m1 note is exactly the same
Click to expand...
Click to collapse
I guess to have Android 5.0 is not the only requisite to use Android Auto... maybe Google should take a look on this..

chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse
try to experiment with other phone with android 511 or higher and with a good quality USB cable

war1 said:
try to experiment with other phone with android 511 or higher and with a good quality USB cable
Click to expand...
Click to collapse
I tried with Huawei P8 lite and Moto G 1st gen (both 5.0) and I got nothing. It works with Nexus 5

Moto G 1st gen the same

Also Moto G 4G

I had the same problem in my Astra.
I've solved it following this steps:
- Wait until the bluetooth connection is fully established.
- Unlock the smartphone (i think is key for this problem)
- Plug the USB cable.
I'm doing it that way since last two weeks and i haven't seen the black screen again on my Intellilink.
Hope it helps.

I have same problem whit samsung A5 (android 5.1).
And secound problem with android auto app (ver. 1.5) in huawei p8lite.
I try connecting phone (android 5.0.1) to opel Astra k.
It works but doesn't refresh screan.
I must tourn on or down the volumne and then screan updates.
Any idea ?

Any workaround about this issue? I'm having the same problem with my Honor 7. Already contacted the Opel Team but that issue seemed to be new to them. I guess it's rather and android/google problem than that of the carmaker. A friend of mine is having the same problems with his Huawei Smartphone, while his wife's Samsung is working.
Both Huwaei/Honor phones run with Android 5 and 6, respectively....

I have an Opel Adam with the Intellilink system. I have the same problem, when connecting Android Auto all I get is a black screen. Sometimes it works and when it does it's really reliable. But it is very rare that it works. I have tried a dozen different phones.
I was wondering if you have Flexdock on your Astra? I have Flexdock on my Adam and I have been thinking if this has something to do with it.
By the way, Apple Carplay seems to work okay. It connects every time but I would prefer using Android.
chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse

erke_ms said:
I had the same problem in my Astra.
I've solved it following this steps:
- Wait until the bluetooth connection is fully established.
- Unlock the smartphone (i think is key for this problem)
- Plug the USB cable.
I'm doing it that way since last two weeks and i haven't seen the black screen again on my Intellilink.
Hope it helps.
Click to expand...
Click to collapse
I am also having this problem despite following these steps... any suggestions? So frustrating as it work sometimes....

Luke.bartholomew1 said:
I am also having this problem despite following these steps... any suggestions? So frustrating as it work sometimes....
Click to expand...
Click to collapse
Same here. These steps didn't help me.
And to add to the misery, AA stopped working completely. The app won't launch anymore when connecting the phone to the car. I'm not getting the black AA splash screen anymore and the car's head unit won't recognize the connection. So I kinda got rid of the black screen problem I have tried clearing cache, uninstall followed by reinstall, pretty much everything besides restoring the phone to factory settings.

chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse
There appears to be major problems with Android Auto and Intellilink 4.0. My car has been into the dealer 3 times in 3 weeks (only just bought it!) And Vauxhall have drawn a blank on what's going on, although Vauxhall have confirmed they know there are problems with their system. I've also got Google on the case analysing debug outputs from my phone by the Android Auto team at Mountain View.
So long as you have installed Android Auto on your phone and responded to the setup prompts, that's all you can do. My car touchscreen often just blanks when I connect the phone too. It is driving me mad.

mjt0801 said:
There appears to be major problems with Android Auto and Intellilink 4.0. My car has been into the dealer 3 times in 3 weeks (only just bought it!) And Vauxhall have drawn a blank on what's going on, although Vauxhall have confirmed they know there are problems with their system. I've also got Google on the case analysing debug outputs from my phone by the Android Auto team at Mountain View.
So long as you have installed Android Auto on your phone and responded to the setup prompts, that's all you can do. My car touchscreen often just blanks when I connect the phone too. It is driving me mad.
Click to expand...
Click to collapse
Okay, that figures. I remember now reading something about Opel/Vauxhall knowing about this problem before. I contacted Opel too and they told me visit the dealer but after what you told, I guess I will pass and let them work it out first.

smatty1 said:
Okay, that figures. I remember now reading something about Opel/Vauxhall knowing about this problem before. I contacted Opel too and they told me visit the dealer but after what you told, I guess I will pass and let them work it out first.
Click to expand...
Click to collapse
I've booked my car in with the vauxhall dealer to have it looked at... However when i said my problem was with android auto, the guy said "what's android auto?" :crying:
So I'm not filled with hope.... On the upside however, I contacted vauxhall head office and a very helpful lady (who knew what android auto was!) said that because it works sometimes, the issue lies with their system and not android auto (so potentially fixable without Google...
She said that there have been a few similar complaints aswell but these were resolved....fingers crossed because it's great when it works... Will update

Luke.bartholomew1 said:
I've booked my car in with the vauxhall dealer to have it looked at... However when i said my problem was with android auto, the guy said "what's android auto?" :crying:
So I'm not filled with hope.... On the upside however, I contacted vauxhall head office and a very helpful lady (who knew what android auto was!) said that because it works sometimes, the issue lies with their system and not android auto (so potentially fixable without Google...
She said that there have been a few similar complaints aswell but these were resolved....fingers crossed because it's great when it works... Will update
Click to expand...
Click to collapse
Would you mind letting us know if the dealer was able to do anything to fix this? I would be interested to hear anything you could tell after the service.
I really hate being stuck on an iPhone and Carplay, which has its problems too, it keeps dropping connection randomly

smatty1 said:
Would you mind letting us know if the dealer was able to do anything to fix this? I would be interested to hear anything you could tell after the service.
I really hate being stuck on an iPhone and Carplay, which has its problems too, it keeps dropping connection randomly
Click to expand...
Click to collapse
Will do. Taking it in tomorrow.
With your issues does it ever work? As i tested it an hour ago and everything was fine.... Tested it 5 minutes ago... Black screen is back

Luke.bartholomew1 said:
Will do. Taking it in tomorrow.
With your issues does it ever work? As i tested it an hour ago and everything was fine.... Tested it 5 minutes ago... Black screen is back
Click to expand...
Click to collapse
It used to work at times, but most of the time I would just get that same annoying black screen. But now it won't even give black screen anymore, nothing happens when plugging an Android phone.

smatty1 said:
It used to work at times, but most of the time I would just get that same annoying black screen. But now it won't even give black screen anymore, nothing happens when plugging an Android phone.
Click to expand...
Click to collapse
So I took it to the dealer and after explaining to them what android auto actually is!! We plugged the phone in and it worked. 10 times in a row....I hate intermittent problems .
So the guy said there was nothing they could do since it was working now but to bring it back if it stops again.... Getting the S7 edge next week so will wait and see how that works.... Apologies i haven't got a better answer for you...

Bluetooth Constantly Becoming Disabled

Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28

I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.

Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.

Post deleted

Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL

Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?

I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.

As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk

I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).

Don't google test their sofware?
This is a poor show by them.

Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?

Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.

danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?

@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk

I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.

@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once

semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
Thanks

GM Android Auto causing my Galaxy to reboot

I've had this happen in numerous GM Vehicles from 2016-2018 Chevrolet, Cadillac, GMC units with AA.
While using Waze or Maps I can run fin 90 percent of the time
While using the above and a music source like I heart or Stitcher I get frequent crashes. My phone will reboot. But when it reboots, I dont have bluetooth connectivity. I have to unplug the phone, Reboot a second time and pluf it back in.
This is annoying and hope there is a solution
Im running the latest versions of Apps on my Galaxy S8 with a Samsung Data cable that came with my phone.

I was recently using an oppo r7sf with lineageos installed and had similar problems. Spontaneous Communications error 12 but no reboot. AA would crash on the head unit and I'd have to reboot in order to get it working properly. Tried many many things but in the end got a new phone and havent had an issue since.

Phone does not connect to android auto head unit

It's been months of on and off again trying to figure this out, still no luck.
I'm running the latest version of Lineage OS.
I'm running the latest download of OpenGAPPs
I'm using a cable that works with my wife's stock moto x4, but does not with mine.
When I connect my phone, I assume android auto tries to start, black screen, then crash back to launcher. My head unit displays "unsupported device"
When i pull down the shade to select a different usb mode, it always reverts back to "no data transfer". Clicking on anything will move the dot, then immediately go back to "no data transfer"
I've tried several troubleshooting guides, I've cleared data and cache for AA, Google, and Play Services.
I'm open to all suggestions.

sythus said:
It's been months of on and off again trying to figure this out, still no luck.
I'm running the latest version of Lineage OS.
I'm running the latest download of OpenGAPPs
I'm using a cable that works with my wife's stock moto x4, but does not with mine.
When I connect my phone, I assume android auto tries to start, black screen, then crash back to launcher. My head unit displays "unsupported device"
When i pull down the shade to select a different usb mode, it always reverts back to "no data transfer". Clicking on anything will move the dot, then immediately go back to "no data transfer"
I've tried several troubleshooting guides, I've cleared data and cache for AA, Google, and Play Services.
I'm open to all suggestions.
Click to expand...
Click to collapse
I thought that was a known Lineage bug. I could never get Android Auto working on Lineage, so I rolled back to stock.
Edit: Here's the open bug https://gitlab.com/LineageOS/issues/android/issues/397

elmerohueso said:
I thought that was a known Lineage bug. I could never get Android Auto working on Lineage, so I rolled back to stock.
Edit: Here's the open bug https://gitlab.com/LineageOS/issues/android/issues/397
Click to expand...
Click to collapse
Interesting. I knew it was an issue for me. not much other talk about it over on reddit for this phone (that i could find). what little i did find was to the tune of "open gapps was messed up from x to y, try installing an updated gapps after y." and that took months for me to do because for the longest time lineage's recovery was messed up, so i figured i'd just check back every now and then. Finally realized recovery was working and here i am. guess I'll go back to stock. Thanks.

Android Auto appears to be working flawlessly after May update of Pixel Experience 10 rom.

Galaxy Note20 Ultra 5G and Uconnect

I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?

Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.