cero

i'm no longer using ideal

just install the updated batterypatch
it has a new profile (better one) and fixed

and about the battery meter
i don't use advanced power
but i have read somewhere that the problem is caused by kernel-power v 47
not sure although

maybe because you use a lot of batteries
that happened with me when i switched 2 different batteries

hmm. :/

it was working fine until i ran your battery script.

i tried to start and stop the bme to see if it would kick-start it...but no go. just crashed the device.


on the new battery profile, should we load anything, or just let it run without kernel-config?

i see

maybe try to remove advanced power
becuase my script changes vfs to 10 when lock
whcih will give more battery life
that makes advanced power get confused
i guess

trying now. though i am not sure why it would have an issue...it is just a status menu plugin to show percentage, time left active, time left idle plugin.

:/

edit:

i just uninstalled the advanced power. then the battery dissapeared. so i reset the status menu.

you were right...there was something that the advanced-power was not liking! the battery meter shows normally now.

good advice karam. thanks.


i am going to download and reinstall the battery patch you added on the first post righ now to see if there is anything new that i may not have recieved when i did it last time.

when i am running this command

i am getting this...is this correct?

also, so at this point, my assumption is that custom-karam has just been made my default kernel even after a reboot?

is that correct?

@karam

How to check dbus-scripts working properly. After apply new battery patch either sleep or normal activity my vfs still show 1000

Nokia-N900:/opt/scripts# cat /proc/sys/vm/vfs_cache_pressure
1000

TQ

to apply the battery patch do we need to install power kernel..coz i have default installed kernel..???

@ceroberts75
you are doing fine
nothing is seems to be wrong

@meLi
if the vfs shows 1000 (looks like you have changed it from 100 to 1000)
but when you lock it should change to 10
but you can't see that because it's locked
but when you unlock it should be changed to 100
that means the patch wasn't applied successfully
means that dbus-scripts are not running
have you uninstalled the old version before installing the new one?


@cutehunk04

i'm not sure about the dbus-script if it needs kernel-power
probably not

but for the profile
i'm sure it needs kernel-power

however if you don't use kernel-power you need to edit the script to not load the profile and make it default

also not install kernel-power-settings
but i strongly recommend kernel-power

i can confirm that the battery patch is very effective
yesterday i hammered my N900 a lot and spent full day
still 66%
awesome result

also the speedpatch is very effective
i have faster multi task and asphalt5 doesn't need to be launched twice
to turn smooth
it is smooth from the first launch

yes i did uninstall old version and appy new battry patch. Look like dbus-scripts not running. How to run dbus-script. Old battery patch working fine i can check vfs=10 and 100 ssh to n900 using putty.

Nokia-N900:~# cat /proc/sys/vm/vfs_cache_pressure
1000
Nokia-N900:~# ps aux | grep dbus*
801 messageb 3292 S < /usr/bin/dbus-daemon --system --nofork
1136 user 2832 S dbus-launch --exit-with-session
1148 user 3088 S < /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
1524 user 1972 S dbus-monitor --session type=signal,interface=org.free
1540 root 3596 S /usr/sbin/dbus-scripts --session
1546 root 3420 S /usr/sbin/dbus-scripts --session
1640 user 39804 S < /usr/bin/mafw-dbus-wrapper mafw-gst-renderer
1647 user 8052 S /usr/bin/mafw-dbus-wrapper mafw-iradio-source
1659 user 16916 S /usr/bin/mafw-dbus-wrapper mafw-tracker-source
1674 user 9260 S /usr/bin/mafw-dbus-wrapper mafw-upnp-source
2084 root 2092 S grep dbus*
Nokia-N900:~#

FIXED
Follow don_falcone http://talk.maemo.org/showpost.php?p...postcount=1671

Test and working but have some questions

If keyboard open but brightness=0 vfs=100

If keyboard open and manually screen lock vfs=100