Re: [tuxdroid-user] Hello; Working with svn ; several questions & suggestions

[Florent T. <ft...@gm...>]

> > - what about autonomy ? Standby (idle) time? "Regular use" battery
> > time?
> Didn't do checks yet but that should be a around 15h but that depends on
> mutliple factors. We need to implement the sleep mode and I hope to reach much longer
> battery life then, a few days probably.

I guess my tux will stay plugged in then :)

> Yep, voltage should be there but not implemented yet, that should not be
> very hard though. But I have no idea on how to get a battery level out of
> that.

As long as we can retrieve a voltage value, we have to use/create a
model of the battery's voltage evolution. I guess acpi's guessing (the
one you get when typing "acpi") relies on such a model, and would give
us hints. What type of battery is it?

> > - about IR: what can we do with it? I mean, of course using the
> > remote, but can tux emit IR? Or is it just recieving? Because if yes,
> > it means tux could act as the first vocal universal remote :)
>
> Atm only RC5 works, you can receive all RC5 codes and send them. I found
> an application note to be able to have a universal receiver/emitter but I
> would want to know if this will be compatible with lirc before doing so.

There's a feature that would be great if tux can emit: a IR recording
mode; you just type the sequences on your regular remote in front of
tux, then you assign a vocal command to them (ex: tv on + dvd player
on + switch tv source + open tray...). We don't really need our
software to "understand"/know the devices, do we? Just mimicking...

> > - about mic : quality? Enough for basic voice recognition? What's the
> > peripheral (/dev/?) ?
> That should be fine for voice recognition.

I'd love to log in/out using voice, or simply audiosudo ^_^ (a pam module?)

> I would prefer to have small scripts that work and a good daemon before
> doing that [super app].

Sure, that's logical :)

> > - python question: what's the "command"/call for knowing the existing
> > objects?
>
> I'm not better than you. But you can use dir(tux) or dir(tux.cmd)

Thx, that's what i was looking for.

> We should use doxygen to generate all the documentation. Someone already
> created the missing configuration file though for the moment you'll get a
> listing of all the functions with only few documentation. You can also
> look at the python class directly and start documenting it ;-)

I started to look, but i lack practical skill and tux knowledge. Plus,
i'm out of time for now, but i may have some in a while.

Thanks for the answears !

Florent