Very strange issue, no results that I could find from google searches.
I am running Windows 7 64 bit. Everything Windows related is up to date, and so are all USB drivers. My computer is a laptop from Puget Systems.
My computer has three USB inputs; one USB 2.0, and two USB 3.0s. 2.0 versus 3.0 doesn't really matter though, because this issue happens with all three drives.
Heres the issue: When connected, USB devices are found, and recognized. 5-30 sec later, they disconnect, only to reconnect in a couple seconds. The cycle of disconnecting/reconnecting continues indefinitely. I have not been successful with keeping USB devices connected for more than ~30 seconds.
At this point, it could be any number of things causing this issue. But this is where it gets weird. This issue ONLY happens with mobile devices, and it happens with ALL mobile devices. By mobile devices I mean phones and iPods. I have tested my Samsung Galaxy S4, an iPod Classic, an iPod touch, an iPod nano, a Droid Turbo, and an iPhone 5. This issue occurred with all of these devices. The issue did NOT occur at all with my 2TB Seagate backup harddrive, my 1TB WD harddrive, several USB pen drives, my external keyboard, or my wireless mouse USB receiver that is plugged in nearly 24/7 in my USB 2.0 drive. My Xbox One controller disconnected 3 times in a row once, but that only happened once so it might have been a fluke...?
Anyways, what could be the reason for this strangely specific issue? Does anyone have any answers or has anyone experienced something similar?
Improper drive installation? Make sure your drivers are installed correctly. Try uninstalling and reinstalling them. If this does not work try to see if it is your USB cable or mobile device's port. (Test by altering to charge the device from a wall adapter) It could also be your computers port but you said in the title that it is only happening for mobile devices.
Reinstall the drivers to the devices you are having problems with. (Oh someone beat me too it.)
Related
My power button died on my phone. Or got less and less responsive. Last time I was lucky that trying a long time I managed to start up my phone. Since then I kept my phone on perpetually or restarting it if that was required. However, now my phone just suddenly turned off out of nowhere. I tried to turn it on again but had no luck. I had previously turned on USB debugging since I thought that was enough to turn it on from the pc if it ever got turned off. Now it seems that was not enough as it shows up as unauthorized in adb (I never tried actually connecting, very stupid on my part). Is there any hope for turning my device on through adb.
Phone: Nokia 7.1
There are some questions on problems with unauthorized devices (ADB Android Device Unauthorized) but those seem to assume I can still turn on my phone to change settings. Is it impossible otherwise?
tldr; Here is a detailed list of instructions if you want to try your luck with fastboot. Your touchscreen and volume buttons must be functional for this to work.
Make sure the phone is turned off.
Press and hold the Volume Down button. Don't release it.
Plug in a USB charging cable
When the screen turns on and shows a message saying "Download" or "Fastboot" mode, release the Volume Down button.
Charge your phone like this for 2 minutes, to make sure it has enough charge.
Move your phone's USB cable and connect it to a PC.
Download the binary for fastboot.
Run fastboot continue.
I am having a problem with adb not finding my evo 4g lte. I have USB debugging selected. The phone is updated to 3.17, so some of the options, like charge only/disk drive have changed (now i think my only options are HTC Sync and disk drive). I am using the most updated version of the Android SDK. I'm running a fully updated windows 7 box. I have tried all of my USB ports, adb kill-server/adb start-server. I even created an .ini file with the hex version of the device USB/VID id (based on the HTC Sync setting, the phone shows only as Android Phone in my windows device manager. I have not yet tried switching it to disk drive), and nothing has worked. The phone's bootloader is unlocked via htcdev, but is otherwise stock. And, oddly enough, my old evo 4g which is rooted and running CM9 can be found, so I think it's got to be something with the new phone, I am just not sure what. I've been researching this over the last few days and have tried everything I have found, all to no avail. Any advice would be greatly appreciated!
Internal port is faulty. Two terminals for charging ,two for data, the data one(s) may have fractured from.the board.
Okay I am going to try and be as discriptive as possible here to get this problem solved. I work at a company that makes BIG gear boxes and we have computers that run our Mills/Laths. These computers are currently FIT-PCs running XP. These computers are used to control the laths/mills via a usb to serial converter (PL2303_Prolific usb to serial converter). When it is plugged into an xp machine it is recognized as a com port. SO these machines are very old and are fail left and right, I intend to replace them with a raspberry pi running xfreerdp but I can't seem to get the usb serial device to be redirected to the virtual machine it is remoting into. Has anyone ran into this/know a fix for it? Please ask me questions if you are unsure of something because I am completely stuck here. TLDR Using raspberry pis as thin clients need to push a usb 2 serial cable through to the virtual xp machine
Unfortunately there are known issues with USB on Raspberry Pi. They're aware of the issue and working on it, but it is as of yet unresolved.
The USB Redux thread was created to capture the state of the work as well as the current list of work-arounds. The USB/serial converters are broken is a related thread.
There is hope, however. First, they are working actively to fix it, so I suspect it's just a matter of time. Second, there are a few things you can try.
There's a config file in
/boot/cmdline.txt where you can try adding a few entries. One that appears quite effective is dwc_otg.speed=1 and dwc_otg.fiq_fix_enable=1 (but they didn't help me). See this page for some examples.
Update the kernel (search for rpi-update) to at least #348 (use uname -a to determine the kernel level)
Good luck.
Update (Mar 13 2013). There appears to be a fix for the majority of USB issues as of kernel #389. Use rpi-update to update.
Am using Nokia 5228 phone. I want to install the other Phone OS like Nokia 5230. Is this possible or Not?
As far as I know this is impossible to achieve. Since the Sw is different for different phones.
Even though two phones appears to look same in functionality, obviously they will have some different functionality some where.. [Either in GUI or in the back end].
As well as, the device S/w are designed as to recognize the particular mobile phones for which they are made for [by serial number/ model number or may be anything else only.]
Also you'll have to get the S/w first which is very difficult to get.
You ca not change anything in the device so that the device gets other phone's S/w.
So conclusion is:
You CAN NOT install the Nokia 5230 OS for Nokia 5228 Phone.
I have Windows 7 64-bit. I also have a Windows 7 64-bit Virtual PC computer set up on the same computer.
I have an Android device installed. It does show up under device manager under Android Phone as a Android Composite ADB Interface on both the actual computer (64 bit) and the virtual computer.
The difference is that on the actual computer ADB devices don't show any devices whereas if I attach the device to the virtual computer ADB devices shows it just fine.
It seems to me that either this is a driver issue on the 64-bit side or it is an ADB installation problem.
What to try? I have tried uninstall/reinstall drivers, power down, power up computer and device over and over.
I know that at some level I have the right drivers, at least the 32-bit ones, because it works on Virtual PC.
You may ask why I don't just use Virtual PC. Well, I will if I have to, but it is slower. I would rather use the real computer if I could.
Reno's suggestion did get me thinking, however (thanks Reno). I decided to try these instructions: http://nookdevs.com/NookColor_USB_ADB
It worked to do this.
I knew about that web page as that is what helped me get it working on my 32 bit computer. The reason I didn't think to do this was because on my 64 bit computer the Android ADB Interface WAS showing up in device manager and that had not been happening before in my 32 bit computer until I did those instructions.
My guess is that on my 64 bit computer the ADB Interface was installing, but not working because there is something weird about the 64 bit driver.
Now everything is golden and I am good to do. Thanks Reno for sparking me to take a second look at that page!
Go through this blog post.
Based on the device you own you will have to hack your way thought the inf file as per the steps in the blog.