**** BEGIN LOGGING AT Sat May 21 02:59:58 2016
May 21 05:00:52 <luke-jr> any reason GPS wouldn't work in Switzerland?
May 21 05:15:54 <freemangordon> luke-jr: no data roaming?
May 21 05:20:43 <luke-jr> freemangordon: using wifi
May 21 05:21:13 <freemangordon> hmm, not sure agps works over wifi
May 21 05:21:24 <luke-jr> :/
May 21 05:21:45 * luke-jr would have expected 15-30 min lock regardless of AGPS
May 21 05:22:35 <freemangordon> :nod:
May 21 05:22:57 <freemangordon> unless signal is weak
May 21 05:49:11 <ds3> neutrality requires military systems such as GPS be blocked? :D
May 21 07:46:10 <jonwil> hi
May 21 07:52:49 <Cor-Ai> hello
May 21 07:54:31 <Vajb_> will wdq change to 1 if charger is connected or i need to remove it first? Related to bme.
May 21 07:57:34 <Sicelo> wdq, or vdq?
May 21 08:02:26 <Sicelo> VDQ is set to 1 when battery gets full. It remains 1 until a charger is connected again, when it gets set to 0 until charge is complet again. when VDQ is 0, then battery calibration will not take place
May 21 08:04:43 <Vajb_> yes vdq, but that doesn't state if it turns to 1 if charger is connected and battery is "full"
May 21 08:05:37 <Sicelo> yes, becomes 1 while charger is connected :)
May 21 08:06:29 <Vajb_> :) ok
May 21 08:07:23 <Vajb_> i think i have to use "partial charge" to get my new dualpolarcell battery calibrated
May 21 08:07:49 <Sicelo> afaik that won't work
May 21 08:07:56 <Vajb_> it had 3,7v left when phone decided this calibration is invalid
May 21 08:08:00 <Vajb_> oh
May 21 08:08:58 <Sicelo> VDQ needs to be 1 until discharge cycle is complete ... see what i said above: the moment you plug in a charger during discharge, VDQ becomes 0
May 21 08:10:48 <Vajb_> yes i know, but now it was 1 and suddenly when charge dropped to 3,7v it went to 0 without me doing anything
May 21 08:11:08 <Sicelo> that also happens once in a while :)
May 21 08:11:41 <Vajb_> happened to me also when i moved from single polarcell to mugen
May 21 08:11:57 <Vajb_> mugen wasn't too good at quality
May 21 08:13:07 <KotCzarny> o.O
May 21 08:26:05 <Maxdamantus> I think you basically need to confuse it by discharging quickly the first time.
May 21 08:26:51 <Maxdamantus> There's some rule involving 12.5% or something of the LMD.
May 21 08:26:59 <Vajb_> yup i know
May 21 08:27:20 <Vajb_> i guess i charge it to max and stream media from web till it dies
May 21 08:27:39 <Maxdamantus> Just leave the camera LEDs on.
May 21 08:27:44 <Vajb_> but so far im happy with my dual setup
May 21 08:27:44 <KotCzarny> i think transmitting data is even more power hungry
May 21 08:27:56 <KotCzarny> so start scp'ing big file too
May 21 08:28:01 <Maxdamantus> You want something that's consistent.
May 21 08:28:09 <KotCzarny> just dont 'splode it
May 21 08:28:14 <Maxdamantus> like the LEDs left on.
May 21 08:28:40 <Vajb_> 28h of my normal heavy use and it went to 3,7v just. Mugen would have died in 12h mark, about
May 21 08:29:35 <Vajb_> my heavy use is constantly checking facebook while listening to music ;)
May 21 08:30:22 <Maxdamantus> er, not 12.5%*LMD, but NAC/16
May 21 08:30:52 <Maxdamantus> er, NAC >= LMD/16
May 21 08:32:04 <Maxdamantus> If you were monitoring it during your failed calibration, it was probably sitting at about NAC = LMD/16 for a few hours, then VDQ would switch to 0 and NAC would continue decreasing.
May 21 08:32:16 <Vajb_> Lmd was 2048 and now i expect it to be around 3200
May 21 08:33:24 <KotCzarny> it will be 2200-2400 probably
May 21 08:33:50 <Maxdamantus> Two of them? I imagine 3000
May 21 08:34:56 <Maxdamantus> My single one was measured at around 1600 the first few calibrations.
May 21 08:35:15 <Maxdamantus> dunno if it scales linearly though.
May 21 08:39:33 <Vajb> damned gprs
May 21 08:39:33 <Vajb> i was saying:
May 21 08:39:33 <Vajb> Lmd was 2048 and now i expect it to be around 3200
May 21 08:40:35 <Maxdamantus> Yeah. I'd suggest charging it and leaving it with the camera LEDs on.
May 21 08:41:48 <Maxdamantus> (for a first, inaccurate, calibtation)
May 21 08:50:54 <Vajb> ok, thx for the camera hint. Never crossed my mind.
May 21 09:21:21 <ceene> prrrrfffffffffffff
May 21 09:21:24 <ceene> banned again
May 21 09:21:26 <ceene> without any cause
May 21 09:21:36 <ceene> as i haven't even tried to log in in a week
May 21 09:28:02 <KotCzarny> maybe you got on the scheduled bans list
May 21 09:28:21 <KotCzarny> or they ban now users that dont use the network for a week
May 21 09:28:41 <ceene> that wouldn't make much sense :s
May 21 09:28:53 <ceene> don't know
May 21 09:29:22 <ceene> i'm really just about to give up
May 21 09:29:30 <ceene> i can't send nor receive messages yet
May 21 09:29:38 <Sicelo> i have two available numbers :)
May 21 09:29:43 <ceene> and i get banned even if i don't do nothing at all
May 21 09:30:09 <KotCzarny> ;)
May 21 09:30:18 <ceene> Sicelo: we may try with one of them if you want, but last time i coudln't even register
May 21 09:30:29 <ceene> whatsapp is not liking your company or whatever
May 21 09:30:35 <Sicelo> lol
May 21 09:30:39 <enyc> moopmeep
May 21 09:30:52 <ceene> vectis3 has offered me his number
May 21 09:30:57 <ceene> but seems not to be online right now
May 21 09:31:21 <ceene> i need to debug why i'm not generating right session cipher keys
May 21 09:31:43 <ceene> but even if i manage to do that... what does it matter, if i'll get banned in two days?
May 21 09:31:59 <KotCzarny> well, it will solve one bug
May 21 09:32:07 <KotCzarny> nd sometimes bugs have the same cause
May 21 09:32:39 <ceene> that's true, yes
May 21 09:33:35 <ceene> fuck, birds are making a nest on my gas chimney
May 21 09:34:38 <Sicelo> is it summer? :P
May 21 09:35:09 <ceene> yes
May 21 09:35:17 <ceene> but if they block gas fumes
May 21 09:35:21 <ceene> my heater won't work
May 21 09:35:29 <ceene> as it will shut itself
May 21 09:42:32 <KotCzarny> i can get you code from my gf number too if you need/want
May 21 09:43:54 <ceene> yes, please, that'll be great
May 21 09:44:18 <ceene> i'll need number, country and provider (or mnc and mcc)
May 21 09:46:08 <KotCzarny> k, let me sms her
May 21 09:46:37 <ceene> if you had whatsapp you could do it for free...
May 21 09:46:46 <ceene> but it wouldn't matter to us then :D
May 21 09:55:57 <ceene> i think i'm gonna start one day porting yappari to use telegram
May 21 09:56:02 <ceene> seems more feasible right now
May 21 09:56:10 <ceene> and people will be happy as well, maybe not as much
May 21 11:33:39 <ceene> birds evicted
May 21 11:33:47 <ceene> at least i've done one useful thing today
May 21 11:33:55 <ceene> one hour and a half later
May 21 11:47:55 <ceene> http://imgur.com/a/PSsOR
May 21 11:50:17 <KotCzarny> pah, you didnt use the flamethrower
May 21 12:04:25 <ceene> blocked
May 21 12:04:26 <ceene> fine
May 21 12:04:27 <ceene> great
May 21 12:04:35 <ceene> i couldn't even register
May 21 12:04:59 <ceene> i've already blocked KotCzarny and his gf's number
May 21 12:05:12 <ceene> that doesn't make any fucking sense
May 21 12:05:16 <ceene> does that mean
May 21 12:05:21 <ceene> that i can block people all around?
May 21 12:07:38 <ginggs> ceene: please package your whatsapp blocker application :)
May 21 12:08:00 <KotCzarny> ceene, no worries, we dont use crapsapp
May 21 12:09:33 <KotCzarny> ceene, one thought, does roaming affect initial registeration info?
May 21 12:09:58 <KotCzarny> play gsm is the network that roams on most of the other network towers here
May 21 12:10:19 <ceene> it shouldn't, the phone extracts this information from the sim
May 21 12:10:51 <ceene> it's the sim's provider's network mcc and mnc what is needed to register
May 21 12:11:10 <ceene> i guess sms may not be received while on roaming
May 21 12:11:29 <ceene> well, that's idiotic also, you can send an sms to anyone no matter where he is
May 21 12:11:35 <ceene> so... don't know, really :/
May 21 12:11:49 <ceene> maybe they're changing registration procedure too
May 21 12:15:34 <Sicelo> hey ginggs :)
May 21 12:15:50 <ginggs> hi Sicelo
May 21 12:16:09 <Sicelo> ceene: blocked during registration already? 0.o
May 21 12:16:44 <ceene> yep :s
May 21 12:17:43 <KotCzarny> hmm
May 21 12:17:47 <KotCzarny> try another ip/isp ?
May 21 12:18:07 <ceene> maybe
May 21 12:18:13 <ceene> next time i'll avoid using this computer
May 21 12:18:24 <ceene> but don't know
May 21 12:18:32 <ceene> it's all quite frustrating
May 21 12:18:59 <Sicelo> you were using wget? could it be that the registration URL is different now?
May 21 12:19:42 <ceene> i've used yowsup directly for this
May 21 12:19:50 <ceene> i've managed to get registration sms
May 21 12:20:00 <ceene> i got this
May 21 12:20:03 <ceene> INFO:yowsup.common.http.warequest:{"status":"fail","reason":"temporarily_unavailable","retry_after":3600}
May 21 12:20:12 <ceene> and then {"status":"fail","reason":"blocked"}
May 21 12:20:14 <ceene> :/
May 21 12:21:01 <KotCzarny> it could be something as simple as a cookie to get you blocked
May 21 12:22:07 <KotCzarny> (and block history reaching some threshold)
May 21 12:32:44 <Venemo> hey
May 21 12:32:51 <Venemo> looks like CSSU has some dependency issues
May 21 12:37:33 <Venemo> http://pastebin.com/mK28aAhx
May 21 12:38:20 <Sicelo> Venemo: we don't dist upgrade on maemo :)]
May 21 12:39:49 <KotCzarny> he he
May 21 12:39:56 <Venemo> plain upgrade doesn't wanna upgrade some packages either
May 21 12:40:08 <Venemo> and mp-fremantle-community-pr has missing dependencies too
May 21 12:40:11 <KotCzarny> venemo, you were told to follow cssu install exactly
May 21 12:41:06 <Venemo> turns out, cssu was already installed, all I did yesterday was switch to its testing version and ran apt-get update and upgrade
May 21 12:42:23 <KotCzarny> so, no dep problems, you just broke the packages
May 21 12:42:24 <KotCzarny> he he
May 21 12:44:50 <Maxdamantus> Earthquake.
May 21 12:48:22 <Venemo> uh.
May 21 12:48:25 <Venemo> what did I break?
May 21 12:48:42 <Venemo> mp-fremantle-community-pr depends on packages that aren't in the repos
May 21 12:49:16 <KotCzarny> which one?
May 21 12:49:29 <KotCzarny> also, list mp-fremantle-community-pr version
May 21 13:00:25 <Venemo> http://pastebin.com/Yt0mjK8x
May 21 13:01:01 <APic> Nice one
May 21 13:04:15 <Venemo> not sure what is wrong
May 21 13:07:37 <Venemo> by the way, since the official nokia sources are out... I downloaded the N900 firmware images from somewhere
May 21 13:07:39 <Venemo> but
May 21 13:07:48 <Venemo> is there a trustworthy source of their MD5 sums?
May 21 13:09:20 <KotCzarny> ~maemo-repos
May 21 13:09:21 <infobot> somebody said maemo-repos was http://wiki.maemo.org/Repository#List_of_Maemo_repositories
May 21 13:10:05 <KotCzarny> also:
May 21 13:10:09 <KotCzarny> ~tabletsdev
May 21 13:10:10 <infobot> [tabletsdev] http://tablets-dev.nokia.com/  http://wiki.maemo.org/Tabletsdev ,  http://tabletsdev.maemo.org (all defunct, thanks Nokia) or the nice site http://www.fladnag.net/downloads/telephone/n900/tools/, or http://www.mmnt.net/db/0/0/93.81.63.203/repositories/skeiron.org/skeiron.org/tablets-dev/maemo_dev_env_downloads, or http://maemo.muarf.org/tablets-dev/maemo_dev_env_downloads/
May 21 13:10:51 <Venemo> are those links trustworth?
May 21 13:10:56 <Venemo> are those links trustworthy?
May 21 13:11:23 <KotCzarny> muarf is ran by bencoh
May 21 13:11:27 <KotCzarny> and bencoh is
May 21 13:15:56 <Venemo> awesome
May 21 13:23:48 <KotCzarny> probably /sys
May 21 14:46:51 <DocScrutinizer05> ~jrrepos
May 21 14:46:55 <infobot> [jrrepos] http://maemo.cloud-7.de/maemo5/et_al/HAM-catalogs/
May 21 14:47:49 <DocScrutinizer05> ~flashing-cmdline
May 21 14:47:49 <infobot> i guess flashing-cmdline is http://mg.pov.lt/maemo-irclog/%23maemo.2016-04-09.log.html#t2016-04-09T01:18:12
May 21 14:48:50 <DocScrutinizer05> Venemo: ^^^
May 21 14:49:11 <Venemo> thanks, will take a look
May 21 14:57:50 <DocScrutinizer05> it's 'my' stuff so I can say there's nothing bad in it from my side. I can't guarantee for the mirror repos but they behaved so far
May 21 14:58:50 <DocScrutinizer05> the flashing-cmdline has all you need, regarding downloads of images and md5ums
May 21 14:59:06 <DocScrutinizer05> all checked to be 100% genuine
May 21 16:11:43 <Venemo> awesome
May 21 16:18:49 <DocScrutinizer05> so "~flashing" is just "copy this into your linux PCs terminal" and you're done
May 21 16:19:27 <DocScrutinizer05> well, you also need to hit enter. The rest is automatically resp guided
May 21 16:27:59 <Venemo> thank you DocScrutinizer05
May 21 16:28:27 <DocScrutinizer05> yw, hope it works flawlessly for you. If not, please let me know
May 21 16:28:47 <Venemo> will do.
May 21 16:29:06 <DocScrutinizer05> ooh, there's one nasty thing I can't handle: you need the libusb0.1.4_32bit on your system
May 21 16:29:20 <DocScrutinizer05> your PC
May 21 16:29:26 <Venemo> I got libusb-0.1.5-6.fc23.i686
May 21 16:29:56 <DocScrutinizer05> I rhink you need the 32bit version
May 21 16:30:00 <Venemo> that is it
May 21 16:30:06 <DocScrutinizer05> ooh, ok
May 21 16:30:15 <Venemo> i686 is just another fancy name for it :)
May 21 16:30:25 <DocScrutinizer05> that's why I can't handle it at all, it's different on each distro
May 21 16:30:41 <Venemo> no problem, let's hope 0.1.5 is compatible with 0.1.4
May 21 16:31:25 <DocScrutinizer05> you'll notice if flasher loads and does something, or just complains about missing file or whatever
May 21 16:32:03 <Venemo> yeah.
May 21 16:32:11 <Venemo> I can grab the old version too if needed
May 21 16:32:21 <Venemo> will let you know how it goes, but now I gotta rush off
May 21 16:32:25 <Venemo> see you later! :)
May 21 16:32:28 <DocScrutinizer05> o/
May 21 16:39:15 <DocScrutinizer05> I wonder if a "LD_PRELOAD=./libusb0.1.4_32b.so flasher ..." would work, for a libusb0.1.4_32b.so shipped together with the flasher
May 21 16:40:46 <DocScrutinizer05> hmmm, where to get an "alien" libusb0.1.4 to test that on my system?
May 21 16:41:47 <DocScrutinizer05> I gather the ARM version from maemo won't work on a PC ;-D
May 21 16:44:09 <kerio> qemu-user dat shit
May 21 16:50:11 <enyc> DocScrutinizer05:  http://archive.debian.org/debian/pool/main/libu/libusb/   ??
May 21 16:50:33 <DocScrutinizer05> or https://packages.debian.org/stretch/i386/libusb-0.1-4/download  ;-) thanks anyway
May 21 16:55:09 <DocScrutinizer05> http://paste.opensuse.org/21643108
May 21 16:55:13 <DocScrutinizer05> hmmmmmm
May 21 16:56:13 <DocScrutinizer05> worth it?
May 21 17:00:07 <DocScrutinizer05> http://paste.opensuse.org/74978496
May 21 17:09:25 <DocScrutinizer05> http://paste.opensuse.org/17328428
May 21 18:16:01 <DocScrutinizer05> kerio: enyc: $whoever: could you please test new version of flash-it-all?
May 21 18:16:19 <DocScrutinizer05> ~flashing-cmdline
May 21 18:16:19 <infobot> extra, extra, read all about it, flashing-cmdline is http://mg.pov.lt/maemo-irclog/%23maemo.2016-04-09.log.html#t2016-04-09T01:18:12
May 21 18:34:09 <DocScrutinizer05> anybody around?
May 21 18:57:13 <DocScrutinizer05> anyway, I hope I generally fixed the libusb issue, please let me know if it works for you
May 21 18:57:48 <DocScrutinizer05> (wget http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz -O - 2>/dev/null| tar xvz)&&cd maemo-my-private-workdir&&sudo ./flash-it-all.sh
May 21 19:00:06 <DocScrutinizer05> it's actually working that fast that it took me a 10s until I understood there was no error
May 21 19:00:54 <DocScrutinizer05> downloading and extracting a humble 60kB is really fast nowadays ;-)
May 21 19:19:57 <DocScrutinizer05> added a note to  http://maemo.cloud-7.de/maemo5/patches_n_tools/
May 21 20:40:14 <Pali> interesting.... https://media.blackhat.com/bh-us-11/Miller/BH_US_11_Miller_Battery_Firmware_Public_WP.pdf
May 21 20:40:28 <Pali> apple uses TI bq charging chips inside its batteries
May 21 20:41:21 <Pali> I did not know that it is possible to reflash firmware in bq chips...
May 21 20:41:34 <DocScrutinizer51> it is
May 21 20:42:03 <DocScrutinizer51> when you got access to Vprg pin
May 21 20:43:17 <DocScrutinizer51> thats why may batteries got a hole somewhere, to contact the Vprg
May 21 20:44:09 <DocScrutinizer51> Pali: seen my nasty hack above?
May 21 20:44:19 <Pali> which?
May 21 20:44:45 <DocScrutinizer51> LD_PRELOAD libusb
May 21 20:45:21 <DocScrutinizer51> works :-P
May 21 20:45:48 <Pali> rename libusb file to libusb-0.1.so.4 and then call with LD_LIBRARY_PATH=$PWD ./flasher-3.5
May 21 20:46:04 <Pali> better then LD_PRELOAD
May 21 20:47:08 <DocScrutinizer51> hmm, pondered that, but more complicated
May 21 20:47:42 <Pali> but thats correct, you tell dynamic linker that it should search for libraries in $PWD
May 21 20:48:19 <DocScrutinizer51> just it needs libs from elsewhere too
May 21 20:48:41 <Pali> LD_LIBRARY_PATH are additional libs
May 21 20:48:48 <DocScrutinizer51> ooh
May 21 20:49:03 <Pali> you can also LD_LIBRARY_PATH=$PWD:$LD_LIBRARY_PATH ./flasher-3.5
May 21 20:49:11 <DocScrutinizer51> take precedence over default?
May 21 20:49:19 <Pali> in case you already have something in $LD_LIBRARY_PATH
May 21 20:49:37 <Pali> yes, that path should be preferred
May 21 20:49:41 <Pali> but you can test it
May 21 20:49:51 <Pali> run: LD_LIBRARY_PATH=$PWD:$LD_LIBRARY_PATH ldd ./flasher-3.5
May 21 20:50:10 <Pali> ldd will show you path to all libraries which are loaded
May 21 20:50:18 <DocScrutinizer51> youre prolly right but I was lazy and it seems to work
May 21 20:50:52 <Sicelo009N> nice info there Pali (about batteries)
May 21 20:52:23 <DocScrutinizer51> anyway
May 21 20:52:42 <DocScrutinizer51> ~flashing-cmdline
May 21 20:52:42 <infobot> from memory, flashing-cmdline is http://mg.pov.lt/maemo-irclog/%23maemo.2016-04-09.log.html#t2016-04-09T01:18:12
May 21 20:52:51 <DocScrutinizer51> more than ever
May 21 20:53:34 <KotCzarny> pali: it may be . instead of $PWD
May 21 20:53:46 <Pali> yes, you can use also .
May 21 20:54:44 <DocScrutinizer51> please give it a test
May 21 20:59:17 <DocScrutinizer51> btw the dirty part in that hack is not the ld-preload but delivering an arbitrary lib
May 21 21:00:00 <DocScrutinizer51> regardless of destination system
May 21 21:02:16 <DocScrutinizer51> a minor not so drty hack is the creative use of -u parameter to flasher
May 21 21:07:03 <DocScrutinizer51> and the need for eval came unexpected
May 21 21:08:54 <DocScrutinizer51> what I would like to add but was too lazy is session logs
May 21 21:10:59 <DocScrutinizer51> eval >(tee -a session.log) 2>&q   ??
May 21 21:11:15 <DocScrutinizer51> s/q/1/
May 21 21:11:15 <infobot> DocScrutinizer51 meant: eval >(tee -a session.log) 2>&1   ??
May 21 21:12:05 <DocScrutinizer51> tat however mangles stdout and stderr for the shell
May 21 21:13:31 <DocScrutinizer51> eval >(tee -a session.log) 2>(tee -a session.log >&2) ??   
May 21 21:14:20 <DocScrutinizer51> too lazy
May 21 21:15:55 <DocScrutinizer51> particlarly since whole script has no straight concept of using STDERR
May 21 21:32:12 <DocScrutinizer05> whatever, enjoy
May 21 22:01:11 <DocScrutinizer05> http://wiki.maemo.org/Updating_the_firmware#The_Lazy_Approach
**** ENDING LOGGING AT Sun May 22 02:59:59 2016