Related
I always get the message that my battery is running low and need to charge it again.
Does wifi card eat power?
Only had out of cradle for 90 minutes or so.
Also is there a way I can see backup battery power?
Only had it a few days and still gettin used to it.
yes WiFi needs power, and so does Bluetooth. but only if it's turned on. Although some say the wifi-SDcard uses power even when turned off.
Adjusting backlight also helps to save power.
Bad reception is also a reason for power consumption.
Start/Settings/System (on the bottom tabs)/Power
There a lot of free today plugins which shows your battery power on the today screen.
What Rom version do you have? Start/settings/System Device information/Version.
I ask this because 1.72 has improved power usage.
Hi All,
I have such a big Power issue with the Magician, or at least Orange's M500 version of it that i'm thinking of taking back the device :'(
It doesn't appear to be a device fault, but a design fault.
In the manual it says that if you press the power button for a short time (less than a second) it turns the PDA on and off. This seems to be correct.
In the manual it says that if you press and hold the power button for two seconds it turns the phone off, but this doesn't work. Instead it turns on and off the back light. If the PDA is on, it turns on and off the back light. If the PDA is off it turns it on with the backlight on.
Last night I turned my PDA into standby mode (As i can't turn the phone off) before going to bed. Around 3am in the morning my PDA woke up saying that the battery power was low. I turned the PDA back into standby mode but it complained later on that night. i.e. had a bad nights sleep last night.
I thought it best to remove the main battery so that it wouldn't continue to wake me up, making sure that the phone and PDA were turned off (no power) and let the data backup battery retain the data until i woke up (5 hours time). However, when i woke up the internal data backup batery was flat. It was fully charged before the i took the main battery out. It is supposed to last 72 hours right!!!!? What a nightmare!
I was wondering if anyone could help me answer these power related questions, as i love the device, but its useless if it won't retain the data when it says it should.
How do you turn the phone off so that nothing is running at all? (i.e. to make sure that the internal battery is only being used to retain my data)
Does activating bluetooth drain the main battery faster even when the PDA is in standby mode? (I think i may have left it switched on last night)
Why would the internal data retention battery drain flat in under 5 hours when the main battery is removed loosing all data? Does it need the main battery in place in order to work? Could the phone and the PDA in standby mode by running off of the internal power?
Thanks in advance to any help you can give. As you can imagine i'm very disappointed as i love the functionality of this device.
Neil
When you took the battery out and left it out, if you had slid the back down (this is the same as a power off) you would of been ok.
The action of sliding the back down and back up is equvalent to a power off. When you press the power button after this, it is like a cold boot. (Not a hard reset)
I hope that made sense.
So to power off the phone and PDA you have to slide off the battery cover and slide it back on again without taking the battery out. Surely there is an easier way to turn off the phone and PDA that to remove the battery cover?
Thats how i do it. I'm sure there is a different [proper] way, but i'm not sure what it is.
Hi
The main battery when flat enough to power off the pda should have 72 hours data retention, its designed that way... so if it goes flat on friday you will still have your data on monday. thats why it was designed that way and apparently it shuts of at 50% capacity.
Bluetooth active will drain more power.
the backup battery is only supposed to last around 20 mins or less, designed so you can take the main battery out without losing data. this is because Ram needs constant voltage to store contents. hence if you leave your main battery out for more time the backup battery has charge you will end up with a hard reset occuring.
The manual needs to be updated i guess. If you want to turn off the phone you can turn on flight mode which disables the GSM radio functions.
Oh and out of interest for the battery type Li ion, its actually better to keep them charged, they dont have cycles like older batteries. they only have a certain lifespan which starts from the date of manufactor and keeping them at low charge degrades them faster.
Enjoy
SpeedN
So up until the 50% point, pressing the power button just puts the PDA in standby and the Phone is still running. Only when the power goes below 50% ish does the PDA power off completely?
So after the phone is fully charged, the M500 battery life meter says there is 6 hours and 31 minutes of battery life in it. You say that the device will turn itself off at 50% battery life remaining, so that means it only has 3h 15m of useable time before it switches off? Can the phone / PDA be used when power gets below 50% or will it just not power up until its recharged?
Thanks for your help BTW very useful information.
Neil
The battery life meter will say eg 6h 31m, the device will turn off in 6h 31m give or take (usage dependant).
when the device is flat there will be still 50% capacity in the battery to allow for the 72 hours data retention. hope thats clearer.
when it is in that state it wont turn on I think...sorry been along time since i been in that state, untill you charge it.
SpeedN
Surely the easiest way to solve this (and yes I was fooled by the manuals answer to press and hold) is to enable flight mode(which turns the phone off) then turn off ? there are a few apps/ shortcuts that will switch to flight mode easily, you then simply press the off button.
Or did I miss something
I think when we push the power off button (or if we select the machine to be powered off after a period of idle time, through setting), the machine will be off except GSM functions. So when you turn on again, it takes a few seconds to make the machine runs.
You can try if you turn off the button, after few minutes (should be more than 180 seconds), then push the Green button to dial, it takes 3-5 seconds to make the dialing pad comes out.
If you do not select the machine to be power off after a period of idle time, you can use other software to "screen off" the machine, so that when you push green button to dial, it comes out very quickly.
If you turn off the GMS, and turn off the PDA, it will not really get into sleep but will be in the state of retention of data. In any case, when you wake up the machine it takes a few seconds.
Therefore, when you are on the run (say on the street) and make calls frequently, do not power off the machine so that you can make calls quickly.
That is only my experience, I have checked other HP and XDA phones, same results. So nothing to do with the speed CPU and size internal ram.
When the machine is ON, I under clock to 208, the dialing pad also comes out very quickly.
flight mode = on , thats all, it turns the gsm function off, so battery would last long.
Hi,
From some days ago, my S200 started restarting itself sometimes (like once or twice a day)..
I thought it was something to do with the ROM but 3 days ago I woke up and the phone was completely turned off. I tried powering it on with the Power On button but nothing happened.. Tried Soft reseting and hard reseting and nothing.. Removed the battery for 10 minutes and then it powered on but the screen started flickering (horizontally).
Then I saw at BatteryStatus that the CPU speed was jumping from 195 MHz to 91 and 52, randomly (195, 52, 91, 52, 195, 91..).
I searched the net and did found almost nothing, just a forum where they say that 195 Mhz is the normal mode, 91 Mhz big sleep mode and 52 Mhz deep sleep mode.
Even if I overclock it with BatteryStatus, it doesn't maintain the speed, and slows down to 195/91/52.. (Even with speeds below 195 MHz it goes to 195).
Other think I realized yesterday was the battery discharges much faster, and I think when the phone is at Standby Mode keeps discharging the battery as if it was fully On (It never discharged me the battery in one day..).
I plugged it in yesterday night and today morning the phone was charged (green light always on) and I pressed the button to power on the screen, and nothing.. Removed the power cord and the green light kept on. Reinserted the battery (the light gone off) and tried to turn it on, and nothing.. Resets did nothing, it was completely dead. Took the battery off and after one hour put it back, and it powered on and it's working right now (with screen flickering and that CPU changes..).
I think the problem is on the CPU.. Reflashed it yesterday (Aserg 3.3.13 ROM) just to be sure it wasn't from the ROM (although I used that ROM without any problems before).
One more thing I remembered, the WiFi isn't working (from some days ago..). It doesn't turn on most of the time, and when it does, it doesn't detect any network.
Sorry for this long post, any help appreciated.
Thanks in advance
when the cpu clock gets down, it could be the cpuscaler feature of batterystatus. disable it or adjust it!
my prophet's screen also flickers if i set the cpu speed below 169mhz. so i made this as the minimal clock of cpuscaler.
disable the cpu scaler and set stepwise locker clocks than 195mhz. then test each step for screen flickering. lowest cpu lock where the flickering doesn't happen, should be you lowest cpu scaler value.
CpuScaler is disabled.. Even if enabled and I set the Min. to 195 for example, it doesn't "fix" and slows down. It's like the CPU doesn't respond to BatteryStatus..
(Yesterday before reflashing I tried uninstalling BatteryStatus but it was the same..)
By the way, it flickers when booting too, on Qtek screen, but it doesn't flick when connected to the pc (and the cpu speed keeps constant.. 195 MHz). If I overclock it keeps the same speed too! If I remove the cable, it slows down immediately to 195 and start flickering
I'm starting to think the problem is the battery.. I hope it is, instead of the CPU
But it's only when connected to the PC, I tried it connected to the wall charger but it does flick and doesn't fix the CPU clock...
Battery now goes from 100% to 10% in 7 hours in standby
I will try with another battery tomorrow to check if the problem persists..
I've tried another battery and I do have the same problems..
Now it doesn't detect usb connection (wall charger or pc charge or sync)
What the hell is happening with it?
You updated new rom or reset machine try again !
It's charging now.. :S So weird..
I'll let it charge and then I'll change the rom..
Update:
Flashed with "ruu_prophet_220734_2207114_026121_qtek_wwe_ship" but the same problems occur..
The cpu still have the same problem.. (195 MHz, 91, 52...)
Anyone with the same problem?
but you know this becouse you intalled batterystatus plug in, if not correctly configured, it is the same. right?
good luck!
I guess your device is permanently damaged, I hope you're elligible to warranty..
One last thing you'd want to try, keep your device open (at least battery & sim off) & shutdown for at least a week, then...... try again
I guess it is permanently damaged too. I'll try to sell it to spare parts.. Thanks
Hi. I recently installed Battery Status and noticed the power drainage feature on this program. I have noticed that when turn on my phone and connect to the network, the power consumption increases to around 350mA and doesn't seem to come down even with no programs (other than the usual background programs) running and CPU usage at 0 - 1%. When I plug my phone to recharge, the consumption will go down to around 75mA and remain at that level (with phone connected to network) when I unplug my phone. When I connect the phone to the computer, the power consumption will increase to 150mA and sometimes drop to around 90mA when I disconnect. What I am wondering is why the power consumption doesn't decrease when the phone is finished connecting to the network (and whether this is the source of my recent drop in battery life). It almost seems that plugging it in for a recharge resets something.
What are other users getting for average power drainage? Is there a way to manipulate the phone to achieve the lower power drainage without plugging it in? Thanks for the input.
The Nook is pretty good on battery life.
Sometimes, randomly it just drains the battery though.
I've been meaning to look into this for a while.
The start of this is posted in this general hardware thread.
There's a plot below.
It seems to indicate that there is some real problem with the Jorjin WiFi module.
The left side of the plot shows fresh booted with WiFi on.
The right side shows after it has been pinged.
The goal is to make the Nook be drawing only 10 mA all the time.
As far as the "40 mA square waves" go, what are they?
When running at 10 mA they represent a significant current draw.
With the WiFi off they run every 30 seconds for 5 seconds.
Wow, great work Renate! I hope this is a big step towards tracking down the Nook's random battery drains.
I don't have any good guesses about what would be running every 30 seconds, but I think seeing a timestamped power graph with the corresponding logcat output might be interesting.
I can't tell from the pictures, are you running this on a NST or NTSG and which firmware version?
Do you see the 30/5 waves when wifi is on, or only when it's off?
What does the power draw look like when the nook is in sleep mode?
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.
The logcat is boring, just occasional battery updates and not related to the square waves.
Oh, ClockworkMod Recovery runs at a solid 150 mA and no square waves.
Yes, I've tried power button off vs. timeout off many times and both of them go to a baseline of a mA or so.
It could be a random thing though.
To give it a real test I'd have to power it up/down 1000 times.
The power button push is no problem, but if I want to keep with an unmodified swipe I'll have to throw in a robotic finger.
Edit: Actually, if one of the side buttons is "Menu", then you can dismiss the slide dialog with that.
Still, since top does not report any real CPU activity I have to presume that this is a DC load problem.
The Jorjin is already suspicious.
I've checked the eInk power section during the square waves and that is not switching on then.
Note: The 60 second pulses on the chart are the time in the status bar updating.
The 5 second pulses do appear to be a display related activity with a timeout.
I made an app that would draw a few pixels every 10 seconds.
If it hit when there wasn't a square pulse it would start a square that would end exactly 5 seconds later.
If it hit in the middle of a square pulse the square would end at exactly 5 seconds from the start of the square, not the hit.
This is all a bit confusing because I can't detect the eInk power sections firing for all the squares (or even the full 5 seconds of any square).
The power management is complex, with 2 DC converters, 2 charge pumps, 2 LDO regulators.
The big supplies are the +/- 15V @ 120mA!
30V x 120mA / 3.7V = an Ampere or so!
Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
The WiFi when it's on, happy and doing nothing draws negligible current.
The WiFi when it's on, just woken up and not even pinged draws an additional 80 mA.
Ping it then and the current goes down to negligible.
Turn it off and the current goes down to negligible.
The USB host mode can be a really power sucker.
With just a OTG cable and no device in host mode it draws an additional 150 mA.
Put it back in peripheral mode and the total Nook drain goes to either 40 mA or 20 mA.
Put the Nook to sleep with the power button and it continues to draw 40 mA or 20 mA.
Code:
Powerdomain (core_pwrdm) didn't enter target state 0
I'm not sure how much this affects anyone else.
I am using S1 as the system console.
When you first boot the Nook, the console is in a normal mode.
It relays dmesg stuff and allows you to type commands.
If you go to sleep and then wake it up it's in a strange mode.
If you hit a console key, it only wakes for 5 seconds.
The next key that you hit will be actually registered.
This is the source of the 5 second square waves.
Type constantly and it's an additional 40 mA.
The thing is, I was seeing this before with nothing connected.
The level shifter has no pullups and was randomly triggering on noise.
A screen update is a major electrical incident that sets it off.
I'll be adding a pullup to my RX in on the console.
Safest way to save the battery (as far as I know right now):
If you reboot, don't use it immediately for long periods, sleep with the power button, then wake.
The safest for WiFi is to wake the Nook with WiFi on, then ping or connect to it.
Then turn it off. (Yes, I know that this is a bit impractical.)
The real wildcard is USB. After using USB host mode, do a power down reset.
Anybody have any insight into why this 5 second wakeup on the console?
From the current drain it must be doing a loop in software or something.
You can show your dmesg and logcat?
You do measurements with SD card?
I am confused by error after sleep
<3> [6439.043121] PM: Failed to prepare device omap3epfb.0 for power transition: error -16
I have a lot these errors. I think that the screen while drawing the screensaver is not the first time screen sleep.
I have deleted the system utility debuggerd. She is all the more load on the CPU.
Renate NST said:
Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
Click to expand...
Click to collapse
How does using the rear power button compare with long-holding the front 'n' button, or using Button Savior's virtual power button?
I always sleep with the power button.
I just checked, I removed long push of the "n" button entirely from my policy.jar
I didn't notice anything.
I may try that "sleep 1000 times" experiment.
jeff_kz said:
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.
Click to expand...
Click to collapse
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!
Sparker_95 said:
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!
Click to expand...
Click to collapse
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place
smeezekitty said:
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place
Click to expand...
Click to collapse
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.
thenookieforlife3 said:
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.
Post thank for the testing?
Click to expand...
Click to collapse
Ok a good enough. The NST without glowlight you don't have to hold it so long