Swift 2 + Battery - Wileyfox Swift 2 Questions & Answers

So my phones battery discharged from almost full to completely empty last night while plugged in. It seems to be charging fine right now however but I did fiddle around with it a bit. Even if it wasn't plugged in it discharged way too fast for regular standby and non of the "use since last full charge" look odd. Anyone else had anything like this happen?

So it turns out a least part of the problem was that my charge cable is damaged, it only works when plugged in in one direction. I still don't know why it was apparently running flat out all night though.

I wouldn't worry about it; there's no telling what a bad cable can or cannot do with your software. For all we know the software was unable to go to sleep because it constantly started charging, then stopped, then started again... Cut your losses, buy a decent cable and forget about the issue
One thing I tend to do to keep my phone behaving: I reboot it every so often (at least once a week).

Related

[Q] Auto shutdown fault - Xperia Neo

Gidday - This morning I woke up to find my phone had switched itself off during the night while on charge.
Last night I put my phone to charge through USB connected to my PC in sleep mode. I've been charging the phone like this since I got it 3 weeks ago and its been working fine.
When I woke up in the morning I found the phone off and when I gave the power button a short press expecting it to show me the time all I got was a battery charging symbol.
When I went to bed I had the standard "Clock" feature running that comes standard with the Neo so it acts like a bedside clock and I always have the Wifi on when I'm at home.
No other applications were running in the background apart from the normal stuff but I'm quite concerned that the phone turned itself off while I was sleeping because I use the alarm feature to wake me up when I need to go to work and I know these Android phones do not wake themselves up to run the alarm.
Any ideas what could be causing this?
Now this is very funny you say this because this happens to me,,, but I'm convinced I turn it off myself,in my sleep my partner confirms lol
But seriously could of just been a reboot
As long as it don't happen again it should be no great consern ''unless you sleep in for work'' lol
Sent from my Xoom using xda premium
I heard charging like this(from night to morning) is not good for the battery.The owner of the shop where I brought my W595,Neo V specially told me NOT to do this,as he said this can reduce both battery life and phones life.Anyway don't get that much concerned about itself switching off mate after only happening it once.But if can in future don't charge like that.
lol kormatoes ,I on the other hand when ppl call in night sometimes I was told that I just answer it and instead talking keep it beside my pillow thinking it was alarm and go back to sleep xD
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Thanks for your comments guys.
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged? either way I've been thinking that charging via usb is better for the battery because its a lower energy input and therefore charges the battery slower/cooler which in turn should make it last longer (just guessing here - no science to back this up)
Then there is the having it plugged in while at 100% - I've noticed that the phone somehow disconnects itself and stops charging the battery when at 100%. I noticed this today when I started my phone after its surprising shutdown = the battery was fully charged (because it had been plugged in all night) and the battery display refused to show me that the phone was plugged in (when it was) so I turned on the flash light feature and blasted some music to drop the %tage down and sure enough as soon as the percentage dropped below 100% the indicators on the phone started to show the batter was charging (both via the lightening bolt in the normal battery icon and also on my battery monitor which tells me if its charging and how much longer it will be charging for).
I'm looking forward to seeing if the phone is still on tomorrow when I get up.
Any more ideas much appreciated - once might not sound like much but if the alarm/phone had the potential to be even the slightest bit unreliable then I'm going to have to go back to the old alarm clock. At least with my Nokia I could even switch the phone off and the alarm would still chime (we've all experienced this with the old school phones) but I notice that android hasn't managed this yet.
kiwiBratwurst said:
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Click to expand...
Click to collapse
Thanks for your thoughts Kiwi (I've only just figured out who this is ) - The laptop was in sleep mode and from what I've experienced the only thing that works when in this mode is the usb ports - the Wifi and the Bluetooth shut down and I'm guessing that the processor mostly shuts down too? guessing here?
But even so what on the computer might cause the phone to crash?
hilfordjames said:
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged?
Click to expand...
Click to collapse
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
But even so what on the computer might cause the phone to crash?
Click to expand...
Click to collapse
Normally if phone crashes it reboots right ? instead switching off ?
Thilina said:
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
Normally if phone crashes it reboots right ? instead switching off ?
Click to expand...
Click to collapse
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
sdk16420 said:
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
Click to expand...
Click to collapse
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
hilfordjames said:
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
Click to expand...
Click to collapse
If you're rooted, I can recommend Link2SD.
HilfordJames and I have discussed this in length already so this is more for other people's benefit..
Link to sd can be dangerous, as can forcing apps to sd that don't offer the choice normally, app developers block the option to install to sd for a reason, that is usually because the app accesses services that can become corupt or crash if the app is suddenly ejected from the phone (like when you mount the sd card on the computer) so its best to leave those apps on the internal memory.
The most likely reason for the overnight shutdown would be (as you said) that you had filled your system memory up with user apps.
Sure enough once you've deleted all that bloatware from the system you have heaps of room just begging to be filled in the system partition.. But you gotta leave some room in there (about 60-70mb should be enough)
I think another thing could be if your computer somehow woke up in the middle of the night and accessed (auto mounted) your phones sd card, sounds unlikely but I've had laptops run scheduled updates in the middle of the night when they were supposed to be "asleep" if this happened and you had an application running off sd card that uses phone services (like Wifi, bluetooth etc) this may have crashed the phone.. And as it was plugged into power remained shutdown.. Once again (AFAIK) these apps should be installed on the phone not sd card. (games and similar apps are fine on sd card)
Just a couple of theories, but I think we are on the right track
Kiwi
Sent from my MT15i using xda premium
Yip all good.
Since transferring a lot of the files/apps back to user memory I've not had the phone auto shutoff and I've tested it by leaving it on the CPU at night as well and it seems fine - although I now charge it from the wall charger if I'm working the next day just to be on the safe side.

[Q] What can I do to get my NT to power back on?

So last night before I went to sleep, my NT had about 40% battery life left in it. I'm currently running the final alpha build of CM7. I've been experiencing really bad wifi loss issues and have kept the 'Never' option enabled under the wifi sleep policy (thinking that would help hold the connection).
I woke up to find the NT was turned off. Figured that was odd as I was only asleep for about 5hrs. I turned it on and then noticed it got into the OS and then died. I did see the battery icon was red briefly.
I then plugged it into the wall and it was boot looping. I saw the 'n' logo pop up, screen went black, 'n' logo, etc. etc.
After numerous attempts of holding down the power button for 20+ seconds, holding power+vol down for 10 seconds, plugging it with or without an sd card into the wall and computer, nothing is happening.
The computer does see something as I'm hearing the common connected/disconnected tone from the USB port. Now I'm noticing that plugged into the wall, the 'n' on the cable stays orange. It never turns green.
Did it go 'poof' in the night somehow?
[EDIT] Ok after leaving it plugged into the wall for about 15mins, it suddenly turned on but had a google framework FC error. Yeah, not sure what I should do at this point. It appears to be charging...
It's been noted by others that if the power level goes below 15% you mustn't turn the device off if you don't have the original charger nearby. If it dies you need to charge it with the original charger for a bit before it'll power back up.
I assume this means that you can't run it off the cable while you've got a completely dead battery. That kind of stinks but isn't too surprising, a lot of devices are like that.
So does that mean that if the device is <40% of battery I need to plug it in if I won't be around it for a while? Not sure I'm cool with that. Battery life was great all day yesterday but somehow it dropped 40% in under 5hrs while asleep.
I can't really say much as I haven't dealt with it personally. People were talking about it in a couple threads about the NT's charger and unique 12 pin cable.
Here's what I understand from what I've read:
You can run it until it's empty all you like. You'll just need to use the Nook's factory charger (or a compatible 2A charger with bridged D- and D+ pins) AND (this is the important one) the factory USB cable to charge it.
If you run it until it dies you have to charge it for a little while before it'll turn on again, BUT you have to use the original cord and charger. It won't charge off of a regular micro USB cable nor will it work if you're using a 2A or smaller charger that doesn't have the middle two pins bridges (the Apple UBS chargers won't work nor will your PC's USB ports, for example).
The NT will charge, albeit slowly, if connected with a third party cable or USB charger (without the data lines D- and D+ bridged), but not if the device's power has been depleted.
So I suspect something sucked up a lot of juice while you weren't using your NT. Not a huge deal, but definitely annoying. Plug it in for 15 minutes and you can get rolling again.... BUT only if you're using the original charger and cable. Lovely isn't it? It's not a huge problem but it is annoying. I wish you could at least use the device with a dead battery while plugged in.
I just mention the charger/stock cable thing because I'm sure someone will probably see this post in the future and may be having that particular problem resuscitating their NT.
Cool, yeah I don't specifically set out to run it down to zero but since the device is clean with minimal stuff running in the background, it's difficult to know when this might happen again. I assumed I'd wake up with like 20-25% battery left. The framework FC is also something I'm concerned about but maybe it was just a fluke.
Ah well, really do appreciate your input and I'll be sure to keep the stock cable/adapter on hand when I'm on the go.
Battery showed fully charged, I rebooted to do another CWM backup and then when it came back up it showed 84% charged. Lol. And this pic made me laugh even more. Time to get that lady from Poltergeist involved I think...
The Google Framework force close is typical of stock rooted NTs. I don't believe it ever did any harm to anything though. Just that it sometimes appears on reboot.
I'll ask one additional question as to not make another topic since it's related.
Opinions on battery calibration with the NT? That was one of the reasons I didn't charge it last night as I wanted to fully run it down and then fully charge it back up. Does the NT require this with a new rom install? That pic above shows the battery gauge clearly wasn't correct initially.
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
ckevinwelch said:
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
That's what I obviously thought of at first but it didn't drain nearly as much when I was using it throughout the day. The only thing I can think of is maybe the fuel gauge itself was wrong from the start, which refers back to my calibration question.
My GS2 has the sleep policy set to 'Never' as well and only loses maybe 7-8% after being asleep for around 7-8hrs and it certainly uses more juice in sleep due to the cell communication, etc.

[Q] Phone Charging While Unplugged (vbus_present)

Hey guys!
I have a weird issue with my phone, and after doing a bit of research I got a bit pessimistic, so here it is:
When I unplug my phone from the charger, the phone stays in "charging" state, which means the charging icon is there, the battery stats are not shown correctly, I can't plug it into my PC via USB, etc. It also doesn't enter deep sleep, since there is a vbus_present wakelock held, which is normal for charging.
I've read that water damage can be one of the causes, and if I think of it, I did have my phone with me, while I took a long bath. While the phone didn't touch any water, the air humidity was really high , so I could blame this for the issue.
Do you have any suggestions / ideas?
Thanks!
Hello?
My phone is dying here!
Sounds like water damage to me... however sometimes, to my knowledge, the issue can be solved like the fuel_alerted wakelocks: pull battery for a while and reinsert. But I assume you already tried that, so water damage would be my best guess although air humidity shouldn't cause that...
It is the same for me when I dropped my phone into water. However, it is now normal again ( lucky me). For your case, I think it water damaged, I would suggest you dry your phone. Take out the battery, dont use phone for some hour(4-5hrs in my case), dry the phone by whatever you can( I just put in under the sun for 15mins, and put it in a bag of rice). It was 2 days since I got the problem, but now its ok. Just try it.
Hope it helps
P/s: still get some minor problem but I can bear with it though
Fixed ?
Hi,
It seams a bit too laste to answer, but it might help someone esle.
I had quite the same issue, and it seams that the solution is to clean the phone USB slot with a toothbrush...
cant post the reference url cause i'm new... so search for "galaxy s2 won't turned off"...
VBUS present wakelock caused by using Apple compatible charger
It does not look like this was ever resolved, so figured I would chime in since I have been looking at this for a while.
If you use a charger which is compatible with Apple products, it will cause the vbus_present wakelock since Apple does not adhere to USB standards and requires two of the pins to be bridged or open (can't remember which) to work for their products. However, when you charge a device that does adhere to USB standards with one of these chargers, it will cause the wakelock (on all the samsung phones I have seen, anyway).
Another downside to using an apple compatible charger is that you can never get more than 500ma out of it due to the non-standard USB connection, even if the charger is capable of 2000ma output. So you get slower charging.
When you are connected to any charger, this wakelock will be present. If you use an Apple compatible charger, it will persist after you unplug it and will drain your battery around 10% per hour since it prevents it from going into deep sleep. You can clear the wakelock by rebooting the phone or plugging it into a standard USB charger, such as a PC or Samsung charger, even for a few seconds.
You can use Better Battery Stats to see the effects of this wakelock. Note that it can take a few minutes to show up once you have unplugged from the apple charger.
Yes, this really p*sses me off. This is one of the reasons I no longer have any Apple products in my house and long since thrown away all the Apple compatible wall chargers I once had. It still comes back to bite me since I still have a couple of chargers that contain batteries to charge when you are away from a wall outlet and they both cause this. When I use them I just have to make sure I reboot afterward. The USB outlet I have installed behind the stereo in my car also causes this wakelock. I have one to replace it but have not gotten around to removing the stereo to do this yet.
The next best solution to never using an apple compatible charger at this point would be to have a kernel that addresses this and removes the wakelock after it is unplugged but I don't see this happening.
Man, I know you love your S II, but don't go taking a bath with it!
Was this recent? why don't you give the little guy a rest and leave it a day in rice, stucked inside a zip lock bag, can't hurt.
Googled this "vbus_present android battery not plugged in"
found this thread. Seems to have worked for me by simply rebooting. thx!

[q] seriously weird problem with charge

I left my tablet in my car, in my backpack, away from the sun. It still managed to get some heat over a few hours and when I turned it back on it turned off after a second. After cooling it and connecting my charger it started working again.
Here is where it starts getting weird. It won’t charge. It says that it isn’t charging though I know it knows there is a charger connected. Every time I insert the charger it gets out of sleep, but no charge! What is even weirder is that the dock won’t charge now either. The tablet still recognizes the dock as well and I can type but it’s not very useful if I can’t get it to charge.
The charger was not in the car so there was no damage to that. I don’t want any feedback about what I should have done as I can’t afford another one so that would be utterly useless. I know that I shouldn’t have left it in the car in the first place, no need to mention it.
The Prime might have become totally discharged. I'd suggest trying to charge them for 24 hours...Plug them in and leave it alone and see if that solves the problem. Just to be sure there are no interaction problems, I'd suggest that each be charged individually.
Good luck,
Bob

Changed the battery in my Nook Tablet

Piece of cake. Although the replacement is a bit lower MhA it's a lot better than the old battery
pepi4 said:
Piece of cake.
Click to expand...
Click to collapse
That's nice to know. Is there a step-by-step guide for it?
Although the replacement is a bit lower MhA it's a lot better than the old battery
Click to expand...
Click to collapse
Which replacement battery did you get?
http://www.batteryship.com/htmlos/htmlos.cgi/batteryship/catalog.html
You even get free tools and they are not junk
How to that I used ... Hard to get pass the women robot talking LOL
https://www.youtube.com/watch?v=3F0glSyvj2s
At first I wondered about this being a smaller battery if it would run down fast. It doesn't !!! Works very well !!!
I changed out my battery with one from the above site, but now every time I plug a USB cable in it to charge it immediately shuts off. Anyone have any ideas what could cause this? Wonder if I got a bad battery..
mpry1 said:
I changed out my battery with one from the above site, but now every time I plug a USB cable in it to charge it immediately shuts off. Anyone have any ideas what could cause this? Wonder if I got a bad battery..
Click to expand...
Click to collapse
That could be a bad/shorted battery. Mine is still going strong! I would try and reverse everything and start over. When I did mine my vol controls didn't work. Didn't have the connector snapped down good enough
I was looking at this one (still am actually although the one you got is cheaper):
https://www.youtube.com/watch?v=3F0glSyvj2s
http://www.newpower99.com/Barnes_No...cement_Kit_p/barnes and noble nook tablet.htm
I am still trying to see if there is a setting that somehow caused my NT to freak out when the battery reaches 23%
But I have this bad feeling I will need to purchase a new battery. By the way, if the nook just shuts off watch the screen closely it usually says "battery too low" for a second before switching off. And if that is the case after plugging it in, you likely have a bad one and I would call the company to get a replacement.
I have been looking around and the only new replacement batteries I find are the two mentioned and both are 3200mh rather than 4000 of the original. How is your battery life since you changed it? Seems like it should be 1/4th what we had when new (or close to it). Or don't you really notice at this point? I have thought about ebay but then they are used batteries and you have no idea how many cycles are left, and likely hold 1/4th less anyway due to their age. *shurgs* not sure which way to go. As of now I am still having a "freak out" situation at about 23% (roughly). If it doesn't get any worse I can live with that, but from what I have read it will only get worse. :/
Anyone know of a battery app I could use to "adjust" the shut down threashold? I have one that will alert me to whatever I set so if I am not watching it will warn me so that will work if I don't have one that will actually shut it down. I know the "calibrating" apps don't do anything except delete the one file that is only usage stats from the last time it was plugged in, so I don't think there is a real way to calibrate it.
Update:
And on another note with the "spare parts" app the 'battery history' option errors with "the application spare parts ) process.com.andriod.spare_parts_ has topped unexpectedly, please try again." Is this normal? It is version 2.3.7. NT Hidden Settings app application settings/battery use works fine and shows the amount of everything that has used the battery since it was last plugged in/charged. Could this error be a sign of the problem with the phantom touches and inaccurate battery display? And if it is a sign of something broken, what and how do I fix it?
I received a replacement battery and it is doing the same thing, so somehow during the battery switch something got wonkey with my nook. It charges OK just powers off to do it. Since it's used by my kids now it's not essential to be on while charging, but I'd still like to figure this out.
mpry1 said:
I received a replacement battery and it is doing the same thing, so somehow during the battery switch something got wonkey with my nook. It charges OK just powers off to do it. Since it's used by my kids now it's not essential to be on while charging, but I'd still like to figure this out.
Click to expand...
Click to collapse
Which battery did you get? And very strange it shuts off when you plug it in. Never seen or heard of that before. It should boot up if off. Or do you mean the screen goes off/goes to sleep but not full shut down when you plug it in? If it is going to sleep, that is likely a app or setting that is doing it. Not sure which but you might want to check any battery apps you have or your settings. It would also depend on which ROM you are running, stock (which I am running) or something else.
Both batteries were the one mentioned in the original post. It doesn't go to sleep when I plug it in, it completely shuts off like no power at all. It will not boot up until I unplug the USB from a power source, although it will fully charge while it is plugged in. I've never seen anything like this and I've been messing with android since my original moto droid 1.
mpry1 said:
Both batteries were the one mentioned in the original post. It doesn't go to sleep when I plug it in, it completely shuts off like no power at all. It will not boot up until I unplug the USB from a power source, although it will fully charge while it is plugged in. I've never seen anything like this and I've been messing with android since my original moto droid 1.
Click to expand...
Click to collapse
Very strange indeed. The only thing I would say to do is turn the USB debugging on and off a few times, to see if that makes a difference. It shouldn't but if you tried two different brands of battery, sounds like it is the hardware on the nook. But that is one really weird bug.
Something interesting I discovered. While I did get a new battery, I decided to do some experimenting. Researching this issue a lot of people said you need to delete the "battery file". There even use to be a option in CWM to remove this file. The thing is the file is deleted every time you plug in the device. So that is not going to help.
Further digging found that some devices you need to plug them in and let them charge. Or run them down for say 20-30 minutes without sleeping then plug in and let it charge fully. For some devices this "resets" the battery management system.
What I found in my tests is the battery gets harder to charge with age. While the little n light might show green, it is likely only 80% charge sometimes 90%. And it takes awhile for it to really get to 100%. What I did was let it charge up to that full 100% which may take hours. I got a nice battery app that alerts me when it gets below 25% after that things can get crazy with phantom touches. I also have it set to give a audio alert when it reaches 100%, this way I know when it is fully charged.
I know the charge it fully (when it actually says 100% and I get a audio alert when this happens) before 50% or so has helped a lot. At one point the phantom touches started to happen at higher than 25% reaching almost 35%, last time I did a test to see when phantom touches started was 17% so it is much better. Not to the level when I bought the device, but still very useable.
I will put in the new battery sometime I am sure as it is taking longer and longer to reach the full 100% (but that is normal for lithium ion batteries.) it is certainly useable in this state and the phantom touch issue is not getting worse. I think the biggest issue was charging it until the n light went green and as the battery ages, the battery manger gets thrown off for some reason and charging to the true 100% helps recalibrate it.
Therefore I would run it for 20 minutes without letting it go to sleep, then charge until it is really full (usually leave it plugged in overnight and that should do it). Do this a few times and see if the battery is better.
Oh another thing I did. Power it off fully (hold down power button then tap shutoff) then plug it in to charge. Let the charger wake, reboot, and charge the device. This I also think helps recalibrate the system. Although I never did it when I ran it for 20 minutes then charged to full. But I am sure powering off then plugging in to charge at times made a difference as well.
I've just bought one of these batteries, hoping it'll be better than my old one.
It should be. It won't be quite as it was when it was new, as these new batteries don't have the capacity compared to the originals that B&N installed (perhaps a hour or two less runtime compared to the originals). But it will be better than a well used Nook Tablet battery that is fading fast.
I don't know if I need a new battery just yet, but I am experiencing the issue of the power being killed when plugging the Nook into the wall or USB (which means transfers over an SD card, which is a pain). I only spent $5 to get it and I can see why someone might have thought it was broken, since they probably plugged it in to charge it but it wouldn't turn on while plugged in. It does charge while off, however.
What I've noticed in my experience is that if I turn it on, I can plug it in while the Nook is on the N screen, and then it'll go to the Cynoboot screen still plugged in, but the second it goes to boot the OS it turns off.
Anyone have any ideas on why it would allow itself to be on until it tries to boot to the OS?

Categories

Resources