Database Users

No charging LED after Flashing ROM

Hey everyone I flashed evervolv and now my phone wont display that it is charging, it is still charging but the LED doesnt come on is there a setting for this or whats going on?

Blitzpwnage said:
Hey everyone I flashed evervolv and now my phone wont display that it is charging, it is still charging but the LED doesnt come on is there a setting for this or whats going on?
Click to expand...
Click to collapse
Just the way he cooled his rom, nothing wrong with the led, it won't show charging till you hit 90%, then it'll show the green charge light however.

tomh1979 said:
Just the way he cooled his rom, nothing wrong with the led, it won't show charging till you hit 90%, then it'll show the green charge light however.
Click to expand...
Click to collapse
I don't think it was a coding option I think that's a Gingerbread thing.

Badious said:
I don't think it was a coding option I think that's a Gingerbread thing.
Click to expand...
Click to collapse
Well, not specifically a Gingerbread issue, but the fact that because it's AOSP, it's not built specifically for the Evo and thus hasn't been coded to use the Evo's LEDs.
That's how I see it at least.

Phone restarts when the led flashlight is on for 60 seconds?

On every rom I have used, when I'm outside in a pitch black situation and I need my flashlight on my phone. When I leave it on for more than 60 seconds, the phone automatically restarts. I suppose because the LED gets too hot? This is on Torch bright widget or widgetsoid flashlight using method 2 for led. However I'm fairly sure that using heart rate monitor app in the market the phone can stay on with the flashlight for more than 60 seconds. I'm going to test this now. This is weird since my HTC HD2 could leave the led flashlight on for hours if I wanted. Well I never had it on for more than say 20 minutes but it worked and the phone never restarted. Any help would be great, thanks!
By the way this happens on all roms including with all kernels and all radios.

I wouldn't leave it on for more than 10 seconds at a time. That is just plain stupid.

Damn I hate useless replies!
Sent from my MB860 using XDA Premium App

Ok try this out. You're going to burn out your LED and the reason it restarts is from the heat. When you take a pic in your camera app does the LED flash for 60 seconds? um no.... you need a flashlight? Get those small LED keychain ones.. how's that for useful? Use your head....

And tour HD2 does not have a Tegra 2 in it so perhaps why that one does not overheat. Either way you'll kill the LED. They aren't designed to be used like that.

I have the exact same problem on CM7 - was fine on my HD2 for a very long time too

At times I find myself needing a flashlight for a minute or 2 at times. The HD2's LED never overheated unless you left in death ray mode but I'm not sure since I can't remember ever having a problem ever. Just use regular brightness at a reduced continuous voltage therefore reducing heat production. That's not stupid to need my f*ing phone as a flashlight for a couple minutes when needed. LED's are very efficient and can take a hell of a beating, however they're efficient in nature so leaving it on may reduce it's life sure. But has anyone reported their cell phone led light going out? I have never heard of it so stop posting stupid idiotic comments. Posting dumb offensive comments makes you look stupid. You could respond with an intelligent response unleashing to the world your hidden genius. Instead you decide to do what you do best.
If anyone who may be having the same problem. I have found a solution to the problem. Downloading instant heart rate monitor will allow the light to stay on forever with no problems.
Later

Atrix_E said:
And tour HD2 does not have a Tegra 2 in it so perhaps why that one does not overheat. Either way you'll kill the LED. They aren't designed to be used like that.
Click to expand...
Click to collapse
I'm sorry. I do understand you stating they aren't designed to do that. However I don't care what you think about cell phone led's. I asked a question therefore I would expect an answer. Not an electronic's lecture.

1chris89 said:
I'm sorry. I do understand you stating they aren't designed to do that. However I don't care what you think about cell phone led's. I asked a question therefore I would expect an answer. Not an electronic's lecture.
Click to expand...
Click to collapse
That was my answer. Sorry that you do not like it. Why not troll on now about video playback on your HD2?

Had the same problem with widgetsoid.
Download Tiny Flashlight + LED from the marketplace. My 60 second reboot problem does not happen with this particular application. I am on stock at&t rom rooted.
Sent from my MB860 using XDA App

Atrix_E said:
That was my answer. Sorry that you do not like it. Why not troll on now about video playback on your HD2?
Click to expand...
Click to collapse
Well my suggestion is to you. Next time you post a comment. Please take a moment to think about the question. So then you can give a helpful answer. Questions are meant to be answered, nothing more and nothing less.

jmaddr said:
Had the same problem with widgetsoid.
Download Tiny Flashlight + LED from the marketplace. My 60 second reboot problem does not happen with this particular application. I am on stock at&t rom rooted.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks buddy! I will give that app a shot. As for the moment. Instant heart rate monitor from the market works wonderfully.

