Develop Bugs

The story of me and my HTC Desire

After some negotiating with my girlfriend I decided I’d buy an Android phone, an HTC Desire from PDAShop.be, where I’ve bought my previous HTC Touch 3G.
As always, the delivery of the phone was quick and soon I unpacked the phone and started playing around with it. I improrted contacts from SIM to phone and linked them to Facebook and Twitter contacts. Piece of pie. I also installed some apps and games from the Android Market (no paid apps here in Belgium, yet) and fiddled around with them, as I also did with various settings in the HTC Sense UI.
After a few hours playing with the phone, I went outside with the phone in my back pocket of my jeans, and I heard the HTC startup again. I thought that somehow I managed to press the power button by accident. Nope, the phone restarted several times on different occasions.
When I went to sleep, the phone was on and the battery was almost charged to 60%. The next morning, 8 hours later, the device was turned off and when I charged it via USB on the PC, the battery was fully drained… 0%!
I then called HTC support, and the kind person on the other end of the line listened to my story and told me I needed a hard-reset of the device. From the mail he sent me:
With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button. 2. Wait for the screen with the 3 Android images to appear, and then release the VOLUME DOWN button. 3. Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER. 4. When asked to confirm, press VOLUME UP
Click to expand...
Click to collapse
I tried that, but the phone just wouldn’t complete the hard-reset. So I called PDAShop and they told me that I could bring the phone in. I removed my SIM from Mobile Vikings and put it in my other phone and drove to them.
To my amazement the guy at the shop managed to hard-reset (without a SIM) the device, and stress-tested it with some rapid movements, changing styles in the UI, setting up a Live-wallpaper. The device didn’t freeze… So I drove back to home.
I put my SIM back in, and voila… the device started to hang on me again. I even tried the hard-reset with the SIM with no luck whatsoever. I contacted PDAShop again and the same person helped me further. He said I can send the phone back to them and they will replace it with a new one…
I really hope this isn’t becoming some part of long tragedy waiting to happen. I really want to enjoy this Android phone, as I am fed up with the current status of Windows Mobile on my brilliant HTC Touch 3G.

Hey
Sorry to heard your story, you must be very unlucky :/ . If it's of any comfort, my desire has a mobile vikings sim in it aswell and functions excellent, so it's probably a faulty model.

Sorry for you, it's probably a faulty device or a faulty ROM, either way, my phone and the ones of multiple other person works fine so keep hope!

