**** BEGIN LOGGING AT Thu Aug 30 03:00:01 2012
Aug 30 06:38:56 <DocScrutinizer05> Estel_: If I ever hear threats again from you, I swear YOU gonna die (as user of this chan)
Aug 30 06:43:20 <freemangordon> DocScrutinizer51: how do you read http://www.ti.com.cn/cn/lit/ug/swcu050g/swcu050g.pdf, p. 477
Aug 30 06:43:51 <freemangordon> DocScrutinizer05: the part "TH05 – 3H103F thermistor resistance variation as a
Aug 30 06:43:51 <freemangordon> function of temperature.
Aug 30 06:44:21 <freemangordon> http://www.mmc.co.jp/adv/dev/csv_pdf/TH05/TH05-3H103F.pdf
Aug 30 06:47:30 <DocScrutinizer05> Estel_: busybox-power *is* optional and it will stay optional. If you don't like this, go and create your own fork where you can play dictator of your users, instead of offering them freedom of choice
Aug 30 06:51:47 <DocScrutinizer05> Estel_: btw this is a topic for #maemo-ssu, aka OT in here basically
Aug 30 06:59:55 <freemangordon> ~seen zeq
Aug 30 07:00:17 <freemangordon> ~ping
Aug 30 07:00:47 <freemangordon> DocScrutinizer05: seems like bot is still sleeping :)
Aug 30 07:01:10 <DocScrutinizer05> infobot impersonation can't log in
Aug 30 07:01:16 <DocScrutinizer05> unclear reasons
Aug 30 07:01:40 <DocScrutinizer05> ~chaninfo
Aug 30 07:01:42 <apt> 14/120 channels, 2043 users, 1855 unique: #debian/1173, #kde/347, #maemo/269, #openmoko/85, #openmoko-cdevel/63, #htc-linux/52, ##guleague/12, #debianppc/12, #debian-bots/10, #debian-france/7, #elive/5, #lugwv/4, ##icf/2, #linuxpakistan/2
Aug 30 07:02:56 <freemangordon> DocScrutinizer05: anyway THS05-3H103F thermistor is mentioned several times in twl TRM, could we assume that is the thermistor (for batt temp) in n900? though the table is different from the one in 3430sdp.s
Aug 30 07:03:12 <freemangordon> 3430sdp.c
Aug 30 07:03:45 <LaoLang_cool> any good news for maemo and maemo-ssu?
Aug 30 07:03:59 <freemangordon> yep, they are still alive
Aug 30 07:04:47 <kerio> freemangordon: "alive"
Aug 30 07:05:11 <freemangordon> kerio: aren't thay?
Aug 30 07:05:19 <freemangordon> *they
Aug 30 07:05:25 <LaoLang_cool> freemangordon, wow!
Aug 30 07:05:37 * freemangordon is still having his morning coffee
Aug 30 07:06:08 <kerio> freemangordon: well, only -thumb used to fit that description
Aug 30 07:06:13 <kerio> but it stopped too
Aug 30 07:06:27 <DocScrutinizer05> freemangordon: Nokia might have picked another thermistor for various reasons
Aug 30 07:06:38 <freemangordon> kerio: too bad :P. Any clue why it stopped?
Aug 30 07:07:01 <freemangordon> DocScrutinizer05: yeah, so the only option is polinomial then :(
Aug 30 07:08:20 <DocScrutinizer05> why do you think we'd need a friggin complex polynomial when we could just adjust the lookup table
Aug 30 07:08:24 <freemangordon> DocScrutinizer05: is that thermistor inside the battery?
Aug 30 07:08:31 <DocScrutinizer05> no
Aug 30 07:08:44 <DocScrutinizer05> apt: quit
Aug 30 07:09:17 <kerio> freemangordon: idk, the maintainer got bored or something
Aug 30 07:09:50 <DocScrutinizer05> infobot: wb
Aug 30 07:09:51 <infobot> thx
Aug 30 07:10:13 <freemangordon> DocScrutinizer05: yes, but we need about 60 points
Aug 30 07:12:08 <DocScrutinizer05> ~chaninfo
Aug 30 07:12:08 <infobot> 124/124 channels, 4881 users, 3467 unique: #debian/1172, #kde/344, #maemo/269, #gsoc/214, #meego/191, #asterisk/185, #harmattan/182, #wowuidev/159, #oe/140, #wowace/124, #webos-internals/105, #wowhead/95, #arm-netbook/86, #openmoko/85, #n9/68, #utah/67, #uclibc/67, #bzflag/64, #openmoko-cdevel/63, #tomcat/56, #qi-hardware/55, #edev/54, #curseforge/54, #htc-linux/52, #maemo-ssu/49, #sc2mapster/45, #asterisk-dev/43, #elinux/42, #/34, #slug/34, ...
Aug 30 07:17:36 <DocScrutinizer05> freemangordon: p477 on http://www.ti.com.cn/cn/lit/ug/swcu050g/swcu050g.pdf  ??
Aug 30 07:19:36 <DocScrutinizer05> freemangordon: can't find your quoted text there
Aug 30 07:21:42 <freemangordon> DocScrutinizer05: sorry, my bad, a typo, it is 474
Aug 30 07:22:56 <freemangordon> also look at p. 456
Aug 30 07:24:09 <DocScrutinizer05> that's what I do right now
Aug 30 07:24:12 <freemangordon> THS05-3H103F looks more than recommendation
Aug 30 07:24:17 <DocScrutinizer05> yep
Aug 30 07:24:33 <freemangordon> thus my question "could we assume"
Aug 30 07:25:00 <DocScrutinizer05> seems it's mandatory since I fail to see a way to configure automatic emergency shutdown at "right" temperature, when using other component
Aug 30 07:25:14 <freemangordon> yes
Aug 30 07:25:24 <DocScrutinizer05> yes, so we can assume
Aug 30 07:25:28 <freemangordon> irqs too
Aug 30 07:25:50 <DocScrutinizer05> dunno if irq, shutdown, both, or self-destruction ;-)
Aug 30 07:25:58 <freemangordon> hehe
Aug 30 07:26:02 <DocScrutinizer05> just had a cursory read
Aug 30 07:26:18 <freemangordon> yeah, same here, but it looks like a mandatory part
Aug 30 07:26:23 <DocScrutinizer05> yep
Aug 30 07:26:57 <freemangordon> well, it seems my work on BCI driver won't be in vain
Aug 30 07:27:14 <DocScrutinizer05> unless manufacturer accepts different shutoff/irq-trigger temperature for bat
Aug 30 07:27:39 <freemangordon> I think to add temp reading functionality to the driver, solving BME replacement issue
Aug 30 07:27:51 <DocScrutinizer05> :nod:
Aug 30 07:28:08 <freemangordon> ok, going afk, bbl
Aug 30 07:28:13 <DocScrutinizer05> o/
Aug 30 07:28:18 * DocScrutinizer05 away too
Aug 30 07:33:22 <DocScrutinizer05> Estel_: best "motivation" of cssu-team would be YOU stopping this useless bitching
Aug 30 07:33:52 <ZogG_laptop> who was trying to switch memory chip on n900, as someeone did on n9 :P
Aug 30 07:35:07 <DocScrutinizer05> ZogG_laptop: different story
Aug 30 07:35:39 <DocScrutinizer05> ZogG_laptop: N900 already comes with 32GB eMMC
Aug 30 07:36:01 <DocScrutinizer05> on N9 you could swap the 16GB for 64GB, I'm sure
Aug 30 07:38:15 <DocScrutinizer05> Estel_: if this is any comedy, then because you're giving the clown here. Stop that and everybody will be fine
Aug 30 07:39:07 <kerio> wait, what?
Aug 30 07:39:19 <kerio> when did Estel_ talk?
Aug 30 07:39:25 <ZogG_laptop> i missed the clown part, was it earlier or my smart lag connection speed does ignore for me all unneeded parts?
Aug 30 07:39:41 <DocScrutinizer05> Estel_: if that makes you happy: i'm also not convinced we should get portrait support to busybox-basic
Aug 30 07:39:58 <kerio> oh, still that old one
Aug 30 07:40:05 <DocScrutinizer05> but it has way less risk that replacing busybox-basic by busybox-power
Aug 30 07:40:45 <DocScrutinizer05> s/that/than/
Aug 30 07:40:48 <infobot> DocScrutinizer05 meant: but it has way less risk than replacing busybox-basic by busybox-power
Aug 30 07:42:50 <kerio> DocScrutinizer05: fwiw busybox-power comes directly from upstream, and it's been heavily tested by all sorts of people
Aug 30 07:43:12 <DocScrutinizer05> plus it's actually scatching an itch, while power enhancements are useless from a cssu perspective
Aug 30 07:44:14 <DocScrutinizer05> kerio: irrelevant, it evidently eats half a megabyte in rootfs, and that's already enough to not include it for the shits'n'giggles, when everybody can as well get it as optional package already
Aug 30 07:44:59 <kerio> DocScrutinizer05: the optional package is an unholy abomination
Aug 30 07:45:23 <DocScrutinizer05> kerio: then fix that unholy abomination, why would CSSU care?
Aug 30 07:45:37 <kerio> it can't be fixed, it needs to replace /bin/busybox in some way
Aug 30 07:45:46 <DocScrutinizer05> no, it doesn't
Aug 30 07:45:59 <DocScrutinizer05> does bash need to replace anything?
Aug 30 07:46:08 <kerio> it needs to replace bash, surely
Aug 30 07:46:14 <kerio> much like busybox needs to replace busybox
Aug 30 07:46:14 <DocScrutinizer05> BS
Aug 30 07:46:32 <DocScrutinizer05> this however is busybox-power
Aug 30 07:46:47 <DocScrutinizer05> the name alone already suggests it's not a busybox replacement
Aug 30 07:46:54 <kerio> it's busybox
Aug 30 07:47:39 <kerio> BusyBox v1.20.2 (Debian 1.20.2power1) multi-call binary.
Aug 30 07:48:23 <DocScrutinizer05> I'll stop this shit now, since it really becomes comedy. All been discussed ad nauseum, and nothing to add to the given arguments. In my book the arguments NOT to mess with busybox-basic for the benefit of busybox power fanboys are stronger than the emotional arguing of estel et al
Aug 30 07:49:44 <DocScrutinizer05> if you want busybox-power, install it. If you don't like the busybox-power package, then fix or stay away from it. Stop pestering CSSU about that package
Aug 30 07:50:27 <ZogG_laptop> Woody14619, ping
Aug 30 07:50:33 <DocScrutinizer05> honestly there's nothing CSSU can do for you, that you couldn't already do on your own, without CSSU getting involved at all
Aug 30 07:52:30 <DocScrutinizer05> ETX with messybox-power and CSSU now. Definitely
Aug 30 07:56:05 * kerio ponders whether or not to say that thumbified busybox-power only adds 300k to the stock busybox
Aug 30 07:56:09 * kerio decides against it
Aug 30 07:58:02 <DocScrutinizer05> ((<estel_> ... It's really unexplainable, why busybox-power is kept out of CSSU.)) The only unexplainable thing is the way your brain refuses to grok sound arguments and refrains to repeating same shit over and over again. Sometimes you sound like a parrot or a defective gramophone
Aug 30 08:40:49 <LaoLang_cool> How to set default time zone and time on maemo? If I took battery out for a long time, then after turn maemo on, I have to choose time and timezone again
Aug 30 08:43:17 <LaoLang_cool> I foiund a file /etc/clock.d/clockd-settings.default, but configuring it has no any effect.
Aug 30 08:43:23 <LaoLang_cool> s/foiund/found/
Aug 30 08:43:23 <infobot> LaoLang_cool meant: I found a file /etc/clock.d/clockd-settings.default, but configuring it has no any effect.
Aug 30 08:44:45 <StyXman_> LaoLang_cool: I just skip the dialog and use ntp to resync
Aug 30 08:45:08 <LaoLang_cool> StyXman_, but I have to change default time zone
Aug 30 08:45:15 <StyXman_> I think the TZ is properly saved
Aug 30 08:45:31 <StyXman_> at least in my case, it does
Aug 30 08:45:35 <DocScrutinizer05> should
Aug 30 08:45:55 <StyXman_> maybe /etc/timezone ?
Aug 30 08:46:59 <LaoLang_cool> StyXman_, no, if the battaery tooken out for a long time (> 20 second maybe), you have to reset them
Aug 30 08:47:35 <LaoLang_cool> StyXman_, no such file /etc/timezone here..
Aug 30 08:47:39 <LaoLang_cool> cssu stable version
Aug 30 08:48:13 <DocScrutinizer05> there's something a bit special about timezone settings n maemo - I mean not like usual on linux
Aug 30 08:49:43 <DocScrutinizer05> lrwxrwxrwx    1 root     root           33 Aug 28 11:15 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin
Aug 30 08:49:44 <DocScrutinizer05> lrwxrwxrwx    1 root     root           29 Aug 28 11:15 /etc/localtime.save -> /usr/share/zoneinfo/Etc/GMT-2
Aug 30 08:51:12 <kerio> maemo is very special, yeah
Aug 30 08:51:30 <DocScrutinizer05> don't create/edit /etc/localtime as it will get replaced by a link again, next time you save that locale-picker dialog
Aug 30 08:52:12 <DocScrutinizer05> o/
Aug 30 08:55:06 <LaoLang_cool> no matter how /etc/localtime, after took batery out for a long time, n900 will restore to it's default time zone
Aug 30 08:55:21 <LaoLang_cool> I have to reset the timezone and time
Aug 30 08:56:43 <StyXman_> DocScrutinizer05: that means that if we point /etc/localtime.save to our tz it should recover perfectly?
Aug 30 08:57:34 <StyXman_> I have both pointing to the right TZ
Aug 30 08:57:48 <StyXman_> /u/s/zi/Europe/Paris
Aug 30 08:58:07 <LaoLang_cool> oh, I should try it, they points to different timezone in my maemo
Aug 30 09:30:01 <kerio> i have both to Europe/Rome
Aug 30 11:12:37 <DocScrutinizer51> infobot: CHANINFO
Aug 30 11:12:37 <infobot> 124/124 channels, 5059 users, 3605 unique: #debian/1204, #kde/375, #maemo/281, #gsoc/227, #meego/200, #asterisk/190, #harmattan/187, #wowuidev/163, #oe/153, #wowace/129, #webos-internals/107, #wowhead/95, #arm-netbook/89, #openmoko/85, #n9/71, #openmoko-cdevel/69, #utah/67, #uclibc/65, #tomcat/60, #bzflag/59, #qi-hardware/59, #htc-linux/57, #curseforge/56, #edev/54, #maemo-ssu/53, #asterisk-dev/46, #sc2mapster/44, #flow3/41, #elinux/41, #slug/36, ...
Aug 30 11:15:25 <ZogG_laptop> asterisk :P interesting
Aug 30 11:21:27 <DocScrutinizer51> hmm?
Aug 30 11:22:15 <DocScrutinizer51> what's so special about #asterisk ?
Aug 30 11:23:27 <DocScrutinizer51> way more interesing: #maemo on position 3 again
Aug 30 11:32:55 <vdv> hi all
Aug 30 11:34:11 <vdv> need help. i've tried the solution given in post http://talk.maemo.org/showpost.php?p=763902&postcount=7 to lock device on startup. expected behaviour is, that after hildon-desktop is started autolock must be disabled, but it still stays active
Aug 30 11:34:55 <vdv> i.e. pre-stop script doesn't work there
Aug 30 11:35:38 <vdv> running "/usr/bin/gconftool -s -t bool /system/osso/dsm/locks/devicelock_autolock_enabled false" from terminal manually disables autolock
Aug 30 11:35:54 <vdv> what's wrong there?
Aug 30 12:13:43 <kerio> DocScrutinizer51: asterisk is special because nobody knows how to make it work
Aug 30 12:15:12 <DocScrutinizer51> vdv: run-standalone.sh ?
Aug 30 12:15:40 <vdv> DocScrutinizer05, i've just noticed that event script actually works
Aug 30 12:15:56 <vdv> but setting is overwrriten
Aug 30 12:16:14 <vdv> if i access hildon menu
Aug 30 12:16:37 <DocScrutinizer51> vdv: I duno which user is running the pre-stop script, but gconftool is user specific
Aug 30 12:17:18 <vdv> i.e. script turns off autolock, but if i go to settings to look whether autolock is disabled or not, it turns on again
Aug 30 12:17:55 <DocScrutinizer51> hmmm
Aug 30 12:18:40 <DocScrutinizer51> strace settings
Aug 30 12:19:02 <vdv> huh?
Aug 30 12:19:37 <DocScrutinizer51> it seems it stores the state either internally (in that case you'd need to kill -o the process immediately after gconftool call)
Aug 30 12:20:15 <DocScrutinizer51> or it has another gconf key or even other file to stroe the state, the you should change it there
Aug 30 12:24:22 <vdv> DocScrutinizer05, yeah, but i can't just strace settings, too abstract suggestion :D
Aug 30 12:25:05 <vdv> and either of two cases are for me obvious too :)
Aug 30 14:08:23 <vdv> interesting, is it safe to modify file "/etc/osso-af-init/gconf-dir/system/osso/dsm/locks/%gconf.xml"? :)
Aug 30 14:08:35 <vdv> wont that brick my n900? :)
Aug 30 14:09:20 <vdv> i've removed entry there: "<entry name="touchscreen_keypad_autolock_enabled" mtime="1284131142" schema="/schemas/system/osso/dsm/locks/touchscreen_keypad_autolock_enabled"/>"
Aug 30 14:10:03 <chem|st> vdv: you should not alter gconf by hand... use gconftool-2
Aug 30 14:10:34 <vdv> if i only knew how :)
Aug 30 14:10:46 <chem|st> gconftool-2 --help
Aug 30 14:11:16 <chem|st> it is like a directory/file tree
Aug 30 14:11:21 <vdv> what's the difference between gconftool and gconftool-2?
Aug 30 14:12:11 <vdv> i disable autolock with gconftool -s -t bool /system/osso/dsm/locks/devicelock_autolock_enabled false
Aug 30 14:12:13 <chem|st> no idea (version age compatibility who knows? why bother)
Aug 30 14:12:26 <vdv> but that setting is overwritten
Aug 30 14:12:46 <vdv> when i enter settings->device lock
Aug 30 14:13:04 <chem|st> vdv: sure it is...
Aug 30 14:13:29 <chem|st> vdv: why do you want to alter it in gconf anyway?
Aug 30 14:13:44 <chem|st> do you want to automate something?
Aug 30 14:13:52 <vdv> chem|st, http://talk.maemo.org/showthread.php?p=763902#post763902
Aug 30 14:13:59 <vdv> yes
Aug 30 14:14:10 <vdv> i want to lock device on startup
Aug 30 14:14:42 <vdv> and it's done with enabling/disabling autolock temporarely in init script
Aug 30 14:15:09 <vdv> but some process reenables autolock after hildon start
Aug 30 14:15:18 <vdv> and also when i enter settings
Aug 30 14:16:04 <vdv> chem|st, i've removed entry from %gconf.xml and seems it has desirable effect
Aug 30 14:16:04 <chem|st> does that actually work?
Aug 30 14:16:20 <vdv> yes, locking at startup works
Aug 30 14:16:40 <vdv> the only problem is annoying autolock when device is on
Aug 30 14:17:06 <chem|st> well if it isn't there anymore the program using its entry might segfault or halt or zombie or bootloop... if it is just being silent good...
Aug 30 14:17:55 <chem|st> vdv: if your startupscript stuff makes it happen then you might start there to have a look for mistakes not the other way round
Aug 30 14:18:34 <vdv> don't understand last idea
Aug 30 14:18:35 <chem|st> the device is not automagically setting the device lock
Aug 30 14:19:27 <chem|st> it is not disabled in the first place and something is holding on to the enabled setting
Aug 30 14:19:32 <chem|st> ?
Aug 30 14:20:02 <vdv> chem|st, so, in general, you think, that modifying /etc/osso-af-init/gconf-dir/system/osso/dsm/locks/%gconf.xml is not a good idea, right?
Aug 30 14:20:09 <chem|st> right
Aug 30 14:20:24 <vdv> and altering that via gconftool-2 too
Aug 30 14:20:46 <chem|st> and do not use the autolock function... initiate the "you are locked" state instead
Aug 30 14:21:19 <vdv> via direct dbus call?
Aug 30 14:21:52 <chem|st> or set the timeout to something within days so it does not happen
Aug 30 14:22:10 <chem|st> how is the lock initiated?
Aug 30 14:22:30 <vdv> this call does that: run-standalone.sh /usr/bin/dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:'com.nokia.mce' string:'/com/nokia/mce/request' string:'com.nokia.mce.request' string:'devlock_callback' uint32:'3'
Aug 30 14:22:51 <vdv> but not sure if i can run it from script in /etc/event.d/
Aug 30 14:23:30 <vdv> with condition "start on startup"
Aug 30 14:24:19 <vdv> can i call run-standalone in early phases during boot?
Aug 30 14:24:26 <vdv> before hildon starts up?
Aug 30 14:25:38 <chem|st> no idea
Aug 30 14:27:08 <kerio> wtf is run-standalone.sh anyway?
Aug 30 14:47:38 <DocScrutinizer51> a scriptie to set some env vars etc that aren't available usually when script doesn't run in interactive user shell
Aug 30 14:48:33 <DocScrutinizer51> less `which run-shandalone.sh`
Aug 30 14:54:13 <vdv> DocScrutinizer05, is it safe to edit /etc/gconf/gconf.xml.defaults/%gconf-tree.xml and remove entry? :)
Aug 30 14:55:13 <vdv> DocScrutinizer51, 
Aug 30 15:34:29 <DocScrutinizer05> vdv: [2012-08-30 14:19:36] <DocScrutinizer51> it seems it stores the state either internally (in that case you'd need to >>>kill -9<<< the process immediately after gconftool call)
Aug 30 15:40:10 <DocScrutinizer05> [2012-08-30 16:24:19] <vdv> can i call run-standalone in early phases during boot? [2012-08-30 16:24:26] <vdv> before hildon starts up?  ###### Nope, you can't lock hildon before it got started
Aug 30 15:41:16 <vdv> DocScrutinizer05, ok thanks
Aug 30 15:41:32 <DocScrutinizer05> dunno what mce does when there's a request to lock the screen while there is no screen to lock
Aug 30 15:42:14 <DocScrutinizer05> anyway, have you had a look to phonecontrol wikipage?
Aug 30 15:44:24 <DocScrutinizer05> http://wiki.maemo.org/Phone_control#Securing
Aug 30 15:47:38 <DocScrutinizer05> vdv: aiui your whole 'problem' is to get a device-lock-code requester on bootup, but not have the device lock automatically later on during normal suage?
Aug 30 15:50:09 <kerio> aw balls, there's no dns2tcp in the repos
Aug 30 15:50:15 <vdv> DocScrutinizer05, exactly
Aug 30 15:51:12 <kerio> who should i pay to get it compiled for me? i *really* don't want to learn how scratchbox works
Aug 30 15:51:13 <vdv> and it works now, if i don't go to settings and open device lock applet 
Aug 30 15:51:22 <kerio> and gcc + glibc-dev won't fit on the rootfs, i'm afraid
Aug 30 15:51:33 <vdv> opening applet breaks the autolock setting
Aug 30 15:51:39 <vdv> sets it to true
Aug 30 15:52:11 <vdv> and if i set it to false from gui, then on next start lock code is not requested
Aug 30 15:52:49 <DocScrutinizer05> vdv: consider this: http://talk.maemo.org/showthread.php?p=763379#post763379
Aug 30 15:54:05 <DocScrutinizer05> vdv: In expression set timeout for autolock to 100h, and consider your problem solved, without any script to run
Aug 30 15:54:06 <vdv> lol, that's exactly the page i've used before
Aug 30 15:54:31 <kerio> DocScrutinizer05: will gcc+glibc-dev fit on the n900's rootfs?
Aug 30 15:55:12 <vdv> DocScrutinizer05, it's not a solution :)
Aug 30 15:55:27 <DocScrutinizer05> vdv: why not?
Aug 30 15:55:53 <DocScrutinizer05> if 100h til device lock are no solution, how's about 10000h then?
Aug 30 15:55:56 <vdv> because after 100 hours it will lock
Aug 30 15:56:11 <DocScrutinizer05> NB the duration is from last interactive event
Aug 30 15:56:15 <vdv> and after 10000h it'll also lock
Aug 30 15:56:30 <vdv> i understand
Aug 30 15:56:43 <vdv> but it's a workaround
Aug 30 15:56:44 <DocScrutinizer05> no it won't since it will never run 10000h without you touching screen or plugging usb or whatever
Aug 30 15:56:58 <vdv> theoretically it can happen
Aug 30 15:57:14 <DocScrutinizer05> no
Aug 30 15:57:18 <kerio> DocScrutinizer05: it won't happen with *your* battery!
Aug 30 15:57:22 <vdv> i hate nokia :) did you what they have written in user guide of n900?
Aug 30 15:57:24 <DocScrutinizer05> unless you got it sitting on charger
Aug 30 15:57:34 <vdv> did you see
Aug 30 15:57:44 <kerio> i didn't know there was a user guide
Aug 30 15:57:57 <vdv> just a moment, i'll give a cite
Aug 30 15:59:17 <vdv> First Start-Up... Switch the device on... If the device asks for a PIN or lock code (!), enter it..
Aug 30 15:59:53 <vdv> damn, n900 don't ask for lock code on startup!
Aug 30 16:00:09 <vdv> it's not designed so, idiots
Aug 30 16:00:19 <kerio> huh? surely it can be configured to do so
Aug 30 16:00:25 <vdv> nope
Aug 30 16:00:40 <vdv> i.e. not so easily
Aug 30 16:00:44 <kerio> \_o_/
Aug 30 16:00:54 <vdv> not by ordinary user
Aug 30 16:01:11 <DocScrutinizer05> sure it will ask for lockcode when lockcode got enabled
Aug 30 16:01:26 <DocScrutinizer05> the whole point of lockcode
Aug 30 16:02:01 <vdv> ups, right, sorry
Aug 30 16:02:18 <vdv> but i can't configure it to ask for lock code ONLY at startup!
Aug 30 16:02:24 <vdv> :)
Aug 30 16:02:33 <vdv> i hate nokia anyway
Aug 30 16:02:47 <kerio> ~nokia
Aug 30 16:02:47 <infobot> it has been said that nokia is a cellphone company from Finland.
Aug 30 16:02:56 <kerio> hm
Aug 30 16:02:57 <kerio> ~elop
Aug 30 16:02:57 <infobot> elop is probably a microsoft spy and one of the most successfull corporate trolls
Aug 30 16:03:03 <kerio> that's better
Aug 30 16:03:12 <vdv> :)
Aug 30 16:03:26 <kerio> infobot: elop is definetely a microsoft spy and one of the most successful corporate trolls
Aug 30 16:03:26 <infobot> ...but elop is already something else...
Aug 30 16:03:28 <kerio> infobot: elop is definetely a microsoft spy and one of the most successful corporate trolls
Aug 30 16:03:35 <kerio> hm
Aug 30 16:03:38 <DocScrutinizer05> you can configure it to ask for lockcode at startup and after 1000h of inactivity
Aug 30 16:03:59 <kerio> infobot: no, elop is definetely a microsoft spy and one of the most successful corporate trolls
Aug 30 16:04:00 <infobot> okay, kerio
Aug 30 16:04:01 <DocScrutinizer05> ~elop
Aug 30 16:04:02 <infobot> it has been said that elop is definetely a microsoft spy and one of the most successful corporate trolls
Aug 30 16:04:10 <DocScrutinizer05> forget elop
Aug 30 16:04:18 <DocScrutinizer05> ~forget elop
Aug 30 16:04:18 <infobot> i forgot elop, DocScrutinizer05
Aug 30 16:04:21 <vdv> i've payed 450$ for that piece of shit.. and i have troubles with it since i've began to use it
Aug 30 16:04:23 <DocScrutinizer05> ~elop
Aug 30 16:04:31 <DocScrutinizer05> ~unforget elop
Aug 30 16:04:31 <infobot> DocScrutinizer05: Successfully recovered 'elop'.  Have fun now.
Aug 30 16:04:35 <DocScrutinizer05> ~elop
Aug 30 16:04:35 <infobot> from memory, elop is definetely a microsoft spy and one of the most successful corporate trolls
Aug 30 16:04:41 <DocScrutinizer05> grrr
Aug 30 16:04:52 <kerio> vdv: aww, don't be like this
Aug 30 16:04:58 <kerio> the n900 is pretty fucking good
Aug 30 16:05:01 <kerio> i mean
Aug 30 16:05:05 <vdv> nope
Aug 30 16:05:09 <kerio> it's awful, but it's lightyears ahead of anything else
Aug 30 16:05:21 <DocScrutinizer05> kerio: you earned a bot-ban for redefining a factoid without even checking it before
Aug 30 16:05:28 <kerio> wait, what?
Aug 30 16:05:38 <kerio> DocScrutinizer05: look up
Aug 30 16:05:51 <DocScrutinizer05> ooh, sorry
Aug 30 16:05:56 <kerio> i most definetely did *not* earn that bot ban
Aug 30 16:06:13 <DocScrutinizer05> yep
Aug 30 16:06:22 <DocScrutinizer05> nm
Aug 30 16:06:22 <kerio> ~botsnack
Aug 30 16:06:22 <infobot> kerio: thanks
Aug 30 16:06:27 <kerio> ~docsmack
Aug 30 16:08:44 <kerio> ooh, i *can* install gcc and libc6-dev
Aug 30 16:08:45 <kerio> neat
Aug 30 16:20:01 <kerio> ah fuck i don't have make
Aug 30 16:20:08 <kerio> oh nvm, it's cheap
Aug 30 16:31:28 <freemangordon> vdv: any chance instead of bashing n900 to open a bug?
Aug 30 16:31:55 <freemangordon> grrr, where is zeq 
Aug 30 16:32:29 <vdv> freemangordon, don't think it make sense
Aug 30 16:32:48 <freemangordon> to file a bug? why is that?
Aug 30 16:33:18 <vdv> n900 users are getting less and less everyday
Aug 30 16:33:38 <freemangordon> hmm, do you have some hard values on that?
Aug 30 16:33:51 <freemangordon> at least their initial count
Aug 30 16:35:51 <vdv> no, just intuitively
Aug 30 16:37:01 <freemangordon> vdv: and how is related the number of users to the chance a bug to be fixed? I don't get it.
Aug 30 16:37:27 <vdv> btw. what bug do you mean?
Aug 30 16:37:56 <freemangordon> the functionality you miss in screen lock
Aug 30 16:38:18 <vdv> don't think it's a bug
Aug 30 16:38:41 <freemangordon> an enhancement falls in the same category
Aug 30 16:39:26 <vdv> there much more serious bugs and enhancements to fix in case of n900 and maemo
Aug 30 16:40:42 <freemangordon> sure, but it won't hurt to open an maybe easy to fix one. The chances are getting real.
Aug 30 16:47:27 <vdv> freemangordon, too demotivated :)
Aug 30 16:48:31 <freemangordon> :)
Aug 30 16:55:18 <kerio> vdv: sounds like a neat CSSU enhancement
Aug 30 16:57:01 <vdv> kerio, messaging app looks ugly in portrait mode :)
Aug 30 16:57:35 <vdv> it has to be scrolled horizontally in order to see all contents
Aug 30 16:58:06 <freemangordon> vdv: there is .css to fix that, search on TMO
Aug 30 16:59:08 <freemangordon> there are at least 10 messaging "themes" supporing portrait
Aug 30 17:00:40 <kerio> freemangordon: hm, why wasn't the default one "fixed" in cssu?
Aug 30 17:00:59 <kerio> btw, what do people use? n-series theme or the orange one?
Aug 30 17:01:08 <freemangordon> NFC, maybe noone knows CSS enough to fix it
Aug 30 17:01:32 <freemangordon> kerio: it is "theme" , not theme ;). Several CSSes
Aug 30 17:01:40 <kerio> k
Aug 30 17:04:12 <kerio> vdv: btw, what smartphone/tablet are you (planning on) using to replace the n900?
Aug 30 17:06:04 <vdv> kerio, i don't know, probably i'll just live further with n900 until it breaks
Aug 30 17:06:15 <kerio> i did that
Aug 30 17:06:19 <kerio> and then i bought another n900
Aug 30 17:06:30 <kerio> but you claim the n900 sucks
Aug 30 17:06:33 <vdv> lol
Aug 30 17:07:03 <vdv> after n900 i'll buy some cheap phone to make calls and send messages
Aug 30 17:07:55 <freemangordon> kerio: could you confirm that new busybox-power-thumb is in the repo?
Aug 30 17:18:34 <freemangordon> ~seen zeq
Aug 30 17:18:38 <infobot> zeq <~s_j_newbu@2a01:348:1e3:1:e6ec:10ff:fe9a:d418> was last seen on IRC in channel #maemo, 7d 23h 56m 52s ago, saying: 'see you later DocScrutinizer05 '.
Aug 30 17:18:46 <freemangordon> ~seen zeq1
Aug 30 17:18:47 <infobot> zeq1 <~s_j_newbu@2a01:348:1e3:1::a20> was last seen on IRC in channel #maemo, 2d 6h 56m 45s ago, saying: 'freemangordon: ok will do'.
Aug 30 17:18:54 <freemangordon> hmm
Aug 30 17:23:17 <kerio> DocScrutinizer05: is the bupbat connected to bq27200 too?
Aug 30 17:23:41 <kerio> or is the calibration data stored in a non-volatile way?
Aug 30 19:12:16 <vi__> holy cow, obama was on reddit.
Aug 30 19:12:24 <kerio> yep
Aug 30 19:12:26 <vi__> the internet is REAL!
Aug 30 19:12:33 <kerio> and the servers crashed hard
Aug 30 19:12:42 <kerio> he had half an hour free, he only answered 10 or so questions
Aug 30 19:12:51 <kerio> he wrote nice, long answers though
Aug 30 19:13:00 <vi__> what a bro.
Aug 30 19:13:16 <kerio> https://my.barackobama.com/page/s/reddit
Aug 30 19:13:17 <vi__> I almost wish I was a yank so I could vote for him.
Aug 30 19:13:21 <kerio> oh :3
Aug 30 19:13:43 <vi__> Then I remember he is up to his balls in bullshit corruption as well.
Aug 30 22:03:30 <DocScrutinizer05> kerio: neither
Aug 31 00:57:54 <GeneralAntilles> Ahaha
Aug 31 00:58:01 <GeneralAntilles> Does this remind anybody else of something? http://www.kickstarter.com/projects/playmg/mg-first-portable-gaming-system-for-the-android-ma?ref=category
Aug 31 00:58:35 <Ken-Young> I had a perfectly working Maemo 5 scratchbox SDK running on my laptop, but foolishly I "upgraded" to the most recent version of Ubuntu, and now the Hildon widgets in my scratchbox environment no longer work properly.   Mouse clicks are ignored, pulldown menus only partiially appear, etc.   Does anyone know how a problem like this can be fixed, or how old a version of Ubuntu I would need to install to have the Maemo 5 SDK work properly?
Aug 31 01:26:40 <LaoLang_cool> Put n900's battery out for a long time, then put it in and start n900, n900 will prompt to set date and time
Aug 31 01:27:42 <LaoLang_cool> My question is: how to change the prompt to another default date, time and the time zone?
Aug 31 01:28:04 <LaoLang_cool> So I don't need to adjust the time zone next time it prompts
**** ENDING LOGGING AT Fri Aug 31 02:59:59 2012