IRC log for #maemo on 20160625

00:22.11DocScrutinizer05SIP presence is a non-satndard SIP extension. Video: I never seen it working but that's mainly been for lack of support by my service provider, anyway I never seen maemo SIP UI quit on trying video
00:23.15DocScrutinizer05possibly the service provider sends a BYE to you when you announce you want to initiate/chnage-to a *video* session
00:25.20DocScrutinizer05again ethereal is your friend, check the Session Description and which codecs are offered/requested and what's the response
00:25.54DocScrutinizer05ethereal even has very nice dissectors for all that stuff
00:26.13DocScrutinizer05almost self explanatory
00:28.17JuestLinphone does video, tested already.
00:28.42JuestJust with her, Jingle and SIP video /does not work *at all* /
00:30.23DocScrutinizer05you *might* be interestef in this little cmdline hack: http://talk.maemo.org/showthread.php?p=1022444  - take care to apply a filter for the ethereal traffic when you use this (modified for WLAN instead ISI) to monitor the VoIP traffic. Otherwise you get an avalanche of self referential logging
00:31.14DocScrutinizer05again, this is no help channel for linphone
00:31.25JuestNot asking linphone help :|
00:31.31Juestbut video call help
00:31.37DocScrutinizer05neither jingle
00:33.14DocScrutinizer05all relevant data for maemo SIP video can get gathered by using ethereal on device as suggested above
00:33.58Juestwireshark-like ?
00:34.18DocScrutinizer05ethereal/wireshark, I forget which is the recent name
00:35.01DocScrutinizer05prolly wireshark, yes
00:35.23Juestaka you're telling us to capture the "event"
00:35.40DocScrutinizer05if you want to put it that way, yes
00:36.32DocScrutinizer05the only effective way to debug SIP issues is to look what's going on on SIP protocol level
00:38.19JuestVoice calls work great, the issue is when any video is attempted it just stops responding
00:38.39DocScrutinizer05when your client receives a session description that's not compliant with its capabilities, or when other end sends an error because of similar problem there, then the session will abort. That's normal
00:39.05DocScrutinizer05yes, understood. Sesion Descriptions differ between voice calls and video calls
00:40.30DocScrutinizer05when you switch on video, the client tries to negotiate a new session (description) with far end
00:40.52DocScrutinizer05since a new RTP channel and a associated video codec is needed
00:41.03Juesti do not even receive video calls
00:41.21DocScrutinizer05en passant a new audio channel description mightt get negotiated too
00:41.56DocScrutinizer05sorry, I don't understand what you meant by >>i do not even receive video calls<<
00:43.44JuestAnything that involves video calls = doesnt work properly
00:45.04DocScrutinizer05and I explained above WHY that might be the case
00:45.37JuestJingle barely worked, Skype on maemo crashes when video is attempted and i never receive a sip video call and if its attempted mid-call the call dies
00:45.43DocScrutinizer05so either you want to check if we can find the reason and possibly fix it, or you contine to state "video doesn't work" and I'm out
00:47.20DocScrutinizer05please understand that it's worth nothing in this context to list what works or doesn't work
00:48.09DocScrutinizer05the only way to takle this is looking at either error logs or traffic dump
00:48.12Juestdidnt you just said you didnt understand?
00:48.16JuestOkay
00:48.24Juesti'll do that
00:49.01DocScrutinizer05alas maemo telepathy logs are pathetic at best, rather non-existent at all
00:49.16DocScrutinizer05so your best chance is wireshark
00:51.46DocScrutinizer05suspects that maemo only offers h.263 video codec and that might not be very popular and commonly supported anymore
00:52.08Juestumm, Jingle and Skype are on H264....
00:52.42DocScrutinizer05so unless far end offers same h.263 codec, a video call will fail (if the assumption is corect)
00:53.35DocScrutinizer05N900 only can do 'low profile' video on the h.26x codecs
00:55.38DocScrutinizer05err maybe it's called baseline profile
00:56.20DocScrutinizer05H.254 Baseline Profile (BP): Primarily for lower-cost applications with limited computing resources, this profile is used widely in videoconferencing and mobile applications.
00:56.32DocScrutinizer05H.264 even
00:57.15JuestAnd Skype shouldnt crash on video then -_-
00:57.42DocScrutinizer05aha
00:58.01DocScrutinizer05Skype crashes too?
00:59.11JuestAs soon she taps Camera = "boom" literally
01:00.03DocScrutinizer05when SIP and Skype both crash, odds are it's either both 'protocols' switched from H.263 / H.254 base line to more CPU power demanding codecs during the last 6 years, or your device's DSP is defect on a hw level
01:00.49DocScrutinizer05dang, s H.254 H.264
01:02.34DocScrutinizer05though the user agents /clients should handle a "codec not supported" gracefully, falling back to audio-only and possibly even telling in plaintext why video isn't possible. a crash would suggest sth is odd on hw level. maybe a peek into syslog could help reveal the root cause
01:03.38DocScrutinizer05I wonder if video recording still works on same device where video calls crash
01:04.17DocScrutinizer05ooh ugh! is the device overclocked?
01:05.01Juestin summary: Jingle barely works, SIP video calls do not function at all (call ghosts on my side and ends on her side if video activated mid-call and i never receive a call if she tries to video call from the start) and Skype crashes on her side on any attempt to send video
01:05.21DocScrutinizer05or rather: has it been used in overclocked mode for extended periods of time?
01:07.57DocScrutinizer05reportedly the DSP which does the H.26x encoding is particularly prone to wearing out permanently and then crashing when operated in overclocked mode
01:08.38*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
01:09.24JuestDamnit, its Saturday in Australia and I'm not the maemo user, i am unable to answer such device questions. Oksana is the user who i am helping/asking on behalf
01:09.27DocScrutinizer05actually it's even notorious for not being that stable and wearing out eventually on non-OC devices
01:10.00DocScrutinizer05dammit then why isn't it HER who asks in here?
01:10.49JuestBecause she's either busy or unavailable
01:11.01DocScrutinizer05when you're asking on behalf, you should receive the answers on behalf as well, no?
01:11.32JuestI cant answer your device questions but sure, i am going to tell her to put a network tracer on her device
01:12.36DocScrutinizer05*sigh*, we already changed investigation vecor towards why Skype also crashes and that it suggests there might be a hw problem
01:14.26DocScrutinizer05a colorblind in a phonecall to the Police ATF guy: "So what do next? the display shows 10s!!"  Reply: "cut the green wire!"
01:17.47DocScrutinizer05you're aware that oksana is ex-councilor and knows about this IRC channel and the chanlog, and she also knows she can ask me any time and will get an answer?
01:18.05JuestYes
01:18.17Juestbut she apparently somewhat isolated from everyone
01:18.22Juestand i am helping her on my own
01:18.30DocScrutinizer05so I don't see how you in a role as proxy will simplify things
01:18.45JuestAt least i tried
01:19.03Juestor trying
01:19.21*** join/#maemo eMHa__ (~mh@p54B0F8D3.dip0.t-ipconnect.de)
01:21.47*** join/#maemo Humpelstilzchen (erik@x4e36fd1c.dyn.telefonica.de)
01:23.26DocScrutinizer05when wikiwide err oksana can't use IRC and instead has other non-public channels to communicate to you, then please you chime in here next time when you have contact to her realtime, so we at least can answer the "multiple choice part" of the test in a timely manner
01:24.57JuestI'll let you know
01:25.01DocScrutinizer05:-)
01:28.47JuestAnd yes, i am aware.
01:40.54DocScrutinizer05for now things to do: install syslog and get the logs of any crash and pastebin them. Test camera recording videos in all offered resolutions/modes, at least 30s each, check for crashes and again see syslog. Do a traffic dump with "tshark .. >dumpfile" and provide it per pastebin or on a server
01:41.36DocScrutinizer05enable coredumps and provide any that may get produced by crashes
01:45.04DocScrutinizer05please see "sp-rich-core - Rich core"  app
01:45.28DocScrutinizer05apt-get install sp-rich-core
02:14.41Juestgdb support?
02:34.04*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
02:35.09*** join/#maemo LauRoman (~LauRoman@5-14-14-3.residential.rdsnet.ro)
02:46.49*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
02:47.08*** join/#maemo ruskie (ruskie@sourcemage/mage/ruskie)
02:59.26*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
03:14.40*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
03:37.05*** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net)
03:49.04*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
03:58.56DocScrutinizer05oxoxoxoxo
03:59.12DocScrutinizer05s/oxo/ÖxÖ/g
03:59.41Juestlol
04:00.36*** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
04:01.05DocScrutinizer05indeed, epic fail for las 'oxo'
04:01.39DocScrutinizer05oxoxoxoxo
04:01.53DocScrutinizer05s/oxo/oXo/g
04:02.16DocScrutinizer05tzz
04:05.26Juesttry just ox instead
04:07.24JuestJust curious, /who/ are you
04:10.16*** join/#maemo pagurus (~user@pD950CD3E.dip0.t-ipconnect.de)
04:30.00*** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net)
04:33.37DocScrutinizer05~joerg
04:33.39infobotrumour has it, joerg is a natural born EE, ex HW-developer and engineer of Openmoko. Usually known as DocScrutinizer. Initiator of http://neo900.org
04:33.54DocScrutinizer05~ DocScrutinizer
04:33.55infobotit has been said that docscrutinizer is jOERG, a HW-developer and engineer of Openmoko
04:34.42DocScrutinizer05Juest: I'm more interested in overlapping pattern matching in regex
04:35.21JuestInteresting.
04:35.50DocScrutinizer05123123
04:36.00DocScrutinizer05s/2/two/g
04:36.10DocScrutinizer05s//TWO/g
04:37.25DocScrutinizer05s/o/Ö/g
04:37.37DocScrutinizer05s/2/Ö/g
04:38.10DocScrutinizer05s\,2,Ö,
04:38.28DocScrutinizer05s/2/Ö/g
04:38.53DocScrutinizer05s#2#Ö#g
04:39.08DocScrutinizer05s/#/\//
04:39.30DocScrutinizer05s/#/§/
04:39.44DocScrutinizer05meh
04:57.42*** join/#maemo r00t-home (~r00t@port-92-196-11-178.dynamic.qsc.de)
05:04.53DocScrutinizer05[jr@lagrange ~]$ echo oXoXoXoYoXoXÖXoXo|tee >(sed 's/oX/ox/g')&&usleep 100000
05:04.55DocScrutinizer05oXoXoXoYoXoXÖXoXo
05:04.56DocScrutinizer05oxoxoxoYoxoxÖXoxo
05:05.25Juestlol
05:05.38DocScrutinizer05I want *all* oXo replaced by oxo
05:05.51DocScrutinizer05but *only* oxo
05:06.26DocScrutinizer05err *only* oXo
05:08.05DocScrutinizer05[jr@lagrange ~]$ echo oXoXoXoYoXoXÖXoXo|tee >(sed 's/oXo/oxo/g')&&usleep 100000
05:08.06DocScrutinizer05oXoXoXoYoXoXÖXoXo
05:08.08DocScrutinizer05oxoXoxoYoxoXÖXoxo
05:09.20DocScrutinizer05here a sed 's/oXo/oxo/g;s/oXo/oxo/g' would do, but that's rahter non-generic
05:09.51DocScrutinizer05at least I guess it's not generic
05:12.20DocScrutinizer05IOW is it valid solution for all arbitrary M, N of 's/M/N/g;s/M/N/g'  ?
05:13.13JuestHmm
05:16.43DocScrutinizer05prolly needs something like sed ': start; s/[Oø]XO/øxø/; t start'
05:19.02DocScrutinizer05jr@saturn:~> echo OXOXOXOXOX|sed ': start; s/[Oø]XO/øxø/; t start'
05:19.04DocScrutinizer05øxøxøxøxøX
05:24.11DocScrutinizer05for performance reasons and possible nasty effects when substitution unexpectedly creates new valid matches in patternbuffer  however I'd prefer a variation of g parameter to s// (e.g. G ?) that sets a marker at beginning of matched substring and in case of a match&substitution would restart at that marker rather than start of pattern buffer (which is what the ': start' version does)
05:29.41*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
05:31.57DocScrutinizer05also sed sucks big time in that it doesn't obey $IFS
05:34.50Juesto.o
06:16.06*** join/#maemo RedW (~redw@89-76-164-87.dynamic.chello.pl)
06:17.19DocScrutinizer05ooooo
06:17.29DocScrutinizer05s/o/X/2
06:17.34DocScrutinizer05thought as much
06:19.15Juestlol
06:26.50DocScrutinizer05o.O  's'(ubstitute) command parameters:  >>
06:26.52DocScrutinizer05<PROTECTED>
06:26.53DocScrutinizer05<PROTECTED>
06:29.25DocScrutinizer05http://paste.opensuse.org/37483588
06:44.28DocScrutinizer05>>... these  commands can enable one to write quite convoluted scripts<< LOL
06:47.01DocScrutinizer05mhm, improved version:  sed 's/[Oø]XO/øxø/; t'
07:21.48DocScrutinizer05manpages and particularly texinfo are funny reads
07:36.12*** join/#maemo lxp (~lxp@unaffiliated/lxp)
07:38.57JuestAlways
07:39.07JuestThe man book ;)
07:46.57*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
08:14.39DocScrutinizer05info ed  -- priceless
08:15.10DocScrutinizer05I actually *used* that stuff 25some years ago
08:16.15DocScrutinizer05on BS1000 or somesuch "OS"
08:16.56DocScrutinizer05hmm BS2000?
08:20.00DocScrutinizer05I guess it was 30 years ago and actually BS1000
08:28.21*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
08:33.02*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
08:33.30*** join/#maemo heroux (~heroux@gateway/shell/insomnia247/x-osabncgmqcpxkaki)
08:50.37*** join/#maemo cyphase (~cyphase@unaffiliated/cyphase)
09:11.58*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
09:16.50*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
09:18.29*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
09:27.51*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
09:31.50*** join/#maemo Cor-Ai (~cor-ai@c-85e5e655.06-922-7570702.cust.bredbandsbolaget.se)
09:48.01*** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
09:50.16*** join/#maemo japa-fi (~jani@mobile-access-bceea2-184.dhcp.inet.fi)
09:54.04*** join/#maemo japa-fi (~jani@mobile-access-bceea2-184.dhcp.inet.fi)
09:57.18*** join/#maemo M4rtinK (~M4rtinK@ip-78-102-146-111.net.upcbroadband.cz)
10:05.05*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
10:12.13*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
10:16.16*** join/#maemo xorly| (~xorly@ip-89-176-117-132.net.upcbroadband.cz)
10:41.29*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
11:06.49*** join/#maemo japa-fi (~jani@mobile-access-6df096-69.dhcp.inet.fi)
11:38.42*** join/#maemo trx (ns-team@cable-188-2-27-101.dynamic.sbb.rs)
11:38.54*** join/#maemo trx (ns-team@devbin/founder/trx)
12:07.07*** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
12:18.58*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
12:48.16*** join/#maemo xelo (~xelo@ip-176-198-129-195.hsi05.unitymediagroup.de)
12:56.20*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
13:04.50*** join/#maemo Cor-Ai (~cor-ai@c-85e5e655.06-922-7570702.cust.bredbandsbolaget.se)
13:23.03*** join/#maemo sq-one (~sq-one@HSI-KBW-109-193-054-130.hsi7.kabel-badenwuerttemberg.de)
13:44.42*** join/#maemo auenfx4 (David@DC-72-89.bpb.bigpond.com)
13:46.54*** join/#maemo Mek_ (~quassel@kde/mkruisselbrink)
13:49.05*** join/#maemo drathir87 (~kamiljk8@unaffiliated/drathir)
13:49.08*** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-lsepwjoudjuodiex)
13:49.13*** join/#maemo oniongar1ic (~milang@tori.tal.org)
13:52.18*** join/#maemo silviof (~silviof@unaffiliated/silviof)
13:52.24*** join/#maemo teotwaki (~teotwaki@Maemo/community/contributor/crashanddie)
13:54.03*** join/#maemo ShadowJK (~jk@212.7.198.194)
13:54.05*** join/#maemo jabis (~jabis@vps003.pumppumedia.com)
13:54.40*** join/#maemo l_bratch (~l_bratch@82.112.156.32)
13:56.17*** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-xupttodvpsjqertk)
14:12.18*** join/#maemo andril (~andril@50-203-31-92-static.hfc.comcastbusiness.net)
14:27.59*** join/#maemo auenf (David@DC-72-89.bpb.bigpond.com)
14:41.20*** join/#maemo LauRoman (~LauRoman@5-14-14-3.residential.rdsnet.ro)
15:09.52*** part/#maemo pagurus (~user@pD950CD3E.dip0.t-ipconnect.de)
15:11.37*** join/#maemo LauRoman (~LauRoman@5-14-14-3.residential.rdsnet.ro)
15:49.50*** join/#maemo krnlyng (~liar@77.116.54.37.wireless.dyn.drei.com)
16:25.24*** join/#maemo lobito (~lobito@unaffiliated/lobito)
16:44.25*** join/#maemo japa-fi (~jani@mobile-access-6df096-69.dhcp.inet.fi)
17:48.32*** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net)
17:48.44L29Ahwhy isn't there navit-graphics-opengl?
17:48.48*** join/#maemo sunshavi (~user@190.235.18.236)
18:31.31L29AhWizzup_: i've written an ebuild for maemo that can utilize gles; would be nice if you check out its performance on an n900
18:31.36L29Ahnavit::booboo
18:31.45L29Ahs/maemo/navit/
18:36.19*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
19:30.34*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
20:00.20*** join/#maemo xes_ (~xes@unaffiliated/xes)
20:12.42*** join/#maemo sparetire (~sparetire@unaffiliated/sparetire)
20:25.03Wizzup_L29Ah: I don't have gles yet on gentoo
20:25.07Wizzup_can try that though
20:29.01*** join/#maemo M4rtinK (~M4rtinK@ip-78-102-146-111.net.upcbroadband.cz)
20:33.29*** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
22:27.59L29Ahincidentally compiled a fresh kernel for n900; i wonder how do i check if it works using only maemo
22:33.16*** join/#maemo eijk_ (~eijk@x4e377830.dyn.telefonica.de)
22:47.16Wizzup_L29Ah: tweak the u-boot menu to use the right args?
22:48.34L29Ahso, will 'init=/bin/bash' work out of the box?
22:49.03L29Ahforgot everything he tried last year
22:51.11Wizzup_I would suggest to see what is in the uboot entry/list
23:13.14L29Ahk display doesn't work, although it seems like i successfully rebooted it with typing 'reboot' :]
23:13.50L29Ahoh maybe i didn't do the dt stuff
23:24.11L29Ahno slash in the console for me, somehow the blue arrow key doesn't do much

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.