Develop Bugs

Is "Autoplay" working for you in Windows 7?

As title says, when you plug in your Galaxy Nexus into your Windows 7 PC, do you get the autoplay window? Whatever I do, I cannot simply get it to show. The reason I want this is for the new Dropbox beta where you can receive more storage by simply testing their camera upload feature.
What I have done so far:
- Uninstalled and reinstalled the Samsung official drivers
- Uninstalled Samsung Kies
- Set ALL the options in AutoPlay configuration (control panel) to "Ask me every time"
- Rebooted the computer between all of the steps above
- Turned off USB Debuggig or switched to PTP instead of MTP
I am using the "Samsung Android ADB driver".
So. Does it work for you guys? If it does, please post what driver you are using and if you can come up with any troubleshooting hints for me. Google could not help me this time. Thanks in advance

I get autoplay just fine, unless I turned it off.

adrynalyne said:
I get autoplay just fine, unless I turned it off.
Click to expand...
Click to collapse
It's definitely turned on. What driver are you using?
News: I tested it on my GFs laptop and autoplay is working there... Maybe I should uninstall the Samsung driver altogether. I'll give it a shot.

Uninstalling the Samsung Driver did not help.
When your phone is plugged in, do you get a menu entry for "Autoplay" if you right click the "Galaxy Nexus" device under "Computer"? I dont...

ipkryss said:
Uninstalling the Samsung Driver did not help.
When your phone is plugged in, do you get a menu entry for "Autoplay" if you right click the "Galaxy Nexus" device under "Computer"? I dont...
Click to expand...
Click to collapse
Thats only valid for drives or devices assigned drive letters.
Go under your autoplay settings and check them.

I get it, win7 64 bit.
I got my drivers via a pdanet install, haven't tried any others.

Plugged my GNex into parent's laptop (Win7 64bit) to give them some pictures, autoplay popped up and pics transferred just fine.

I am having problems with the autorun feature in W7 finding photos on my Galaxy Nexus also.
When I look in AutoPlay options page I see multiple selections for our camera, my old droid, my Gnex and my old Blackberry.
I am thinking these drivers are causing problems. How do you clear out these old drivers?

on Win7: Start>Default Programs>Change AutoPlay Settings. check if your GN is there and you can change the autoplay option.

[Q] Debugging Apps on the 360

Hey everyone,
I read through the big thread in this forum about trying to unlock the bootloader, but I didn't see anything that answered my question. I am currently creating an app, and according to the Google Developer site (http://developer.android.com/training/wearables/apps/creating.html), I need to plug the watch into my computer and set USB debugging. The obvious problem is that there is no USB debugging on the Moto 360. So my question is this: Is it possible for me to debug my application on my Moto 360 vs the Android Wear emulator? Or is it a situation where I would need to generate a final apk, put it on my phone, and have it install the wearable part automatically in order to test it? (That last part is how applications are installed onto the watch from apps in the Play Store). Any help would be appreciated, as the emulator is really annoying to use . Thanks.

You can connect to the watch using bluetooth debugging. I've messed with it a little. It's actually pretty easy.
https://developer.android.com/training/wearables/apps/bt-debugging.html
The downsides I experienced were that you couldn't do anything in the recovery or bootloader via the bluetoothed adb, which was the outcome I was expecting.

Mi|enko said:
You can connect to the watch using bluetooth debugging. I've messed with it a little. It's actually pretty easy.
https://developer.android.com/training/wearables/apps/bt-debugging.html
The downsides I experienced were that you couldn't do anything in the recovery or bootloader via the bluetoothed adb, which was the outcome I was expecting.
Click to expand...
Click to collapse
That is exactly what I am looking for. I will definitely test this out when I get home. Thanks a lot.

dragonforce11 said:
That is exactly what I am looking for. I will definitely test this out when I get home. Thanks a lot.
Click to expand...
Click to collapse
Do this
adb forward tcp:4444 localabstract:/adb-hub;
then
adb connect localhost:4444
instead of all at once... I wasted too much time because i tried to run the whole command together...

Offline
I've spent a lot of time these past few days trying to figure out how Bluetooth ADB is supposed to work.
I've turned on debugging on my watch, and on my tablet. The companion app has debugging enabled. I type in the same console messages.
I get
List of devices attached
08f2a262 device
localhost:4444 offline
And I can't figure out how to make it online. The companion app agrees that the host is connected but the target is disconnected.

I don't think a tablet is going to cut it here

[Q] Analog keyboard installing help

