<uvos>
_inky: porting maemo mapper would be neat but if you need something right now that works dose navigation and vector maps navit is in the repos and works fine and is even touch frendly (atho clunky)
<_inky>
uvos, i never was able to use navit on fremantle, don't remember why. but i'll try again. i remember i was in love with maemo-mapper for some reason.
<uvos>
on leste it works fine i use it regularly
<uvos>
you have to configure the xml file a bit to get resonable ui
<uvos>
otherise it works out of the box
<uvos>
you need to donwload maps for it too ofc get them here
<uvos>
i dident do anything :P its in the debian/devuan repos
<_inky>
downloadable maps are cool for offline work. (:
<_inky>
oh.
<uvos>
but i think i should publish my config
<_inky>
but what does it use? liblocation? gpsd?
<uvos>
gpsd
<_inky>
it works on droid with gpsd?
<_inky>
cool.
<uvos>
yeah
<tmlind>
so for the n900 off idle issue, i think the bug is kernel is too busy with timers to hardly ever hit the 484ms target residency. somebody should measure longer term idle power consumption though with lower values, i suspect it still saves power below 484ms sleep lengths
<uvos>
tmlind: btw i noticed that ret wakeups on d4 can be reduced in frequency a bit by messing wihth the sched
<uvos>
might help here too
<uvos>
*the sched values
<tmlind>
uvos: yeah cool i saw that
<uvos>
but yeah not way the kernel is ever going to sleep for half a second
<uvos>
at least in its current state
<tmlind>
nope.. n9 often slept for about 8 seconds between debug led blinks :(
<uvos>
might make sense to trace the timers a bit
<tmlind>
yeah
<tmlind>
so n900 should be idle and limited to a single cpuidle state at a time while measuring
<tmlind>
some kind of sample integration is needed to get let's say 10 minute total power consumption
<tmlind>
well i guess those cheapo usb charge monitor dongles will show the cumulative power consumption
<uvos>
the n900 battery chip should be enough no
<uvos>
it has a charge counter
<tmlind>
oh ok yeah that should do
<Wizzup>
I have a n900 on lab psu, so could use that too for measuring
<tmlind>
Wizzup: ok, not seeing a charge counter after bq2415x_charger, don't have a battery connected if that matters
<tmlind>
hmm or was it the twl madc that's needed?
<tmlind>
rx51_battery module using twl madc i guess
<_inky>
can you remind me, so we supposed to have maemo/beowulf branch, and the builder bilds code from that branch?
<_inky>
or from master?
<Wizzup>
inky_: tag master, maemo/beowulf for debian/ dir
<_inky>
so maemo/beowulf branch contains debian dir, ok, i understand that.
<_inky>
but tag should be done in master?
<_inky>
ok.
<_inky>
and the builder will take debian dir from maemo branch, and tag from master?
<_inky>
ok.
<tmlind>
not seeing a charge counter with cat /sys/class/power_supply/*/uevent, should not be hard to add it based on the madc data. although reading might affect the idle states..
<uvos>
someone had a userspace script to dump that
<uvos>
i have been trying to find it the last 5min :P
<tmlind>
i don't think madc has a charge counter, but maybe it's sampling time can be set long enough to not require much polling
<uvos>
ok i was pretty sure it did
<uvos>
but maybe the script was simply calculating behind my back
<tmlind>
oh ok
<tmlind>
i sort of recall madc being just a few raw adc inputs
<uvos>
i might be wrong
<uvos>
im just basing this off me running this script and viewing its output once
<tmlind>
the bq chip might have one though
<uvos>
the bq chip has one internaly for sure
<uvos>
but looking at the register datasheet you cant read it drectly
<tmlind>
so maybe the script you're talking about is using i2cget on the bq2415x chip?
<tmlind>
ah ok
<uvos>
ah its bq27200
<tmlind>
oh
<uvos>
there is another bq27200 fule guage
<tmlind>
right, i forgot :0
<tmlind>
:)
<uvos>
heh :P
<uvos>
yeah the script was just i2cget'ing from that
<uvos>
for sure
<uvos>
you wil lwant to read 0x15 and 0x14
<tmlind>
looks like after modprobe of bq27xxx_battery_i2c i see power average but not charge counter, weird that it's not implemented if it can be just read
<tmlind>
here's another good project for somebody :)
<uvos>
er 0x21 -0x20
<uvos>
its not totaly directly
<tmlind>
uvos: any idea what units the register shows?
<uvos>
Available Energy in mWh
<tmlind>
ok
<uvos>
effectively a charge counter
<uvos>
(just in reverse)
<tmlind>
yeah ok
<uvos>
you also have to devide by the shunt
<uvos>
its external to the chip
<uvos>
so you need to know what value nokia used
<uvos>
but its irellivant if you just want to compear values
<uvos>
between to operating states to figure out what uses more power
<tmlind>
hmm yeah, that should be a fun project to award to somebody as writing linux kernel drivers project :)
<Wizzup>
I tried that on my d4 and it didn't give me a launcher yet
<freemangordon>
(23,42,05) freemangordon: uvos: any clue why hildon-desktop does not update applicatyions in the launcher when new one is installed? is that common issue?
<freemangordon>
:)
<Wizzup>
yeah that helped
<Wizzup>
weird
<freemangordon>
mhm
<freemangordon>
anyway, I need sleep, night!
<Wizzup>
hm I can't change the port number for the imap server
<Wizzup>
gn
<Wizzup>
freemangordon: cool, works
<Wizzup>
scrolling through messages doesn't work on the d4 though for some reason
<Wizzup>
hmm now it does
<Wizzup>
really cool.
<Wizzup>
managed to email myself as well
belcher has quit [Ping timeout: 245 seconds]
belcher has joined #maemo-leste
<_inky>
people, please open two repos for me: lagrange and oricutron. i am ready to push and test.