Quick rant: I purchased a pixel 2 xl and a Pioneer NEX headunit and was very excited to get Android Auto in my vehicle. Since day one it's been a raging dumpster fire. Biggest issue being Android Auto just won't launch on my pixel 2 xl and my wife's pixel 2. However my Nexus 6p works perfectly. Sometimes it launches within a few minutes, sometimes it takes my entire 45 min commute to work and it never launches. It's like it's RNG based. Once connected it stays connected. I'm not going to into all the other frustrating bugs such as volume issues, Assistant coming out of different speakers, hangs, crashes, weather tile is now gone somewhere, and many more smaller gripes.
Now that that's out of the way does anyone make a ROM or unofficial app for Android Auto that works on some of these issues? In the past I relied on the community to fix Google's shortcomings. It may just be that since this only seems to affect the pixel 2 and Android Auto that there are only a few people experiencing the issues I am. With only a few affected there may be no community attention.
Not sure if this is what you are talking about, but there is the openauto project and crankshaft:
https://github.com/f1xpl/openauto
https://github.com/htruong/crankshaft
Since his Nexus 6p is working very well the issue is on the phone end, not the HU. I am having similar issues with a Sony Z3 compact I am playing with to keep AAMirror on. However, other phones running latest version AA 3.1 have no issue at all - Note8 on Oreo, S8 on Oreo, S4mini on Lineage 14.1 all connect ASAP to my Suzuki HU.
Related
I have a moto x pure connected with chevy volt using android auto. It used to work perfect with the stock rom.
Recently I have installed the orionos custom rom, and the screen resolution in the car is totally wrong. I can only see the very top left portion of the screen, I think it is a screen resolution issue, but do not know how to solve it.
Any help is appreciated.
same issue
I have a brand new Skoda connected to an LG Optimus G updated to Android 6.0.1 and exactly the same issue. The screen is completeley screwed up and showing only the top left quarter of the screen way too large (huge fonts, etc.) Is there a way to fix this? Would even be good to know if this is a bug in the phone, in the car system or in the Android Auto app.
Anyone else facing this?
Is it possible you may have downloaded a 1024x600 rom instead of a 800x480?
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
I could fix my display issue by upgrading my phone to an Android 7 custom ROM.
duflez said:
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
Click to expand...
Click to collapse
Same thing here, HTC10, but with stock+magisk/xposed, same issue in Maps - until I saw this I thought that is because of one of xposed module. I cleanup the storage data several times, reinstalled aa also, disabled magisk/xposed, played with app settings xposed module in order to try to change the screen dp. Could not find the issue.
Interesting part is that on the same car but with different phone (moto x 2nd, xposed, same aa version, same google maps version) the Maps is displayed properly.
I have the same problem after updating my rom to a 1024x600. My unit was 800x480 and thats why the screen is cut off. What can i do?
In my case issue was related to Boost+ app "optimization", see this post https://forum.xda-developers.com/htc-10/help/android-auto-google-maps-issue-t3533388
Hi,
I have used Android auto with 3 phones with my current car (2017 Civic). Pixel 2 was running great, 6T runs great as well, but Note 9 is unusable. The animations are very slow, they never finish completely unless I touch the screen, and it just feels horribly laggy compared to the Pixel or 6T.
I've updated the Android auto app of course, factory reset the phone many times, tried with Oreo, with Pie Beta 1 and with Pie Beta 2 and same even if Beta 1/2 seem faster, they are still very slow.
Has anyone ran into the same problem before?
Saw this thread just now and have the exact same problem with my 17 civic and 10+
Heard it might work better if you change the usb cable- have you tried that?
I upgraded my phone from Galaxy S8 ( SM-G950F) to Galaxy Note 9 ( SM-N960F) and I noticed really poor performance when using Android Auto with my car head unit. It was OK when I was using Galaxy S8. AA ran fine on the phone (Note 9) itself. Below are some of the things I noticed when using AA with Note 9.
Every button touch up to 10 seconds to load and sometimes will not fully load (animation stuck halfway) until I touch another button or hold and drag the screen.
Scrolling is unusable (hit and miss), difficult to properly scroll and select the item I wanted.
Voice control is laggy and may take 5-6 seconds to respond to my voice command.
Audio worked fine (Call, Spotify & Navigation voice).
I have tested with AA version 3.x up to 4.1, all shown similar behavior. My current phone OS version is N960FXXS2CSCB, running Android 9 running OneUI 1.0. I have also tested pairing my head unit with other phones (Xiaomi Mi 8 & Huawei P20 Pro) using AA version 4.1 and they were working fine.
I contacted Samsung, they have no solution too. Only says they will bring the case to their internal team to take a look, no further update from then (it was 2 weeks ago).
I tried to find similar issue on the internet and below are some that I can find, none has any solution.
https://productforums.google.com/forum/#!msg/android-auto/_m3iTadSDx0/KAz0-iX0CQAJ
https://www.reddit.com/r/GalaxyS9/comments/99v0wf/anyone_else_having_issues_with_android_auto/
https://forum.xda-developers.com/showpost.php?p=77477202&postcount=8
Any of you faces similar issue? Any possible fix?
UPDATE: The latest update in May 2019 (Build N960FXXU2CSDE) fixed the problem
The damnedest thing just happened over the weekend. I recently had shoulder surgery and have been driving a secondary vehicle (Ford SUV) because it's easier to get in and out of than my 4 series coupe. Anyway, I upgraded to the Beta 11 once it was available a few weeks ago and had my phone synced to the SUV. Saturday, I went to take my BMW out for a wash as it has been sitting in my garage for about 5 weeks and apparently the Beta 11 BT crashes the IDrive, it puts it in a bootloop. I can connect my S20+ with no issues, my rarely used iPhone 11 Max Pro but not my DD, my Pixel 4XL. I doubled checked software updates for the IDrive system, there was a small one but did nothing to the bootloop issue.
Anyone else experiencing this issue
Anyone else got a pixel 5 and pixel stand?
If you enable s teen off when dark and DND mode, then put on stand on dark room the screen goes off. However as soon as your phone gets a notification the screen lights back up with the stands ambient display and stay on. Unless you lift the phone off the stand and then place it back on again but only until you get another notification.
The stands ambient display is quite bright and it's causing me to wake up super annoying.
Contacted Google they claming it's not an issue the pixel 5 works with the stand and sent a replacement but the replacement does the same thing also tried mine and GF pixel both do the same thing.
First pixel and I feel Google support just seems to blame the user.
I have wireless charging although not the pixel stand. I always just put phone into do not disturb mode at night. I know it doesn't answer your question but.....
Sent from my Pixel 5 using Tapatalk
same here
And here.
Same for me. Didn't realise it was notifications waking it up but have noticed it being on in the morning. It is also full brightness where my pixel 3 was nicely dimmed even if you set it to stay on....
My pixel 3 stays off if you set it to turn off though. Seems like a bug on the pixel 5 - sure they will fix it eventually.
Same here with pixel 5 ! And also using the pixel stand, charging wirelessly my phone seems to stuck it at 100% battery unless I restart the phone...
My phone can sit at 100% a few hours before it starts depleting - not sure if that's wireless charging related?
I contacted Google they said there is no bug and it's all rumors and the stand is faulty well one replacement later and 2 pixel 5s later the issue is still there told them this was software but they won't believe it.
I had the same problem. The only thing that I have found that will truly fix it is to disable the Pixel Stand app.
Sent from my Pixel 5 using XDA Labs
same issue here
I have the same issue and it drives me nuts. I will also complain to Google about it.
I do have 1 question for those that have this issue. Did you setup your phone as new or copy from an older device like I did. A lot of my settings were transferred to my Pixel 5 from my 4. I'm just wondering if that has anything to do with it or not.
I copied and had the issue. I started messing with Digital Wellbeing and eventually turned it off entirely and forgot/re set up the pixel stand to put the phone into DND and that worked, but let one notification through. I turned off everything but alarms and calls and I was not woken up last night.
The new fw update from Google seems to fix this ?