Develop Bugs

[Q] insertcoin USB problem

Device: Desire GSM
I installed insertcoin 1.1.3 on monday and it seemed to have sorted the problems I had with crashing sense.
However I did have a problem with usb detection on win7 64 at one point. I had a demand for a scan pop up- this is something that occured frequently when my camera was still crashing. I cancelled the scan and Win7 sprung me a device error. That had not happened before.
I just unplugged/replugged and the issue was solved.
The next day I saw the 1.1.3 and 1.1.4 updates solved usb tethering issues. I figured why not try and updated, then flashed the kernel (without booting).
Result: windows won't recognize the device anymore, doesn't accept android usb drivers for it (the device returned an error). It is shown as unknown device in device manager. Furthermore, after trying to connect the card can no longer be mounted by the phone.
A restart sorts it, but it's still not very satisfactory. Does anyone have the same problem?
Did I flash the wrong kernel? It said bravo...
Meanwhile I'm going to go back to 1.1.2 and stay there...

Sounds like usb brick. A guide how to fix can be found here on xda.
TouchPaled from Oxygen with Transparent XDA App

Not a phone issue
Well I went back to 1.1.2, flashed a different kernel, flashed leedroid, then back to 1.1.2.. all of which gave no joy. Same issue exactly.
However finished my sick leave and it connects fine on my work pc.
So it's probably the cable and I'll check that tonight (was a bit too ill to crawl around the back of my home desk) and report.
(for those who found this by searching I guess RMD recovery is the USB Brick fix.)

No that's not the usb brick fix, it's a recovery. By using the search one can find a guide extra for usb brick.
TouchPaled from Oxygen with Transparent XDA App

So it turns out to be a faulty cable, and that is that.

[Q] usb not working

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

[Q] Statusbar USB connection -> reconnect

Hey,
i'm using the RunnyMede Xtreme v2.1.2.
Everything is working except this little problem.
If my phone is connected to the pc (usb cable) there's the notification about which type of connection i want to establish. Then i'll pick some random method (problem happens on all of them). After i applied the method and i only even touch the statusbar again, the phone like "reconnects" and asks for the connection type again. If i would set "Only Charge" for the standard connection type it is atleast working like this, but if i switch to harddrive again and then touch the statusbar again i automaticly puts the "Only Charge" method again.
Dont answer like: "Don't pull down the statusbar while having a connection established" because that wont help.
Thanks for any advice!

if your using stock kernel, try flashing rcmix or virtuous. if not, i have no idea

i Think its kernel related the virtuous is better cz the rom is based on the build of virtuous

Hmmmm
1) For sure is not kernel related. I tried all.
2) For sure is not ROM related. I tried all sense 3.5.
3) For sure I'm not sure what it is.

cable?

t0mas_ said:
cable?
Click to expand...
Click to collapse
No sorry. The phone is brand new.^^
It's not kernel related, i tried 2 different one's already. And the built in kernel in the ROM.

I am facing also this problem, as far as I know, it is common to all GB ported ROMs....

i dont think so. im using rcmix 4 and it does not happen.

t0mas_ said:
i dont think so. im using rcmix 4 and it does not happen.
Click to expand...
Click to collapse
I am using it too and it happens. In another thread somebody said that is not manifest if you have windows 7. I have win xp.
Sent from my Desire HD

could be it, im on win 7

I have the same problem, but I found a quick fix for it: reboot the phone into recovery and wipe cache and dalvik cache. This solves the problem for a few day, but then suddenly it happens again.

Weird connection-to-pc behaviour

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

[Q] Inc 2 with Evervolv: WiFi issue [Solved]

[I posted this yesterday in the wrong forum, and with fewer than 10 posts I can't post this in the developer forum. Sorry if this is the wrong place, again, but I need help.]
I have rooted my Inc 2 and was using CM 7.2 for a time; everything worked. Recently I installed a new ROM, Evervolv. I first installed the 2012.12.13 release, which didn't work well, then two nightlies: 2013.07.01, then 2013.07.03. Everything has worked on the nightlies except for a weird WiFi error. When I scrub the phone and install the Evervolv zip file, along with gapps, then reboot into Evervolv, WiFi starts right up and works normally. I can download files, sync my accounts, no problems. Then I turn off WiFi, either through the widget or through the slider in system settings, and it shuts off permanently. There is no way to turn WiFi on again. Pressing the widget makes it light up for a few seconds then go dark, and the WiFi "wedge" never appears in the top bar. Alternatively, through system settings, I will slide the WiFi bar to On, the message will appear that WiFi is turning On, but then the slider goes to Off and WiFi does not turn on.
I love this ROM and don't want to get rid of it. Can anyone suggest what the problem is? Thank you!
Kernel version
3.0.84-evervolv
Mod version
ev_vivow-eng 4.2.2 JDQ39E
----Update---
Someone on the developer forum experienced the same thing and just posted a solution: an alternate kernel http://forum.xda-developers.com/showthread.php?t=2044824&page=93
Wifi now works as it should.