-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Android 13 update phone key not working
- Thread starter Midwst modlS
- Start date
I hope I get that update soon. Pixel 6 Pro the supposed flagship always gets the updates last. It may be unrelated but the door handles are not presenting when I walk up either. (no issue with phone as a key.) The car MSLR say car off when I get in. My previous MYP was very seamless. I know the cars have some differences but that is an unusual one.
That worked temporarily for , but now it's worse. I had to try that again and want able to get the phone too communicate with the car at all. Going to try again this afternoon.
First tried to reset key, which worked a day or two. Then didn't work. This morning tried resetting I couldn't get the phone to work at all. Uninstalled the app and tried again. App couldn't communicate (as a key) at all. Bluetooth for music continued to work and the app can unlock the doors, etc. But as a key no go.
I was on advanced Tesla updates. I turned that off, so maybe that will help if get a stable release. And Android's next update? Very frustrated.
Time for a key fob?
Ah, yes, I also rebooted and it worked a bit. I'll try that again, if I can get the phone reconnected. Will do that before trying to reconnect since I can't even do that right now. Agh!
Yes, My wife and I both have Pixel 5 phones and updated to Android 13, and our phones appear to lose bluetooth connectivity with the car. We have only seen the car when we get ready to leave home after the car has sat overnight. To fix the problem, we just go into the phone settings / Connected devices / Connection preferences / Bluetooth and then disable and re-enable "Use Bluetooth". I have not found a permanent fix yet.
trying this now - will report back after update.
I hate how this system update is not triggered when you go play store for update checks :|
Toggle didn't work for me. Phone updated Thursday and all is well now. That was so frustrating.
In my case (Pixel 4a 5G with Model Y), I have found that the Tesla process must be running or it won't work, and if I set the Tesla app battery usage setting to Unrestricted as described above, it stays running (may need to launch the app after restart). You can see running processes in System > Developer Options if enabled, otherwise you can see if the Tesla app is running by swiping down twice on the status bar and tapping the bottom bar which appears when at least 1 app is running in the background. If you don't want to do that, you can run the Tesla app when you need to unlock.
Sometimes, even if the Tesla process is running, the connection fails (per the bug linked to previously here) and toggling Bluetooth off/on restarts the Bluetooth stack and generally fixes the problem. Often you have to toggle Bluetooth after starting the Tesla process, whether after startup or after the system stopped it in the background.
If the Tesla process isn't running, toggling Bluetooth won't fix the problem.
Sometimes, even if the Tesla process is running, the connection fails (per the bug linked to previously here) and toggling Bluetooth off/on restarts the Bluetooth stack and generally fixes the problem. Often you have to toggle Bluetooth after starting the Tesla process, whether after startup or after the system stopped it in the background.
If the Tesla process isn't running, toggling Bluetooth won't fix the problem.
See below on the new android update release notes. I updated this morning and so far so good. Hopefully it is a fix.
I still get really old texts that pop up as notifications on the Tesla but that is for another thread another day....
Attachments
I don't think the issue mentioned is the problem some people are having.
I updated my Pixel 6 to Android 13, and had to reinstall it as a lock, using the method I mentioned earlier. Since that one time, it has worked perfectly every time, without any need to reboot, reinstall, disable/enable anything like bluetooth, etc. Every time I walk up to the car, it unlocks, and locks when I leave. So, I say it must be something else causing problems, probably user error. It's a little complicated to uninstall fully before reinstalling - in fact, it's hard enough to install the first time if you've never done it before. But after doing the uninstall/reinstall half a dozen times on various phones due to installing various versions of the Tesla app, I've got it down pretty well.
I updated my Pixel 6 to Android 13, and had to reinstall it as a lock, using the method I mentioned earlier. Since that one time, it has worked perfectly every time, without any need to reboot, reinstall, disable/enable anything like bluetooth, etc. Every time I walk up to the car, it unlocks, and locks when I leave. So, I say it must be something else causing problems, probably user error. It's a little complicated to uninstall fully before reinstalling - in fact, it's hard enough to install the first time if you've never done it before. But after doing the uninstall/reinstall half a dozen times on various phones due to installing various versions of the Tesla app, I've got it down pretty well.
lulu2
Model YLR•5 Seat•FSD•Blue/black
I just realized I too have been leaving my car unlocked. I am now trying to reconnect the phone key after removing and reinstalling app and it fails to connect. Bluetooth will connect, but the car, key card and phone will not communicate. Who do I escalate this to? Google? (Have a Pixel 4a (5G).
Similar threads
