Database Users

[Q] N4 USB stopped working yesterday

I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.

I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this

BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course

Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...

BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.

Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists

When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta

Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4

tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!

Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4

Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.

tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post

Fast charging not working and phone charging extremely slow

So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?

topaz330 said:
So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?
Click to expand...
Click to collapse
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.

Outbreak444 said:
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.
Click to expand...
Click to collapse
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.

topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk

amorrn said:
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Nope not rooted.

topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
topaz330 said:
Nope not rooted.
Click to expand...
Click to collapse
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.

Outbreak444 said:
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.
Click to expand...
Click to collapse
yep, its the stock cable. I plugged in my wifes s6 on it and it worked perfectly.

Anyway to flash stock rom without the use of odin or usb?

Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.

Action123 said:
Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.
Click to expand...
Click to collapse
so verizon exchanged it via warranty no issues. They just checked to see if it was rooted whichi it wasn't and confirmed that the usb port was defective. All is well in the world again!

I was having this problem about 4 weeks ago. I tried everything but nothing worked. Rebooting would help for a bit then it would slow down to a crawl when I tried to wireless charge. Then I recalled I had taken an update recently and hadn't done a factory reset. I had traditionally always done one because in the past android was always buggy if you didn't. I thought android was supposed to have gotten better about taking updates without needing a FR so I had decided to do one without and had no problems for a while so forgot about it. When I realised that was the issue I saved as much as I could with Helium (normally I would use Titanium but I don't like the root method so for now have remained stock) and performed a FR. Since then I have had no issues and wireless charging works as expected.
TLDR: Backup everything and perform a factory reset.
Sent from my SM-P600 using XDA-Developers mobile app

Android Auto error 7

Anyone having issues with Android auto? I keep getting an error 7 my cars security doesn't meet the requirements for..... I've reset my phone already and made sure my navigation was up to date.
Any suggestions?

Brandon.gold said:
Anyone having issues with Android auto? I keep getting an error 7 my cars security doesn't meet the requirements for..... I've reset my phone already and made sure my navigation was up to date.
Any suggestions?
Click to expand...
Click to collapse
What kind of car?
Sent from my SM-G955U using Tapatalk

Is it factory or after-market radio? I'm waiting on my S8 to arrive today...Android Auto is one thing I've been wondering about...whether it's going to screw up or not with the new phone. Mine is an after-market (Pioneer).

I'll be keeping an eye on this thread as well. I have the Pioneer AVH-4200NEX and I have come to rely on AA with my S7E, it didn't work at first a while back, but after an (phone) update it works fine. I can't see going without it at this point, very useful. I'll chime in when I get my S8+ (hopefully tomorrow) if I have any issues.

physicsguymatt said:
I'll be keeping an eye on this thread as well. I have the Pioneer AVH-4200NEX and I have come to rely on AA with my S7E, it didn't work at first a while back, but after an (phone) update it works fine. I can't see going without it at this point, very useful. I'll chime in when I get my S8+ (hopefully tomorrow) if I have any issues.
Click to expand...
Click to collapse
Same here...that's exactly what I have and I've gotten so used to it, it's a must have for my new phone to work with it! My S8 should be arriving any minute and top of my priority list is connecting it to my car. I'll keep you posted.

Works fine for me. Hyundai with AVN 4.0 (latest) stock head unit. Remember too that if you used Smart Switch to set up your phone you need to uninstall and reinstall all your AA dependent apps. AA doesn't see them for some reason when they're copied vs. installed from scratch.

physicsguymatt said:
I'll be keeping an eye on this thread as well. I have the Pioneer AVH-4200NEX and I have come to rely on AA with my S7E, it didn't work at first a while back, but after an (phone) update it works fine. I can't see going without it at this point, very useful. I'll chime in when I get my S8+ (hopefully tomorrow) if I have any issues.
Click to expand...
Click to collapse
It worked flawlessly on my way home from work!

Finally figured it out. Turns out the play services app need updating and wouldn't update unless connected to Wi-Fi. All works now!

Also having some issues it seems with android auto, s8, and connection to my car.
I love having new technology but I wish things like this were already hammered out.

EnCincy said:
Also having some issues it seems with android auto, s8, and connection to my car.
I love having new technology but I wish things like this were already hammered out.
Click to expand...
Click to collapse
Did you try uninstalling Android Auto app? I uninstalled mine then went plug it up in my car and let it prompt me to download everything and allow permissions, etc. I had to put my emergency brake on and go through the whole nine yards, but it worked perfectly once all done.

hlanclos said:
Did you try uninstalling Android Auto app? I uninstalled mine then went plug it up in my car and let it prompt me to download everything and allow permissions, etc. I had to put my emergency brake on and go through the whole nine yards, but it worked perfectly once all done.
Click to expand...
Click to collapse
Yes. This was the first step I did. Uninstalled AA, Spotify, and then installed AA. Once done with that I went into android auto and downloaded Spotify. Still not listed as an option. Also tried another USB cord just for good measure.

Finally got to use android auto this morning. I used a micro USB to USB C adapter I had bought earlier. Everything ran perfectly, I didn't need to install anything, spotify worked, everything so far exactly as before with no hiccups.
Sent from my SM-G955U using XDA-Developers Legacy app

hlanclos said:
Did you try uninstalling Android Auto app? I uninstalled mine then went plug it up in my car and let it prompt me to download everything and allow permissions, etc. I had to put my emergency brake on and go through the whole nine yards, but it worked perfectly once all done.
Click to expand...
Click to collapse
I had to do this twice to get it working right lol.
But now... Sometimes it tells me Spotify isn't working and has a spinning icon. I have to restart the phone and car to remedy. This has been happening since android 7 came out to update on my devices. S7Edge before and now the S8

I hadn't realized it till over the weekend that my iHeart Radio wasn't appearing in my music choice either. I uninstalled and re-installed iHeart Radio app to see if that helped but it didn't. Then suddenly I get in my car this morning and it's working! IDK what the deal is.

Android auto, s8, google maps
Somebody please help. 2016 jeep wrangled. When I TRY to use Google maps nav as soon as my s8+ display goes black I get the searching for GPS. So frustrating. Any advice??? Please and thank you

Waze in Android auto issues

Anyone have so many problems as me when using Waze in Android auto?
1) street names text is so pixelated and not crisp/smooth
2) freezing
3) sometime it doesn't even update the location and blank map
Etc..

