norayr has left #maemo-leste [Error from remote client]
xmn has quit [Ping timeout: 260 seconds]
xmn has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
Danct12 has joined #maemo-leste
alex1216 has joined #maemo-leste
norayr has joined #maemo-leste
dev has joined #maemo-leste
Twig has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
uvos__ has joined #maemo-leste
uvos__ has quit [Remote host closed the connection]
uvos__ has joined #maemo-leste
<buZz>
i wish the calibration of battery was a bit simpler to hit :P
<buZz>
i went 1100 > 900 > 1200 > 400 > now 750
<buZz>
lol
<buZz>
no clue why it went from 1200 to 400 in a single calibration cycle, maybe i was burning a lot of cpu
<sicelo>
bad battery :-p
ceene has quit [Read error: Connection reset by peer]
ceene has joined #maemo-leste
mardy has joined #maemo-leste
<buZz>
still, i'd love to be able to do 'calibrate now' and some interface tells me its status / if its done
<buZz>
but no doubt these batteries are bad, sure :D
<Wizzup>
maybe discharge it almost entirely and then go to charge mode?
<Wizzup>
btw, my / filled up again with kernel oopses
<Wizzup>
6GB kern.log, 6GB syslog, 6GB messages
<buZz>
gee
<buZz>
maybe we should install logrotate by default? :)
<r3boot>
^_^
<buZz>
Wizzup: i keep trying to hit the 'charge now!' weep-weep-weep msg, but so often i just does that while i'm not near the phone before going full-off, which (afaik?) prevents calibration loop to run
<sicelo>
huh? what's 'charge now'?
<freemangordon>
missing, most-probably
<buZz>
there's a notification between 10% and 5% battery charge, with 'almost empty'
<buZz>
and a different one between 5 and 0%
<sicelo>
ok, i get you
<buZz>
afaik you need to hit the 5-0% one to start a calibration, while -not- having rebooted since phone knew about charge stats?
<freemangordon>
buZz: not really
<freemangordon>
unfortunately those are independent
<sicelo>
i'm not sure about that ... the script doesn't care
<buZz>
aw
<freemangordon>
also, I think it works on the ooposite
<buZz>
afaik uvos said the script no longer is functional, and calibration is now by kernel?
<freemangordon>
and then wait for "battery low at xxx" kernel message
<freemangordon>
afaik
<buZz>
and thats the design_low_voltage now?
<freemangordon>
but, because mce is too conservative, on bad battery it is really hard to hit that
<freemangordon>
no
<buZz>
ah
<freemangordon>
it is still 3.35 (or somesuch)
<buZz>
so calibration only runs between ~3.35 and 4.2?
<sicelo>
btw who shuts down the device on low battery in general? mce? maybe for d4, it should first run that calibration script ... or it does?
<freemangordon>
or 3.3, can't remember, look at driver sources, there is a explanation when 'high' low gets triggered
<freemangordon>
sicelo: mce
<freemangordon>
calibration it done by the driver
<freemangordon>
scripts just saves what has been calibrated for the next boot
<freemangordon>
IIUC
<sicelo>
the driver just counts coulombs, yes
<freemangordon>
well, not really
<freemangordon>
it comes up with 'charge_full' when calibration is done
Pali has joined #maemo-leste
<sicelo>
ok.
<Wizzup>
Pali: I will hook up serial in the next hour and try u-boot
<sicelo>
awesome :-)
<sicelo>
in the meantime, tmlind has provided some nice patches that fix the musb problem for N900.
norayr has left #maemo-leste [Error from remote client]
<buZz>
freemangordon: so, charge_full to 'low at xxx' , would that be full calibration?
<buZz>
or would it need to hit charge_full twice
norayr has joined #maemo-leste
<freemangordon>
buZz: status 'Full' and then 'low at xxx'
<buZz>
ok, so even if it poweroff after 'low at xxx' ?
<freemangordon>
yes
<Wizzup>
sicelo: great, what was the fix?
<freemangordon>
that's the theory, at least
<buZz>
nice, ok
<buZz>
i'm at full now, and will run it till shutting down , to see if i can get it back to ~1000
<buZz>
:)
<sicelo>
Wizzup: https://marc.info/?l=linux-omap&m=166876674609260&w=2 ... so it's a1a2b7125e10 that was causing my issues. anyway he has further patches to convert omap3 to work similar to omap4 regarding hwmods/ti-sysc,
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
<Pali>
Wizzup: ok, thanks!
<Wizzup>
sicelo: great
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
<uvos__>
buZz: one wrinkle about callibration on d4 is that after boot
<uvos__>
you still need to hit full OR empty even if you hit full AND before and have charge_full saved
<uvos__>
*full AND empty
<uvos__>
since the driver has no way of knowing what the coulomb counter should be at after boot
norayr has joined #maemo-leste
<uvos__>
probubly we should just improve soc estimation (ie do what android on d4 dose) and forget about callibration alltogether
<uvos__>
without usable nvram in the battery its not that viable
<buZz>
uvos__: yeah thats the wrinkle that prevents battery percentage, i guess?
<uvos__>
buZz: the battery is totaly uncallibrated untill it starts showing the percentage
<buZz>
right, not uncalibrated, but unknown
<uvos__>
its functionally uncallibrated
<buZz>
it can be calibrated -and- unknown, is what you mean
<uvos__>
the state of charge display comes from the same place
<buZz>
and only after hitting 0% or 100% will it be calibrated -and- known
<uvos__>
regardless of if charge_full exitsts or not
<uvos__>
makes no difference to the accuracy of the state of charge display
<buZz>
right, but it can become known only if calibrated before
<buZz>
-or- if doing calibration and finishing it
<uvos__>
sure
<uvos__>
btw the reason the capacity jumps around is
<uvos__>
that the empty value is taken from an irq that is suseptable to noise
<uvos__>
and load
<buZz>
sometimes i hit some mode where my d4 suddenly sees 'no battery' , i think that might have caused 1200 > 400
<uvos__>
so if the device is heavly loaded or voltage noisy
<uvos__>
it will take the battery as empty for callibration purposes
<uvos__>
way to early
<buZz>
the battery icon will go from normal green 'growing bar' on charging, to a red bar and a lot of notification sounds play very fast
<sicelo>
uh ... no battery? you're sure your contacts are fine?
<buZz>
sicelo: yeah, phone remains functional the whole time really
<uvos__>
there is no way d4 displays no battery hw wise
<buZz>
unless kernel thinks its really empty , leading to mce to powerdown
<uvos__>
oh nvm thats only true on my device
<sicelo>
oh, red bar means empty, not no battery :-)
<buZz>
right, but even with charger connected, it shouldnt be showing red + not charging
<uvos__>
on stock d4s the kernel driver checks if the thermistor is present
<Wizzup>
buZz: getting the sounds very fast sounds bad
<buZz>
hmhm, there's cpu spikes around it aswell, but not so noticeable
<buZz>
if i find some reliable way to trigger it i'll open a issue
<uvos__>
check kernel events
<uvos__>
when it happens
norayr has left #maemo-leste [Error from remote client]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #maemo-leste
ceene has quit [Remote host closed the connection]
elastic_1 has joined #maemo-leste
elastic_dog is now known as Guest8966
elastic_1 is now known as elastic_dog
sunshavi has joined #maemo-leste
norayr has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
xmn has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
norayr has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
mighty17[m] has joined #maemo-leste
alex1216 has quit [Quit: WeeChat 2.3]
norayr has left #maemo-leste [Error from remote client]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
uvos__ has quit [Ping timeout: 256 seconds]
norayr has joined #maemo-leste
pere has joined #maemo-leste
rafael2k has quit [Ping timeout: 268 seconds]
uvos__ has joined #maemo-leste
norayr has quit [Quit: Gateway shutdown]
dev has quit [Quit: Gateway shutdown]
norayr has joined #maemo-leste
Blikje has quit [Ping timeout: 256 seconds]
Blikje has joined #maemo-leste
<sicelo>
tmlind: i tried the 'Update musb to probe with ti-sysc for omap3' series, without applying 'usb: musb: omap2430: Fix probe regression for missing resources' - unfortunately musb breaks again for N900 ... missing interrupt numbers again
<sicelo>
did i jump the gun here, i.e. 'usb: musb: omap2430: Fix probe regression for missing resources' remains necessary?
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
Twig has quit [Remote host closed the connection]
<sicelo>
Wizzup: which kernel config is used when building d4/n900 kernel?
<sicelo>
i think there are missing options
dev has joined #maemo-leste
mardy has quit [Quit: WeeChat 3.5]
noidea_ has quit [Remote host closed the connection]
noidea_ has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
noidea__ has joined #maemo-leste
noidea_ has quit [Ping timeout: 260 seconds]
noidea__ has quit [Remote host closed the connection]
noidea_ has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
Twig has joined #maemo-leste
Twig has quit [Remote host closed the connection]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
uvos has joined #maemo-leste
* uvos
just bought something amusing
* uvos
(a motoactv)
<uvos>
leste target? xD
<Wizzup>
actv? is that a new thing?
<Wizzup>
ahh
<Wizzup>
nice
<norayr>
uvos, this is amazing. you can write a daemon which will forward maemo notifications to the watch via bt.
<norayr>
or u can add the support of the watch to the amazfish - it is a qt app which works with regular qt, i wanted to package it for maemo.