So I've been trying to install the microsoft analog keyboard on my zenwatch. I've been using usb connection as I cant seem to connect my msi with the watxh via bluetooth.
When I try to install it initially connects with each other but when I try to run:
"adb -s localhost:4444 install com.microsoft.research.analogkeyboard-Signed.apk"
It seems to lose the connection between the watch and pc and I keep getting an error message.
Has anybody had this issue?

The watch has voice recognition. I use it many times daily to reply to texts and perform searches while driving. It's extremely accurate. Only one time did it not pick up exactly what I said. Even in a noisy environment it works flawlessly. No need for a keyboard

Yeah but the problem is that I am from Denmarl and I think my friends and family would find it weird if I began to answer their texts and mails in english ?

Can you install other keyboards like Minuum for example?

Unless you've got more than one device connected to adb at the same time, I think you should remove the "-s localhost:4444". I've been able to install things okay with just "adb install apkname.apk" after connecting the watch via USB (and having no other devices connected).

Info on the Marshmallow update for Turbo 2

I had a little chat with "ASHLEY" from Verizon's Live Chat. Apparently (and she told me this after i factory reset my phone) the marshmallow update is getting little patches so that everyone's phone is prepared... a little annoying since i almost got to installing but i had to take my phone off Wi-Fi for 6 1/2 hours while i was at school, and so the update i would've gotten was canceled by verizon or something... I even had downloaded part of it.
Just a little FYI.

Thank you for the update. I just picked up the phone. I deferred the update when I set up the phone and now I can't get the download back. Now, I most likely know why. I'll wait a day or two. If I can't get the update back, I'll hard reset the phone. Sighs...
Sent from my XT1585 using Tapatalk

Verizon's Twitter support just confirmed a hold on the marshmallow update. Any exact date then?

I had the OTA update notification on Friday but no wi-fi at work. Got home and the download failed and then got software up to date when checking on the phone. Plugged the phone into my pc Saturday night and the Verizon Wireless Software Update popped up saying an update was available. In less than 20 minutes I was good to go.

tonbonz said:
I had the OTA update notification on Friday but no wi-fi at work. Got home and the download failed and then got software up to date when checking on the phone. Plugged the phone into my pc Saturday night and the Verizon Wireless Software Update popped up saying an update was available. In less than 20 minutes I was good to go.
Click to expand...
Click to collapse
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.

cdowning22 said:
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.
Click to expand...
Click to collapse
Some have reported the the Verizon software update assistant works if you connect your phone to your pc/laptop via USB 2.0 -- but not USB 3.0. That didn't make a difference for me. We've got 3 Turbo 2's: two of them got both updates successfully OTA. One of them never got it OTA, and still gets nothing when we check for updates. I've tried connecting that third DT2 to my laptop and using the software update assistant - with the phone connected at different times to each of the 4 USB ports on my laptop (3 of them are USB 3.0, 1 is USB 2.0), and I've toggled MTP mode on and off, but no joy: the update assistant never recognizes the phone. However the laptop does, indeed, recognize the phone, and lets me open a file browser window and look at files on the SD card.
Only variable I'm not confident about here: when I connect the phone to the laptop, there's the typical Windows popup that asks what I want to do when this device (the phone) is connected to the laptop. Note: the update assistant is NOT offered: just typical options such as, "transfer media files to PC". Not sure which to accept, I've ignored that prompt -- wondering if perhaps I need to select one of these options in order to complete the MTP connection properly?

jonstrong said:
Some have reported the the Verizon software update assistant works if you connect your phone to your pc/laptop via USB 2.0 -- but not USB 3.0. That didn't make a difference for me. We've got 3 Turbo 2's: two of them got both updates successfully OTA. One of them never got it OTA, and still gets nothing when we check for updates. I've tried connecting that third DT2 to my laptop and using the software update assistant - with the phone connected at different times to each of the 4 USB ports on my laptop (3 of them are USB 3.0, 1 is USB 2.0), and I've toggled MTP mode on and off, but no joy: the update assistant never recognizes the phone. However the laptop does, indeed, recognize the phone, and lets me open a file browser window and look at files on the SD card.
Only variable I'm not confident about here: when I connect the phone to the laptop, there's the typical Windows popup that asks what I want to do when this device (the phone) is connected to the laptop. Note: the update assistant is NOT offered: just typical options such as, "transfer media files to PC". Not sure which to accept, I've ignored that prompt -- wondering if perhaps I need to select one of these options in order to complete the MTP connection properly?
Click to expand...
Click to collapse
None of my USB ports work. I've tried uninstalling and reinstalling everything, with no results. Unless there is a manual solution available, I guess I'll have to wait through this 2nd straight Verizon branded false alarm.

