Develop Bugs

Phone crashes in car dock on AOSP ROMs

Here's the deal. I have an iBolt car dock (that specific really shouldn't matter) and Tasker profiles to turn on GPS, Bluetooth, etc while my phone is plugged in. Been like that for months. Up until about a week and half to two weeks ago, my phone app would crash when trying to receive a call while in said dock. The message I got was "unfortunately, the process com.android.phone has stopped". When I noticed, I was running Carbon. I clean flashed the nightly I was on and same result. I then tried Deviant, Slim, JellyBeer, PAC-man, etc. All of them gave the same result. Same wipe procedure for all of them. Same apps as I've always had. I then flashed AOKP M1 and everything worked. Then I tried Task's AOKP. Same thing. Everything worked. I don't get it. I posted the issue without a logcat (as pulling one of those while driving is a no no) in those respective dev's threads but it seems they don't know what's going on with everyone else. Hence, this thread. If you are running any of the ROMs I mention and experienced the same problem, post here. If you have logcats (ballsy), even better. I figure this would be the best way for all the devs of those ROMs to see what is happening and so the problem can be nailed down.

I'm also using an iBolt dock. Posted this in Xone Deviant thread: http://forum.xda-developers.com/showthread.php?t=2215840&page=55
itsmikeramsay said:
Not 100% sure bro, haven't been able to test it...
Click to expand...
Click to collapse
CrackerTeg said:
@ itsmikeramsay. Did you see this a few pages back? Thoughts?
Click to expand...
Click to collapse
Same here. Phone ui crashes when call is initiated but call goes through. Catlog attached.

Glad to see someone else feels my frustration with this. I battle this issue all the time. I have 2 iBolt docks(the regular one & the pro dock) & have had this issue with both. If not the not the incoming calls freezing the phone, its the phone rebooting when pluging it in, or the dev will update the rom and the usb audio doesn't work at all. I'll give task's AOKP a try to see how things with it. I was a huge fan his roms in the past up untill an update and the usb audio stopped working. In that situation, I usual just try a couple different roms untill one works. But then, the incoming issue happens or it reboots when docked and I feel like throwing my phone out the window
btw, i got an email today about the prodock cables being shipped. I've been using the one that came with the first iBolt
If my wallet would allow it, I would buy a headunit with bluetooth and use a NFC chip to put the phone in dock mode and not have this issue regardless of what rom i'm running. but my wallet stays empty
---------- Post added at 01:16 PM ---------- Previous post was at 12:41 PM ----------
I'm pretty sure the usb audio out working on some roms/updates vs. not working others is due to something in the kernel. Ex. I flashed the latest deviant xone update(2.0) and the didn't work. So I reflashed the previous version (1.0 stableish) and the audio works.
I hope this gets resolved 'cause I enjoy listening to podcasts & playing ingress during my commute only to have it ruined by a phone call that freezes my phone, rebooting booting and listening to my wife "quit ignoring my phone calls"
Sent from my SGH-I747 using xda premium

Interesting. My complaint has nothing to do with the audio out portion of it as I use my phone for browsing and as a phone. I have my tablet or iPod for the music in my car. So the complaint has nothing really to do with the iBolt but the phone being docked and not being able to use the actual phone function. If the usb audio gets fixed, bonus but I'm much more concerned with the primary function of this device.

After doing a bit of research, it seems that samsung didn't implement call audio through the dock connector. I know this is not your direct complaint BUT if you are using the ibolt cable that has the dock resistor( that tells the phone to go in dock mode) and the Rom/kernel is trying to route the audio via the usb than the phone may be getting confused. I think the solution to your issue, since your not concerned about audio out, is to replace the supplied cable with a standard data/charging cable. I haven't tested this theory, but i'm pretty sure taking the dock resistor out of the equation will fix the phone freezing when receiving a call.
I did have a rom installed at one point that had audio out working AND didn't freeze on incoming BUT had an unrelated bug that drove me nuts, so flashed another rom. It's too bad I can recall which rom and which release it was

