norayr has left #maemo-leste [Error from remote client]
uvos__ has quit [Ping timeout: 256 seconds]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
joerg has quit [Ping timeout: 256 seconds]
joerg has joined #maemo-leste
Twig has joined #maemo-leste
ceene has joined #maemo-leste
mardy has joined #maemo-leste
Twig has quit [Ping timeout: 268 seconds]
Twig has joined #maemo-leste
norayr has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
alex1216 has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
Twig has quit [Remote host closed the connection]
norayr has left #maemo-leste [Error from remote client]
mrtux has quit [Read error: Software caused connection abort]
mrtux has joined #maemo-leste
norayr has joined #maemo-leste
<sicelo>
Wizzup: looks like the dma patch is no longer enough in 6.1 :'(
<Wizzup>
sicelo: usually I had to manually call 'git revert' on the original commit
<Wizzup>
did you try doing that? you might have to manually fix some things
<Wizzup>
e right
<Wizzup>
(oops, xrandr)
tvall has quit [Quit: Bridge terminating on SIGTERM]
PureTryOut[m] has quit [Quit: Bridge terminating on SIGTERM]
BlagovestPetrov[ has quit [Quit: Bridge terminating on SIGTERM]
stintel has quit [Quit: Bridge terminating on SIGTERM]
MartijnBraam[m] has quit [Quit: Bridge terminating on SIGTERM]
mighty17[m] has quit [Quit: Bridge terminating on SIGTERM]
bumpkinbye[m] has quit [Quit: Bridge terminating on SIGTERM]
humpelstilzchen[ has quit [Quit: Bridge terminating on SIGTERM]
mogolobogo[m] has quit [Quit: Bridge terminating on SIGTERM]
MartijnBraam[m] has joined #maemo-leste
PureTryOut[m] has joined #maemo-leste
stintel has joined #maemo-leste
BlagovestPetrov[ has joined #maemo-leste
humpelstilzchen[ has joined #maemo-leste
bumpkinbye[m] has joined #maemo-leste
mighty17[m] has joined #maemo-leste
mogolobogo[m] has joined #maemo-leste
tvall has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__>
sicelo: it would be great if you could provide me with a list of patches you currently use on top of 6,1 for n900 purposes, since i dont really know what is sill required
norayr has left #maemo-leste [Error from remote client]
<Wizzup>
uvos__: imho I'd keep all patches we had unless we're certain we don't need them anymore
<uvos__>
that leads to an absolute mess
<Wizzup>
if we still have the patch, we can easily test if we need it, if we don't have the patch, we might not know which one we need, no? :p
norayr has joined #maemo-leste
Danct12 has quit [Quit: Quitting]
norayr has left #maemo-leste [Error from remote client]
Danct12 has joined #maemo-leste
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
rafael2k has joined #maemo-leste
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
rafael2k has quit [Ping timeout: 246 seconds]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
rafael2k has joined #maemo-leste
<buZz>
ahh, i reset charge_full to 1750000 and did a full discharge while gprs on, ssh open, got 1250000 as calibration now
<buZz>
having too low a charge_full leads too almost impossible to calibrate 'up' as when battery get under '10 percent' mce starts to nag and below 5% it gets reaaally annoyed
<buZz>
even if that 5% if at 3.9V , lol
<buZz>
is at*
<buZz>
(also i now default set constant_voltage to 4.max volt and input_current to 888888
<buZz>
just need some repeatable figures and tests for the battery replacement :)
norayr has joined #maemo-leste
<uvos__>
i dont see how the modem dropping away beacuse of low battery can be normal btw
<Wizzup>
agreed
<uvos__>
we shutdown earlier than android (but i have to check androids critical voltage again), and this would mean that celluar would stop working on android when the battery is low
<uvos__>
i can attest this is not the case
<uvos__>
i never had any problems using cellular on android at anny state of charge, includeing calls that lasted right up to the point where the device shut off
<Wizzup>
I think it could also be perhaps thermal reasons, I am not sure
<Wizzup>
I don't regular switch to different d4's, so I don't know how much it happens on other d4's
noidea_ has quit [Quit: Leaving]
noidea_ has joined #maemo-leste
noidea_ has quit [Client Quit]
noidea_ has joined #maemo-leste
noidea_ has quit [Client Quit]
noidea_ has joined #maemo-leste
<Wizzup>
uvos__: hm on ~3.4v on psu the system is much slower than on ~3.6v it seems
<Wizzup>
maybe 3.4 was too low, but yeah
<Wizzup>
I wonder if something reclocks without us knowing, seems unlikely
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]
asriel has joined #maemo-leste
<buZz>
maybe the modem has some lowvoltage mode that we arent enabling?
<tmlind>
the modem has it's own pmic wired to the battery directly, no idea what it's shutdown voltage might be
<uvos__>
Wizzup: you getting a cpcap irq storm?
<uvos__>
that makes it lower
<uvos__>
tmlind: the point is we shutdown at a higher voltage than android, which dosent encounter the modem not working when it thinks he battery is low
<tmlind>
uvos__: yeah.. this could be easily tested by connecting a bench power to d4 instead of a battery and lowering voltage until modem issue occurs
<uvos__>
so clearly the shutdown voltage in the modem must be below androids threshold
<uvos__>
or android must have some way to telling the modem not to shutdown
<buZz>
tmlind: maybe that pmic needs some controls?
<tmlind>
buZz: the modem uses it's own signed firmware, nothing we can do about it
<buZz>
aw right
<buZz>
beside beg to qualcomm i guess
<uvos__>
motorola
<uvos__>
who dont exist anymore anyhow
<Wizzup>
uvos__: I didn't see a lot in dmesg, so not sure
<uvos__>
Wizzup: ok
<uvos__>
maybe we should check if android dose something when battery is below 10% wrt dowclocking
<uvos__>
or if it tells the modem something via usb
<tmlind>
uvos__: well with a weak battery the modem pmic might actually know the remaining capacity better and shut down earlier?
pere has quit [Ping timeout: 268 seconds]
<Wizzup>
I think maybe sgx is clocked lower too
<Wizzup>
anyway bbiab
<uvos__>
tmlind: idk, at the very least i have never seen the modem pmic decide to shutdown before the rest of the device on android
<tmlind>
ok
<tmlind>
having the soc usb phy integrated into the modem is not a nice design solution :(
<uvos__>
this would have been extreamly obvious while i was using it as my main device for 4 or so years ;)
<tmlind>
the other option is the modem just hangs because of some reason
<uvos__>
the device behaves wierd when the battery is low on the mainline kernel in general
<uvos__>
maybe there is just some errata that motorola masked by reducing clocks while the battery is low
<uvos__>
ill check that first
<tmlind>
ok
<Wizzup>
is it possible things get re-clocked out of our control?
<uvos__>
i dont see who would be doing that
<uvos__>
we fully controll the plls in the omap4
<uvos__>
if it gets slower when the battery is low atm
<uvos__>
id lean towards irq pressure because some periferal device is misbehaveing
<uvos__>
like hickuping or somehting
<uvos__>
theres probubly a global irq counter somewhere we can look at to see if there are lots more handlers fireing?
<uvos__>
tmlind?
<Wizzup>
back in ~1 hour
<uvos__>
we def had irq pressure from the cpcap low irq before
<uvos__>
where it would start fireing lots of times per second
<uvos__>
while the battery was low
<uvos__>
but this should be fixed now
<sicelo>
uvos__: i have asked a number of times what config is used for the leste kernel ... no response from you ...
<sicelo>
i don't know what patches matter for leste and n900 because i don't really use leste with n900 much. please keep the patches and configs that were already there from spinal/Wizzup
<freemangordon>
I think I see ants more clearly when battery is low
<freemangordon>
so there must be something going on
<tmlind>
Wizzup: you can cat /proc/interrupts every 10 secs and diff to see if there's a crazy amount of some interrupts
<uvos__>
sicelo: its just omap2plus_defconfig
<tmlind>
freemangordon: pvr should not know anything about the battery voltage hopefully :)
<uvos__>
some patches in the old n900 pach collection are def obsolete
<uvos__>
they are in the mainline kernel allready
<tmlind>
uvos__: ok
<uvos__>
tmlind: i have noticed that that d4's voltage rails are noticably more noisy than xt875's
<uvos__>
maybe this is related to issues
<sicelo>
vanilla omap2plus is not best option for N900/droid4, as it includes a lot of other omap stuff that doesn't apply to any of them. in the past, there was an n900_defconfig somewhere, for example
<sicelo>
s/droid4/mapphones/
<tmlind>
uvos__: so are the ants there on xt875?
<buZz>
oh yeah, the modem is usb, can we 'unplug it' and plug back in? might just be the usb phy complaining
<buZz>
i've seen the modem going offline at >4v too
<uvos__>
sicelo: sure but those are mostly just modules and the omap2 stuff (wich we disabled via patch iirc) and extra modules we dont need (wich have minimal detriment to build for no reason) our omap2plus_defconfig isent entirely stock either, see the mameo repo and diff the file vs mainline
<uvos__>
its true that eventually we might want to have a maemo_defconfig or so
<uvos__>
tmlind: yes however i have at least not encounterd them to the same degree as on d4
<tmlind>
i believe multi_v7_defconfig does not work with kexec on d4, kernel is too big for something
<uvos__>
on d4 sometimes the statusbar is compealty hidden behind ants
<uvos__>
but that might just be because my usage hours with xt875 is lower
<tmlind>
ok
<uvos__>
tmlind: the kernel will be to big for n900 way before that happens presumably :P
<tmlind>
heh yeah
xmn has joined #maemo-leste
<buZz>
can we get rid of the 4330000 charge limit at next kernel? :) and just do 4349000 as battery states
<buZz>
such minor step, it seems :P
<uvos__>
have to check where it comes from first
<uvos__>
its possible that exatcly 4,349 is not a possible register state at all
<buZz>
i bet cpcan_charger
<buZz>
ah
<buZz>
wonder what android does :)
<uvos__>
nothing special if so
<uvos__>
the eb41 cell (not the battery case) was used on lots of moto phones from the era
<uvos__>
with different pmics
<uvos__>
the 4,349 dosent need to line up with anything in cpcap
<freemangordon>
well, without having GPU accelerated browser...
<freemangordon>
:nod:
<uvos__>
right
<uvos__>
also gtk2 is not hw accelered
<uvos__>
while androids widget set is
<uvos__>
that prob also helps android
<freemangordon>
mhm
<uvos__>
anyhow not important rn
<tmlind>
yeah
* freemangordon
is afk
rafael2k_ is now known as rafael2k
alex1216 has quit [Quit: WeeChat 2.3]
uvos__ has quit [Remote host closed the connection]
rafael2k has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
noidea_ has quit [Read error: Connection reset by peer]
rafael2k has joined #maemo-leste
Twig has joined #maemo-leste
uvos has joined #maemo-leste
noidea_ has joined #maemo-leste
uvos has quit [Remote host closed the connection]
<norayr>
i always read everything in this and some chats. and hdmi and performance issues brought me back to this thought that though we love and enjoy old retro devices (and i wish droid3 would be better supported) people cannot buy them, those aren't availble in amounts old film cameras are available.
<norayr>
so we need new devices.
<norayr>
and what we have is librem and pinephone, most supported devicen of pmos are pine64 devices.
<norayr>
i wish we had something better or could support devices that have better availability.
<norayr>
but even now if i want to buy segond d4 or if i want to regommend someone to get a d4, you cannot buy it today on ebay.