Originally Posted by MohammadAG

Well, most of you don't know this, but, PR1.3 introduced two things:
Backports of new kernel patches to musb, which really helped with hostmode.
And.. a new bug, if you connect the wall charger to the device, 100% of the time it will stay on 500 (sometimes 550?) MHz, we do not know the behavior of an overclocked device when this bug is triggered on it, if it stays clocked @ 900 (for example), then we're going to see some dead devices pretty soon.
Anyways, hostmode's patches require 1.3's patches to musb, so until titan updates his kernel, it's a no go, feel free to contact his email address (see http://maemo.org/packages/view/kernel-power-flasher and click his name) and request an update.

Originally Posted by joerg_rw

here an intermediate version of booston, that replaces original file and has some small goodies - a direct uncleaned copy of what's on my hostmode devel device. You might want to edit /etc/mce/mce.ini to define a new pattern "PatternVboost" signalling device is in boostmode (attached my mce.ini for an example).
Of course you may want to keep permissions and owner of original booston, and maybe you need to change the hardcoded path to ic2set in this script (the line "i2cset=/usr/local/sbin/i2cset") to your result of `which i2cset`

This is no official update but just a teaser, as I'm feeling sad with all of you while this is collecting dust on my t900.

Bear with me, a better version is about to include charging and slowly matures here...

/j

Code:

#!/bin/sh
# jrbme "just replaces bme" in fact does more than just that
# It implements FOSS charging via bq24150 and manages hostmode
# For this it implements a daemon mode which is entered by default
# when jrbme is called by user root (i.e. on system init usually) 
# and which cares about keeping battery charged and about signalling
# battery charge status and other events via system dbus 
# When called by any user who's not root, jrbme doesn't enter daemon 
# mode. Instead it serves as a cmd interface between user and a daemonized
# instance of itself, talking to the daemon via signal and named pipes,
# and reporting back to user all result codes, messages to stdout/stderr.
#
# sed -i "s/LEDPatterns=/LEDPatterns=PatternVboost;/" /etc/mce/mce.ini
# vboost with reset on exit and (#'d) partial hostmode for PF-kernel
#(c) 20101030 J.Reisenweber

set -eu
true=true
false=""

${debug=/bin/false} && set -vx; # call like ~# debug="echo -n $0; date" script.sh

#const
PatternVboost=PatternVboost
dbus-send="/usr/bin/run-standalone.sh /usr/bin/dbus-send"
i2cset=/usr/local/sbin/i2cset

#var
: ${start_bme=true}
: ${notify=true}



trap cleanup INT QUIT TERM EXIT
cleanup(){
  trap - INT QUIT TERM EXIT

  # reset bq24150
  $i2cset -y -m 0x80 2 0x6b 0x04 0x80

  # stop LED indicator 
  $dbus-send --system --type=method_call \
    --dest=com.nokia.mce /com/nokia/mce/request \
    com.nokia.mce.request.req_led_pattern_deactivate \
    string:$PatternVboost

  $debug && (
    Reg1=`$i2cget -y 2 0x6b 0x00`
    echo $Reg1
  )
  
  if [ $start_bme ]
  then
    sleep 2
    log "Starting bme"
    /sbin/start --quiet bme
  fi
  exit
}

log(){
  echo "${0}: $@"
}

logn(){
  echo -n "${0}: $@"
}

# the script body. We read in whole text, and then execute a main at end of script,
# this ensures the whole script has correct syntax and there'll be no reads at 
# runtime
main(){
  log "Stopping bme"
  /sbin/stop --quiet bme
  sleep 3
  #echo host >mode
  
  # start vbus boost 5V
  $i2cset -y -m 0x07 2 0x6b 0x01 0x05;
  
  # set notification LED
  $dbus-send --system --type=method_call \
    --dest=com.nokia.mce /com/nokia/mce/request \
    com.nokia.mce.request.req_led_pattern_activate \
    string:$PatternVboost
  
  #sleep 1
  #echo F >/proc/driver/musb-hdrc

  while sleep 5; do
    Reg1=`$i2cget -y 2 0x6b 0x00`
    if [ 8 -ne $(( Reg1 & 0x0F )) ]; then
      errortext1="ERROR in VBUS supply: BQ24150-Reg1=$Reg1"
      case $(( Reg1 & 0x07)) in
        0) errortext2="No error, just stopped";;
        1) errortext2="VBUS OVERVOLTAGE - You just fried your N900";;
        2) errortext2="OVERLOAD - N900 can deliver max 200mA. VBUS got shut off";;
        3) errortext2="Battery too low. VBUS shut off";;
        4) errortext2="Battery OVP - WTF are you doing?";;
        5) errortext2="Thermal Shutdown (too hot)";;
        6) errortext2="Watchdog expired. Script sucks";;
        *) errortext2="WTF? This should not happen";;
      esac

      log "$errortext1"
      log "$errortext2"
      if [ $notify ]; then
        $dbus-send --type=method_call --dest=org.freedesktop.Notifications \
         /org/freedesktop/Notifications \
         org.freedesktop.Notifications.SystemNoteDialog \
         string:"`echo -en "Shutting down 5V supply for USB! Reason:\n$errortext2"`" uint32:0 string:"WARN"; #no idea about WARN
      fi
      cleanup
    fi
    
    # tickle watchdog timer
    $i2cset -y -m 0x80 2 0x6b 0x00 0x80;
  done
  cleanup
}
main "$@"; exit

Originally Posted by Estel

with updated booston, hostmode works like a charm.

Originally Posted by Estel

Huge thanks joerg_rw, but could You tell me - it was related to my device, or every "generic" user should get this problem? I.E, it was not reported, cause no one dared to test it before, or it's just fault of my configuration?