Thing is, I have a Parrot bluetooth adapter that my calls go through. They don't go through the dock at all. I have a tasker profile that triggers the phone to go into car mode with Google's no longer supported Car dock app when the device is plugged in. It also turns on bluetooth, GPS, blah blah. Like I said in the OP, everything was just peachy up until two weeks ago where something in those ROMs got borked. Either way, I'm now running Carbon's latest and the issue is gone. Whatever got messed up is now fixed. I wish I knew what it was tbh but I can't read git.

I would like to add my two cents.
I too have an iBolt dock for SGS3, and an after-market radio with bluetooth.
I have tried several ROMs (CM stable, LiquidSmooth, ParanoidAndroid), and all of them exhibit the same behavior:
Going into the docked mode is flakey at best. 90% of the time the phone doesn't recognize it has been docked.
Now comes the "best" part: on disconnect from the dock the phone's bluetooth stack apparently crashes. The bluetooth connection gets immediately lost, and the phone's bluetooth status is stuck in 'ON' position. After that there is no way to turn the phone's bluetooth 'OFF' and back 'ON'. The only way to restore is to reboot the phone.
I haven't tried to pull the logs from the phone yet, but it may be possible if I take the dock home and try to repro the condition.
Not asking for answers, just voicing my frustration hoping to draw dev's attention to the problem.

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.

I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.

nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk

thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).

I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.

millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.

I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.

Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.

Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk

I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently

I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.

I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!

Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!

t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!

Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.

BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.

I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.

Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.

I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol

Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.

Does Oreo update fix all these issues ?

I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?

The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again

Well, sincerely I have been with this device for 1 day, I will see if it brings problems, although for now I have not found an anomaly.

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
I haven't had those problems, but clicking the down arrow on the mobile data quick settings crashes, every so often my phone freezes and reboots (though less than Nougat), and there's the multitouch bug which gets fixed in the May security patch (which as far as i know is not out yet).

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.

waiflih said:
The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again
Click to expand...
Click to collapse
The issue itself is nothing to do with covering the light sensor. I've read on here and on Razer Insider forum that it is heat/power related and that lowers the screen brightness because it consumes too much power. A lot of people get this problem and a lot dont know about it too.
ThatGuy94 said:
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.
Click to expand...
Click to collapse
Its not my car radio. I've tried on 3 different car radio's and a Bluetooth portable speaker, I get this problem with literally every device i connect to. I still have not had a fix or a solution. Only thing Razer suggests every time is a factory reset which did not change anything.

This thing on max settings according to Ampere is pulling nearly 1.5amps from the battery with brightness at full and all settings maxed
Sent from my Phone using Tapatalk

Question Android Auto

Is Android Auto working for anyone? No matter if I connect it to my car or use wireless AA, it starts and disconnects right away and just keeps doing that over and over. I haven't been able to get it to work with anything I found online with past Samsung phones that had connection issues. Any help with this would be greatly appreciated.

Same issue here with my 2019 volvo xc60. Car briefly shows it's going to connect then says "reconnect device". Phone will display the initial setup screen but when you hit next it flickers something and vanishes. Using cable.
All updates installed...

Working just fine in my iX3 wireless. Not tried wired, but then never do. I am running 8.x.x beta though, might be worth trying that

Found The beta and sideloaded the update. No luck, same problem.
This really sucks.

Broken here too. I'm using a JVC head unit in my truck. Works great with my S22 Ultra, Z Fold3 and iPhone 13 Pro Max.

I've tried everything under the sun. No luck. Even reset network connections in case it was a corruption from migration.

Same here, 2021 Tacoma. Fold 2 worked just fine, now nothing.

AA desperately needs an update in general.
iOS carplay is so much better.
BUT! Not working at all is very, very bad.
Early users also reporting July security patch too so perhaps an update is in order. They usually smooth out new devices (aka shakedown) after a few months so fingers crossed.

Just rec'd my G4F today, and also nada for me in my 2015 Mazda 3.
G3F works like a charm. This sucks.

How the fck could Samsung deliver a phone that has broken aa? WTF

Also broken on both my kenwood radios. fold 2 still working like a champ

No issue in france with my peugeot 208

Kia Sportage no issues....

No issue on e208