cdowning22 said:
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.
Click to expand...
Click to collapse
You can run it and check for updates manually once it's installed. Just to be clear, when my phone is connected to my pc if I pull down the notification menu on my phone and tap the usb notification there is an option to install software that, when checked, adds a cd installer in windows explorer on the pc to install the Software Update and Repair assistant. @jonstrong I just ignore the pc popup or select take no action.

cdowning22 said:
None of my USB ports work. I've tried uninstalling and reinstalling everything, with no results. Unless there is a manual solution available, I guess I'll have to wait through this 2nd straight Verizon branded false alarm.
Click to expand...
Click to collapse
I had similar issues, I installed SUA on my laptop and it would not detect the phone. Installed it on my desktop and it recognized the phone. Both are running Windows 10.

What cords are you using to connect? Sometimes that can make a difference.
Sent from my XT1585 using Tapatalk

scadilla said:
I had similar issues, I installed SUA on my laptop and it would not detect the phone. Installed it on my desktop and it recognized the phone. Both are running Windows 10.
Click to expand...
Click to collapse
I haven't had a desktop computer for years. But at least I'm not alone.
sparky697 said:
What cords are you using to connect? Sometimes that can make a difference.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Doesn't matter what cord I have, won't detect. I'm screwed at this rate.

I can not get the Software Upgrade Assistance (SUA) to work on my Desktop PC but was able to get it to work on my wife's Desktop PC. I tried on my laptop and found that the Verizon Software Upgrade Assistance (SUA) works (recognizes the phone) on the laptop's USB2 ports but will not work on the USB3 ports. My wife's PC has USB2 ports and My PC has USB3 ports. All the above computers are running Windows 10.
Based on my testing, it appears that the Verizon Software Upgrade Assistance (SUA) does not work with USB3 ports.
Try using a PC or laptop with USB2 ports.

rbird2 said:
I can not get the Software Upgrade Assistance (SUA) to work on my Desktop PC but was able to get it to work on my wife's Desktop PC. I tried on my laptop and found that the Verizon Software Upgrade Assistance (SUA) works (recognizes the phone) on the laptop's USB2 ports but will not work on the USB3 ports. My wife's PC has USB2 ports and My PC has USB3 ports. All the above computers are running Windows 10.
Based on my testing, it appears that the Verizon Software Upgrade Assistance (SUA) does not work with USB3 ports.
Try using a PC or laptop with USB2 ports.
Click to expand...
Click to collapse
Won't even recognize on USB2. Repeating: Screwed

make sure that your phone does not have USB debugging on. Also make sure you are using OEM cable (from any brand really). COnnect to a USB 2 por and go to www.motorola.com/verizonsoftwareupdatewin (if you have a windows computer) or replace win with mac
Download, install, and run software assistant... unplug your droid turbo 2 a couple of times until the software sees it... then it should work
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
gabo_e30 said:
make sure that your phone does not have USB debugging on. Also make sure you are using OEM cable (from any brand really). COnnect to a USB 2 por and go to www.motorola.com/verizonsoftwareupdatewin (if you have a windows computer) or replace win with mac
Download, install, and run software assistant... unplug your droid turbo 2 a couple of times until the software sees it... then it should work
Click to expand...
Click to collapse
1. my signature is old... lol
2. don't let your phone lock/ go to sleep while it is downloading

