Hi all
I have a Kindle Fire with Cyanogenmod 9 v1.3.
The problem is that while charging the orange light flickers.
When i use the device (screen on) the orange light stays on but as soon as i put it to sleep the light turns off and every few minutes it flickers for a second.
The device is still charging (charge percentage increases) but i am wondering is the current constant or will i destroy my battery. Does anybody else have this problem and what did you do.
Also i bought my device on e-bay (new but no warenty) because i live in europe and kindle is not shipped there yet so please no responses like send it back to amazon because i can't
Thnx for all your help!!!
totally normal for cm9 if you dont like how the light stays on when unplugged just reboot if you have the old bootloader with the yellow triangle you may wanna upgrade dont let the battery die if you do
i don't think we understood each other. The light problem is accuring while the device is plugged to charger.
so when i turn the screen off the light switches off but every few minutes it flickures
on the contrary we understood each other perfectly mine does the same this is entirely normal
Ok than i apologies and thank you for your help.
So what you are saying that everything is normal and i can enjoy my kindle for a long time without the need of battery replacement
or I guess I should say normal for cm9 its work in progress there will be bugs IMO its harmless just doesnt act like stock is all
Thepooch is correct. This is a well known issue with the kernal and IIRC, hashcode is working on it. The device will charge just fine, but the light will not function like stock.
Related
I just bought a used SX66 and the device just seems to reboot when on the charger.
It powers on, right light in top right seems to blink, then the device restarts.
Almost seems like it is a battery/power problem. Will only stay on long enough to show that battery is near 6%.
Does any one have any idea whats wrong with this phone? Should I try and send it back via ebay?
Apparently related to the battery.
Let the unit charge over night, and see if this fixes it.
Hey guys,
So I just bought myself one of these:
http://store.androidcentral.com/seidio-innocell-1750mah-extended-battery/8A37A6040.htm
And so far I've been fairly pleased by the performance.. although I haven't yet done a real good test of it (I will this week). One issue I've noticed, though, is that no matter how long I leave the thing on the charger, the light (infuriatingly ) remains red. If I reboot the device while it's charging, or turn it off, the light will turn green, indicating that it is charged up, but if I unplug & use the device, then put it on the charger later, it will never come back to 'green'.
Does anyone know what this means or how to fix it (other than just popping my stock battery back in..)?
*bump*
I just got rid of the sense homescreen, and the default one displays the battery charge; it's stuck at 96%.
Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
- P.s. This is pretty urgent as I use this number for work!
:victory:
Ok, it seems to have been resolved at last... just for anybody who gets the same issue, here's what worked for me.
After doing some more searching I found someone mentioning this method: Leave the phone plugged in to your USB port for a while until the orange LED flashes. Leave it flashing for a few minutes, then quickly swap the lead from your USB port to a wall charger. If you leave it unplugged too long then it seems the LED stops flashing and it won't work, so do it quickly.
If successful the LED will keep flashing while plugged into the wall, and it will start to charge up. Give it a while (I left mine for about 25 minutes) then try and turn it on. This worked for me, but even after this period of time it had only charged up to 2%!
:S This is an odd phone indeed.
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Croaton said:
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Click to expand...
Click to collapse
Very strange indeed... I tried pretty much everything I could before this, but this was the only thing to get the phone to boot. Charging and working fine now :S. I'll have to make sure to never run it flat if I can help it, this would be a right pain if it it happened while I was out
Just saved from similar issue
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
silenttalker said:
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
Click to expand...
Click to collapse
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
wont turn on
chrisoverson said:
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
Click to expand...
Click to collapse
im unable to see led light i believe unsupported kernel fryed phone
I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.
sarsius said:
I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.
Click to expand...
Click to collapse
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did
powerpoint45 said:
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did
Click to expand...
Click to collapse
Yes I attempted a reset but it wouldn't respond and I tried to let it charge, but after about an hour it got extremely hot and I didn't feel I could leave it plugged in safely. When I contacted amazon for support I did all this for the tech on the phone and when I plugged it in and told him about the light, he said something about the usb port had come off the board which I know is possible but to happen twice in 60 days with two different devices is just ridiculous. I'm not sure what I am doing wrong if anything both devices were fully charged when the errors occurred. I just don't want to have to get a fourth before the month is out, the only positive is the fast turn around from amazon.
My HOX just seems to have died overnight. It has been completely fine and stable at least a month on AOKP ICJ 1.3.0. Have not done any form of meddling with the rom/kernel/anything since then.
Yesterday the phone was working completely fine, but this morning, the phone screen won't turn on, it won't boot(at all), holding power button/power + vol down doesn't do anything.
The phone is now behaving very weirdly:
Charging does not turn on any LED lights, and it still would not boot during/after charging for hours.
However, it seems the LED will start flashing red if I leave it charging for a while(it's not overheating as far as my hands can tell).
The default action for charging normally is a always-on red LED.
Also, after a some plug-in time, it seems the the HTC sync manager will detect it and auto-run.
Phone remains unable to be turned on.
I kinda panicked here and unplugged the phone to see if the effect can be reproduced; it could not. Phone now remains undetectable.
After plugging it out, the red LED continues flashing for a few minutes, the phone can be noticeably felt to be getting hotter gradually.
But still nowhere near overheating levels.
Could anyone perhaps help me troubleshoot? Any help would be greatly appreciated.
I'll try to see if I can get into get it to be detectable again later after it cools down a bit; see if I can at least get into bootloader.
-Reproduced, but adb reboot bootloader seems to reset the cycle, bringing it back to undetectable.
leave it charging
Oh wow. It really works. Thanks tomascus!
Alright phone's useable again. What a panic attack.
Any idea why the first 2 hours of charging before I posted this didn't seem to do the trick? Is this just some internal checkpoint thing?
ULAMSS5 said:
Oh wow. It really works. Thanks tomascus!
Alright phone's useable again. What a panic attack.
Any idea why the first 2 hours of charging before I posted this didn't seem to do the trick? Is this just some internal checkpoint thing?
Click to expand...
Click to collapse
It likes to take its time
The light blinks when the charge is really low....
Sent from my HTC One X using Tapatalk 4 Beta