1chris89 said:
Well my suggestion is to you. Next time you post a comment. Please take a moment to think about the question. So then you can give a helpful answer. Questions are meant to be answered, nothing more and nothing less.
Click to expand...
Click to collapse
Noted and thought about. Wouldn't change my answer.

First of all you don't have to be a flamer, second....you have no clue what your talking about. The led light is led ...led lights put out insanely low amounts of heat...which is why that technology has been incorporated into growing plants...not that it's good ti leave the led on for too long but I have uses the led flashlight for about 30 minutes before on my ATRIX, ya it gets a little warm but that's it. Yes it's possible to burn it out over time but you will be fine for short durations. Why do you think there are so many flashlight apps, if they really caused that much damage google would remove those apps from the market.
And im not talking out if my ass because I know quite a bit on the topic of led technology.
The possible reason for your phone rebooting is because a lot of the flashlight apps out there aren't compatable with the ATRIX for some reason, don't ask me why. You need to download "droidlight" from the market because it was developed for Motorola phones by Motorola ...then I doubt you will be rebooting
But please don't talk like your an expert on the subject and give false information to people because it just adds to confusion for those that don't know. Im no expert on everything so I don't chime in on things I don't know about. Cheers
Sent from my MB860 using XDA Premium App

Atrix_E said:
That was my answer. Sorry that you do not like it. Why not troll on now about video playback on your HD2?
Click to expand...
Click to collapse
Also you should be suspended by mr.clown for a comment like that.
Sent from my MB860 using XDA Premium App

Tiny flashlight +led works great. Has a good widget as well. Don't recall having a timeout. Accidentally turned it on and fell asleep for hour. Woke up to a dead battery and a brown spot on the coffee table lol. Led was still kicking an hour later. I use mine all the time.
Sent from my MB860 using xda premium

Its more than likely the app, I have the same problem using Tesla led + widget locker + cm7. Disregard about damaging your LEDs, as long as the proper voltage is applied... they will never burn out... if its getting HOT(not warm) then I would be worried. LED lights do have a "lifespan" but generally exceed it, tremendously.
Sent from my MB860 using XDA Premium App

J-Roc said:
First of all you don't have to be a flamer, second....you have no clue what your talking about. The led light is led ...led lights put out insanely low amounts of heat...which is why that technology has been incorporated into growing plants...not that it's good ti leave the led on for too long but I have uses the led flashlight for about 30 minutes before on my ATRIX, ya it gets a little warm but that's it. Yes it's possible to burn it out over time but you will be fine for short durations. Why do you think there are so many flashlight apps, if they really caused that much damage google would remove those apps from the market.
And im not talking out if my ass because I know quite a bit on the topic of led technology.
The possible reason for your phone rebooting is because a lot of the flashlight apps out there aren't compatable with the ATRIX for some reason, don't ask me why. You need to download "droidlight" from the market because it was developed for Motorola phones by Motorola ...then I doubt you will be rebooting
But please don't talk like your an expert on the subject and give false information to people because it just adds to confusion for those that don't know. Im no expert on everything so I don't chime in on things I don't know about. Cheers
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I mean I don't really know anything about it, but if my LED light is on (for a flashlight) it get's noticeably hot within like 10 seconds...
I haven't quite had the same problem as the OP, but I was using TeslaLED with Widgetsoid (had a flashlight toggle in my rotary slider). I turned the screen on, and without unlocking used the flashlight like normal a few days ago, and had it on for 10+ seconds (after 10, my screen timed out like normal). I went to turn the screen on again though, and my entire phone froze - with the LED still on! I had to remove the battery...
I dunno all the technicalities of the LED, nor do I know if this was a freak accident and won't happen again (hopefully!). Might be a problem with TeslaLED/Widgetsoid, or maybe the screen shouldn't go off when the LED is on?
EDIT: Weird, I just tried it out again for fun, and it did in fact freeze my phone again lol. It did the exact same thing: turn on screen, turn on flashlight, use for like 10 seconds. Screen times out, flashlight flickers. Turn screen on, looks normal, but try to turn flashlight off, feel slight haptic feedback then froze.

Being an electrician by trade, I also specialize in luminaire devices, and tend to push LED devices over traditional flourescent, incandescent, halogen & HPS/MH lamps, for various reasons & applications. In fact LEDs last longer than the auxiliary components driving them .. which is why the still have a rated life span, many suppliers guarantee 12,000+ hours.
Sent from my MB860 using XDA Premium App

JaronBang said:
Its more than likely the app, I have the same problem using Tesla led + widget locker + cm7. Disregard about damaging your LEDs, as long as the proper voltage is applied... they will never burn out... if its getting HOT(not warm) then I would be worried. LED lights do have a "lifespan" but generally exceed it, tremendously.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I don't know about everyone else but my led starts getting hot after only having it on for ~10 seconds. I try not to leave it on because of the heat. But yah I do leave it on for more than a minute all the time so it was probably the specific app causing a rare OS bug that caused it to crash.