I would advise you to recontact Coolbleu (aka pdashop) and tell them that you went there they did reset it and tested it but that it didn't fix the problem. I would be surprised if they wouldn't offer to give u a new one. (I bought several phones at coolbleu and I've always been happy with after sale support) BTW I'm also using Mobile Vikings (but on HTC Legend) and I don't have any problems with it at all.

@JonasDroid & @Cooki3s:
Good to know that, because the person at coolblue received some disturbing calls from people with MobileVikings SIM cards. How old are your SIM cards?
@All Thanks for the support, I really hope my next Desire will be somthing that I can actually enjoy
Will keep you posted.
Cheers!

I tried a hard reset again, but without a SIM and SD card inserted. This seemed to work.
I then did go through all the settings in the wizard and rebooted. Then I shut it down, inserted to SD again and I went into Settings > SD and Storage, unmounted the card, formatted it, and rebooted the phone. I stress-tested it for a while, and then I shut it down, inserted my SIM and it still works.
Could it be that some corrupt data on the card caused the instant reboots and faulty hard-resets?
I'm going to charge my phone and test it throughout the day to see if it still hangs/reboots on its own. Fingers crossed!
EDIT:
I spoke too soon... a few minutes later and the device was shut down when I tried to bring the screen back up. Now it reboots until it hangs itself... I don't hear the startup-sound either when it come to "Quitely Brilliant"
The phone will be sent back to pdashop!
Edit2:
I narrowed the problem down to a device-specific issue... It shuts down/freezes/reboots randomly even when no SIM and no SD card are in the device... I really hope the next device I'll receive doesn't have these issues

Have you got any apps installed on it? If so what? I had issues with some apps that changed the APN when the internet wasnt being used.

its a faulty device

langers1 said:
Have you got any apps installed on it? If so what? I had issues with some apps that changed the APN when the internet wasnt being used.
Click to expand...
Click to collapse
No external apps installed since first hard reset
dexteral said:
its a faulty device
Click to expand...
Click to collapse
That's what I thought also

Hey,
My SIM dates from early January this year.

I love my desire
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I bought it unlocked no problems.

jimlad said:
I love my desire
I bought it unlocked no problems.
Click to expand...
Click to collapse
Very usefull and mature. We all thank you for enlightening us!

[Q] Deadboot brick --- 7 vibrations --- what is the cause ?

This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?

Try to charge the battery in another phone and then try to turn it on using power+vol down. If that works 2.3 ruu is a solution for everything.
In my signature you have the explanation how HTC works, go to the thread and download the image.

Thanks nloooo but as I already said it - battery is ok. Tried it in another Desire - works, tried battery from another Desire in mine - phone wont work. Believe me - If there was a way for me to get into bootaloder or fastboot, I would do so by now. I am trying everything to avoid JTAG, and I wanna know why it will start once in 100 times, and why is this even happening.
looking for a motherboard online - boy those are expensive! they cost more than whole used unit ...

Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?

I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire

jmcclue said:
I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire
Click to expand...
Click to collapse
+1
HTC Sync or HTC drivers.

I installed SYNC but now im freezing phone again (so I could enter HBOOT), will post results in couple of minutes.
As im figuring out - device surely has Hardware failure, being that only frozen is able to boot. since freezing shrinks matter, my conclusion is that EMMC or CPU solder got melted by the working temperature, thus making Tin (or whatever is used for soldering these days) touching somehow on two sepparate solders, but when is frozen, they "go apart".
Once I start it, will check this -
http://forum.xda-developers.com/showthread.php?t=1284196
to determine if EMMC is fried or unsoldered.

Not sure about that thread, it points to problem with eMMC chip that Desire S has not regular Desire. For Desire the most common hardware problem is overheating motherboard issue, usual for PVT1 devices.

And that's just what im going to do - it lays opened on my table now, and there is a big design flaw - NOTHING disperses heat from the CPU cover!!!
I cant believe that HTC did this, this is just like not plugging a CPU cooler onto the motherboard of a PC.
all things aside, the problem lays in bad motherboard, and even if I purchase another one, same thing will happen over time cause CPU cant get rid of the heat.
- reflow solder (im good with that, have proper tools)
- thermal paste over cpu, before covering it back with metal
Im pretty sure this will work. phone is brand new, could get out of the factory if it had such a big flow, it must be overheating problem caused by high CPU usage. will post results later this evening, when I do a reflow soldering.

Well, I have mine for almost 2 years, used it with advance roms (sense 3.0 and 3.5) usually overclocked, sometimes it gets hot, but I can't say I had overheating issue.
The problem is not related to all devices, it's usually connected to PVT1 version of device (which was the first series) that later got fixed.

havent checked my version, but the fact is - it works! (partially) Oh, and on that topic - how do I find out my version .. ? is there a hard print .. ?
After hot air gun (reflow pin by pin could not be done, this shi* is small!) and after putting thermal paste onto the CPU - it goes past HTC logo, tries to load Sense, and then freezes. So all this trouble with software/firmware was for nothing, I guess .. I just need to reflow it a bit more, I got scared that those small pins would melt fast. Boy, I really hope this will work, cause when HW is the problem, I know my stuff, or at least I think I do ..
EDIT: well FOK MI! I dont believe this ...
I am the first to ever open this unit. I removed all the warranty stickers. On top of CPU, there IS NO METAL COVER! Nothing to act as a Heat sink! this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess this gray plate is Aluminum or iron, and the other one small is copper, but I dont have none. No wonder phone hangs 10sec after boot. Im off to make a cover, damn you HTC, how did this ever got out of the factory .. ?

Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?

ludemon said:
Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?
Click to expand...
Click to collapse
same here.. ANY SOLVE ?

Igoritza said:
Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?
Click to expand...
Click to collapse
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Igoritza said:
This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?
Click to expand...
Click to collapse
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.

Begin12 said:
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.
Click to expand...
Click to collapse
Post in the desire x forum they will help you.
Sent from my HTC Desire using XDA Free mobile app

even my htc desire x has same problem
before this happened i dropped my phone 3 times in 2 months...but the phone was still normal..but suddenly it did'nt start then i gaved my phone to a private phone repairing shop..the man told me that therz a circuit problrm in the phone and difficult to fix it.....before it i tried by power+vol down but any option does not work..same it keeps on vibrating 7 times ...what should i do now...

HTC M8 - Host Mode - Only charges in hibernation mode.

Hello, new member here. I recently purchased an HTC One M8 from AT&T, unrooted to put superuser on my phone since I really disagree with an operating system telling me what I can and cannot do with the device I purchased. I did not know about S-OFF before this issue so no, it is currently S-ON I believe.
Just to be clear, my phone worked fine after this for ~2 months at least.
Anyways, to the issue. When I try plugging in my charging cable it says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although, I do have to say not even all the time. Most of the time when it's plugged in I get zero response that it is. It didn't use to be that way, this was a progression. It started charging fine, then the Car app started booting up asking to accept or decline. The car app doesn't even open up anymore.
So here I'm thinking, either the battery is broken, or the micro USB port.
However, I CAN charge the phone if I have fastboot turned ON and I turn off the phone. It's my understanding that fastboot only puts the phone in a hibernation state and it's not really turned off. When it is in this state, I can plug my charger in and I see the battery appear on the screen charging.
This is the only way I can charge my phone, by turning it off.
I cannot communicate with a PC, I cannot charge while it is turned on. This leads me to believe that this is in fact a software issue and not a hardware issue. However, this issue prevents me from communicating with a PC through USB which removes a number of options for me to test why this is happening.
I can transfer files over WIFI, and I have done so. Yesterday I transferred Android Revolution HD 11.1 to my phone over WIFI and was able to flash it, though I think I have a bad flash and just need to reflash due to a few minutes boot time, and I already read up that you need to try a few times until you get a fast response signifying you got a good image or something like that.
If anyone has any suggestions I am willing to try them, I have everything I need from the phone backed up. I have subscribed to this thread so I should receive a notification.
Tricks that I have tried:
Turning the phone on while the sensor is facing a bright light. Not sure why that would do anything but it was a common "solution".
Powering off the device and holding the power button as well as both volume buttons. This supposedly resets the "charge mode", no result. I was able to boot up to safe mode so I learned that I guess. No it doesn't charge in safe mode.
Draining the battery 100%, holding the power button until no response. Then charging. However, this was a nightmare, as when I tried doing this I got this guys problem: youtube.com/watch?v=r_Nll_01jG0 — This only happens when fastboot is off, or in this case, the power drained and the phone actually turned off, so it clearly only charges in hibernation.
Tricks that I have not tried:
Spraying the port with WD-40 while the device is turned off. Yea okay, I guess I'm worried about putting a liquid/oil in my phone.
They ended up only being tricks, not solutions to the problem. IF it was hardware I would understand completely. I no longer get a response from the phone when it is plugged in except for the occasional error message as the image above. HOWEVER, it charges in hibernation mode, every attempt, nothing weird, it just charges like it should. This is weird to me, because if it was hardware then this should not work. It makes no sense.
I tried an app called USB Host Diagnostics, I'm not sure if this is even going to provide any information to help or not but here is the result: usbhost.chainfire.eu/?search=455254
Since I've changed the ROM / OS of the phone to Android Revolution HD 11.1, and the problem still persists, then the next step down would be the... kernel? So it is either hardware or the kernel? That's just me guessing really... it's so hard to imagine it's the hardware. I take great care of my phone, never dropped it, don't overcharge it, I just don't understand what it could be other than the software of the phone just not recognizing the port while it is turned on, and whatever functions are turned on during hibernation are working correctly. Unless it's a voltage issue where it disables it to protect the motherboard, and during hibernation it isn't a risk, if that's even a thing. If it was a voltage thing, why then would it not charge when fastboot is turned off and the phone is off? It starts up with a battery on the screen then reboots in an endless loop like the video showed above. I just don't understand, wish there was something more to figure out other than it telling me that it's in host mode and can't charge, and by extension can't connect to a PC.

I found something out while just randomly rebooting the device. I rebooted my phone while it was still plugged into the computer and opened up the... bootloader? (Power button + volume down), and then I went to the Fastboot option and I heard the chime on my computer of a new device being detected, and it installed android 1.0 driver or something. I wasn't able to see storage or anything (probably because I was in a bootloader), but I actually heard a response from my computer.
If I toggled between the main menu and FASTBOOT the chime would go on and off between detected and removed.
This really makes me confused, it has to be a software issue right? I've reflashed the android revolution HD ROM multiple times so I don't think it's that... is it my kernel? I am so lost here. The fact that my computer made that chime and installed a driver proves that it can work, but why won't it work when it's turned on?

Hi b.white,
Have you found any solution.
My HTC has shown the same USB in OTG so can't charge problem. It is the first time I have seen this message and problem on my phone. I have my phone for the last few months. I also want to mention that it is as stock as it can get. Never even rooted. I have no popping up CAR app problem. Maybe because it is just been a few minutes the problem showed up. So maybe I'll be seeing the car app later on. But I had about 10% battery on my phone which died out during the few tests I've made.
So right now my phone is turned off (because of battery got to 0%) and is plugged in using standard cable and charger in to a wall socket. It shows that it is charging by using the animation and the percentage is growing continuously. The LED is stable and Amber which means that it is charging.
During the last few battery moments, I turned off the car app through its settings. Never had the daydream setup or turned on anyway. But my fastboot from the settings is off. It was like this when the phone came, and never needed to change this setting.
I also tried this but I'm not sure that I did it correctly and it hasn't showed any difference either.
http://forum.xda-developers.com/showpost.php?p=46415840&postcount=1
While I was keeping the three buttons pressed the phone kept turning on the the htc logo and going back to black screen. I don't think that should have happened, or at least the original thread didn't mentioned this behavior.
This is my main phone. And I am really worried about this problem.
Please help. :crying:

USB Host Mode charging issue (plus Car Mode) just started happening to me last night. I can intermittently charge while the phone is on, but it's inconsistent. Nothing I've tried so far has fixed it for more than a few minutes. Probably will have to send it in for warranty service.
Sent from my Nexus 7 using Tapatalk

OK, so now after I charged my phone to 100% while it was off and turned it back on, I am also having the same CAR mode app problem.
Maybe the latest update that is coming our way can solve this problem. I am talking about the update with the EYE enhancements etc.

Wifi and USB not working

Hello:
I have a Pumpkin head unit Model S07 - MTCB-KLD2 migrated to Malaysk ROM 4.4.4, and everything was working until suddenly the internal WIFI didn't work anymore.
Decided to make a new upgrade, I have actually the Lollipop Android 5.1 Malaysk ROM for RK3188 1024x600, and I wasn't able to had the Wifi working. After reading posts in this Forum I've got the chance to put a Wifi USB dongle into one of the USB external ports, and for my surprise I've just discovered that both USB's are not working anymore, so actually I have a broken radio in actual state.
I've also noticed that the internal beep sound has changed to a new one, and furthermore whenever i try to get into the Recovery mode pressing until the three beeps come out, 2 seconds after this 3 beeps sounds a long beep, and the bootup menu doesn't show, so I couldn't try to update the firmware anymore.
Did you think that going back to the original Pumpkin firmware will solve the problem? Is the WIFI faulty, as I've read before, so common in these units, and there is not any workaround possible to fix it? What about the USB's broken how could I check it up? Anyone know if there exists any APP to check system LOG faults to try to guess the workarounds with all this faulty hardware? Exactly one year after I' ve bought the unit is starting to give the problems I mentioned before, programmmatic obsolescence?
Thanks for the hard work!!!!
Greetz from Madrid.

Nobody?
twelvemonkeys said:
Hello:
I have a Pumpkin head unit Model S07 - MTCB-KLD2 migrated to Malaysk ROM 4.4.4, and everything was working until suddenly the internal WIFI didn't work anymore.
Decided to make a new upgrade, I have actually the Lollipop Android 5.1 Malaysk ROM for RK3188 1024x600, and I wasn't able to had the Wifi working. After reading posts in this Forum I've got the chance to put a Wifi USB dongle into one of the USB external ports, and for my surprise I've just discovered that both USB's are not working anymore, so actually I have a broken radio in actual state.
I've also noticed that the internal beep sound has changed to a new one, and furthermore whenever i try to get into the Recovery mode pressing until the three beeps come out, 2 seconds after this 3 beeps sounds a long beep, and the bootup menu doesn't show, so I couldn't try to update the firmware anymore.
Did you think that going back to the original Pumpkin firmware will solve the problem? Is the WIFI faulty, as I've read before, so common in these units, and there is not any workaround possible to fix it? What about the USB's broken how could I check it up? Anyone know if there exists any APP to check system LOG faults to try to guess the workarounds with all this faulty hardware? Exactly one year after I' ve bought the unit is starting to give the problems I mentioned before, programmmatic obsolescence?
Thanks for the hard work!!!!
Greetz from Madrid.
Click to expand...
Click to collapse

http://www.autopumpkin.com/forum/viewtopic.php?f=3&t=777

As you could suppose I've read it, the problem is the USB malfunction that doesn't allow the workaround showed there.
Here there's a LogCat of the system when WIFI enabled:
paste board . co / n8j6icCLW.jpg

I've written in many forums as it's supposed to be a generelized problem with resellers as Eonon, Joying, Pumpkin (mine), and all those HuiFei type brands. Some of them tried a workaround setting the Date/Time not to be automatic and fied the Wifi, but no chance whenever USB/Wifi are both broken. The Pumpkin reseller asked to return the HA and charging for the fix of the PCB!!!, it sounds like I have to open up the HA, dismantle it and send it back to factory to fix. My unit it's actually exactly 1 year old, and I will be without radio until receivng it, wait for fix and resend it to me from China, charging me with a repair fee and the billing costs, and no radio plugged in my car!

Wifi and USB Fixed
Finally I've got the solution with the unvaluable Help from ZelenyR that helped me on the full process.
I've guessed that some internal resistance, capacitor, inductor was burnt, and tried to find following the PCB routes all over the circuit what in the hell were, tried to find a little burn in some of them and find finally that a small inductor L9 (all of them are inductors beginning with a 'L') did not showed on the multimeter as nornally should do, verified that is a component very sensible to tensions peaks produced because of over tension when connecting external USB electronics such as a mobile, or ext HDD. On ZelenyR's words: "The problem is inductance which you need. I used 220nH for 3.5Amp main parameter was max current over 3Amps to be sure that it will not burn again. Easiest way is just simply short this component but I don´t recommend it because it is not safe and can go to bigger damage in case of overloading USB and also it is necessary to block supply noise going to WiFi ."
Thanks to him I'm actually repaired my init luckily!!! and saved 100€ and 3 months without the unit.
Greetz

Bad eyes
I have same problem after iphone 4 was connected thru usb interface, wifi is off and cant be ON. Where is L9 located ? Try to find it about an hour...

this is....
SwIFTop said:
I have same problem after iphone 4 was connected thru usb interface, wifi is off and cant be ON. Where is L9 located ? Try to find it about an hour...
Click to expand...
Click to collapse
It's located as L19 you could see that is slightly brown (it means it's burnt) at the middle bottom of the image in a row that reads: "C103 Q9 R134 L19 R131 Q6 R128"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