It's like the AA crashes before it finishes authorizing the permissions for the vehicle. I may try getting everything set up to pull ADB logs this afternoon and see if there's any clues there.

Solved it!
I went into apps, Android Auto, cleared cache + data (again) then I went to the battery option for Android Auto and set it to "Unrestricted". I'd already gone under the central battery options and set it to never sleep for Android Auto previously but that alone didn't do it.
Paired perfectly on next connection. After that I just paired it with my wireless AA dongle and everything is fine with the world again.

AA working fine with my GF4 + 2022 BMW M3.

cybermage1 said:
Solved it!
I went into apps, Android Auto, cleared cache + data (again) then I went to the battery option for Android Auto and set it to "Unrestricted". I'd already gone under the central battery options and set it to never sleep for Android Auto previously but that alone didn't do it.
Paired perfectly on next connection. After that I just paired it with my wireless AA dongle and everything is fine with the world again.
Click to expand...
Click to collapse
Hello,
I just wanted to let you know that it worked for me. I was having the same issue. I have a 2020 Hyundai Palisade with the new Fold 4.. Thanks for posting the solution!!!!
Dave

I can confirm that resetting caches and data for Play Services a Play Store did the trick. Also AAWireless is working now.

I was going to reply and tell you all that if you have uploaded apps from the old phone you had to the new Z Fold 4 , there will be some apps that will require a clean start and date and cache probably will require it, especially AA. Getting my phone today (FedEx say it is on the truck to be delivered) and here is my part I am re-thinking the wireless AA.. I drive an Audi A6 with an after market module for Car Play and AA.. That worked fine with my S20+ so far. The screen in the car is not a touch screen , 8.5" lower resolution than the fold 4. I got the new car Qi mount for the fold 4 installed last night and it looks , even with the S20+ much more crisp and clean, not to mention a touch screen. I bet when the Z Fold 4 arrives today and I will have it placed in the mount open, the 950NIT , hi-res , will make my car screen look bad even more.. I truly think of removing AA from my phone, not connecting to the car although I can, connect only Bluetooth to have Spotify/phone use the speakers, and turn off the car's screen.. For less than $50 good car mount, WHY would I need AA? Controlling from the steering wheel ? Meh, I use Google Voice anyways.. Your thoughts, as Z Fold 4 7.6" hi res screen owners? I'll share my comparison between the two options after 2-3 days of driving around with an open phone, vs. Car screen..

Question Poco F5 Android Auto does not work

Poco F5
MIUI 14.0.6 TMREUXM
Android Auto 9.4.631624
Car: Škoda Scala
Poco F3 worked flawlessly. F5 fails to connect. Tried different cables.
It correctly detects the phone on the car and prompts me to connect via AA or Mirrorlink.
On the phone, USB connectivity menu appears. I select data transfer / Android Auto.
And then the car tells me it failed.
Is this known? Is is a weird issue with car compatibility?
Any way to make it work by messing with settings?

Seems Android Auto works on EU Rom or other non-official ROMs. Marble doesn't have proper certificate so car's audio component cannot accept pairing and fails to establish a connection in wired mode. It is probably the reason it fails in wireless mode too.

What's "marble"?
Is this a bug that could be fixed by an update or deliberate?
I need to figure out if I should return this phone, as this is serious.

I'm having the same problem.

I am having the same problem. I tried with 3 different cables but the result did not change. I'm thinking of returning it. Incredible problem!!
My car Skoda Scala 2020

I've seen multiple reports associated with android auto,. i have poco f4 gt and getting the same problem right after I upgraded my phone to miui 14 and android 13. they are saying that it's from android 13 version cause all of them getting the issue has Android 13 ,, even in samsung phones and other brands, they are getting the same issue. The only similarity that I noticed is that they all have android 13 on their phone.

I have no experience with the stock rom.
I'm using Xiaomi EU and Android Auto works both wired and wireless mode. Even better than my previous Flip 3

bellissimo.io said:
I have no experience with the stock rom.
I'm using Xiaomi EU and Android Auto works both wired and wireless mode. Even better than my previous Flip 3
Click to expand...
Click to collapse
good to know tho,, so aside from android 13 there might be another factor that affects android auto with most devices.

