<sicelo>
does the mce battery full thing work on droid 4 or something else?
<sicelo>
oh btw droid 4 always shows green ...
<sicelo>
i guess mce already does something like turn led green if charger online && capacity > 96% ?
<sicelo>
Wizzup: 9a36f9f25c9440e412b672c mce - i would say those need to be blacklisted at kernel level. i was going to say remove from config but i guess kernel blacklist will be easier
xmn has quit [Ping timeout: 276 seconds]
Twig has joined #maemo-leste
maemish_ has quit [Quit: Connection closed for inactivity]
antranigv_ is now known as antranigv
antranigv is now known as antranigv_
antranigv_ is now known as antranigv
antranigv is now known as antranigv_
elastic_dog has quit [Quit: elastic_dog]
elastic_dog has joined #maemo-leste
brabo has quit [Ping timeout: 246 seconds]
akossh has joined #maemo-leste
antranigv_ is now known as antranigv
antranigv is now known as antranigv_
antranigv_ is now known as antranigv
antranigv is now known as antranigv_
user_____ has joined #maemo-leste
user_____ has left #maemo-leste [#maemo-leste]
nela3 has joined #maemo-leste
nela has quit [Ping timeout: 248 seconds]
nela3 is now known as nela
Twig has quit [Ping timeout: 276 seconds]
arno11 has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
07:16 < sicelo> does the mce battery full thing work on droid 4 or something else?
<Wizzup>
no, but it used to work on the n900 when spinal was working on it
<Wizzup>
maybe it's a kernel thing, or upower thing
<Wizzup>
sicelo: I disagree, we already had a blacklist in place, so having it in mce for now makes sense to me, but yeah, fine to do in the kernel too, but I don't have the time and skill to do it
<sicelo>
ok
<sicelo>
i meant blacklist the module from loading, but yeah, anything that works is fine
<Wizzup>
hmmm
<Wizzup>
well, we can do in parallel
<Wizzup>
do you think this will not interfere with the functioning of the rest?
<Wizzup>
because I think some of these we need, but we just don't want upower to use them
<Wizzup>
I mean sure there's this one useless rx51 battery, but the rest, I think we need
<sicelo>
we don't need these drivers on n900
<Wizzup>
ok, then let's work on a blacklist for these as well
<Wizzup>
so I checked and maemo-system-services is at the new/fixed version
<Wizzup>
and the input dev getting disabled seems to suggest mce does its thing
<Wizzup>
but why does X keep it open now
arno11 has joined #maemo-leste
<Wizzup>
freemangordon: so I see DisableDevice get called in X
<Wizzup>
but elogind and X do not free it
<arno11>
Wizzup:i can confirm as well elogin/xorg ts issue on n900 but by chance I have still an old img
<arno11>
from march 13
<arno11>
last dist-upgrade march 15
<arno11>
and issue already there
<arno11>
kernel 6.0 bla bla rc
<arno11>
otherwise no inpact on power consumption
<Wizzup>
I'm pretty sure the problem is with elogind and X running in user mode
<Wizzup>
I'm retracing our steps
<arno11>
on my old img x and elogin run as root
<Wizzup>
yes, I think this is it
<arno11>
but the issue is already there
<Wizzup>
this is with old maemo system services
<Wizzup>
if you upgrade just that it should be fixed
<Wizzup>
I think what happened is that we figured out half of the problem: mce wasn't able to disable the devices when X ran as root
<Wizzup>
but the other half: X and elogind not actually releasing the fd when X runs as user, was not solved
<arno11>
so 2 different issues ?
<Wizzup>
21:45 < freemangordon> but, maybe we shall drop logind session (and run Xorg as root) until done
<Wizzup>
let me try something
<Wizzup>
lol, another loop-break apt upgrade
<Wizzup>
hm, even with the xorg legacy pkg installed this still happens
<Wizzup>
:(
<Wizzup>
I am out of options right now
<arno11>
I've just upgraded maemo system services on old img to check difference
<arno11>
no change
<arno11>
still root and ts issue
<Wizzup>
phone call, brb
<arno11>
Wizzup:ttyl have to go too
arno11 has left #maemo-leste [#maemo-leste]
Twig has joined #maemo-leste
<Wizzup>
so I think the short term solution is to just not build X with logind support
<Wizzup>
we will still get the sessions any everything
<Wizzup>
it'll just run as root
brabo has joined #maemo-leste
Twig has quit [Ping timeout: 248 seconds]
<Wizzup>
yeah, with xorg-server built without logind everything is fine pm-wise
<Wizzup>
so there is really some unique breakage there in the logind code
<Wizzup>
I think this is probably what we want to do
<Wizzup>
brb\
DPA- has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
DPA has joined #maemo-leste
Twig has joined #maemo-leste
Twig has quit [Max SendQ exceeded]
Twig has joined #maemo-leste
<Wizzup>
so I think what happened is that I promoted the -devel xorg-server a while back when talking with fmg even thoguh we should not have since it has this bug
<Wizzup>
wait.... `user` is not in the `input` group
<Wizzup>
I think that can be a problem too, but I am not sure if that's why we have this problem
<Wizzup>
freemangordon: ^^
<freemangordon>
what is the isuue?
<freemangordon>
*issue
<Wizzup>
freemangordon: hi!
<Wizzup>
freemangordon: on chimaera now, ts is again now released by xorg and elogind
<Wizzup>
and it's unrelated to the problem we saw before with mce not disabling it
<Wizzup>
mce disables it, but X still does not release
<Wizzup>
I went down our previous steps trying to figure out what is up
<freemangordon>
on which device?
<Wizzup>
all
<freemangordon>
on d4?
<Wizzup>
d4, n900, etc
<Wizzup>
and I think the problem is that I moved xorg with elogind support to chimaera
<freemangordon>
not possible, I have more than 24 hours idle, but still lemme check the current
<Wizzup>
ok, well, lsof shows it
<Wizzup>
and power usage shows it
<Wizzup>
we all have the problem
<Wizzup>
I've fixed it in -devel for now by downgrading to xorg without elogind (everything else still works)
<freemangordon>
ok
<freemangordon>
sorry, just came home, will need some time to catch up
<Wizzup>
I think the above is the whole summary really
<Wizzup>
unless you're sure you had it working before with xorg with elogind support enabled
<freemangordon>
well, I was seeing the smae average current
<freemangordon>
*same
<freemangordon>
lets have my d4 battery charged, will check what's going on
<Wizzup>
arno11: if you dist-upgrade on -devel the pm issue should be gone
antranigv_ is now known as antranigv
<tmlind>
Wizzup: yup that looks better for power consumption
<Wizzup>
tmlind: right, so with this I can look again at the neigh probe stuff
whatsupboy has quit [Ping timeout: 265 seconds]
<tmlind>
Wizzup: ok, that's still about 20mW higher compared to what i'm seeing on alpine with wlan off 3g voice and data online
<tmlind>
and i think we still have some mystery 5 - 7mW of idle saving lurking around in some d4 device
<tmlind>
just a gut feeling though
<arno11>
Wizzup: ok i'll try in a bit but i never had pm issue
<Wizzup>
tmlind: it could perhaps also be my device, I've had one or two droids that just used more power, even when turned off i saw them use power on lab psu
<Wizzup>
might not be this one
<tmlind>
ok
<Wizzup>
I might be worth at some point to upgrade to -devel on yours and check (the ts not being closed bug is worked around there)
<arno11>
Wizzup:there is no inpact on n900 pm and it's logical
<Wizzup>
arno11: well it will be a pm issue I think, on n900 there used to be a kernel hack to force suspend the ts, but I think that is gone
<Wizzup>
arno11: how is that logical?
<arno11>
because touch screen is never really off
<Wizzup>
arno11: what do you mean?
<Wizzup>
it should be
<arno11>
remember pm stuff with n900, we can't hit ret or off mode because of screen
<Wizzup>
so what I know is that with ff62b5a2d7c4794659b626469b30d4fce43fdcbf and 34df5ff446f3b03f2dc4f1049fa57db544cd7b66 the screen idles ok with fd closed
<arno11>
elogin and x issue or not, idle is still the same
<Wizzup>
that is
<Wizzup>
wip: Input: tsc200x-core: use runtime PM instead of custom functions
<Wizzup>
and
<Wizzup>
wip: Input: tsc2005: disable irqs on suspend
<Wizzup>
and we ship this
<Wizzup>
however, note that the ts is only released when the device is locked
<Wizzup>
that is not the same as 'screen off'
<Wizzup>
so you need to use double power button press or lock screen slider
<Wizzup>
let me check this on my n900
<arno11>
ok
<arno11>
weird
<Wizzup>
btw latest kernel also has the pm debugging sysfs file
<Wizzup>
well I guess this depend on the setting that auto locks the screen or not
xmn has joined #maemo-leste
<Wizzup>
arno11: how many mW did you normally see?
<arno11>
I've just triplecheck and everything is fine as always
<Wizzup>
do you mean that X does not hold the touchscreen open?
<arno11>
50mW /185mW as usual
<Wizzup>
arno11: sorry, this is screen off / on?
<arno11>
i'm just saying that elogin issue or not, i have the same idle
<arno11>
off
<arno11>
sorry 50mA/185mW
<Wizzup>
I see two values
<Wizzup>
ok
<arno11>
giving more than 24 hours
<Wizzup>
I am seeing p=230mW right now, with wifi off
<Wizzup>
in any case, if you want I can try to see what happens if I keep the ts actually enabled, but I'm sure it will use a lot more power
<Wizzup>
unless the kernel misbehaves, which is possible, since it's my patch
<arno11>
yes could be interesting
<Wizzup>
like: userspace should never keep ts open, ever, if it doesn't need it
<Wizzup>
since that means the ts will be powered
<Wizzup>
btw it looks like the check bl-5j's I bought are really poor, like less than 400mAh :D
<Wizzup>
(they were not polarcell)
<Wizzup>
s/check/ceap/
<Wizzup>
cheap* even
<arno11>
ah could explain that
<Wizzup>
arno11: but, you see lsof keeping ts open now, or not?
<Wizzup>
just to see where you're at atm
<arno11>
yes ts open in lsof
<Wizzup>
also, if you download the n900 pm script and don't start it, just run status, we can compare blockers and such (even with off/ret not enabled)
<Wizzup>
ok, well, I think if you upgrade to -devel and reboot, you will see it probably use less power
<arno11>
ok but there is a bias i forgot
<arno11>
i'm a bit undervolted
<arno11>
with custom uImage
<bencoh>
undervolted?
<arno11>
yes
<arno11>
opp table modified
<bencoh>
oh
<arno11>
and overclocked to 850
<bencoh>
hmm, is it still stable?
<arno11>
very stable
<arno11>
and much more smooth
<Wizzup>
hard to compare then yeah :D
<arno11>
yes indeed
<Wizzup>
in any case I will modify leste-config to add swap on emmc by default to fstab, but not only once and not if there is some other entry
<arno11>
ok cool
<Wizzup>
then I guess we need.. phone audio, some ofono fixes eventually, and better pm
<Wizzup>
(for n900)
<arno11>
yes we are not so far
<Wizzup>
230mW seems like my regular idle mW btw
<arno11>
ok so arround 60mA
<bencoh>
I think fmg has had his main n900 overclocked for years, but I don't think he undervolted it ...
<Wizzup>
bencoh: there's no need with ret/off working
<bencoh>
true
<bencoh>
idle power on fremantle is quite low as it is
<arno11>
bencoh: every known overclocked profiles from fremantle are undervolted
<Wizzup>
very low :)
<Wizzup>
arno11: well if you can confirm that latest devel with the ts closed idles even better, I'd like to know
<Wizzup>
also, lmk what you did on phone audio so we can get back to pavel
<arno11>
ok but i need time because to compare with my previous idle, i need to create a new uImage with same parameters
<Wizzup>
oh, right
<Wizzup>
well, conceptually it should really help :P
<arno11>
so let's go
<arno11>
back in 20-30min with results
<Wizzup>
but also conceptually you should have seen this before any of our elogind work
<Wizzup>
(this = the idle saving)
<Wizzup>
s/idle/power/
<arno11>
never seen any difference
<arno11>
(dist-upgrading...)
<arno11>
Wizzup:"lmk what you did on phone audio so we can get back to pavel" ok
dsc_ has quit [Quit: leaving]
whatsupboy has joined #maemo-leste
dsc_ has joined #maemo-leste
<arno11>
(arghhh force loopbreak option i don't like that lol)
<arno11>
anyway seems to work
<arno11>
rebooting and then creating new uImage
<Wizzup>
cool
<buZz>
hmmm weird, my d4 lost(?) its calibration while being on charge overnight
<buZz>
seemingly didnt reboot
<buZz>
guess i'll just discharge to 'omg charge now' and charge it all the way up
<arno11>
ok uImage created...rebooting
<arno11>
uImage seems fine. loading
<arno11>
Wizzup: ok let's testing and compare
<arno11>
no difference 46mA
<arno11>
as usual
<Wizzup>
and if you run cat /dev/input/eventX >/dev/null where X is the ts?
<Wizzup>
(and then measure)
<arno11>
ok let's go
<arno11>
no difference same result
<arno11>
let's try again to be sure
<arno11>
still 47mA
<Wizzup>
ok
<Wizzup>
sounds like my kernel patches for pm are not enough then
<Wizzup>
thanks for verifying
<Wizzup>
seems like we can get lower pm then still even without ret
<arno11>
yes totally agree!
<buZz>
47mA is already amazing to me :D
<arno11>
it's really great arround 27 hours idle ;)
<arno11>
modem on 52mA
pere has quit [Ping timeout: 255 seconds]
<arno11>
btw user experience should be really different using custom overclock kernel. i didn't talk to much about that but the n900 is so much responsive...comparable to overclock fremantle
<arno11>
even better playing videos
<buZz>
:) cool
<buZz>
even youtube?
<arno11>
yes using yt-dlp
<arno11>
and 360p
<buZz>
nice nice
<arno11>
even kodi is working
<arno11>
17.6
<arno11>
and for me the most impressive stuff is retroarch
<arno11>
impossible to run on fremantle afaik
<buZz>
why not the actual emulators?
<arno11>
not really working on n900
<arno11>
i mean snes, nes, megadrive
<arno11>
scummvm runs fine
Twig has quit [Remote host closed the connection]
<buZz>
arno11: gee, not even picodrive?
<arno11>
picodrive doesn't work (even the retroarch module)
Twig has joined #maemo-leste
<arno11>
but through retroarch, genesis gx works well
<buZz>
gee
<Wizzup>
documenting all of this would be real cool btw
<Wizzup>
we have people who do fun stuff with leste but then others have to jump through the same hoops
<Wizzup>
but I know, E_TIME :D
<arno11>
:)
<Wizzup>
I have my macro lens set up now to make some photos of the batteries
<arno11>
oops i've to go. i will try to find time to document fun stuff.