[TESTING] SCBS: Improved battery meter system

[toadlife]

Originally Posted by arrrghhh

What I'm wondering is how to stop it? Does it just perpetually take logs?

By default, it logs to /sdcard/scbs.log, but you can effectively disable logging by making it log to /dev/null

e.g. `scbs -d -co /sdcard/scbs.conf -lf /dev/null`

Here are the command line options...

 # scbs --help
scbs --help
Warning: Failed to open config file /etc/scbs.conf
Super cool battery software, version: 0.04.a

Usage: scbs [OPTIONS]
Start battery daemon or perform maintance functions on data files.

Mandatory arguments for long options are mandatory for short options too.
  -h, --help                display this help and exit
  -v, --version             display scbh version number
  -pn                       print nan warnings to console
  -df PATH                  use device file def:(/dev/scbs0)
  -lf PATH                  use file for logging def:(/sdcard/scbs.log)
  -co PATH                  use file for initial config def:(/etc/scbs.conf)
  -d                        start sbcs in daemon mode
  -s INT                    set the sleep mode data interval def:(5000)
  -w INT                    set the wake mode data interval def:(5000)
  -cf REAL                  set the charge scale factor def:(0.312500000)
  -vf REAL                  set the voltage scale factor def:(1.098000000)
  -se REAL                  set the sleep error constant def:(0.007000000)
  -ln PATH                  open data file and use it to compute linearization
  -n PATH                   open data file and use it to compute Rc,Cc,Re,Cb
  -nr REAL                  set nls learning rate def:(0.000010000)
  -wf                       write the computed battery model out to the config file
  -l PATH                   open data file and generate stream of Cb estimates
  -lr REAL                  set luenberger learning rate def:(0.000001000)
  -rc REAL                  set Rc value def:(0.028796000)
  -re REAL                  set Re value def:(0.130299000)
  -cc REAL                  set Cc value def:(2.064020000)
  -cb REAL                  set Cb value def:(64.219460000)
  -sl REAL                  set Cb slope value def:(0.000000000)

[ndno]

Originally Posted by toadlife

By default, it logs to /sdcard/scbs.log, but you can effectively disable logging by making it log to /dev/null

e.g. `scbs -d -co /sdcard/scbs.conf -lf /dev/null`

Here are the command line options...

Thanks for the syntax. I think I'm happy with my model now so I'm going to disable logging by redirectly to /dev/null. That should lighten up the writes to the SD card constantly.

[toadlife]

jonpry,

I'm having a strange issue with scbs and was wondering if you could shed some light on why this was happening.

I've integrated scbs into F22's latest rootfs and in /init I've integrated the following code, which starts debug logging and scbs

    logfiledate=`date +%Y%m%d%H%M%S`
    cat /proc/kmsg>"$card"/debuglogs_kmsg_"$logfiledate".txt &    
    logcat -v time >"$card"/debuglogs_logcat_time_"$logfiledate".txt &
    logcat -v time -b radio>"$card"/debuglogs_logcat_time_radio_"$logfiledate".txt &


    dev=$(cat /sys/class/scbs/0/dev | sed -e "s/:/ /g")
    mknod /dev/scbs0 c $dev


    scbs -d -co /sdcard/scbs.conf

The problem I am having is that, if I enable scbs, it causes both instances of logcat to crash with the errors 'unable to access /dev/log/main' and 'unable to access /dev/log/radio'.

I tried starting scbs before the logging and after, and it makes no difference. I also tried some other things like having the script sleep for 5 seconds but the result is always the same. If I start scbs via gscript logcat does not blow up, so it seems like it might have to do with them being fired of in the same tty.

[hlo]

Originally Posted by ndno

Thanks for the syntax. I think I'm happy with my model now so I'm going to disable logging by redirectly to /dev/null. That should lighten up the writes to the SD card constantly.

I probably missed a post about this but what file do I edit to redirect to /dev/null? Thanks.

[toadlife]

Originally Posted by hlo

I probably missed a post about this but what file do I edit to redirect to /dev/null? Thanks.

The file /init

It's possible to edit it directly on your phone, but it might be easier to download the file using droid explorer, edit it and re-upload the file.

You have to remount your rootfs so that it is writable in order to change the file

mount -o remount,rw /

Set permisisons on the Remount the fs read only after you're done...

chmod 755 /init
mount -o remount,ro /



If you are confused by any of the above, I would recommend you NOT do this.

[steveholtam]

I'm trying to stop SCBS by using /dev/null via a terminal emulater. I have set rootfs as writable, but after running the /dev/null code as written above, I get the following error:

Cannot open device: /dev/scbs0

Anyone have a clue on what I should try? THANKS!

[toadlife]

Originally Posted by steveholtam

I'm trying to stop SCBS by using /dev/null via a terminal emulater. I have set rootfs as writable, but after running the /dev/null code as written above, I get the following error:

Cannot open device: /dev/scbs0

Anyone have a clue on what I should try? THANKS!

You are getting that error because scbs is already running. You can't stop scbs once it's running. In order to change the way it logs you have to edit the file /init and reboot the phone.

You should probably just leave things as they are if you don't understand what that means.