IRC log for #maemo-ssu on 20120326

00:32.01*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.142)
02:39.56*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
03:18.18*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
07:32.10*** join/#maemo-ssu dafox (~dafox@dyn-194234.nbw.tue.nl)
07:39.44*** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn)
07:57.40*** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy)
08:03.59*** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre)
08:39.12*** join/#maemo-ssu dafox (~dafox@dyn-194234.nbw.tue.nl)
08:43.20*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138)
09:19.05*** join/#maemo-ssu Pali (~quassel@unaffiliated/pali)
09:49.54Lava_Crofthmm, those 'fixed' transitions from TMO actually are really well done
09:49.57Lava_Croftcssu material
09:50.51Lava_Croftoh, the word seems to be 'smoothest'
09:50.52Lava_Crofthttp://talk.maemo.org/showthread.php?t=83000
09:58.37peetahLava_Croft: is'nt OC 1000MHz the real smooth factor, rather than the transition.ini ?
09:58.46Lava_Croftpeetah: not at all
09:58.51Lava_Croftim using stock kernel
10:21.34*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
10:31.06*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-ugyewanumjxgfyaj)
10:31.27*** join/#maemo-ssu trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623)
10:39.52*** join/#maemo-ssu arcean (~Arcean@aadc39.neoplus.adsl.tpnet.pl)
10:51.36*** join/#maemo-ssu DocScrutinizer (~halley@openmoko/engineers/joerg)
11:43.52*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-85-160-39-243.eurotel.cz)
11:51.30*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
11:59.36*** join/#maemo-ssu M4rtinK2 (~M4rtinK@ip-85-160-184-7.eurotel.cz)
12:02.04*** join/#maemo-ssu Pali (~quassel@unaffiliated/pali)
12:07.40*** join/#maemo-ssu M4rtinK2 (~M4rtinK@ip-85-160-46-40.eurotel.cz)
12:25.43*** join/#maemo-ssu arcean_ (~Arcean@aact250.neoplus.adsl.tpnet.pl)
12:31.14*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138)
13:40.45*** join/#maemo-ssu M4rtinK2 (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
13:47.01dafoxhi all. Since A few days ago I updated my n900 to newest CSSU (I think it's 2.1, with 1.2 already installed). Since then my phone seems to sometimes get confused about whether it is in landscape/portrait orientation. Does anyone know what might be going on?
13:47.11dafoxWhen it happens for example 'xbmc remote' will always be in landscape mode, eventhough it does not support this, and normally it is always in portrait mode (the interface is only designed for portrait mode)
13:47.21dafoxwhen I launch the phone app by turning the following happens: desktop rotates from landscape->portrait, desktop spins to show phone app in portrait mode, phone app spins to landscape mode. If I then select for example settings it rotates back again to portrait to show the settings dialog. Here 'turning control' was set to 'always portrait mode' (so it shouldn't have rotated to landscape in the first place)
13:48.38dafoxI am suspecting it may somehow be related to the gui/desktop (hildon?) sometimes crashing when I stop/pause drnoksnes (it already always did this, but not caused any issues before)
14:40.09*** join/#maemo-ssu sam23m (~user@112.201.222.115)
14:43.31sam23mhi yall
14:45.00sam23mwhenever i get an email so there are those yellow notifications on the task nav right? when i press it, it goes to the mailbox folders. is it possible to make it direct to the inbox?
14:45.35*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
14:51.03*** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm)
15:04.06*** join/#maemo-ssu MohammadAG (~MohammadA@ool-45772b34.dyn.optonline.net)
15:10.15*** join/#maemo-ssu Guest82264 (~rd@p57B4948C.dip0.t-ipconnect.de)
15:53.38*** join/#maemo-ssu NIN101 (~NIN@206.253.166.69)
16:24.15*** join/#maemo-ssu M4rtinK2 (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
17:17.26*** join/#maemo-ssu int_ua (~int_ua@93.126.96.47)
17:20.07*** join/#maemo-ssu BCMM_ (~user@unaffiliated/bcmm)
17:32.53*** join/#maemo-ssu NIN102 (~NIN@206.253.166.69)
17:35.45*** join/#maemo-ssu Pali (~quassel@unaffiliated/pali)
17:38.47DocScrutinizermerlin1991: update done, no obvious adverse effects
17:39.00DocScrutinizerrtcom-sip stayed
17:43.02DocScrutinizerdman drive by askers
17:44.02DocScrutinizerseems their problems either aren't that severe, or they solve magically
17:44.16merlin1991dafox is coming and going as far as I see it
17:44.23DocScrutinizermh#
17:44.27DocScrutinizermhm even
17:44.28merlin1991but whe he reports has nothing todo with cssu
17:44.42merlin1991from 1.2 to 2.1 were no rotation related changes in h-d
17:45.07DocScrutinizermaybe in blacklist though
17:45.20DocScrutinizereven in *his* blacklist?
17:45.46DocScrutinizeranyway, his report sounds strangely familiar to me
17:45.55DocScrutinizermus've heard this before
17:48.15DocScrutinizerponders writing a shorty for /etc/init.d/, to set the orientation lock during each boot
17:49.15DocScrutinizerprolly I rather should get rid of this friggin self-destr^Worientation-lock statusbar widget
17:51.12DocScrutinizerthough it still blows my minds to get the point in nuking a gconf-key like gui-may-rotate when hitting this lock-button, and then not restoring it to original value when 'un'hitting same button
17:51.55DocScrutinizerI'm temped to shout BUUUUUG!
17:57.11merlin1991DocScrutinizer: well when you hit the lock you change 2 values
17:57.31DocScrutinizerand the rationale for that?
17:57.40merlin1991both are checked for by h-d
17:57.57DocScrutinizertoldya, BUUUG ;-D
17:58.06merlin1991rotation rendering in h-d is a HUGE 500 lines long BUG :D
17:58.57DocScrutinizerwow, that squirts when we smash it
18:00.01merlin1991lol
18:00.02DocScrutinizeranyway, 500 lines is probably average length of a minor helper function on that system I maintain for bagels
18:01.22merlin1991hm I need to refacter 200 lines of helper functions into a class here
18:01.27merlin1991and add threading on top
18:01.32merlin1991not looking forward to that
18:01.41DocScrutinizerseems some of our coders use their 31" screen in portrait, just to be able to say "but well, it not exactly one screen length, but almost only two"
18:01.55merlin1991:D
18:02.07*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
18:03.04DocScrutinizerusing insanely long inline functions and even macros is another popular method ;-)
18:03.16merlin1991insanely long inline functions?
18:03.18merlin1991WTF
18:03.54merlin1991macros and long explicit inline functions, probably 2 of the worst things in regard to speed
18:04.11DocScrutinizeridly wonders if OMAP3430 also has a built-in embedded-tracing-module
18:04.59DocScrutinizermerlin1991: look at ARM assembler log of a good C compiler. You'll be amazed
18:05.44DocScrutinizerthe friggin thing optimizes so ruthlessly that I sometimes honestly doubt I'm looking at my own code
18:06.04DocScrutinizermoving functions inline though they aren't
18:06.20merlin1991I live way too highlevel on x86, arm assembler is a language I don't understand :D
18:06.27DocScrutinizerswapping sequence of code lines, in the magnitude of 10 to 100
18:06.35DocScrutinizerlines
18:06.57DocScrutinizerreal fun to watch those things on in-circuit-debugger
18:07.29merlin1991well next or the semseter after that I'll have a compiler specific lecture where as a part of it we're going to build our own, that's going to be fun
18:09.19DocScrutinizerjust compile an arbitrary n900 pkg with the proper compiler flags to produce asm logs with interleaved c sourcelines. You'll marvel at what you see
18:10.01DocScrutinizerI'm rather sure gcc is no less nifty regarding optimisation than RVCT
18:11.06DocScrutinizerinline directive is just a suggestion to compiler
18:12.02DocScrutinizerand register directive is simply nonsense to use, the compiler is waaaay better than you are, regarding keeping the right vars in registers
18:13.38DocScrutinizerit seems there are even such weird things like an ARM functioncall ABI, which defines that up to 4(?) 32bit dates are passed to a function in registers, not stack
18:14.16DocScrutinizeron c++ of course one less
18:14.32DocScrutinizerfor THIS
18:15.45DocScrutinizerthe mixing of thumb and ARM code doesn't help on readability of asm code ;-D
18:18.15*** join/#maemo-ssu BCMM_ (~ben@unaffiliated/bcmm)
18:23.13RaimuIs there some neat list of all of maemo's important sqlite-based databases?
18:23.56RaimuI understand some're filename.db while others have no signifier in their filename at all.
18:24.33Raimu(This in regards to the discussion of bloated eventdb and whatnot databases)
18:50.53*** join/#maemo-ssu ekze (nyan@2002:5046:e474:1::3)
19:02.38*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
19:21.11*** join/#maemo-ssu arcean (~arcean@aact250.neoplus.adsl.tpnet.pl)
19:54.46*** join/#maemo-ssu infobot (~infobot@rikers.org)
19:54.46*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version (testing): 21.2011.38-1Tmaemo2.1; (stable): 21.2011.38-1Smaemo2.1 | meeting: 28.03 20:00 UTC
19:54.46*** mode/#maemo-ssu [+v infobot] by ChanServ
20:06.29*** join/#maemo-ssu Guest82264 (~rd@p57B4948C.dip0.t-ipconnect.de)
20:17.18*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
20:36.16*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
22:02.02*** join/#maemo-ssu int_ua (~int_ua@93.126.96.47)
22:34.42*** join/#maemo-ssu Kaptenen (~Kaptenen@81.216.60.47)
22:37.42*** join/#maemo-ssu f4cl3y (~user@94.249.83.64)
23:47.38*** join/#maemo-ssu Jade (~jade@modemcable028.134-202-24.mc.videotron.ca)
23:47.38*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)

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