Develop Bugs

[SOLVED]Computer see's device for a few seconds, then disconnects.

Interesting problem I have had on and off. When I plug my phone into my desktop, it will connect normally, then a few seconds later it acts like I unplugged it. It's not the rom as it does it in recovery as well(both with usb-ms activated and without). I have HTC Sync installed. Rebooting either the computer and/or phone doesn't fix it, it just goes away after awhile and starts working again. I've experienced the problem FAR less when connecting it to my laptop, it will typically work there and not on my desktop when the problem crops up.
it's like this problem but it's not constantly http://forum.xda-developers.com/showthread.php?t=711616
-Edit- the device also doesn't show it's charging even when it 'disconnects'

I have the same problem. just keeps discontenting over and over it sees it for a few seconds then disconnects reconnects then off again.

sasigns said:
I have the same problem. just keeps discontenting over and over it sees it for a few seconds then disconnects reconnects then off again.
Click to expand...
Click to collapse
Mine doesn't reconnect, it 'disconnects' and stays that way(as if i unplugged it) until i actually do unplug it and reconnect it.
-edit- 1,000th post, YAY

I was having the same problem on my MacBook until I realized the MacBook must be plugged into power. Once plugged in everything was good. I wonder if the Evo demands more power through USB then other devices.

Yeah, sounds like a power issue to me. If you're using a USB port on a hub or on a keyboard, try one on the PC itself. Also, it could be a slow USB port or a bad cable if you are continuing to have issues. Try another computer if you can, and if you still have the problem try a different cable. Still have the issue, reflash (if you're running a custom rom) or contact Sprint for service.

Same issue here, but on a desktop PC (Dell Studio XPS) using the front-mounted USB port (not a hub). Keeps disconnecting/reconnecting, but often takes 10-15 minutes between cycles. Using stock ROM (for now, at least). Will try other ports & another PC and will report back.

Already tried different ports, only motherboard ports
Rom doesn't matter as the problem exists in both android and recovery
Don't have a different cable, however the same cable will work fine on my laptop then not work on my desktop

mrono said:
Already tried different ports, only motherboard ports
Rom doesn't matter as the problem exists in both android and recovery
Don't have a different cable, however the same cable will work fine on my laptop then not work on my desktop
Click to expand...
Click to collapse
If it works on a laptop, but not the desktop, then it appears to be an issue with your desktop. Any other USB devices doing it?
I would check your motherboards manufacturer and make sure you've got the right USB drivers, a bios update might be in order as well.
But before all that, I've got an idea. First and foremost, try this:
Go to device manage (either from control panel, right-clicking my computer and going to properties, or searching for devmgmt.msc in the start menu search.)
Navigate down to Universal Serial Bus controllers, double click on USB Root Hub (you probably have 1 for every USB Port, so you may have to do them all.)
Click on the Power Management tab, and uncheck the "Allow the computer to turn off this device to save power." check box and see if that solves your problem.

i had this issue on my hero. it was corrected for me after i did a wipe of data and cache. i restored from titanium afterwards. YMMV
good luck

one thing you might try is disabling sense and using the android launcher. then reset the phone. once it boots up try and connect it to your pc. This was how I got mine to connect. when I was using the sense launcher it somehow blocked that options screen and the default I selected wouldn't stick. once I got the connection to my pc working this way I was able to re-enable sense and it's worked perfectly ever since.
I do not take credit for this fix, someone else on here told me to try this n it worked perfectly.

tarheelsmj12001 said:
one thing you might try is disabling sense and using the android launcher. then reset the phone. once it boots up try and connect it to your pc. This was how I got mine to connect. when I was using the sense launcher it somehow blocked that options screen and the default I selected wouldn't stick. once I got the connection to my pc working this way I was able to re-enable sense and it's worked perfectly ever since.
I do not take credit for this fix, someone else on here told me to try this n it worked perfectly.
Click to expand...
Click to collapse
it was nothing with the rom, since it was doing the same thing in recovery.
it turned out to be the short little usb extender cable that was going a foot and ahalf from behind my pc to the side so i could plug it in easier.

Sirchuk said:
...Navigate down to Universal Serial Bus controllers, double click on USB Root Hub (you probably have 1 for every USB Port, so you may have to do them all.)
Click on the Power Management tab, and uncheck the "Allow the computer to turn off this device to save power." check box and see if that solves your problem.
Click to expand...
Click to collapse
I can confirm this works on my HTC Desire - had been racking up my brains for the past couple of days now with no solution! Thanks a lot. This is on PC with Win7 Ultimate.

[Q] Soft-bricked, trouble with Odin + USB

