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.
Related
So who's done the leap and updated to CM 6?
Here's what I noticed, and I've be curious if anyone else has too.
1/ Apps2SD: Not quite sure what they are doing but there is some sort of method that uses 'moved to SD Card' but it seems that noone is calling it Apps2SD. It essentially does the same and seemingly working on my phone but my internal memory is down to 31.74MBs.
2/ The Email App (NOT to be confuse with GMail). Under 5.0.7 it worked just fine. Under 6 it will receive and I can read emails but I cannot reply. When I hit reply I get taken back to the list of emails I received.
3/ I'm using a new GApps Set:
garok89 said:
there are issue with a certain set of gapps....try this set....
http://www.kanged.net/mirror/gapps/gapps-mdpi-FRF91-3-signed.zip
Click to expand...
Click to collapse
Gmail works but Maps does not. It opens to the grey grid then closes. It's like the GPS wasn't turning on but it is turned on.
For this, I'm gonna go back to the other GApps set and see if that fixes this annoying issue.
gapps-ds-ere36b-signed.zip
Well, installing the old GApps set didn't work....it was acting like I did click on 'install anyzup from SDcard" in the recovery menu....oh well, reinstalled the newest suggested set and I'm back to where I was. GMail working but no Maps.
For those who can understand logs:
http://cyanogenmod.pastebin.com/5AET3g8m
I'm going to try a fix_permissions but I am rather loath to do so...last time ir broke a bunch of other things which ended up in a re-flash.....well, here goes nearly lost hope....
Yeah...shoulda known....fix_permissions just seems to break things...
http://cyanogenmod.pastebin.com/xaUufamL
Phone rebooted after it finished booting up and I hadn't touched a thing.
It booted up and stayed the 2nd time but couldn't get into my wireless settings to tell it to connect to my provider without a FC.
http://cyanogenmod.pastebin.com/n8zeNLSj
Sigh...back to wiping and reinstalling again....maybe I will go back to 4.2....
So I used a guide a few months back to make my HTC One into the Google Play edition. Today I finally got around to installing some updates. I went to 4.4.3 and installed it, and then noticed that there was another update out, 4.4.4, and went ahead and it installed that as well. Everything came out fine, but I'm having some issues:
The biggest is a flickering kind of screen glitch - I've attached a photo. I can't take screenshots anymore, either; it tells me that 'storage may be in use'. It goes away if I swipe or change something, but always comes back if I, say, reopen the keyboard. It happens everywhere, including the status bar.
The powerdown menu also no longer displays. My screen simply goes dark like it does when the menu opens, but it doesn't display the options. It still functions as if it's there, as I've been able to use it to shut down my phone.
I haven't been able to find anything online about it - perhaps I should just roll back to the last version I was running if I can't figure this out.
Anybody know? Wasn't having issues like this before.
dilyn said:
So I used a guide a few months back to make my HTC One into the Google Play edition. Today I finally got around to installing some updates. I went to 4.4.3 and installed it, and then noticed that there was another update out, 4.4.4, and went ahead and it installed that as well. Everything came out fine, but I'm having some issues:
The biggest is a flickering kind of screen glitch - I've attached a photo. I can't take screenshots anymore, either; it tells me that 'storage may be in use'. It goes away if I swipe or change something, but always comes back if I, say, reopen the keyboard. It happens everywhere, including the status bar.
The powerdown menu also no longer displays. My screen simply goes dark like it does when the menu opens, but it doesn't display the options. It still functions as if it's there, as I've been able to use it to shut down my phone.
I haven't been able to find anything online about it - perhaps I should just roll back to the last version I was running if I can't figure this out.
Anybody know? Wasn't having issues like this before.
Click to expand...
Click to collapse
Bump, same problem, same situation. Rolled back to 4.4.3 for now
My WiFi was working fine the entire day, until I took a nap. When I woke up the WiFi started to turn on and off constantly. I tried messing with the WiFi settings, but it did nothing. I tried restarting the phone a few times, but then it started to boot loop a couple times and eventually it fully booted. I tried restarting my router, but it did nothing. I still have to install the August Security Patch, maybe that will fix it? I have also tried forgetting my WiFi networks.
Anyone run into this issue or have some tips on what to do?
I am running stock, not rooted, 6.0.1, with July Security Patch.
porky101 said:
My WiFi was working fine the entire day, until I took a nap. When I woke up the WiFi started to turn on and off constantly. I tried messing with the WiFi settings, but it did nothing. I tried restarting the phone a few times, but then it started to boot loop a couple times and eventually it fully booted. I tried restarting my router, but it did nothing. I still have to install the August Security Patch, maybe that will fix it? I have also tried forgetting my WiFi networks.
Anyone run into this issue or have some tips on what to do?
I am running stock, not rooted, 6.0.1, with July Security Patch.
Click to expand...
Click to collapse
Go into "Settings", then select "Storage & USB", then select "Apps". Proceed down the page until you locate "Google Connectivity Services". When you open the storage details for the app, select the information icon (lowercase "i" with a circle around it) located near the top/upper-right section of the screen; where it displays "Google Connectivity Services". From there, It'll load the "app info" page. Located at the top-right corner of the screen, select the Image Button icon (the three dots going vertically) and uninstall the updates for the app. It will ask if you want to replace the app with the factory image, select "OK". When the updates are uninstalled, open up the Play Store and navigate to "My Apps & Games". If all of the apps that you have downloaded on your phone are up-to-date, the first app indicating that it needs an update will be "Google Connectivity Services". Reinstall the updates for the app and that should resolve the issue. When I executed this method for my Nexus it stopped disconnecting spontaneously. I hope this method works for you, as well. Let me know if you experience any further issues. Take care, dude.
Start from the beginning. Back a few weeks ago, when 4.1.5 was leaked but not officially announced, I downloaded 4.1.5 and flashed it through TWRP. Then 4.1.6 was released officially right after I've done my upgrading. So I CLEAN FLASHED 4.1.6 again on my phone.
Now the weird part: after 2 days of normal use (no flashing, no new apps installed), I left my phone charging today while went asleep. After I woke up, my phone is at 15% of battery. Although connect to the DASH charger, the phone doesn't charge at all with its LED showing red.
More weird is I can't open the notification center. I can pull the 5 toggles down, but can't open the whole menu.
Plus, notifications don't show up (no toast notification, no icons while in the homepage either).
My access to developer options is also blocked (says "Developer options is not available to this user").
The home button, recent apps button DOESN'T work - no matter if u switch the buttons in settings, or toggle the on-screen soft buttons. Although the "return" button and the fingerprint sensor DOES work.
Root access is still there (using Magisk).
While using TitaniumBackup, the app warns "This device's Android ID has changed". And a few apps have logged themselves out (I guess because of the ID change).
I think I can solve the problem by simply factory reset it. But Questions is : what's going on with my phone?
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
elmarian756 said:
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
Click to expand...
Click to collapse
Wow! I can't image someone had the same issue. So i actually re-flashed 4.1.6 and it's working.
But the charging problem persists. I've tried multiple power sources from the room, the kitchen, etc. None seem to be working.
Strangely, I was able to charge the device once a few hours ago at evening. And then it stopped charging again after I got the system working.
Any idea?
I just got into my car (2018 Ford Fusion with Sync 3) and connected my phone. When I pushed the infotainment "Android Auto" button, the screen went to black and stayed there. I then looked at my phone and saw that the phone was trying to launch AA (in my status bar, I saw the Android Auto icon), then the icon would disappear, and then the phone would try again. This continued repeatedly.
When I got back to my computer, I looked at google play store and saw there was an update yesterday (6AUG).
In the car, I also tried clearing out the data/cache for Android Auto and then reconnecting, but it continued to exhibit this behavior.
I'm wondering if others have noticed this issue.
For the record, I have a Pixel 3xl on the July Security patch.
Edit: I installed August Security Update and all seems to be well now. Strange.
Cheers,
B.D.
I am having the same issue. I have a Oneplus 7 pro and my car is a 2018 VW Golf GTI. When I plug it in to the USB, the head unit just goes black. When you touch the screen you can hear clicks, however then the screen cuts back out "No Communication". I've tried turning USB Debugging On/Off. I've uninstalled android auto, reinstalled..cleared cache, cleared data. I've also cleared cache on Google play services. I've tried older versions of Android Auto and different cables same issue. Any recommendations? I'm guessing it a Google Play Services update causing it.
change your cable.... android auto is terribly picky on the cable.
The only cable working with my oneplus 8 is the stock cable...
ShadowJP88 said:
change your cable.... android auto is terribly picky on the cable.
The only cable working with my oneplus 8 is the stock cable...
Click to expand...
Click to collapse
Well I've done some more trouble shooting...still haven't solved it, but still... I have tried 5 different cables to no success. 2 other "official" OnePlus cable, a high end cable and another standard cable. So we can eliminate that. I tried an Old Nexus 6 I have around and "bingo" that does work with the cable I've been using my and shows up with Android auto. So I know know it's the OnePlus 7. And after uninstalling and reinstalling android auto, clearing cache to no success. I'm thinking of only two options left
..Either wait for Google to provide an update or wipe and reset my phone which is a HUGE headache...
mullman85 said:
Well I've done some more trouble shooting...still haven't solved it, but still... I have tried 5 different cables to no success. 2 other "official" OnePlus cable, a high end cable and another standard cable. So we can eliminate that. I tried an Old Nexus 6 I have around and "bingo" that does work with the cable I've been using my and shows up with Android auto. So I know know it's the OnePlus 7. And after uninstalling and reinstalling android auto, clearing cache to no success. I'm thinking of only two options left
..Either wait for Google to provide an update or wipe and reset my phone which is a HUGE headache...
Click to expand...
Click to collapse
Are you using a beta version of Google play services?
I'm some situations it create different problems
Fishcat7 said:
Are you using a beta version of Google play services?
I'm some situations it create different problems
Click to expand...
Click to collapse
I was in Beta, and left it...it still doesn't work, unless there is a easier way to roll back to an earlier version of play services.
Play Services Version
version 20.26.14 (120400-320008519)
--Edited--
I ended up wiping my phone and putting paranoid android quartz 4 as a custom rom.
Android Auto works fine now.