Got a generic reply from support, so it seems they are not really familiar with this or interested.
Please reinstall the latest update package to eliminate possible errors during installation. Settings - About phone - MIUI LOGO - 3 items - Download last update package.
Next, you can also check the functionality of the device in Safe Mode. To enable Safe Mode, you need to turn off your smartphone first, then press the Power Button and Volume Plus at the same time, once the Recovery Menu appears let go of the buttons. In the recovery menu, please select the Safe Mode option.
All third-party apps are disabled in Safe Mode and will not be displayed. If the device works fine, please reboot to exit Safe Mode and boot the device in "Normal Mode". Please then uninstall the last three apps that were installed and check the functionality again.
If the problem persists, reset the device to factory settings. Please note that before you factory reset the device, please backup your data first, otherwise all your data (pictures, videos, music, apps, etc.) will be lost.
Click to expand...
Click to collapse

I might finally consider custom rom, most likely xiaomi.eu, but I am really hesitant to do this.
There is a lot of uncertainty regarding warranty, and everything working, and conflicting reports about battery life and bugs. Most are seemingly happy, but there are lso reports of it not really working that well.
Or I might return it and wait and see what Nord 3 is priced like.

I know you've said you tried different cables. I was having connectivity issues with Android Auto when my previous phone (Poco F1) had no issues whatsoever.
I've been using an Amazon Basics USB 3.1 cable for a few days now and touch wood, everything is fine. Perhaps the Poco F5 is just very particular about what cables it uses.

Hm..
I suppose it's easier to try with that then to return the phone, though my current cable is 90 degree on one end for practical reasons, and I want a short one.
And some people online are reporting that it works on one car and does not on another, but I don't remember they said it was tested with the same cable.
But I could try. This is like a MUST feature. I would not buy a car without it, let alone a phone.
Though my car is C plug, so I have to try with random cables :/

Android Auto is definitely possible with the proper software. This is definitely a software issue and not a hardware issue. I will revisit this thread once a stable solution (not via custom rom) has been applied. Marble devices (Poco F5/Redmi Note 12 Turbo) should be able to use Android Auto starting from Android 13. Ig we just need to provide some feedback via SocMed so we can be heard.

Same problem with Skoda and Poco f5 pro miui14 latest.
Any known solution to come or throw this phone away ?

You can sell it, don't throw it away.
I might get the Nord 3 if they have an early sale. Though oneplus is allegedly prone to bugs. So I can't be smart about this, just reactionary.

Did you guys try a new cable? I never had problems with my F5 but as I wrote before it happened in the past with another phone and the solution was 1) change the cable 2) unpair the phone/car and pair them again from scratch

It's not the cable. I tried multiple different C-C cables, 2.0 and 3.1. I only have not tried 3.2.
It could be that for some reason it's not standard spec USB, so it does not work with all infotainment systems. There are a few posts about Škoda/VW specifically, but also Honda and some others. My car is USB-C, so maybe for some reason it only works in cars with USB-A?
It could also be MIU14 bug, as there are multiple posts about Xiaomi phones being upgraded to MIUI14 and having these issues, Poco F3 included, and I have that one, works fine with MIUI13. But it's again not all users of the same model, just some.
In my case, it definitely seems to be USB related, because the phone does charge, but keeps dropping connection. When I am charging, it does not. I just remembered I have not yet tried connecting to my laptop and see if it drops connection there, that would be an easy test.
My F3, MIUI13/12, works flawlessly.
I sent my to service, as there was also a post where someone sent a Xiaomi phone to service with the same symptoms and allegedly they fixed it.
It is frustrating to say the least, as it is a crucial functionality for me.
Unfortunately, I don't have any other convenient car I can try it on. Everyone I know has older cars, no AA :/
I mean some do, but nobody where I can try it conveniently.

Now I'm kinda optimistic, becuse the phone also can't be connected to a PC. Nothing happens. nd it also keeps reconnecting.
nd, when I was switching stuff over via cable from my F3, this did not work, so I had to use wireless option.
I say optimistic, because it appears it is clearly an issue with USB, so service might be able to solve it.