**** BEGIN LOGGING AT Sat Aug 29 02:59:59 2015
Aug 29 03:53:56 <mtnman> hello all maemoans
Aug 29 03:54:04 <mtnman> or is it maemoers?
Aug 29 03:54:13 <mtnman> maemoites?
Aug 29 03:54:35 <mtnman> is there anybody out there?
Aug 29 03:54:56 <mtnman> just not if you can hear me...
Aug 29 03:54:59 <mtnman> nod even
Aug 29 03:58:36 <jon_y> maemo's DEAD!
Aug 29 03:58:41 <jon_y> DEAAAAAAAAD!
Aug 29 03:58:43 <jon_y> :)
Aug 29 03:59:56 <mtnman> what?
Aug 29 04:57:56 <KotCzarny> oksanaa: yes, it works
Aug 29 04:58:14 <KotCzarny> most likely diablo's elinks isnt compiled with ssl
Aug 29 05:02:49 <KotCzarny> oksana: if you want i can try compiling it for diablo too and see 
Aug 29 07:15:26 <Vajb> nwolf900: do you have cssu-features installed? Also check from "clockmenu or powerkeymeny" that you dont have orientation lock ticked.
Aug 29 07:23:29 <Vajb> question about qml-browser. Is there a way to make it zoom in if click of a link wasn't precice enough? That's how opera behaves and i got used to feature.
Aug 29 08:30:13 <Vajb> nvm. I think it's no longer needed. I installed new screen protector and can safely say that I should have done it few months ago.
Aug 29 08:33:40 <KotCzarny> vajb, i havent used qml-browser, but did you try two finger zoom or volume key?
Aug 29 08:37:43 <Vajb> it zooms via volume keys, but that's not what i needed
Aug 29 08:38:37 <Vajb> i wanted something like from 100% to 200% with one tap
Aug 29 08:38:41 <KotCzarny> so you mean some automatic misclick detection?
Aug 29 08:38:57 <KotCzarny> or just zoom-on-tap in the non-link place?
Aug 29 08:39:15 <Vajb> i guess volume key does 10% at a time
Aug 29 08:40:19 <Vajb> if there is two links close to each other and screen can't tell which i tap it could zoom in to make them bigger and easier to tap.
Aug 29 08:41:13 <Vajb> and this is the place where someone tells me to use "pen" :)
Aug 29 08:41:30 <KotCzarny> of nail
Aug 29 08:41:31 <KotCzarny> :)
Aug 29 08:48:36 <Vajb> :p
Aug 29 09:29:56 <Wizzup> hmm...
Aug 29 09:30:19 <Wizzup> wanting to dual boot and I get this error when trying to install "U-Boot with kernel 2.6.28-omap1": "!!!U-Boot with kernel 2.6.28-omap1 breaks the 3rd party package policy" 
Aug 29 09:30:30 <Wizzup> (I want to dual boot so I can try the mainline kernel.)
Aug 29 09:32:13 <Wizzup> trying it using apt-get now
Aug 29 09:32:26 <Sicelo> conflits with PK?
Aug 29 09:32:44 <Wizzup> That seems to work
Aug 29 09:32:49 <Wizzup> I don't think I have PK installed on this one
Aug 29 09:32:55 <Wizzup> This is pretty much plain flash + cssu update
Aug 29 09:47:41 <kerio> Wizzup: honestly, for stuff like that you probably want to use apt-get, to keep as much control over what's happening as possible
Aug 29 09:48:23 <Wizzup> I did
Aug 29 09:48:25 <Wizzup> :)
Aug 29 09:53:16 <Vajb> any advice how to turn off that blue led caused by usbhostmode? Without reboot.
Aug 29 09:54:11 <Vajb> stop-start mce turns it off temporarily, but it's lit immediately after mce restarts
Aug 29 09:55:18 <kerio> i get all sorts of leds stuck every once in a while
Aug 29 09:57:12 <Sicelo> Vajb: reboot only :) 
Aug 29 09:57:21 <Sicelo> email Pali .. he wanted to fix it
Aug 29 09:57:36 <Vajb> meh
Aug 29 09:58:04 <Sicelo> btw, it only happens on one of my N900. the other is perfectly fine. i wish i knew why the difference
Aug 29 09:58:54 <Wizzup> Vajb: I just switch the n900 to non hostmode and it turns off
Aug 29 09:59:20 <Sicelo> so Wizzup's got a good one :)
Aug 29 09:59:27 <Sicelo> Vajb: you're on thumb?
Aug 29 10:00:08 <Sicelo> my "bad" one is a thumb device, and the "good" one is not. both are CSSU, and same kernel
Aug 29 10:00:18 <Vajb> Sicelo: that's what it used to do for me too, but today it failed to make hostmode connection. And now led is lit no matter what
Aug 29 10:00:29 <Sicelo> maybe i should compare their mce.ini
Aug 29 10:00:49 <Vajb> even succesfull host mode on and off
Aug 29 10:04:48 <Wizzup> I think my good one is on thumb
Aug 29 10:06:07 <Vajb> argh i thought i did it, but it's back
Aug 29 10:06:52 <Vajb> sent dbus deactivate to PatternBoost
Aug 29 10:07:04 <Vajb> it was off like 10 seconds
Aug 29 10:41:21 <KotCzarny> something turns it on apparently
Aug 29 10:46:59 <Vajb> hmm could it be?
Aug 29 10:47:03 <Vajb> ;)
Aug 29 10:47:43 <Vajb> mdbus2 has no info on com.nokia.mce
Aug 29 10:49:20 <Vajb> saw two instances of mce in powertop results, but killing highest priority one made just same effect than stop mce
Aug 29 10:49:42 <Vajb> going for lower one now
Aug 29 10:59:13 <Vajb> 10627 |          1 |            mce | tsc2005_start_scan (tsc2005_esd_timer_handler)
Aug 29 10:59:56 <Vajb> that shows up in powertop but that pid doesn't excist when i try to kill it
Aug 29 11:01:29 <Vajb> reboot
Aug 29 11:07:04 <Vajb> after reboot there is just one instance of mce
Aug 29 11:28:17 <Pali> hi, if you need to test patched usbmode.sh, please drop me email
Aug 29 11:28:27 <Pali> Sicelo Vajb 6
Aug 29 11:28:28 <Pali> 6
Aug 29 11:28:31 <Pali> ^
Aug 29 11:36:38 <Vajb> Pali: to do that i need your email address
Aug 29 12:12:35 <zGrr> moin :)
Aug 29 12:45:12 <nwolf900> 10x, Vajb
Aug 29 13:12:42 <DocScrutinizer05> Pali: I got sth for you to chew on  ;-) https://android.googlesource.com/kernel/msm/+/f632ea92329bc9197daf02ea4baceddceb89a6be/drivers/char/diag  Maybe you can understand the structure (way faster than I would) and tell me how it basically works (upward interface, downward interface (which I suppose is HSI or SDI)) - we would like to have that thing for USB attached Qualcomm chipset. Is it feasible?
Aug 29 13:13:51 <Pali> "This enables diagchar for maemo usb gadget"
Aug 29 13:13:54 <Pali> what is that??
Aug 29 13:18:31 <DocScrutinizer05> what??
Aug 29 13:18:35 <DocScrutinizer05> where?
Aug 29 13:19:02 <DocScrutinizer05> I just found https://android.googlesource.com/kernel/msm/+/f632ea92329bc9197daf02ea4baceddceb89a6be/drivers/char/diag/diagchar.h#108
Aug 29 13:20:12 <DocScrutinizer05> Pali: am I right that this driver could link a /dev/diag_char (or whatever the name) to a USB?
Aug 29 13:20:50 <Pali> https://android.googlesource.com/kernel/msm/+/f632ea92329bc9197daf02ea4baceddceb89a6be/drivers/char/diag/Kconfig#10
Aug 29 13:21:08 <Pali> DocScrutinizer05: I do not know now
Aug 29 13:21:11 <DocScrutinizer05> LOL
Aug 29 13:21:18 <DocScrutinizer05> @maemo
Aug 29 13:28:59 <DocScrutinizer05> Pali: we got a Qualcomm chipset in PHS8, there's https://opensource.srlabs.de/projects/snoopsnitch that needs Qualcomm DIAG_CHAR kernel driver to work, and there's https://android.googlesource.com/kernel/msm/+/f632ea92329bc9197daf02ea4baceddceb89a6be/drivers/char/diag/Kconfig#10  and   https://android.googlesource.com/kernel/msm/+/f632ea92329bc9197daf02ea4baceddceb89a6be/drivers/char/diag/diagchar.h#108
Aug 29 14:06:15 <kerio> infobot just warned me that IRCing as root is a bad idea
Aug 29 14:06:18 <infobot> that's too long, kerio
Aug 29 14:06:25 <kerio> sod off
Aug 29 14:47:22 <DocScrutinizer05> hmm, maybe there's an onjoin for kerio configured in infobot?
Aug 29 14:47:37 <kerio> no, my hostmask matched *!root@*
Aug 29 14:48:01 <DocScrutinizer05> infobot doesn't do that sort of automatic messages afaik
Aug 29 14:48:10 <kerio> on the other hand
Aug 29 14:48:11 <kerio> IT DID
Aug 29 14:48:25 <DocScrutinizer05> yes, maybe because I once asked it to do ;-)
Aug 29 14:48:28 <DocScrutinizer05> years ago
Aug 29 14:49:15 <DocScrutinizer05> however such onjoin always is for particular users, so I had exactly you in mind when asking infobot to do this (*if* I even did)
Aug 29 14:49:33 <DocScrutinizer05> I'll sort it out, sorry for the inconvenience
Aug 29 14:50:19 <DocScrutinizer05> at least I'll try to find out what's going on and stop it
Aug 29 14:50:24 <rootie> hrm, no ident on this server
Aug 29 16:36:59 <Vajb> up with new usbmode.sh
Aug 29 16:38:19 <Vajb> Pali: it says "error: setting usb mode is not supported"
Aug 29 16:38:32 <Vajb> when i click usb mode in menu
Aug 29 16:38:54 <Vajb> i replaced file and rebooted
Aug 29 16:38:59 <Pali> and is script working?
Aug 29 16:39:26 <Vajb> how to confirm?
Aug 29 16:39:31 <Pali> run it?
Aug 29 16:41:37 <Vajb> it works if i run it in terminal, but not from menu
Aug 29 16:41:55 <Vajb> trying host mode now
Aug 29 16:45:43 <Vajb> same problem persist. Blue led is lit and ca't be turned of
Aug 29 16:45:57 <Vajb> host mode works tho
Aug 29 19:14:10 <Vajb> back
Aug 29 19:25:50 <DocScrutinizer05> hmm, Pali forgot that Vajb is a end user who needs precise instructions e.g. regarding sudo gainroot (aka simply `root`) etc
Aug 29 19:39:55 <Vajb> DocScrutinizer05: we debugged till Pali asked me to compile hald-addon-bme and we decided to wait for Sicelo's output :D
Aug 29 19:40:26 <Vajb> err DocScrutinizer05 compile hald-addon-bme with debug symbols
Aug 29 19:44:22 <Vajb> but im just wondering am i the only end user in this channel? Or others are wiser and shut up :D
Aug 29 19:44:40 <KotCzarny> hehe
Aug 29 19:44:55 <KotCzarny> truth is end users dont know about irc
Aug 29 19:45:10 <KotCzarny> so anyone on irc is considered above 'end user'
Aug 29 19:46:04 <Vajb> oooh! So im finally that exception that makes the rule :)
Aug 29 19:46:12 <KotCzarny> nope
Aug 29 19:46:25 <KotCzarny> once you discovered irc, you are not end user anymore
Aug 29 19:47:24 <Vajb> hmm does it count if i discovered irc ten years before i bought maemo device?
Aug 29 19:47:35 <KotCzarny> nope
Aug 29 19:47:42 <Vajb> hmm actually 12 years
Aug 29 19:47:55 <KotCzarny> doesnt matter when, if you know irc, you arent classical luser anymore
Aug 29 19:48:28 <Vajb> so that makes me more like ameba which doesn't develope
Aug 29 19:49:50 <KotCzarny> you apparently never met/supported luser
Aug 29 19:51:21 <Vajb> i think i did, but under different circumstations.
Aug 29 19:51:28 <KotCzarny> :)
Aug 29 19:53:36 <Vajb> and i suppose any lusers cut&paste abilities are brilliant :)
Aug 29 19:53:51 <KotCzarny> you would be surprised
Aug 29 19:54:31 <Vajb> well obviously they need how and where also
Aug 29 19:55:27 <KotCzarny> asking them to paste sudo rm -rf / in the terminal sometimes works
Aug 29 19:56:31 <Vajb> hmm this sounds very much like deltree and so on under windows
Aug 29 19:56:37 <KotCzarny> yup
Aug 29 19:57:00 <Vajb> what is -rf exactly?
Aug 29 19:57:07 <KotCzarny> in original it was seven letters of doom for noobs
Aug 29 19:57:19 <KotCzarny>  -r is recursive, -f is force (ie. dont ask)
Aug 29 19:57:32 <Vajb> ah
Aug 29 19:57:46 <Vajb> so basically remove evything ask nothing
Aug 29 19:57:50 <KotCzarny> yup
Aug 29 19:58:11 <KotCzarny> thats why one should never paste unknown commands
Aug 29 19:58:16 <KotCzarny> read about shell bomb too
Aug 29 19:58:19 <KotCzarny> :)
Aug 29 19:58:20 <Vajb> cool. Now we just need an app for it :)
Aug 29 19:59:08 <Vajb> well that's just common sense
Aug 29 20:05:46 <KotCzarny> as i said, you would be surprised
Aug 29 20:05:47 <KotCzarny> :)
Aug 29 20:07:01 <Vajb> heh. Vajb in wonderland
Aug 29 21:12:56 <Sicelo> Vajb_: hald-addon-bme? in connection with usb-mode issue?
Aug 29 21:13:51 <Vajb_> Pali told me that hald-addon-bme is responsible for light
Aug 29 21:15:14 <Vajb_> and actually i managed to turn off the blue led by issuing "kill hald-addon-bme, stop mce, start mce, stop mce, start mce" , but Pali told me it is not goos to go and adviced to reboot
Aug 29 21:15:33 <Vajb_> goos=good*
Aug 29 21:16:12 <Sicelo> i guess dsme won't like that stop mce too much
Aug 29 21:17:06 <Vajb_> so Sicelo it's up to you now. Compile hald-addon-bme with debug symbols and see what prints /tmp/hald-addon-bme.log IF i recall all that correctly.
Aug 29 21:18:00 <Vajb_> well if you do too much start and stop mce it eventually refuses to start mce for awhile
Aug 29 21:19:04 <Sicelo> yes, dsme begins to think something's wrong with mce .. if you keep forcing it, dsme will simply reboot device anyway
Aug 29 21:20:51 <Sicelo> i'll have to find time for compiling .. haven't booted my scratchbox in a long time
Aug 29 21:24:37 <Vajb> Sicelo: be sure to ask confirmed instructions from Pali. My explanation can't be trusted that much :)
Aug 29 22:07:10 <DocScrutinizer05> stop mce is safe. kill mce isn't
Aug 29 22:08:14 * DocScrutinizer05 thinks hald-addon-bme shouldn't mess with notifier light
Aug 29 22:08:17 <bencoh> start/stop/start/stop/start/stop doesn't seem to be safe either
Aug 29 22:08:27 <DocScrutinizer05> hmm?
Aug 29 22:09:13 <bencoh> I had n900 reboot a few times when doing this
Aug 29 22:10:05 <DocScrutinizer05> I dunno (to lazy to look up) what `stop mce` or `start nmce` does. Could check in upstart event files. But I'd guess it actually *tells* dsme to stop the mce process, so dsme should be happy with that, no matter how often you do it
Aug 29 22:10:59 <bencoh> unless there is a silly timer somewhere or a race (or both)
Aug 29 22:11:27 <Vajb> if you do stop-start cycle too many times in certain time period. Mce refuses to start for few minutes.
Aug 29 22:12:16 <Vajb> but no forced reboot for me today.
Aug 29 22:19:40 <DocScrutinizer05> http://paste.opensuse.org/35983988  http://paste.opensuse.org/43524056
Aug 29 22:20:18 <DocScrutinizer05> if there's a problem with repeatedly doing `start mce` && `stop mce` then that's a bug in dsme
Aug 29 22:24:43 <DocScrutinizer05> Vajb: how does "refuses to start" manifest?
Aug 29 22:25:29 <DocScrutinizer05> I mean, what's the error message?
Aug 29 22:26:25 <DocScrutinizer05> or does upstart return without error msg and yet there's no mce process in process list, after `start mce` ?
Aug 29 22:29:08 <DocScrutinizer05> IroN900:~# initctl status mce
Aug 29 22:29:09 <DocScrutinizer05> mce (start) running
Aug 29 22:29:51 <DocScrutinizer05> http://paste.opensuse.org/45586020
Aug 29 22:30:38 <DocScrutinizer05> IroN900:~# status mce
Aug 29 22:30:39 <DocScrutinizer05> mce (start) running
Aug 29 22:34:06 <DocScrutinizer05> ooh, and device forgot it's connected to fastcharger, after `stop mce && sleep 5 && start mce` (or my USB starts getting old, seen problems with it before)
Aug 29 22:38:27 <DocScrutinizer05> DANG! could somebody please fix dsme(tool)? http://paste.opensuse.org/71910775
Aug 29 22:40:34 <DocScrutinizer05> obviously somebody had a massive hangover, not resetting dsme's internal restart counter on killing a process with -k
Aug 29 22:41:03 <DocScrutinizer05> (hangover while coding)
Aug 29 22:41:20 <DocScrutinizer05> *sigh*
Aug 29 22:42:33 <bencoh> "not resetting dsme's internal restart counter on killing a process with -k" so that's a timer/counter issue ?
Aug 29 22:44:00 <DocScrutinizer05> that's a bug in dsme
Aug 29 22:44:42 <DocScrutinizer05> it increments internal restart-counters on each start, but forgets to reset them on killing the same job
Aug 29 22:44:55 <bencoh> meh :))
Aug 29 22:45:48 <DocScrutinizer05> formally this is in line with the specs, but it's a highly unexpected and nonsensical behavior
Aug 29 22:48:21 <DocScrutinizer05> actually the respawn-counter should count process aborts that are NOT initiated by dsme. And it probably should even reset the internal counter on any start command for a process
Aug 29 22:49:34 <DocScrutinizer05> after all the whole thing is meant to keep processes alive and worst case automatically restart them. Not block user from manually restarting them
Aug 29 22:50:04 <DocScrutinizer05> Pali: ^^^
Aug 29 22:50:35 <DocScrutinizer05> ~seen freemangordon
Aug 29 22:50:38 <infobot> freemangordon <~ivo@46.249.74.23> was last seen on IRC in channel #maemo, 13d 11h 22m 31s ago, saying: 'spongie: nice talk, but I have to leave. still, try to resurrect your n900 with booting rescueos on it :)'.
Aug 29 22:50:38 <Pali> do you mean hald-addon-bme?
Aug 29 22:51:03 <DocScrutinizer05> no, I meant dsme which is borked
Aug 29 22:51:04 <Pali> HAL is broken by design... we cannot fix this *addon*s problems
Aug 29 22:52:01 <Pali> DocScrutinizer05: that paste log is not from dsme but from upstart
Aug 29 22:52:04 <DocScrutinizer05> (HAL) well, I wondered whether hald-addon-bme is the right process to send notification dbus msgs to mce
Aug 29 22:52:20 <DocScrutinizer05> yes, I know that
Aug 29 22:52:30 <Pali> and it is problem in upstart
Aug 29 22:52:33 <DocScrutinizer05> however http://paste.opensuse.org/35983988
Aug 29 22:52:37 <Pali> "respawning too fast, stopped"
Aug 29 22:52:37 <DocScrutinizer05> aha
Aug 29 22:53:01 <Pali> no idea how to fix that maemonized upstart
Aug 29 22:53:03 <DocScrutinizer05> then upstart is *really* idiotic program
Aug 29 22:53:10 <Pali> this is maemo upstart
Aug 29 22:53:17 <Pali> normal ubuntu upstart do not do that
Aug 29 22:53:35 <DocScrutinizer05> I still guess it's a dsme message
Aug 29 22:53:36 <Pali> years ago I tried to fix that problem, but no chance...
Aug 29 22:53:55 <Pali> no this is upstart for sure, I know that!
Aug 29 22:54:13 <DocScrutinizer05> hmm, I could try. but not now, about to get that beer that's waiting for me out there :-)
Aug 29 22:54:56 <Pali> dsme autorespawn works fine
Aug 29 22:55:22 <DocScrutinizer05> anyway, when you say you know, I won't bother to check. You know your shit. However it's a pity we can't fix it
Aug 29 22:55:57 <Pali> fix could be possible, but that means to read and understand that old maemonized upstart code
Aug 29 22:55:59 <DocScrutinizer05> what did they do to maemo upstart?
Aug 29 22:56:10 <Pali> which is not ubuntu upstart
Aug 29 22:56:17 <DocScrutinizer05> sucks
Aug 29 22:57:23 <Pali> I do not want to touch init process without 100% knowledge of all changes
Aug 29 22:57:27 <Pali> this is high risk
Aug 29 22:57:47 <Pali> broken pid 1 means non working system
Aug 29 22:57:55 <Pali> without way to recover
Aug 29 22:58:45 <kerio> let's just move to systemd
Aug 29 22:58:59 <kerio> :>
Aug 29 22:59:01 <DocScrutinizer05> yes I know :-) However I guess PID1 *is* broken. Look at http://paste.opensuse.org/98152157, says it all already. I feel an urge to bash somebody
Aug 29 22:59:01 <Pali> leave this channel
Aug 29 23:02:48 <DocScrutinizer05> >>Alternatively if --by-id is given...<< WTF?! where is this listed?
Aug 29 23:03:46 <DocScrutinizer05> this prolly is >>  -i, --id                    arguments are job ids, instead of names<<, NOT >>--by-id<<, suckers!!
Aug 29 23:05:17 <DocScrutinizer05> IroN900:~# initctl --version
Aug 29 23:05:19 <DocScrutinizer05> initctl (upstart 0.3.8)
Aug 29 23:05:20 <DocScrutinizer05> Copyright (C) 2007 Canonical Ltd.
Aug 29 23:05:25 <DocScrutinizer05> no word about maemo or Nokia
Aug 29 23:06:02 <DocScrutinizer05> whatever, bbl. cya
Aug 29 23:08:04 <DocScrutinizer05> Vajb: you could stop mce once with `stop mce`, then start it with  `/usr/sbin/dsmetool -n -1 -t "/sbin/mce --force-syslog"` and stop with `/usr/sbin/dsmetool -k "/sbin/mce --force-syslog" `
Aug 29 23:27:42 <DocScrutinizer05> stuff like >>/usr/bin/tonegend -s cept -b 100 -r 20 -D module-stream-restore.id=x-maemo-key-pressed -I media.role=phone,module-stream-restore.id=sink-input-by-media-role:phone -N media.role=phone,mod<< makes me shudder
Aug 30 01:16:12 <DocScrutinizer05> particularly since:
Aug 30 01:16:14 <DocScrutinizer05> IroN900:~# tonegend --help
Aug 30 01:16:16 <DocScrutinizer05> usage: tonegend [-h] [-d] [-u username] [-s {cept | ansi | japan}] [-b buflen_in_ms] [-r min_req_time_in_ms] [-i] [-8] [-S] [--tag-dtmf tags] [--tag-indicator tags] [--tag-notif tags] [--volume-dtmf volume] [--volume-indicator volume] [--volume-notif volume]
Aug 30 01:17:33 <DocScrutinizer05> thankyou for missing -D and -t and -N
Aug 30 01:18:43 <DocScrutinizer05> s/-t/-I/
Aug 30 01:18:43 <infobot> DocScrutinizer05 meant: thankyou for missing -D and -I and -N
Aug 30 02:46:18 <Maxdamantus> Hmm .. what causes the VDQ to reset to 0 shortly before EDV1 goes to 1?
Aug 30 02:48:37 <Maxdamantus> https://gist.github.com/Maxdamantus/702809177892347cb778
Aug 30 02:49:26 <Maxdamantus> (that isn't actually the original bq27200.sh script—I modified it to read the registers from /sys instead of using i2c directly)
**** ENDING LOGGING AT Sun Aug 30 02:59:58 2015