Best ROM/Android Version for Android Auto Mirroring (Car gauges) - Google Pixel 5 Questions & Answers

Hey guys,
I'm back here after many years because I bought a Pixel 5 to mirror my screen to show my EcuTek gauges for my Infiniti Q50 on the infotainment display via Android Auto. I was very into Android modding back when I had the Nexus 5X, so I thought this would be an easy task and I was very wrong. So much has changed since then. (there's two firmwares now? lol)
I got the phone rooted on the latest AOSP image, but none of the Android Auto root apps seem to have too much of an effect. I can't downgrade AA because it appears baked into the AOSP Gapps.
What's the best setup to use for this? The phone can be on any version/ROM of Android and will not be connected to cellular/wifi/hotspot so it can't auto-update.
Thanks for the help!

Related

Did you mange to establish a successful connection with Android Auto?

Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
kmajewski said:
Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
Click to expand...
Click to collapse
Sorry but what is android auto
cultofluna said:
Sorry but what is android auto
Click to expand...
Click to collapse
It is an interface in your car. It lets you mirror android to the built in mulitmedia system in a vehicle. There are only main features like dialer, maps, spotify. Works great if you travel a lot and the voice commands helps. Totally hands free.
You gotta have a car which supports Android Auto obviuosly.
I drive Opel Astra MY2017.
kmajewski said:
It is an interface in your car. It lets you mirror android to the built in mulitmedia system in a vehicle. There are only main features like dialer, maps, spotify. Works great if you travel a lot and the voice commands helps. Totally hands free.
You gotta have a car which supports Android Auto obviuosly.
I drive Opel Astra MY2017.
Click to expand...
Click to collapse
I have Volvo V40.....I will try it...
Install through Playstore... or apk?
cultofluna said:
I have Volvo V40.....I will try it...
Install through Playstore... or apk?
Click to expand...
Click to collapse
Please check if your car is supported: android [dot] com [slash] auto
(Sorry I'm still below 10 posts, can't write links)
I had to download an apk, since AA is not yet officialy released where I live.
Android auto works flawless for me now that I have a Oneplus 3t. It Never worked when I had the LG V10. You may want to see if it's a problem with the headunit itself and bring it to the dealer.
I have a 2017 Ford Fusion.
I never had any problems on LG G4 and same vehicle. Once switched to OP3T start having difficulties. It's not only me.
Doesn't work with OOS.
I tried, and tried to get my op3t to work with android auto, but everything I tried failed. I recently started rooting, and was able to use android auto with LineageOS, and RR roms. Turns out these
two are based on ASOP, not OOS.
So far Resurrection Remix 5.8.2 has been the most stable, and have had zero issues with Android Auto.
I don't know why OOS doesn't handle this well (at least for me), but I hope they fix it. I really like OOS, except for that one bug which is a big one for me.
Have the issue..Have not found a work around.
On any OOS build i got it to work but it will freeze when phone gets hot... When I use any other rom it works flawlessly... Right now I'm on Phoenix AOSP extended and works great..
kmajewski said:
Hi folks,
I've been struggling for almost two weeks to got OP3T work with Android Auto. I know it's not only me who is having such issue. The connection itself may be established be it randlomy disconnects after few minutes or even seconds.
Do you have any clue what is going on?
There is a ticket open on OP forums, people are having exactly the same issue.
Link to the discussion: https:// forums.oneplus .net/threads/android-auto-does-not-work.479503
Do you know any workarounds? I can't live without Android Auto anymore
Click to expand...
Click to collapse
No issue here. I'm using cheap 3rd party USB and on a Kenwood unit.
Sent from my ONEPLUS A3000 using Tapatalk
Well this is disappointing. Android Auto is one of the main features I'm looking for in my next car which I plan to get this year...
Works without a problem on my Nexus 6p and now on my 3t Car is a Civic 2016
Sent from my OnePlus 3T
Recently purchased a 3T and having the same issue with OOS 4.1.3. My (soon to be sold unless I go refund my 3T) Nexus 6p never had an issue with AA w/ 2016 Golf GTI.
After reading the official forum's support thread (linked in OP), I updated to the recent Open 5 Beta and gave the "change to MIDI" for USB options a shot and it works for a period of time ~10-15 min but then the OS switches back to USB charging. I have to do the same procedure again to get another short successful duration out of AA. I have roughly a dozen different branded Type C cables and only 2/10 of them work with this method (the official Dash cable being one of them).
I'm going to give RR / Lineage a go and see if they can produce steady AA connections. Since I'm also still playing Pokemon Go I can't root / will have to try the Magisk route. I currently can't seem to get my Pokemon Go Plus to Bluetooth sync with the Go app on either 4.1.3 or Open 5.

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.
anyone ever come across a fix for this?
nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