Are you using a Oneplus 6T? I just got off the phone with Oneplus support because I cannot get Android Auto to work at all.

I'm in similar boat too.
Android Auto is messed up on this phone.
OnePlus has been of no help whatsoever.
I have been providing them logs they requested. No reply from them.

nictabor said:
Are you using a Oneplus 6T? I just got off the phone with Oneplus support because I cannot get Android Auto to work at all.
Click to expand...
Click to collapse
Yes 6T international ver..

damn... sucks seeing all of you having issues with AA
works great for me... I'm on the latest 9.0.11 with root and twrp and haven't seen any problems

I ranted about this on Twitter. Probably not gonna make a difference, but did it anyway..
https://twitter.com/iamshahaz/status/1081590759935987713?s=19

I posted on another thread, but I'll update this one too. I have an almost clean install as my phone was only hours old. I upgraded to the latest oxygen build (non-beta) and still no-dice. Tier 1 customer support was worthless, as was the advanced support team. It wasn't until after they told me to return the phone and hope for the feature to be fixed eventually in another build, that I again tried but with the factory dash cable. Android Auto worked immediately! I'm not sure why, but the cable that I was using with my other phone for AA wouldn't work for the 6T. Now that it is working, it works amazing.
I hope this helps someone else... Best of luck.

I can tell you my non-standard cables on my Essential phone are intermittent with AA in my car, but the stock cord, works...only phone I now that didn't work at all is the Pixel 2 XL...sold it anyway. But I use AA daily and about to buy this phone because I'm on Verizon and been awaiting support. So as long as the cable is just the issue, no biggie..can always buy a spare one for the car.

coolguy said:
3) sometime it doesn't even update the location and blank map
Etc..
Click to expand...
Click to collapse
Same. I finally just switched over to Google Maps and it's been solid.

SportingChap said:
Same. I finally just switched over to Google Maps and it's been solid.
Click to expand...
Click to collapse
Yah, but missing cops info.

Fixed the blank screen in Waze on AA by going to the battery optimization of the app and disabling it.
Works flawlessly

Question NOS 1.1.3 breaks Android Auto

My Android Auto is stopped working when i manually update to 1.1.3
Anyone seeing the same issue? Is there a way to downgrade to 1.1.2?
Also, i had performed factory reset on 1.1.3 and it didn't helped, AA is still not working.

you shouldn't have done that

UserNamist said:
you shouldn't have done that
Click to expand...
Click to collapse
yes lesson learned in a hard way. so i need to downgrade to previous version or use my other phone since i rely heavily on AA...

