**** BEGIN LOGGING AT Thu Nov 28 02:59:58 2013
Nov 28 05:39:55 <DocScrutinizer05> anybody from USA or Canada awake?
Nov 28 05:40:15 <DocScrutinizer05> I have a question regarding your phone carriers
Nov 28 06:47:40 <ruskie> http://www.theregister.co.uk/2013/11/28/exnokia_team_unveil_jolla_smartphone_with_added_sailfish_os/
Nov 28 07:30:45 <DocScrutinizer05> hmm
Nov 28 08:34:51 <vi__> 18650 are not dangerous.
Nov 28 08:34:53 <vi__> wtf
Nov 28 08:35:13 <vi__> does that mean 36650 are 2*dangerous?
Nov 28 08:35:46 <vi__> any lithium battery will nuke if it is overcharged/reverse polarity.
Nov 28 08:42:51 <vi__> DocScrutinizer05: good lord.  some of the questions in here in the past 20hours.  Batteries sparking?  Hand wound Chinese dynamo?
Nov 28 08:43:20 <vi__> What do you wan to know about US carriers?
Nov 28 08:43:29 <Hurrian> vi__: there are so many badly made 18650 though.
Nov 28 08:44:12 <vi__> That is true.
Nov 28 08:44:36 <Hurrian> given their energy density, Really Bad Things(tm) can happen, compared to other plain ol' dinky batteries
Nov 28 08:44:41 <vi__> However it would have to be the worst 18650 ever to explode without promting.
Nov 28 08:44:56 <vi__> ^prompting.
Nov 28 08:45:28 <vi__> Pretty much all of the tales of exploding li-ions on the net are due to not charging them properly.
Nov 28 08:46:00 <DocScrutinizer05> vi__: thanks, got all answers 
Nov 28 08:46:15 <DocScrutinizer05> http://talk.maemo.org/showthread.php?p=1389579#post1389579 refresh!
Nov 28 08:47:03 <vi__> with lte maybe I can finally have sip over mobile phone data.
Nov 28 08:47:45 <vi__> Li-ions require special treatment.  They are usually fine when they are hidden from the user in sealed pack with a charge controller.
Nov 28 08:47:58 <DocScrutinizer05> when UMTS doesn't suffice then odds are you're SOL
Nov 28 08:48:26 <vi__> When there is no charge controller the user is required to obey the rules of li-ion.
Nov 28 08:48:32 <vi__> If not, that is when they explode.
Nov 28 08:49:02 <Hurrian> vi__: IIRC the guy who used the 18650s in his super duper LED flashlight just supplied rated voltage to it.
Nov 28 08:49:17 <Hurrian> isn't there supposed to be a curve?
Nov 28 08:49:27 <vi__> DocScrutinizer: I seem to get around 300ms ping over 3g.
Nov 28 08:49:33 <vi__> This makes SIP SUCK.
Nov 28 08:50:19 <vi__> Hurrian: I do not know specifically which case you are referring too.  The most famous case I read where the guy almost blew his hand off was very much his own fault.
Nov 28 08:50:31 <vi__> Also he nearly burned his house down.
Nov 28 08:50:35 <DocScrutinizer05> nah, this actually almost doesn't matter
Nov 28 08:50:57 <vi__> He was using knockoff cells in a knockoff charger in a knockoff light.
Nov 28 08:51:22 <vi__> DocScrutinizer05: you are saying 300ms ping is ok?
Nov 28 08:51:30 <Hurrian> Li-ion bomb!
Nov 28 08:51:33 <DocScrutinizer05> sure, for VoIP
Nov 28 08:52:04 <vi__> huh.
Nov 28 08:54:00 <DocScrutinizer05> what would be the negative effect?
Nov 28 08:54:21 <DocScrutinizer05> you hearing far end 150ms later?
Nov 28 08:54:41 <DocScrutinizer05> how terrible! ;-P
Nov 28 08:56:58 <vi__> mmm
Nov 28 08:57:17 <vi__> then why does the n900 sound like shit over a 3g connection?
Nov 28 08:57:41 <vi__> which codec is best for a high latency line?
Nov 28 08:57:44 <vi__> ilbc?
Nov 28 08:59:44 <DocScrutinizer05> yep
Nov 28 09:40:08 <jaska> need lithium6-deuteride batteries.
Nov 28 12:27:40 <kerio> my Conversations stopped working, lol
Nov 28 12:35:46 <auenfx4> blank?
Nov 28 12:36:01 <mashina> have you tried turning it off and on again?
Nov 28 12:41:09 <kerio> auenfx4: eyup
Nov 28 12:41:59 <auenfx4> err, n9 or n900?
Nov 28 12:42:35 <kerio>  n900
Nov 28 12:47:25 <auenfx4> dont recall seeing blank with n900
Nov 28 13:02:59 <vi__> perhaps your database has become corrupted?
Nov 28 13:03:09 <vi__> try renaming it see if it works.
Nov 28 13:04:32 <kerio> i deleted draft.db already
Nov 28 13:09:43 <vi__> I meant the txt message db.
Nov 28 13:09:46 <kolp> kerio: It's ~/rtcom-eventlogger/el-v1.db
Nov 28 13:09:53 <vi__> kolp: ty
Nov 28 13:09:55 <kolp> s/rtcom/.rtcom/
Nov 28 13:09:57 <infobot> kolp meant: kerio: It's ~/.rtcom-eventlogger/el-v1.db
Nov 28 13:10:04 <kerio> oic
Nov 28 13:10:12 <vi__> DONT DELETE IT!
Nov 28 13:10:16 <vi__> rename it!
Nov 28 13:12:52 <kerio> why
Nov 28 13:14:49 <kerio> hey vi__
Nov 28 13:14:50 <kerio> u mad
Nov 28 13:20:49 <vi__> No, I am utterly ambivalent to the notion that you may lose your entire history of txt messages.
Nov 28 13:21:24 <vi__> wtf is this:
Nov 28 13:21:26 <vi__> http://en.wikipedia.org/wiki/Radio_fingerprinting
Nov 28 13:21:38 <vi__> It smells like bs to me.
Nov 28 13:37:43 <fizzie> There seems to be a number of more or less sensible-looking academic papers on the concept, for different kinds of radio transmitters, but not really much about it being applied in practice to modern cell phones, except vague allusions to some commercial product from around 1998-2000 -- "PhonePrint", by "Corsair Communications" -- and there doesn't seem to be much of anything newer written ...
Nov 28 13:37:49 <fizzie> ... about the product or even the company itself.
Nov 28 13:37:52 <fizzie> (Some of the "PhonePrint" press releases do bear quite a resemblance to parts of that Wikipedia article.)
Nov 28 14:23:37 <LjL> shame on me, i haven't turned on my N900 in months now
Nov 28 14:23:50 <LjL> and i just found out i probably should, since Android is going all proprietary ;(
Nov 28 14:33:40 <vi__> android is going proprietary?
Nov 28 14:39:57 <SAiF> ??
Nov 28 14:41:57 <LjL> vi__: well, they're moving more and more components that used to be part of it into Google apps, and deprecating/abandoning the open solutions... i think the icing on the cake so far is the location API
Nov 28 14:42:14 <LjL> good article about it http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/
Nov 28 14:45:51 <vi__> fucking proprietary software.
Nov 28 14:46:30 <vi__> I appreciate you have to make some bucks, but when the hardware is utterly obsolete, let people use it.
Nov 28 14:47:55 <vi__> so are there any platforms that do not suck all the asses?
Nov 28 14:50:04 * LjL is wondering too, but thinks not
Nov 28 14:52:35 <LjL> i hope my N900's battery isn't all kinds of dead from the neglect
Nov 28 14:55:51 <vi__> LjL: batteries are cheap as f*
Nov 28 14:59:01 <LjL> vi__: but it's often kind of hard to determine whether they're actually original, when buying them from ebay or amazon
Nov 28 14:59:15 <LjL> and when buying them elsewhere (if they're available at all), they're usually not all that cheap at all
Nov 28 14:59:58 <vi__> hey intel gma500 drivers source code is available.
Nov 28 15:00:07 <vi__> it is linked to on the openpandora boards
Nov 28 15:00:38 <vi__> intel gma500 is a rebranded powervr535
Nov 28 15:02:09 <vi__> n900 has a shitty powervr530
Nov 28 15:02:24 <vi__> by some magic can I get vsync now?
Nov 28 15:02:31 <SAiF> atleast it have one
Nov 28 15:03:29 <kerio> vi__: that 1600mAh battery is still going strong, btw
Nov 28 15:03:32 <kerio> not sure about yours
Nov 28 15:03:38 <vi__> eh?
Nov 28 15:03:44 <vi__> I do not even know where mine is.
Nov 28 15:03:50 <kerio> D:
Nov 28 15:03:54 <vi__> I pulled the label off to look inside,
Nov 28 15:04:03 <vi__> Then I lost it somewhere.
Nov 28 15:04:07 <kerio> why did you do that
Nov 28 15:04:13 <kerio> you let the magic leak out
Nov 28 15:04:22 <vi__> I wanted to see if the true capacity was stamped on thte side of the cell.
Nov 28 15:04:47 <vi__> I told you it was 1600mAh.
Nov 28 15:04:58 <kerio> i know!
Nov 28 15:04:59 <vi__> I am using an old 1530 scud at the moment.
Nov 28 15:05:16 <kerio> it's still like 1580mAh or something
Nov 28 15:05:25 <vi__> It is probably down to ~12-1300 mAh.
Nov 28 15:05:30 <vi__> nice.
Nov 28 15:05:34 <vi__> Can you still buy them?
Nov 28 15:05:36 <kerio> it's a surprisingly good battery
Nov 28 15:05:44 <kerio> i couldn't find it anymore on aliexpress
Nov 28 15:06:03 <vi__> Obviously it was too good.  The government must have pulled the plug.
Nov 28 15:06:08 <kerio> haha
Nov 28 15:06:37 <vi__> I would like a raw li-ion cell with no protection that will fit in the battery bay.
Nov 28 15:06:52 <vi__> It would be at least 1700mAh.
Nov 28 15:06:54 <kerio> i wonder if i should just wait for a neo900 at this point
Nov 28 15:07:19 <kerio> my n900 has a broken wifi :(
Nov 28 15:07:26 <vi__> aw man.
Nov 28 15:07:33 <vi__> that sucks asses
Nov 28 15:07:34 <kerio> i should still try to reflash it
Nov 28 15:07:43 <kerio> and yeah, it's kind of awful
Nov 28 15:07:43 <vi__> what is worse, broken wifi or broken CMT?
Nov 28 15:08:01 <kerio> to be fair, i have working usb networking and, in some way, working bluetooth PAN
Nov 28 15:08:17 <kerio> there's no good bluetooth PAN UI tho
Nov 28 15:08:25 <vi__> no
Nov 28 15:08:40 <vi__> what about a smashed n900 on ebay?
Nov 28 15:08:46 <vi__> Get the mobo out of it.
Nov 28 15:08:47 <kerio> i have a n900 with a working wifi
Nov 28 15:08:53 <vi__> oh.
Nov 28 15:08:57 <kerio> and broken musb
Nov 28 15:09:03 <vi__> rofl.
Nov 28 15:09:04 <kerio> lolololo
Nov 28 15:11:00 <vi__> broken n900 have hit ~40 euro on fleabay.
Nov 28 15:11:28 <deepy> Maybe I should sell my working one and pay my rent with it
Nov 28 15:11:41 <vi__> is your rent 70 euro?
Nov 28 15:11:42 <kerio> don't be silly
Nov 28 15:11:52 <deepy> becuase the browser IS TOO SLOW FOR ME D:
Nov 28 15:12:04 <vi__> deepy: uninstall adblock.
Nov 28 15:12:10 <deepy> I don't have adblock
Nov 28 15:12:12 <vi__> install some flash blocker.
Nov 28 15:12:21 <deepy> I'm looking at pure HTML pages
Nov 28 15:12:23 <vi__> overclock the shit out of it.
Nov 28 15:12:40 <kerio> and THEN sell it!
Nov 28 15:12:47 <vi__> crank that mutha to 1.15GHz.
Nov 28 15:12:51 <vi__> No mercy.
Nov 28 15:12:55 <deepy> I don't trust overclocking
Nov 28 15:13:07 <vi__> ...
Nov 28 15:13:09 <vi__> why?
Nov 28 15:13:29 <kerio> maybe the cpu will calculate some bits wrong
Nov 28 15:13:35 <deepy> Because it traditionally meant voiding warranty, sacrificing stability and increasing heat
Nov 28 15:13:41 <vi__> rofl.
Nov 28 15:13:42 <kerio> >warranty
Nov 28 15:13:59 <deepy> >traditionally
Nov 28 15:14:10 <kerio> besides, winter is coming
Nov 28 15:14:21 <deepy> I'm Swedish, there's no such thing as winter
Nov 28 15:14:25 <vi__> so why don't you trust overclocking now?
Nov 28 15:14:31 <kerio> if you're swedish, why the hell do you care about extra heat
Nov 28 15:14:42 <deepy> Because I live in Dublin, we have eternal autumn
Nov 28 15:14:49 <kerio> oic
Nov 28 15:14:50 <vi__> also undervolting somewhat mitigates heat thing.
Nov 28 15:15:01 <kerio> not really
Nov 28 15:15:07 <vi__> yeah really.
Nov 28 15:15:12 <kerio> besides, the heat is really not the issue here
Nov 28 15:15:32 <vi__> then what is the issue?
Nov 28 15:15:36 <vi__> I dont get it.
Nov 28 15:15:50 <kerio> it eventually poops out
Nov 28 15:15:54 <kerio> a lot sooner than the usual
Nov 28 15:16:27 <vi__> O dear lord.  I have reduced the lifespan of my processor from 10000000 hours to 1000000 hours.
Nov 28 15:17:28 <vi__> again, undervolting mitigates this.
Nov 28 15:18:21 <vi__> deepy: install power kernel.
Nov 28 15:18:41 <vi__> It comes with smartreflex activated.
Nov 28 15:19:18 <vi__> it will overclock your device by around %30 and you will have a longer battery life as well.
Nov 28 15:19:25 <kerio> u wot m8
Nov 28 15:20:06 <vi__> I assume powerkernel comes with the powerkernel settings script and the default profiles is as I have just said.
Nov 28 15:20:38 <kerio> there's no overclock by default
Nov 28 15:20:51 <kerio> and even smartreflex isn't enabled until you decide
Nov 28 15:20:57 <vi__> Oh.  Ok.
Nov 28 15:21:07 <vi__> I stand corrected.
Nov 28 15:22:51 <vi__> deepy: to make it go faster, install powerkernel.  enable SR and overclock 250-805MHz.
Nov 28 15:23:00 <vi__> wham bam, thank you FMG.
Nov 28 15:23:13 <kerio> install cssu-thumb first!
Nov 28 15:23:22 <kerio> maybe it'll be fast enough
Nov 28 15:23:23 <vi__> yeah that too.
Nov 28 15:23:27 <kerio> without overclocking
Nov 28 15:23:34 <vi__> Dont be such a puff.
Nov 28 15:23:36 <vi__> OC it.
Nov 28 15:23:40 <vi__> 1.15GHz.
Nov 28 15:23:43 <vi__> No mercy.
Nov 28 15:23:47 <vi__> Go hard or go home.
Nov 28 15:24:34 <SAiF> I couldnt get it past 950..
Nov 28 15:24:34 <vi__> ~3!
Nov 28 15:24:35 <infobot> hmm... 3! is 6
Nov 28 15:24:41 <vi__> ~!999999999
Nov 28 15:24:49 <vi__> ~99999!
Nov 28 15:24:59 <vi__> ~9999!
Nov 28 15:25:02 <SAiF> even in 950 when I run heavy, It collapse
Nov 28 15:25:05 <vi__> ~999!
Nov 28 15:25:06 <infobot> ~999
Nov 28 15:25:16 <vi__> infobot that is bullshit.
Nov 28 15:25:16 <infobot> vi__: I think you lost me on that one
Nov 28 15:25:44 <vi__> SAiF: SR does not work above 805.
Nov 28 15:25:48 <vi__> IIRC.
Nov 28 15:26:25 <SAiF> oops thats it
Nov 28 15:26:45 <kerio> vi__: 4e2564
Nov 28 15:27:06 <SAiF> so how should I be OC ing
Nov 28 15:27:07 <vi__> kerio: sorry, i only count up to base12.
Nov 28 15:27:26 <vi__> SAiF: start off by reading the wiki section on overclocking.
Nov 28 15:28:04 <SAiF> okay..
Nov 28 15:28:27 <kerio> SAiF: 3ghz or you're a pussy
Nov 28 15:29:22 <vi__> in short...install powerkernel, install powerkernel settings, kernel-config limits 250 805
Nov 28 15:29:27 <vi__> kerio: http://farm5.static.flickr.com/4044/4494088129_9b62ba7b1f.jpg
Nov 28 15:29:30 <SAiF> its even above microwave frequency, 
Nov 28 15:55:23 <android_808> freemangordon: ping
Nov 28 16:20:04 <DocScrutinizer05> ~omap-oc
Nov 28 16:20:05 <infobot> rumour has it, omap-oc is http://mg.pov.lt/maemo-irclog/%23maemo.2010-08-01.log.html#t2010-08-01T22:16:05  read that!, or and this http://mg.pov.lt/maemo-irclog/%23maemo.2011-03-11.log.html#t2011-03-11T03:04:11
Nov 28 16:20:12 <DocScrutinizer05> ~overclocking
Nov 28 16:20:14 <infobot> "OK, listen up.  This is your CPU."  apt drops the CPU into a hot frying pan.  "This is your CPU on overclocking.  Any questions?"
Nov 28 16:20:28 <DocScrutinizer05> ~sr
Nov 28 16:20:30 <infobot> [SmartReflex] >>Again, TI and we [Nokia] couldn't fix SmartReflex - we say memory corruption in front of our own eyes with that enabled, so we had to ship that disabled.<<
Nov 28 16:21:28 <DocScrutinizer05> also SR is massively overrated
Nov 28 16:22:27 <DocScrutinizer05> it might crate a maybe 10% runtime improvement on particular special use cases, like mp3 playback
Nov 28 16:22:32 <DocScrutinizer05> create*
Nov 28 16:24:38 <DocScrutinizer05> usually you'll not notice a difference at all. Why? Because CPU usually is doing "rush to idle" means it's running on max CPU clock to go to idle/zeroclock the faster, thus no SR will have any effect since it only is relevant for clock scaling to fractions of max CPU clock
Nov 28 16:28:15 <DocScrutinizer05> so in my book SR definitely is not worth the risk. Particularly since you never know what memory corruption will cause as fallout. Odds are all sorts of terrible things happen that you never would associate to SR
Nov 28 16:29:42 <vi__> I have been running my device with SR enabled sine it was 'fixed'.
Nov 28 16:29:54 <vi__> That is what, 1.5 years now?
Nov 28 16:30:02 <vi__> on is it only 1?  I forget.
Nov 28 16:30:07 <vi__> No corruption here.
Nov 28 16:30:17 <DocScrutinizer05> how do you even know?
Nov 28 16:31:00 <vi__> I think 1 year is a looooong test case.  especially for a 'heavy' user.
Nov 28 16:31:02 <DocScrutinizer05> and there been no "fix2 for SR
Nov 28 16:31:43 <DocScrutinizer05> just an enabling of stuff Nokia intentionally disabled to protect users
Nov 28 16:32:11 <vi__> I think FMG did a little more than uncomment some code.
Nov 28 16:33:27 <SpeedEvil> The problem is we have no understanding of why SR was disabled. Was it 'we can't prove 100% that it's reliable on all devices' or 'stuff catches fire'
Nov 28 16:33:46 <vi__> Who knows.
Nov 28 16:34:18 <vi__> The anecdotal evidence, which there is a lot of suggests it is now working OK. 
Nov 28 16:42:56 <Pali> speex arm neon optimalization (which is closed in n900/maemo5) was opened, look: http://lists.xiph.org/pipermail/speex-dev/2011-September/008242.html
Nov 28 16:43:22 <vi__> cool
Nov 28 16:44:06 <Pali> I do not understand why nobody informed maemo devs about it 2 years ago when it happened
Nov 28 16:44:44 <Pali> jpeg neon oplimazations was opened too and patches are already in jpeg-turbo project
Nov 28 16:44:45 <DocScrutinizer05> vi__: nonsense
Nov 28 16:45:02 <vi__> ~vi__
Nov 28 16:45:03 <infobot> somebody said vi__ was 13:21 < DocScrutinizer05> vi__: you're absolutely right
Nov 28 16:45:27 <DocScrutinizer05> don't make me redefine the factoid! :-P
Nov 28 16:46:41 <Pali> and here is git repo with that neon speex patches created/maintained by author of patches: https://gitorious.org/oku-speex/speex
Nov 28 16:48:26 <DocScrutinizer05> you're free to state you are willing to gamble on not having one of the maybe 10% lemons that don't work, or that you don't care MTBF going down form maybe 5000h to 500 or 10 or whatever, or that you don't need the level of reliablity or safety that Nokia thought is mandatory for commercial products. But don't claim Nokia and TI were simply too dull or evel minded to put their own technology to proper work, that's extreme hybris and silly
Nov 28 16:49:17 <DocScrutinizer05> Pali: maybe Neon is considered a bummer?
Nov 28 16:49:30 <solofight> people, i am trying to install the usb host mode gui application on my nokia n900 running maemo but i get this error - http://pastebin.com/ULgCDLyg
Nov 28 16:49:41 <vi__> I never said such a thing.
Nov 28 16:49:56 <solofight> even if i try to force the installation with -f it aint installing the app
Nov 28 16:49:59 <solofight> how to proceed ?
Nov 28 16:50:03 <solofight> kindly help
Nov 28 16:50:03 <vi__> I said 'I do not know why nokia/ti could not make it work' or something like that.
Nov 28 16:50:43 <vi__> what kernel are you running?
Nov 28 16:50:47 <DocScrutinizer05> solofight: install i2ctools manually
Nov 28 16:51:05 <DocScrutinizer05> and you also need to install a recent powerkernel
Nov 28 16:51:50 <solofight> DocScrutinizer05: i2ctools manually ? you mean download the file and compile it in the system ?
Nov 28 16:51:52 <DocScrutinizer05> vi__: don't you think nokia and TI also didn't know, and felt pretty pissed about it?
Nov 28 16:52:03 <DocScrutinizer05> nah
Nov 28 16:52:10 <solofight> recent powerkernel ?
Nov 28 16:52:24 <DocScrutinizer05> solofight: download the .deb and and install with dpkg -i
Nov 28 16:52:31 <DocScrutinizer05> ~kp
Nov 28 16:52:32 <infobot> rumour has it, kp is http://talk.maemo.org/showthread.php?t=85665
Nov 28 16:53:20 <DocScrutinizer05> solofight: sorry for the inconveniences but recently it seems our repos bitrot a lot
Nov 28 16:54:21 <Pali> ~kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 16:54:21 <infobot> Pali: i already had it that way
Nov 28 16:54:30 <Pali> ~kp
Nov 28 16:54:31 <infobot> from memory, kp is http://talk.maemo.org/showthread.php?t=85665
Nov 28 16:54:35 <DocScrutinizer05> vi__: again, see
Nov 28 16:54:36 <DocScrutinizer05> +sr
Nov 28 16:54:39 <Pali> wtf?
Nov 28 16:54:40 <DocScrutinizer05> ~sr
Nov 28 16:54:41 <infobot> [SmartReflex] >>Again, TI and we [Nokia] couldn't fix SmartReflex - we say memory corruption in front of our own eyes with that enabled, so we had to ship that disabled.<<
Nov 28 16:55:48 <DocScrutinizer05> (verbatim quote FatPhil )
Nov 28 16:56:08 <DocScrutinizer05> (who been kernel maintainer at Nokia)
Nov 28 16:57:49 <DocScrutinizer05> so unless you can come up with a proper stresstest on a number of devices like >NN, to spot *every* memory corruption caused by SR, you can't even claim it's supposed to have seen any fixes at all
Nov 28 16:59:09 <vi__> Well in my opinion it is fine.
Nov 28 16:59:15 <vi__> Use it at your own risk.
Nov 28 16:59:21 <DocScrutinizer05> opinions are like a.....
Nov 28 16:59:24 <DocScrutinizer05> everybody got one
Nov 28 16:59:36 <vi__> give me a break.
Nov 28 16:59:51 <vi__> I am not some 2 bit shit shoveling 'rom cooker' from xda developer.
Nov 28 17:00:02 <DocScrutinizer05> just don't claim "SR is ficed"! it isn't!
Nov 28 17:00:06 <DocScrutinizer05> fixed*
Nov 28 17:01:17 <DocScrutinizer05> all that got accomplished is parts of community deliberately ignoring a bugreport from inside Nokia
Nov 28 17:01:41 <DocScrutinizer05> and working around the safeguards Nokia implemented in kernel after they found out
Nov 28 17:01:44 <vi__> It works for me.
Nov 28 17:02:03 <vi__> I enjoy my extra 10% battery life while cpu is at work.
Nov 28 17:02:07 <DocScrutinizer05> WFM is the worst of all statements when it comes to heissenbugs
Nov 28 17:02:33 <DocScrutinizer05> and your 10% extra only happen when your CPU runs at 250MHz
Nov 28 17:02:44 <vi__> wot
Nov 28 17:03:23 <vi__> The cpu is running on a reduced voltage on every frequency step.
Nov 28 17:03:31 <DocScrutinizer05> aha!!!
Nov 28 17:03:32 <vi__> Not just 250.
Nov 28 17:03:44 <DocScrutinizer05> so WTF would Nokia decide to overvolt the CPU?
Nov 28 17:03:57 <DocScrutinizer05> and why would SR be needed to fix that?
Nov 28 17:04:00 <vi__> Who claims they overvolted the CPU?
Nov 28 17:04:05 <solofight> DocScrutinizer05: so i need to manuall download the .deb package of i2ctools and then do a apt-get install kernel-power-flasher 
Nov 28 17:04:07 <solofight> correct ?
Nov 28 17:04:08 <DocScrutinizer05> and how *could* it fix that?
Nov 28 17:04:23 <DocScrutinizer05> vi__: YOU
Nov 28 17:04:33 <DocScrutinizer05> [2013-11-28 18:03:23] <vi__> The cpu is running on a reduced voltage on every frequency step.
Nov 28 17:04:37 <vi__> Nokia set the CPU voltage within a nice safe margin, guaranteed to work on all devices. 
Nov 28 17:05:07 <DocScrutinizer05> solofight: kernel-power-flasher *modules and kernel-power
Nov 28 17:05:10 <DocScrutinizer05> see 
Nov 28 17:05:13 <DocScrutinizer05> ~kp
Nov 28 17:05:14 <infobot> kp is probably http://talk.maemo.org/showthread.php?t=85665
Nov 28 17:05:45 <DocScrutinizer05> though I heard right now a working KP should be in extras-devel again
Nov 28 17:05:48 <DocScrutinizer05> asl Pali
Nov 28 17:05:52 <DocScrutinizer05> ask*
Nov 28 17:06:14 <DocScrutinizer05> when post #1 in http://talk.maemo.org/showthread.php?t=85665 doesn't have the info it should have
Nov 28 17:06:30 <Pali> ~kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 17:06:30 <infobot> i already had it that way, Pali
Nov 28 17:06:33 <Pali> ~kp
Nov 28 17:06:33 <infobot> methinks kp is http://talk.maemo.org/showthread.php?t=85665
Nov 28 17:06:46 <Pali> kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 17:06:55 <Pali> ~kp
Nov 28 17:06:55 <infobot> it has been said that kp is http://talk.maemo.org/showthread.php?t=85665
Nov 28 17:07:04 <Pali> bad link again
Nov 28 17:07:18 <Pali> infobot is not working...
Nov 28 17:07:26 <Pali> kp52 is in extras
Nov 28 17:07:28 <DocScrutinizer05> no, you're not working
Nov 28 17:07:31 <DocScrutinizer05> ;-P
Nov 28 17:07:33 <zammy> infobot has to get graduated
Nov 28 17:07:40 <DocScrutinizer05>  ~literal kp
Nov 28 17:07:40 <infobot> "#maemo kp" is "http://talk.maemo.org/showthread.php?t=85665"
Nov 28 17:07:41 <zammy> XD
Nov 28 17:07:54 <Pali> [18:06:30] <infobot> i already had it that way, Pali
Nov 28 17:08:02 <DocScrutinizer05>  ~literal kp
Nov 28 17:08:03 <infobot> "#maemo kp" is "http://talk.maemo.org/showthread.php?t=85665"
Nov 28 17:08:08 <zammy> which way
Nov 28 17:08:26 <DocScrutinizer05> ~forget _default kp
Nov 28 17:08:26 <infobot> DocScrutinizer05: i didn't have anything called '_default kp' to forget
Nov 28 17:08:30 <DocScrutinizer05> ~forget  kp
Nov 28 17:08:31 <infobot> i forgot kp, DocScrutinizer05
Nov 28 17:08:35 <DocScrutinizer05>  ~literal kp
Nov 28 17:08:35 <infobot> "#maemo kp" is "http://talk.maemo.org/showthread.php?t=85665"
Nov 28 17:08:39 <DocScrutinizer05> ~kp
Nov 28 17:08:40 <infobot> hmm... kp is http://talk.maemo.org/showthread.php?t=85665
Nov 28 17:09:07 <DocScrutinizer05> ~#maemo kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 17:09:08 <infobot> ...but #maemo kp is already something else...
Nov 28 17:09:16 <zammy> forget boobs
Nov 28 17:09:17 <DocScrutinizer05> infobot: no, #maemo kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 17:09:17 <infobot> okay, DocScrutinizer05
Nov 28 17:09:23 <zammy> ok...?
Nov 28 17:09:26 <DocScrutinizer05> ~kp
Nov 28 17:09:27 <infobot> extra, extra, read all about it, kp is http://talk.maemo.org/showthread.php?t=89823
Nov 28 17:09:33 <DocScrutinizer05> Pali: better?
Nov 28 17:09:57 <DocScrutinizer05> Pali: please make sure you are editing the correct factoid!
Nov 28 17:10:12 <Pali> ah, this aliasing is bad
Nov 28 17:10:22 <DocScrutinizer05> this is no aliasing
Nov 28 17:10:32 <Pali> there is factoid aliasing
Nov 28 17:10:33 <DocScrutinizer05> this is channel specific factoid search
Nov 28 17:10:47 <DocScrutinizer05> ~chanset #maemo
Nov 28 17:10:48 <infobot> chan: #maemo (see _default also)
Nov 28 17:10:48 <infobot>  OnJoin => 1, _time_added => 1179878166, autojoin => infobot, factoidSearch => $chan _default
Nov 28 17:10:51 <Pali> by default ~kp modifing something else as showing
Nov 28 17:11:34 <Pali> so when infobot told me that "i already had it that way, Pali" I did not know why it still shown me old link
Nov 28 17:11:39 <DocScrutinizer05> Pali: infobot is in ~120 channels
Nov 28 17:12:24 <DocScrutinizer05> you mustn't fight with 119 other channels about pretty commonplace factoid keys like "kp"
Nov 28 17:12:30 <DocScrutinizer05> ~chaninfo
Nov 28 17:12:31 <infobot> 125/125 channels, 4741 users, 3560 unique: #debian/1365, #kde/403, #maemo/243, #gsoc/237, #asterisk/214, #cubieboard/152, #wowuidev/144, #oe/143, #harmattan/120, #wowace/107, #meego/99, #arm-netbook/88, #wowhead/77, #utah/73, #/71, #webos-internals/66, #maemo-ssu/66, #openmoko/57, #edev/57, #bzflag/55, #asterisk-dev/53, #openmoko-cdevel/52, #neo900/43, #curseforge/39, #sc2mapster/38, #slug/33, #gllug/30, #uphpu/30, #elinux/30, #htc-linux/29, ...
Nov 28 17:12:32 <Pali> it is BAD idea that calling "~kp new_value" is changing other factoid as calling "~kp"
Nov 28 17:12:45 <vi__> ~curseforge
Nov 28 17:12:45 <infobot> curseforge is, like, at http://curseforge.com/ but is still under development.
Nov 28 17:13:02 <vi__> ~gentoosmite DocScrutinizer05
Nov 28 17:13:02 * infobot spends 5 days recompiling DocScrutinizer05, and when it's all done, DocScrutinizer05 runs 6% slower than previously
Nov 28 17:13:03 <DocScrutinizer05> Pali: take it to infobot
Nov 28 17:13:59 <DocScrutinizer05> Pali: I don't even have access to the server infobot is running on
Nov 28 17:14:31 <zammy> infobot, should learn how to program it self
Nov 28 17:14:36 <DocScrutinizer05> ~owner
Nov 28 17:14:36 <infobot> TimRiker is my owner
Nov 28 17:15:57 <DocScrutinizer05> Pali: we need factoidSearch => $chan _default otherwise factoids like kp wouldn't be available at all or point to something completely unrelated
Nov 28 17:16:10 <DocScrutinizer05> hi dos1
Nov 28 17:16:50 <DocScrutinizer05> ~multiboot
Nov 28 17:16:51 <infobot> i guess multiboot is http://maemo.org/packages/view/multiboot/, or **DEPRECATED*, see ~maemo-multiboot
Nov 28 17:17:03 <DocScrutinizer05> ~_default multiboot
Nov 28 17:17:04 <infobot> hmm... multiboot is http://maemo.org/packages/view/multiboot/
Nov 28 17:17:31 <DocScrutinizer05> damn, another factpoid some uneducated user ruined/hijacked
Nov 28 17:17:44 <DocScrutinizer05> ~forget multiboot
Nov 28 17:17:46 <infobot> i forgot multiboot, DocScrutinizer05
Nov 28 17:17:56 <DocScrutinizer05> ~listkeys multiboot
Nov 28 17:17:57 <infobot> Factoid search of 'multiboot' by key (3): #maemo multiboot ;; maemo-multiboot ;; multiboot #DEL#.
Nov 28 17:18:07 <DocScrutinizer05> ~unforget multiboot
Nov 28 17:18:08 <infobot> DocScrutinizer05: Successfully recovered 'multiboot'.  Have fun now.
Nov 28 17:18:14 <DocScrutinizer05> ~_default multiboot
Nov 28 17:18:14 <infobot> somebody said multiboot was http://maemo.org/packages/view/multiboot/
Nov 28 17:18:19 <DocScrutinizer05> ~forget multiboot
Nov 28 17:18:19 <infobot> i forgot multiboot, DocScrutinizer05
Nov 28 17:18:59 <DocScrutinizer05> :-S
Nov 28 17:19:31 <DocScrutinizer05> ~multiboot is http://en.wikipedia.org/wiki/Multiboot
Nov 28 17:19:31 <infobot> DocScrutinizer05: okay
Nov 28 17:19:38 <DocScrutinizer05> ~multiboot
Nov 28 17:19:38 <infobot> rumour has it, multiboot is http://maemo.org/packages/view/multiboot/, or **DEPRECATED*, see ~maemo-multiboot
Nov 28 17:19:45 <DocScrutinizer05> ~_default multiboot
Nov 28 17:19:46 <infobot> i heard multiboot is http://en.wikipedia.org/wiki/Multiboot
Nov 28 17:20:35 <DocScrutinizer05> Pali: please learn to use "~literal <factoid>" to check what you are planning to teach bot
Nov 28 17:20:48 <DocScrutinizer05> also "~factinfo <factoid>"
Nov 28 17:21:18 <DocScrutinizer05> factoid database is not a toy to mess with lightheadedly
Nov 28 17:22:34 <DocScrutinizer05> and the way bot works can get critizised but not ignored
Nov 28 18:45:24 <Tekk_> is there a package to get the file manager to recognize nfs shares?
Nov 28 18:45:39 <Tekk_> it picks up on the various smb shares on my network, but not my nfs one
Nov 28 20:12:15 <DocScrutinizer05> hmm, prolly sth in or next to gnome-vfs or whatsitcalled
Nov 28 20:13:13 <DocScrutinizer05> only wild guessing
Nov 28 20:13:49 <DocScrutinizer05> also, NFS seriously?
Nov 28 20:14:20 <DocScrutinizer05> a pita even on stable wired local ethernet
Nov 28 20:14:32 <Defiant> works fine over wlan
Nov 28 20:14:58 <DocScrutinizer05> yeah, until $something stalls
Nov 28 20:15:04 <DocScrutinizer05> then happy boot time
Nov 28 20:15:33 <Defiant> unless you set soft,intr or do a lazy unmount
Nov 28 20:15:46 <DocScrutinizer05> usually of ALL machines in the network entangled with NFS shares
Nov 28 20:17:23 <DocScrutinizer05> and don't get me started about user IDs
Nov 28 20:18:44 <DocScrutinizer05> current ubuntu comes with a brilliant¡ hack to use target machine's etc/passwd to convert numerical user ID to file permissions
Nov 28 20:20:11 <DocScrutinizer05> go figure!
Nov 28 20:20:48 <DocScrutinizer05> err /etc/groups
Nov 28 20:20:58 <jaska> idmap?
Nov 28 20:21:38 <DocScrutinizer05> and source machines etc/groups iirc
Nov 28 20:22:25 <DocScrutinizer05> to ship around the NFS design limitation of max (iirc) 16 auxiliary groups a user can be in
Nov 28 20:22:32 <jaska> aah
Nov 28 20:22:51 <DocScrutinizer05> been so stupid I already actively forgot about the details
Nov 28 20:24:02 <DocScrutinizer05> particularly since I never touch ubuntu without massive pressure and violence threat
**** ENDING LOGGING AT Fri Nov 29 02:59:58 2013