Be carefull with the new ICS ROMS. Always shut down by holding the button for 20 secs

I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.

Thanks!
Sent from my Kindle Fire using xda premium

It happened to me already, but it woke up with the original charger.
Thanks!

yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery

It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.

This just happened to me...
My kindle died after shutting down for one day. No battery at all...

Did you even read the first post of the kernel thread?

ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA

StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.

If the devs were offered a dime every time somebody failed to follow directions...

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.

Not going to argue with you on that one.

ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?

@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.

umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.

This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2

It will always work best with the stock charger, but until the bugs are fixed, who knows.

KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).

For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA

[Q] HELP!! Phone died, wont charge

Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?

See this thread and good luck.
http://forum.xda-developers.com/showthread.php?t=2013977
Sent from my Nexus 4 using xda app-developers app

chelsierae said:
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
Click to expand...
Click to collapse
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.

elliot.newnham said:
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
Click to expand...
Click to collapse
I dont even know what Fauz's Kernel is... I tired that and I still get nothing

chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4

chelsierae said:
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
Click to expand...
Click to collapse
This happened to me today. The battery indicator is incorrect, and shuts down before notifying you sometimes.
Phone shut down on me randomly and wouldn't turn back on today. Plugging into the wall didn't help. It was only when I plugged it into my PC and let it charge for 5 minutes that it came back. Scary bug.

chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.

elliot.newnham said:
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
Click to expand...
Click to collapse
I thanked you on accident, you didn't deserve it. There is no evidence that his phone is bricked, a user above reported the same thing happening and how he resolved it.
Also, he can type in bold if he wants to.

I hope the OP issue gets resolved. Wish you all the best buddy!

I'm having the same issue. Except this happened when I pulled the device new out of the box. Can't even get it to stay on long enough to get into bootloader mode. :-/ RMA time

Good luck on fixing the problem.
Sent from my Nexus 4 using Tapatalk 2

Display problem when charging

Hi i have the latest cm-10.1-20130901-NIGHTLY-find5.zip and I have problems when charging while powered off: The display stays on while charging and the telephone overheats. Are there any fixes?
Best Regards ngt

negiot said:
Hi i have the latest cm-10.1-20130901-NIGHTLY-find5.zip and I have problems when charging while powered off: The display stays on while charging and the telephone overheats. Are there any fixes?
Best Regards ngt
Click to expand...
Click to collapse
Have you seen if this is a problem with other users? I'm using PAC ROM and have the same result with the screen being lit to a black screen when powered off and charging. I'm checking now to see if it overheats. It may be(and probably is) the screen on and charging at the same time that is causing it to heat up like that. My suggestion is to not charge while powered off if you can help it. A little warm is ok, but these quad-core phones can cook when that CPU is going.. I've felt mine to the point of needing to power it off with usage in the sun making it unbearably hot. And if it's getting HOT HOT.. than yeah.
3 things you can do.
1.Charge with phone powered on.
2.Go back to stock ROM where this was not an issue.
3.Work with the devs to try and figure out what is causing it. Be prepared to provide a logcat if the problem can't be reproduced on their end.
My phone has been charging off for about 10 minutes now and it still feels a little cool to the touch. Battery is 100% full. Not sure if that makes a difference. I'll keep in on charge for another 10. I'll update this post in a little bit.
**UPDATE** Its been on the charger for 30 minutes.. no heat increase. Note* I'm running PAC ROM AOSP ROM.

Batteries always get hot if you use them while they are charging. This is slightly harmful to the battery too, but if it only happens once or twice I wouldnt worry about it.
All AOSP roms on this device so far are afflicted by this problem. Just turn your phone on first and as soon as you see the boot logo you can plug it in. You'll get used to it.

shawnbon206 said:
Batteries always get hot if you use them while they are charging. This is slightly harmful to the battery too, but if it only happens once or twice I wouldnt worry about it.
All AOSP roms on this device so far are afflicted by this problem. Just turn your phone on first and as soon as you see the boot logo you can plug it in. You'll get used to it.
Click to expand...
Click to collapse
Yeah for sure. It wasn't me with the issue but the OP.

Coreym said:
Yeah for sure. It wasn't me with the issue but the OP.
Click to expand...
Click to collapse
Sorry I didn't mean to quote you

all good my man
Sent from my Find 5 using Tapatalk 4

cyano forever
Hi have problem with the microphone and display while charnging... but I don't want go back!!! Bye ngt

Use cm10.2
Sent from my Find 5 using xda app-developers app

maxwen said:
Use cm10.2
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
maxwen, does cm10.2 for find5 have deadlocks like nexus 4 does?
I am waiting for the deadlocks to stop before I upgrade.