<uvos__>
btw the known issue with the cpcap detection code
<uvos__>
is that the device name of the chip changes (baste on what exact supplier motorola used for the eeprom i presume?), and i have no way of knowing what device on the bus is the right one
<uvos__>
so it uses only the chip i hapen to have on my devce
<freemangordon>
hehe :)
<freemangordon>
ok, will see what we can do
alex1216 has quit [Ping timeout: 252 seconds]
<freemangordon>
uvos__: I see no polling there
<freemangordon>
why do you think it polls?
<uvos__>
reading the protocoll spec
alex1216 has joined #maemo-leste
<freemangordon>
HW does polling?
<uvos__>
it also uses a lot of power
<uvos__>
its possible that hw dose poling, main symptom here is it draws a lot of power to have it on
<freemangordon>
ok, will see what happens, reading TRM atm
<uvos__>
also theres a commen in android kernel somehwere
<uvos__>
about avoiding the bus polling
<uvos__>
*comment
<freemangordon>
uvos__: I think cpcap shall allow userspace to write the id of the battery
<uvos__>
freemangordon: feals ugly, but maybe its the only option
Daanct12 has quit [Remote host closed the connection]
<freemangordon>
unless we know how ids are coded
<freemangordon>
like - if it starts with 89, then it is the battery
<uvos__>
right , but i dont, i wanted to figure out whre it comes from
<uvos__>
but wasent a priority ofc with the code being dead due to the blacklist and all
<freemangordon>
it is programmed during manufacture afaik
<uvos__>
ok
<freemangordon>
I don;t see it in nvram
<uvos__>
well it might also help if everyone could post the ids they have
<freemangordon>
right
<uvos__>
you have mine in the code
<freemangordon>
was about to ask you what is your id :)
<freemangordon>
ah, right
<uvos__>
well mine is none now
<uvos__>
since i dont use a battery with a chip :)
<uvos__>
as for identifieng idk if opening random devices to look for MOTOROLA is really acepptable
<uvos__>
to the mainline folks
<freemangordon>
why random? it is nvmem
<uvos__>
freemangordon: thanks
<uvos__>
well random nvmem devices
<freemangordon>
ok, lets gather some IDs, will decide what to do
<freemangordon>
uvos__: 'your' idle is not as 'my' idle, I have ssh connections active
<freemangordon>
this is with 2 sessions, lemme check with 1 only
<freemangordon>
same
<norayr>
i think maaajordomo was a software to setup a mailing list. it was written in perl and had a web frontend.
<norayr>
majordomo
<norayr>
you also supposed to create a mail account for it so that it will be possible to subscribe or unsubscribe by sending an email.
<norayr>
uvos__
<uvos__>
norayr: yeah i know about that one
<uvos__>
i was hoping for something simpler
<norayr>
it is sad that droid4 is not available on market (read ebay) any more for pretty long time already. i k last time i saw about a month ago the one which was in state 'read' and it had some problem.
<norayr>
uvos__ i think 20 years ago when i was searching for something that was the simplest.
<uvos__>
norayr: ok yeah i might have to use it, i was thinking there would be some 300 line c program that just mails whatever it recives on pop3 to a static list.
mardy has quit [Ping timeout: 252 seconds]
mardy has joined #maemo-leste
<norayr>
yes it would be good to have such a thing. maybe that's a good idea to write something like that. i wish i had a bit of time, that's something that inspires me for work.
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
akossh has joined #maemo-leste
<freemangordon>
uvos__: do you know which blob reads nvmem on android? I may try to RE the structure
<uvos__>
freemangordon: i dont quite remember, but it had an obvious name batd or something like that
<freemangordon>
ok
Daanct12 has quit [Remote host closed the connection]
uvos__ has quit [Quit: Konversation terminated!]
uvos has joined #maemo-leste
uvos is now known as uvos_
uvos__ has joined #maemo-leste
uvos_ has quit [Ping timeout: 272 seconds]
<freemangordon>
uvos__: nvram contents on 2 devices here is exactly the same
<uvos__>
freemangordon: that is correct
<uvos__>
its allways the same for eatch battery of one type
<freemangordon>
that's good
<freemangordon>
I guess
<uvos__>
it dose _not_ contain any information on battery health or anything like that
<freemangordon>
right
<uvos__>
or even a serial
<freemangordon>
this is just device id
<freemangordon>
so we can use to match
<uvos__>
its lots of data for a device id
<uvos__>
presumably its a voltage/current->state of charge table
<freemangordon>
maybe some cherging parameters
<uvos__>
as this is how the batttery display works on android
<freemangordon>
could be
<freemangordon>
lemme feed IDA with batd
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
<freemangordon>
uvos__: so, blob checks for "CORP", "MOTOROLA E.P CHARGE ONLY", uid starting with 0x89 and last 2 bytes being 0x0050
<freemangordon>
it also calculates 2 checksums, but I don;t think we shal care
<uvos__>
that all?
<uvos__>
what about all the other data
<freemangordon>
it is used co calculate "SBCM CORE convert_rom_data: bcap= %d, raw= 0x%x"
<freemangordon>
so most-probably you are right and this is voltage->% table
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
<freemangordon>
also it seems the capacity is there
<freemangordon>
uvos__: capacity = mul * batt_data.nvram.data[34];
<freemangordon>
where mul is calculated based on some other data
<freemangordon>
I will provide the formula later on
<uvos__>
something also has to tell the android what to charge too
<freemangordon>
what do you mean?
<freemangordon>
what is the type?
<uvos__>
if you plug in a bw8x to bionic it suddenly knows to only charge to 4,2v
<uvos__>
just click through the depends and download them all
<uvos__>
Guest224: another alternative is a usb-otg cable and a usb ethernet adapter
<Guest224>
thanks
<uvos__>
youll have to setup the network by hand in comandline
<uvos__>
but then it should work fine
<uvos__>
assuming d4/bionic/pp here
<uvos__>
n900 cant do otg
<Guest224>
Is pp with dockin-bar ethernet supported yet?
<uvos__>
no idea
xmn has quit [Ping timeout: 252 seconds]
xmn has joined #maemo-leste
alex1216 has quit [Quit: WeeChat 2.3]
<Wizzup>
uvos__: I think so @ buying ones that got removed, kinda lame ;)
<Wizzup>
freemangordon: I can send it, how do I read it?
<Wizzup>
(just woke up, brb)
<uvos__>
Wizzup: i can live with just one btw
<uvos__>
if you are short
<uvos__>
since i have just one d4 now anyhow
<Wizzup>
just short on time atm, not short on devices
<uvos__>
(i want one to modify)
<uvos__>
i mean doors
<Wizzup>
ah
<Wizzup>
right
<Wizzup>
I need coffee :p
<uvos__>
what time zone are you in, Pacific?
<freemangordon>
Wizzup: umm, send what?
pere has joined #maemo-leste
Guest224 has quit [Ping timeout: 244 seconds]
<Wizzup>
freemangordon: you wanted me to share some battery data
<freemangordon>
ah, no
<freemangordon>
we already figured it out
<Wizzup>
ok
<freemangordon>
like, I am writing patches to cpcap-battery to process eeprom data
<Wizzup>
I have a lot of d4's that I am bringing back
<Wizzup>
like, it has to be ~40
<freemangordon>
:)
<Wizzup>
freemangordon: ok, cool
<Wizzup>
freemangordon: I wonder if we also ought to have a patch to charge the battery a bit more than 4.2 for folks who want it
<freemangordon>
I think we shall increase that
<freemangordon>
like, if battery is for 4.35, so be it
<Wizzup>
right, but we thought it maybe caused them to balloon quickly
<Wizzup>
this happened two at least two android phones I had that I kept on charger at all times
<freemangordon>
d4 phones?
<Wizzup>
yes
<freemangordon>
why keep them on charger though?
<freemangordon>
also, charger driver shall be smart enough and have some hysteresis, like, it should not restart charging before the voltage has dropped by lets say 2 or 3 percent
<freemangordon>
but in general, I would trust what manufacturers say
<freemangordon>
so, if they say 4.35, then...
<freemangordon>
Wizzup: also, were those batteries new?
<freemangordon>
I guess no
Daaanct12 has joined #maemo-leste
<freemangordon>
uvos__: did you check idle power usage with hdq enabled?
Daanct12 has quit [Ping timeout: 252 seconds]
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 246 seconds]
<Wizzup>
freemangordon: no, probably not new
freemangordon has quit [Quit: Leaving.]
freemangordon has joined #maemo-leste
<tmlind>
freemangordon: yeah d4 batteries kept on charger at higher than 4.2v will ballon after some weeks or months, no issues at 4.2v afaik
<tmlind>
you can already tweak the charge voltage via sysfs if you really want, i would not recommend it
<freemangordon>
I don't see a reason why anyone would want to keep the device on charger
<freemangordon>
but ok
<freemangordon>
though, I think default should be what battery is made for
uvos__ has joined #maemo-leste
uvos has joined #maemo-leste
<tmlind>
the battery was not made to last it seems
<freemangordon>
hmm
<freemangordon>
well, I guess we can at least increase a bit, like to 4.25, no?
<uvos>
im terribly convinced that there is anything wrong per say with charging eb41 to 4.35V
<uvos>
but hvlipos have lower cycle lifetime
<uvos>
which is why they are all very degraded by now
<uvos>
only charging them to 4.2v helps emensely
<freemangordon>
afaik even 'new' are degrated
<uvos>
sure yes
<uvos>
10 years is old even for purley calendary ageing
<ashley>
ballooning batteries are such "fun"...I just had to throw out a brand new, unused Nokia XL battery a few weeks ago because of how swollen it had gotten, all on its own :-/
<uvos>
shelf life of lipos is about 5 years so yes
<freemangordon>
so, I am not convinced reducing the charge voltage help much, but ok :)
<uvos>
all d4 batteries are degraded
<uvos>
degraded batteries tend to be most unsafe at full charge
<uvos>
it makes some sense to reduce the voltage
<uvos>
not that i agree we should
<freemangordon>
btw, why do we report li-ion and not li-po for genuine batteries?
<tmlind>
freemangordon: looks good to me, please check the default charge current stays the same to be sure..
<freemangordon>
how?
<freemangordon>
tmlind: ^^^
Daanct12 has joined #maemo-leste
Daaanct12 has quit [Ping timeout: 252 seconds]
* buZz
excited to try this new cpcap :)
freemangordon has quit [Ping timeout: 252 seconds]
freemangordon has joined #maemo-leste
norayr has joined #maemo-leste
uvos has quit [Ping timeout: 252 seconds]
<tmlind>
freemangordon: hmm i guess that patch does not affect the default charge voltag
<freemangordon>
no
<freemangordon>
just design voltage
<freemangordon>
tmlind: please, what is the proper git command to send series? "git send-email -3 --subject="[PATCH 0/3] power: supply: cpcap-battery improvements" --compose"?
uvos has joined #maemo-leste
<tmlind>
freemangordon: i first use git format patch to /tmp/outgoing, then to send git send-email --confirm=always --suppress-cc=self --cc-cmd=~/bin/my-git-get-cover-cc --to "..." --cc "..."
<tmlind>
that git-get-cover-cc is some script that adds folks to cc
<tmlind>
not sure if that's even needed any longer to add folks to cc
<freemangordon>
ok, thanks
<tmlind>
the get cover i have is from some mailing list thread i can't find and contains: