Related
I've only had my Xoom for a day, havent had a chance to use it much. So far there are a few minor problems, but one is really bugging me. The battery level is constantly changing from 100% to what I can only guess is the actual level. Most of the time it reads 100%, but for whatever reason sometimes it will briefly show the actual level for awhile, then back to 100%.
I did some searching and couldn't find anyone talking about this problem, any idea what it is or how to remedy it?
BoostedSR20 said:
I've only had my Xoom for a day, havent had a chance to use it much. So far there are a few minor problems, but one is really bugging me. The battery level is constantly changing from 100% to what I can only guess is the actual level. Most of the time it reads 100%, but for whatever reason sometimes it will briefly show the actual level for awhile, then back to 100%.
I did some searching and couldn't find anyone talking about this problem, any idea what it is or how to remedy it?
Click to expand...
Click to collapse
That is odd. Unplugged, it switches to a lower number then back up to 100% again? Did you install any battery apps or monitoring tools?
keitht said:
That is odd. Unplugged, it switches to a lower number then back up to 100% again? Did you install any battery apps or monitoring tools?
Click to expand...
Click to collapse
Not at first. I watched it happen for awhile then I installed a gauge to see what it would do, and it matches the stock battery meter perfectly.
Sent from my Xoom using XDA Premium App
Looks like your Xoom actually came with a magical unicorn inside that chargers it with magic dust...lol, j/k. But I wish mine had a unicorn.
I say drain the battery, recharge and see if that does anything..or just exchange it.
Been sitting here using it for awhile, and it seems to be time based. I would say 5ish minutes at 100%, then it changes to the actual % (which has been going down) then back to 100% in about 1 or 2 minutes.
I'm going to kill it, then charge it while its off and see what happens. I guess we have no way yet to delete the battery stats?
Sent from my Xoom using XDA Premium App
Killed the battery last night, charged it fully while it was off. Same problem. I guess the next step is a factory reset, then if that doesn't work its going back.
Sent from my Xoom using XDA Premium App
Factory reset didn't help either. I also noticed that the charge light isn't showing the right colors while charging, it just stays white. Guess I'm going to return this thing for another one.
The manual is incorrect re: charging colors. It is just white and only when off. It will turn green if off and fully charged, but there is no red and none of the percentage variations.
Where are you looking at the battery level? Are you keeping the little window in the lower left hand corner open?
Xatt said:
The manual is incorrect re: charging colors. It is just white and only when off. It will turn green if off and fully charged, but there is no red and none of the percentage variations.
Where are you looking at the battery level? Are you keeping the little window in the lower left hand corner open?
Click to expand...
Click to collapse
Actually just returned it, the new one is charging now, haven't turned it on.
It didn't matter where you looked at the battery level. I looked at the notification area, and the setting/status area. Every couple of minutes it would switch between 100% and actual %. Also, when it was plugged in, when it switched to 100%, it would say charged, and wouldn't charge.
Has anyone solved the "Low battery" and "immediate turn off" problem yet?
Man this is the most frustrating issue EVER.
I'm running SRF 1.1.0
I have a 3500 mAh battery.
For some Farking reason, if the battery is under 50% and I get a call. It will RANDOMLY beep LOW BATTERY and turn off, in the middle of the farking call!!!
You turn it back on and it'll have 40+ % charge left!!!
AHHHHH!!!!!
After watching the 25 how to videos, I fixed almost everything that pissed me off, but this one thing drives me bonkers!!!!
I think that's the battery. Is its a yoo-bao from china (cheapie) or a good brand from a reputable source(sedio)? I have that problem with all the cheapies I bought on ebay.
Sent from my SPH-D700 using XDA App
It's not just the battery. My stock phone and rom does it too when the battery gets to 15%. When it reboots it has 20 or 30%.
This phone should never have been released with such a serious bug.
Sent from my SPH-D700 using XDA App
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Now I dont normally let my phone get down to 0% but yeah i know i've gone WAYYYYYYY past even 10% and the phone hasn't done this. Stock battery not extended.
Kcarpenter said:
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
it's a cheapy battery.
However, it's also a bug somewhere in some software...
If it hits 15% when u are NOT on a call, the phone doesn't shut off. It's only when you're actually talking that it does it.
I'm surprised to hear STOCK people saying it happens to them... When I had my phone stock it didn't do this. I assumed it was a ROM issue.
I would try calibrating... I believe there's an actual app in the market to do everything for you. I'm fairly certain its free, so ill post a link, but if its not, I apologize, and well get a mod to take it out.
http://db.tt/NaGV1TB
J3ff said:
I assumed it was a ROM issue.
Click to expand...
Click to collapse
I love how people assume I sprinkle magic fail dust on my ROMs.
Charge to 100% with the device off and wipe battery stats in CWM.
Key word there, "Assumed"
Kcarpenter said:
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yes. I've calibrated my battery. I have seen a couple threads on the issue. I have repeated the issue on several roms and modems. Happens every time i'm on a call and the battery gets to 15%. That makes it serious since it is a phone after all. What if I was talking to 911?
Sent from my SPH-D700 using XDA App
k0nane said:
I love how people assume I sprinkle magic fail dust on my ROMs.
Charge to 100% with the device off and wipe battery stats in CWM.
Click to expand...
Click to collapse
Not just YOUR rom, I've read that this is a problem on all different ROM's including the stock one!
J3ff said:
Not just YOUR rom, I've read that this is a problem on all different ROM's including the stock one!
Click to expand...
Click to collapse
Right, but you said you assumed it was a ROM issue before you found out stock users had it.
k0nane said:
Right, but you said you assumed it was a ROM issue before you found out stock users had it.
Click to expand...
Click to collapse
well even stock is a rom right?
What I'm hoping for is I can figure out what you guys are running that doesn't crash on you when the low battery beep happens.
I think this is a battery issue. I never had this problem with stock battery and it happened twice on cheap 3000 ma battery I bought. Returned the battery and got another one (same kind) and this one works fine. I think this is a manufacturing problem with cheap batteries. When you look at reviews of more expensive ones online, you never see anything about this problem.
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
styles420 said:
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This! Cheap batteries are never worth the money. I bought some cheap chinese rechargeable packs for my 360 controllers... they ALWAYS show low charge even if I just charged to full. Same deal with cheap chinese cell phone batteries.
I am sure the battery calibration is way off with one of the cheapies.
styles420 said:
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok Mr. Smarty pants. You are not understanding the problem. It happens with the stock battery too.
The SECOND you hit 15% while on the phone and get the battery low warning, the phone turns off, MID CALL. You turn the phone back on and it will last hours, even on the stock battery.
If it hits 15% without being on a call, it does not shut down.
That is the real problem here.
This has happened to me once , what could be the cause ? Defective phone or software?
J3ff said:
Ok Mr. Smarty pants. You are not understanding the problem. It happens with the stock battery too.
The SECOND you hit 15% while on the phone and get the battery low warning, the phone turns off, MID CALL.
If it hits 15% without being on a call, it does not shut down.
That is the real problem here.
Click to expand...
Click to collapse
You mean just like a 360 controller can have enough juice to turn on, but not enough to actually play? Or how a flashlight will be too dim to be worth it when the batteries get low?
Would it be better if the battery ran like a champ right up to the second that it shuts off without warning? That would fix your problem - no notification when the battery is low (the sudden shut off can't be avoided until we find an unlimited energy source small enough to fit in our phones)
Your expectations are unrealistic. Just sayin'...
Sent from my SPH-D700 using XDA App
J3ff, it's likely the cheap battery. Here's why:
Charge level is a simple linear voltage function. Our phones consider 4.2V to be full charge (100%), and empty to be around 3.6V (0%). The voltage drops roughly linearly between these two values as charge is consumed.
The kicker is this: The voltage seen at the battery terminals is also affected by the interaction between the internal resistance of the battery and the instantaneous load, or current draw. For electronics buffs, this is the classic V=IR, and what happens is that the voltage on the battery will drop by IR in addition to it's unloaded voltage level due to whatever the stored charge state is.
Good quality batteries have a very low internal resistance, and will not drop much voltage due to an increased load. Crappy batteries are just the opposite, and even though they do carry the charge storage (most of the time) advertised, they are only suitable for low load applications.
What's happening is you have a battery with a horribly high internal R. When you make a phone call, the load increases A LOT -- transmit power goes way up. This if why phones get hot when talking on them -- they really suck the juice.
As a consequence, because of the high resistance, voltage from the battery takes a nosedive. At an "idle" reading of 50% (3.9V, thereabouts) you're probably dropping more than 0.3V when the load goes up during a call, the phone panics, and shuts down to protect the battery (LiIon doesn't like to be discharged below 3.3V, and can be damaged).
When you reboot, the high load is gone, so the voltage shows higher again, reflecting the fact that there is truly still plenty of charge stored and available. The battery simply can't handle gulps, but only slow sipping.
High internal R is one of the most common reject reasons from mfgs, and those batts are sold on the cheap to dealers and distributors in a secondary market. Honest ones then resell into appropriate application spaces where low-current is all that is needed. Most, however, are not that scrupulous, and sell right back to the same market, leaving behind puzzled and unhappy customers.
Sent from my mind using telepathitalk
Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?
Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.
Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App
Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...
did you try booting in recovery? vol down ±power
zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.
You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium
Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Kermode said:
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Click to expand...
Click to collapse
Hold the power button down.
Sent from my Galaxy Nexus using XDA App
Happened to several guys.
Did you try to press and hold power for ten or more seconds? It should power off and you should be able to power it on again.
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
fone_fanatic said:
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
Click to expand...
Click to collapse
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Just an idea but what if you use something like SetCPU and up the lower frequency. Had this issue on a kanged ICS rom for my phone. It wasn't the deep sleep that was the problem but the lowest frequency was too low to re-initialize the apps that were cached once you woke it up.
I did a full complete wipe and updated from .13 to ICS and am not going to jinx myself by saying what I am implying. If you know what I mean.
Interesting, and I do agree that there are too many threads, since I am trying to get some idea of how common this is. I think I was the original poster on this, but in any case in my particular situation I tried holding the power button down, resetting it through the reset hole, and holding the power button in while pressing the volume button down (this did give me the option of reformatting which I tried) but in every case it simply flashed the eedpad screen. The battery finally appears to have died and I'm trying to recharge it now, but so far it is now completely dead. All of this happened after it went into deep sleep. This tablet is 100% original, never been rooted or tampered with in any way so, unless this is a coincidence or a combo of ICS and one of the apps I have in it, I expect this to become a very common occurence. Anyway, I'll let it charge for a bit and see what happens. I already have an RMA (the service person didn't seem too surprised and didn't really try much trouble shooting - when I asked if he had heard of this before he kind of said I wasn't the first) so I'm sending it back to Asus on Monday so that when I get it back I can sell it, but I'm just wondering what percentage of people are having this problem. Heck, if it's even just 5% Asus is going to have a major expense on its hand.
I had the dreaded Asus logo freeze twice now, since the ics update. Both times when I wasn't using the tablet.
Sent from my Galaxy Nexus using Tapatalk
Mine has frozen 2x already since the ics update. I performed a factory reset before and after the update.
Screen just goes black/blank and would have to hold the power button for 10secs.
Sent from my Transformer TF101 using Tapatalk
Hey thanks, I thought I had pressed power down for long enough - but apparently not.
I was on normal HC and just accepted the update when it prompted me for it.
But if a lot of people are seeing this i guess Asus made a little blunder in this version.
I just came in after leaving my Transformer asleep for about three to four hours, and found the asus logo flashing on for a few seconds and then off, repeating over and over. Had to do a reset with power and vol down to get it to reboot. Seems OK for now except it really drained the battery.
I guess there will be a few ICS bugs to work out.
jparity said:
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
msaraiva said:
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Well asus is good about providing prompt follow up updates so I wouldn't be surprised if we start getting bugfix updates in the coming weeks.
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
It's next to the hdmi port.
jparity said:
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
eminembdg said:
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
There isn't holding the power button for 15 seconds resets it.
Sent from my Transformer TF101 using Tapatalk
r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
I thought it's the mic too... Does your voice record still work after you "reset" your TF?...
Edit: Saw the dreaded Asus loading screen again when I came back from dinner... 3rd time today... It's getting on my nerves a bit now. Such a pity that the TF is perfect besides this issue... I don't care if it reboots every hour or so, as long as it doesn't hang and depletes the battery.
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
fone_fanatic said:
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
Click to expand...
Click to collapse
How do you it didn't happen? It doesn't get stuck at the ASUS logo for me, it simply reboots. Try leaving something open, like a browser window, turn off the screen and come back sometime later. If it's back to the homescreen and there are no recent apps, then it rebooted.
I don't know if it is the deep sleep that is causing it. All i know is that the bug is only triggered while sleeping. Every logcat i get stops at an AlarmManager event, before the reboot.
Sent from my Transformer TF101 using XDA Premium HD app
Hi All,
I was browsing the web a couple of hours ago and my N10's screen started flashing on/off and after around 10secs the thing crashed/turned itself off. Being an N10 this was not an unusual event! However when I try to turn it back on nothing happens. I can hold the power button / power button with volume buttons pressed and nothing happens. If I plug it in to charge I do not get even get a charging icon.
If it makes any difference I was running the latest Rasaber with Franco's r11 kernel and I know I had at least 40% battery left when it died. I have left it plugged in to the stock charger for around an hour hoping that something might happen but still nothing.
Has anyone ever experienced anything like this?
There was not a sad enough looking Emoticon to convey my sadness over the possibility my lovely Manta is dead......
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Something similar happened to me but I'm totally stock. I Googled and the solution was to recharge the unit via my PC USB instead of plugging it into an outlet. I have no idea what happened but after a few hours of being connected to my PC it was back and working. Hope that helps.
I'm running the same rom and kernel combo. No problems or anything weird happened. It must be hardware related.
Did you try the holding-the-power-button-for-a-minute routine?
I would try to leave it plugged in on the charger for a while and see if it gets fixed. That usually solves all sorts of "wont turn on" problems
samwheat said:
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You seem upset
i seem realistic
another nexus 10 with problems
Sent from my Nexus 10 using xda app-developers app
is it possible for the tablet to get overheated?
I have had that happen on stock.
My theory: it is linked to the 'battery status not updating'-bug. Your Nexus thinks the tank is still half full, while in fact you are running on fumes. It does not realize this, so no dimming of screen, no low power warning, it just goes full steam ahead, until the battery is totally and utterly and completely depleted.
Then, obviously, it won't start but it will also have trouble charging. You need to charge it for quite some time, sometimes try a different charger, and sometimes keep the power button depressed for a full minute for it to come back to life.
Now when I use my Nexus, I keep an eye on the battery status. If it does not go down, I know I need to reboot for the battery status to be read properly again. It is a bit of a bother, but not too much. The bug only kicks in after the tab has been lying around for a while sleeping. So if I want to watch a movie, I first reboot. As long as I keep using the tab (i.e.watching the movie), the bug won't 'activate' and the tab will shut off properly when it senses the battery is low, in stead of continuing and deep depleting the battery.
Sent from my Nexus 10 using XDA Premium HD app