**** BEGIN LOGGING AT Thu Apr 30 02:59:58 2015 Apr 30 06:33:29 krbtgt_: maybe you have installed some packages from other repos and now you have conflicts Apr 30 06:34:05 instead of fighting in ham try apt-get way Apr 30 06:34:34 in the worst case you might try removing them or forcibly installing via dpkg Apr 30 06:37:07 well, otherwise just backup and flash stock image Apr 30 06:37:12 might be faster Apr 30 06:37:13 :) Apr 30 06:49:01 or maybe already prepared cssu or cssu-thumb image if there is such thing Apr 30 07:31:55 bencoh: did you play with maemo-launcher? any result? Apr 30 08:02:49 freemangordon_: havent tried it yet Apr 30 08:06:04 bencoh: http://pastebin.com/uuBp3JiF Apr 30 08:07:09 time is ~550 with QGuiApplication *gui... commented, vs ~290 with those 2 lines uncommented on my laptop Apr 30 08:08:29 going to try on the device Apr 30 08:17:08 hmm Apr 30 08:21:25 bencoh: on device it is ~880 vs ~960, using QCoreApplication (seems there is no QGuiApplication in qt4.7) Apr 30 08:23:13 bencoh: by using QApplication, time is reduced to ~220, but there are some UI artifacts Apr 30 08:24:54 oh, wait, actually those are not artifacts :) Apr 30 08:24:55 hmm² Apr 30 08:26:11 so ... it means we'd save at most 10% by writing a qt launcher ? Apr 30 08:26:39 or am I missing something ? Apr 30 08:27:01 save 10% time but lose part of memory? Apr 30 08:27:13 so it will slow rest of the system? Apr 30 08:27:33 960 vs 220 is not 10% Apr 30 08:27:41 if I remember what math is :P Apr 30 08:27:44 oh, 960 vs 220 Apr 30 08:27:46 nevermind Apr 30 08:28:04 you wrote 960 vs 880 Apr 30 08:28:13 I see :) Apr 30 08:28:26 KotCzarny: read it again, please Apr 30 08:28:53 right, missed it too Apr 30 08:28:55 :) Apr 30 08:29:46 but it seems creating qapplication twice, leads that the "real" application is started with GTK style, instead of maemo style Apr 30 08:29:57 funny Apr 30 08:30:23 now wait, isnt precisely why it seems to be running "faster" ? Apr 30 08:30:27 +it Apr 30 08:30:32 :> Apr 30 08:31:05 bencoh: look at the code Apr 30 08:32:43 yeah I'm reading it (10:30am, I should be fully awake ...) Apr 30 08:33:08 http://pastebin.com/Rm6PbFt6 Apr 30 08:33:15 this is the latest Apr 30 08:33:39 now that's different :) Apr 30 08:33:49 see where is QTime::elapsed qDebug()'ed Apr 30 08:33:55 yeah Apr 30 08:35:16 (before widgets get drawn ?) Apr 30 08:36:06 yes Apr 30 08:44:34 moin :) Apr 30 08:51:34 dammit, the wifi I am connected to drives me mad, it disconnects every now and then :( Apr 30 09:15:53 hmm, looks like https://gitorious.org/meegotouch/maemo-applauncherd hasnt been transfered to github (?) Apr 30 09:22:26 nor did we move maemo-af (?!) Apr 30 09:22:49 maybe write a script that would check all of the components ? Apr 30 09:23:18 I thought it was done already, but ... Apr 30 09:24:18 ooh, that might be on maemo.org ... dunno where though Apr 30 09:59:45 freemangordon_: looks like maemo-launcher inits every booster for every app Apr 30 09:59:55 hmm? Apr 30 10:00:12 that doesn't make sense Apr 30 10:00:24 boosters_init(boosters, prog.argv[0]); Apr 30 10:00:33 ooh Apr 30 10:00:38 in the child (after fork and before launch_process) Apr 30 10:00:57 and boosters_init loops on ... well, the boosters chained list Apr 30 10:01:02 do we have problem with that? Apr 30 10:01:10 dunno, maybe Apr 30 10:01:30 i doubt, after all there should not be n=much work done in that function Apr 30 10:01:33 if we add a qt booster, gtk apps would init a qt env as well Apr 30 10:01:39 dunno how long it takes Apr 30 10:02:11 wait, what is "qt env"? Apr 30 10:02:11 it is init *before* fork Apr 30 10:02:28 once , not for every program. that is the whole point Apr 30 10:02:34 preinit is launched once and for all Apr 30 10:02:39 init is done for every program Apr 30 10:02:40 :nod: Apr 30 10:02:52 I dont know what should go there for qt Apr 30 10:03:11 instantiating a QApplication ;) Apr 30 10:03:22 in init ? Apr 30 10:03:36 you mean preinit I guess :) Apr 30 10:03:55 yes, preinit Apr 30 10:04:06 yeah, but what about init ? :) Apr 30 10:04:46 bencoh: see http://pastebin.com/364z6i1H Apr 30 10:04:50 booster_gtk_init sets an idler, I wonder why Apr 30 10:05:17 bencoh: maybe we'll need to do some hackery because of the QApplication being singelton Apr 30 10:05:26 or argv parsing Apr 30 10:05:50 hmm Apr 30 10:07:37 please check memory footprint before and after Apr 30 10:08:06 KotCzarny: which memory footprint? parent or child process? Apr 30 10:08:15 both I guess :] Apr 30 10:08:33 shouldnt change much for the child though Apr 30 10:08:37 does that preloader keep apps in memory? Apr 30 10:08:42 no Apr 30 10:08:46 when it inits them all Apr 30 10:08:54 it keeps libraries in memory Apr 30 10:09:26 ok, then check how much it stores, wouldnt help if system has to swap more Apr 30 10:09:28 however, /me needs some food, bbl Apr 30 10:09:31 libraries, and its own copy of initialized structures (that's the point of it) Apr 30 10:09:42 :nod: Apr 30 10:10:05 (because library objects are already taken care of by ld) Apr 30 10:10:08 KotCzarny: we don't really car if it swaps more, as long as apps launch faster Apr 30 10:10:13 *care Apr 30 10:10:19 ... Apr 30 10:10:29 but then multitasking suffers Apr 30 10:11:34 suffers as in? I'd prefer to have clock-ui launched in 2 seconds instead of 6, no matter that browser in background will have 1 second delay Apr 30 10:11:56 as in swapping in and out Apr 30 10:12:08 actually it depends on what you're swapping Apr 30 10:12:08 flash is slow Apr 30 10:12:37 and i would really want more free ram than having clock ran 4s faster Apr 30 10:12:50 KotCzarny: also, keep in mind that more things in swap doesn't necessarily mean more lag Apr 30 10:13:01 KotCzarny: wrong, you don;t need free RAM Apr 30 10:13:10 what you need is used memory ;) Apr 30 10:13:14 let's say a page with only memleaked structures gets swapped ... you'll never try to access it, so it's not an issue (apart from eating swap) Apr 30 10:13:23 correct Apr 30 10:13:35 but if you happen to access a variable in this page ... you're doomed Apr 30 10:13:42 you'll keep swapping back and forth Apr 30 10:14:24 what we need to do is to check launcherd mamory usage *before* and *after* qt booster Apr 30 10:14:29 *memory Apr 30 10:14:39 i dont mind swapping on pc, but on n900 flash wears out Apr 30 10:14:50 that is also a concern to me Apr 30 10:14:54 ooh Apr 30 10:14:59 well then, swap on microsd ;) Apr 30 10:15:10 :nod: Apr 30 10:15:12 :) Apr 30 10:15:16 :) Apr 30 10:15:17 * freemangordon_ is afk Apr 30 10:15:44 isnt microsd unmounted when usb connects? Apr 30 10:16:03 *doom* Apr 30 10:19:56 not exactly Apr 30 11:20:09 KotCzarny: what is unmounted, is what was previously mounted. swap is never mounted Apr 30 11:26:07 but if i undestand how it's shared, WHOLE card is shared as a single block device, so any partition cant be used Apr 30 11:28:56 KotCzarny: no, at least in CSSU, only the first fat partition is exported Apr 30 11:29:20 that has positive and negative sides Apr 30 11:29:26 sure Apr 30 11:29:42 but you have no problems if swap is on uSD Apr 30 12:09:27 hi Apr 30 15:37:11 bencoh: "Apr 30 18:23:14 Nokia-N900 maemo-launcher[16457]: opening of /usr/bin/worldclock.launch took 644745 usec " :) Apr 30 15:37:25 still no qt accel though Apr 30 15:37:35 oh Apr 30 15:37:38 only gtk and cpp Apr 30 15:37:41 well I have a patch here but havent tried it Apr 30 15:37:49 what for? Apr 30 15:38:02 qt accel in maemo-launcher Apr 30 15:38:22 http://pastebin.notk.org/pastebin.php?show=d2fecc06e Apr 30 15:39:27 I dunno why I have a strange error when including QMaemo5Style so it's commented out for now Apr 30 15:39:48 what error? Apr 30 15:40:09 btw i made a similar patch to yours, without actual code though Apr 30 15:40:20 http://pastebin.notk.org/pastebin.php?show=d4822ee03 Apr 30 15:40:20 with only enabling qt-booster Apr 30 15:41:06 bencoh: you're missing a lot of defines Apr 30 15:41:09 I looked at the gtkmm-booster, it doesnt do anything in preinit Apr 30 15:41:14 oh okay Apr 30 15:41:28 I've never used QMaemo5Style, so ... :) Apr 30 15:42:01 or do you mean, Qt defines ? Apr 30 15:42:21 yes Apr 30 15:42:35 see the trickery I did https://github.com/community-ssu/feedservice-plugin-fb-common/blob/master/src/oauth/Makefile.am Apr 30 15:42:54 ugly. Apr 30 15:42:54 :) Apr 30 15:43:05 yeah, I know Apr 30 15:43:06 qmake yay .... :) Apr 30 15:43:20 but did not find other way to get platform qmake defines Apr 30 15:43:35 I might be missing -DQT_GUI_LIB -DQT_CORE_LIB Apr 30 15:43:51 and several others :) Apr 30 15:44:02 think so ? dunno Apr 30 15:44:08 I am sure Apr 30 15:44:12 hacking software - ultimate geek game Apr 30 15:44:16 :) Apr 30 15:44:55 tbh I dont really like qt, so ... ;) Apr 30 15:45:18 -D_REENTRANT -DQT_GL_NO_SCISSOR_TEST -DQT_DEFAULT_TEXTURE_GLYPH_CACHE_WIDTH=1024 -DQT_NO_DEBUG -DQT_MAEMO5_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED Apr 30 15:45:37 that's just an example Apr 30 15:45:50 tbh I like it :) (qt) Apr 30 15:46:18 looks like a lot of libs being loaded Apr 30 15:47:04 ok, lets try with qt booster Apr 30 15:52:25 "Jan 2 06:15:48 Nokia-N900 maemo-launcher[2099]: opening of /usr/bin/worldclock.launch took 110321 usec" Apr 30 15:53:06 ok, lets see what will happen if we have qapplication instance :) Apr 30 16:18:43 bencoh: qmameo5style error can be workarounded if you change the header files order :) Apr 30 16:19:04 meh :( Apr 30 16:23:37 hmm, ok, qith qapplication in booster-qt, hildon-desktop won't start :D Apr 30 16:23:41 *with Apr 30 16:34:09 huhu Apr 30 16:34:13 I was afraid of that Apr 30 16:36:16 rescueos to the rescue :) Apr 30 16:36:52 yeahhhhhhhhhhh Apr 30 16:36:58 wooops, silly bug. "yeah" :) Apr 30 16:37:55 maybe we should fork another maemo-launcher with qt only Apr 30 16:38:06 hmm, why? Apr 30 16:38:17 will only waste resources Apr 30 16:38:41 it will need gtk and cpp boosters as well Apr 30 16:38:59 did someone say fork? Apr 30 16:39:04 ;) Apr 30 16:39:17 oh Apr 30 16:39:19 :) Apr 30 16:42:08 ooh: "Maemo applications must be run with the run-standalone.sh script!" Apr 30 16:46:27 "maemo-launcher: opening of /usr/bin/worldclock.launch took 71228 usec" Apr 30 17:30:05 wait, what ? 71ms ? Apr 30 17:30:44 freemangordon: what did you change ? Apr 30 17:30:52 (to make hildon-desktop start) Apr 30 17:35:24 disabled qt booster, then started maemo-launcher from terminal (with qt booster enabled) Apr 30 17:35:33 to achieve those 71 ms Apr 30 17:35:49 oh, okay Apr 30 17:36:10 and the 110321 usec was with qtbooster but without qapplication in preinit() ? Apr 30 17:36:18 yes Apr 30 17:36:29 but actually it is qcoreapplication now Apr 30 17:36:32 and 644745 usec with cpp ? Apr 30 17:36:35 otherwise bad things happen Apr 30 17:36:41 yes Apr 30 17:36:43 oh, sad ... okay Apr 30 17:36:46 cpp+gtk Apr 30 17:36:48 well Apr 30 17:36:54 well, 71 is not that bad Apr 30 17:37:00 it's great Apr 30 17:37:06 actually the UI appears in 1.5s Apr 30 17:37:10 but 110321 isnt bad either, if hildon-desktop works Apr 30 17:37:24 1.5s vs ... ? Apr 30 17:37:27 but with some more smoke and mirrors... it will look great :D Apr 30 17:37:34 vs 3-5 Apr 30 17:37:34 110321 is 0.1s Apr 30 17:37:52 yeah we know that Apr 30 17:38:00 :) Apr 30 17:38:17 drat, those changing contexts Apr 30 17:38:28 1.5s is the perceived time between "click on icon" and "woohoo, window popped" I suppose Apr 30 17:38:39 bencoh: I guess you can check the vs by symply starting worldclock :P Apr 30 17:38:49 bencoh: yes Apr 30 17:38:50 freemangordon: cssu-stable here ;) Apr 30 17:38:55 oh Apr 30 17:38:55 it's blazing fast Apr 30 17:38:56 ;p Apr 30 17:39:00 how fast? Apr 30 17:39:03 (worldclock) Apr 30 17:39:05 lemme see Apr 30 17:39:12 where do you run it from ? hildon-status-menu ? Apr 30 17:39:15 yes Apr 30 17:39:21 "clock and alarms" Apr 30 17:39:49 hm more than 2sec I'd say Apr 30 17:39:57 maybe not that fast :) Apr 30 17:40:22 :) Apr 30 17:40:26 yeah a bit more than 2sec Apr 30 17:40:27 how much? 2s? Apr 30 17:40:31 yeah Apr 30 17:40:59 KotCzarny: cssu on your device? Apr 30 17:41:02 did you rebuild worldclock ? Apr 30 17:41:20 nope, stock Apr 30 17:41:22 yes, ofc Apr 30 17:41:50 bencoh: BTW, is UI responsive right after it appears? Apr 30 17:43:20 or you are presented a screenshot? Apr 30 17:43:54 it's responsive Apr 30 17:44:38 ok Apr 30 17:46:50 I dont think I've ever seen a "screenshot" Apr 30 17:59:44 what's a decent jabber client that's not Contacts? Apr 30 17:59:58 pidgin ? Apr 30 18:36:35 I like how jabber works with Contacts TBH. Apr 30 18:43:33 it's probably one of the few mobile OSes to do IM right Apr 30 18:43:37 (along with webOS) Apr 30 18:43:49 SMS, Skype, XMPP, Facebook convos all with one consistent UI Apr 30 19:04:05 freemangordon: btw, when I said "cssu-stable" I was implying I'm still using stock worldclock ... dunno if that was clear :) Apr 30 19:05:59 yeah Apr 30 19:28:02 what i dislike about n900 is low battery situations Apr 30 19:28:42 just now i didnt check battery level and received a call, obviously it turned itself off after few secs Apr 30 19:28:55 but now it cant turn on unless charged for how long? Apr 30 19:29:02 1-2 mins is not enough Apr 30 19:29:35 KotCzarny: replace your battery Apr 30 19:29:46 nope, its not that Apr 30 19:29:57 that situation is since i got it Apr 30 19:30:16 when battery was brand new it behaved same way Apr 30 19:30:16 it is, unless you've been warned a couple of thimes that your battery is low Apr 30 19:30:22 *times Apr 30 19:30:42 how old is that battery? Apr 30 19:30:45 i probably was, but phone was unused whole day Apr 30 19:30:51 s/i/it/ Apr 30 19:30:52 KotCzarny meant: it probably was, but phone was unused whole day Apr 30 19:31:16 so? how old is the battery? Apr 30 19:31:17 so 'battery low' was probably displayed, just didnt get a chance to see it Apr 30 19:31:21 2009 ? Apr 30 19:31:23 :) Apr 30 19:31:32 oh, sure, it is not the battery ;) Apr 30 19:31:53 i get solid 5-6 days of standby still Apr 30 19:32:09 KotCzarny: you're aware that internal battery resistance increases with time? Apr 30 19:32:14 yes Apr 30 19:32:19 standby does not matter Apr 30 19:32:40 yes, but still im talking about something else Apr 30 19:32:58 so, when you receive a phone call, with that increased resistance, the voltage drops bellow emergency shutdown level. Apr 30 19:33:20 im not talking about powering off, because most likely it was already at the red bar Apr 30 19:33:27 im talking about trying to turn it on Apr 30 19:33:40 I can turn it on instantly after attaching charger Apr 30 19:33:40 and mind you, it was the same story even when new Apr 30 19:33:51 ShadowJK_: me too Apr 30 19:33:54 heh Apr 30 19:34:05 polarcell here, ~1 yo Apr 30 19:34:37 apparently it stops chargine on reboot/boot Apr 30 19:34:43 and powerkernel boots twice Apr 30 19:35:00 and yellow light turn off during boot Apr 30 19:35:12 KotCzarny: trust me, just replace your battery. with powercell, ~1600 mAh Apr 30 19:35:49 KotCzarny: bootloader charges up to a threshold(voltage), after which it boots the linux kernel. Apr 30 19:35:59 nah, if i'll be replacing i will get double cap one Apr 30 19:36:03 already got the cover Apr 30 19:36:04 :) Apr 30 19:36:22 but because your battery is with decreased capacity, it can;t hod until bme is started Apr 30 19:36:27 *hold Apr 30 19:36:41 ShadowJK_: correct? ^^^ Apr 30 19:36:46 why cant it just run on charger power? Apr 30 19:36:53 droid can Apr 30 19:37:21 heh Apr 30 19:37:23 and i think its the reason why n900 cant run without battery Apr 30 19:37:58 because n900 *does not* know what tpe of charger it is attached to Apr 30 19:38:03 before bme runs Apr 30 19:38:06 Electrically it can run without battery, though not on 2G unless you sit right next to celltower Apr 30 19:39:12 ShadowJK_: you can turn on n900 without battery? Apr 30 19:39:37 It turns on, software sees battery is missing, and turns off ;) Apr 30 19:39:46 heh Apr 30 19:50:36 and another thing that irks me is usb port on the top (when talking) Apr 30 20:35:42 polarcell <3 Apr 30 20:35:57 but they're 1500mAh, not 1600mAh ... at least for mine Apr 30 20:38:04 mine is > 1600, if we should trus bq chip Apr 30 20:38:32 lucky :) Apr 30 20:38:48 bq says ~1490-ish Apr 30 20:53:11 last measured discharge on mine is 1185 Apr 30 20:53:14 :) Apr 30 20:54:02 KotCzarny: oh, just like a new battery :) Apr 30 20:54:08 :) Apr 30 20:54:15 - internal resistance Apr 30 20:54:28 but yes, quite a lot after 6 years for a liion Apr 30 23:09:37 my desktop graphics card just seemed to die today... updated drivers and stuff to no avail :( Apr 30 23:09:50 Then I read about baking them... Apr 30 23:10:16 so aluminium foil around it and 30 mins later at ~125° C - it works again!!! Apr 30 23:10:27 temporary solution Apr 30 23:10:30 * Win7Mac is very impressed Apr 30 23:10:32 it will die again Apr 30 23:10:42 :( Apr 30 23:11:00 bad solder Apr 30 23:11:04 bad design Apr 30 23:11:40 Gigabyte GTX 470OC Apr 30 23:12:08 no warranty? Apr 30 23:12:21 ~4 years old Apr 30 23:13:42 how much time am I supposed to gain before it dies again? Apr 30 23:13:56 may be days, may be months Apr 30 23:15:56 if reballing costs less than 1/4 of the card do it, otherwise just buy new card Apr 30 23:17:46 found this Apr 30 23:17:51 whoops Apr 30 23:17:55 ignore that Apr 30 23:17:56 :D Apr 30 23:18:10 Win7Mac i did a ghetto ass reflow on my GTX 470, it lasted 6 months Apr 30 23:18:29 guess ill have to look for a new card then Apr 30 23:18:32 then it died again, did another reflow, and ran out of thermal paste Apr 30 23:18:39 so i dont know if it still works Apr 30 23:18:44 too lazy to put some new paste in there Apr 30 23:18:53 ghetto ass reflow? Apr 30 23:18:57 baking Apr 30 23:18:58 :) Apr 30 23:19:07 :) Apr 30 23:19:12 not on the oven Apr 30 23:19:29 i dont know the name but uh, i happen to have a "heat" gun? Apr 30 23:19:48 i have to set it on one of the lowest levels or the whole thing melts Apr 30 23:20:04 hehe Apr 30 23:20:25 6 months was still nice Apr 30 23:20:25 I have a heat gun used for paint stripping, its fan was strong enough to blow off a surface mount PCB I was testing it on... heh Apr 30 23:20:28 baking (oven) is more even i guess Apr 30 23:20:50 yeah, some say to apply more heat on the "main" chip tho, i don't know Apr 30 23:20:51 and no real reflow Apr 30 23:21:46 oh just scrolled and saw that you also had a GTX 470 lol Apr 30 23:22:06 yeah Apr 30 23:22:07 i had mine clocked to 800/1900 :x Apr 30 23:22:24 mine is OCed by factary Apr 30 23:22:35 *factory Apr 30 23:26:15 and is suppused to have a superb thermal design called "windforce"... Apr 30 23:26:36 how long did your video cards last before they croaked? Apr 30 23:26:56 so far it's like they last 2 years for me... Apr 30 23:27:04 not really much longer i guess Apr 30 23:27:21 though this RadeonHD 5770 has survived a bit so far... forgot when I bought it Apr 30 23:27:22 ~4years Apr 30 23:27:33 thats about the same mine lasted Apr 30 23:27:41 i hope it still works but... lazyness **** ENDING LOGGING AT Fri May 01 02:59:59 2015