twelvemonkeys said:
It's located as L19 you could see that is slightly brown (it means it's burnt) at the middle bottom of the image in a row that reads: "C103 Q9 R134 L19 R131 Q6 R128"
Click to expand...
Click to collapse
Can you mark the on the picture where the burn is? I cant see anything by L19 just the writing.

typos1 said:
Can you mark the on the picture where the burn is? I cant see anything by L19 just the writing.
Click to expand...
Click to collapse
Oh dear!! count the chips!! the legends are in the same row(1st legend, first chip, 2nd legend 2nd chip,...), it's the fourth one chip

twelvemonkeys said:
Oh dear!! count the chips!! the legends are in the same row(1st legend, first chip, 2nd legend 2nd chip,...), it's the fourth one chip
Click to expand...
Click to collapse
Chips ? Youre not talking about chips youre talking about an inducter. I can see the legends but nothing near them to show what the legend is referring to. And besides, the quote in your post says its "L9" not "L19" as you say.
Can you mark on the picture where ? I am not thinking of me, but or anyone who reads this to be able to see for reference should it happen to someone else.

Same thing happened to mine. My wifi and both usb doesn't work anymore after 8 months of use. 11-RQ0369E-US part number. I wonder if the board is the same as mine. I haven't open it yet, just wanted to confirm that it's something within the board. Everything else works except what I've described. I usually would play music through the usb. Where did you get the inductor?

