DPA has quit [Ping timeout: 252 seconds]
belcher_ has joined #maemo-leste
DPA has joined #maemo-leste
belcher has quit [Ping timeout: 252 seconds]
branon has joined #maemo-leste
l_bratch has quit [Ping timeout: 240 seconds]
l_bratch has joined #maemo-leste
lyubov has quit [Ping timeout: 256 seconds]
zhxt has joined #maemo-leste
lyubov has joined #maemo-leste
peterleinchen has joined #maemo-leste
peterleinchen has quit [Quit: IRC for Sailfish 1.0-alpha]
zhxt has quit [Ping timeout: 252 seconds]
xmn has quit [Ping timeout: 252 seconds]
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
linmob has quit [Ping timeout: 252 seconds]
linmob has joined #maemo-leste
zhxt has joined #maemo-leste
Pali has joined #maemo-leste
pere has joined #maemo-leste
Pali has quit [Ping timeout: 260 seconds]
doc has quit [Ping timeout: 252 seconds]
doc has joined #maemo-leste
inky has quit [Ping timeout: 252 seconds]
inky_ has quit [Ping timeout: 265 seconds]
inky_ has joined #maemo-leste
uvos has joined #maemo-leste
inky has joined #maemo-leste
Langoor has quit [Ping timeout: 250 seconds]
Langoor has joined #maemo-leste
Danct12 has joined #maemo-leste
Blikje has quit [Remote host closed the connection]
Blikje_ has joined #maemo-leste
Blikje_ is now known as Blikje
belcher_ is now known as belcher
amk has quit [Remote host closed the connection]
amk has joined #maemo-leste
amk has quit [Remote host closed the connection]
amk has joined #maemo-leste
amk has quit [Remote host closed the connection]
amk has joined #maemo-leste
amk has quit [Remote host closed the connection]
amk has joined #maemo-leste
sunshavi has quit [Ping timeout: 252 seconds]
pere has quit [Read error: Connection reset by peer]
<lel> IMbackK opened a pull request: https://github.com/maemo-leste/leste-config/pull/25 (add quirks-mapphone to mapphone mce config)
peterleinchen has joined #maemo-leste
<Wizzup> what does this do?
<uvos> do the SCRN= thing with the display state
<uvos> and kick ttyUSB3/4 to avoid the pm bug
<Wizzup> aha
<uvos> essentaly manage the mapphone modem wierdness
inky has quit [Ping timeout: 260 seconds]
inky_ has quit [Ping timeout: 252 seconds]
peterleinchen has quit [Ping timeout: 245 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
xmn has joined #maemo-leste
<Wizzup> uvos: I see you build mce for -devel
<uvos> yes
<Wizzup> for the quircks, we have other scripts in place that kick the modem, don't we?
<Wizzup> would we not need to remove those?
<uvos> no
<uvos> was never merged
<Wizzup> so just my devices have that?
<Wizzup> based on the dbus-scripts
<uvos> this was never merged
<Wizzup> hm this is for touchscreen
<Wizzup> I meant the scripts to kick the modem
<Wizzup> I thought we had those with dbus-scripts
<uvos> no its also modem
<uvos> printf 'U1234AT+SCRN=1\r' > /dev/gsmtty1
<uvos> this is what mce now dose
<uvos> regarding head /dev/ttyUSBx that was never added or proposed anywhere afaik
<Wizzup> ok
<uvos> dbus-scripts in general should be demoted to extras now btw
zhxt has quit [Ping timeout: 265 seconds]
<lel> IMbackK closed a pull request: https://github.com/maemo-leste/droid4-pm/pull/2 (Idle the ts while the display is off but the device is not locked)
xmn has quit [Ping timeout: 265 seconds]
zhxt has joined #maemo-leste
pere has joined #maemo-leste
sunshavi has joined #maemo-leste
inky has quit [Ping timeout: 252 seconds]
inky_ has quit [Ping timeout: 252 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #maemo-leste
uvos has quit [Ping timeout: 252 seconds]
_whitelogger has joined #maemo-leste
amk has quit [Ping timeout: 252 seconds]
Pali has joined #maemo-leste
<lel> MerlijnWajer renamed a repository: https://github.com/maemo-leste/libicd-tor
inky has quit [Ping timeout: 265 seconds]
<Wizzup> uvos: tmlind: might be coincidence but I was waiting for quite some time for ofono to acknowledge the data connection was activated, and when I sent myself a sms it was activated as soon as the sms was received
uvos has joined #maemo-leste
<Wizzup> uvos: I upgraded to the latest mce, overwrite the config file, and my display no longer blanks on double power key tab
<Wizzup> s/tab/tap/
<uvos> but it blanks otherwise?
<uvos> ie power menu option
<Wizzup> no
<Wizzup> I see the power menu
<uvos> ok
<Wizzup> but the display never turns off
<uvos> please stop mce via the init script
<uvos> and run "mce --verbose --verbose"
<uvos> in a sudo su - env
<uvos> with DSIPLAY set to :0
<Wizzup> did you change anything recently?
<Wizzup> I thought it was just the quircks thing
<uvos> and give me the log of the startup as well as the power button press
<uvos> nothing that should have any impact on this
<uvos> i also added a new module to eventually replace ke-recv
<uvos> but its not loaded
<Wizzup> ke-recv has a lot of scripts, but nevermind that for now
<uvos> sure
<uvos> im just goint to fix the stuff in ke-recv that dosent work (memory interface kbd slide needing gconf etc)
<uvos> by implmenting that stuff in mce
<Wizzup> ke-recv as in sd card mounting, etc
<uvos> no
<uvos> not that
<uvos> just the ke-recv deamon
<uvos> not all the other programs in the repo
<Wizzup> k
<uvos> (altho some of those need revisiting/ ellimination)
<Wizzup> ke-recv has some dbus interface that is used though, so that'll need care
<uvos> the memory interface yeah
<uvos> also usb
<uvos> sfos implmented those into mce, im just following here
<Wizzup> I will power off my droid until it can lock for now, I assume you can also test on your d4?
<uvos> it works on mine which is wierd
<uvos> anyhow let me read the log
<Wizzup> I don't see any errors there
<Wizzup> is it your maemo d4, or your mixed one :)
<uvos> mameo
<Wizzup> the only addition to 10-maemo.ini seems to be state-dbus
<uvos> mce: Failed to load module: battery-upower; skipping <- thats wierd
<Wizzup> I just accepted the package maintainer version
<uvos> (but would not cause this failure)
<uvos> ok the log dosent appear to show anything ammis
<uvos> ok the log dosent appear to show anything ammiss
<uvos> let me delete 90-user.ini and see if the default work
<Wizzup> so what I did was apt upgrade, and said 'Y' to overriding the config with the maintainer config
<Wizzup> my 99-user.ini is only lm3532 configured lights
<uvos> ok yeah there is something ammis with lock-tklock
<uvos> oh it missing
<uvos> wtf
<uvos> mce: Failed to load module: lock-tklock; skipping
<uvos> or rather it dosent link
<uvos> hmm
<uvos> we are missing a symbol: has_flicker_key
amk has joined #maemo-leste
<uvos> Wizzup: have a n900 running?
<Wizzup> not next to me, but can in a few hours
<kona> i have one
<uvos> kona: great
<kona> it's up to date according to apt update && apt upgrade
<uvos> kona: ok 1 sec
<uvos> this path dosent exist right: /sys/devices/platform/gpio-switch/kb_lock/state
<uvos> kona: please check, but it should not
<uvos> kona: gpio-switch was renamed gpio_keys in mainline afaik
<kona> ls: cannot access '/sys/devices/platform/gpio-switch/kb_lock/state': No such file or directory
<uvos> thx
<kona> user@devuan-n900:~$ find /sys -name gpio-keys
<kona> /sys/bus/platform/drivers/gpio-keys
<uvos> Wizzup: ok its fixed
<uvos> let me rebuild
<Wizzup> uvos: what was the problem?
<uvos> i removed has_flicker_key in a different module becasue it gets set based on if /sys/devices/platform/gpio-switch/kb_lock/state exists (which is only the case on the n900 vendor kernel)
<uvos> but tklock has a nasty habbit of just externing global variables from random other modules
<Wizzup> aha
<uvos> so it wouldent link
<uvos> into mce when the module loaded
<uvos> we should have some automated testing that checks if all the modules load i think
<Wizzup> is it not possible to get a link error at build time?
<uvos> no because its extern to a symbol in a different module
<uvos> and since we build the modules seperatly they dont get linked at compile time
<uvos> which asks a interesting question apearantly systemui wants to know if has_flicker_key is true (it gets this via a dbus interface)
<uvos> not sure what the flicker key is
<uvos> but we have been sending systemui false regardless of if the key is present or not
<uvos> tklock dosent seam to change its behavior at all regardless of true or false here
<uvos> (tklock in systemui that is)
<uvos> Wizzup: anyhow im building a mce version that restors the previous behavor now
<Wizzup> do you mean without linking problems?
<uvos> yeah that and allways sends false (even on n900 where that is wrong)
<uvos> ok dosent matter
<uvos> systemui-tklock dosent care about the flicker_key in the slightest
<uvos> and since the only thing lock-tklock dose with flicker_key is send it to systemui via SYSTEMUI_TKLOCK_OPEN_REQ
<uvos> its totaly vestigial
<uvos> thats half of lock-tklock in a nutshell :P
<Wizzup> upgrading now
<Wizzup> it's nice that the dsmeutil bug is fixed
<Wizzup> uvos: why does mce no longer get restarted post upgrade?
<Wizzup> that's weird
<Wizzup> (tklock works again)
<uvos> Wizzup: i just upgraded from repo
<uvos> and mce got restarted here
<uvos> you where running it in a shell as mce --verbose --verbose no?
<uvos> then ofc it wont get restarted
<uvos> since its not under conroll of openrc
<Wizzup> nah I rebooted the device
<Wizzup> I am sure it didn't restart because tklock didn't work until I restarted it via /etc/init.d/
<uvos> did apt complain about something?
<Wizzup> no
<uvos> wierd
<Wizzup> yup
joerg has quit [Read error: Connection reset by peer]
joerg has joined #maemo-leste
inky_ has quit [Ping timeout: 252 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
inky_ has quit [Read error: Connection reset by peer]
inky has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
Pali has quit [Ping timeout: 252 seconds]
xmn has joined #maemo-leste
inky has joined #maemo-leste
uvos has quit [Ping timeout: 260 seconds]
xes_ has joined #maemo-leste
xes_ has quit [Client Quit]