ASOP / Lineage Android Auto Setup Issues - Samsung Galaxy Note 8 Questions and Answers

Hope someone can help.
I have no issues connect my Note 8 to my Android Auto device in the car using a Samsung ROM. However, if I try the same with either ASOP or Lineage ROM I get through to set up to the point that assistant page pops up then there is another page requesting something. But it crashes everytime. It shows connected devices in the android auto app but it doesn't connect. Does anyone else have this issue or could help me?

Related

Android Auto not working

I have an issue with Android Auto refusing to start. I always get an error: "Something went wrong: Google services doesn't seem to be working at the moment" and the app closes.
Stock, locked, global ROM pie.
Any idea on how to get it working? Thank you!
Problem solved. You need to disable dual apps.
In my case it does not work at all... I connect the phone, start android auto (and it starts on the phonefine, no problems) but nothing happens on the car side. I don't have dual apps enabled. Tried with USB debugging on, but still nothing. Running latest MIUI 10.2.1.0. Anyone can help? With my previous umidigi phone it worked (most times). It's like neither can see the other connected...

Android 10 - Android Auto "this internet connection isn't reliable at the moment"

Android 10 - Android Auto "this internet connection isn't reliable at the moment"
EDIT - According to THIS Android Auto support thread it's been reported and is being worked on.
-----
I've got an AT&T locked Note 9 (SM-N960U). I recently updated to Android 10 via Odin using the CCT variant of DTA4 build. The update worked fine but afterwards I noticed that if I try to compose a message (new message or reply, Hangouts or SMS) in Android Auto it will work OK up to the "do you want to send it or change it" part and then it IMMEDIATELY gives a quick beep and says "this internet connection isn't reliable at the moment". The signal is fine from all I can see.
I've tried clearing cache on Play services and Android Auto with no luck. Today I went all in and did a factory reset in case it was an issue with the upgrade vs a fresh install. No luck, same error. I can use Assistant on the phone to compose/send messages successfully. I've also tried being on wifi vs being on a strong 4G LTE signal, same failure.
I found a mention HERE of someone solving it by removing GBoard. I didn't have that installed, but I did try disabling Google Voice Input under the keyboard section to no avail.
For grins I tried posting at the AA help site HERE but I figured this audience might be better equipped to help. Any ideas?
If it matters, the car is a 2018 Volvo S90, but there's been no changes to the car's software in this time so I don't suspect is as the cause.
Thanks!

Skype and Teamviewer issues with Samsung Tablets running Android 10 (T515+T505)

Hi Folks,
I have been using a Samsung Galaxy Tab A 10.1 (SM-T515) to connect with an elderly relative. I have Teamviewer Host installed for remote access and Skype set to auto-answer. It was all working fine until the tablet was stupidly upgraded to Android 10. Now Skype will only auto-answer if the app is open and in the foreground. Otherwise, it just shows up with the normal notification of an incoming call. As for Teamviewer it mostly now connects with a back screen.
I then purchased a new Tablet, Samsung TAB A7 10.4 (SM-T505) to set up at home and swap with the other one. However, I get the same issues. I've been on to both Samsung and Skype help both in terms of the community and company support. Skype at least seem to be trying to find out what the issue is. Samsung just gives and blames Skype/Teamviewer. There was a post in the Samsung community of someone else with a similar Teamviewer issue on a Tab A 8.4 which was resolved by an update with the Feb security fix. The TAB A7 I have has the December security update. Although I can't find any reference to the issue with skype auto answering as most of the posts are about trying to stop it doing that.
Before I go and try and get a non-Samsung tablet I just wanted to check if this was a wider issue or just with these Samsung Android 10 devices. While it is obviously getting expensive in useless tablets the bigger issue is restoring a simple connection with my relative during this time so any and all help or advice would be most graciously received.
N
Similar issue here,
Cannot remote view Samsung a7 tab if it locks
Tried to set up the pin and password in team viewer yet all I get is a blank screen until I unlock at the source
I assume Skype cannot auto answer until it is unlocked... have you tried this then called the device? If it works then samsung security is the issue
If we can set these apps as device administrators (like with antivirus) it may fix this, but Samsung doesn't allow us to set them. Possibly rooting would fix this problem?
Custom OS otherwise, take Samsung software out of the equation without needing to buy another tab
Hi There,
Thanks for your response. Ultimately the Teamviewer issue seemed to be sorted by an update. Strangely it would work in portrait mode but not in landscape (or the other way round). I turned off the screen lock so maybe that is why it worked for me.
However, after some back and forth with Microsoft Skype support they have acknowledged that this is now a known issue is a known problem with Skype on Android 11. I have since found out that the windows desktop version of skype also has the same problem. They said they are working on it but who knows. Have to say the skype support was at least pretty responsive and kept me informed through the process. Which was positive but ultimately they didn't resolve the issue.
n

Question About Android auto

