Related
Any help here appreciAted all the sudden my shift won't charge I plug it in and get a solid amber light for 5 seconds then nothing. Tried various chargers Anne removing as still nothing.
try a battery pull and try again
Tried removing battery SDcard still solid then off
Check the charger port. If you keep your phone in your pocket like I do, you get lint build up. I've already had to clean mine out twice. I used compressed air, and was very careful.
Tried charger port looks clean used air did try to turn it on while amber light was solid iT began to then shut off
try a different mini usb cord, see if that works. It could be a bad cord...
Also tried different cord combinations USB>AC USB>Pc etc to have same result plug in a few seconds Later I get solid amber for about 5 seconds then it goes off. Have to unplug and remove battery and replugin to get it to recognize anything again.
Can you clear battery stats? Long shot, but you never know...
Sent from my Shifty Speed Brick using xda premium
All I can do is try a power on during that 5 seconds. Which initiates a power up but it still shuts off as soon as either the white HTC screen starts or if I try recovery as soon as the Boofloader screen where it gives you boot options and shows sff that screen don't know correct name for it. Either way all I get is a quick flash of either screen when it attempts to boot then shuts off.
This is a longshot too try plugging it in and leave it for a couple hours or if somebody you know has a hero or og evo charge your batt in it for a hour or 2 then see if it is your battery or the phone. I remember reading somewhere if you completely kill those li-lon batteries it messes them up and possibly the phone too. You didn't run it completely down did you?
Edit: you may have to flip the hero or evo's battery over to make the contgacts match up,not to worry it'll work cuz I'm running my heroi 1700mha battery in my shift now.
Sent from my PG06100 using xda premium
Themikmik.com has a thread on battery calibration, one of the options is to pull the battery during bootup. This clears the battery stats folder.
Ought to see if your local sprint store has a battery you can test b4 you buy, may be that simple. I would avoid the full service stores, maybe a mall kiosk?
Sent from my Shifty Speed Brick using xda premium
FdxRider said:
This is a longshot too try plugging it in and leave it for a couple hours or if somebody you know has a hero or og evo charge your batt in it for a hour or 2 then see if it is your battery or the phone. I remember reading somewhere if you completely kill those li-lon batteries it messes them up and possibly the phone too. You didn't run it completely down did you?
Edit: you may have to flip the hero or evo's battery over to make the contgacts match up,not to worry it'll work cuz I'm running my heroi 1700mha battery in my shift now.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
+1 You might want to try a different Battery. These batteries do not like being run all the way down to nothing. Had an issue once where I thought it was a rogue app running the battery down really quick. It wasn't, I had let the battery drain down to nothing one to many times. Fresh battery cured the issue. Actually got it from Sprint for free. Walked in said my battery was no good and they gave me a new one, no questions .
HERE is the thread on the MikMIk for Battery Calibration.
Issue resolved after 3 hrs at retail seems battery boost is all it. Needed so far although CSR tried to blame it on water damage. Saying litmus near USB port was pink which they refuses to show me when I asked to see It knowing that it's never been near moisture other then the humidity in the air. Let's hope this does it.
bentear said:
Issue resolved after 3 hrs at retail seems battery boost is all it. Needed so far although CSR tried to blame it on water damage. Saying litmus near USB port was pink which they refuses to show me when I asked to see It knowing that it's never been near moisture other then the humidity in the air. Let's hope this does it.
Click to expand...
Click to collapse
Water damage is their fallback answer everytime.. I've dealt with the same thing from Sprint. It's a bunch of bs.
Sent from Gingerbread Speedy 4G
Glad you got it solved! We're here if ya need anything else.
Sent from my PG06100 using xda premium
Glad you got it sorted out. That BS about water damage is just that, BS. Been told that a bunch of times. Actually showed them it was BS. They opened one of thier own unused phones, and the damm indicator was red. Never been opened and red. Oh yea, sure it's a good indicator
MikShifted on XDA Premium APP
TEAM MiK
Mik ROMs Since 3/13/11
Thanks for finding that link prboy, I didn't have time to hunt it down earlier.
Anyone mind tellin me what a battery boost is? New to me.
Also, according to HTC, we should be completely killing the battery once a month as maintenence. Has this proven detrimental to the life of the cell?
Sent from my Shifty Speed Brick using xda premium
No proplem, help when I can. No idea what a battery boost is . But as for killing the battery once a month. Well that's a whole different can of worms . There are different schools of thought on that. Some say it's really bad, because it kills the cells. Others say it's necessary to kill it in order to retrain it. Just Google it, but be prepared to read through a lot of info. Personaly ( IMO not that it means a damm thing ) I don't believe in the whole drain it dead phiosophy. But that's just my opinion
I used to manage batteries plus... Lithium ion batteries are the best because there arent memory gimmicks... It is not a bad thing to drain it down to 1 - 2 percent. I personally dont drain down all the way because I had an odd experience with my phone not being able to turn on (no recovery, nothing!) for about 2 hours... I thought it bricked somehow, so I let it alone for an hour on the charger and it magically (thankfully) turned on when I tried... It freaked me out so I never let my phone's battery die...
It is always a good idea to cycle the battery but the most imporatant thing to do with any cell phone battery is to charge it uninterrupted for 24 hours before using it...
Sent from my PG06100 using Tapatalk
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
Without fail my Nexus 7 seems to die around 25% battery. Strangely, this only happened after I unlocked/rooted it, but now it happens every time. I even charged to full, used CWM to wipe battery stats and let it run down from there, still no dice.
Safe to say I should get a replacement?
No? I'd be surprised if I'm the only one having this problem... Seems like the Nexus 7's hardware issues are pretty widespread.
I must admit, when it died, I dont know what % the battery was at.
omnikai said:
No? I'd be surprised if I'm the only one having this problem... Seems like the Nexus 7's hardware issues are pretty widespread.
Click to expand...
Click to collapse
Since youve rooted it, your warranty may be void, assuming that it wont be have you tried a custom rom? as daft as it sounds i had this issue on my old HTC desire, but a custom rom did fix this.
I havent had any issues at all with my nexus 7, my nexus was down to 8% last night when i plugged it in to charge before bed.
Aslo i wouldnt assume there are "wide spread" issues with the nexus7, for every device ever made there are always numerous threads about faults and the odd pixel being missing, people like to come onto the internet to broadcast there views when they feel they have been slighted or wronged in someway, if there was any "widespread issues with the nexus" (such as apples antenagate issue with the iphone 4) then it would be everywhere over ever tech blog.
Jjust reflash a different Rom
》》》Samsung Galaxy S3《《《
Been down as low as 2% before relenting and letting the poor thing power up. Rooted and on jr5.
Thanks for the feedback all, perhaps I'll try un-rooting it while at 100% battery and see if it fully discharges. Perhaps it's just sensitive about the battery capacity when it changes ROMs/Bootloader status.
My Nexus 7 is doing the same thing at 20%. What happened to yours?
Have you tried a factory reset? That's fixed similar problems on other devices.
Factory reset yes, but not at 100% charge.
Mine dies at/or around 30% - I'm stock+not rooted.
Factory reset it. It doesn't matter what the charge percentage is. I did it to mine and it's working fine
clear your batter stats in CWM, full charge, full discharge, full charge
davidcampbell said:
clear your batter stats in CWM, full charge, full discharge, full charge
Click to expand...
Click to collapse
I tried this and it didn't work for me. The only thing that did was a factory reset by flashing the stock image through the root manager tool.
A user named NeoMagus has received two units with this issue, but I haven't seen many people mention it otherwise.
http://forum.xda-developers.com/showthread.php?p=30787728#post30787728
I'm new to tablets but I returned a Fire with the same problem. I assume it's a freak battery thing and not something innate to this device.
Yup my first C6 and last C7 also had this problem. Charged/Decharged fine for about a week, then just started turning off at about 19-20%. The screen would also display in very small text "show low low battery logo". Re-flashing stock, wiping, calibrating by deleting batterystats.bin, nothing helped, always died at 20%. Just ended up exchanging both so don't know what to tell you guys, everyone else seems to be fine so my only conclusion is bunk battery
omnikai said:
Without fail my Nexus 7 seems to die around 25% battery. Strangely, this only happened after I unlocked/rooted it, but now it happens every time. I even charged to full, used CWM to wipe battery stats and let it run down from there, still no dice.
Safe to say I should get a replacement?
Click to expand...
Click to collapse
Flash back stock ROM, lock boot loader and see if it fix. At this point, you got back your warranty and can ask for replacement
Sent from my Nexus 7 using Tapatalk 2
I have the same issue on mine, which is stock/unrooted. I just did a factory reset and it's been okay so far, but it's a little early to tell if it really worked.
**UPDATE** - Doing a factory reset did not fix the issue. It died again after some more use. I'm going to return it to Google.
**UPDATE 2** - After connecting the device to the charger and powering it on again it reported 0% battery. I charged it back up to 100% and I've currently run it back down to 7%. I'm not sure how or why it's working now, but it does seem to be a problem with the software misreporting the remaining battery life.
Mine shut down at 9% last night. Not that bad but not ideal I think it should go to 2-4% or 'go down with the ship' at 0% like my phone does.
Oh well I'm going to get a replacement after my next trip due to audio and touchscreen issues, I've been putting it off in hopes that they iron it out but I can't wait much longer a dead left headphone and random zooming when I scroll is a drag.
Same here ,last week my N7 died at 15% battery
but now at 20% ..
no Low battery Logo show
Should i do Factory Reset ???
So I just beat DeadSpace (yay), then I decided to reply on a harder difficulty. Within 15 minutes the phone turned itself off and the LED flashed RED once really briefly. Now it won't power on at all. The issue just happened, I don't know what's up.
I hope it isn't in the untouchable state (soft-bricked) again...................... Of course this stuff happens to me at this time in the night when nobody is awake to respone ......... What do I do? How can I fix it?
If it fixes itself I'll let you know.... I know for sure that I'm not playing Deadspace again after this...
EDIT 1* Just unplugged the charger and popped it into another wall. Now the Red Flash is just staying on, the phone is plugged in. What's going on?.......
EDIT 2* The Red LED stopped, phone still won't power on
EDIT 3* The phone now shows the low battery screen while being powered off... I'm guessing it'll power on now
EDIT 4* The phone successfully powered on, nothing is wrong with it now
Sorry for posting this thread it seems like a waste now..
Soooo! To make it not so pointless, I think I found out why it does this. I think Deadspace drained more battery than the phone could charge so the phone died (battery drain) with no warning. And when it did die the phone was in a state of "what the heck - - - computing - - - enjoy this RED LED!!!!!!". I guess it just means "Super dead battery". So in case anybody else fears for their $500 investment, just give it 10-15 minutes before you panic, and let your phones actually charge
From what I can gather from the various threads about the "Red Led Of Death" is that if it's flashing - it's recoverable in some way, if it's just a solid glow you're SOL. I've spent the last 2 days trying to get my N4 to live again Would actually help if people where more specific about if it's flashing or not.
Just got off the phone to the Play Store and arranging for them to start the RMA process. I guess I'll find out in a couple of weeks what the problem is.
When I first rooted I had the light for 4 hours, got it in and out of the red LED state 3 times that night. It was a horrifying experience. I do not know how I fixed it. I was jamming buttons and eventually got into the boot loader mode, from there I flashed stock boot.img and the rest is history... I wish you luck!!!
Sent from my Nexus 4 using xda app-developers app
I've read it has something to do with the stock charger..
calanizzle said:
I've read it has something to do with the stock charger..
Click to expand...
Click to collapse
I wasn't using the stock charger
Sent from my Nexus 4 using xda app-developers app
When I leave the Nexus 4 on a flat surface with nothing around it, it will randomly turn the screen on, wait the 30 second timer, then turn back off.
I did just install 4.2.2, but I hadn't used it enough before to say if it only started since then.
I'm currently unrooted, though unlocked the bootloader when I first got it so I do plan to root soon, would flashing a custom kernel like franco kernel possibly fix this? Or would this be a problem in the rom or a third party app?
In BetterBatteryStats I saw 2 Kernel Wakelocks that seemed to have a high ammount of wakes.
(Screenshots Attached)
And here's the BetterBatteryStats Dump File: https://www.dropbox.com/s/dbc2vn3littc0fp/BetterBatteryStats-2013-02-21_054751350.txt
Any help would be highly appreciated, thanks.
Possibly a third party app.
Sent from my Nexus 7 using Tapatalk HD
Was gonna say that I'm having the same issue, but mine only lights up when I charge my phone..
Sfkn2 said:
Was gonna say that I'm having the same issue, but mine only lights up when I charge my phone..
Click to expand...
Click to collapse
That's normal bro. Mine does the same and so does every other phone I had.
Sent from my Nexus 7 using Tapatalk HD
scream4cheese said:
That's normal bro. Mine does the same and so does every other phone I had.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Err I meant like, it keeps turning the screen on and off - like if the charger is disconnecting itself.
Sfkn2 said:
Err I meant like, it keeps turning the screen on and off - like if the charger is disconnecting itself.
Click to expand...
Click to collapse
Sounds almost like the charger has a short or something.
jsilvermist said:
Sounds almost like the charger has a short or something.
Click to expand...
Click to collapse
It does that with all sorts of different cables and chargers. Think I might have a loose USB port?
Maybe it's linked to the Daydream feature?
Sfkn2 said:
It does that with all sorts of different cables and chargers. Think I might have a loose USB port?
Click to expand...
Click to collapse
Not sure, guess it's possible, but even if it is lose I wouldn't expect it to effect it once it starts unless it gets bumped.
Also, what is the temp of the battery when charging? Not sure if it's true but I've heard that if the battery is over 40c it won't charge properly.
If you want, here's a really nice widget with temp on it: https://play.google.com/store/apps/details?id=ccc71.bmw
I would just be careful with anything to void your warranty until you figure out whats causing the problem, as I've heard a lot of stories about bad batteries, and shorts in usb causing the red light bug (For lack of a better name).
jsilvermist said:
Not sure, guess it's possible, but even if it is lose I wouldn't expect it to effect it once it starts unless it gets bumped.
Also, what is the temp of the battery when charging? Not sure if it's true but I've heard that if the battery is over 40c it won't charge properly.
If you want, here's a really nice widget with temp on it: https://play.google.com/store/apps/details?id=ccc71.bmw
I would just be careful with anything to void your warranty until you figure out whats causing the problem, as I've heard a lot of stories about bad batteries, and shorts in usb causing the red light bug (For lack of a better name).
Click to expand...
Click to collapse
Thanks for the link. I actually looked through the 'must have apps for the N4' thread under themes and apps, and Goku80 had posted a link to a battery meter that I just downloaded and installed moments ago. I have yet to see what the charge temp is, but I will report back tonight. Idle temp is around 25*c from what I've noticed just now.
The only thing I've noticed with temps so far is when I have my phone pulled in and I'm watching something on the phone. The phone gets really hot, and the system starts to lag badly. I would assume this is a fail-safe for the battery to not overheat by downclocking itself, but this is only a theory.
As for the red light bug, I saw my phone drop from 28% to 4% instantly out of nowhere yesterday, with no warnings. I immediately pulled the phone in, and watched the battery meter jump to 30%. According to the red light threads, I think it's a software issue with the phone shutting down completely when it thinks it's out of battery to prevent damage. Hopefully we'll never run into that issue ourselves.