For anyone who's still having trouble getting the update on their Droid Turbo 2 - my experience might be worthwhile knowing about:
We've got three DT2's (would have been four, but my son opted for an iPhone). The first two were offered the update when the first big wave came around - before they shut it down a second time; we accepted the 2 step update for those two phones, and they were both successfully updated to Marshmallow over a week ago. The third DT2 however never got the offer, and punching "check for updates" never found the update either -- even as recently as today, March 19.
I had tried connecting the third phone to my laptop via USB -- and made sure to use the USB 2.0 port on my laptop (the other three USB ports are USB 3.0), and made sure the phone was set to MTP mode. Still no joy. Never offered the "CD Install" option on the phone, even though I had checked both MTP mode and Software install on the phone under USB options.
Finally this evening I tried the same on a different laptop, and tried a different USB cable as well. This time, the phone actually offered the CD install option, and was able to prompt the laptop to download and install the Verizon Software Upgrade Assistant (VSUA). It was till touch and go for a while: once I fired up the assistant, it still didn't seem to recognize the phone the first several times I tried it. Finally -- I let it sit for a couple of minutes with the VSAU loaded and the phone plugged into the laptop, and this time the phone showed up in the Upgrade window. I selected it and clicked on the upgrade button. I was amazed at how long the download took, as I remembered the "1 of 2" upgrade being pretty small -- with the 2 of 2 being the 1.1GB file.
Finally - the download completed, and the update began. That also took a long time, but I could see the progress indication, so I was encouraged. In the end, this single upgrade completed, and then the Android "upgrading" process began for what I recall to be 40 programs (probably what my daughter had installed on her phone) -- again -- I was surprised at how slow this was, but I made a point of NOT disturbing it.
Anyway - it finished, rebooted, and after this SINGLE update, the phone was all the up to the latest update for 6.0 for the DT2 -- the same version I'm at after doing the 1 of 2 and 2 of 2 updates the week before last -- 24.24.11 kinzie_verizon.verizon.en.US . It seems that the VSUA got my daughter's phone there with a single update -- something that surprised me. Maybe there's a new update file out there that does this in a single pass? Don't know.
But -- the take away for anyone still frustrated by not getting the update yet should be: you probably CAN get it, if you're patient enough, and are willing to try a couple of different cables, and possibly different PC's (one of my laptops couldn't deliver the update, but another was somehow able). Seems that it's still on their servers waiting to be downloaded, and VSUA can actually function if you somehow get the magical combo of computer, USB 2.0 port, proper cable, and LOTS of patience and willingness to try something repeatedly.
Jon

Well I Finally managed to get the VWSUA going on an older computer. Upgrade in progress...

Upgrade complete. I'm now on Marshmallow. Thank you all.

Computers don't recognize XL2 to transfer files

I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!

Delete

Did you set the connection type to data transfer?

InfiniteReality said:
I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!
Click to expand...
Click to collapse
I had the same issue and with a little searching I figured it out.. Make sure the phone is set to "Transfer Files" in the notification window drop down and download the Google USB drivers zip and install the driver after unzip. Right click the driver file and select install.
Since this is a new account XDA won't let me link yet so Google search for : Get Google USB Drivers

I'm having a similar issue, and we're not alone. I'll copy what I posted on reddit.
Asus ROG Maximus Hero IX motherboard. Tried with multiple cables. Wifes OG Pixel detects it is plugged in right away, my 2XL has to be screen off and set down for a couple of minutes, then the phone recognizes it is plugged in and starts charging and is available for data transfer.
Seven minutes and twenty seconds before it started charging, and another twenty seconds before the computer recognized it as being attached and ready for data transfer. I'm going to do it a few more times to see if there is a pattern.
Edit: Second time was seven minutes for both, third was three fifty one for both, eleven thirty three on the fourth.

I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.

Using Windows seems to be the common problem when connecting Android Phones to a PC.

stevemw said:
I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.
Click to expand...
Click to collapse
dratsablive said:
Using Windows seems to be the common problem when connecting Android Phones to a PC.
Click to expand...
Click to collapse
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version

InfiniteReality said:
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version
Click to expand...
Click to collapse
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin

When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)

I don't know if this will have any effect but on the pc, plug to the usb ports on the back that are direct to the motherboard instead of usb headers on the top/front of pc.
I have this issue with a TomTom satnav and a Mio miview dash cam. Unless they are plugged in on back pc / with Windows 10 doesn't recognize
Sent from my XT1572 using Tapatalk

Thanks everyone for the suggestions!
dratsablive said:
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin
Click to expand...
Click to collapse
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
stevemw said:
When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)
Click to expand...
Click to collapse
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!

InfiniteReality said:
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!
Click to expand...
Click to collapse
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?

stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
Nothing at all, it's like it's not even connected. Just kind of dumbfounded on why when my XL never has had an issue. Attached a screenshot. The one with the triangle doesn't have anything to do with the phone though, it's always been like that and never bothered to mess with it.
The 2nd XL2 shipped yesterday and due in Thursday, so will be curious on if it has an issue. Hopefully it works as intended and I can just set it up and send this one back. Fingers are crossed for sure.

Are you updated to the latest ADB drivers? Right down to, you might have to remove and reinstall. I'm pretty sure I read that it's required.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

If the Pixel 2 is plugged in your screenshot indicates that it is present on the USB bus. It's like the drivers aren't completely loaded.

I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.

JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
Yea on my regular pixel I have to enable debugging for mine too work. Sometimes lol

stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
I had it enabled for a while, but no such luck. I'll give it another shot, haven't had it on while at work. Also will uninstall and reinstall ADB as well.

When this has happened to me a few times, reinstalling the Windows MTP drivers has worked. Someone else posted these instructions that worked for me.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.