System_Error has quit [Remote host closed the connection]
Daanct12 has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
mkfx has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 4.4.4]
Daanct12 has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
Livio has joined #maemo-leste
_fab has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
mkfx has joined #maemo-leste
<freemangordon>
Wizzup: hmm, d4 ucm ignores initial headphones jack state, any idea?
mkfx has left #maemo-leste [Error from remote client]
<freemangordon>
also, why would we want to set volumes from UCM?
_fab has quit [Quit: _fab]
xmn has quit [Ping timeout: 260 seconds]
Twig has joined #maemo-leste
RedW has quit [Ping timeout: 244 seconds]
mkfx has joined #maemo-leste
_fab has joined #maemo-leste
RedW has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
<Wizzup>
freemangordon: to set initial volume
<Wizzup>
don't know about hp jack state
arno11 has joined #maemo-leste
<arno11>
freemangordon: by initial jack state, you mean no headphone detected if already plugged on boot or when you switch profile, right ?
_fab has quit [Quit: _fab]
akossh has joined #maemo-leste
_fab has joined #maemo-leste
pere has quit [Ping timeout: 272 seconds]
arno11 has left #maemo-leste [#maemo-leste]
_fab has quit [Quit: _fab]
mkfx has joined #maemo-leste
hm has joined #maemo-leste
System_Error has joined #maemo-leste
Anasko has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
mkfx has left #maemo-leste [#maemo-leste]
<freemangordon>
arno11: I implemented proper jack state detection (even on boot), amixer -c 0 contents reports proper state
<freemangordon>
however, sound is not redirected to HP
<freemangordon>
Wizzup: setting initisl volume shall not be doen on profile switch
<freemangordon>
*done
<freemangordon>
but only on boot
System_Error has quit [Remote host closed the connection]
Twig has quit [Ping timeout: 265 seconds]
System_Error has joined #maemo-leste
<Wizzup>
sure
Twig has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
freemangordon: ah ok
<arno11>
weird @sound not redirected
<arno11>
maybe 'Headset Left/Right Playback Route' is still 'off' because of no jackcontrol event, no ?
<arno11>
maybe it should be removed from SectionVerb
<arno11>
(or worth a try to set it to HiFi in SectioVerb to see if sound is back after boot)
xmn has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
Daanct12 has quit [Quit: WeeChat 4.4.4]
akossh has quit [Ping timeout: 265 seconds]
pere has joined #maemo-leste
<freemangordon>
arno11: there is no jackcontrol event because HP are plugged *before* PA is started
<freemangordon>
if I plug them after PA is running, it works fine
akossh has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
freemangordon: yup that's why i asked for SectionVerb in HiFi profile: with no jackcontrol event, Headset Playback Route is probably still 'off'
<freemangordon>
well, I am not sure what you're talking about :)
<freemangordon>
SectionDevice."Headphones" {
<freemangordon>
...
<freemangordon>
JackControl "Headphones Jack"
<arno11>
i mean, even if headsets are detected by amixer, ucm2 keeps probably what has been set in SectionVerb in HiFi profile
<freemangordon>
but why does it work after I re-plug?
<arno11>
because a jackcontrol event happens
<freemangordon>
hmm, everything is set to "off" in section verv
<freemangordon>
SectionVerb
<freemangordon>
also, this is not exactly about boot, but that PA seems to ignore initial state
<arno11>
yes i think that's the problem (everithing off)
<freemangordon>
ok, but why Speaker is on then?
<arno11>
because that's the default state depending of priorities
<arno11>
let me check ucm
<freemangordon>
arno11: yes, please do
<freemangordon>
as I think it is just a bug that noone checks the initial jack state
<freemangordon>
or, shall we check that state manually in UCM?
<arno11>
indeed speaker is highest prio so speakers are 'on' and
<arno11>
yes you should try to manually set headset PR stuff to HiFi in SectionVerb
<arno11>
and reboot to see if sound is back if headsets are well recognised on boot
<sicelo>
arno11: someday the N900 ucm needs to be cleaned up and upstreamed too
* sicelo
assigns arno11 :p
<arno11>
sicelo: yes it needs to be cleaned...a lot
<arno11>
same for d4 btw
<freemangordon>
arno11: you don;t get it
<freemangordon>
this is d4 BTW :)
<freemangordon>
so, regardless of boot state, imagine:
<arno11>
yes i know for d4
<freemangordon>
1. PA is running and you plug HP
<freemangordon>
-> sound is switched to HP
<arno11>
yes makes sense
<freemangordon>
2. you restart PA (with HP still plugged in)
<freemangordon>
->sound stays on Speakers until you re-plug HP
<freemangordon>
this is wrong behaviour IMO
<freemangordon>
so, the issue is not only on boot
<arno11>
yes and that's just because of jackcontrol imo
<freemangordon>
and that's the part of your statement I cannot parse :D
<arno11>
and so yes i understand correctly
<freemangordon>
what is 'because of jackcontrol'?
<freemangordon>
isn't it supposed to switch based on state? or, because there is no event, initial state is ignored?
<sicelo>
i think he means ... when PA starts, it reevaluates the ucm rules, sets Speaker, then starts waiting for events
<freemangordon>
which is another way of saying "initial conditions are ignored", no?
<sicelo>
yes, only sawyour last messagesafter already hitting enter
<arno11>
iirc, with no jackcontrol, no change, excepting if you switch profile
<arno11>
back to default, depending of priorities which is tricky
<sicelo>
but arno11, i agree with fmg that this kind of behavior is wrong. either we're missing something, or it's a bug
<arno11>
ofc that s wrong
<arno11>
that s just the current behaviour
<arno11>
i reported it months ago (only on irc, not in bugtracker, my bad)
<arno11>
and yes initial conditions are totally ignored