I've scoured the forum to an answer to my problem but I've not yet found any so hopefully you guys can help.
Somehow I managed to soft-brick my Epic 4g, just been having all sorts of problems. Anyway I'm able to get in download mode just fine so I should be able to restore my phone no problem right? Wrong.
The problem I'm having is that my computer won't freaking recognize my phone when it's plugged in. Here's what I'm doing:
1) Start Odin, have phone ready in Download Mode
2) Load up the PDA file
3) Plug USB cord in to Phone
Once I plug the cord in to the phone my computer says that it does not recognize the device (or that it's malfunctioned or some such thing).
I've tried everything to fix this! Here's a weird bit of success though:
This morning I turned on my phone, did the 3-button combo to get to clockwork recovery then plugged my phone in. The phone was recognized!! I rebooted, went to download mode and Odin recognized it! At this point I tried flashing my stock kernel and it failed. Now I'm no longer able to get in to recovery using the 3 button combo and my computer no longer recognizes my USB connection again in download mode.
Am I totally screwed here? What's up with the USB??
OH! Just wanted to add: I'm using Windows 7 x64 and I do have the correct USB drivers installed.

hmmm
Have u tried redownloading the samsung drivers? They really ***** out sometimes...

I have. I've actually gone through and tried the x86 and x64 drivers listed on the forums as well as the official samsung drivers.

Usually when Windows says the device is unrecognized or has malfunctioned it has to do with the USB port you're using not having enough power. The stock Epic USB cable also sucks because its long and skinny which leads to more power drop. Try using a better quality USB cable (I always use a blackberry cable when flashing) and connect it to a USB port on the back panel of the computer that comes directly off of the motherboard.
Some USB ports may work better than others - for instance on my Dell E series laptops I can't flash when using the USB ports on the left side of the machine, but the ones on the right work perfectly. The left side ones just don't deliver as much juice and this phone is a power hungry little guy.

Alright I got it working. I do think it had something to do with the cable. I kept swtiching back and forth between Samsungs and my old Motorola one. After a few reboots and reinstalls of drivers the Motorola one finally worked

I have had that same thing happen, tried an old moment cable and problem solved. After that went on ebay and bought some extras just to have on hand just in case. Also thanks about the usb port explanation, makes sense.
Sent from my SPH-D700 using XDA Premium App

[Q] Telus Samsung Galaxy SII X

Hello everyone,
i have the Telus Samsung Galaxy SII X
i have rooted the phone
added the custom ROM (team kang)
changed the kernel.
i am going to bring the phone for repair, issues when charging the phone.
I would like to know how can i restore my phone the way it was ?
thank you

Pretty sure thetes a tut for this.
Anyways, flash stock rom
Odin recovery
Sent from my SGH-T989 using xda premium

If you don't mind me asking, what issue are you having?

the phone won't charge when i plug the usb cable
i have give it a lot of try until it finally detects and starts charging.
from a wall or usb to computer

yerem.k said:
the phone won't charge when i plug the usb cable
i have give it a lot of try until it finally detects and starts charging.
from a wall or usb to computer
Click to expand...
Click to collapse
Youve tried two different power sources, what about a different USB cable? Had that issue before where the cable was bad and only noticed when other USB devices werent connecting through it..or intermittently.

yes i tried different usb cables, different power outlets and different computer's.
also i noticed that when its actually charging on the PC, i don't get the small usb icon on the notification to copy files from pc .. i need to power off/on the phone.
ever happened to anyone ?

yerem.k said:
yes i tried different usb cables, different power outlets and different computer's.
also i noticed that when its actually charging on the PC, i don't get the small usb icon on the notification to copy files from pc .. i need to power off/on the phone.
ever happened to anyone ?
Click to expand...
Click to collapse
Ive never read that here, i have a Telus one also and it shows up right away. The odd time ive noticed that ill hear the usb unplug/replug sound from my pc and the phone will show the USB Connected on the status bar as though it somehow reset its connection. But never had an issue where it stays disconnected.
I also only got that issue with certain roms, i dont remember which though. I ran painlessly on Juggernaut for a while and right now im on Touchless and its also perfect.

I am running on Juggernaut, i recently did a clean install (wipe data .. everything) i was having few issues, i though maybe that would fix the issue.
the phone at times thinks that i have plugged the charger in to charge
and u see the battery icon changing. weird...

Have you tried charging with the phone powered down?

[Q] Galaxy Nexus USB Malfunction

Hi all. Long time lurker, first time poster here.
I have had my Galaxy Nexus for around a year now and have never had any problems - I've flashed countless ROMs and kernels, etc. However, just recently my phone has stopped being recognized by my computer(s). I've searched and searched and read every thread remotely related to the problem and still the problem persists.
At first I thought it was the new Macbook I was using, or OSX, but I've tried everything I can think of in Windows, OSX, and Linux.
When plugged in, I get nothing in OSX - finder won't find it, android file transfer won't find it, adb won't find it. In Windows, I get an unknown device in device manager, and a popup on the toolbar saying the device has malfunctioned. I've tried all three driver installs with Wug's toolkit, switching from MTP to PTP, turning Debugging on and off, flashing new roms and kernels, installing drivers manually, installing drivers through the Android SDK, even different computers - but every time I get "The USB Device has malfunctioned," or nothing at all in OSX's case. I've even tried a laptop running Ubuntu - still a no go. All the while the phone shows it is charging fine, but no indication of being connected to a PC like it used to do.
I've even tried bending the USB port a little as I've read in some guides and cleaning out the port - no luck. I have yet to try a different cable - one is on the way - but my next step is to replace the USB port board myself, unless anyone has ANY ideas.
It charges fine and never has any problems, it's just I cannot get it to be recognized by anything I plug it into.
I don't have an option to enable/disable fast charge in this ROM (currently on CM10) but I have disabled it in one of the ROMs I flashed to and still no luck.
Is there anything I've yet to try, besides using a different cable? Maybe fast charge was enabled in another kernel and it's screwed up some stuff? Although that seems impossible because I've factory reset/wiped everything and flashed different ROMs and kernels and still nothing. I just don't know at this point.
Any input at all would be great, but I understand if there's nothing else I can do besides trying a new cable and then replacing the board. I finally get going in Android development and this brick wall stops me in my tracks.
Thanks guys.

Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port

The two options you came up with yourself sounds most plausible. I've been through a ton of MiniUSB cables that have gone bad out of nowhere (just lying in my briefcase). So test that one first before buying a new USB port.

Well what do you know, it was the USB cable. I cannot fathom how a USB cable just stops working on the data side of things but still charges after just sitting around. I found another cable in a drawer, plugged it in, and voila, everything's working. Glad I don't have to replace anything, though. Woo!
Good thing is though I now know my way around the drivers and the SDK and am pretty sure I could write a guide on everything you could do to fix a USB issue. The more you know!
tuk1maar said:
Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port
Click to expand...
Click to collapse
I had been using AirDroid before and loved it. And even though it was a cable problem, I know know my USB port is squeaky clean, ha.

Nexus 7 not recognized by PC?

Hi all, I've been lurking the forums since bout September of 2012. I haven't really been posting here, mainly just gathering ROMs, kernels, help etc.
Anyways, my Nexus 7 isn't being recognized by Windows 8, Windows 7, Windows Vista, or even Ubuntu. this leads me to belive this is caused from the tablet. I have installed numerous drivers, but with no luck. Recently, I noticed when I boot into recovery, and the tavlet uis on the Google screen, my computer recognizes it as, "Unknown Device." Soon after it passes the Google screen and boots into TWRP Windows can't detect it anymore. My tablet says it's connected via AC, not USB - which is probably why I can't transfer files. I have MTP checked, and I tried PTP too. I've tried enabling and disabling debugging with no luck still. I'm using the OEM charger for the device, and I have tried using multiple cable with no dice.
"So a new possible way of fixing this after having contacted Asus support. They had me turn of my Nexus 7 and then hold the Volume Up + Power button for 30 seconds and then hold only the power button for 60 seconds. I was told this is to remove static from the mother board. USB Charging, USB Transfer, and Wireless Charging (which is what made me notice the issue) now work. The only problem I have now is that the cord that came with the tablet seems to be a bit loose and will cause it to stop charging when I don't just let it sit on a table."
That was suggested on a different forum, but that didn't work for me neither.
ADB nor fastboot cannot see my device as well.
Any help?

have you tried plugging the cable in to a different usb port?

What drivers are you using? Try the generic USB ones here, which I use with no problem at all: http://developer.android.com/sdk/win-usb.html
For best results, go to Device Manager first, set it to show all hidden devices, then delete (not just disable) any previous drivers you may have installed.
"They had me turn of my Nexus 7 and then hold the Volume Up + Power button for 30 seconds and then hold only the power button for 60 seconds. I was told this is to remove static from the mother board."
I feel like hitting my head against a brick wall when hearing such advice.

timrock said:
have you tried plugging the cable in to a different usb port?
Click to expand...
Click to collapse
Yes, I've tried USB 3 ports, and USB 2 ports with no success.

Pandae said:
What drivers are you using? Try the generic USB ones here, which I use with no problem at all: -snip-
For best results, go to Device Manager first, set it to show all hidden devices, then delete (not just disable) any previous drivers you may have installed.
"They had me turn of my Nexus 7 and then hold the Volume Up + Power button for 30 seconds and then hold only the power button for 60 seconds. I was told this is to remove static from the mother board."
I feel like hitting my head against a brick wall when hearing such advice.
Click to expand...
Click to collapse
Gotta love Asus' tech support.

Try Nexus Root Toolkit, it has a nice walkthrough that shos you how to first uninstall any existing non-working usb drivers. Then just try its options one by one and you'll have working drivers in minutes.

I gave up even trying to get my original N7 and my N7 (2013) to be recognized by any PC. What I do instead is use a free app of the day I got from Amazon a while back called Wifi File Explorer. Run the app and you can access the file system from your PC. Upload, move, copy and create folders.
It's worked for me for a while now. I'm sure there are other free apps that will do the same.
[MOBILE] Nexus 7 (2013)

VertzxD said:
Yes, I've tried USB 3 ports, and USB 2 ports with no success.
Click to expand...
Click to collapse
Have you also tried usb ports on the back of the PC? Those are directly on the motherboard, whereas usb ports on the front of a PC are almost always via a usb hub connected to the MB. I know of instances where this makes a substantial difference (device being recongnized or not). You might try it (if you haven't already).
Edit : also try disabling AV software and possibly firewall. But admitedly I have personally never had any issues regarding device not recognized due to this.

This was my solution.