Does anyone have a workaround about how to connect androidauto on MIUI?
I plugin the cable only got a blackscreen (the phone screen freeze as well)
shijiav said:
Does anyone have a workaround about how to connect androidauto on MIUI?
I plugin the cable only got a blackscreen (the phone screen freeze as well)
Click to expand...
Click to collapse
I don't get a black screen at all, instead I get an error message about "no installed apps work with this usb accessory".
deathernater said:
I don't get a black screen at all, instead I get an error message about "no installed apps work with this usb accessory".
Click to expand...
Click to collapse
go to settings to allow android auto to autostart, you will get rid of the "no installed apps work with this usb accessory"
shijiav said:
go to settings to allow android auto to autostart, you will get rid of the "no installed apps work with this usb accessory"
Click to expand...
Click to collapse
Just tried that didn't work same error. Even reinstalled to see. I know auto start if disabled can cause notification missed issues on other apps.
deathernater said:
Just tried that didn't work same error. Even reinstalled to see. I know auto start if disabled can cause notification missed issues on other apps.
Click to expand...
Click to collapse
initially I have the same "no installed apps work with this usb accessory" as well, but all I do is opened up all the permission for android auto and other google services, and I got a black screen during connection.
What I notice is on CN version even if you allow it to auto-start, and the phone knows that(it pops a notice saying do you want to start android auto?) the android auto does not response to the start command it seems result in a black screen.
I'll try the permissions can you let me know which apps aside from Android Auto you flipped the permissions for? Let me try to get to the same spot as you.
deathernater said:
I'll try the permissions can you let me know which apps aside from Android Auto you flipped the permissions for? Let me try to get to the same spot as you.
Click to expand...
Click to collapse
I spent quite a lot of time on this. There's something broken on the Chinise firmware. I also got the pop up and then phone freezes. I tried beta 12.5.2 and still the same issues. I don't know if 12.5.3 fixed this, since I move to the global ROM - where Android Auto works just fine.
Also, I tried many many apk versions of Android Auto with the same luck...
deathernater said:
I'll try the permissions can you let me know which apps aside from Android Auto you flipped the permissions for? Let me try to get to the same spot as you.
Click to expand...
Click to collapse
I can`t remember tbh, maybe the google app and the android auto app, also I enabled fullscreen mode on those apps
YoSoyCarlosG said:
I spent quite a lot of time on this. There's something broken on the Chinise firmware. I also got the pop up and then phone freezes. I tried beta 12.5.2 and still the same issues. I don't know if 12.5.3 fixed this, since I move to the global ROM - where Android Auto works just fine.
Also, I tried many many apk versions of Android Auto with the same luck...
Click to expand...
Click to collapse
I have encountered this in other phones like oneplus 8 pro CN version ROM, My guess is that all the CN ROM lacks a small crucial permission for android auto to start normally during the connection, but the thing is we don`t know what it is.
Well even without the Android Auto installed I get that USB message so I guess it didn't make a difference installed or not permission and what not. Something is just not registering with the phone.
What are the draw backs with a global rom and also does that enable smart lock? That is something else that seems to be missing from MIUI.
deathernater said:
Well even without the Android Auto installed I get that USB message so I guess it didn't make a difference installed or not permission and what not. Something is just not registering with the phone.
What are the draw backs with a global rom and also does that enable smart lock? That is something else that seems to be missing from MIUI.
Click to expand...
Click to collapse
Android auto wont work on CN rom but on the EU rom it works just as you would expect, also wireless Auto works as well.
deathernater said:
I don't get a black screen at all, instead I get an error message about "no installed apps work with this usb accessory".
Click to expand...
Click to collapse
I am facing the same issue. Did you find a resolution for it?
don't forget to use original usb c cable (only one works with me)
I faced a bunch of issues too.
I had to do two things:
1) change my crappy USB-c cable
2) go to apps, manage apps, search for Android auto, then clear settings for Android auto: first cache and then all.
After I did that, I was greeted by the android auto setup and all work out!
Hope this helps!
Ps: I'm on 12.5.4 global
same issue with K30 Ultra China rom. i got this issue after upgrading to MIUI 12.5.4 from 12.0.20. every worked in last ROM but appeared right after i upgraded to 12.5.4. Has anyone fixed it?
Without the Android Auto installed I get that USB message so I guess it didn't make a difference installed or not permission and what not. If your phone is facing issues or slowing down because of Android Auto then you can disable Android auto. That is something else that seems to be missing from MIUI.
I'm getting this issue with my Mi 10 Ultra (Chinese version) MIUI 12.5.6.0
Any practical fix so far (without the need to flash any other rom)? This is really annoying!
If anyone finds this on google, clearing play services data solved the issue for me.
shijiav said:
go to settings to allow android auto to autostart, you will get rid of the "no installed apps work with this usb accessory"
Click to expand...
Click to collapse
Switch on Hotspot on your phone, connect your car to your network and update the system/check for updates. Once updates are complete, you should be able to connect

Question Android Auto Not Connecting w/ Android 12

I have two OP's now, an 8T and 10 Pro, both on Android 12. While the 10 Pro came with 12, the 8T was just recently upgraded.
Neither of them will start Android Auto without me first unlocking the phone. This problem only started on the 8T after the 12 upgrade and then the minor update that followed.
I noticed when I unlock my phones the popup to specify what type of USB connection pops up, (charge only, file transfer, etc) - so wondering if this is part of the problem? I tried setting the default to file transfer which is the option for Android Auto, but I still have to unlock the phone every single time I connect to my car.
Did something change between 11 and 12 that would make this happen? Is this a bug?
Does anyone else have this issue, or a resolution idea?
TYIA
Try disabling the screensaver on your phone. I had similar issues on my OnePlus 7Pro, though not on Android 12. After I disabled the screensaver, it connected fine.
gocoogs said:
Try disabling the screensaver on your phone. I had similar issues on my OnePlus 7Pro, though not on Android 12. After I disabled the screensaver, it connected fine.
Click to expand...
Click to collapse
Thanks but I'm not sure what you mean by screensaver? Oxygen OS, at least, doesn't have anything like that in settings. We have a "lock screen" but I need security on my phone so I can't disable that.
I did find a "trusted devices" section where your phone will remain unlocked when it detects things like a location or connected device. I added my car to this, but it still doesn't work. "Trusted Devices" still requires you to unlock phone once before it works properly once connected, just like my Android Auto is doing
I went into developer options and set the default USB configuration to charging/Android Auto. It still shows when you plug it in but my phone still works with the screen off. Also, check the settings in AA as there is one which you have to toggle for starting Android Auto when the phone is locked.

Categories

Resources