I hooked my 2 pixels together with USB thinking I could transfer some files, now all the options are greyed out, how do I put things back to normal?
So it turns out, that when I am plugged into PC "connected device" and "this device" are available but "Use USB" for has all the options greyed out, and not able to connect for ADB, on my other pixel all it fine?
I had this problem as well, i even factory reset phone and nothing so Google sent me a replacement and all good after that
Summer 2019, I had (have?) this problem with my Pixel XL. My "Use USB For" is greyed out. (I'd *like* to transfer files to my computer.)
I'd tested multiple cables on multiple computers. (including cables & computers that used to work previously)
I had tried rebooting the phone.
A couple of weeks passed, and I tried again just now. Same problem. But this time, when I rebooted my phone, the problem immediately resolved itself!
(may be worth testing: I rebooted the phone while it was plugged in to the computer... not that this should matter.)
Anyway: My conclusion (based on meager evidence) is that rebooting *may* fix the problem. Rebooting a couple of times may also help.
I sprayed alcohol in the port, and all is good.
Related
hi there,
I have two (potentially related) problems, the power draw of my desire is immense, from a full battery I get 3hrs tops (in airplane mode). Even when plugged in I don't get much longer i receive a message saying that the power draw is too high.
I have tried restoring factory settings a few times, 3 different batteries and an external charger.
I thought it might be worth trying a custom ROM to see if that helps but i can't get the phone to connect to the computer, it appears to "charge" when plugged in (although still with the above problem) and when i enable USB debugging it senses that there is a cable plugged in and says "USB debugging connected" but the computer can't see it and the phone never asks what i want to do with it when it's plugged in. I've played around with all the USB settings on the phone, tries 2 different cables, 2 computers and both winXP and Ubuntu.
any ideas?
Liambass.
Hi guys,
My GNex has a problem. Many users seem to have a similar problem but theirs seem to be hardware related and I'm pretty confident mine is software related.
It started a few months ago when my GNex wouldn't charge through the wall charger. I was on a trip with my friends so I didn't have access to a pc and wasn't able to troubleshoot further. The charging icon would appear when the phone was off but when I turned it on it didn't charge. I played around with the phone for about two hours, rebooting, Googling for solutions, changing the USB connection modes in the Storage settings. When I changed from Next Launcher to Stock launcher and rebooted everything was working fine again. However I think it was only a coincidence. Then the problem didn't occur again until now and this is why I think it's software related. If hardware would have been broken the problem wouldn't just have fixed itself like that.
It happened 3 days ago but somehow fixed itself again. I was troubleshooting the issue with my GNex connected to PC and installed Nexus Root Toolkit by Wugfresh. During install my phone rebooted on it's own and suddenly USB worked perfectly again!
However yesterday I forgot to charge and my GNex died. On reboot the issue was back.
"Symptoms":
Phone won't charge with any wall charger (and any cable) unless off
Phone will charge through USB in any mode but PC will not recognize it and install it as unknown device.
USB Debug Icon and Connection Mode notification do not appear in status bar upon PC connection
OTG doesn't work and apps like "Stickmount" do not detect external drives
Attempts:
Gently bending the "tongue" inside the micro usb on the phone in case there is a bad connection
Reinstalling drivers on PC
Rebooting device in different modes including fastboot
Using different batteries
NOTES
This problem started after latest 4.3 update. It has only occured after battery completely runs dry. I have 3 batteries (a bit excessive I know) and an external battery charger so charge is not the issue, I just really want to understand what's going on with my phone.
I'm not ready to Factory Reset or replace the USB port yet, those are last resort options to me. Any other options, especially software related, are very welcome. I am on stock 4.3 only rooted and with CWM recovery.
In Testing menu (type *#*#4636#*#* in Dialer) under Battery Settings my phone also says Charging (AC) when connected through USB. Hope this helps.
Been Googling around for two days now so I decided to make my own thread. Any help is appreciated. Sorry for this very long post.
Fixed it! Tried bending the tongue inside the micro usb again, forced much more this time, everything is working again, for the moment
So my phone is no longer being recognized as a USB device by my computer. Whenever I plug my phone in, I don't see the USB storage option on the top of my phone, nor will my computer even acknowledge that it's been plugged in. This issue has never happened to me before, and it only started acting up just last night. It isn't an issue with the computer OR the cable; I've tried with many different PCs and cables, both third party and official, and I'm getting the same problem. I don't think it's an issue with a broken microusb port, either, since it still charges. Interestingly enough,the computer WILL notice that something has been inserted when I plug it in... if the phone is off. However, the phone only shows up as an unknown device. Also, when I check the battery status, it almost always says that I'm charging via AC even though I'm using USB.
After exploring the forum, I've discovered and tried using *#7284#, but the code refuses to work. (I also tried other codes just to see HOW they work, and none of them will register on my phone.)
I'm currently running CM 7.1, and my phone is rooted. I haven't changed the ROM ever since I started using it, which was about a good year or so ago, and I seldom do any sort of flashing, so I highly doubt it's related to that.
Any suggestions? I thought it might be a dirty microusb port, since I've also been getting the random Car Mode popups as of late, but after cleaning it out, nothing seems to have changed.
Just wondering if Android Auto for connected car displays stopped working for anyone as of yesterday or today. I'm skeptical of another Google "back end experiment" that caused it to stop working. I have a Ford with Sync 3
Symptom: Plug phone into car, nothing happens. Phone only charges and will even say USB is connected.
I've done some basic and partially in depth trouble shooting. It most likely couldn't be caused by any updates on Car infotainment system or my Phone because it has been working (unless there was a back end play services update that was pushed out).
From the obvious to less obvious:
-Tried rebooting phone and restarted car
-Tried using a different USB A to C cable (Anker ones have worked perfectly for me)
-Tried using secondary USB port in car
-Tested phones ability to connect to a PC and transfer data, no issue
-Threw music onto a USB flash drive and plugged it into car, no issue
-Tried turning on USB debugging on phone, no change (not sure if this would have even helped in first place).
I'm at a loss right now. It does not make any sense.
I do not have another android phone to try or an iPhone to test CarPlay unfortunately.
Literally had the same thing happen to me on Sync 3 last week. I just deleted the car from the Android Auto app and deleted the phone from Sync 3. After that I was able to use Android Auto again after going through the setup prompts. No issues since.
Works fine for me on my 2018 silverado
no issues on 2017 Sierra
Here it works perfectly
bigblueshock said:
Just wondering if Android Auto for connected car displays stopped working for anyone as of yesterday or today. I'm skeptical of another Google "back end experiment" that caused it to stop working. I have a Ford with Sync 3
Symptom: Plug phone into car, nothing happens. Phone only charges and will even say USB is connected.
I've done some basic and partially in depth trouble shooting. It most likely couldn't be caused by any updates on Car infotainment system or my Phone because it has been working (unless there was a back end play services update that was pushed out).
From the obvious to less obvious:
-Tried rebooting phone and restarted car
-Tried using a different USB A to C cable (Anker ones have worked perfectly for me)
-Tried using secondary USB port in car
-Tested phones ability to connect to a PC and transfer data, no issue
-Threw music onto a USB flash drive and plugged it into car, no issue
-Tried turning on USB debugging on phone, no change (not sure if this would have even helped in first place).
I'm at a loss right now. It does not make any sense.
I do not have another android phone to try or an iPhone to test CarPlay unfortunately.
Click to expand...
Click to collapse
happens to me every 3-6 months.
Swapping out the cable resolved it every time.
ya dude you need to try some different cables. that should always be your first step if there have been no updates.
Thanks for the replies. I deleted and unpaired AA from my phone and my car with no luck.
I actually had my coworker who has a Pixel 2 XL plug his phone in to my car. He had no issues at all even after multiple tries. Mine still wont connect. We're both on Pie with same security patch level. Did try tried Multiple new cables and still no luck (the anker high quality ones).
I found this thread incase it starts happening to anyone...
https://productforums.google.com/fo.../PWBrDUXzR4o;context-place=forum/android-auto
Something I picked off of that topic was some USB patches/features that went in to effect between Pie release and last month security patch.
I may just wait a month. Maybe another security patch which tweaks USB or 9.1 will drop fixing my issue. We shall see. At least I know its not my car or my cables.
Go into apps and check your "play services" versions between the two phones. Google controls a lot of **** through that app
Or just try to clear your usb port
Thanks for the replies. After the October patch I'm back up and running.
Lack of communication between departments at Google baffles my mind.
I am running the latest Android 13 QPR beta release. Ever since I updated, I've been having a connection issue in every app. Every 2 minutes or so, my phone "loses connection", regardless of Wi-Fi or data, regardless of signal strength, any app will struggle to connect for a few seconds. My phone doesn't actually lose connection, it's weird. Most apps will just reconnect and go on about it's business after about 10-15 seconds of connection issue, but some refuse to "reconnect", so I have to close the app and reopen. After weeks of this, I decided to reformat my phone and go back to the stable android 13 release, by opting out of the beta and receiving the OTA to go back to stable. I did this with the intention of installing a custom ROM.
However, the OTA took an abnormally long 2 hours to complete. Upon completion of the update, my phone gave the the installation successful message with a restart. Upon restarting, I was greeted with the bootloader and the message "No operating system installing. Cannot boot". After a few minutes of restarting and fumbling around to no avail, eventually it booted back into my beta build. I breathed a sigh of relief. This was, however, not the end.
At this point, I thought "that was frightening. Best off just to try to install the factory image through ADB". So I go on to plug in my USB cable, and I see the notification that USB was connected. I try to click the notification to switch to file transfer mode, and then it disappears, and Windows loses connection to my phone. I'm now no longer able to get my P6P to recognize that it is plugged into a computer, and my computer refuses to detect my phone. It does however charge off the PC connection though. I've tried updating drivers, switching cords (including the factory cable, the usb-c to a cable that I usually use with this phone with success), USB 2 ports, USB 3 ports, restarted my computer, factory reset my phone, quadruple checked USB debugging was enabled, and nothing seems to work.
I'm stuck on the beta build. Cannot do anything with ADB. Cannot do anything with recovery mode, as apply update from SD just returns an error. I'm hoping I'm just missing something simple. Are there any other suggestions or ways to get around needing a computer for anything?
Thanks for reading!
This can be closed. After hours of frustration, I tried a cord that doesn't seem like it should work. It's a "universal" cord (one with a micro-USB connection and an adapter for USB-C and lightning). Never give up, you never know ¯\_(ツ)_/¯
xChowderrrx said:
This can be closed. After hours of frustration, I tried a cord that doesn't seem like it should work. It's a "universal" cord (one with a micro-USB connection and an adapter for USB-C and lightning). Never give up, you never know ¯\_(ツ)_/¯
Click to expand...
Click to collapse
I always have mtp set as default. Better to be safe than sorry
I do, as well. Connection wasn't being detected on either side. I was also getting a pop-up on my computer saying something along the lines of "the last time this device was connected, it malfunctioned. Windows cannot recognize the device." That's why I initially thought drivers, and only tried a few cords. But I got desperate and reached deeper in the bin. Thanks for the pointer, though.