Just flashed Android Revolution HD 4.0. It works fine, however the USB debugging always on even when I disabled it. Anyone have the same issue?
Why would you want to disable it?
Just leave it on, it won't hurt.
Hmm... However, it's gone after I rebooted.
Related
So I have been having some trouble lately. I'm running the latest versions of everything and have been having a few USB problems. First, my phone was mounting as a usb device even when set to charge only. Then, USB Debugging stopped working. I redid the entire thing, using the PC36IMG.zip that contains the image for the latest OTA and Radios and patching with Superuser. It worked for a while, then a couple days ago the charge only stopped working again. Now my Evo rebooted on its own while plugged in, something I've heard of but never experienced with any Android phone. After the reboot, USB Debugging stopped working again. Please, if anyone knows what I can do to fix this, please help. I'd be willing to give more information if needed. I'm fairly good at ADB, but can't seem to fix this problem. Thanks.
Hello, I have recently upgraded from ARHD 2.13 to the latest 3.2, and I've noticed that once I connect the phone to the PS3 via USB, the phone completely freezes. This has never happened with 2.13. I have found a similar thread regarding this issue, with no solutions however. The USB freeze ONLY happens on PS3, PC works fine.
http://forum.xda-developers.com/showthread.php?p=12169141#post12169141
As you can see, it happens with Inspire 4G, and I am using DHD.
I would report this problem myself in the main thread, but I can't due to postcount limit. Could someone please confirm this and report in in the main thread?
My thoughts on this is that it might have to do with the Inspire compatibility, as ARHD 2.13 was only for DHD, if I remember correctly, and it did not have this issue at all.
Lastly, I have flashed 3.2, no-sense, advanced power menu and the 3.1 performance patch, if needed to know. Thanks alot!
Hey guys
i recently flashed codename android 1.3.3 and i could no longer mtp host so i switched roms and still not dice i flashed every kernel and nothing is working does anyone know how to fix this or and i screwed. to be clear my phone still charges it just wont mount to transfer files. adb does not recognize that a phone is plugged in either
thanks in advance for all the help
Matt
Mine is doing this now as well following AOKP Build 23. I haven't bothered flashing anything else yet as I was doing preliminary research before work to try to find out exactly what happened and how I could fix it. (No answer yet).
Edit: I found a solution. It won't automatically turn on anymore, but I can turn it on manually under Settings > Storage. Problem fixed (for me anyway).
no idia??how can improve this
i tried that still not working is there any way to uninstall the drivers from the phone?
Had this problem after installing AOKP 23 too. Have to turn on manually.
Working now.
Could be that you have a faulty USB port. Many have reported about this here http://forum.xda-developers.com/search.php?searchid=15930021
My GSM unlocked GN, running original ROM IMM76D with Franco kernel Milestone 3, stopped responding to being plugged into a USB port using the original cable (I don't have another cable atm). I just wanted to change some music I had on it and I realized it just doesn't detect the phone.
Since I tried an OTA update to IMM76I that didn't work, I thought it might have fiddled with something, so I decided to upgrade to IMM76I using the trusted toolkit which I've already used several times.
[on win7 sp1 64bit]
I managed to browse the phone when it was in recovery mode (ADB), and take off it my various backups - not via the toolkit. Flashed, unlocked, rooted, the works. Restored apps. Plugged back into the computer... Nothing. The computer reads it when in fastboot or recovery though. If the device is plugged in before fully booting into Android, it works fine. If I unplug it and try again - when android is fully up and running - no cigar. It doesn't even read on the toolkit. Receives power though.
I've tried connecting the phone to other computers (other win7 no sp1, xp), still nothing. That's why I assume it's a phone software problem, but I can't figure out what. Did anyone encounter this phenomenon?
Do you have fast-charge enabled?
Also make sure MTP is checked in Settings>storage>options.
MTP is on and always was.
I have supercharging on via the franco app. I'll try turning it off and plugging it in when I get home.
Sent from my Galaxy Nexus using XDA
That is why. If you disable USB fast charge it'll work great again.
Only use fast/supercharge, if you're in a hurry to charge your phone, like in a train, or something...
When you're at home, just leave everything as it is, and you'll never have problems, like that...
If that then doesn't work, reinstall the drivers
thanks people! I'll send franco an email about mentioning that supercharging disables data right next to the enabling tickbox.
Not home yet...
Sent from my Galaxy Nexus using XDA
Whenever i connect phone to pc, the option on the phone on whether i charge only or mount etc, doesnt show up. Even after a fullwipe problem persists. I have to mention that this came up after installing v6supercharger, but even after fullwiped and reinstall rom, still cant make it work. Any help will be welcome!
Using GingerSense4 with RCmix3d v12 kernel
Also, the PCSCII.apk is installed, and reinstalled, but the service is not running (under Application-management-services).
Problem semi-fixed. Flashed the PCSCII.apk from this guys thread: http://forum.xda-developers.com/showthread.php?t=1559683&page=9
But you have to untick the "ask me everytime i connect" button on settings, and manually change whatever you want.
I'm having this same exact problem, and tried all the same things; I've been scavenging the internet for a fix, but have yet to find a solution.
In my case I'm on a rooted Inspire(same as Desire) HD, running Android Revolution HD ver. 6.3.1. This problem didn't occur right after any of that though, It's been working fine this whole time up until 2 days ago(to my knowledge at least). "Funny" thing is I've had this happen before with this same model of phone, and that one wasn't rooted.