Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
12 hours remaining... yeah, right.
02-18-2010, 12:30 PM
Post: #1
12 hours remaining... yeah, right.
[Image: Capture2.PNG]

Oh, I wish. Actually, it showed 17 before I managed to get a screenshot.

Now it's showing 4:51. That's more like it.
Find all posts by this user
Quote this message in a reply
02-19-2010, 07:19 AM
Post: #2
RE: 12 hours remaining... yeah, right.
Does this happen frequently? If so, you can capture a log so I can see why that's happening. Use the steps here:
http://osirisdevelopment.com/wiki/Submit_a_bug_report

BatteryBar's time estimation does two things:
1) It calculates a time remaining based on history averages of number of seconds each percentage point takes to discharge
2) That value is adjusted based on an accuracy measurement. The accuracy measurement measures that actual amount of time elapsed while running on battery versus the estimated time elapsed. It calculates a ratio between the two and adjusts the display accordingly. For example, if you're watching a movie, you'll see the time estimation drop. If you're not doing anything and the screen is off, you should see the time remaining go up. My guess is that the accuracy calculation got messed up somehow. I'd like to see a log if you can reproduce the issue.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-19-2010, 07:40 AM
Post: #3
RE: 12 hours remaining... yeah, right.
I've only seen it once. And it isn't nearly as absurd as the 120 hour calculation I've seen OS X give.
Find all posts by this user
Quote this message in a reply
02-19-2010, 05:01 PM
Post: #4
RE: 12 hours remaining... yeah, right.
Well at least you know what's going on now. I do think I should put some limits on the accuracy calculation, such as nothing below 50% or above 150% of normal usage.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-23-2010, 11:24 AM (This post was last modified: 02-23-2010 11:25 AM by Sovereign.)
Post: #5
RE: 12 hours remaining... yeah, right.
(02-19-2010 05:01 PM)Chris Wrote:  Well at least you know what's going on now. I do think I should put some limits on the accuracy calculation, such as nothing below 50% or above 150% of normal usage.

Well, define "normal usage." My "normal" usage is 4-5 hours, but if I turn off wireless, dim the screen down, terminate background processes and run only one app (OneNote) I can get 7 real hours out of my computer. My computer is an energy-hungry Inspiron E1505. I'm betting that some smaller computers can see even greater variance in power usage from "heavy" to "light" usage.

In my case I'd be getting 140% of "normal." Not outside your range, just food for thought.

Also, regarding "nothing below 50%" if your battery begins to die, it will have a lifetime possibly less than "50% of normal usage." Further, if your computer essentially has all its power saving features turned off (portable gaming mode) it may be possible to breach the 50% lower value.
Find all posts by this user
Quote this message in a reply
02-24-2010, 04:50 PM
Post: #6
RE: 12 hours remaining... yeah, right.
I haven't actually implemented that idea.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-25-2010, 06:47 AM
Post: #7
RE: 12 hours remaining... yeah, right.
Time estimates of BB Pro 3.3.3 are weird. I have never seen such estimates in 3.3.2.
I have fully charged my battery. My usual total time estimate by BB is 7+ hours. After some 20-30 minutes on battery I noticed an estimate in the tray 6+ hours. But what is strange this time was growing. Here is the picture
[Image: 939f5007948e.png]
I was doing web browsing using the power scheme I usually use, reading the usual sites and forums. The power consumption was quite usual.
here are some lines from BatteryBar.Profiles.xml
Code:
<PercentTime Percent="84" Time="271" Samples="4" />
      <PercentTime Percent="85" Time="269" Samples="5" />
      <PercentTime Percent="86" Time="267" Samples="5" />
      <PercentTime Percent="87" Time="261" Samples="5" />
      <PercentTime Percent="88" Time="256" Samples="4" />
      <PercentTime Percent="89" Time="222" Samples="3" />
      <PercentTime Percent="90" Time="261" Samples="3" />
      <PercentTime Percent="91" Time="285" Samples="3" />
      <PercentTime Percent="92" Time="299" Samples="4" />
      <PercentTime Percent="93" Time="312" Samples="5" />
      <PercentTime Percent="94" Time="330" Samples="4" />
      <PercentTime Percent="95" Time="281" Samples="4" />
      <PercentTime Percent="96" Time="256" Samples="5" />
      <PercentTime Percent="99" Time="0" Samples="1" />
Visit this user's website Find all posts by this user
Quote this message in a reply
02-25-2010, 08:18 AM
Post: #8
RE: 12 hours remaining... yeah, right.
If you use less battery than usual, BatteryBar makes an adjustment for that. It does this by comparing the actual time that the computer has been running to the estimate time it should have run.

Right now there's now way to see what that ratio is without generating a debug log. Perhaps it would be a good idea to include that information somehow.

Turn on debugging by holding SHIFT while you right-click on BatteryBar. In the log file you'll see some entries about the Accuracy ratio/percent. That value is multiplied against the time remaining to make the adjustment.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-25-2010, 03:46 PM
Post: #9
RE: 12 hours remaining... yeah, right.
Chris I think the weird estimate is due to the line PercentTime Percent="99" Time="0" Samples="1". I usually do not charge my note when it is on. This time I've inserted power plug when working with note. After the battery was fully charged I have pulled the power cord off after some 10-20 minutes. That gave me (after the power adapter was pluged off) not 100% but 99% - this makes this record. It is also strange - there are no records with 98% and 97%. I am sure this charges (98% and 97%) lasted some time (some minutes).
I have already send you the debug log on the problem described here - http://osirisdevelopment.com/forum/threa...tml#pid266 (jump at 50%). This jump also ocures in 3.3.3.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-25-2010, 06:38 PM
Post: #10
RE: 12 hours remaining... yeah, right.
The fact that your battery profile doesn't contain data for 95-98 percent wouldn't cause the time remaining to increase as you discharge. The fact is, those data points that are missing are extrapolated based on surrounding data points, so those points will be estimated at approximately 250-300 seconds each.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


[-]
Quick Reply
Message
Type your reply to this message here.


Image Verification
Please enter the text contained within the image into the text box below it. This is necessary to prevent automated signups.




Real Time Web Analytics