za_ny said:
Same thing happened to mine. My wifi and both usb doesn't work anymore after 8 months of use. 11-RQ0369E-US part number. I wonder if the board is the same as mine. I haven't open it yet, just wanted to confirm that it's something within the board. Everything else works except what I've described. I usually would play music through the usb. Where did you get the inductor?
Click to expand...
Click to collapse
Have you tried updating the MCU ?

typos1 said:
Have you tried updating the MCU ?
Click to expand...
Click to collapse
No, I haven't. How would I do that, unless I use a sd card. Where would I get the update if there was one. I'm running the 5.1

za_ny said:
No, I haven't. How would I do that, unless I use a sd card. Where would I get the update if there was one. I'm running the 5.1
Click to expand...
Click to collapse
It doesnt matter what Android version youre running. MCUs are in the links in my signature, try an MTCC one if you have a Klyde (KLD), this is an update to MTCB

typos1 said:
It doesnt matter what Android version youre running. MCUs are in the links in my signature, try an MTCC one if you have a Klyde (KLD), this is an update to MTCB
Click to expand...
Click to collapse
signature, try an MTCC one if you have a Klyde (KLD), this is an update to MTCB[/QUOTE]
I see the firmware but it's kind of confusing me though. My MCU version is MTCC-KLD6-V2.91 May 31 2016. So I would have to download the MTCB-MTCC_lolipop_5.1.1 but noticed there are a custom and official. Should I download the official one? Thanks.

