norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
uvos__ has quit [Ping timeout: 248 seconds]
uvos__ has joined #maemo-leste
Daanct12 has joined #maemo-leste
xmn has quit [Ping timeout: 268 seconds]
joerg has quit [Ping timeout: 276 seconds]
joerg has joined #maemo-leste
Twig has joined #maemo-leste
<tmlind>
uvos: not quite sure what omapdss register that was, i think i only tinkered with the sgx clock speed
<tmlind>
Wizzup: false alert on the dss blank/unblank test, it was just the ssh connection over wlan that was timing out, no reboots seen
<tmlind>
need to try that also with sgx enabled though
Daanct12 has quit [Ping timeout: 276 seconds]
uvos has joined #maemo-leste
uvos has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
panzeroceania has quit [*.net *.split]
udder has quit [*.net *.split]
jr-logbot has quit [*.net *.split]
sixwheeledbeast has quit [*.net *.split]
branon has quit [*.net *.split]
Oksanaa has quit [*.net *.split]
udder has joined #maemo-leste
branon has joined #maemo-leste
panzeroceania has joined #maemo-leste
sixwheeledbeast has joined #maemo-leste
jr-logbot has joined #maemo-leste
Oksanaa has joined #maemo-leste
pere has quit [Ping timeout: 240 seconds]
Twig has quit [Ping timeout: 252 seconds]
ceene has joined #maemo-leste
pere has joined #maemo-leste
branon has quit [Read error: Connection reset by peer]
branon has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 3.8]
akossh has joined #maemo-leste
macros_ has joined #maemo-leste
<Wizzup>
tmlind: ок
<Wizzup>
er, ok
<Wizzup>
uvos__: how do you use bt on the d4/bionic?
<Wizzup>
like, with what devices, and when do you start/stop it
<Wizzup>
I'm still baffled that you don't get these modem drops that I see shortly after using bt
rafael2k has joined #maemo-leste
norayr has joined #maemo-leste
uvos has joined #maemo-leste
xmn has joined #maemo-leste
rafael2k has quit [Ping timeout: 268 seconds]
maemish_ has joined #maemo-leste
rafael2k has joined #maemo-leste
rafael2k has quit [Remote host closed the connection]
attah has quit [Ping timeout: 265 seconds]
attah has joined #maemo-leste
ceene has quit [Ping timeout: 268 seconds]
rafael2k has joined #maemo-leste
maemish_ has quit [Quit: Connection closed for inactivity]
antranigv has joined #maemo-leste
<antranigv>
hey al
<Wizzup>
hi
<antranigv>
silly question: I have a Nokia N900, but I don't remember what I've done with it. it just booted fine, but I don't remember if I used a custom bootloader, or anything. do I need to reset it before installing Maemo Leste?
<Wizzup>
I think you need to set up u-boot on it, easier to do with fremantle
<antranigv>
Wizzup hi! long time no see :))
<Wizzup>
but the wiki has instructions on how to try it without changing anything
<antranigv>
looks like I need an SD card. time to turn the house upside down!
<antranigv>
Wizzup should I download maemo-leste-1.0-armhf-n900-20230326.img.xz ? wait, when did you reach v1.0? :D
<Wizzup>
1.0 was always in the images
<Wizzup>
that image ought to boot, yes
<antranigv>
I wonder if there's a way in shell to alias an operator
norayr has left #maemo-leste [Error from remote client]
Twig has joined #maemo-leste
rafael2k has quit [Ping timeout: 250 seconds]
pere has quit [Ping timeout: 260 seconds]
<uvos>
Wizzup: i just modprobe the module by hand
<uvos>
start the bluetooth serivce
<uvos>
and thats it
<uvos>
autoconnects with my qcII hadphones i paired using blueman-manager
<uvos>
I have never seen the modem drop away at all - ever
<uvos>
btw i know the kernel build yesterday failed
<uvos>
i tagged the wrong thing, ill fix it in a bit
pere has joined #maemo-leste
<Wizzup>
uvos: ok, I wonder if it is thermal related or something
uvos has quit [Ping timeout: 255 seconds]
uvos has joined #maemo-leste
<uvos>
Wizzup: well i did on occasion play openlara with audio going via bt
<uvos>
the device can hardly get any more loaded than that
<Wizzup>
I mean, I see it on both my d4 and bionic, so it can't be a hw defect
<Wizzup>
at least it's very unlikely
<uvos>
i gues you elliminated all other differences
<uvos>
i also have used several d4
<uvos>
never seen it
<uvos>
so no hw defect is unlikely
<Wizzup>
do you customise much beyond the normal image
<uvos>
the other differences would be: my specific bt client (ok this one is hard to repo), my sim and operator being 2g only,
<uvos>
nothing related to the modem
<uvos>
i dont use telepathy maybe it causes ofono to issues some qmi commands that the modem dosent like or something
<Wizzup>
my bionic is on 2g here usually
<Wizzup>
I also didn't have tp there per se
Danct12 has quit [Remote host closed the connection]
<uvos>
Wizzup: well my sim not even having umts entries means the modem probubly dosent even scann for umts
Danct12 has joined #maemo-leste
<Wizzup>
mhm
<Wizzup>
I think the bionic does the same unironically :P
<Wizzup>
I can't get it to go into 3g mode even though it should
<uvos>
i mean bionic may just have poor reception on your umts band
<uvos>
its not intendet to be used on these bands after all
<tmlind>
hmm getting this now on doing dist-upgrade: dpkg-divert: error: 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-droid4' clashes with 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-mapphone'
<uvos>
yeah sorry about that
<tmlind>
any idea how to fix?
<uvos>
yeah you need to undisplace that file
<tmlind>
so how does one undisplace?
<uvos>
good question i dont quite remember the command amt
<tmlind>
getting some dist-upgrade errors after changing to chimaera:
<tmlind>
E: This installation run will require temporarily removing the essential package hildon-base:armhf due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
<tmlind>
E: Reverse conflicts early remove for package 'elogind:armhf' failed
<freemangordon>
hmm, actually it is not *that* bad
<freemangordon>
tmlind: do as it says, activate the option
<tmlind>
freemangordon: ok thanks
<uvos>
freemangordon: i mean this dosent look totaly unresonable
<uvos>
a bit high in the middle
<freemangordon>
uvos: so, it is very, very bad at the linear approximation part (the straight line @ 20%)
<freemangordon>
between 20 and 10 % we shall have something else
<uvos>
i mean if you look at a typical lip dscharge curve
<uvos>
i dont think the function is totaly out of wack, i doubt you can do mucht better than 10% without mesureing the discharge curve for the battery that is installed
<uvos>
so +-5%
<freemangordon>
hmm
<freemangordon>
anyway, I think I now measure Ri with much bigger precosion
<freemangordon>
for the battery here it is Ri ~= 0.12
<freemangordon>
depends on the current ofc
<freemangordon>
but not much
<tmlind>
freemangordon: also the 1-wire chip on the battery consumes some minimal amount of power that we're not measuring in addition to the 20mohm shunt resistor
<freemangordon>
you mean a couple of mV that we don;t account for?
<tmlind>
yeah, i think it's a ds2450 on the battery, the datasheet might say how much it consumes
<freemangordon>
but, that should be part of Ri, no?
<freemangordon>
I mean - no matter how many resistors we have before the stunt, they are all part of Ri that we calculate based on the measurements
<tmlind>
i guess, the datasheet for ds2450 says 25 μW idle
<tmlind>
battery voltage is sampled before the 20mohm shunt though
<freemangordon>
umm, no
* freemangordon
checks the datasheet
<freemangordon>
oh, right
<freemangordon>
but thats ok, no?
<tmlind>
i guess just trying to list what all is outside the pmic
<tmlind>
see mc13783 8.1.1 dual path charging for the shunt, i think BATT is what the adc measures, then your 2x4 also uses BATTISNS
<freemangordon>
yes
<tmlind>
and then the ds2450 is before BATT
<freemangordon>
yes
<tmlind>
ok
<freemangordon>
but, we can account it as part of Ri
<tmlind>
ok great
<freemangordon>
because we don't really care about the internal structure of the battery
<tmlind>
ok
<uvos>
i mean if its very inductive it might throw you off
<uvos>
since you assume the battery is a first order thevenin model
<freemangordon>
I am doing lots of non-linear filtering, so spikes does not do much damage
<freemangordon>
hmm, wait
<uvos>
ok
<freemangordon>
actually it is not that bad
<freemangordon>
because 100% full for the driver is ~95 for 'us'
<freemangordon>
because driver stops charging before OCV hits 4.2V
<uvos>
ofc
<uvos>
since charge terminateion is based on current dropping below some thresh while charge voltage is 4.2
<freemangordon>
mhm
<uvos>
nessecarly this means that ocv is a bit below 4.2
<freemangordon>
right
<freemangordon>
which we account as 95%(or similar) full
<freemangordon>
so driver reports a bit highr value
<freemangordon>
*higher
<freemangordon>
ok, I'll capture a couple of discharge curves (driver vs algo) for idle, medium and full load