Active Topics
-
maemo.org (0)
to Community by teroyk - 17 mins ago -
Old stuff for Nokia 770 (0)
to Nokia 770 by teroyk - 1 hr, 20 mins ago - more...
 |
tso |
2011-05-28
, 00:05
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#681
|
all where running, and restarting them did not help. Rebooted before i could check gconf tho. If i get it again i will check.
|
|
2011-05-28
, 00:58
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#682
|
Originally Posted by tso
Oh, I thought your sound had completely stopped working even after a reboot.
all where running, and restarting them did not help. Rebooted before i could check gconf tho. If i get it again i will check.
|
|
2011-05-28
, 01:14
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#683
|
heh, not yet. Who knows about the future tho 
|
|
2011-05-29
, 14:39
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#684
|
@ maacruz, I implemented your formula and it doesn't work.
Device idle, active time of 1 hour and 25.2% battery, your drain rate is 25.2%. A rate based on one data point doesn't work well.
While playing a video with wifi active ASUI reported a 3%/hr drain while my battery was dropping from 25.2 to 23.9 and 1 active hour, dropping to 0 for two of the 10 capacity changes. Not sure how that zero active hours should be handled but the drain rate was decreasing under load.
The formula appears to be okay at higher capacities because active hours is able to fluctuate between a larger range but due to the lack of precision in active hours it breaks down at lower capacities. I'm going to comment out the code for now and play around with a drain rate for last 5,10,15 minutes but if you want to tweak the formula I'll turn it back on.
Device idle, active time of 1 hour and 25.2% battery, your drain rate is 25.2%. A rate based on one data point doesn't work well.
While playing a video with wifi active ASUI reported a 3%/hr drain while my battery was dropping from 25.2 to 23.9 and 1 active hour, dropping to 0 for two of the 10 capacity changes. Not sure how that zero active hours should be handled but the drain rate was decreasing under load.
The formula appears to be okay at higher capacities because active hours is able to fluctuate between a larger range but due to the lack of precision in active hours it breaks down at lower capacities. I'm going to comment out the code for now and play around with a drain rate for last 5,10,15 minutes but if you want to tweak the formula I'll turn it back on.
|
|
2011-05-29
, 14:59
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#685
|
Heh, i am tempted to ask if that overlay can be hijacked to show cpu use rather then battery drain rate. This as i removed the load-applet as i wanted to save tray space (and it was somewhat redundant as ASUI provides much the same features).
__________________
Be warned, posts are often line of thoughts at highway speeds...
Be warned, posts are often line of thoughts at highway speeds...
|
|
2011-05-29
, 15:01
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#686
|
Originally Posted by auouymous
Yes, I also implemented the formula yesterday and arrived at the same conclusions.
@ maacruz, I implemented your formula and it doesn't work.
Device idle, active time of 1 hour and 25.2% battery, your drain rate is 25.2%. A rate based on one data point doesn't work well.
While playing a video with wifi active ASUI reported a 3%/hr drain while my battery was dropping from 25.2 to 23.9 and 1 active hour, dropping to 0 for two of the 10 capacity changes. Not sure how that zero active hours should be handled but the drain rate was decreasing under load.
The formula appears to be okay at higher capacities because active hours is able to fluctuate between a larger range but due to the lack of precision in active hours it breaks down at lower capacities. I'm going to comment out the code for now and play around with a drain rate for last 5,10,15 minutes but if you want to tweak the formula I'll turn it back on.
But later I also realized that we both are looking at the wrong place.
We are looking at bme dbus responses, and those are deeply flawed, the active time has a accuracy of 60 min, and the idle time also has a accuracy of 60 min, not good.
But I remembered advanced-power did it different, it connects directly to bme. I've been playing with it and it give us much more data and with much more time resolution and accuracy, like current drain in uA averaged over 5 seconds, and battery remaining time updated every minute.
I'm trying to do a little test program in python but I did a mistake somewhere. Unfortunately any mistake in talking to bme causes the device to reboot. Just wait a bit while I iron out the bug.
| The Following User Says Thank You to maacruz For This Useful Post: | ||
|
|
2011-05-29
, 16:43
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#687
|
Originally Posted by tso
Would a tiny 4 pixel tall horizontal bar below the battery work? Drain on top, wifi and bluetooth on sides and cpu usage below?
Heh, i am tempted to ask if that overlay can be hijacked to show cpu use rather then battery drain rate. This as i removed the load-applet as i wanted to save tray space (and it was somewhat redundant as ASUI provides much the same features).
Only problem is that it will consume cpu even when the applet is not visible. Hildon-desktop constantly uses about 1% cpu when load-applet is enabled. Will add a setting to disable for those who don't want it.
Originally Posted by maacruz
Okay.
I'm trying to do a little test program in python but I did a mistake somewhere. Unfortunately any mistake in talking to bme causes the device to reboot. Just wait a bit while I iron out the bug.
|
|
2011-05-29
, 17:18
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#688
|
Originally Posted by auouymous
WOW, everything but the kitchen sink crammed into one applet?
Would a tiny 4 pixel tall horizontal bar below the battery work? Drain on top, wifi and bluetooth on sides and cpu usage below?
I'm done with the crappy test program. Run it with "python BMEFree.py"
You are gonna absolutely love this.
| The Following User Says Thank You to maacruz For This Useful Post: | ||
|
|
2011-05-29
, 18:14
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#689
|
Originally Posted by auouymous
No argument from me
Would a tiny 4 pixel tall horizontal bar below the battery work? Drain on top, wifi and bluetooth on sides and cpu usage below?
__________________
Be warned, posts are often line of thoughts at highway speeds...
Be warned, posts are often line of thoughts at highway speeds...
|
|
2011-05-29
, 19:56
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#690
|
New test release
If you've made your own theme you will need to move it to /home/user/.asui-themes first or it will be deleted. You will also need to rename and add a few colors.
asui uu; asui dc; asui dt; asui da; asui ds; asui it; asui is
@ maacruz, are the drain icons better? I haven't looked at your python script yet but this indicator is average for last 5 minutes.
- larger statusbar drain arrows
- statusbar drain rate is %/hr over last 5 minutes
- statusbar drain rate updates every two minutes while screen is on
- statusbar drain rate disables if cfg_history_days=0
- user themes can be added to /home/user/.asui-themes/
- `asui dc` deletes old /etc/asui-themes files
- added blue_color, renamed status colors, renamed white_color to bold_color
- added a statusbar settings page
If you've made your own theme you will need to move it to /home/user/.asui-themes first or it will be deleted. You will also need to rename and add a few colors.
asui uu; asui dc; asui dt; asui da; asui ds; asui it; asui is
@ maacruz, are the drain icons better? I haven't looked at your python script yet but this indicator is average for last 5 minutes.
 |
| Tags |
| bada blows, bada rox |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 17:03.