IRC log for #maemo on 20121203

00:14.56*** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com)
00:18.53*** join/#maemo guampa (~guampa@unaffiliated/guampa)
00:27.41*** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg)
00:32.37*** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg)
00:40.36*** join/#maemo ALoGeNo (~alogeno@unaffiliated/alogeno)
01:04.45*** join/#maemo thedead1440_ (~chatzilla@cm53.sigma102.maxonline.com.sg)
01:06.08*** join/#maemo dos11 (~dos@unaffiliated/dos1)
01:06.11*** join/#maemo robbiethe1st (~robbiethe@71.221.196.99)
01:32.58*** join/#maemo stardiviner (~stardivin@122.236.253.168)
01:43.06*** join/#maemo dos1 (~dos@unaffiliated/dos1)
02:04.02*** join/#maemo uen| (~uen@p5DCB2719.dip.t-dialin.net)
02:16.47*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
02:19.50*** join/#maemo Jade (~jade@Jade.broker.freenet6.net)
02:19.50*** join/#maemo Jade (~jade@unaffiliated/jade)
02:46.00*** join/#maemo Ken-Young (~Ken@pool-129-44-187-162.bos.east.verizon.net)
03:01.00*** join/#maemo maybeHere (~cl@p5B1661BD.dip.t-dialin.net)
03:18.27*** join/#maemo e-yes (~e-yes@94.45.183.155)
03:35.09*** join/#maemo Smily (Smily@86.61.56.62)
03:39.52*** join/#maemo SmilyOrg (Smily@BSN-61-107-45.dial-up.dsl.siol.net)
03:44.32*** join/#maemo pcfe` (~pcfe@brln-d9ba4589.pool.mediaWays.net)
03:44.33*** join/#maemo pcfe` (~pcfe@redhat/pcfe)
03:55.26*** join/#maemo SmilyOrg (Smily@BSN-61-107-45.dial-up.dsl.siol.net)
04:02.58*** join/#maemo fastlane` (~weezy@115.186.65.70)
04:03.48*** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
04:17.31*** join/#maemo joerg_rw_ (~jr@p549396F7.dip.t-dialin.net)
04:18.54*** join/#maemo SmilyOrg (Smily@BSN-61-107-45.dial-up.dsl.siol.net)
04:49.27*** join/#maemo radic (~radic@dslb-178-002-233-031.pools.arcor-ip.net)
05:03.58kwtm7remind me -- what do I do if the ~/.rtcom-eventlogger/el-v1.db  database fills up, so that response is really sluggish?  (I tried deleting it, thinking the system would just regenerate it, but put it back after 24 hours of malfunctioning horror)
05:16.43*** join/#maemo kwtm7 (~kwtm1@adsl-76-246-18-63.dsl.pltn13.sbcglobal.net)
05:17.56*** join/#maemo githogori (~githogori@c-69-181-109-127.hsd1.ca.comcast.net)
05:20.19Ken-Youngkwtm7, WHat events get logged to that database?
05:35.22kwtm7Ken-Young: mainly phone calls and SMS
05:37.14*** join/#maemo ALo (~alogeno@243.Red-217-125-20.staticIP.rima-tde.net)
05:46.53*** join/#maemo pcfe (~pcfe@brln-4dbadee1.pool.mediaWays.net)
05:46.53*** join/#maemo pcfe (~pcfe@redhat/pcfe)
06:05.58*** join/#maemo kwtm7 (~kwtm1@adsl-76-246-18-63.dsl.pltn13.sbcglobal.net)
06:12.15*** join/#maemo jon_y (~enforcer@2002:3c35:9f73::3c35:9f73)
06:30.14*** join/#maemo Hurrian (~Hurrian@121.54.2.104)
06:31.48*** join/#maemo VDVsx (~VDVsx@194.157.16.35)
06:37.04*** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg)
06:41.39*** join/#maemo valerius (~user@95.153.178.139)
06:52.34DocScrutinizer05kwtm7: http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Maemo-Conversations/td-p/1034177
07:04.23*** join/#maemo ian--- (ian---@78.133.46.19)
07:06.22*** join/#maemo calvaris (~calvaris@12.98.117.91.dynamic.mundo-r.com)
07:06.40DocScrutinizer05kwtm7: it's not exactly about deleting that db
07:07.23DocScrutinizer05but I think with sqlite3 frontend deleting all records should be simple
07:07.30DocScrutinizer05google is your friend
07:15.16DocScrutinizer05kwtm7: another method might be to select "delete conversations" from conversations pulldown menu, then select *all* conversations with ctrl-A from kbd, and click "delete"
07:15.32*** join/#maemo valerius (~user@178.76.208.218)
07:16.14DocScrutinizer05alas same procedure doesn't work for call history
07:18.50DocScrutinizer05so: http://www.sqlite.org/lang_delete.html
07:20.49DocScrutinizer05>>If the WHERE clause is not present, all records in the table are deleted<<
07:21.20DocScrutinizer05in any case, CREATE A BACKUP of ~/.rtcom-eventlogger/el-v1.db !
07:23.05*** join/#maemo jhb (~joerg@e176092029.adsl.alicedsl.de)
07:25.31*** join/#maemo udovdh (~udovdh@pindarots.xs4all.nl)
07:26.09*** join/#maemo _berto_ (~berto@dsl-hkibrasgw4-fe5ef800-28.dhcp.inet.fi)
07:32.31DocScrutinizer05fool's solution ;-): sqlite3 ~user/.rtcom-eventlogger/el-v1.db-backup .dump|grep CREATE|sqlite3 ~user/.rtcom-eventlogger/el-v1.db
07:42.27*** join/#maemo Rantwolf (~rantwolf@2002:d911:cf36:0:753b:433e:98ec:96cd)
07:42.28*** join/#maemo FIQ (~fiq@unaffiliated/fiq)
07:44.37*** join/#maemo e-yes (~e-yes@94.25.130.1)
07:47.48*** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com)
07:49.13*** join/#maemo rcg (~rcg@92.230.52.159)
07:54.43*** join/#maemo edheldil_ (~edheldil@217.31.207.1)
08:00.59*** join/#maemo Pali (~pali@unaffiliated/pali)
08:11.33*** join/#maemo murrayc (~murrayc@ppp-188-174-121-137.dynamic.mnet-online.de)
08:16.31*** join/#maemo Hurrian (~Hurrian@121.54.2.104)
08:18.19*** join/#maemo zhxt (~zhxt@118.26.60.97)
08:23.33*** join/#maemo florian (~fuchs@port-217-146-132-69.static.qsc.de)
08:23.33*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
08:24.51*** join/#maemo pcfe` (~pcfe@brln-d9ba6819.pool.mediaWays.net)
08:24.51*** join/#maemo pcfe` (~pcfe@redhat/pcfe)
08:27.38*** join/#maemo _berto_ (~berto@dsl-hkibrasgw4-fe5ef800-28.dhcp.inet.fi)
08:29.39*** join/#maemo sasquatch (~username@p57958102.dip.t-dialin.net)
08:36.44*** join/#maemo Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz)
08:43.58*** join/#maemo FIQ (~fiq@unaffiliated/fiq)
08:54.32*** join/#maemo ketas (ketas@ketas6-sixxs.si.pri.ee)
09:01.26*** join/#maemo Dibblah (~Dibblah@86.162.107.55)
09:02.57*** join/#maemo eMHa_ (~mh@et-0-30.gw-nat.bs.kae.de.oneandone.net)
09:03.43*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
09:06.08*** join/#maemo Milhouse (~irc_milho@Maemo/community/contributor/Milhouse)
09:10.08*** join/#maemo AD-N770 (~jep@195.10.10.180)
09:10.19*** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl)
09:11.41*** join/#maemo Dragnslicer (~scott@c-76-118-7-184.hsd1.ma.comcast.net)
09:21.19deepyCan I make my N900 stop beeping at night just because the battery is low?
09:21.31deepyI think I jumped up through the roof at 2AM
09:21.54tadzikwow, it beeps on low battery? That's news to me
09:21.57deepyAnd the feelings of guilt from charging my almost full cell instead of the almost empty one didn't subside for at least an hour
09:22.37deepyIt doesn't beep on low battery?
09:25.32DocScrutinizer05errrr http://opencharities.org/charities/1082252
09:25.43DocScrutinizer05hildon foundation
09:26.23*** join/#maemo lbt (~david@63-145-238-4.dia.static.qwest.net)
09:26.23*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
09:26.54DocScrutinizer05tadzik: deepy: sure it makes weird sounds on low battery
09:27.48*** join/#maemo valdyn (~valdyn@valdyn.org)
09:28.39DocScrutinizer05play-sound /usr/share/sounds/ui-battery_low.wav
09:29.27DocScrutinizer05and, **special**: play-sound /usr/share/sounds/ui-recharge_battery.wav
09:30.21DocScrutinizer05deepy: ((Can I make my N900 stop beeping...) sure! power it down, or charge it ;-D
09:31.17tadzikwhispers: "or remove the wav file!" and hides
09:31.51DocScrutinizer05well, that's a possibility to just stop the empty-bat warning
09:32.16DocScrutinizer05the more genuine and sane way though would be to set system-sounds to 0 in settings
09:32.39DocScrutinizer05will affect all system sounds
09:33.41DocScrutinizer05(like charging notification, connection-established notification...)
09:38.47DocScrutinizer05cd /usr/share/sounds/; for f in ui-charging_started.wav ui-connection_lost.wav presence-offline.wav presence-online.wav; do play-sound $f; sleep 1;done;
09:39.06deepyI'll lower the system sounds then
09:39.37DocScrutinizer05play-sound is unrelated to systemsounds volume!
09:40.03DocScrutinizer05just in case you might've pondered to check volume with the line I pasted above
09:41.32DocScrutinizer05for f in /usr/share/sounds/*.wav; do play-sound $f; sleep 1;done;
09:41.34deepyOh I don't have my N900 with me
09:41.36DocScrutinizer05is funny though
09:41.53deepyIt's at home
09:42.35tadzikstationary phone? :)
09:43.22*** join/#maemo eijk (~eijk@85.178.220.60)
09:44.24DocScrutinizer05and the diagnostic output is hilarious
09:44.27DocScrutinizer05ca_context_play_full (vol -0.000000): Success
09:44.28DocScrutinizer05callback called, error 'Success'
09:45.36deepyWell, I need to have 3G to even get a signal with Meteor :p
09:48.17*** join/#maemo kolp (~quassel@212.255.224.138)
09:53.18*** join/#maemo drussell (~dave@cpc1-brom10-2-0-cust341.16-1.cable.virginmedia.com)
09:55.12Palideepy, open control panel, then profile settings and set system sounds to 0 or off
09:55.37Palibattery low volume level is stored in profiled daemon settings
09:55.48Paliin some system sound key
09:57.04PaliI'm using Timed Silencer application where can be configured switching to silent profile at night
09:57.19Pali(it using alarmd for executing commands)
09:57.48deepyCheers, but Doc beat you to it :-P
09:57.56PaliDocScrutinizer05, ^^^^ another good feature of alarmd :D
09:57.58deepyWell, the first line, the rest was interesting on it's own though
09:58.06*** join/#maemo mvp_ (~mvp@port463.ds1-abc.adsl.cybercity.dk)
10:04.02*** join/#maemo dimir (~dimir@dimir.eu)
10:04.06dimirHello there!
10:04.09DocScrutinizer05I prefer alarmed for that
10:04.46DocScrutinizer05sounds more universal purpose than Timed Silencer application
10:05.04dimirQuick question. I was wondering how easy it is to change the n900 motherboard by myself. I'm not an expert in these things but was wondering should I trust this operation to the specialist or it's safe to do that at home?
10:05.52dimirThe thing is, on my n900 the GSM-module died. I have found the guy that has broken display on his n900 and willing to sell it cheap. I need to make sure his motherboard is fine before buying it.
10:06.38DocScrutinizer05swap is simple
10:06.57dimirYou mean swapping the motherboard?
10:07.05DocScrutinizer05making sure that this mainboard is OK is a tad more demanding task
10:07.10DocScrutinizer05yep
10:07.14dimirAh.
10:07.15dimirShit.
10:07.46dimirIs there something you could recommend?
10:07.48dimirWhat would you do?
10:08.02dimirHe is selling his n900 for 40$ USD.
10:08.04DocScrutinizer05get the board, swap, see if everything ok
10:08.17dimirHow much time would it take?
10:08.26dimirI wouldn't want to hold the seller for an hour. :-D
10:08.29DocScrutinizer0560min
10:08.32dimirAh
10:08.33dimirShit.
10:09.00DocScrutinizer05you might be able to swap screen half in 20 min
10:09.08dimirAlright, I'll give him a call and find out if his display shows at least something.
10:09.10DocScrutinizer05depending on luck and experience
10:09.17dimirExperience is almost 0.
10:09.45DocScrutinizer05separating kbd and screen half takes ~5 min
10:10.09DocScrutinizer05but plugging in the flex cable connector again may cost you your last hair
10:10.25DocScrutinizer05or might as well be a matter of 20s
10:11.06DocScrutinizer05I'd get a screen-broken N900 for 40 bucks any time
10:11.24DocScrutinizer05for 30 for sure
10:11.39DocScrutinizer05s/get/buy/
10:11.54chem|st+1
10:12.06dimirHeh, hes device has no display at all. :-D
10:12.07DocScrutinizer05only with working USB though
10:12.45dimirAh.
10:12.58dimirSo in general I could take the risk.
10:12.59dimirGood.
10:13.02chem|stdimir: you can check if everything is working by attaching it to a tv for example
10:13.04DocScrutinizer05ooh, even better. that might mean the screen / display is OK and only main flex connector is defect
10:13.25DocScrutinizer05chem|st: doesn't work with FPC defect
10:13.30DocScrutinizer05don't ask me why
10:13.36dimir:-D
10:13.56dimirWell, he said he sat on it and the display glass broke. So he took it apart.
10:13.57chem|stDocScrutinizer05: darn that worked with the broken N9
10:14.06dimirI don't know what does it mean exactly.
10:14.06DocScrutinizer05but you should see proper ENUM in syslog when pluggin in to PC's USB
10:14.41dimirSo, in general, swapping the MB is less risk, right?
10:14.43DocScrutinizer05*sigh* so maybe it's not really worth 40 bucks
10:14.51dimirDo I need some special screwdriver for that or anything?
10:14.56dimirIs there a howto for that?
10:14.56dimir:-)
10:15.00dimirI guess there is on youtube.
10:15.01DocScrutinizer05yes, yes
10:15.06DocScrutinizer05nope
10:15.13DocScrutinizer05well, possibly
10:15.19chem|stP0 and T5 iirc
10:15.27DocScrutinizer05TX6
10:15.32DocScrutinizer05and Ph0
10:15.34chem|stoh 6 it was...
10:15.36*** join/#maemo setanta (setanta@nat/indt/x-pcutujmrbejvwbnu)
10:15.48*** join/#maemo calvaris (~calvaris@fanzine.igalia.com)
10:16.01dimirhttp://www.youtube.com/watch?v=aVEHm325-z8 n900 disassembly
10:16.08chem|stin long Philips0 and Torx6
10:16.45DocScrutinizer05MEH http://www.tehkseven.net/news/nokia-news/nokia-n900-disassembly/ ->404
10:17.23DocScrutinizer05google for N900 L1_L2
10:17.37dimirPH0 and T6 says in the video.
10:18.09*** join/#maemo zap_ (~zap@94.25.229.80)
10:18.30DocScrutinizer05forget all those videos, they often are missleading
10:19.11dimirOK. Well, thanks a lot for the info. I think I'll first practice a bit at home and then when I meet the guy I do the swap quicker.
10:19.17DocScrutinizer05ouch, the tehkseven vid
10:19.26dimirWhich one?
10:19.36DocScrutinizer05yours
10:19.50DocScrutinizer05same as my dead link, but it's no good video
10:20.05DocScrutinizer05get service manual L1_L2
10:20.06dimirIt's no good?
10:20.28DocScrutinizer05nope, it neglects some important details
10:21.05DocScrutinizer05and it does nonsense
10:21.39dimirI got the manual, thanks.
10:21.48*** join/#maemo shamus (~shamus@ip-206-192-195-49.marylandheights.ip.cablemo.net)
10:21.58DocScrutinizer05nonsense: removing the "I'm not sure what's that" GSM antenna. Neglect: "please be careful with that one"
10:22.20dimir:-D
10:23.00DocScrutinizer05you probably don't want to disassemble the screen assembly half at all
10:25.00dimiryeah.
10:25.37DocScrutinizer05just *carefully* unplug the flat plastic connector ribbon from mainboard, and swap screen completely
10:26.03DocScrutinizer05don't bend or pull the flat plastic connector
10:26.27DocScrutinizer05they call it main flex connector iirc
10:28.31DocScrutinizer05but honestly, when that guy planted his fat back on the screen so it cracked, then disassembled it and wrecked it some more, it's questionable if that device is still worth 40 bucks
10:29.13DocScrutinizer05at very least connect his device to a linux PC and check PC's syslog
10:29.28DocScrutinizer05so you can be sure the board is semi-alive at least
10:29.36DocScrutinizer05incl USB
10:30.32dimirAh, good idea. I'll take my notebook with me.
10:31.05DocScrutinizer05and a charged BL-5C
10:31.05dimirWell, what wonders me, he said the device works properly, I wonder how did he conclude that.
10:31.17dimirDocScrutinizer05: the battery?
10:31.20DocScrutinizer05yep
10:31.49DocScrutinizer05odds are his battery is depleted and without battery it won't really boot
10:32.41DocScrutinizer05put a mark on yours, so you don't swap it
10:33.08DocScrutinizer05dimir: German?
10:33.49DocScrutinizer05prolly not
10:33.55*** join/#maemo M4rtinK2 (~M4rtinK@mail.melf.eu)
10:36.32DocScrutinizer05BL-5J, sorry
10:36.55*** join/#maemo Hurrian (~Hurrian@121.54.2.104)
10:40.07*** join/#maemo andre__ (~andre@ip-84-42-203-5.net.upcbroadband.cz)
10:40.07*** join/#maemo andre__ (~andre@wikimedia/aklapper)
10:41.03*** join/#maemo theheadofabroom_ (~theheadof@109.204.120.170)
10:45.32*** join/#maemo mpthx (~mpthx@support.leaseweb.net)
10:46.02dimirDocScrutinizer05: me? No. :-D
10:46.52dimirDocScrutinizer05: Thanks for a hint on mirking my MB. He promised to try to connect his phone to a PC to see if it works. He said after the accident he has put it back to the box where it's been for 1 year.
10:48.29DocScrutinizer05I meant your battery though ;-)
10:49.38DocScrutinizer05actually mainboard defects might easily be caused by too much mechanical stress, like someone sitting on the device
10:51.00DocScrutinizer05it seems that often the soldering balls of BGA chips disconnect, probably caused (among others) by bending the PCB while chips can't be bent
10:53.30DocScrutinizer05anyway, good luck!
10:54.45*** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it)
10:57.28*** join/#maemo thetet (~raggam-nl@ELE-130.mur.at)
11:00.54*** join/#maemo lizardo (lizardo@nat/indt/x-faitfojptnruqrgy)
11:06.14Aoyagi_joytophttp://www.theregister.co.uk/2012/12/03/apple_charging_patent/
11:15.25Skryyeah, madness
11:16.00Aoyagi_joytopThe top comment is nice.
11:16.09Aoyagi_joytop"I think Nikola Tesla may have a few things to say on applying power at a distance wirelessly.."
11:18.33SkryYup :D I read somewhere that some parties are already negotiating about possibility of patenting (human) genes, in simple terms.
11:18.38*** join/#maemo FlameReaper-PC (~FR@203.106.66.65)
11:20.02Aoyagi_joytopSure, let's patent breathing :D
11:23.27Skryit's coming.. :)
11:36.27*** join/#maemo Chiku|dc (~Chiku01@unaffiliated/chiku)
11:42.42*** join/#maemo mpthx (~mpthx@support.leaseweb.net)
11:52.43ShadowJKthere are already gene patents I think?
11:57.59chem|stwasn't it tesla who said it is no problem to power a town OTA?
11:59.47HurrianLet's patent a "method of filing exclusive rights by a recognized authority, to concepts pertaining to machines and methods", and torpedo every patent holder in existence.
12:01.26chem|stHurrian: patent education and sue 1 year old children's parents!
12:02.17chem|stthat would at least lead to an end!
12:03.27chem|stI am fed with all those "The first foobar ever" commercials by apple...
12:04.10Hurrian"A method of absorption of information from sources recognized by an apparatus, which by mechanical, chemical, electromagnetic or analogous means classifies and relates the information obtained into a database"
12:04.30Hurrianoh man, that's loaded with so much buzzwords the patent office has to accept that
12:04.53jon_yWireless Charging? Will there be a backlash like wifi? :)
12:05.02jon_ysurely it is higher power than wifi
12:05.18jon_yspread the word, Apple causes cancer! :)
12:05.22Aoyagi_joytopIt's not really related, me thinks.
12:05.32chem|stjon_y: 2 different things
12:05.43jon_ywell, people think EM causes cancer
12:05.52Aoyagi_joytopPeople are idiots, end of story.
12:06.09Hurrianchem|st: THEY'RE SENDING POWER OVER THE AIR! SORCERY, I TELL YOU! RAISE YOUR PITCHFORKS!
12:06.14jon_yright, so I was wondering if the same idiots will make noise
12:06.39Aoyagi_joytopNoise is all they can do as we have superior technology :P
12:06.42jon_yalso, cellphone emission cancer
12:06.56chem|stHurrian: ouh in saudi arabia you get stonewalled for that
12:07.02jon_ycancer everything :)
12:07.05Hurrianit's inevitable - someone even called RFID tags the mark of the devil, iirc.
12:07.22Aoyagi_joytop"If you like, put an egg on your cellphone, it like, totally cooks the egg"
12:07.24Hurriannot to say that tracking isn't bad, but the dude literally said it was the mark of the devil, see the bible.
12:07.44jon_yI am a very model of an infrared range radioactive source
12:08.06jon_ysurely I cause cancer by being in the same room :)
12:08.15Aoyagi_joytopand actually
12:08.20Aoyagi_joytopshe said "I feel it's the implementation of the Mark of the Beast"
12:08.23Hurrianjon_y, so, if you're a cancer causing IR source, what isn't?
12:08.24Hurrian;)
12:08.46jon_yI was just wodering how they'd freak out :)
12:08.49HurrianEVERYTHING CAUSES CANCER! RUN FOR YOUR LIVES AND UNMUTATED CELLULAR NUCLEI!
12:08.52Aoyagi_joytopOh and I thought this was a different channel :D
12:08.59chem|styou are definetely a source... of what kind is to be determined
12:09.46chem|stwell back to charging OTA
12:10.17chem|sthas s/o tried to reassamble a wireless charger to a n900's backpanel?
12:10.34ShadowJKfinds it amusing that 666 is a mistranslation
12:11.07chem|stShadowJK: so what...
12:11.08Aoyagi_joytopMost of the bible things are.
12:11.11jaskadclxvi!
12:11.19jon_yaww, Jewish numerology
12:11.57ShadowJKYou'd think since it's like almost only exact figure in the whole book people would've paid more attention to get it right
12:12.08*** join/#maemo mpthx (~mpthx@support.leaseweb.net)
12:14.53Aoyagi_joytopThey are Catholics, they don't question. They accept.
12:15.35*** join/#maemo etrunko (~etrunko@134.134.137.73)
12:16.30kolpchem|st: I just got myself 2 spare palm pre backcover sto take apart and put into the n900 to use with my touchstone charger
12:17.03chem|stkolp: pictures?!
12:17.14chem|stkolp: keep the community posted
12:17.35kolpIt's not done yet. :) There's an old thread on TMO where someone achieved that
12:18.42kolpchem|st: http://talk.maemo.org/showthread.php?t=56950
12:24.03*** join/#maemo Hoolxi (~Openfree@120.204.177.18)
12:29.29*** join/#maemo vi_ (~vi_@87.115.161.232)
12:38.21*** join/#maemo Flyser (~flyser@unaffiliated/flyser)
12:49.58*** join/#maemo krau (~krau@2001:4830:2446:ff00:4687:fcff:fea6:5117)
13:10.46*** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl)
13:22.17*** join/#maemo guampa (~guampa@unaffiliated/guampa)
13:24.49*** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg)
13:30.26*** join/#maemo Flyser (~flyser@unaffiliated/flyser)
13:32.22*** join/#maemo NeutrinoPower (~neutrino@HSI-KBW-078-042-069-207.hsi3.kabel-badenwuerttemberg.de)
13:38.41*** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net)
13:49.36*** join/#maemo vi_ (~vi_@87.115.161.232)
13:52.09*** join/#maemo Pali (~pali@unaffiliated/pali)
13:59.31*** join/#maemo jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)
14:07.22*** join/#maemo Araya (~ircchatte@92.37.189.129)
14:07.48*** join/#maemo Smily (Smily@89.142.208.225)
14:15.14JaffaGeneralAntilles: ping
14:16.01*** join/#maemo cehteh (~cehteh@pipapo.org)
14:16.12cehtehhi
14:18.24fastlane`hi
14:18.42cehtehmy n900 loosing wlan connection and cant reconnect until i reboot it since some time, anyone of you heared of this issue?
14:20.53cehtehgoing out of range, switching to wwan .. coming back and it wont reconnnect
14:34.25r00t|homenever had such problems...
14:34.32r00t|homedoes it just not scan for wlans/try to connect?
14:34.39r00t|homeor does it try and fails?
14:34.49*** join/#maemo teotwaki (~teotwaki@Maemo/community/contributor/crashanddie)
14:35.04teotwakiSo, massive fail.
14:36.00teotwakiI developed a new function on one of our products, testing it quickly, build an rpm, send it to the test environment, play with it. Small problems, fine tune it... aaaaand, stuck. Bug. Regression. No data is detected anymore, parsing errors everywhere.
14:37.07teotwakiMy direct co-worker starts looking with me, we find a quick helper function that always returns 1, for some reason, so we add a breakpoint in that function, test it, breakpoint doesn't get triggered. Ok, wanna play? I add a delete (char *) 0x12345678; compile, test again, no coredump.
14:37.14teotwakiOk, wait, what?
14:37.51teotwakiI check the gcc/clang version, maybe some newfangled noob error handling that prevents you from coredumping by your own accord, I decide to simply to a cout to see what the values are, disregarding the logging system. Nothing.
14:38.00teotwakiTurns out, we were adding code *after* the return line.
14:38.28teotwakiSo, that's all nice, we now see the values, but they still don't add up. How can 84 - 16 = 1?
14:38.43teotwakiTurns out I wrote "bool", instead of unsigned long int.
14:38.59dimir[12:53] <DocScrutinizer05> anyway, good luck! <- Thanks! :-)
14:41.44*** join/#maemo ArGGu^^ (~ArGGu^^@a88-112-164-9.elisa-laajakaista.fi)
14:47.01*** join/#maemo Timo (~Timo@unaffiliated/tiempjuuh)
14:51.31*** join/#maemo dos1 (~dos@unaffiliated/dos1)
14:52.50*** join/#maemo at1as (~at1as@kurios.r4780y.com)
14:54.15*** join/#maemo Timo_ (~Timo@195-241-167-194.ip.telfort.nl)
14:56.32*** join/#maemo lizardo (lizardo@nat/indt/x-kcmmstlxahbvinhv)
15:00.28*** join/#maemo SmilyOrg (Smily@89.142.208.225)
15:02.49*** join/#maemo Dibblah (~Dibblah@86.162.107.55)
15:02.54*** join/#maemo konelix (~konelix@200.119.153.107)
15:03.43*** join/#maemo Darkchaos (~darkchaos@i59F7A2AB.versanet.de)
15:05.46GeneralAntillesJaffa, pong?
15:06.53vi_I have found a novel way of keeping the squirrels out of my bird feeder.
15:07.05vi_I have covered the pole in goosefat.
15:07.23vi_Now they jump on and try to climb but slide down.
15:07.36GeneralAntillesHaha
15:07.44GeneralAntillesFriend of mine tried a bunch of stuff for his hanging feeder
15:07.46vi_But now I have greasy squirrels :/
15:08.07GeneralAntillesfinally settled on buying the cheap stuff in bulk from CostCo and putting that on the ground.
15:08.12GeneralAntillesand giving the quality seed to the birds.
15:08.25vi_try mixing in chilli seeds.
15:08.33vi_the birds DGAF.
15:08.37GeneralAntillesvi_, you should hire an oil spill recovery team to clean up your squirrels.
15:08.43vi_the squirrels shit themselves.
15:09.55jaskaheh, squirrels will hang upside down to get to the seeeeed
15:20.53*** join/#maemo Timo (~Timo@unaffiliated/tiempjuuh)
15:26.52*** join/#maemo kwtm7 (~kwtm1@adsl-76-246-18-63.dsl.pltn13.sbcglobal.net)
15:27.38*** join/#maemo NishanthMenon (~nmenon@192.94.92.14)
15:30.23*** join/#maemo VDVsx (~VDVsx@a88-112-254-211.elisa-laajakaista.fi)
15:32.46*** join/#maemo int_ua (~int_ua@159.146.169.15)
15:32.58vi_uk dvla.  utter SCUM.
15:34.04int_uaHi. I have four hildon-desktop core dumps in a row. CSSU Tmaemo6. Where should I send them? Leaving in 5 minutes
15:35.23*** join/#maemo Timo (~Timo@unaffiliated/tiempjuuh)
15:36.49*** join/#maemo konelix (~konelix@200.119.167.114)
15:40.50*** join/#maemo ab (~ab@pdpc/supporter/professional/ab)
15:41.26*** join/#maemo radic (~radic@dslb-178-002-233-031.pools.arcor-ip.net)
15:42.49*** join/#maemo drussell (~dave@217.194.73.202)
15:45.37*** join/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz)
15:51.33*** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG)
16:07.19*** join/#maemo pcfe` (~pcfe@brln-4d0ccf52.pool.mediaWays.net)
16:07.19*** join/#maemo pcfe` (~pcfe@redhat/pcfe)
16:10.18*** join/#maemo konelix (~konelix@200.119.180.209)
16:16.09*** join/#maemo ZogG (~zoggrules@funtoo/user/ZogG)
16:16.34*** join/#maemo vi____ (~user@87.115.161.232)
16:17.22vi____who wants to help a gnoob compile some code?
16:17.28vi____That is me by the way.
16:20.51vi____who was the guy here who suggested the use of codeblocks as a C IDE?
16:21.13kolpvi____: Might have been me
16:21.20vi____aah, yes!
16:21.27kolpDepending on what your impression is ;)
16:21.30vi____You have jsut volunteered yourself!
16:21.36vi____http://www.imagemagick.org/script/magick-wand.php
16:21.42vi____^how do I compile that?
16:22.09vi____I see I need to get the magickwand library, however I am not sure where I have to put it.
16:22.24vi____I am using debian BTW.
16:22.45kolpYour using c::b on debian?
16:22.51vi____yes.
16:22.56vi____Is that...bad?
16:22.59Aoyagiyou're
16:23.40vi____Aoyagi, yes...
16:23.42kolpI guess not. I've never used an IDE on linux for writing code
16:23.57vi____kolp.  aah.
16:24.23kolpWell, you can put that lib wherever you want
16:24.35kolpI guess it would be easiest to install the -dev package
16:25.32Aoyagivi____: I was correcting kolp, sorry, reflex.
16:25.53*** join/#maemo valerius (~user@95.153.169.219)
16:26.03kolpAoyagi: Thanks, just a typo, I know the rules ;)
16:26.59AoyagiWell, no problem, I can get annoying with that and eventually even banned :D
16:28.23*** join/#maemo otep (~quassel@AP-203.167.4.11.sysads.com)
16:28.59kolpvi____: Btw, are you trying to cross-compile for maemo?
16:30.11*** join/#maemo rm_work (~rm_you@johnx.xen.prgmr.com)
16:30.11*** join/#maemo rm_work (~rm_you@Maemo/community/cssu/rm-you)
16:32.08*** join/#maemo Jaded (~jade@Jade.broker.freenet6.net)
16:32.08*** join/#maemo Jaded (~jade@unaffiliated/jade)
16:32.16vi____kolp, no.  I have SB for that.
16:32.30vi____I am trying to write a firmware patching utility.
16:33.21vi____i.e. a program that will load a firmware file and replace a certain number of bytes starting at a particular offset.
16:33.45vi____If you know of any example code you could point me too, I would be very grateful.
16:37.15kolpShouldn't be too difficult. You'd just mmap that file and modify those bytes
16:41.28vi____mmap?
16:42.52*** join/#maemo thedead1440_ (~chatzilla@cm53.sigma102.maxonline.com.sg)
16:43.20*** join/#maemo NIN101 (~NIN@p5DD28F14.dip0.t-ipconnect.de)
16:43.55*** join/#maemo Darkchaos2 (~darkchaos@i59F7A2AB.versanet.de)
16:44.13*** join/#maemo dimw1t (~at1as@kurios.r4780y.com)
16:45.01kolpUsed for memory-mapped I/O. I.e. you don't read the whole file into memory but just the chunk you want to access
16:45.10kolpvi____: Check man mmap
16:45.52*** join/#maemo guly_ (~why@shivaya.guly.org)
16:46.12*** join/#maemo peetah_ (~peetah@cha92-9-82-236-202-86.fbx.proxad.net)
16:46.23*** join/#maemo tchell_ (~mitchell@unyew.silverninja.net)
16:49.43*** join/#maemo FredrIQ (~fiq@unaffiliated/fiq)
16:51.39*** join/#maemo lbt (~david@63-145-238-4.dia.static.qwest.net)
16:51.39*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
16:52.25*** join/#maemo Cor-Ai_ (~cor-ai@212.112.62.30)
16:53.57*** join/#maemo lbt (~david@63.145.238.4)
16:53.57*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
16:54.49*** join/#maemo realitygaps (~realityga@static.146.244.9.176.clients.your-server.de)
16:54.50*** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps)
16:56.47vi____fuck C::B
16:56.53vi____fucking piece of fucking shit.
16:57.13vi____I will compile it myself.
16:57.22vi____From sh.
16:58.11*** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net)
16:58.20*** join/#maemo e-yes (~e-yes@94.25.130.1)
16:59.37r00t|homevi____: xxd or dd or such can easiy be used for patching
17:01.10*** join/#maemo amospalla (~amospalla@amospalla.es)
17:08.12*** join/#maemo lbt_ (~david@63-145-238-4.dia.static.qwest.net)
17:08.12*** join/#maemo lbt_ (~david@Maemo/community/contributor/lbt)
17:11.45*** join/#maemo freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
17:15.04*** join/#maemo juozapas (~juozapas@78-61-169-218.static.zebra.lt)
17:15.31juozapashi how to disable turning control? after last cssu upgrade it's total mess
17:15.46juozapasorientation lock doesnt help
17:21.32*** join/#maemo valerius (~user@85.26.180.179)
17:26.20*** join/#maemo githogori (~githogori@c-69-181-109-127.hsd1.ca.comcast.net)
17:29.14*** join/#maemo ced117 (~ced117@AStrasbourg-552-1-148-236.w86-204.abo.wanadoo.fr)
17:29.14*** join/#maemo ced117 (~ced117@opensuse/member/ced117)
17:35.06*** join/#maemo FIQ (~fiq@unaffiliated/fiq)
17:59.44*** join/#maemo Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz)
18:06.52*** join/#maemo niklaus (~niklaus@90-168-213-213.static.zapp.ch)
18:06.59niklaushello everyone.
18:08.01niklausI got a problem: I changed the device lock code on My Nokia N9 and forgot it. That's a bit of a problem! though! I still have SSH access to the device (via the developer account) and can gain root access. Does anyone know how I can reset/disable the device lock from ssh?
18:08.37*** join/#maemo konelix (~konelix@200.119.170.54)
18:09.38kerioniklaus: you'll probably find more help in #harmattan
18:12.59niklauskerio: thx
18:13.02*** part/#maemo niklaus (~niklaus@90-168-213-213.static.zapp.ch)
18:18.47*** join/#maemo ufa (~ufa@fedora/ufa)
18:18.52ufahello :)
18:19.17ufaI am trying to flahs my n900. but the nokia image page does not seem to work :(
18:19.28ufadoes anyone knows an alternative location?
18:19.47*** join/#maemo eMHa_ (~mh@HSI-KBW-5-56-244-117.hsi17.kabel-badenwuerttemberg.de)
18:20.43*** join/#maemo konelix (~konelix@200.119.166.167)
18:20.52ufaI am trying to download the flasher too, but not working too
18:25.11r00t|homeufa: the licensing of the nokia images not allow redistribution
18:26.20*** join/#maemo lbt_ (~david@63-145-238-4.dia.static.qwest.net)
18:26.20*** join/#maemo lbt_ (~david@Maemo/community/contributor/lbt)
18:27.51*** join/#maemo Chiku|dc (Chiku01@unaffiliated/chiku)
18:29.00*** join/#maemo Flyser (~flyser@178-25-3-60-dynip.superkabel.de)
18:29.00*** join/#maemo Flyser (~flyser@unaffiliated/flyser)
18:29.53*** join/#maemo konelix (~konelix@190.143.249.100)
18:32.24*** join/#maemo Sazpaimon (wat@unaffiliated/Sazpaimon)
18:40.52*** join/#maemo konelix (~konelix@190.143.170.69)
18:45.57*** join/#maemo NishanthMenon (~nmenon@cpe-24-27-111-228.tx.res.rr.com)
18:46.41*** join/#maemo NishanthMenon (~nmenon@cpe-24-27-111-228.tx.res.rr.com)
18:52.46*** join/#maemo lbt_ (~david@63-145-238-4.dia.static.qwest.net)
18:52.50*** join/#maemo lbt_ (~david@Maemo/community/contributor/lbt)
18:54.28*** join/#maemo calvaris (~calvaris@12.98.117.91.dynamic.mundo-r.com)
18:56.03*** join/#maemo konelix (~konelix@190.143.239.146)
18:58.45*** join/#maemo ufa (~ufa@fedora/ufa)
19:05.10*** join/#maemo at1as (~at1as@74.204.38.163)
19:15.40FIQhmm
19:16.00FIQcan I somehow avoid the "hey, you clock is reset, go fix it NAO"-screen?
19:16.13FIQif my clock is reset, I'll see that as soon as I startup anyway
19:16.32FIQand I really don't like that screen, it just wastes my time with useless junk (at least that's how I see on it :D)
19:17.10FIQi believe this thing is called "hildon-welcome"
19:17.15FIQmight be wrong on that though
19:18.45*** join/#maemo Milhouse (~irc_milho@Maemo/community/contributor/Milhouse)
19:19.58vi____FIQ, it is called osso-startup-wizard
19:20.10FIQoh ok
19:20.13vi____FIQ, You can apt-get purge it
19:20.13FIQbut well...
19:20.20vi____but well what.
19:20.25FIQ...will my device boot fine afterwards? :P
19:20.34vi____dunno.
19:20.42vi____Depends how you have made your device!
19:20.46FIQI'd rather not TIAS then
19:20.52vi____I have removed it from my device.
19:20.58vi____WFM
19:21.00vi____YMMV
19:21.00FIQoh, and it worked fine?
19:21.11vi____Yup.
19:21.17FIQeven on an instance in which it's called (normally)?
19:21.18vi____You have to set the clock by hand though.
19:21.22FIQyeah ofc
19:21.35FIQ(not that I would need to do that anyway, it doesn't do it for me)
19:21.41FIQ*wouldn't
19:21.53vi____It works for me.
19:21.57FIQhmm
19:22.06FIQi'll make a BM backup just in case
19:22.06vi____There was some discussion yesterday as to the best ways to replace it.
19:22.29FIQi need to do it anyway, was long time ago last time
19:22.43vi____I use a zenity dialogue that lets me type in the time/date like: MMDDhhmmYY
19:22.58FIQoh another stupidity with this thing
19:23.11vi____r00t|home made a rather nice event.d script that used nptime server.
19:23.13FIQit lags horribly when setting time/date
19:23.35FIQunlike when you do it from the settings menu (why is there 2 different ones anyway??)
19:24.03vi____FIQ, Because the osso-startup-wizard is a standalone program that has to run in a raw matchbox session.
19:24.20vi____Where as the settings menu one is a settings menu plugin.
19:24.33FIQI guess I can live with that explanation
19:25.19r00t|home<r00t|home> vi____: xxd or dd or such can easiy be used for patching
19:25.44vi____I need to write a standalone C program.
19:25.51r00t|home<r00t|home> wget http://www.math.ucla.edu/~jimc/nokia770/dists/mistral/user/binary-armel/system-tools/ntpdate_4.2.0a+stable-9_armel.deb
19:25.51r00t|home<r00t|home> vi_: http://pastebin.com/CCuMgLkX
19:26.13r00t|home<kerio> ohoho, busybox-power has ntpd
19:26.14r00t|home<kerio> r00t|home: ntpd -dnq -p pool.ntp.org
19:26.36vi____FIQ, ^that beauty right there.
19:26.57FIQi'm quite happy with the answer to my question, was expecting it to be too tightly bound to the system and render it unbootable if I simply removed it
19:26.58r00t|homemany improvements have been suggested already
19:27.02FIQvi_: i'll look into it
19:27.20vi____well screendump the stuff r00t just pasted.
19:27.27kerioFIQ: if removing it makes the system unbootable, then it's a bug
19:27.34keriobecause it's not depended upon by stuff
19:27.34FIQkerio: ok :P
19:27.43FIQwell I did a BM backup anyway
19:27.54FIQ(i need to do it anyway, was too long ago last time)
19:28.42r00t|homekerio: DocScrutinizer does NOT agree with such an interpretation
19:28.55FIQso let's see
19:29.15kerioDocScrutinizer is a grumpy old man
19:29.20r00t|homekerio: he pointed out before that running 'apt-get autoremove' will make your system unbootable
19:29.23kerioDocScrutinizer05: :3
19:29.26FIQi do this bm backup, boot maemo, remove this POS, install that deb, then do what exactly with the pasted configuration file?
19:29.28*** join/#maemo rcg (~rcg@92.230.52.159)
19:29.32kerior00t|home: it won't, actually
19:29.34keriocssu fixed that
19:29.36FIQi've actually done that
19:29.42FIQw/o an unbootable system
19:29.46r00t|homeFIQ: the file goes in /etc/event.d/ntpdate
19:29.47FIQhowever I heard it broke SIP
19:29.50FIQ...which I don't use
19:29.52kerioFIQ: it used to break SIP
19:29.53r00t|homeFIQ: ah, yes, that
19:30.04FIQso essentially it affected me zero
19:30.16kerioCSSU now "manually installs" the things in the metapackage
19:30.18FIQeven though it probably broke SIP for me
19:30.21kerioof course when you remove them, you remove them
19:30.28vi____FIQ, you know linux right?
19:30.29kerioFIQ: it didn't, if you installed cssu beforehand
19:30.42kerioFIQ: use ntpd from busybox-power, it's easier
19:30.47FIQvi_: i'm confident with linux yes
19:30.55FIQkerio: hmm ok
19:30.55vi____aah. then you will be fine!
19:31.00keriohell, just install an event file for ntpd
19:31.08kerioit'll fix the time once you connect to the internet
19:31.12kerio(maybe)
19:31.14*** join/#maemo florian (~fuchs@Maemo/community/contributor/florian)
19:31.50ufaI am trying to flash my n900. but the nokia download page does not seem to work :(
19:32.06FIQkerio: well, I'll most likely set the time manually on boot if i've no internet access :P
19:32.14*** join/#maemo jonne|reconnecte (~jonne@109.133.81.71)
19:32.15FIQas I don't like n900 showing weird time
19:32.25*** join/#maemo Elfix (elfix@wikipedia/pdpc.21for7.elfix)
19:32.43FIQ(not that manually will set it right on second, but in that case, +/-5min is better than +/-5h
19:32.45FIQ)
19:32.57kerioFIQ: i just don't see how it's slower to set it from the worldclock
19:33.07kerioor from xterm
19:33.40vi____or put a zenity dialogue in xsession.post
19:33.41FIQthere we go, bm done
19:34.29keriovi____: why?
19:34.40keriothe system is booted at that point, every damage done by the date has been done already
19:35.18vi____kerio, not the damage to my face.
19:35.31vi____where I see it is 00:00
19:36.25FIQhm
19:36.33FIQthe purge was semi-successful
19:36.44vi____semi?
19:36.45FIQit didn't purge properly, as it failed to remove /var/lib/osso-startup-wizard/
19:36.49DocScrutinizer05purge is nonsense
19:37.07DocScrutinizer05you don't need to purge the packages to fix the initscript
19:37.13FIQshould be safe to just remove the directory I guess
19:37.41DocScrutinizer05neither is it warranted that purging will fix the initscript for you
19:37.43FIQ(and the file within)
19:38.21*** join/#maemo Jade (~jade@Jade.broker.freenet6.net)
19:38.21*** join/#maemo Jade (~jade@unaffiliated/jade)
19:39.08vi____FIQ, alternativley you could just comment out the starting of the osso-startup-wizard in the Xsession.d scripts.
19:39.21FIQoh you say that now... :p
19:39.31FIQi've already removed it
19:39.47FIQbut well, as that line would just throw an error, I guess I can comment it out anyway
19:39.53vi____It makes no difference.
19:40.14FIQso let's see here
19:40.30vi____what line?
19:40.48FIQs/line/part/
19:41.05FIQAnyway
19:41.33FIQosso-startup-wizard removed, now to install busybox-power
19:42.01FIQand make ntpd autostart with the pasted script
19:43.45FIQhttp://pastebin.com/CCuMgLkX hm
19:43.47*** join/#maemo NeutrinoPower (~neutrino@HSI-KBW-078-042-069-207.hsi3.kabel-badenwuerttemberg.de)
19:45.03kerioFIQ: we need some testing though
19:45.20kerioboot with the time set to 2000 01 01 00 00 and then start busybox's ntpd
19:45.26FIQdoes busybox-power need a reboot..?
19:45.27keriosee if the time is eventually fixed
19:45.30kerioFIQ: no
19:45.54FIQwell I started a new shell and it still reported old (vanilla) version of busybox
19:46.01FIQi'll see if I did something wrong
19:47.06FIQah, guess I misread the startup text.. w/e
19:47.11kerioare you sure there wasn't a -power? :)
19:47.12kerioheh
19:47.53vi____does anyone know of a irc room that is for C coding enthusiasts?
19:48.03kerio##c maybe
19:48.23FIQhowever there seems to be no ntpd..
19:48.26vi____Cannot join ##c (You are banned).
19:49.11FIQ"ntpd: not found.", and "help" (I don't use busybox normally but I think it echoes every known busybox command) doesn't mention it
19:49.15FIQvi_: grats
19:49.56*** join/#maemo ufa (~ufa@fedora/ufa)
19:50.04FIQerrr nvm I'm tired
19:50.32FIQbusybox simply refused to give meaningful errors, that's all
19:51.27*** join/#maemo straind (~stupidper@n119s035.bbr1.shentel.net)
19:52.19FIQhttp://pastebin.com/0TVGCH5d in /etc/event.d/ntpd is what I want, right?
19:52.43FIQdid small modification to the pastebinned script earlier as it mentioned ntpdate instead of simply ntpd
19:53.01FIQ@ vi_
19:53.13kerioFIQ: ntpd is in sbin
19:53.29FIQyes
19:53.51kerioFIQ: first, always specify full paths
19:54.01FIQwell, the previous script didn't, but ok :)
19:54.16keriothe previous script didn't use stuff in /usr/sbin i think
19:54.17kerioanyway
19:54.18*** join/#maemo Timo (~Timo@unaffiliated/tiempjuuh)
19:54.43kerioFIQ: use quotes around your tests
19:55.07kerioFIQ: also easier, start ntpd on started hal or something like that as a daemon
19:55.12kerio(tell it to not daemonize ofc)
19:56.03kerioi mean, it's the network time protocol daemon
19:56.41FIQhm
19:57.03keriotest if it actually adjusts the time, though
19:59.12FIQbtw vi____: *__*!*@* <-- is the reason for your ban
19:59.26vi____I do not get it??
19:59.34FIQ@ ##c
19:59.39vi____I cannot help it if people keep stealing my nick
19:59.53FIQwell, just saying
20:00.18FIQkerio: sorry, but I don't follow "started hal" (mostly because I don't know what you mean with hal)
20:00.19DocScrutinizer05((<FIQ> oh you say that now... :p)) I said it a few minutes before
20:00.31OxFFFFnoted
20:00.33FIQDocScrutinizer05: guess I missed it
20:02.25DocScrutinizer05vi_: it's your e-peen
20:02.32DocScrutinizer05*__*
20:02.49DocScrutinizer05regex for +b
20:03.12OxFFFFDocScrutinizer05, I am over here 0/
20:03.57OxFFFFugh.
20:04.15DocScrutinizer05vi_: lrn2nickserv
20:04.31OxFFFFwhat is the C equivalent of fscanf?
20:04.38DocScrutinizer05there's a nice useful command called GHOST
20:05.20*** join/#maemo NIN102 (~NIN@p5DD293F2.dip0.t-ipconnect.de)
20:05.21tadzikOxFFFF: uh, fscanf(3)?
20:05.56FIQhmmmmm
20:06.03DocScrutinizer05/msg nickserv id vi_ <password>; /msg nickserv ghost vi_; /nick vi_
20:06.21FIQso what exactly does maemo do if you set it in y2k38-wrapping time
20:06.26FIQI suppose it.. wrap
20:06.35FIQbut would be interesting to see how hildon stuff reacted to it
20:06.59OxFFFFy2k bug!
20:07.08OxFFFFEquinox fail!
20:07.10FIQy2k38 is an actual issue though, unlike y2k
20:07.24*** join/#maemo cyborg-one (~cyborg-on@188.115.131.197)
20:07.29FIQwhich mainly failed visibly
20:07.47FIQand some minor fails here and there due to people insisting on storing it in a 2-digit number
20:08.08FIQstoring years in 2-digit when you're at the end of a millenium isn't really long-term huh
20:08.28*** join/#maemo EgS (~egs@quassel/developer/egs)
20:08.42FIQhmmmmm
20:10.25FIQwhile I do have a ntpd running now that I started phone, it seems to not do much
20:10.58r00t|home(which is why i prefer ntpdate ;) )
20:11.21FIQis there any actual differences?
20:11.34r00t|homeFIQ: note that the menubar clock widget will NOT immediately update when the time is set
20:11.36FIQapart from possibly command-line options and such
20:11.42DocScrutinizer05FIQ: ntpd has a guard window, which disables time adjusts of >60s or sth
20:11.56FIQDocScrutinizer05: yeah I know about this one
20:12.04r00t|homeDocScrutinizer05: kerio already checked that that is not the case with busybox
20:12.05FIQ(i think it's bigger than this though)
20:12.15OxFFFFFIQ, clock will only update after you un/lock the screen/wait 30s.
20:12.27FIQwell I've waited 3min now :P
20:12.33OxFFFFthen  is has failed!
20:12.35FIQand it ticks nicely on 00:0x
20:12.44FIQbut ntpd appears in ps list..
20:12.45kerioFIQ: ok, stop ntpd and restart it
20:12.48FIQso it's definitely started
20:12.50FIQkerio: i'll try
20:12.51kerioit did work for me, i swear! :(
20:13.09kerioto be fair i only checked for a handful of hours of offset
20:13.13kerioperhaps 12 years is too much
20:13.27FIQi changed in gui
20:13.34FIQso i could only offset it 3 years :(
20:13.48kerioFIQ: change it with date, then restart ntpd
20:14.27FIQi'll try to start ntpd from commandline w/o changing with date first
20:14.37FIQto prevent ambiguos error reasons
20:14.41keriono, change the date and then start ntpd
20:14.45FIQok..
20:17.41FIQhuh
20:17.58DocScrutinizer05kerio: uhuh
20:18.06FIQkerio: ntpd only supports -dSs
20:18.25kerioFIQ: are you sure you don't have openntpd installed?
20:18.26kerio:)
20:18.28FIQ"usage: ntpd [-dSs] [-f file]
20:18.31FIQkerio: maaaaybe
20:18.43keriothat's why i specified "ntpd from busybox-power"
20:18.50keriook actually i didn't specify it now
20:18.54DocScrutinizer05RTFM
20:18.59FIQyeah i know
20:19.07FIQi just forgot that I also had openntpd
20:19.15kerioFIQ: btw you have to reinstall busybox-power after removing openntpd
20:19.24kerioit's the easiest way to recreate all the possible symlinks
20:19.42FIQbecause they both have /usr/sbin/ntpd..
20:19.50FIQshouldn't they conflict?
20:20.00keriobusybox-power creates its symlinks in postinst, if they don't exist already
20:20.03FIQ(the packages, that is)
20:20.05*** join/#maemo konelix (~konelix@200.119.174.203)
20:20.33kerioand it removes the symlinks in prerm, only if they are symlinks to busybox
20:20.50kerioFIQ: nope, busybox-power will never overwrite installed stuff
20:21.00kerioand i think that dpkg will just silently remove the symlink and install its files
20:21.06FIQit just let other stuff take priority
20:21.09FIQI suppose?
20:21.11DocScrutinizer05get ntpdate, add `sleep 30; ntpdate && hwclock --systohc` zo ifup
20:21.38FIQkerio: now I got actual usage info
20:21.48FIQlet's try to just reboot phone
20:21.52kerioDocScrutinizer05: ntpd -dnq -p europe.pool.ntp.org && hwclock --systohc
20:21.53FIQto see if ntpd does stuff right this time
20:22.05kerioFIQ: how are you resetting the clock, btw?
20:22.16FIQyou mean normally?
20:22.17OxFFFFI liked kerio solution, put the line in ifup.post
20:22.25FIQi switch batteries
20:22.41kerioheh, silly people with a non-working backup battery
20:22.49FIQmeh
20:23.30FIQreboot time
20:23.48r00t|homekerio: silly nokia installing backup batteries that die that early
20:24.10FIQkerio: I switch batteries as fast as possible
20:24.16FIQhaving the other one ready in <1s
20:24.21FIQsometimes I don't get reset clock
20:24.24DocScrutinizer05r00t|home: silly hitachi that bulds such crap
20:24.25FIQif I'm lucky...
20:24.29DocScrutinizer05seiko?
20:24.40kerioFIQ: on my old n900, i used to just lift the old one a bit, start sliding the new one under, then remove the old one and put the new one in
20:24.48FIQhaha
20:24.51kerioless than half a second, never had the clock reset :D
20:24.54FIQthat's what I'm doing, precisely
20:24.58r00t|homeDocScrutinizer05: are there any reports of people successfully replacing the backup battery? (somebody suggested to ask you)
20:25.01FIQit *usually* works
20:25.06FIQsometimes I'm too slow
20:25.12DocScrutinizer05r00t|home: yes, some users did
20:25.36DocScrutinizer05~bupbat
20:25.36infobotbupbat is, like, http://www.mouser.com/catalog/632/2009.pdf http://il.farnell.com/taiyo-yuden/pas414hr-va5r/cap-0-06f-3-3v-80ohm-4-8mm-coin/dp/1853000?Ntt=PAS414HR-VA5R, or use the capacitive type, LiIon are breaking during 12 months
20:25.41FIQuh
20:25.44FIQ...
20:25.55FIQkerio: Now ntpd just did something confusing
20:26.05keriohaha
20:26.06FIQbefore, I had time set at 2000-01-01 00:0x
20:26.13FIQNow it's at 1970-01-01 01:01
20:26.29DocScrutinizer05ntpd is not the right thing for mobile devices with intermittent connectivity
20:26.37FIQi.e. seconds after unix epoch
20:26.42kerioi think it's ossosuw that sets it to 2000
20:27.19FIQkerio: basically it did something, but it didn't do it right
20:27.22OxFFFFkerio, surely RTC chip resets to 2000
20:27.30FIQalso
20:27.33DocScrutinizer05and usually ntpd config has localhost (== cmos clock) as lower prio startum
20:27.35*** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ff55c100-11.dhcp.inet.fi)
20:27.40DocScrutinizer05stratum*
20:27.41kerioOxFFFF: your username deeply upsets me
20:27.42FIQwhen battery dies, time's set at 2009-01-01 06:00 for me
20:27.50kerioFIQ: that's definetely osso-startup-wizard
20:27.52FIQ(if that's what you're discussing)
20:28.10FIQkerio: ah
20:28.15FIQwell, dunno what happens *now*
20:28.18FIQnow that I don't have it
20:28.19r00t|homeDocScrutinizer05: some docs on doing the replacment aswell?
20:28.36DocScrutinizer05unsolder old part, solder new one
20:28.45*** join/#maemo konelix (~konelix@190.143.170.66)
20:29.03r00t|home<kerio> open n900, remove battery, put in new battery, ???
20:29.38DocScrutinizer05I suggest either using two soldering irons in parallel, or shove some paper or tin/alu foil under the contact you are just desoldering
20:29.40OxFFFFr00t|home, replace with double layer electrolytic supercap.
20:30.02OxFFFFkerio, I am vi
20:30.21OxFFFFthey come in 0.07uF
20:30.30OxFFFFBut most are obsolete.
20:30.33kerioOxFFFF: your username still upsets me
20:30.37r00t|homei just read that as: 0xFFFFuF
20:30.39OxFFFFEAT IT
20:30.39DocScrutinizer05me too
20:30.50kerioOxFFFF: IT'S NOT A REAL HEX NUMBER
20:31.12kerioIT'S NOT A REAL ZERO
20:31.24DocScrutinizer05and capslock upsets me too
20:31.29kerioindeed!
20:31.29OxFFFFI am not allowed a zero.
20:31.40OxFFFFAt the start of the nick.
20:31.42keriobut it's not capslock, i was holding shift
20:31.47kerioi disabled capslock
20:31.55FIQhmm
20:32.02FIQstill doesn't work
20:32.07OxDEADBEEF?
20:32.11r00t|homeDocScrutinizer05: the mouser catalog url on infobot is broken (redirects to /catalogrequest/catalog.aspx)
20:32.20FIQ(also, battery out, battery in = time is 2000-01-01 01:00 for me)
20:32.32FIQprobably as I'm on cet
20:32.36OxDEADBEEFkerio, is this better?
20:32.41DocScrutinizer05r00t|home: meh, you're welcome to find a better not outdated URL
20:33.02r00t|homeDocScrutinizer05: i can't without knowing what the content of the original url was
20:33.06FIQOxABADBABE @ OxDEADBEEF
20:33.14*** join/#maemo EgS (~egs@quassel/developer/egs)
20:33.57DocScrutinizer05http://il.farnell.com/taiyo-yuden/phttp://il.farnell.com/taiyo-yuden/pas414hr-va5r/cap-0-06f-3-3v-80ohm-4-8mm-coin/dp/1853000?Ntt=PAS414HR-VA5Ras414hr-va5r/cap-0-06f-3-3v-80ohm-4-8mm-coin/dp/1853000?Ntt=PAS414HR-VA5R
20:34.14keriovi, wat r u doin
20:34.25OxBEEFBEEFI am trying to find a new name
20:34.29keriovi, stahp
20:34.58FIQkerio: ok, so the problem lies in autostart thingy
20:35.04FIQbecause I tried to start ntpd manually
20:35.05FIQworked just fine
20:35.31FIQ(also, the 1970 nonsense wasn't caused by ntpd apparently, I guess that I just produced a malformed dateset)
20:36.18DocScrutinizer05FIQ: the problem lies in ntpd, it doesn't work on machines with intermittent connectivity
20:36.57kerioDocScrutinizer05: hmm, i wonder if we can abuse upstart's respawn to launch the appropriate magic command every x time
20:37.04FIQDocScrutinizer05: so are you suggesting me to download that package that anyone suggested from the beginning?
20:37.06*** join/#maemo fil (~phil@switch.hands.com)
20:37.12DocScrutinizer05FIQ: ntpd in daemon (11min) mode is BS for whacky internet
20:37.17FIQ(a version of ntpdate)
20:37.32kerioFIQ: ntpdate or ntpd oneshot is the same
20:37.35FIQ[21:25:51] <r00t|home> <r00t|home> wget http://www.math.ucla.edu/~jimc/nokia770/dists/mistral/user/binary-armel/system-tools/ntpdate_4.2.0a+stable-9_armel.deb
20:37.36FIQi.e. this
20:37.46keriodoc's objection lies in ntpd in daemon mode
20:37.47vi_ntp is suitable for one-shot mode.
20:37.51*** join/#maemo gomiam (~knoppix@89.128.139.188)
20:38.04kerioanyway, my phone booted with osso-startup-wizard purged
20:38.15gomiamcries... I'm unable to bring my n900 back to life.
20:38.25gomiamok, I'm not really crying, but it is annoying
20:38.33FIQgomiam: what happened?
20:38.36DocScrutinizer05add `sleep 30; ntpdate && hwclock --systohc` zo ifup
20:38.36tadzikconsider describing your problem :)
20:38.37vi_have you flashed it?
20:38.50FIQn900 can be resurrected (assuing no hw problem) with usb
20:38.50keriogomiam: http://24.media.tumblr.com/tumblr_mck6jbduSs1r96x1xo1_400.png
20:39.05DocScrutinizer05where ntpdate == ntpd -d iirc
20:39.14DocScrutinizer05for *some* flavours of ntpd
20:39.14gomiamwell, I bought this second hand N900 and found out it dropped the GSM card connection randomly.
20:39.19kerioDocScrutinizer05: ntpd -q
20:39.27keriogomiam: ouch
20:39.29DocScrutinizer05or that
20:39.31FIQntpd -d is daemonization IIRC
20:39.36FIQ-q is just "set time and quit"
20:39.42kerioFIQ: it's actually "don't daemonize" afaik
20:39.50FIQkerio: oh, so the opposite :D
20:40.02keriogomiam: it could be a hardware problem
20:40.08kerioit's a common fault, and there's no known fix :(
20:40.21keriogomiam: have you tried using a different, *new* sim?
20:40.29keriochecking the contacts?
20:40.32kerioreflashing?
20:40.35DocScrutinizer05fsckng ntpd is missing ntpdate's option to just *display* nettime
20:40.36gomiamso I decided to reflash it. I downloaded everything, ran flasher-3.5 (kind of) successfully from Windows 7 64 bit... and that's all she wrote.
20:40.46vi_pentium 4 laptop with tiny battery==utter bs.
20:40.50kerioDocScrutinizer05: ntpd -w
20:41.05kerio-wDo not set time (only query peers), implies -n (do not daemonize)
20:41.08vi_gomiam, Step 1. Dont use win 7.  An update has rendered it broken.
20:41.10FIQgomiam: i had the issue you had earlier, turned out it was my sim (it was ~5 years old)
20:41.13gomiamI have just tried the back-to-back root/emmc flash method to see if it would work from Knoppix 32 bits
20:41.20DocScrutinizer05pfff that's 'new'
20:41.22vi_gomiam, Step 2.  Use linux.
20:41.29FIQDocScrutinizer05: well it failed anyway
20:41.34gomiamand... it still gets in an endless boot loop.
20:41.37kerioDocScrutinizer05: "stupid developers fixed my problem"
20:41.43keriogomiam: you flashed it incorrectly
20:41.46kerioor it has a serious hw problem
20:41.54FIQwent to a reseller of my operator, requested replacement, got one that was due to activate in ½h, worked flawlessy
20:41.57DocScrutinizer05kerio: eh?
20:42.02vi_gomiam, use linux
20:42.09FIQunusually seamless "repair" for me
20:42.18kerioDocScrutinizer05: what's the problem if it's a new thing?
20:42.25filnotes that wifieye no longer shows me any stations, despite iwlist seeing stations -- is this a power kernel thing, or is it just coincidence that I recently installed that?
20:42.26vi_we should really roll an n900 'flashing' distro.
20:42.30DocScrutinizer05that it's not an old thing
20:42.37gomiamI get this message when trying to flash the root (among other things):   ERROR: EP0 STALL sent
20:42.41DocScrutinizer05what a stupid question
20:42.45vi_Base it on something like gparted, include the pr1.3 firmware files.
20:42.59keriovi_: NO REDIST!1!1
20:43.01gomiamhold on, I'm putting it all in pastebin so you can read it yourselves if you wish
20:43.11vi_kerio, IDGAF about nokia license.
20:43.15kerioit's in the eula that you have to mindlessly click through to download the fiasco images
20:43.18DocScrutinizer05the obvious problem is that my objection been correct for the last ~5 years
20:43.30kerioDocScrutinizer05: but it's not correct anymore! :D
20:43.37DocScrutinizer05so what?
20:43.46DocScrutinizer05the devels still are morons
20:43.48gomiamhttp://pastebin.ca/2289114
20:44.18Sicelofil: wfm.
20:44.29gomiamas you can see, the rootfs flash proceeds correctly... until it tries to flash cmt-mcusw
20:44.36filvi_: would it be worth knocking up some udebs so that one could do that from debian-installer?
20:44.50keriogomiam: signs point to hardware fault, sadly
20:44.54DocScrutinizer05gomiam: cmt hw defect
20:45.07keriounfixable unless you have a reflow station, afaik
20:45.15FIQI couldn't follow kerio's advice on fixing the shellscript completely, but http://pastebin.com/BF8KUty8 is what I have atm
20:45.19gomiamI read about someone using a heat gun to bring it back to life... is that even possible?
20:45.23filoh typical -- stupid proprietary license pain
20:45.32FIQsomething is most likely rendurant
20:45.37keriogomiam: are you an EE?
20:45.40FIQi.e. line 7 part
20:45.41DocScrutinizer05gomiam: yes, possible. with extreme luck and much experience
20:45.52gomiamkerio: no, but I have access to a few :)
20:46.08DocScrutinizer05gomiam: also see what kerio posted
20:46.22FIQsomeone willing to help me fix that ^, as i'm pretty bad on commandline-fu? :p
20:46.26gomiamDocScrutinizer05: yup, checking on reflow stations right now
20:46.37FIQbrb
20:46.40DocScrutinizer05err wut? for buying one?
20:47.05vi_just slap it in your oven at 220 degrees for 10 minutes.
20:47.10DocScrutinizer05you'll get ~20 new N900 for that money
20:47.10vi_Job done.
20:47.13keriovi_: stahp
20:47.26DocScrutinizer05vi_: stop telling BS
20:47.26kerioDocScrutinizer05: hopefully he's checking his accessible engineers
20:47.36gomiamkerio: mostly :)
20:48.29DocScrutinizer05vi_: check reflow profile allowed for most of the components. also check which components are hand assembled and not reflow-able at all
20:48.48DocScrutinizer05vi_: and consider this is a doublesided PCB
20:49.27DocScrutinizer05with a little luck your upper side looks brilliant after that procedure, while the bottom side is suddebly empty
20:49.31DocScrutinizer05X-P
20:49.51kerioDocScrutinizer05: just put the correct side in the oven, duh
20:49.53vi_yeah, that would suck.
20:50.06gomiamkerio: LOL
20:50.11vi_put a sacrificial n900 underneath duh.
20:50.55gomiamit seems air soldering rework stations are quite cheap... I need to ask around and see if someon I know has something like that
20:51.16gomiamin any case, getting back to the flash procedure
20:51.35vi_gomiam, USE LINUX
20:51.37gomiamis it normal that the rootfs flash procedure finishes (even if it complains about cmt)
20:51.46vi_gomiam, The best shareware OS available.
20:51.55keriogomiam: what's not normal is that it doesn't work afterwards
20:52.02kerioeven with a nonworking cmt
20:52.02gomiamvi_: I'm on Linux right now, and I'm using it for reflashing... unsuccessfully.
20:52.07vi_aah
20:52.16gomiamkerio: the real problem comes when I try to flash the eMMC
20:52.18vi_There is a flag in flasher that lets you ignore CMTcheck.
20:52.34vi_Also, you can tell flasher to ONLY flash rootfs image.
20:52.44*** join/#maemo ale152 (~quassel@82.57.110.116)
20:52.45keriogomiam: it doesn't really appear to be finished
20:53.02vi_So if you have the stock kernel flashed you can simply --flash-only=rootfs.img
20:53.07vi_or something
20:53.27kerioyep, --cmt-no-verify
20:53.49keriogomiam: make sure you don't boot inbetween the two images
20:53.52gomiamwhen I start flashing the eMMC (I'm going to try with --cmt-no-verify in a jiffy)
20:54.13gomiamthe phone reboots automatically and disappears from the USB devices... at least as far as flasher is concerned
20:54.22vi_when flashing emmc image, you do not need cmt no verify
20:54.30*** join/#maemo WPA2 (~WPa@host-78-150-220-251.as13285.net)
20:54.37gomiamhold on a few seconds while I try to flash the rootfs with --cmr-no-verify
20:54.45gomiamerm, cmt
20:54.50vi_gomiam, You are doing flasher3.5 -F <YOURFLASHFILEHERE> -f
20:54.53vi_right...
20:54.56vi_no -R
20:54.57gomiamvi_: exactly
20:55.01vi_good
20:55.14DocScrutinizer05irrelevant
20:55.24gomiamyes, I'm afraid that had to do with my original problem. I probably added a -R in the beginning when I shouldn't
20:55.30gomiamanyway, testing this new option
20:55.30kerioremove battery, enter commandline to flash COMBINED without -R, hold u, put battery in, wait for flash to finish, remove battery, enter commandline to flash VANILLA without -R, hold U, put battery in, wait for finish, remove battery, enter commandline to flash COMBINED without -R, hold U, put battery in, wait for finish, remove battery, unplug everything, put battery in, turn on
20:56.04kerioand use --cmt-no-verify
20:56.14gomiamkerio: I have tried that unsuccessfully too. Then again, I may have tried it incorrectly, so I will try again
20:56.15keriobut accept the fact that the phone part of your n900 is fucked
20:56.15DocScrutinizer05:nod:
20:56.26gomiamthanks everyone for your help so far
20:56.44kerioand agps will also be fucked, so expect fix times in the order of minutes
20:56.56DocScrutinizer05gps is borked
20:57.12DocScrutinizer05TTFF -><infinite>
20:57.51DocScrutinizer05if cmt is deaf for flashing, it won't reply as usual to GPS inquiries
20:58.07kerioDocScrutinizer05: hm
20:58.09DocScrutinizer05GPS chip is connected to BB5
20:58.16keriocan't you disable agps?
20:58.20keriolike, from the GUI
20:58.27DocScrutinizer05sure, so what?
20:58.37keriooh, it'll still check, i see
20:58.51DocScrutinizer05the GPS chip is wired to BB5
20:58.58keriohmm... doesn't stopping sscd do the same thing as a borked cmt, pretty much?
20:59.35DocScrutinizer05what got supplementary service code daemon to do with it?
21:00.07kerioit makes a cute "no sim" icon! :3
21:00.44DocScrutinizer05osso-paint can do that too
21:00.48gomiamOk, battery off, start up rootfs flash with --cmt-no-verify (and no -R), complains and ends.
21:00.57keriohm
21:00.58kerio:(
21:01.36gomiambattery off again, I start up eMMC flash, and it recognizes the device for a moment before it starts booting up and gets "lost"
21:01.41gomiamhttp://pastebin.ca/2289123 for more details
21:01.44DocScrutinizer05indeed :(, for fuzzy problem description
21:01.57keriogomiam: are you sure you're still holding u?
21:02.02gomiamkerio: certainly
21:02.09DocScrutinizer05battery empty
21:02.12kerioanyway, you won't be able to flash VANILLA without a working rootfs
21:02.53vi_Invalid argument for 'cmt'
21:02.55gomiamkerio: ouch. And if I read the instructions correctly, I can't get a working rootfs without a proper VANILLA.
21:03.06vi_are you sure you got the cmt-no verify correct?
21:03.08ShadowJKfil; wifieye randomly does one or all of the following: stops finding wlans, jacks up power consumption, leaves itself running and constantly scanning for wifi networks even if main window is closed
21:03.08DocScrutinizer05meh!
21:03.10FIQgomiam: correct
21:03.10keriogomiam: nah, you don't need *that* working of a rootfs :)
21:03.11DocScrutinizer05Bootloader error log follows:
21:03.12DocScrutinizer05<PROTECTED>
21:03.13FIQbut that's no problem
21:03.28keriogomiam: basically, you need to flash COMBINED before VANILLA to be sure
21:03.30FIQyou just flash rootfs, make unbootable n900, flash emmc, then rootfs again
21:03.40vi_ffs
21:03.52gomiamFIQ: "make unbootable n900"... please elaborate your thoughts
21:03.54vi_--flash-only=rootfs.img or sometghing.
21:03.59DocScrutinizer05FIQ: incorrect
21:04.04FIQDocScrutinizer05: hmm ok
21:04.05keriovi_: --flash-only=rootfs actually
21:04.15*** join/#maemo Jaded (~jade@Jade.broker.freenet6.net)
21:04.16*** join/#maemo Jaded (~jade@unaffiliated/jade)
21:04.16vi_gomiam, ^ what he said
21:04.17FIQoh well, i'm tired
21:04.23gomiamtesting with --flash-only=rootfs
21:04.27filShadowJK: ah, ok -- ta
21:04.37keriogomiam: you can do it separately with nolo, kernel, initfs, rootfs, cmt
21:04.40kerioof course cmt will fail for you
21:04.49kerioi'm not sure if you can tell it to flash more things at once
21:05.00vi_assuming you had stock kernel installed, that should work.
21:05.14keriogomiam: when flashing from COMBINED, you don't have to reboot between each thing
21:05.47gomiamkerio: I'm not. I'm removing the battery once the program gets back to command line
21:06.00vi_did it work
21:06.01kerioi mean when using --flash-only
21:06.38gomiam--flash-only=rootfs worked.
21:06.46gomiamat least it didn't complain
21:06.48keriogomiam: do it for kernel too
21:06.53gomiamproceeding
21:07.00ShadowJKwould think just flashing rootfs makes bootable N900 as long as emmc partitions aren't in any half-broken state
21:07.03kerionolo has been flashed successfully, initfs isn't needed, cmt won't work for you
21:07.04DocScrutinizer05then do eMMC
21:07.11kerioShadowJK: in theory, yes :)
21:07.17gomiamflashing correct
21:07.21gomiamproceeding to eMMC
21:07.30kerioDocScrutinizer05: if he's careful about not even half booting in the middle, he doesn't need to flash rootfs again, right?
21:07.37ShadowJKright
21:07.39DocScrutinizer05right
21:07.48gomiamshould I remove the battery again before flashing eMMC?
21:07.53filis there any way of discovering what wifieye is upset about?  (do errors get sent anywhere useful, like .xsession-errors, say?)
21:08.18DocScrutinizer05gomiam: try without, if it doesn't work, remove battery
21:08.33gomiamDocScrutinizer05: thanks. Starting eMMC flash run...
21:08.33ShadowJKThe constraint is: never-booted rootfs must exist after emmc has been flashed
21:08.36FIQgomiam: at least you have a working USB...
21:09.05gomiamflashing proceeds! Yay! Let's see how it ends :)
21:09.10FIQnice :)
21:09.30FIQgomiam: did the device boot before eMMC flash and after rootfs flash?
21:09.43FIQ(every kind of boot counts)
21:09.48kerioDocScrutinizer05: going back to the gps problem - shouldn't it be the same as a missing SIM?
21:10.00DocScrutinizer05FIQ: meh, if device doesn't boot, just reflash rootfs again
21:10.04kerioie it has no agps but it eventually gets a fix?
21:10.16DocScrutinizer05kerio: no
21:10.28*** join/#maemo loganbr (~user@206.81.98.165)
21:10.45DocScrutinizer05the gps chip is attached to cmt BB5
21:10.52DocScrutinizer05damn!
21:10.55gomiamFIQ: nope. When I flashed only rootfs and kernel it kept waiting, and when I started eMMC flashing it booted, but it is supposed to do that, I guess, because this time the VANILLA flash finished successfully from flasher's POV
21:11.14gomiamNow I should remove the battery and see if it starts, right?
21:11.21keriogomiam: yep
21:11.23DocScrutinizer05if BB5 is zombie state, how would it proxy GPS info
21:11.26FIQgomiam: yes
21:11.27gomiamproceeding.
21:11.30kerioDocScrutinizer05: oic
21:11.36keriowell, it's a shame :(
21:11.46filoh, I see -- it's spewing python errors
21:11.59FIQalso is there a way to confirm broken gps?
21:12.10kerioFIQ: go outside, gpsrecorder or gpsjinni
21:12.12FIQmine has stalled on "waiting" infinite time since uh
21:12.21FIQa while ago
21:12.29FIQ(~a year)
21:12.32gomiamit gets to the dots running right and left...
21:12.54DocScrutinizer05wait!
21:13.01DocScrutinizer05wait some more!
21:13.02FIQgomiam: it's rather slow first boot
21:13.10DocScrutinizer05wait....!
21:13.12FIQvery slow tbh, I even though it got stuck the first time
21:13.37*** join/#maemo MrOpposite (~MrOpposit@85.8.57.207)
21:13.37*** join/#maemo MrOpposite (~MrOpposit@unaffiliated/mropposite)
21:13.38FIQbut then I forgot about the phone and started a game, and before i got to start it proper, it was done :p
21:13.43DocScrutinizer05you might want to hook up fastcharger right now
21:13.56FIQbtw
21:14.01gomiamI get the telephony functions disabled message which is encouraging
21:14.06FIQDocScrutinizer05: what happens if there's a power outage on first boot?
21:14.10*** join/#maemo brzys (~quassel@77-92-38-176.cable-modem.tkk.net.pl)
21:14.13kerioFIQ: madness
21:14.14DocScrutinizer05undefined
21:14.26DocScrutinizer05mess
21:14.41gomiamkeeps waiting patiently for MAemo to get its act together...
21:14.43FIQit would be slightly frustrating for me if I got that after successfully reflashing recently...
21:15.05kerioafaik there's *something* regarding graceful failure during updates
21:15.08FIQlike "grats, you did it, only took an hour! now do it again!"
21:15.18kerionot sure what happens during firstboot though
21:15.53gomiamwhile waiting, a small offtopic question: have you ever dealt with an Always Innovating Smart Book?
21:15.54*** join/#maemo nox- (noident@freebsd/developer/nox)
21:16.23gomiam(this MID device you could pop into a screen to turn it into a pad, which you could slot into a keyboard to turn it into a netbook?
21:16.28keriogomiam: looks overly complicated
21:16.58gomiamkerio: it does at that, but it also had four Linux distros from start :)
21:17.04kerioneat
21:17.24FIQI have not
21:17.31gomiamI'm asking because the company stopped selling them and they won't answer to any queries about remaining stock
21:17.40DocScrutinizer05gomiam: you attached fastcharger?
21:17.47FIQbut seeing it reminds me of asus transformer
21:18.04gomiamDocScrutinizer05: no. I just have this battery that I charged before starting all this.
21:18.13FIQwhich I'm considering getting, but haven't yet
21:18.41keriogomiam: attach it, just to be sure :)
21:18.44gomiamFIQ: actually, the Asus Transformer reminds me of this thing... but less flexible. Always Innovating's product was on the market before Asus' one, anyway
21:18.48gomiamkerio: WILCO
21:19.01*** join/#maemo sequantz (~sequantz@194.11.24.44)
21:19.08DocScrutinizer05btw firstboot should be done with no PC attached
21:19.20FIQi don't see the point in pads, sure they have some adventages, but it feels a bit too nisched
21:19.25kerioDocScrutinizer05: why, what happens otherwise? :o
21:19.32DocScrutinizer05ass rage mode would possibly interfere
21:19.34FIQtransformer combines netbook and pad nicely, which made me consider it
21:19.47FIQwould rather get one that came with a better os though..
21:19.59gomiamaaaand... it plays the Nokia startup tune!
21:19.59DocScrutinizer05and generally it introduces unneeded complexity and points of failure
21:20.09kerioFIQ: i don't get this fixation with tablets, really
21:20.17gomiamdoes little victory dance... and the neighbours below complain.
21:20.23keriogomiam: yay ^_^
21:20.27FIQkerio: I don't get the hype of pads at all
21:20.44FIQbut I can see they be decent in some situations.. but they're few
21:20.44kerioheh, we don't really have to tell gomiam to uninstall cherry ASAP
21:20.55FIQhaha :P
21:21.06gomiamok, setting options and checking but, for the time being, THANKS A LOT
21:21.14kerioYOU'RE WELCOME
21:21.36gomiamno, I'm gomiam :P
21:21.37FIQ(gomiam: fyi, cherry is my-nokia thing, which is obligatory premium SMS giving "support")
21:21.42FIQin case you wondered
21:22.05gomiamI will ask around to see if someone has a new SIM card I can play around with
21:22.13FIQhmm
21:22.17FIQwell
21:22.18keriogomiam: forget about it, your cmt is toast
21:22.19*** join/#maemo Jade (~jade@Jade.broker.freenet6.net)
21:22.19*** join/#maemo Jade (~jade@unaffiliated/jade)
21:22.25FIQif SIM card was the issue, then cmt would flash fine
21:22.28kerionot being able to flash cmt is *the* telltale sign
21:22.33FIQyeah
21:22.33keriodammit FIQ
21:22.35gomiamouch...
21:22.51FIQgomiam: enjoy your upgraded N810, pretty much :|
21:22.51DocScrutinizer05we seen cmt "segfault" on fsckdup SIM
21:23.04FIQDocScrutinizer05: then, sim removal should work
21:23.06FIQno?
21:23.09DocScrutinizer05yes
21:23.31gomiamFIQ: will do XD at least it lets me browse some webpages that bork on my N800 (slashdot, I'm looking at you)
21:23.33kerioand it would flash nicely
21:23.36DocScrutinizer05so if gomiam has no SIM inserted right now, he got a defect cmt
21:23.45DocScrutinizer05otherwise it's worth removing SIM
21:23.49gomiamDocScrutinizer05: no SIM right now, correct.
21:23.59DocScrutinizer05then sorry, dude
21:24.00FIQthen cmt = defect
21:24.14FIQ(not literally, mind you)
21:24.20DocScrutinizer05unless....
21:24.21gomiamtsch... I will ask around and see if someone manages to "resolder" it
21:24.30gomiamDocScrutinizer05: ?
21:24.42DocScrutinizer05please check your OS version, in settings "about product"
21:24.48gomiamchekcing
21:25.10gomiam20.2010.36-2
21:25.21DocScrutinizer05hmm, no 'luck'
21:25.23FIQDocScrutinizer05: now you remind me of v1.0 issue with certain SIM cards
21:25.30DocScrutinizer05correct "firmware version"
21:25.30keriohuh...
21:25.37kerioDocScrutinizer05: wait, what?
21:25.41FIQ(I happened to have one of the SIMs that didn't work)
21:25.43kerioit should be 21.2011.38-1, shouldn't it
21:25.48FIQkerio: no
21:25.52FIQgomiam has PR1.3
21:25.54DocScrutinizer05cmt PR1.3 won't flash with fiasco 1.1
21:25.55FIQthat is 1.3.1
21:26.05keriooic
21:26.15DocScrutinizer05afaik
21:26.22gomiamis there a newer version?
21:26.27keriogomiam: anyway, upgrade to pr 1.3.1 with HAM
21:26.28FIQgomiam: you want cssu
21:26.31keriothen install cssu-something
21:26.33DocScrutinizer05nope, yours is the most recent one
21:26.41FIQkerio: that isn't needed
21:26.42gomiamok, proceeding to update the hell out of it.
21:26.44FIQcssu installs on 1.3
21:26.47keriogomiam: you have the latest version of the fiasco images
21:26.58keriothere's a community thing for updates, but it's only post-flash
21:27.23FIQI'm still surprised that nokia even did 1.3.1
21:27.36DocScrutinizer05indeed
21:27.55FIQwas there any contract or anything saying "end of support: XXXXX"?
21:28.06DocScrutinizer05esp since the DGAF about vulnerabilities in flash
21:28.08FIQbecause that would be the only reason I see for nokia to do such thing
21:28.11kerioFIQ: meh, ssl brokenness is a big deal
21:28.32FIQkerio: what about the other vulnerabilities?
21:28.45FIQand the other cert issue creeping up after a while? :p
21:28.50FIQ(they didn't do a pr1.3.2 for it)
21:28.53kerioi guess they stopped caring
21:29.07gomiamconnected to local wifi...
21:29.08DocScrutinizer05and we all thought the had done before
21:30.17ShadowJKwonders what gps software shows "waiting" forever, if it's ovi maps, give up, because it cycles gps on and off like some adhd person
21:30.28DocScrutinizer05gomiam: you could try dialing '*#0000#' in dialer
21:30.30FIQShadowJK: yeah, ovi maps
21:30.43FIQbut i wouldn't be surprised if it was ovi maps issue
21:30.47FIQit never worked any good
21:30.58FIQtherefore I asked in here for a proper way to check if gps worked
21:31.36ShadowJKIt basically switches off gps sooner than theoretical worst case cold start minimum time required to first fix in ideal conditons, so..
21:31.46FIQ..
21:31.46DocScrutinizer05gomiam: I have no clue what it will show for you, I only know it *should* show OS version
21:31.48FIQwell
21:31.54ShadowJKgpsjinni, location test
21:32.01FIQthe only reason I consider gps broken at all is that ovi maps at least worked before
21:32.03kerioFIQ: gpsrecorder
21:32.05FIQ(not good, but it worked)
21:32.15FIQsince a year ago it doesn't work *at all*
21:32.19FIQkerio: what's that?
21:32.25kerioa program
21:32.28gomiamDocScrutinizer05: it shows 20.2010.36-2
21:32.30DocScrutinizer05also *#06# for IMEI which definitely will blow chunks when cmt defect
21:32.32FIQohhhhhhhhhhh
21:32.35FIQit's a program!
21:32.53FIQDocScrutinizer05: heh, what happens if cmt is broken? :p
21:32.56FIQ@ imei check
21:32.57ShadowJKagps "broke" for me at home recently, because my operator installed a new 3g antenna in the mast, and none of the supl servers know of it, and don't give any usable data back :)
21:33.00DocScrutinizer05nfc
21:33.18FIQgomiam: try it :3
21:33.21gomiamDocScrutinizer05: and *#06# answers "IMEI:"... because I have no SIM in it right now?
21:33.27FIQgomiam: no
21:33.31FIQimei is phone, not sim
21:33.32keriogomiam: because your cmt is busted
21:33.37gomiamtrue, true
21:33.48gomiammy bad
21:33.48FIQ(well, assuming working cmt)
21:33.53gomiamuser error: replace user and proceed :)
21:34.07FIQdidn't korea produce new n900 boards or anything?
21:34.17FIQsomeone in here told earlier...
21:34.19DocScrutinizer05that's the newest rumor
21:34.28tadziknew n900 boards?
21:34.34DocScrutinizer05yep!
21:34.36tadzikwhat for? :)
21:34.37*** join/#maemo MrOpposite (~MrOpposit@85.8.57.207)
21:34.37*** join/#maemo MrOpposite (~MrOpposit@unaffiliated/mropposite)
21:34.40FIQrepair
21:34.41keriowhich korea?
21:34.42DocScrutinizer05repair
21:34.45FIQninja'd
21:34.52gomiamDocScrutinizer05: so... should I install the CSSU Features Configuration application?
21:34.52FIQkerio: the good one I guess
21:34.54tadzikhuh, I'm surprised anyone still cares
21:34.58FIQcertainly not the north side
21:35.16DocScrutinizer05gomiam: one of the two available ones is obsolete and borked
21:35.24ShadowJKthey recently discoveered unicorn caves
21:35.35gomiaminteresting, only one shows by default. Checking version
21:35.44DocScrutinizer05gomiam: anyway before you install that, you'll want to install CSSU
21:35.55gomiamok, reading on installing CSSU...
21:36.03FIQ~cssu
21:36.03infobotmethinks cssu is http://wiki.maemo.org/Community_SSU
21:38.09FIQok so what was I supposed to do...
21:38.17FIQright, check what gpsrecord was
21:38.19FIQor whatever it was named
21:38.26*** join/#maemo MrOpposite (~MrOpposit@85.8.57.207)
21:38.26*** join/#maemo MrOpposite (~MrOpposit@unaffiliated/mropposite)
21:38.31DocScrutinizer05FIQ: get location test
21:38.42DocScrutinizer05way better than gpsrecord
21:38.53kerioDocScrutinizer05: but does it update the clock?
21:39.00DocScrutinizer05err  nope
21:39.01FIQjust tell me what the package is named, i just want to check if this thing works..
21:39.04DocScrutinizer05afaik
21:39.21DocScrutinizer05~pkg
21:39.21infobotit has been said that pkg is http://maemo.org/packages/
21:39.26FIQshh
21:39.30gomiamhow stable is CSSU "testing"?
21:39.38DocScrutinizer05stable enough
21:39.41DocScrutinizer05usually
21:39.46keriogomiam: like debian testing
21:39.53gomiamthen it is good enough :)
21:39.53*** join/#maemo NishanthMenon (~nmenon@cpe-24-27-111-228.tx.res.rr.com)
21:39.56FIQgomiam: do note that you can't go to stable from testing
21:40.09FIQw/o reflash or BM restoration
21:40.10keriodisclaimer: it might not be as stable as debian testing
21:40.12FIQ(but you can do the opposite)
21:40.15DocScrutinizer05but you can go to testing from stable
21:40.19keriogomiam: make sure to follow the instructions
21:40.22kerioaka MAKE A BM BACKUP
21:40.27FIQyep
21:40.35DocScrutinizer05follow the instructions *verbatim*
21:40.38FIQthe instruction that I didn't see the first time, as it wasn't there then :)
21:40.48DocScrutinizer05and waaaaait til you see results
21:40.54DocScrutinizer05don't abort anything!
21:41.13DocScrutinizer05there's nothing known to ever lock up
21:41.16gomiamkerio: wilco, though currently I have no info on the phone so I would have no problem reflashing, now I know how to get it back up.
21:41.21FIQhmmmmmmm
21:41.22DocScrutinizer05just sometimes takes quite a while
21:41.25FIQahh whatever
21:41.30FIQlet's do this
21:41.35FIQupgrades to cssu-testing
21:41.44FIQor... cssu-thumb perhaps
21:41.55kerioFIQ: you're supposed to yell "LEEROOOOOOOOY JEEEEEEEEEENKINS" when you do that
21:42.06FIQkerio: OOOOOOOOOOOOOOOOOK
21:42.18keriono, LEEEEEROOOOOOOOOY
21:42.40DocScrutinizer05what? jenkings? who the f* is jenkins? <sing!>
21:42.46FIQok cssu thumb needs a new kernel afaik
21:42.57FIQthat means that BM restorations wont work
21:43.15FIQ(as I found out the hard way earlier)
21:43.17kerioinstall kernel-power before
21:43.21FIQi have it
21:43.22kerioand make a backup with that
21:43.26keriothen it won't need a new kernel
21:43.33keriounless you have an ancient kernel-power
21:43.34FIQbackup was made 2h ago
21:43.38FIQuhm
21:43.40FIQchecks
21:43.57FIQ..uname doesn't seem to tell version
21:44.32FIQok...
21:44.36FIQnever mind
21:44.37DocScrutinizer05idly wonders if a backup could be done after download of PK but *before* it gets flashed
21:44.41FIQi didn't have kernel-power
21:44.49FIQbut I'll have it soon
21:45.04DocScrutinizer05so that restoring to that state would trigger immediate kernel flashing
21:45.28FIQ~kp
21:45.28infobotsomebody said kp was http://talk.maemo.org/showthread.php?t=85665
21:45.33FIQnot that..
21:46.19FIQDocScrutinizer05: i'd rather not try it out
21:46.20DocScrutinizer05((<FIQ> ..uname doesn't seem to tell version)) of what?
21:46.25DocScrutinizer05kernel? it does
21:46.29FIQkernel-power version
21:46.31DocScrutinizer05rootfs? nope
21:46.36FIQbut i realized it was due to vanilla
21:46.41*** join/#maemo MrOpposite (~MrOpposit@85.8.57.207)
21:46.44FIQso i'm installing kp atm
21:47.44FIQbut I'm honestly surprised, I thought I did this ages ago
21:47.51FIQ(or weeks, at least)
21:48.12gomiamstarting big cssu download and install...
21:48.15FIQat least I was going to do it.. guess i forgot it
21:48.18*** join/#maemo vi_ (~vi_@87.115.161.232)
21:48.36DocScrutinizer05honestly, doing restore of a suspended-to-disk swap and rootfs, then triggering immediate hard reboot, that would be awesome
21:49.12vi_is there any program on maemo that lets me watch videos from where I left off?
21:49.14FIQn900 hibernation?
21:49.26vi_like panucci, but for videos?
21:49.41ShadowJKWeirdly the default media player seems to do that for me
21:49.50ShadowJKor then it's gpodder, *shrug*
21:49.54FIQDocScrutinizer05: i don't use it on computer *at all*, but it would be really nice to have suspend-to-disk on n900
21:49.59vi_ah! of course!
21:50.10FIQespecially at the rate I power cycle as I can't charge..
21:50.28FIQok DocScrutinizer05, I have kp51
21:50.33FIQI guess that's enough?
21:50.37vi_ty SJK
21:50.40FIQfor thumb
21:50.40DocScrutinizer05FIQ: for some purposes it would indeed be nice. But particularly for installing a live system it would be mad useful
21:50.44kerioFIQ: then you should be able to just install cssu-thumb
21:50.49FIQkerio: nice
21:50.51keriowithout changing your kernel
21:50.54FIQi'll do bm backup first though
21:51.00FIQ(again)
21:51.02kerioif you want to be sure, install pali's fiasco-do-update-ask
21:51.03vi_FIQ: good move!
21:51.17keriobut make sure to actually flash if it asks to flash
21:51.57FIQbtmm
21:52.02FIQpretty simple to remember
21:53.06FIQheh
21:53.26FIQthere's lots of adventages with a (mostly) open system like maemo
21:53.44FIQit's improving now, after 3 years of existing
21:53.50FIQ(n900, that is)
21:53.55DocScrutinizer05orly? :-D
21:53.58FIQ:P
21:54.18DocScrutinizer05and I thought all n900 users are steampunks
21:54.22FIQbut I guess the community can only shrink now, mostly
21:54.30FIQas there are hardly any new n900s
21:54.48vi_plenty of old ones.
21:55.01vi_right now is the golden time to stock up on n900s
21:55.02*** join/#maemo cobalto (~unifly@87.20.145.158)
21:55.04DocScrutinizer05well, we seen - like - 4 new users during last 3 weeks
21:55.13DocScrutinizer05just here in this chan
21:55.16FIQDocScrutinizer05: true
21:55.30FIQeven though n900 users wont increase, the community might do
21:55.50FIQas casuals replace the device, and their devices get re-used by people that actually care about an open system
21:56.00DocScrutinizer05yep
21:57.11gomiamvi_: unfortunately, n900's are still a bit pricy on eBay :)
21:57.25gomiamok, CSSU testing installed
21:57.31FIQgomiam: a shop in my country sold *new* (yes, really) n900s
21:57.37FIQthough they did it for launch price..
21:57.41FIQso not really worth it eh
21:57.44tadzikthey still sell new ones here
21:57.51tadzikfor ~150€ or so
21:58.09FIQthe shop I saw did it for launch price, so ~600€
21:58.16FIQtadzik: interested? ;)
21:58.22gomiamtadzik: yup, I got mine for about EUR100
21:58.23tadzikhardly a good offer
21:58.29tadzikFIQ: not really, mine works pretty fine :)
21:58.33r00t|homei bought a like-new n900 on ebay for 80eur...
21:58.40FIQI guess I could stock up on them
21:58.48FIQthen keep them for some years
21:58.52FIQthen sell it for moar :o
21:59.03FIQ(once they get very hard to come by)
21:59.06tadzikif there will be people to buy them for more
21:59.10FIQ:P
21:59.16tadzikI don't think I'll buy another one if this one broke
21:59.23FIQi would
21:59.37FIQI seriously considered ^ that offer as my n900 was useless in a period
21:59.57FIQbut decided to do a last attempt on getting my n900 in working state
22:00.08FIQwhich succeed
22:00.30DocScrutinizer05tadzik: I'd be interested in new N900 with warranty and original package
22:00.37DocScrutinizer05for that price
22:00.42FIQDocScrutinizer05: for 600€?
22:00.49DocScrutinizer05no, 150
22:00.50FIQor 150€? :P
22:00.51FIQah
22:00.55FIQme too
22:01.06FIQyay
22:01.06FIQbm don
22:01.07FIQe
22:01.13tadzikI see 5 units with 24 months warranty for 699 PLN
22:01.27tadzikthat's 169€
22:01.29FIQ=gcalc 699 PLN in EUR
22:01.33FIQoops
22:01.39DocScrutinizer05could you get me 2 of them please?
22:01.48tadzikwe can arrange that
22:01.59FIQwants one
22:02.07tadzikI can't guarantee how legit those are
22:02.10tadzikhttp://allegro.pl/nowa-nokia-n900-gwarancja-24mc-zestaw-i2809945538.html
22:02.27kerioi kinda want one too, but my parents will think that i'm crazy if keep buying the same phone over and over
22:02.37FIQkerio: lol
22:02.45kerioi mean, more crazy
22:02.50FIQjust tell them that they don't understand
22:03.11DocScrutinizer05kerio: tell your parents that uncle doc allowed it
22:03.21kerioyeah, that'll go well
22:03.25FIQkerio: my parents told me that I acted like oldies that don't do new tech stuff
22:03.42FIQwhen I considered getting *one* new n900 as my old one is starting to fall apart
22:03.50FIQ(yes, not just usb issue)
22:03.57kerioFIQ: well... it's kinda true
22:04.11FIQkerio: but there aren't any replacements :(
22:04.16kerioi know! :(
22:04.32AoyagiWhen "new tech stuff" is something, that's less open than a virgin, well, I think I'll pass.
22:04.47DocScrutinizer05tadzik: that's the problem with legit, I hoped for your knowing the language to be able and check that out
22:04.54FIQAoyagi: this new iphone 5 would suite you perfectly then!
22:05.12FIQhmmm
22:05.13AoyagiI think you misunderstood me there :P
22:05.26FIQohhhhhh
22:05.27FIQright
22:05.29FIQcompletely forgot
22:05.34FIQso what did jolla have to say?
22:06.33gomiamok, time for me disconnect. Once again, thanks a bunch for your help, and have fun.
22:06.48gomiams/ me / me to /
22:06.53keriotake care
22:06.56DocScrutinizer05they say they might come up with a new device next summer, but alas the OS/desktop is *very* HARM-alike. So it's basically a portrait-only phone
22:07.16FIQDocScrutinizer05: aw
22:07.25FIQwell if it's open, it can be fixed, right?
22:07.27AoyagiWell I heard Nokia might have some Android plans.
22:07.27kerioFIQ: and no keyboard!
22:07.28FIQ...right?
22:07.31FIQWAT
22:07.33FIQ...
22:07.35FIQnvm then
22:07.40kerioso there's that
22:07.47tadzikDocScrutinizer05: well. They claim them new, with Service Warranty
22:07.52FIQAoyagi: ...
22:07.53DocScrutinizer05FIQ: yep, it *can* be fixed. Like KDE4 *can* get fixed
22:08.02FIQnokia tried everything *but* android
22:08.06FIQit avoided it like the pest lol
22:08.16tadzikthis is an auction-thingy however, like ebay, so you never truly know
22:08.21FIQso it's considering jumping on the android train now?
22:08.33FIQ*they're
22:08.38DocScrutinizer05tadzik: could you give them a call and make sure it's unusued factory-new stuff in original packaging?
22:09.00AoyagiFIQ: http://www.tomshardware.com/news/Nokia-Android-Smartphone-Microsoft-Google,19495.html it's a rumor, of course. It might as well be MeeGo.
22:09.15AoyagiOooor nothing at all.
22:09.17FIQmeego? nokia wont do that
22:09.20FIQor.. well
22:09.26FIQnokia has been very confusing the latest years
22:09.35fralstrololol
22:09.38DocScrutinizer05tadzik: of course I'll pay all your expenses
22:09.39tadzikDocScrutinizer05: I can write them an email if that's fine with you
22:09.40FIQindeed
22:09.40jon_ysummon Mi-Go
22:09.41AoyagiOf course, they have a M$ saboteur :P
22:09.47FIQ@ frals
22:10.14FIQjon_y: you make me think of pokémon now..
22:10.32DocScrutinizer05tadzik: sure
22:10.38jon_ywell, there was that lovecraft-pokemon crossover
22:10.45FIQ"Mi-Go", that is
22:10.52AoyagiWild Mi-Go appears.
22:10.54FIQ(which I read as ho-oh at first)
22:11.00jon_yall the trainers are kids because adults will go insane
22:11.09FIQheh
22:11.36FIQAoyagi: WP used Charm
22:11.43jon_yiirc pokethulu or something
22:12.12AoyagiMi-Go is confused.
22:12.34jon_yall the mons were freaky butt ugly ersatz
22:12.38FIQok so jolla is making a meego-phone w/o keyboard
22:12.45tadzikwhoa
22:12.53tadzikthere's another offer where they have...
22:12.59tadzik98 devices. 12 months warranty
22:13.07FIQjon_y: i never liked romhacks that featured fakemons, i'm sure i would like that even less
22:13.36jon_yFIQ: the game was paper and pencil like Call of Cthulhu
22:13.51FIQjon_y: heh
22:13.53jon_yso perfectly fine to make up your own mons
22:13.56tadzikDocScrutinizer05: sent them a question
22:13.59FIQ:P
22:14.14FIQHm
22:14.19FIQAbout lack of keyboard
22:14.42FIQThere was this kickstarter earlier.. of a keyboard you could connect to whichever phone you wanted
22:14.52FIQHave anyone of you tried something like that?
22:14.59FIQconnected to bt, etc
22:15.11FIQi.e. how well does stuff like that work?
22:15.14DocScrutinizer05tadzik: thanks a lot, mate
22:15.23*** join/#maemo shamus (~shamus@ip-206-192-195-49.marylandheights.ip.cablemo.net)
22:16.10FIQi'm wondering if it could potentially solve vendors complete refusal of bundling phones with ak eyboard
22:16.20*** join/#maemo Ken-Young (~kenyoung@208.54.36.227)
22:16.21tadzikDocScrutinizer05: you're welcome
22:16.23FIQs/k e/ ke/
22:16.26kerioFIQ: bluetooth keyboards do exist
22:16.38FIQkerio: yeah, i know
22:16.47FIQbasically I asked how good they work
22:16.56FIQif they can replace a real one nicely, etc
22:17.04kerioit depends
22:17.17keriohttp://akiba-pc.watch.impress.co.jp/hotline/20101228/ni_cgk308e.html this one is a fucking beast, or so i've been told
22:17.25FIQthe one I looked at (but didn't buy) @kickstarter also featured game buttons
22:17.30keriofor "compact" ones
22:17.38FIQand would be generally awesome if it worked well
22:17.49keriothe kickstarter one is even more compact i think
22:18.01kerioor possibly the same
22:18.11kerioyep, the one on kickstarter looks awfully similar
22:18.27FIQkerio: link me to which one you're looking at
22:18.37keriohttp://www.kickstarter.com/projects/jorno/jorno-the-pocketable-folding-bluetooth-keyboard the one on kickstarter
22:18.38FIQ@kickstarter
22:18.55keriothe geyes one is actually full-size i think
22:18.55FIQah, that wasn't the one i was looking at
22:19.22FIQwhile I guess that would work, I was more on something compact, as native keyboards do
22:19.29FIQi'll google a bit
22:19.32keriothere's plenty of those
22:19.44keriothere's an iphone one that slides from below
22:19.51keriobluetooth keyboards work fine
22:20.03*** join/#maemo lbt (~david@63-145-238-4.dia.static.qwest.net)
22:20.03*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
22:23.05FIQohh
22:23.32FIQicontrolpad2 was what I was looking at earlier but didn't buy
22:23.40FIQthat one would be awesome if it actually worked :)
22:24.40kerioDocScrutinizer05: how would someone identify what's loading a module on a linux desktop, btw?
22:25.07FIQbut it's unavailable atm
22:25.43DocScrutinizer05kerio: not that easy, but then there's also not that many possibilities
22:25.59DocScrutinizer05most modules get loaded by udev I guess
22:26.21kerioDocScrutinizer05: yeah but imagine in a fully poettered system
22:26.34DocScrutinizer05blaeerrrgh!
22:26.43kerio"in a modern linux desktop, there's no need to blacklist modules"
22:26.57FIQi haven't a single module blacklisted
22:27.10FIQ*reminds himself of n900 flashing* nvm
22:27.27kerioi use os x, i'm kinda used to bullshit black boxes thinking they're too clever
22:28.11keriomeh, if joshgillies doesn't come here soon with his problem i'll go to sleep
22:28.35*** join/#maemo jhb (~joerg@e176084182.adsl.alicedsl.de)
22:29.00DocScrutinizer05joosh got the solution to his problem
22:29.03DocScrutinizer05blacklist phonet
22:29.20DocScrutinizer05needed on 99% of distros nowadays
22:29.58DocScrutinizer05and symptoms when you fail to do are exactly as described by him
22:30.28FIQDocScrutinizer05: yeah, i did
22:30.50FIQthat's what i meant with "nvm", i.e. i have *one* module blacklisted :p
22:31.07keriok, i'll go to sleep then
22:31.15FIQerr oh it was @keri
22:31.16FIQo
22:31.19FIQis tired
22:31.21FIQshould sleep
22:31.33DocScrutinizer05idly wonders which moron included cdc_phonet to standard linus kernel
22:31.58*** join/#maemo teotwaki_ (~crashandd@2a01:e35:8a44:eb00:213:2ff:fe39:c4d4)
22:32.20DocScrutinizer05I couldn't think of any 'app' that would actually use cdc_phonet
22:32.41FIQ:p
22:33.03kerio[PATCH] USB host CDC Phonet network interface driver
22:33.09kerioFrom: Rémi Denis-Courmont <remi.denis-courmont@nokia.com>
22:33.13kerioDAMN YOU ELOP
22:34.12FIQkerio: really or trolling?
22:34.23keriothe third line was me trolling
22:34.26keriothe first two are serious
22:34.35keriohttp://thread.gmane.org/gmane.linux.network/133220 this is the thread
22:34.48FIQwhy..
22:35.34FIQok, so basically, the one that made nokia devices fail was... nokia
22:35.52tadzikgo figure
22:39.53*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
22:44.11*** join/#maemo teotwaki_ (~crashandd@Maemo/community/contributor/crashanddie)
22:56.14DocScrutinizer05well, Alan cox got it to the point in http://thread.gmane.org/gmane.linux.network/133220
22:56.45DocScrutinizer05http://article.gmane.org/gmane.linux.network/133538 actually
22:57.22*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
22:58.12SpeedEvilindeed
22:58.41SpeedEvilgetting vendors to fix stuff - or worse - create new standards - is hard
22:59.11merlin1991SpeedEvil: they'll happily create a new standard
22:59.22merlin1991if they can just encapsulate the old one within it
22:59.26SpeedEvilinteroperable open
22:59.33SpeedEvilthat too
23:01.43*** join/#maemo kolp_ (~quassel@212.255.29.125)
23:01.50*** join/#maemo stardiviner (~stardivin@122.236.241.125)
23:02.09FIQessentially making it worse
23:02.45FIQhm
23:02.53FIQok, bm is probably done now
23:03.08FIQi forgot about that it was backupping
23:03.13FIQguess battery died
23:03.58FIQuh
23:04.06FIQNow I got the weird issue once again...
23:04.23FIQwhen maemo doesn't boot w/o open keyboard
23:05.04Aoyagino keyboard connected, press F1 to continue?
23:05.16FIQlol Aoyagi
23:05.40FIQAoyagi: for me, as one that has boot menu, keyboard open or closed during boot actually makes a difference
23:06.01FIQthere we go
23:06.11FIQfor some reason the issue can be fixed by starting bootmenu once
23:06.18FIQthen it happily boots with keyboard closed
23:06.39FIQmaybe this is related to the fact that i just ran backupmenu?
23:06.58FIQand that maemo doesn't boot after running backupmenu unless I use boot menu?
23:08.27*** join/#maemo r00t|d430 (~r00t@dyndsl-095-033-081-246.ewe-ip-backbone.de)
23:10.56AoyagiWell, since not much is happening here, could you name a few things that you can do and 'droids can't? I need some fighting arguments here...
23:15.16Skry22:41 [ Sicelo900] today i attached to a cisco router's console via the console cable + usb-serial adapter + h.e.n , and dealth a huge blow to all the techs i work with, who own different types of android & iphone devices
23:15.37Aoyagiheh
23:16.55vi_recompile kernel on itself
23:17.12*** join/#maemo Gizmokid2005 (~Gizmokid2@dedi.gizmokid2005.com)
23:22.16DocScrutinizer05Skry: h-e-n \o/
23:23.19DocScrutinizer05Aoyagi: airodump
23:23.31Aoyagia hwat?
23:23.52DocScrutinizer05N900 runs airodump
23:24.32DocScrutinizer05and even aircrack
23:25.51DocScrutinizer05multiboot (NOT the friggin "app" of same name!) also is a feature hardly found on iPhones at least ;-D
23:27.37*** join/#maemo vi_ (~vi_@87.115.161.232)
23:28.23cobaltoi think a few things that droids can, for example some new background want internet connection
23:30.05*** part/#maemo sequantz (~sequantz@194.11.24.44)
23:43.55*** part/#maemo Aoyagi (~opera@222.18.broadband15.iol.cz)

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