[Q] Kernels and charging

[mhoffman54]

I've been messing around with roms for a while now, and I've finally chosen one that I really like, but the other day I decided to start playing with kernels, and I flashed netarchy-toastmod-4.3.2-cfs-sbc-havs-more-universal-signed. Once I flashed it, my phone would no longer charge at all. When I plug it in, the orange charging indicator would come on for just a second, and then turn off as if I unplugged it.
I had this happen once before, when I installed the fullHDMI app, I read that if I installed a custom kernel I would get better performance, and the same thing happened.
Luckily I am OCD about most things I do, and I ALWAYS Nandroid, so I was easily able to revert back to my former rom and kernel with no problems.
And the last time, my phone would charge fine if it was off, so worst case scenario, until I did a restore, I could get by just turning my phone off and charging til it was ready. But this time, my phone wouldn't do either! When its on, again, light comes on for a second, then turns off. And when its off, I don't even get that much!
I have never had an official htc charger (bought my phone on Craigslist and the guy "forgot it"), but I used to use my old Samsung Reclaim charger with no problems. Therefore, I can't remember whether or not the charger I'm currently using (stupid Rocketfish micro usb charger from best buy) ever charged my phone when its off.
Which brings me to my question, really. How do kernels affect charging on the Evo? I've read elsewhere about people having issues after flashing a new kernel. And really, does it matter if you're using an aftermarket charger or the OEM htc charger?
I would love to be able to play with new kernels and see what's best for my battery life, but every time (btw, if its relevant, the 2 times I've tried flashing a kernel without a full Rom I've had charging issues) I've tried I run into trouble, and I am terrified that I'll flash and forget, and won't have enough battery life to restore to my old kernel!
Edit: Also, whenever I forget my charger at home, I can usually find one laying around at work, and the one I usually use, some AT&T micro usb charger, has never worked unless my phones off, even with the built in kernels. It works perfect, on or off, with my buddys stock, non-rooted Evo. I haven't tried it lately, so I'm not sure if it'll even charge while off. I just feel like my charging issues are kernel related, and I wouldn't think the kernel would affect anything while the phone is turned off? Do different kernels work only with certain chargers? And do some chargers only work when enabled by certain kernels? I find it hard to believe that there's anything physically wrong with my phone when I can always restore and get it working again, but at the same time, its weird to me that some work while my phones off, and others do not.

 

[mhoffman54]

Update: Just tried the Rocketfish charger while off. Phone does not respond to it whatsoever.. I need my Reclaim charger back! But again, this raises the question, do some chargers only work when enabled by certain kernels? Why would this charger not work when the phone is off, when no software is running, but work fine when its on and certain kernels are running??

 

[mhoffman54]

Nothing??
Does anybody know anything about this?

 

[gotshores]

that's weird man. if your phone isn't charging even when the phone is off, then it's not kernel related, it would be hardware related (possibly your charger port on the bottom of the phone) i read somewhere that the charger port has been reported to break off easily. have you connected it to a computer to see if the computer recognizes it?

edit: i noticed you were using an SBC kernel. I'm not gonna get into the whole debate about if sbc fries batteries and stuff, but have you tried swapping out your battery for another one? maybe the battery is fried?

 

[blakeboys]

that's weird man. if your phone isn't charging even when the phone is off, then it's not kernel related, it would be hardware related (possibly your charger port on the bottom of the phone) i read somewhere that the charger port has been reported to break off easily. have you connected it to a computer to see if the computer recognizes it?

edit: i noticed you were using an SBC kernel. I'm not gonna get into the whole debate about if sbc fries batteries and stuff, but have you tried swapping out your battery for another one? maybe the battery is fried?

I think its your charger too. I've had other phone (hybrids..yuck) that were very charger sensitive so it would not surprise me at all. THIS is the same charger that came with the phones so it will work or if your an ebayer like myself than go THIS route since its cheaper. And I've used SBS kernels since they first arrived on the seen and still to this day have had no problem, but everyone is different.

I also have had a phone with a broken usb port. It wont let you charge unless the port is wiggled just right and as soon as the phone is moved itd stop charging. Your issue definitely sounds like a charger problem to me.

Also, next time try to sum everything up in a paragraph or so. Many people will turn down a question when they have to read an essays worth of info.

 

[mhoffman54]

Yeah sorry, I know I wrote a novel. I was kinda drunk and wanted to get the facts out there. I know my problem is not hardware related though. Charges perfect, no wiggling required, while my phone is on. Won't charge whatsoever, no matter how much I wiggle, with the phone off. It's just weird to me..

 

[mhoffman54]

And the second the kernel loads after the boot animation (screen dims and 4 softkeys light up) my phone starts charging. Can a kernel make a charger that's not compatible compatible?

 

[blakeboys]

I believe the kernels are based off of HTC Stock Kernels, they are just tweaked to achieve greater performance. I've never seen any evidence of Dev's adding/removing charger compatibility so Id say its safe to say no.

... I was kinda drunk...

Nuff said! Been there. lol

 

[k2buckley]

Yeah sorry, I know I wrote a novel. I was kinda drunk and wanted to get the facts out there. I know my problem is not hardware related though. Charges perfect, no wiggling required, while my phone is on. Won't charge whatsoever, no matter how much I wiggle, with the phone off. It's just weird to me..

And the second the kernel loads after the boot animation (screen dims and 4 softkeys light up) my phone starts charging. Can a kernel make a charger that's not compatible compatible?

I've never experienced anything like that before. Very strange. I wouldn't think that a kernel would prevent the phone from charging while the phone is powered off. I also wouldn't think that a kernel could make an 'incompatible' charger 'compatible'. If the charger is Micro USB, it *should* be compatible. I always use the charger that came with my phone, but I have used other ones in a few different instances, and have never had a charging issue whatsoever. Some chargers have different ratings, such as 1Amp charge output, or .5A charge output. Generally USB and car chargers charge at .5A, while wall chargers charge at 1A. The Evo should charge with either one, as long as the cable is Micro USB. I just don't see how a charger could even be 'incompatible', unless the charger itself was no good. My guesses are, either a bad battery, or a bad connection where the battery makes contact. Or, a hardware issue. There is a known problem for some Evo's, where the solder joints that connect the USB charge port to the motherboard fail. Poor solder joints. That could be your problem. I just don't buy that it's software related, because the phone should charge when it's powered down, regardless of the software. However, it is strange that this happened right after changing kernels, and nandroid restoring to your previous setup alleviated the problem...that is strange. I guess the easiest and least invasive thing to try would be flashing a few different kernels, and see how different kernels affect the problem. If the problem persists no matter what kernel / rom combo you're on, then it's not software related. If the problem goes away when you change kernels, then maybe somehow it is software/kernel related. It's just very odd.