za_ny said:
signature, try an MTCC one if you have a Klyde (KLD), this is an update to MTCB
Click to expand...
Click to collapse
I see the firmware but it's kind of confusing me though. My MCU version is MTCC-KLD6-V2.91 May 31 2016. So I would have to download the MTCB-MTCC_lolipop_5.1.1 but noticed there are a custom and official. Should I download the official one? Thanks.[/QUOTE]
Neither, the MCU is separate from the ROM, I suggestd you try updating the MCU not the ROM, updating your ROM will likely not help your problem.
Try the MCUs attached, the later one first, if you get any problems try the earlier one.

Try the MCUs attached, the later one first, if you get any problems try the earlier one.[/QUOTE]
I've tried both of them and I still see the wifi being off and the USB doesn't work as well. Thank you for your time though, I appreciate it.

za_ny said:
Try the MCUs attached, the later one first, if you get any problems try the earlier one.
Click to expand...
Click to collapse
I've tried both of them and I still see the wifi being off and the USB doesn't work as well. Thank you for your time though, I appreciate it.[/QUOTE]
That was just the first thing to try.
When you say "the wifi being off", what happens when you turn it on ? USB is always not very good for various reasons, adding more power to it may help.

That was just the first thing to try.
When you say "the wifi being off", what happens when you turn it on ? USB is always not very good for various reasons, adding more power to it may help.[/QUOTE]
The wifi remains grey out in the on position, then it goes back to being off again. Before when it wasn't broken, I could turn it on and it would search for wifi but not anymore. For the USB, I can no longer use it at all. I was reading the circuit board share the same circuit so it wouldn't surprise me if it needs one because both the wifi and usb failed and stopped at the same time while driving.

Charging Problem

I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?

buugiewuugie said:
I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?
Click to expand...
Click to collapse
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.

sb1893 said:
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.
Click to expand...
Click to collapse
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.

buugiewuugie said:
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.
Click to expand...
Click to collapse
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also noticed from your link that my USB options look completely different than Oreo and Pie

sb1893 said:
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....
Click to expand...
Click to collapse
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.

buugiewuugie said:
I also noticed from your link that my USB options look completely different than Oreo and Pie
Click to expand...
Click to collapse
Ehhh - that article was from back in March 2018 so likely based on one of the developer previews of Android P....I'm guessing it evolved a bit since then from a visual standpoint - mine looks the same as yours does...
---------- Post added at 10:50 AM ---------- Previous post was at 10:47 AM ----------
buugiewuugie said:
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.
Click to expand...
Click to collapse
If you are unlocked I would just flash the latest factory image. Be sure to remove the "-w" from the flash-all.bat if you want to retain your data. (Although, depending on where that default preference for charging behavior is stored - retaining data may retain that "bad" default value as well.) Maybe try factory flash with retaining data first and see if it works...before doing the full factory flash and needing to reset up the entire phone and restore your data manually.

Another one bites the dust
Exact same problem with my Pixel XL.
It's difficult to charge the phone because every short power disconnect I have to manually choose "this device" again on else it won't charge.
I'm not rooted but bought it unlocked.
Grts
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
https://www.multitopicblog.com/usb-supplying-power-attached-device-pixel/#comment-133

Same Problem
I have the same problem with my Pixel 3 XL. Did you find a solution?

Just started experiencing this issue 8/1/2019 on a standard Pixel XL

Same issue, started in September. It's completely killed Android Auto for me and routinely leaves me with a dead battery. I've found mention of the issue all over the net but no solution. If anyone comes up with something, please share, it's driving me nuts.
Pixel 2 XL on Android 10 (QP1A. 191005.007.A1)