| 00:00.59 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 00:36.03 | *** join/#maemo LinuxCode (~LinuxCode@fedora/LinuxCode) |
| 00:44.02 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 01:11.41 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 01:21.49 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 01:32.13 | *** join/#maemo LinuxCode (~LinuxCode@fedora/LinuxCode) |
| 01:49.55 | *** join/#maemo mschlens (~mschlens@p549360CF.dip0.t-ipconnect.de) |
| 01:55.26 | *** join/#maemo Defiant (erik@e179199030.adsl.alicedsl.de) |
| 01:55.30 | mashina | my n900 is dropping connections like flies |
| 01:55.41 | mashina | ssh seems stable but irc connections die a lot |
| 01:57.28 | *** join/#maemo robotanarchy_ (~robotanar@g227072118.adsl.alicedsl.de) |
| 02:02.24 | mashina | this is brutal |
| 02:02.31 | mashina | its dropping everything now |
| 02:02.51 | mashina | [86946.828430] wlan0: roaming signal from driver, sending LOWSIGNAL |
| 02:02.51 | mashina | [86965.158599] wlan0: roaming signal from driver, sending HIGHSIGNAL |
| 02:03.03 | mashina | it just does that |
| 02:06.24 | *** join/#maemo Termana (Termana@gateway/shell/panicbnc/x-fyhgodteiytjdejo) |
| 02:09.46 | mashina | its really bad |
| 02:09.56 | mashina | i have no idea how its this bad |
| 02:10.17 | mashina | i have little distance and little penetration needed |
| 02:25.51 | *** join/#maemo valerius (~user@95.153.176.230) |
| 02:54.40 | *** join/#maemo valerius (~user@85.26.180.140) |
| 02:56.51 | *** join/#maemo gormux (~gormux@46.29.125.12) |
| 03:02.31 | *** join/#maemo lxp (~lxp@188-23-59-125.adsl.highway.telekom.at) |
| 03:15.12 | *** join/#maemo valerius (~user@85.26.180.148) |
| 03:20.15 | *** join/#maemo Gh0sty (~ghosty@77.109.101.94) |
| 03:20.32 | *** join/#maemo hubutm20 (~hubutm20@79.113.87.197) |
| 03:24.53 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 03:31.09 | *** join/#maemo uen| (~uen@p5DCB194B.dip0.t-ipconnect.de) |
| 03:34.17 | *** join/#maemo maybeWTF (~cl@p5B164170.dip0.t-ipconnect.de) |
| 03:50.07 | *** join/#maemo Herbstb3rt (~Herbstber@drms-590ce7f3.pool.mediaWays.net) |
| 04:20.55 | *** join/#maemo valerius (~user@85.26.180.139) |
| 04:30.17 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 05:25.22 | DocScrutinizer05 | this doesn't mean a thing |
| 05:31.44 | DocScrutinizer05 | it's a normal message from WLAN driver not special to N900 nor maemo nor does it indicate an already flawed WiFi signal situation. In short: you see it everywhere and it not really means a problem: http://forum.ubuntu-it.org/viewtopic.php?t=500060 |
| 05:32.52 | DocScrutinizer05 | when your IRC connections die while ssh is stable, you got completely different problems than WiFi signal strength |
| 05:34.09 | DocScrutinizer05 | e.g your keep-alive ping interval might be too high to keep any NAT session alive that's possibly in the route from your client to IRC network server |
| 05:35.02 | DocScrutinizer05 | or your IRC server you connect to is simply flaky, not enything unheard in freenode either |
| 05:36.58 | DocScrutinizer05 | run a `ping 8.8.8.8` in a terminal on N900 and see if that stops the connection loss. |
| 05:39.06 | DocScrutinizer05 | also check what's your IRC server (you see this during login, in "freenode" tab. might be sth like pratchett.freenode.net (([Whois] mashina is online via pratchett.freenode.net (Rennes, France).)) Then run a ping against that server, possibly keeping open any NAT session and also stopping WLAN from entering deep sleep PSM |
| 05:39.59 | DocScrutinizer05 | if that changes situation repeatably, come back here for further advice, since a ping is no fix but only a diagnostic means |
| 05:46.02 | DocScrutinizer05 | http://www.spinics.net/lists/maemo-users/msg16155.html |
| 05:46.17 | DocScrutinizer05 | try to set PSM to medium or low |
| 05:47.00 | DocScrutinizer05 | possibly your AP and the N900 WiFi firmware don't harmonize on PowerSavingMode |
| 05:49.54 | *** join/#maemo LauRoman (~LauRoman@5-14-90-91.residential.rdsnet.ro) |
| 05:50.27 | DocScrutinizer05 | http://features.techworld.com/mobile-wireless/4103/a-guide-to-wi-fi-power-save-technologies/ |
| 05:52.54 | DocScrutinizer05 | http://wiki.maemo.org/Wifi_power_saving_mode |
| 06:11.18 | *** join/#maemo Custodian (~Custodian@46.39.225.253) |
| 06:50.39 | *** join/#maemo bef0rd_ (~bef0rd@186.29.27.224) |
| 07:51.02 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 07:54.19 | *** join/#maemo Sludge321 (~Sludge321@106-68-93-72.dyn.iinet.net.au) |
| 08:02.37 | *** join/#maemo NIN101 (~NIN@p5DD28960.dip0.t-ipconnect.de) |
| 08:15.46 | *** join/#maemo zammy (~sammy@ppp-198-254.98-62.inwind.it) |
| 08:20.42 | *** join/#maemo sq-one (~sq-one@p549ABAA8.dip0.t-ipconnect.de) |
| 08:22.00 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 08:35.26 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 08:40.02 | *** join/#maemo shentey (~shentey@g226180242.adsl.alicedsl.de) |
| 09:12.07 | DrCode | hi all |
| 09:12.33 | DrCode | is there simple appliction that can send sms when missed call? |
| 09:12.39 | DrCode | like I will can back or I am driving? |
| 09:17.34 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 09:32.24 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 09:37.53 | *** join/#maemo jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 09:55.18 | *** join/#maemo shaggycat (~shaggycat@178.217.27.70) |
| 09:56.17 | shaggycat | Hi! i need help: my n900 never boot if battery not copleate charge |
| 09:56.40 | shaggycat | it's always switch off, if i try power on my N900 |
| 09:56.55 | shaggycat | now i need switch on my N900 fastly |
| 09:57.04 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 09:57.23 | shaggycat | is any hack to power on n900 without check charger of battery? |
| 09:59.10 | jonwil | if your N900 wont power on then your battery doesn't have enough power |
| 09:59.16 | jonwil | you need to charge your battery |
| 09:59.22 | jonwil | then it will properly charge |
| 10:00.12 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 10:01.06 | shaggycat | it's hardware bug, i think |
| 10:01.31 | *** join/#maemo zemmy (~sammy@ppp-198-254.98-62.inwind.it) |
| 10:01.31 | shaggycat | loader don't correct check level of battery |
| 10:01.57 | shaggycat | only if battery copmplete (100%) charging, |
| 10:02.05 | shaggycat | my phone load OS :( |
| 10:02.17 | shaggycat | if green light is |
| 10:02.30 | shaggycat | if ellow light, it's never boot :( |
| 10:02.46 | shaggycat | is any way to hack it? |
| 10:03.07 | shaggycat | f.e. remove check of battery level in loader? |
| 10:04.16 | shaggycat | how i may hack the loader of Maemo OS? |
| 10:09.21 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 10:10.12 | DocScrutinizer05 | this is hardware and never heard about such problem, I guess yiur battery is defect |
| 10:12.45 | shaggycat | i have 3 battery |
| 10:13.16 | shaggycat | one good, and 2 not good (small time for work N900) |
| 10:13.49 | shaggycat | degradation on small temperature (I'm from Russian, russian winter...) |
| 10:14.07 | shaggycat | and with 3 battery is this bug :( |
| 10:14.50 | shaggycat | my be i may remove checker of battery level with OS loader? |
| 10:14.54 | shaggycat | how i may it? |
| 10:15.15 | shaggycat | *i'm from Russia |
| 10:15.52 | shaggycat | could anybody help me to hack OS loader? |
| 10:16.56 | cehteh | you cant repair a dead battery with software |
| 10:17.34 | ShadowJK | As far as I know, nobody has tried to hack the os loader |
| 10:17.34 | shaggycat | who check level of battery before load os? |
| 10:17.53 | shaggycat | is :(( |
| 10:18.04 | sono | mdew |
| 10:19.09 | shaggycat | also, i have another N900 with not light of screen |
| 10:19.19 | zammy | ... |
| 10:19.43 | shaggycat | may be, in service may put miscro cheme of loader, |
| 10:20.06 | shaggycat | and put it on another n900? |
| 10:20.51 | zammy | I found bleach in app and I installed it... but no gui? |
| 10:22.01 | ShadowJK | does orange led shine steady, or is it glowing/pulsing? |
| 10:22.18 | ShadowJK | Anythinh shown on screen? |
| 10:23.23 | zammy | and my dropbox does not recognize my account |
| 10:23.30 | zammy | does never authenticate |
| 10:25.54 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 10:34.59 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 10:36.38 | *** join/#maemo valerius (~user@85.26.180.152) |
| 10:38.25 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 10:48.15 | *** join/#maemo tzafrir (~tzafrir@local.xorcom.com) |
| 10:50.04 | DrCode | hi DocScrutinizer05 |
| 10:50.46 | DrCode | I am looking for simple appliction that can send sms when I missed call, some sms template, like "I am a way" or "I am in a meeting" any idea? |
| 10:55.43 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 10:59.34 | *** join/#maemo Hurrian (~textual@unaffiliated/rikanee) |
| 11:02.52 | DocScrutinizer05 | look for the python script in ~phonecontrol. It's not simple but does almost what you're looking for |
| 11:06.49 | DocScrutinizer05 | just it waits for an inbound SMS "ping" to answer hardcoded "pong" |
| 11:07.21 | DocScrutinizer05 | yours needs to wait for inbound call or even better for inbound call missed notifier popping up |
| 11:10.03 | *** join/#maemo arcean (~arcean@aael192.neoplus.adsl.tpnet.pl) |
| 11:13.31 | *** join/#maemo brzys (~brzys@176.31.26.206.speedhost.pl) |
| 11:19.49 | *** join/#maemo arcean (~arcean@aael192.neoplus.adsl.tpnet.pl) |
| 11:21.47 | DrCode | thankyou |
| 11:28.24 | jonwil | DocScrutinizer: ping |
| 11:28.30 | jonwil | DocScrutinizer05: ping |
| 11:34.13 | DocScrutinizer05 | hmm? |
| 11:34.28 | jonwil | hmm, now I forget why I wanted to talk to you :P |
| 11:35.45 | DocScrutinizer05 | ayeeeh |
| 11:36.47 | jonwil | btw I will do whatever I can towards helping with Neo900 RE work |
| 11:36.59 | DocScrutinizer05 | maybe you want to know that I'm not inclined to mce-bugfix any time soon |
| 11:37.15 | DocScrutinizer05 | no time |
| 11:38.36 | jonwil | heck, MCE is already the biggest piece of reverse engineering work in the maemo community :) |
| 11:38.50 | dos1 | DocScrutinizer05: hello |
| 11:38.54 | DocScrutinizer05 | hi! |
| 11:38.57 | dos1 | any comments about that news piece, or should i publish it as it is? |
| 11:39.19 | DocScrutinizer05 | well, I already siad it's probably ok |
| 11:39.25 | DocScrutinizer05 | ask Nikolaus though |
| 11:39.30 | dos1 | k |
| 11:41.18 | DocScrutinizer05 | s/all donated/your donated/ |
| 11:43.22 | jonwil | I just hope the USB port on my N900 doesn't fail, otherwise all my dev work will grind to a halt (its dangerously close to failing) |
| 11:43.34 | DocScrutinizer05 | and maybe we don't want customers to judge about feasibility, that sounds not right. We want to allow them to judge if the project is what they expect |
| 11:43.43 | jonwil | I would do the fix for it but I dont have the skills, tools or know-how |
| 11:44.21 | DocScrutinizer05 | jonwil: then immediately let it repair in a repair shop |
| 11:44.29 | DocScrutinizer05 | **imediately** |
| 11:44.34 | jonwil | I cant find a local repair shop that can do repairs |
| 11:44.44 | jonwil | all of them dont even wanna touch a N900 |
| 11:44.55 | jonwil | only usual crap like iCrap screen repalcements |
| 11:44.56 | DocScrutinizer05 | damn, what idiots |
| 11:45.21 | DocScrutinizer05 | no nokia care around? |
| 11:46.05 | jonwil | there is a nokia care but I think they dont do any repairs, just send things away for advice |
| 11:46.09 | DocScrutinizer05 | or a technical university or club? |
| 11:46.28 | jonwil | dont know anyone with electronics skills around |
| 11:50.21 | jonwil | its a matter of finding not just someone that does phone repairs but someone who can do the USB repair |
| 11:50.30 | DocScrutinizer05 | dos1: on the final device price, >>and give us a feedback if there are enough customers so we can dare to continue development. |
| 11:52.31 | DocScrutinizer05 | jonwil: everybody who does phone repair that involves soldering can do *now*. This may change to the worse once you completely ripped the USB off the mainboard |
| 11:52.43 | jonwil | ok |
| 11:54.20 | *** join/#maemo Neutron116 (~neutron@80.202.98.36) |
| 11:55.42 | jonwil | Not exactly sure what I should be asking for when I go to these shops, i.e. what I should tell them I need them to do |
| 11:56.33 | DocScrutinizer05 | print out this: |
| 11:56.36 | DocScrutinizer05 | ~usbfix |
| 11:56.36 | infobot | usbfix is probably http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater) |
| 11:56.44 | DocScrutinizer05 | there are pictures |
| 11:57.37 | DocScrutinizer05 | more than sufficient for an electrician with a soldering iron to know what to do |
| 11:58.18 | DocScrutinizer05 | probably even a goldsmith could do |
| 11:58.31 | jonwil | so basically go to the shop, show them the stuff between the "--------------------------" in that post and then ask if that is something they have the facilities to carry out |
| 11:59.34 | DocScrutinizer05 | http://talk.maemo.org/showpost.php?p=547991&postcount=20 |
| 12:00.03 | jonwil | ok |
| 12:00.39 | *** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net) |
| 12:00.45 | psycho_oreos | jonwil, there's a mob known as FixMyMobile, it's where I got/am getting my nokia phone/devices fixed. |
| 12:01.12 | DocScrutinizer05 | http://talk.maemo.org/showpost.php?p=1191819&postcount=116 |
| 12:01.31 | jonwil | they are in Brisbane, I am in Perth |
| 12:01.54 | DocScrutinizer05 | http://talk.maemo.org/showpost.php?p=1073214&postcount=22 |
| 12:02.06 | psycho_oreos | Hmm bugger, there might be stalls that can do it. |
| 12:02.59 | jonwil | I will probably print out those links and go to a few repair shops (not the stalls that do "iphone screen repairs" and are filled with 100s of iPhone and iPad and iPod covers and cases, the actual shops that do repairs |
| 12:03.22 | jonwil | show them the N900 and the printout and say "is this a fix you can do and what will it cost" |
| 12:03.26 | DocScrutinizer05 | DO NOT use glue |
| 12:04.12 | DocScrutinizer05 | also print out service manual L1_2 |
| 12:04.34 | DocScrutinizer05 | they will need it to correctly and safely disassemble the device |
| 12:05.02 | jonwil | well at least one shop I know is the shop that replaced the screen surround parts (the one with the little Nokia logo on it) |
| 12:05.47 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 12:06.53 | DocScrutinizer05 | in L1_2 cross out all pictures that show steps not needed to access the USB port |
| 12:07.36 | DocScrutinizer05 | otherwise the dude in shop might get overwhelmed by the number of steps it seems to take to do this disassembly |
| 12:08.13 | jonwil | I will probably be going to shops that say "we do board level repairs" |
| 12:08.20 | jonwil | e.g. this one http://www.ctf.com.au/physical_damage.html |
| 12:08.29 | jonwil | that one says they can do anything up to replacing chips |
| 12:08.43 | jonwil | I will try a few shops in my local area |
| 12:11.22 | DocScrutinizer05 | https://sites.google.com/site/svcr0c0/n900 is maybe better than L1_2 but do NOT use fingernail to unplug the cable, use a credit card and lever it out carefully, it's very delicate |
| 12:13.25 | jonwil | I will worry about it |
| 12:13.37 | DocScrutinizer05 | jonwil: yes, that shop sounds very adequate |
| 12:14.01 | jonwil | there are a few that can probably do it |
| 12:14.18 | jonwil | I will go to a few with printout of the USB repair bits and see what they say about whether they can do it |
| 12:14.21 | DocScrutinizer05 | they explicitly offer "charger port" fix |
| 12:14.58 | DocScrutinizer05 | they also offer backup battery replacement, so maybe you want to get this as well when you're already there |
| 12:15.12 | jonwil | yeah that makes sense |
| 12:17.05 | jonwil | If they dont know N900 because they dont have the service manual, I will point them at the PDF :) |
| 12:19.21 | DocScrutinizer05 | jonwil: when you drop by at them, can you ask them if they can replace the SoC (and storage) in a N9 please? |
| 12:19.48 | DocScrutinizer05 | particularly if they can get replacement chip |
| 12:20.42 | *** part/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 12:21.04 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 12:22.44 | DocScrutinizer05 | if they can, you might want to get as many as you can get, at least for your own Neo900 to get 1GB of RAM |
| 12:23.26 | jonwil | I doubt I will remember to ask about that |
| 12:23.30 | jonwil | but if I do I will ask :P |
| 12:23.51 | DocScrutinizer05 | I will help you to remember |
| 12:23.52 | jonwil | as for Neo900, I haven't said I can afford to buy a Neo900 |
| 12:24.24 | DocScrutinizer05 | when the USB fix ever fails, your only option is a Neo900, and that will not come with 1GB of RAM when you can't find that chip |
| 12:25.15 | DocScrutinizer05 | now I guess you can't help but remember this the very moment you receive your fixed N900 at that shop |
| 12:25.53 | jonwil | thats if the shop can fix it, I dont know if they can or not |
| 12:25.57 | DocScrutinizer05 | since you will wonder how good this USB repair will save your N900 |
| 12:26.11 | DocScrutinizer05 | they *can* fix this USB |
| 12:26.16 | DocScrutinizer05 | 110% |
| 12:26.39 | DocScrutinizer05 | it's their easiest job of the day |
| 12:27.28 | jonwil | assuming its not already too damaged to repair with that fix |
| 12:27.36 | DocScrutinizer05 | and finding spare RAM chip for N9 will be their all time nightmare |
| 12:27.51 | DocScrutinizer05 | does it still work? |
| 12:28.33 | jonwil | it appears to |
| 12:28.41 | DocScrutinizer05 | then they CAN fix it |
| 12:28.58 | DocScrutinizer05 | unless you ruin it before they can do |
| 12:29.13 | jonwil | it works but there was a time when I bumped the plug and it flicked to "disconnect charger" and "charging" |
| 12:29.18 | jonwil | hence why I am starting to worry |
| 12:29.31 | Sicelo | is one of those who doubt they can afford Neo900 :( |
| 12:29.40 | DocScrutinizer05 | tell them about it, they can manage that too |
| 12:29.44 | jonwil | I am also on the list of people who cant afford a Neo900 |
| 12:30.29 | jonwil | at least so long as I remain unemployed :( |
| 12:30.46 | DocScrutinizer05 | jonwil: I guess you qualify for a developer-program device |
| 12:30.56 | *** join/#maemo kolp (~quassel@tmo-108-157.customers.d1-online.com) |
| 12:30.58 | Sicelo | +1.. he deserves one :) |
| 12:31.09 | jonwil | I think my work on MCE would be more than enough reason for dev-program access |
| 12:31.48 | jonwil | it is the biggest single piece of reverse engineering done in the history of Maemo |
| 12:32.34 | Sicelo | i saw in #maemo-cssu backscroll.. so MCE has now been busted open? completely? |
| 12:32.51 | *** join/#maemo jdoles (~jdoles@unaffiliated/jdoles) |
| 12:32.54 | jonwil | yep |
| 12:32.56 | jdoles | How can I see recent events? |
| 12:33.11 | Sicelo | nice one jdoles :P |
| 12:33.16 | jdoles | I accidentally closed the event. |
| 12:33.22 | Sicelo | recent events .. what events? |
| 12:33.23 | DocScrutinizer05 | it doesn't matter if somebody deserves anything - that may matter later when we have mass production devices. Developer devices are loaners handed out to those who *need* one to make fremantle port work |
| 12:33.31 | jonwil | :) |
| 12:33.35 | jdoles | Sicelo: "missed calls", "you have a new message", etc. |
| 12:33.44 | jdoles | Sicelo: the thing in yellow. |
| 12:33.46 | jonwil | well I dont deserve a loaner device |
| 12:34.01 | jonwil | because I doubt I will be able to contribute enough dev programming time to make good use of it |
| 12:34.37 | jonwil | i.e. I would be doing more RE than writing code and I dont need a dev device for RE |
| 12:34.52 | jdoles | A loaner device should go to whoever already has an application running in a virtual environment. |
| 12:34.59 | Sicelo | jdoles: your message is still on Conversations, highlighted blue. and your missed call is still in the Phone application |
| 12:35.18 | jonwil | loaner devices should also go very much to kernel guys |
| 12:35.18 | DocScrutinizer05 | jdoles: we're not dealing with apps here |
| 12:35.27 | jonwil | who would be doing kernel and system-bits dev |
| 12:35.40 | jonwil | i.e. MCE, kernel, DSME, BME, ke-recv and other hardware bits |
| 12:35.41 | DocScrutinizer05 | +1 |
| 12:35.53 | DocScrutinizer05 | exactly |
| 12:36.05 | jonwil | So yeah there is now code available that (assuming no bugs caused by incorrect reverse engineering) should match exactly to MCE of PR1.3 |
| 12:36.05 | Sicelo | agrees |
| 12:36.08 | DocScrutinizer05 | apps are considered compatible |
| 12:36.31 | jdoles | I think if the device cannot be developed without physical hardware that the software ecosystem is broken. |
| 12:36.37 | DocScrutinizer05 | so no app developer needs a devel device |
| 12:36.44 | jonwil | so yeah I dont need a loaner because I wont be writing the kind of code people need loaners for |
| 12:37.11 | DocScrutinizer05 | jdoles: I think you lack a complete picture of what we're talking about here# |
| 12:37.14 | Sicelo | jdoles: ? |
| 12:37.23 | jdoles | DocScrutinizer05: probably. |
| 12:38.26 | jonwil | so yeah I think my N900 is still lowish risk of USB damage as of right now but its high enough risk that its worth getting the USB repair done now rather than taking risk of e.g. bumping device wrong and causing cable to pull USB device slightly and break it too much to fix |
| 12:38.54 | DocScrutinizer05 | yes |
| 12:39.02 | jdoles | Sicelo: I think for any "driver" (i.e. runs in some kind of privileged mode) it should be possible to develop it without having a physical device. |
| 12:39.22 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 12:39.25 | DocScrutinizer05 | sure, but how would you TEST it? |
| 12:40.00 | jdoles | DocScrutinizer05: there is no reason to test it, unless the hardware guys didn't write a contract (cf. design by contract). |
| 12:40.14 | DocScrutinizer05 | how would you TEST the new accelerometer in Neo900? |
| 12:40.27 | DocScrutinizer05 | WUT? |
| 12:40.47 | jdoles | If it's some community hackjob, then I suppose it couldn't be done like this. |
| 12:40.54 | *** join/#maemo arcean (~arcean@aael192.neoplus.adsl.tpnet.pl) |
| 12:40.56 | jonwil | I have seen enough hardware dev stuff to know that writing drivers without the physical hw is a bad idea |
| 12:40.57 | DocScrutinizer05 | uhuh |
| 12:41.00 | Sicelo | yay! :-/ |
| 12:41.29 | DocScrutinizer05 | like I said, you're missing a clear picture of what we're doing |
| 12:41.50 | DocScrutinizer05 | btw *I* am "the hw-guy" |
| 12:42.34 | jdoles | If you created the hardware, you should write a specification saying after how many seconds a particular signal arrives. |
| 12:42.35 | DocScrutinizer05 | and community is writinf the drivers and adaption, e.g. in MCE |
| 12:42.47 | DocScrutinizer05 | aha |
| 12:42.50 | jdoles | The same for the shape of the signal, etc. |
| 12:42.55 | DocScrutinizer05 | interesting |
| 12:43.03 | DocScrutinizer05 | ;-P |
| 12:43.12 | jdoles | I.e. a complete specification of everything that your magic device does. |
| 12:43.13 | jonwil | writing drivers with just the specs is a bad idea, you need physical hw at all |
| 12:43.23 | DocScrutinizer05 | *sigh* |
| 12:43.30 | jdoles | You only need physical hardware if the specification is not complete. |
| 12:43.37 | DocScrutinizer05 | jonwil: futile effort |
| 12:43.52 | jdoles | That way, there is even no reason to test it. You can just prove that it works. |
| 12:44.05 | DocScrutinizer05 | BWAHAHAHA |
| 12:44.24 | jonwil | I meant you do need physical hardware |
| 12:44.32 | jdoles | I understand, and I am saying you don't. |
| 12:44.40 | dos1 | life isn't *that* easy |
| 12:44.53 | kolp | is looking for popcorn |
| 12:45.00 | jonwil | jdoles: Have you ever done linux kernel development? Hardware work? Anything low-level? |
| 12:45.20 | dos1 | especially when we're talking about pretty complicated device consisting of lots of 3rd-party modules |
| 12:45.20 | jonwil | If not, stfu and let the people who HAVE done such work decide how it is best done |
| 12:45.21 | jdoles | jonwil: I have written some drivers. |
| 12:45.29 | jonwil | hmmm ok |
| 12:45.45 | jonwil | have you written hardware drivers without hardware (or simulated hardware) in hand? |
| 12:46.00 | jdoles | jonwil: no. |
| 12:46.06 | Sicelo | :D |
| 12:46.10 | DocScrutinizer05 | ask freemangordon about DT and clock dividers in 3.12 kernel, and how he had debuugged that crap when he hadn't had access to hardware to test it |
| 12:46.12 | jdoles | jonwil: or, actually, I did. |
| 12:46.30 | jdoles | jonwil: I got a few weeks to develop a driver without the physical hardware and only a manual. |
| 12:47.02 | jdoles | jonwil: but this is still irrelevant. |
| 12:47.26 | jdoles | jonwil: just because everyone is doing it in a particular way now, doesn't mean they aren't all doing it wrong. |
| 12:47.45 | jdoles | jonwil: 99.99% of people also develop software in the wrong way. |
| 12:47.59 | DocScrutinizer05 | sure |
| 12:48.16 | jdoles | All I see are projects that are never *finished*. |
| 12:48.16 | dos1 | so yes, in utopian world you're absolutely right |
| 12:48.21 | DocScrutinizer05 | and jes err jdoles is our savior who tells us the truth |
| 12:48.27 | dos1 | but utopian world does not exists |
| 12:48.42 | jdoles | A computer is just a circuit which is evaluated. |
| 12:48.53 | jdoles | (repeatedly) |
| 12:49.06 | jdoles | I don't see any reason for introducing errors. |
| 12:49.12 | Sicelo | <PROTECTED> |
| 12:49.18 | DocScrutinizer05 | the great jdoles who never wrote a code with any bug, not a single one. His software works when finished, doesn't need testing. Ever |
| 12:51.05 | DocScrutinizer05 | actualle he removed the backspace key from all his keyboards |
| 12:51.46 | DocScrutinizer05 | since he never falls for any mistake |
| 12:52.42 | DocScrutinizer05 | jdoles: the problem is: even when we all learn to be as smart as you seem to be, we need to deal with code written by other less smart devels |
| 12:52.54 | DocScrutinizer05 | unless we write everything anew from scratch |
| 12:53.15 | jdoles | DocScrutinizer05: the solution for that is to fire all those people. |
| 12:53.29 | dos1 | :) |
| 12:53.37 | jdoles | I applaud rewriting everything from scratch. |
| 12:53.42 | DocScrutinizer05 | and particularly for hw drivers I don't know a 100% proven test except running it against the real hardware |
| 12:53.48 | jdoles | If you don't do it right the first time, you just need to do it again. |
| 12:54.14 | DocScrutinizer05 | jdoles: I' almost ready to kick you for trolling |
| 12:55.04 | jdoles | I find it a rather weak excuse to point at other supposedly less smart people and blame them for the failure. |
| 12:55.22 | DocScrutinizer05 | one more please |
| 12:55.27 | *** mode/#maemo [+o DocScrutinizer05] by ChanServ |
| 12:55.52 | dos1 | jdoles: if you've got all resources needed to develop whole device from scratch by yourself, then go for it! |
| 12:56.35 | dos1 | we will be happy if we find resources to develop just a device using 3rd-party modules, which might or might not be perfect |
| 12:56.38 | dos1 | and usually, are not |
| 12:56.44 | DocScrutinizer05 | dos1: the only thing he can do, since even testing the 100% bugfree nature of the other co-devels needs testing on real hardware |
| 12:57.09 | DocScrutinizer05 | dos1: don't feed the troll |
| 12:58.05 | DocScrutinizer05 | his approach is from utopia anyway |
| 12:58.13 | DocScrutinizer05 | or just trolling |
| 12:59.45 | DocScrutinizer05 | and if he actually written anything more complex than bitbanging I2C and claims to have done this without a single glitch in it that needed testing to get debigged, he's a liar |
| 12:59.54 | *** join/#maemo rd1381 (~quassel@91.98.9.51) |
| 13:00.11 | DocScrutinizer05 | s/if he/if he claims to have/ |
| 13:00.13 | rd1381 | hi |
| 13:00.26 | rd1381 | can someboy help me fix my n900 speed bug |
| 13:01.04 | DocScrutinizer05 | spped? |
| 13:01.06 | Sicelo | speed bug rd1381? |
| 13:01.08 | DocScrutinizer05 | speed even? |
| 13:01.10 | jdoles | There is a way in which you don't need to trust the output from other developers. |
| 13:01.53 | rd1381 | yes |
| 13:02.24 | rd1381 | i restored my n900 twice but still it has this wierd bug |
| 13:02.59 | rd1381 | when i use apt-get it gets the first 300kb of files ok ut then it gets stuck |
| 13:04.06 | *** join/#maemo amospalla (~amospalla@unaffiliated/amospalla) |
| 13:04.19 | DocScrutinizer05 | df -h |
| 13:05.55 | rd1381 | can somebody help me? |
| 13:06.31 | DocScrutinizer05 | pastebin the result of `df -h` |
| 13:06.38 | rd1381 | oh |
| 13:06.40 | rd1381 | sorry |
| 13:07.00 | rd1381 | i can pasebin it |
| 13:07.13 | rd1381 | web site loads very slow and buggy |
| 13:07.28 | rd1381 | but isee that my tmpfs is only 1mb |
| 13:07.39 | rd1381 | and 256kb |
| 13:08.08 | rd1381 | "/tmp and /var" |
| 13:08.12 | *** join/#maemo Custodian (~Custodian@46.39.225.253) |
| 13:08.21 | rd1381 | is this normal? |
| 13:08.32 | DocScrutinizer05 | http://privatepaste.com/94f3935019 compare please |
| 13:09.43 | rd1381 | i dont have a second sd card inserted |
| 13:09.53 | rd1381 | but others are more or less the same |
| 13:10.08 | DocScrutinizer05 | hmm |
| 13:10.15 | rd1381 | excpt my /home is 8 gb |
| 13:10.22 | DocScrutinizer05 | doesn't matter |
| 13:10.31 | DocScrutinizer05 | :-) |
| 13:10.33 | rd1381 | and mydocs is 21gb |
| 13:10.41 | DocScrutinizer05 | yeah, obviously |
| 13:11.05 | zammy | a brand new maemo on n900 is funny |
| 13:11.10 | DocScrutinizer05 | then you seem to have other problems |
| 13:11.24 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 13:11.44 | DocScrutinizer05 | WLAN? |
| 13:11.49 | rd1381 | yep |
| 13:11.57 | DocScrutinizer05 | did a bandwith test? |
| 13:12.50 | DocScrutinizer05 | wget <somebigfile-URL> -O /dev/null |
| 13:13.13 | rd1381 | no wget :) |
| 13:13.19 | DocScrutinizer05 | o.O |
| 13:14.13 | *** join/#maemo jrocha (~JRocha@AAnnecy-651-1-281-233.w86-200.abo.wanadoo.fr) |
| 13:14.31 | DocScrutinizer05 | sysinfo-tool -g /device/sw-release-ver |
| 13:16.38 | rd1381 | its the " rx-51 2009se_20.2010.36-2.003_pr_003 |
| 13:17.02 | DocScrutinizer05 | hmm, you should update |
| 13:17.22 | rd1381 | update? |
| 13:17.29 | rd1381 | its the latest version |
| 13:17.35 | DocScrutinizer05 | ~pr131 |
| 13:17.36 | infobot | from memory, combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://maemo.cloud-7.de/maemo5/fiasco+co/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin or http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin |
| 13:18.44 | DocScrutinizer05 | but that's probably not the culprit of your troubles |
| 13:18.52 | rd1381 | yes |
| 13:19.06 | rd1381 | but igot these from nokia site for firmware |
| 13:19.12 | DocScrutinizer05 | anywy I'd trecommend reflashing |
| 13:19.42 | rd1381 | where is the site realse notes for this update you linked? |
| 13:19.46 | DocScrutinizer05 | yes, it's the last "official" one |
| 13:20.02 | DocScrutinizer05 | there's none, basically |
| 13:20.13 | DocScrutinizer05 | PR1.3.1 got updated via SSU |
| 13:20.29 | DocScrutinizer05 | Nokia never officially published the fiasco image |
| 13:20.31 | rd1381 | ssu from nokia or cummunity? |
| 13:20.37 | DocScrutinizer05 | nokia |
| 13:21.07 | DocScrutinizer05 | look at 2nd link above |
| 13:22.21 | DocScrutinizer05 | nokia distribution service - file repository . nokia . com |
| 13:22.37 | rd1381 | its for what region? |
| 13:22.53 | DocScrutinizer05 | err MR0 is globl |
| 13:23.06 | DocScrutinizer05 | you got 003 |
| 13:23.15 | DocScrutinizer05 | but global is safe |
| 13:23.30 | rd1381 | ok |
| 13:23.54 | rd1381 | but i dont think bug is from this image |
| 13:24.12 | *** join/#maemo FlameReaper-PC (~honoo-pc@jiz-214-122.tm.net.my) |
| 13:24.16 | rd1381 | but idont have any other thing installed so |
| 13:24.21 | DocScrutinizer05 | prolly not. But maybe from some weird app or patch you installed |
| 13:24.55 | DocScrutinizer05 | aa wait |
| 13:25.28 | DocScrutinizer05 | ls -l /home/user/.rtcom-eventlogger/el-v1.db |
| 13:25.37 | DocScrutinizer05 | should be <1MB |
| 13:26.37 | DocScrutinizer05 | if it's larger, then you eventually will get cought in swap hell that brings system to a grinding halt |
| 13:29.38 | dos1 | 38.5M /home/user/.rtcom-eventlogger/el-v1.db |
| 13:29.42 | dos1 | wow :) |
| 13:31.19 | rd1381 | i got 43008 for its size |
| 13:31.27 | *** join/#maemo kolp (~quassel@tmo-108-157.customers.d1-online.com) |
| 13:31.39 | *** join/#maemo arcean_ (~arcean@aael192.neoplus.adsl.tpnet.pl) |
| 13:35.13 | *** join/#maemo sequantz (~sequantz@194.11.24.44) |
| 13:36.34 | *** join/#maemo FlameReaper-PC (~honoo-pc@jiz-214-122.tm.net.my) |
| 13:36.56 | rd1381 | i have this wierd bug |
| 13:37.26 | rd1381 | i used a proxy to connect to test if it was network problem or not |
| 13:38.07 | rd1381 | when i close the proxy on my pc and use apt-get to update it correctly says it cant connect |
| 13:38.40 | rd1381 | but when i run the apt-get and then close the proxy it doesnt give any error and gets stuck in getting files |
| 13:39.05 | DocScrutinizer05 | hmm, that *might* be normal |
| 13:40.35 | DocScrutinizer05 | just an idea: cat /etc/hosts |
| 13:40.38 | rd1381 | not on my pc |
| 13:40.45 | rd1381 | sigh |
| 13:40.58 | rd1381 | its very frustrating |
| 13:41.01 | DocScrutinizer05 | should have 127.0.0.1 only |
| 13:41.19 | rd1381 | my download speed is very low on my n900 |
| 13:41.29 | rd1381 | but before it wasnt like this |
| 13:42.45 | DocScrutinizer05 | well, I can't help much. Slow download speed is way too fuzzy a bug report |
| 13:43.06 | rd1381 | yes i know |
| 13:43.18 | rd1381 | it not just the slow speed |
| 13:43.31 | rd1381 | its the getting stuck that .... |
| 13:44.17 | DocScrutinizer05 | I'd suggest to test it on another hotspot |
| 13:45.02 | DocScrutinizer05 | install and run iwconfig |
| 13:45.29 | DocScrutinizer05 | install and scrutinze syslog |
| 13:45.43 | rd1381 | scrutinze? |
| 13:45.45 | DocScrutinizer05 | run ping and wget tests |
| 13:45.58 | rd1381 | i cant install any thing on n900 |
| 13:46.04 | DocScrutinizer05 | studdy syslog for anything suspicious |
| 13:46.10 | DocScrutinizer05 | then reflash |
| 13:46.28 | rd1381 | can i use the firmware u send with older fisco image? |
| 13:46.30 | DocScrutinizer05 | I mean... when you can't install anything |
| 13:46.48 | DocScrutinizer05 | hmm? |
| 13:47.02 | DocScrutinizer05 | this is a fiasco image |
| 13:47.15 | rd1381 | RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin with Latest Vanilla version of the eMMC content for Nokia N900-RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM |
| 13:47.41 | DocScrutinizer05 | yes |
| 13:47.50 | rd1381 | btw |
| 13:47.58 | rd1381 | what is the n900 root pass |
| 13:48.04 | DocScrutinizer05 | nothing |
| 13:48.06 | rd1381 | does it have one? |
| 13:48.08 | Apic | Will nitdroid-installer blow up my U-Boot? |
| 13:48.14 | rd1381 | caus ei cant use sudo |
| 13:48.22 | DocScrutinizer05 | use root |
| 13:48.29 | DocScrutinizer05 | or sudo gainroot |
| 13:48.42 | Apic | nitdroid-installer 0.2.6-3 |
| 13:48.45 | DocScrutinizer05 | but you need to install rootsh for that |
| 13:49.04 | DocScrutinizer05 | Apic: no idea, odds are it will |
| 13:49.10 | Apic | So 'root' is a backdoor that's avail' from the Start? |
| 13:49.23 | DocScrutinizer05 | no, you need to install rootsh |
| 13:49.23 | Apic | B-( |
| 13:49.26 | Apic | ic |
| 13:49.41 | Apic | Or enable R&D-Mode, eh? ;-) |
| 13:49.47 | DocScrutinizer05 | or that |
| 13:50.17 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 13:50.20 | DocScrutinizer05 | though that's not recommended |
| 13:50.31 | DocScrutinizer05 | it has side effects |
| 13:50.41 | rd1381 | wow |
| 13:50.43 | rd1381 | nm |
| 13:50.50 | rd1381 | i think i found the problem |
| 13:51.20 | Apic | Yep, it tries to install multiboot-kernel-maemo |
| 13:51.34 | Apic | Maybe there's a newer Ver than 0.2.6-3 on tha Intarwebs. |
| 13:51.35 | DocScrutinizer05 | ~maemo-multiboot |
| 13:51.35 | infobot | maemo-multiboot is probably deprecated, and a horrible hack. PROBLEMS WITH NITDROID/MULTIBOOT? reflash rootfs&kernel aka COMBINED |
| 13:52.21 | DocScrutinizer05 | damn!!! |
| 13:52.30 | DocScrutinizer05 | without telling us what's been the problem |
| 13:52.34 | Apic | B-( |
| 13:53.08 | DocScrutinizer05 | makes a note that rd1381 is not a nice guy |
| 13:53.45 | Apic | There's 0.2.7 |
| 13:53.47 | Apic | I'll look at it |
| 13:57.50 | Apic | Nope, I see I even had 0.2.8, and it _still_ depends on that bricky multiboot :-( |
| 13:57.56 | *** join/#maemo kolp_ (~quassel@anon.camaya.net) |
| 13:58.02 | Apic | I give up for the Moment, do not need Android _that_ urgent anyhow. |
| 14:08.40 | *** join/#maemo kolp (~quassel@tmo-108-157.customers.d1-online.com) |
| 14:14.57 | *** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa) |
| 14:27.35 | *** join/#maemo kolp_ (~quassel@148.122.197.152) |
| 14:32.43 | jdoles | I set my ringtone to a custom file. When I click on this custom file it plays, when I get a call, I get the default sound. This looks like a very basic bug or is the UI just so terrible that I am misunderstanding? |
| 14:38.19 | *** join/#maemo stef_204 (~kvirc@unaffiliated/stef-204/x-384198) |
| 14:38.54 | *** part/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 14:39.53 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 14:44.07 | jdoles | Jolly, a bug from 2010. http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Phone-doesnt-ring-after-I-change-profile-from-Silent-to-General/td-p/712436 |
| 14:47.12 | jdoles | Apparently it was caused by some "community" code. |
| 14:57.49 | *** join/#maemo wmarone__ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 15:03.38 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:03.50 | *** join/#maemo Gizmokid2005 (~Gizmokid2@dedi1.gizmokid2005.com) |
| 15:20.37 | *** join/#maemo mm0ss (~moss@nl1x.mullvad.net) |
| 15:23.31 | *** join/#maemo Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 15:24.04 | Sicelo | where is "community" code in that bug/link? |
| 15:25.09 | Sicelo | looks like jdoles bought the wrong device. a samsung will likely be a better device for him |
| 15:25.27 | *** join/#maemo psychologe (~user@58.243.250.232) |
| 15:35.38 | mm0ss | Hi |
| 15:41.23 | *** join/#maemo arcean_ (~arcean@aael192.neoplus.adsl.tpnet.pl) |
| 15:41.51 | *** join/#maemo hardfalcon (~hardfalco@f048106026.adsl.alicedsl.de) |
| 15:42.29 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 15:47.34 | psychologe | mm0ss, hello |
| 15:48.06 | mm0ss | Anyone working on a drop box application for meego? |
| 15:49.40 | psychologe | now i used maemo ,.i don't know |
| 15:51.01 | mm0ss | Oooo |
| 15:51.09 | mm0ss | Brb |
| 15:51.39 | *** join/#maemo mm0ss (~moss@pool-71-175-72-227.phlapa.fios.verizon.net) |
| 15:53.13 | *** join/#maemo moss__ (~moss@de3x.mullvad.net) |
| 15:54.09 | *** join/#maemo jrocha (~JRocha@AAnnecy-651-1-281-233.w86-200.abo.wanadoo.fr) |
| 15:56.31 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 16:07.29 | *** join/#maemo valerius (~user@85.26.180.148) |
| 16:08.21 | *** mode/#maemo [-o DocScrutinizer05] by ChanServ |
| 16:16.02 | *** join/#maemo hardfalcon (~hardfalco@f048106026.adsl.alicedsl.de) |
| 16:23.48 | *** join/#maemo trumee (~parul@185.11.39.191) |
| 16:29.26 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 16:38.54 | *** join/#maemo rcg (~rcg@2a02:908:e280:28cc:76de:2bff:fe08:7809) |
| 16:49.20 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-214-185.triad.res.rr.com) |
| 16:50.26 | *** join/#maemo maybeHere (~cl@p5B164170.dip0.t-ipconnect.de) |
| 17:08.18 | *** join/#maemo mvp (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 17:09.11 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 17:18.57 | *** join/#maemo sq-one (~sq-one@p549ABAA8.dip0.t-ipconnect.de) |
| 17:27.58 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 17:34.31 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 18:01.42 | *** join/#maemo NIN101 (~NIN@p5DD28960.dip0.t-ipconnect.de) |
| 18:13.23 | *** join/#maemo kimitake_idle (~kimitake@adsl-108-254-247-86.dsl.pltn13.sbcglobal.net) |
| 18:13.37 | *** join/#maemo trumee (~parul@185.11.39.191) |
| 18:16.55 | *** join/#maemo HylianSavior (hylian@HYLIANDESKTOP.RES.CMU.EDU) |
| 18:19.40 | *** join/#maemo NIN101 (~NIN@p5DD28960.dip0.t-ipconnect.de) |
| 18:22.48 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 18:36.32 | *** join/#maemo trumee_ (~parul@185.11.39.191) |
| 18:39.29 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 18:40.18 | *** join/#maemo sq-one (~sq-one@p549ABAA8.dip0.t-ipconnect.de) |
| 18:41.54 | *** join/#maemo maybeHere (~cl@p5B164170.dip0.t-ipconnect.de) |
| 18:51.03 | *** join/#maemo robink (~quassel@unaffilated/robink) |
| 19:07.18 | *** join/#maemo maybeHere (~cl@p5B164170.dip0.t-ipconnect.de) |
| 19:07.53 | *** join/#maemo maybeHere (~cl@p5B164170.dip0.t-ipconnect.de) |
| 19:12.46 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 19:15.54 | *** join/#maemo piggz (~piggz@host-92-18-173-77.as13285.net) |
| 19:18.23 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 19:19.01 | *** join/#maemo shentey (~shentey@f052243104.adsl.alicedsl.de) |
| 19:29.54 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 19:30.58 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 19:31.12 | *** join/#maemo piggz (~piggz@host-92-18-173-77.as13285.net) |
| 19:42.01 | *** join/#maemo cybr1d (cybr1d@gateway/shell/freebnc/x-sbrxpvielckxdavr) |
| 20:03.35 | *** join/#maemo louisdk (~louis@static-5-103-130-65.seas-nve.net) |
| 20:06.29 | *** join/#maemo wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 20:07.52 | *** join/#maemo NIN101 (~NIN@p5DD28960.dip0.t-ipconnect.de) |
| 20:11.41 | *** part/#maemo Herbstbert (~Herbstber@drms-590ce7f3.pool.mediaWays.net) |
| 20:18.36 | *** join/#maemo maybeHere (~cl@p5B164170.dip0.t-ipconnect.de) |
| 20:22.40 | *** join/#maemo pdz- (~paul@c-71-202-114-76.hsd1.ca.comcast.net) |
| 20:22.57 | *** join/#maemo pcfe (~pcfe@37-5-4-129-dynip.superkabel.de) |
| 20:22.58 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 20:28.11 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 20:35.36 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 20:37.02 | *** join/#maemo Kabouik (~quassel@51.154.136.88.rev.sfr.net) |
| 20:38.15 | *** join/#maemo ssvb (~ssvb@212.16.98.80) |
| 20:42.11 | *** join/#maemo _rd (~rd@p57B4B091.dip0.t-ipconnect.de) |
| 20:43.08 | *** join/#maemo sq-one (~sq-one@p549ABAA8.dip0.t-ipconnect.de) |
| 21:41.37 | *** join/#maemo Wulfe (~ninja@74.61.222.224) |
| 21:41.38 | *** join/#maemo Wulfe (~ninja@unaffiliated/wulfe) |
| 21:53.29 | *** join/#maemo Natch (~Natch@c-cdcee155.25-4-64736c10.cust.bredbandsbolaget.se) |
| 21:55.53 | *** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa) |
| 22:14.11 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 22:23.54 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 22:28.18 | *** join/#maemo cybr1d (cybr1d@gateway/shell/freebnc/x-nsrwqnohqplnledb) |
| 22:29.59 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 22:37.55 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 22:53.41 | *** join/#maemo unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
| 23:24.28 | *** join/#maemo M4rtinK (~M4rtinK@ip-89-177-124-88.net.upcbroadband.cz) |
| 23:26.44 | *** join/#maemo Ex-Opesa (~Ex-Opesa@unaffiliated/ex-opesa) |
| 23:51.07 | *** join/#maemo drussell (~dave@38.126.120.10) |
| 23:52.17 | *** join/#maemo triggerhappy (~quassel@112.209.10.184) |