Thanks Azerox and community at large for helping me out. USB - MTP or any Android Composite ADB Interface option will allow Windows to recognize the Pixel 6 as a storage device (assuming, again, that file-transfer is enabled on the phone). So for the sake of SEO and future frustrated pixel-users, update your USB driver from Device Manager by selecting "Browse my computer for drivers," and then "Let me pick from a list of available drivers on my computer." You will not be looking for the Google USB Driver-that's for ADB purposes/troubleshooting. ![]() It wasn't until I stumbled across this Stack Overflow thread that I realized I had to abandon the automatic "search for updates" and manually roll back the driver. ![]() To add to my confusion, when I updated the driver from Device Manager (right click > Update Driver), Windows prompted me with a "The best drivers for your device are already installed" message. Secondly, avoid using a USB C to USB C cable. If you are unaware of a PC’s USB 2.0, you can check the manual you got when you first bought the computer. Just use the USB 2.0 port, as many cables are incompatible with USB 3.0. Every time I restarted or plugged my phone back in, I saw Windows re-assert the Acer driver. Firstly, avoid using the USB 3.0 port of your PC. I installed the aforementioned Google USB Driver, and uninstalled the "Acer Composite ADB Interface" from Device Manager (right click > Uninstall) erroneously thinking that the Google driver would appear on restart by default (spoiler: they're different drivers). It remained invisible in all other modes. When I enabled USB Debugging and switched to PTP mode, I could see the Camera folder in Windows Explorer. My Pixel 6 was invisible to Windows Explorer in all USB modes, but it would show up as "Acer Composite ADB Interface" in Device Manager and as "Unspecified Device" in Devices and Printers. In the off chance that it may help someone else, I would like to share my journey and credit Azerox's solution. That one check mark being left off is what killed me.I apologize for the mass text, but this was the only resource I could find when I had this issue and I wasted a lot of time running in circles before understanding what was actually causing the problem. I should note that part of the answer was as I was adviced, to do each step methodically and not miss anything. I've seen it in Andoid Phones before too. This shows up in Device Manager in the old LeMobile area (what is that in reference to?). ![]() But, it keeps saying I have the latest driver. Here are the driver files: View attachment 5744451Īs for why it is Microsoft or why I can't update the driver to latest Google V13 I am not sure (I tried to update it per the the latest 'usb_driver' folder both from directly downloading and the same version from Android Studio. Note that it is by Microsoft dated V1.746 driver (how whacky is that date, first Android phone I owned, maybe the original Note). I checked each of the phones including the directories and SD Cards (for the LG and Samsung). I then checked Device Manager and all four are showing in the Portable Devices area (no longer under Samsung Phone): I then reconnected the phones and File Explorer came up with the Pixel 7 Pro, then Nexus, then LG V35, then Samsung. Once I selected that it uninstalled the pesky driver. The key was not just 'Uninstalling Device' in the Android Composite areas driver properties, but, the dialogue from the first of the sequence of drivers uninstalls had a small tick mark on the left bottom that I had missed: 'Delete the Driver Software from this Device'. I zeroed in on the multiple Androids (two from Google, an LG, and a Samsung) that I've had and that the drivers were showing from 2012. Okay, owe a debt of gratitude to all of you especially simplepinoi177.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |