You - for now - will need to download and copy to N900 the script I linked to, if you want to duplicate the above procedure. If you feel that's too complicated to put to work, please wait for next h-e-n release. This isn't meant for day-by-day usage by even early adopters.

This is a report about results of work in progress, a proper release will come as soon as I finished jrbme and supporting stuff around it (events.d script for starting, udev rule for automounting, etc) and Mohammad augmented the GUI to handle hostmode via jrbme calls rather than direct access to /sys. Mohammad told me something about 26/1 just an hour ago.
The pure jrbme script however could also be used via xterm or a set of queen-beecon buttons, so maybe you'll see it prior to next "official" h-e-n pkg release.

cheers
jOERG

Thanks Joerg. Thought I'd ask as I wasn't 100%, and it might help others.

I'm a big fan of this project, so thanks for the update.

ok, now this is my experience with h-e-n so far:
i only attached a kingston datatraveler 2GB, and it successfully mounted, BUT only if i uncheck a box: "Open file manager after mount" in setting dialogue....
don't know why is this making problems, but, i cannot mount my usb stick if that checkbox is checked
so to be clear: no matter if my file manager is open or closed, i CAN mount, and everything is ok, only if that i don't check to open file manager after mount...
maybe a little bug, but everuthing else is working fine
thx!!!

Known bug in h-e-n GUI.
IIRC it's something along the line "binary missing or not executable".
Nevertheless, thanks for reporting
Please keep in mind [mount] has been marked as transient and unsupported from beginning. Mounting will be handled by udev rule, probably starting with next version scheduled to roll out end of this month

cheers
jOERG

ok! will keep that in mind
anyhow, i have one more... hmmm... question: i have ENORMOUS power drain, when using h-e-n... is that normal...??? (didn't test it for how much long it could keep, but on battery graph, it shows almost VERTICAL line...)

bme / stock applet reports a way-off battery meter, restarting bme kicks it back into action, so the vertical line might actually bme remembering it has to check battery life.

As Mohammad said - bme is guestimating, and the only interesting thing about that effect is that it sheds some light on how bme internally works to calculate battery remaining capacity. It seems bme is remembering data bits from last run, after start - probably saved in CAL - and on noticing differences in battery voltage during what bme thinks had been no time, it gets panic about battery status.

For the grip of real life: VBUS boostmode (the 5V) can deliver max 200mA to USB, so that's ~1W and shouldn't eat more than 30% of battery capacity per hour, on maximum load of USB VBUS. The CPU, when constantly running at high clockrate will also eat more power than on idle, but that's comparable to watching video or any other high system load.

And then there's "charging while hostmode" (post #647) to get rid of all battery depletion concerns :-D

cheers
jOERG

ok! thx for the answers! so i could keep my battery safe for about 4 hours when mounted usb stick.... that's ok i think (like browsing on net, and installing apps in a same time would kill battery in same time...)

I've watched a full length movie (~2hrs) from a USB flash drive during h-e-n, and it went from fully charged to around 35%.

As already noted, there are ways around that. And really, having a short run of non-tp cable will simply slow down the connection. It won't stop it from working all together. I'll suffer with USB 1.0 speeds if it means I have 0 chance of my internal USB port falling off.