Android Auto on Android 10

My latest AA version on Pie doesn't work properly, so I've side loaded a much older one that works perfectly. If i upgrade to Android 10 with AA baked in...and it doesn't work well for me...will i be able to uninstall/downgrade the version of AA? (Considering that it is baked in)
Sent from my SM-N960F using Tapatalk
When my phone updated to Android 10 all of my aa issues went away, it works flawless now
Sent from my SM-G975U using Tapatalk
I don't want to risk, especially if the answer to my question is no. AA ver 4.6 works flawlessly for me
Sent from my SM-N960F using Tapatalk
It works fine now. Previously you had to roll-back or install the app "Android auto for phone screens"
They have fixed it and removed the app mentioned above from the play store.
Hi Note 9 owners!
Has anyone noticed/experienced that Android Auto is not starting but the Dex for PC is available in the notification?
I have the latest version which is available from everything. Android 10, January security patch.
Last week it worked without problems. Today I have installed some updates from the Galaxy store, I don’t know whether it is connected to this issue or not and I don’t remember wherher samsung dex was in the list of apps to be updated.
Its included on my Note 9 / android 10 as well. However, I can't open it? Any suggestions?
Hello
Install "Android Auto for mobile" to Google store.
Work fine

AA Shutting down after screen unlock

Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.
Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!
Same here , s10
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect
Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse

Is this the best place to ask about Moto Z3 (non-play, XT1929-17)

Hello,
I'm very new to android roms
Well, I did a little bit of that back in pre-2010 times and some times with my samsung galaxy nexus, but I assume things have changed a lot since then.
I have many XT1929-17 Z3 non-play and a couple Z4 XT1380 and a few Z2F
I want to try many things,
Download all firmware from each phone, and upload firmware to a phone (I guess that's the flash device and radio firmware , not sure)
Make setup a phone to my taste, make a backup so I can continue messing around without having to go through the entire setup process again !
Next, I have the crappy verizon firmware, I would like the stock android or Z3 motorola stock firmware instead of the verizon one ! WIth all the non-erasable bloat- and spy-ware
Next, I am stuck on Android 9 forever, I would like to try android 10/11/12 especially if the moto mods and gestures are still working. Really, just android 10 would be great, the only thing I really want is darkmode notifications and settings !
After that, if there are roms for those, I would like to try lineageos, grapheneos, pixel experience and the other popular firmwares that are made for many phones.
I would like the fastboot and adb windows 10 offline drivers to remote control all aspects of the phone. (I will be using many of those phones as wifi cameras and I'm trying to reliably stop and start recording 240fps video with wifi remote control)
Oh, and I would like to try just plain linux on those phones, if that's even possible. Even if that's just cpu/ram/wifi. I'd like to use one of them as a mini server
I think that's pretty much all I want to try with these phones, do you have advice on how to do this on Moto Z3 non-play ?
Thanks !
you cannot run linux on android smartphone, except you're talking about "linux" on top of "android kernel" which still provides full hardware HAL access. the overhead is nearly the same as running android, so no point in this. but here you go.
https://docs.ubports.com/en/latest/porting/introduction

Categories

Resources