ok problem solved. i need to manually go to phone usb setting and select file transfer. what a rookie mistake.

I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.

Gerard03 said:
I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.
Click to expand...
Click to collapse
It doesn't work on 1.1.2 for you?

panni said:
It doesn't work on 1.1.2 for you?
Click to expand...
Click to collapse
No it doesn't just black screen in the car and the phone says it's connected, also the first time I done it it showed the Android auto introduction screen on the phone, but the screen remains in black.

Gerard03 said:
No it doesn't just black screen in the car and the phone says it's connected, also the first time I done it it showed the Android auto introduction screen on the phone, but the screen remains in black.
Click to expand...
Click to collapse
have you checked your usb connection option when connected to AA? there should be an option for selecting either file transfer/AA, USB tethering, MIDI, PTP, and no data transfer (default selection).

advanxer said:
have you checked your usb connection option when connected to AA? there should be an option for selecting either file transfer/AA, USB tethering, MIDI, PTP, and no data transfer (default selection).
Click to expand...
Click to collapse
No but I will check. I didn't know you need to do that to use AA.

So this is not related to 1.1.3. Please stop picking this thread up in other threads and stop posts like "there are issues with 1.1.3 and Android auto". Thanks!

advanxer said:
My Android Auto is stopped working when i manually update to 1.1.3
Anyone seeing the same issue? Is there a way to downgrade to 1.1.2?
Also, i had performed factory reset on 1.1.3 and it didn't helped, AA is still not working.
Click to expand...
Click to collapse
Gerard03 said:
I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.
Click to expand...
Click to collapse
panni said:
It doesn't work on 1.1.2 for you?
Click to expand...
Click to collapse
This is not from the Nothing OS 1.1.3 update, but from the Android Auro update
The most common message users report seeing is "phone not compatible" when pairing their device via the Android Auto app. What happens on the car screen depends on the specific make and model, but it's usually an error message of some sort, with some user submissions shown below.
The issue appears to be Android version independent and related solely to the Android Auto 7.8.6 update.
Google representatives responded to the thread, asking for more details about the user reports, including Android Auto version number, smartphone model, car make/model and other relevant data. But for the past three days, Google has remained silent on the issue besides mentioning that the information has been passed on to the Android Auto team.
If you're having problems, downloading an earlier version of Android Auto may solve the problem, and you can also try signing up for the beta programme while you wait for a fix for the app.

Ok thanks I will try.

Gerard03 said:
Ok thanks I will try.
Click to expand...
Click to collapse
If you want, go to see this news from AndroidSage : https://www.androidsage.com/2022/08...8-0-6-beta-apk-with-new-features-coolwalk-ui/

I am not sure whether my previous issue was related to specific Nothing OS or AA version. But here's what i had observed:
In 1.1.2, i can simply plug in the AA usb cable to the Nothing phone (with locked screen) and AA will load automatically on the car HU.
In 1.1.3, that did not happened. After connecting the USB cable, AA will not load automatically. Instead, i will need to unlock my phone, go to USB Accessory setting and change either from "File transfer" to "No data transfer" or from "No data transfer" to "File transfer", then only AA will load on my HU. Since this setting is not permanent, i need to repeat this steps every single time i want to use AA.

Works perfectly fine here

Funny, i changed from S22 Ultra and now all troubles with Android Auto is gone, louder navigation and the 1-3 sec of silence every 5 mins when playing music is gone, OnePlus 8t Samsung s20 fe 5g and s22 Ultra all had the same issues, now i can finally enjoy music while driving!

Android-Desire said:
Funny, i changed from S22 Ultra and now all troubles with Android Auto is gone, louder navigation and the 1-3 sec of silence every 5 mins when playing music is gone, OnePlus 8t Samsung s20 fe 5g and s22 Ultra all had the same issues, now i can finally enjoy music while driving!
Click to expand...
Click to collapse
Doubt that's an hardware or phone issue.
It's an AA issue mostly. I haven't had any problems with my OP8T for example. On some phones i had issues but after clearing cache, force close and reinstalling AA it worked flawless.

P6P said:
Doubt that's an hardware or phone issue.
It's an AA issue mostly. I haven't had any problems with my OP8T for example. On some phones i had issues but after clearing cache, force close and reinstalling AA it worked flawless.
Click to expand...
Click to collapse
Wierd how there is no issue on this phone out of any phone i have used before.

Can we mark this thread as fixed?