| 00:31.25 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 00:36.20 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 00:41.56 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 01:09.34 | *** join/#maemo kthomas_vh_ (~kthomas@c-107-3-244-159.hsd1.tn.comcast.net) |
| 01:10.49 | *** join/#maemo uen| (~uen@p5DCB1704.dip.t-dialin.net) |
| 01:13.29 | *** join/#maemo Dragnslcr (~scott@c-76-118-7-184.hsd1.ma.comcast.net) |
| 01:15.30 | *** join/#maemo kthomas_vh_ (~kthomas@c-107-3-244-159.hsd1.tn.comcast.net) |
| 01:17.15 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 01:37.16 | *** join/#maemo t_s_o (~tso@84.48.230.202) |
| 01:39.12 | *** join/#maemo mitsutaka (~mitsutaka@219.143.36.82) |
| 01:41.41 | *** join/#maemo ukhamitov (~ircchatte@85.26.234.90) |
| 01:53.59 | *** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com) |
| 02:07.55 | *** join/#maemo Sazpaimon__ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 02:08.59 | *** join/#maemo Dragnslcr (~scott@c-76-118-7-184.hsd1.ma.comcast.net) |
| 02:13.56 | *** join/#maemo Milhouse (~irc_milho@Maemo/community/contributor/Milhouse) |
| 02:39.12 | *** join/#maemo bergie (~bergie@91-65-189-143-dynip.superkabel.de) |
| 02:42.13 | *** join/#maemo pcfe (~pcfe@91-158-3-129.elisa-laajakaista.fi) |
| 02:42.13 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 02:54.02 | *** join/#maemo GeorgeH (~George@c-69-141-105-145.hsd1.nj.comcast.net) |
| 02:56.41 | *** join/#maemo robbiethe1st (~robbiethe@71-221-216-73.spkn.qwest.net) |
| 02:57.15 | *** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com) |
| 03:00.36 | *** join/#maemo dockane_ (~dockane@dsdf-4db51dad.pool.mediaWays.net) |
| 03:35.48 | *** join/#maemo em (~em@unaffiliated/emma) |
| 03:38.53 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 03:45.33 | *** join/#maemo ZogG_laptop (~ZogG_lapt@bzq-79-177-202-143.red.bezeqint.net) |
| 03:48.18 | *** join/#maemo CodenameStrike-N (~Codenames@175.139.171.24) |
| 04:08.30 | *** join/#maemo mavhc (~mavhc@cpc3-basf10-2-0-cust617.12-3.cable.virginmedia.com) |
| 04:20.22 | Sazpaimon__ | guys |
| 04:20.28 | Sazpaimon__ | tell me if I made the right decision |
| 04:20.33 | Sazpaimon__ | my girlfriend started playing minecraft |
| 04:20.53 | Sazpaimon__ | so im like, what will get you to *not* play this game |
| 04:20.56 | Sazpaimon__ | she says coin dozer |
| 04:21.09 | Sazpaimon__ | so I get out the N900, install nitdroid and coin dozer |
| 04:21.28 | Sazpaimon__ | i dont know which is worse |
| 04:27.14 | joga | Sazpaimon__ why not play minecraft? |
| 04:27.37 | joga | challenge her to build a computer there |
| 04:28.43 | Sazpaimon__ | because minecraft is stupid |
| 04:29.13 | joga | no it's not |
| 04:29.25 | joga | sounds like you haven't played it! :p |
| 04:29.40 | joga | why not play with your girlfriend in multiplayer? |
| 04:31.24 | *** join/#maemo Roomerlol (~Roomerlol@95-26-18-34.broadband.corbina.ru) |
| 04:36.01 | Sazpaimon__ | I have played it |
| 04:36.03 | Sazpaimon__ | its stupid |
| 04:39.09 | joga | Sazpaimon in comparison to what? |
| 04:40.06 | *** join/#maemo dimw1t (~atlas@71-13-79-30.static.aldl.mi.charter.com) |
| 04:40.35 | Sazpaimon | it doesnt compare |
| 04:40.40 | Sazpaimon | its in a league of its own |
| 04:40.42 | joga | yeah, it doesn't :) |
| 04:40.48 | Sazpaimon | a league i want no part of |
| 04:40.53 | joga | it's more like painting than playing some "game" |
| 04:41.12 | Sazpaimon | this is coming from someone that runs a minecraft server |
| 04:41.18 | Sazpaimon | i just dont like it |
| 04:41.31 | joga | what sort of server do you run? |
| 04:41.54 | Sazpaimon | just a vanilla server |
| 04:42.02 | joga | I didn't really bother much with it either before I found there was a technic pack and a multiplayer version too |
| 04:42.20 | joga | so it was great fun building machines with a couple of friends |
| 04:42.24 | joga | :) |
| 04:43.11 | joga | but anyway, it is more like a sandbox where you have to make you own fun, and some of it can be pretty intimidating for sure heh |
| 04:43.44 | joga | to me it's very impressive from a simulation perspective and social interaction |
| 04:44.04 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 04:45.52 | Sazpaimon | on a side note a microsim fits well on an N900 |
| 04:46.10 | Sazpaimon | once you align it correctly |
| 04:50.47 | joga | heh, I made a ghetto solar usb charger an hour ago, it's charging a tiny phone right now. anyone tried a solar panel with n900? |
| 04:52.56 | *** join/#maemo eijk_ (~eijk@e178214131.adsl.alicedsl.de) |
| 05:02.37 | robbiethe1st | joga: so long as your voltage is between 4.5 and 6V it'll attempt to charge |
| 05:02.51 | robbiethe1st | So long as the voltage never goes over 20V, you won't ruin anything. |
| 05:03.46 | joga | robbiethe1st yeah, these have a decent 7.5V or so and I have 3 of them in parallel (with a 5v voltage regulator), it's the first time I just actually test them to charge something |
| 05:04.35 | robbiethe1st | N900's TI charging chip is surprisingly tolerant; if the voltage droops too much however, it will slow down/stop charging... |
| 05:23.03 | joga | robbiethe1st ok |
| 05:23.30 | joga | I'll see how the little phone does first if I go to sleep and leave it there |
| 05:23.48 | joga | sun's shining here already |
| 05:26.48 | *** join/#maemo muelli (~muelli@46.59.209.138) |
| 05:26.51 | *** join/#maemo Openfree` (~Openfreer@116.228.88.131) |
| 05:36.22 | *** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com) |
| 05:49.29 | *** join/#maemo e-yes (~e-yes@94.45.180.138) |
| 06:02.28 | *** join/#maemo ArGGu^^ (~arggu@91-157-140-34.elisa-laajakaista.fi) |
| 06:10.34 | *** join/#maemo kerio92 (~kerio@unaffiliated/kerio) |
| 06:22.59 | *** join/#maemo hurbu (~hurbanza@81-174-24-98.dynamic.ngi.it) |
| 06:24.20 | *** join/#maemo Trizt (~user@2a03:4000:1::2e26:ed96:1) |
| 06:33.15 | *** join/#maemo valdyn (~valdyn@valdyn.org) |
| 06:35.36 | *** join/#maemo dhbiker (~dhbiker@APN-122-122-10-gprs.simobil.net) |
| 06:47.41 | *** join/#maemo Kilroo1 (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 06:57.55 | *** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 07:25.22 | *** join/#maemo hurbu_ (~hurbanza@81-174-50-191.dynamic.ngi.it) |
| 07:26.29 | *** join/#maemo zap_ (~zap@178.130.21.28) |
| 07:29.37 | *** join/#maemo sasquatch (~username@p4FF2D6BF.dip.t-dialin.net) |
| 07:34.37 | *** join/#maemo dhbiker (~dhbiker@APN-122-123-232-gprs.simobil.net) |
| 07:43.20 | *** join/#maemo mortenvp (~mortenvp@port463.ds1-abc.adsl.cybercity.dk) |
| 07:45.37 | *** join/#maemo jrocha (~JRocha@156.0.60.213.dynamic.mundo-r.com) |
| 07:45.45 | *** join/#maemo Jooles (~Jooles@02dbe00c.bb.sky.com) |
| 07:46.13 | *** part/#maemo Jooles (~Jooles@02dbe00c.bb.sky.com) |
| 07:54.20 | *** join/#maemo kerio92 (~kerio@unaffiliated/kerio) |
| 07:54.50 | *** join/#maemo kerio92 (~kerio@unaffiliated/kerio) |
| 07:55.20 | *** join/#maemo kerio92 (~kerio@unaffiliated/kerio) |
| 07:56.35 | *** join/#maemo kerio92 (~kerio@unaffiliated/kerio) |
| 07:56.42 | *** join/#maemo DocScrutinizer (~halley@openmoko/engineers/joerg) |
| 08:00.54 | *** join/#maemo liar (~liar@clnet-p09-185.ikbnet.co.at) |
| 08:01.43 | *** join/#maemo TNZ (~quassel@2a01:e35:2e0e:3290:540b:ae21:8021:db68) |
| 08:02.11 | *** join/#maemo MacDrunk (~marper@201.165.164.208) |
| 08:03.08 | *** part/#maemo MacDrunk (~marper@201.165.164.208) |
| 08:10.02 | *** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl) |
| 08:11.41 | *** join/#maemo NIN101 (~NIN@p5DD28841.dip0.t-ipconnect.de) |
| 08:21.18 | *** join/#maemo s1gk1ll (~sigkill@2.82.34.17) |
| 08:21.33 | *** join/#maemo k273 (~Zerosubs@182.5.124.145) |
| 08:38.26 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 08:47.55 | *** join/#maemo disco_stu (~wrt54gl@190.216.32.137) |
| 09:00.28 | *** join/#maemo lasher (~lasher@220-245-1-130.static.tpgi.com.au) |
| 09:01.06 | *** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz) |
| 09:05.55 | *** join/#maemo mitsutaka (~mitsutaka@219.143.36.82) |
| 09:05.55 | *** join/#maemo BCMM (~ben@unaffiliated/bcmm) |
| 09:18.27 | *** join/#maemo lool (~lool@pig2.dooz.org) |
| 09:19.54 | *** join/#maemo tank-man (1000@S010600121729c6a1.vc.shawcable.net) |
| 09:21.45 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 09:29.21 | *** join/#maemo ArGGu^^ (~arggu@91-157-140-34.elisa-laajakaista.fi) |
| 09:39.44 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 09:46.25 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 09:46.53 | *** join/#maemo piggz (~piggz@host-92-18-188-143.as13285.net) |
| 09:48.58 | *** join/#maemo SmilyOrg (Smily@BSN-176-190-61.dial-up.dsl.siol.net) |
| 09:51.19 | flux | when using gst-launch for streaming video out of n900, is there a way to focus the camera? |
| 09:52.18 | flux | I guess I could do it at least with a custom software that activates the gstreamer pipeline.. maybe even python, direct-on-device? |
| 10:00.24 | flux | at least if I'm able to acces the v4l2 device directly (can I get the fd handle from gstreamer? can I reopen the device? at least I could find the open fd from proc :P) |
| 10:00.34 | flux | ..I should be able to set the focus to 'auto' |
| 10:01.10 | flux | oh, it gives device-fd, so it should work alright. next question, is there an app that already does this?-) |
| 10:03.15 | *** join/#maemo freemangordon (freemangor@130-204-50-168.2074221835.ddns.cablebg.net) |
| 10:03.35 | freemangordon | hi |
| 10:04.21 | *** join/#maemo zap_ (~zap@213.59.86.89) |
| 10:09.24 | freemangordon | guys, recently i bought a nokia phone to my GF. for my surprise, the battery inside was the same (BL5J) as in n900, but 1430 mAh, instead of 1320, so we swap the batteries. The problem is, that lshal never shows more than about 1200 mAh charge, capacity is correctly reported (1415). Anything I can do to fully charge the battery? |
| 10:14.47 | *** join/#maemo user_ (~user@dslb-188-100-025-216.pools.arcor-ip.net) |
| 10:14.58 | user_ | hi there, got a question. |
| 10:15.25 | user_ | is it possible to continuous capture images with the n900? |
| 10:15.38 | user_ | maybe over the shell? |
| 10:16.28 | user_ | used to do the same with my canon eos |
| 10:21.05 | user_ | anyone? |
| 10:29.31 | *** join/#maemo jhb (~joerg@p579F68E6.dip.t-dialin.net) |
| 10:30.19 | ShadowJK | phone-control has a option to take pics but ime they dont come out well |
| 10:46.47 | DocScrutinizer | freemangordon: your question is incorrect |
| 10:47.00 | freemangordon | :) why? |
| 10:47.22 | freemangordon | DocScrutinizer ^^^ |
| 10:47.34 | DocScrutinizer | lshal never shows more than VS I can do to fully charge the battery |
| 10:47.46 | DocScrutinizer | figure :-D |
| 10:48.29 | freemangordon | well, ok. However, it seems bme really does not want to charge that over 80%. |
| 10:48.50 | DocScrutinizer | what makes you think so? |
| 10:49.03 | freemangordon | that is what lshal shows |
| 10:49.13 | ShadowJK | Charging is OK, the meter isn't |
| 10:49.36 | freemangordon | hmm, why is that? |
| 10:49.40 | DocScrutinizer | I thought he already noticed, after I critisized his Q, ShadowJK :-D |
| 10:50.09 | freemangordon | bme does not know what current for how long? really? |
| 10:50.29 | ShadowJK | it's somewhat hardcoded for 1200mAh-ish battery :P |
| 10:51.21 | ShadowJK | And it has some voltage curve matching stuff going on too, mixed with the current integration stuff |
| 10:51.57 | freemangordon | so, if i understand what you say, the battrey is fully charged, but i have 7 bars? And that is ok? |
| 10:51.59 | DocScrutinizer | get bq27k-detail to get an idea |
| 10:52.03 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 10:52.32 | freemangordon | DocScrutinizer, your i2c script would do the better job? |
| 10:52.34 | ShadowJK | If you get green light with bme charging, it's more than full |
| 10:52.39 | DocScrutinizer | or bq27200.sh |
| 10:53.00 | freemangordon | the one in wiki? |
| 10:53.37 | ShadowJK | (except if you insert charger when battery is close to full (80-90 percent or so), green light might come on right away, but it's still charging |
| 10:54.07 | ShadowJK | The charging, green light, and bme battery meter all operate independently.. |
| 10:54.22 | freemangordon | ok, thanks a lot. |
| 10:54.36 | ShadowJK | and bars - percentage mapping isn't linear :) |
| 10:55.37 | freemangordon | yeah, i know that, but lshal showing 80% and battery meter showing 7 bars 15 minutes after green led made me curious WTF is going on |
| 10:56.20 | DocScrutinizer | freemangordon: yes, the one on wiki (I guess) |
| 10:56.29 | freemangordon | ok, thanks |
| 10:57.03 | ShadowJK | Also it's designed to show "0" relatively early on, so that device runs long enough to find charger cable and more |
| 10:57.23 | freemangordon | yeah, know that too |
| 10:57.35 | ShadowJK | The hardware charge meter has nice accuracy, but it's 0 point is kinda low |
| 10:57.52 | ShadowJK | And default parameters in it are really wrong |
| 10:58.12 | freemangordon | yeah, it needs calibration |
| 10:58.22 | ShadowJK | but it self-learns and adjusts those, however under bme control the required conditions for self-learning are never met |
| 10:58.50 | freemangordon | DocScrutinizer, what has happened with your project (together with pali) for bme replacement? |
| 10:59.06 | *** join/#maemo ZogG (~zoggrules@bzq-79-177-202-143.red.bezeqint.net) |
| 10:59.15 | ShadowJK | bbl, food |
| 10:59.26 | freemangordon | bb |
| 10:59.27 | DocScrutinizer | I dunno about what pali does, I never had any such project actually |
| 10:59.48 | freemangordon | but you wrote some specs iirc |
| 10:59.54 | DocScrutinizer | sure |
| 11:00.02 | Pali | I had created driver |
| 11:00.10 | DocScrutinizer | which pali generously disregarded |
| 11:00.15 | freemangordon | :D |
| 11:00.31 | freemangordon | so, hof far are we from getting bme replaced? |
| 11:00.46 | Pali | ready for testing |
| 11:00.54 | freemangordon | wow, where? |
| 11:01.03 | Pali | I wrote info somewhere in TMO usb host mode thread |
| 11:01.23 | freemangordon | but that deserves its own thread aiui |
| 11:02.14 | DocScrutinizer | freemangordon: btw all I wrote was a 50% done API spec for a bq24150 driver |
| 11:02.28 | DocScrutinizer | nothing at all regarding bme replacement |
| 11:02.37 | Pali | DocScrutinizer, my driver has interface as you described in spec |
| 11:02.51 | DocScrutinizer | ohh? never realized |
| 11:02.57 | DocScrutinizer | :-D |
| 11:03.00 | Pali | I exported all settings via sysfs |
| 11:03.18 | Pali | all what was written in bq datasheet |
| 11:03.41 | freemangordon | so, now we just need a wrapper to i2c for bme? |
| 11:03.44 | Pali | (no idea if TI bq chip has some undocumented registers..) |
| 11:03.54 | DocScrutinizer | freemangordon: nope |
| 11:03.56 | Pali | no, we need to remove BME :D |
| 11:04.03 | freemangordon | ouch |
| 11:04.12 | DocScrutinizer | freemangordon: with pali's (my) sysfs API you don't use i2c anymore |
| 11:04.24 | freemangordon | yeah, but bme uses it afaik |
| 11:04.32 | DocScrutinizer | Pali: it has no undocumented registers |
| 11:04.44 | Pali | but kernel driver doing all what is doing BME... |
| 11:04.56 | freemangordon | and i am not sure we have all the knowlegde needed to integrate in the same way bme does |
| 11:04.57 | DocScrutinizer | though bme is writing to register #46 or sth |
| 11:05.01 | DocScrutinizer | X-P |
| 11:05.14 | freemangordon | do we? |
| 11:05.27 | Pali | so then my driver does not doing what BME :D |
| 11:05.38 | DocScrutinizer | forget that |
| 11:05.53 | *** join/#maemo maybeHere (~cl@p5B165F5C.dip.t-dialin.net) |
| 11:05.57 | DocScrutinizer | we neither need that nor do we want or like to do what bme does |
| 11:06.02 | Pali | freemangordon, you need to replace hald-addon-bme and libbmeipc library |
| 11:06.17 | Pali | for both exists open source implementations |
| 11:06.23 | freemangordon | hmm |
| 11:06.48 | Pali | you need only rewrite both programs to use sysfs interface from bq2415x and bq27x00 driver |
| 11:06.50 | freemangordon | here? http://gitorious.org/mer-toggles/hald-addon-bme |
| 11:06.54 | Pali | yes |
| 11:07.07 | Pali | it is simple addon for hal |
| 11:07.09 | Pali | nothing more |
| 11:07.12 | freemangordon | hmm, let me see |
| 11:07.17 | Pali | also check lshal -u on real n900 |
| 11:07.23 | Pali | that version is for n8x0 |
| 11:07.41 | freemangordon | didn't understand that |
| 11:07.47 | Pali | you need to export BME properties |
| 11:07.58 | Pali | you can see it with command: lshal |
| 11:08.05 | freemangordon | aah, ok |
| 11:08.06 | DocScrutinizer | bme is like controlling your washing machine by hand via switching between max heating (95°C) and cold to keep the water @ 60° for the laundry, then manually stepping thru drain water, rinse, tumble, whatnot |
| 11:08.45 | DocScrutinizer | our bq24150 is the washing machine that perfectly knows to do all that without you(/bme) forcing that manually on it |
| 11:09.07 | Pali | and libbmeipc is library which communicate with BME |
| 11:09.31 | Pali | so needs to rewrite to use again /sys/power/bq... instead some BME socket interface |
| 11:09.49 | freemangordon | well, why not do it then? |
| 11:10.08 | Pali | no time :D |
| 11:10.24 | freemangordon | aah, yeah :D |
| 11:11.15 | DocScrutinizer | freemangordon: basically it's still non-comparible to a stock system |
| 11:11.21 | Pali | freemangordon, here is that thread: http://talk.maemo.org/showpost.php?p=1156614&postcount=973 |
| 11:11.27 | DocScrutinizer | thanks to friggin bq27200 driver |
| 11:12.12 | DocScrutinizer | I.E. on a system set up to run that sys/bq interface youz can't use original bme anymore |
| 11:12.30 | Pali | you cannot use both BME and bq :D |
| 11:12.46 | DocScrutinizer | concurrently obviously not |
| 11:14.27 | DocScrutinizer | but tanks to the way sysfs and modules work, it isn't even an alternative at boot time (unless you make sure bq27200.ko isn't modprobed when you plan to boot to the bme version of system) |
| 11:15.48 | DocScrutinizer | almost same applies to different versions of hald-addon-bme and libbmeipc |
| 11:15.49 | freemangordon | And why should I want that? i.e. having HW charger, why should I want to use those spaghetti called bme? |
| 11:15.50 | Pali | DocScrutinizer, both modules (bq2415x_charger.ko and bq27x00_battery.ko) will be always blacklisted in kernel-power |
| 11:16.19 | DocScrutinizer | freemangordon: no idea :-D |
| 11:16.40 | freemangordon | why the should we care about so-called "bme" version? |
| 11:16.47 | Pali | I will look at LKML what problems have kernel devs for integrating bq2415x module into upstream |
| 11:16.57 | Pali | ...and try to fix that |
| 11:17.02 | freemangordon | Pali, it is stable in KP50? |
| 11:17.03 | DocScrutinizer | good plan |
| 11:17.18 | Pali | I tested it and worked fine with pre v50 |
| 11:17.23 | freemangordon | ok |
| 11:17.31 | Pali | binary .ko file on my page is for pre v50 |
| 11:18.21 | Pali | current version does not support autoselect changer current limit |
| 11:18.40 | DocScrutinizer | Pali: I got 3 weeks holiday now, *maybe* I could invest some time into this development |
| 11:19.07 | Pali | but in upstream kernel is isp1704 driver which provide inromations about connected charger type |
| 11:19.08 | freemangordon | and I have 4 days, lets do something about it |
| 11:20.00 | DocScrutinizer | Pali: this upstream isp1704 driver for _sure_ conflicts with our monolitic kernel USB driver |
| 11:20.12 | Pali | yes I know |
| 11:20.33 | Pali | but code for isp driver is copied from musb 2.6.28 |
| 11:21.00 | Pali | I will look if it is simple to use our isp code in musb for that too |
| 11:21.08 | *** join/#maemo ErwinJunge (~ErwinJung@s3eea6043.adsl.wanadoo.nl) |
| 11:21.13 | freemangordon | ok, I am going to port hald-addon-bme |
| 11:22.08 | DocScrutinizer | Pali: check hostmode kernel for a printk dmesg string like "some bastard tried to probe for charger" |
| 11:22.11 | DocScrutinizer | OWWTE |
| 11:22.23 | DocScrutinizer | s/WW/WT/ |
| 11:23.15 | *** join/#maemo kimitake (~kimitake@75.0.181.167) |
| 11:23.54 | DocScrutinizer | doing D+/- short probing in isp1707/4 breaks any actual data transmission over USB that may run concurrently |
| 11:24.44 | DocScrutinizer | that'S the root cause why we need to remove bme for h-e-n |
| 11:27.10 | DocScrutinizer | that and of course the boostmode we operate bq24150 that conflicts with bme chargemode. Anyway we enable vboost and that gets detected by bme via vbus sysnode. bme thinks vbus == charger/host attached, and queries sysnode for fastcharger detect which in turn causes kernel to switch isp1707 to D+- short detect which breaks our USB hostmode setup |
| 11:29.12 | ShadowJK | doesn't use bme |
| 11:29.53 | DocScrutinizer | so if your bme 'replacement' does the same (read fastcharger detection sysnode), it's as incompatible to h-e-n as bme_original |
| 11:32.12 | DocScrutinizer | since we use booston script to enable bq24150 boostmode via direct I2C, there's no way for kernel (yet) to know vbus is not applied by external charger/USB-host but rather endogenic, and thus kernel refusing to mess with 1707 to detect fastcharger when somebody reading that sysnode |
| 11:32.26 | Pali | it doing upstream isp kernel driver |
| 11:33.44 | Pali | my driver has 2 modes: one auto (prepaired mode for isp or something else which select charger current limit automatically) and manual mode when automode is disabled |
| 11:33.47 | DocScrutinizer | of course your/our bq24150.ko might know it's driving the chip into boostmode so "the kernel" now could know it's endogenic and thus tell musb kernel driver to reject D+- probing |
| 11:34.22 | Pali | so when you activate hostmode, driver changed to manual and then do not listen for any auto changes |
| 11:36.13 | DocScrutinizer | :nod: not wrapping my head around it completely, but on first touch it sounds about correct way |
| 11:40.11 | *** join/#maemo doc|home (~doc@gentoo/contributor/doc-007) |
| 11:42.32 | Pali | next will be to implement simple battery charging into u-boot |
| 11:47.26 | DocScrutinizer | well, that's extremely simple |
| 11:48.19 | DocScrutinizer | bare bones script like my PoC script will do |
| 11:48.33 | DocScrutinizer | max USB current = 500mA |
| 11:48.35 | *** join/#maemo CodenameStrike-N (~Codenames@203.82.90.97) |
| 11:50.19 | DocScrutinizer | freemangordon: not wiki, http://maemo.cloud-7.de/maemo5/usr/local/sbin/ |
| 11:50.45 | freemangordon | i found a post from estel with link to it |
| 11:51.05 | DocScrutinizer | Pali: (uboot) http://maemo.cloud-7.de/maemo5/patches_n_tools/charge21_500mA-USBlimit__UNTESTED.sh |
| 11:51.38 | DocScrutinizer | though that's for sure way too sophisticated and "large" |
| 11:52.02 | Pali | it is same as charge21.sh? |
| 11:53.19 | DocScrutinizer | no, it's "patched" for max 500mA USB |
| 11:53.29 | DocScrutinizer | of course you can patch http://talk.maemo.org/showthread.php?p=658278#post658278 same way |
| 11:57.33 | Pali | ok, 500mA limit is good for usb charger and also wallchanger |
| 11:58.15 | Pali | freemangordon, I updated u-boot deb packages & source code on gitorious |
| 11:58.41 | freemangordon | great |
| 11:58.47 | DocScrutinizer | <PROTECTED> |
| 11:58.49 | DocScrutinizer | <PROTECTED> |
| 11:58.50 | DocScrutinizer | <PROTECTED> |
| 11:59.01 | DocScrutinizer | i2cset -y 2 0x6b 0x01 0x48; |
| 11:59.10 | Pali | 3 problems: mkimage not worked, syntax error in debian/rules and bad size (only half) of RAM in u-boot rx51 port |
| 11:59.16 | Pali | fixed |
| 11:59.54 | Pali | DocScrutinizer, 800mA is for what type of changer? |
| 12:00.10 | freemangordon | along with cursor garbadge and eMMC -11 ? |
| 12:00.18 | freemangordon | *-110 |
| 12:00.28 | Pali | same version as yesterday |
| 12:00.31 | DocScrutinizer | 0x48 = 0b0100 1000 = [(8,4) = 01 = 500)] |
| 12:00.32 | freemangordon | ok |
| 12:00.44 | Pali | only that 3 small fixes |
| 12:01.09 | DocScrutinizer | Pali: 800 is for chager that can deliver max 800 ;-) |
| 12:01.46 | Pali | of course, but how BME detect this charger type? |
| 12:01.56 | DocScrutinizer | not at all |
| 12:02.36 | DocScrutinizer | unless USB ENUM would advertise such strange host that allegedly can deliver 800mA |
| 12:02.45 | DocScrutinizer | I think it's not possible |
| 12:02.54 | Pali | In isp upstream kernel code is only 3 options: none, usb charger (500mA) and wallchanger (no limit) |
| 12:03.06 | DocScrutinizer | :nod: |
| 12:03.16 | DocScrutinizer | about what we can detect |
| 12:03.36 | DocScrutinizer | where "none"=100mA |
| 12:04.00 | DocScrutinizer | = 0b00xx xxxx |
| 12:04.24 | DocScrutinizer | in register #01 |
| 12:04.30 | Pali | it is safe in u-boot enable permanent charging (e.g. when charger is not connected too) with limit 500mA? |
| 12:04.41 | DocScrutinizer | yes, mostly |
| 12:05.03 | *** join/#maemo spark666 (~spark666@92.86.186.16) |
| 12:05.03 | *** join/#maemo spark666 (~spark666@unaffiliated/spark666) |
| 12:05.08 | Pali | ok |
| 12:05.08 | DocScrutinizer | as safe as any random USB fan/lamp/rocketlauncher/whatever gadget |
| 12:05.16 | *** join/#maemo mase76 (~mase76@p5DD3A34D.dip.t-dialin.net) |
| 12:06.06 | DocScrutinizer | USB mugwarmer even worse - they use up to 1000+mA without any "safety check" |
| 12:06.27 | DocScrutinizer | that's how you fry one out of 5000 laptops |
| 12:06.47 | DocScrutinizer | not nowadays anymore, I guess |
| 12:07.57 | DocScrutinizer | per definition USB has to be short circuit resilient |
| 12:08.57 | DocScrutinizer | one *some* PCs windows actively detects obercurrent/short on USB and powers down the USB in case of error |
| 12:10.25 | DocScrutinizer | since that doesn't improve your life in any way, it's getting rarely done like that nowadays |
| 12:11.13 | DocScrutinizer | nowadays each PC USB host shall have an electronic fuse that triggers on a safe threshold @ >=500mA |
| 12:11.27 | DocScrutinizer | and OS should keep sticky fingers out of that |
| 12:12.05 | DocScrutinizer | most PC have a threshold of >=1000mA |
| 12:13.51 | DocScrutinizer | I.E. they use only one electronic fuse with 1000 or even 2000mA and feed the vbus rail to 2 or 3 or 4 USB ports in parallel |
| 12:15.12 | DocScrutinizer | so you could either use 4 compliant 500mA loads on 4 USB ports, or one spec-breaking mugwarmer 1500mA+ on one USB port while not using the other 3 ports |
| 12:16.08 | DocScrutinizer | or s/mugwarmer/UMTS-stick, 3.5" HDD, whatever/ |
| 12:16.12 | *** join/#maemo otep (~quassel@AP-203.167.31.157.sysads.com) |
| 12:16.48 | DocScrutinizer | Nokia been extremely careful not to break USB spects with N900 |
| 12:17.19 | DocScrutinizer | regarding the max allowed current under any phase of ENUM/detection |
| 12:17.45 | DocScrutinizer | I think it's overly prudent |
| 12:17.53 | *** join/#maemo inz (inz@inz.fi) |
| 12:19.59 | DocScrutinizer | but then, IANAL and maybe they have their very own history of paying refund for destroyed laptop USB ports, like they have with exploding batteries |
| 12:20.35 | DocScrutinizer | if any of the chinese USB-acme-gadget (mugwarmer) manufacturers was as prudent, they couldn'T sell a single unit |
| 12:24.01 | DocScrutinizer | My 3.5G USB dongle came with a Y-cable to split the vbus load on two USB ports of PC. They obviously had less scruple to violate specs (basically all 2G/3G dongles do) |
| 12:24.45 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 12:24.55 | *** join/#maemo xev (~xev@unaffiliated/xev) |
| 12:24.59 | DocScrutinizer | either that or they violate GSM/UMTS specs |
| 12:28.37 | *** join/#maemo jeverling (~quassel@jeverling.de) |
| 12:32.02 | *** join/#maemo NIN101 (~NIN@p5DD28841.dip0.t-ipconnect.de) |
| 12:38.13 | *** join/#maemo udovdh (~udovdh@pindarots.xs4all.nl) |
| 12:38.21 | *** join/#maemo t_s_o (~tso@84.48.230.202) |
| 12:39.25 | *** join/#maemo hurbu__ (~hurbanza@81-174-24-201.dynamic.ngi.it) |
| 12:41.35 | *** join/#maemo hurbu (~hurbanza@81-174-50-244.dynamic.ngi.it) |
| 12:46.05 | *** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ffdec300-4.dhcp.inet.fi) |
| 12:49.00 | *** join/#maemo spark666 (~spark666@unaffiliated/spark666) |
| 12:49.35 | *** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141) |
| 12:50.33 | *** join/#maemo DocScrutinizer (~halley@openmoko/engineers/joerg) |
| 13:00.00 | *** join/#maemo hurbu (~hurbanza@81-174-24-131.dynamic.ngi.it) |
| 13:01.04 | *** join/#maemo mortenvp (~mortenvp@port463.ds1-abc.adsl.cybercity.dk) |
| 13:10.35 | Pali | freemangordon, I uploaded my last version of bq2415x_charger driver and .ko binary for kp v50: http://atrey.karlin.mff.cuni.cz/~pali/bq2415x/ |
| 13:11.11 | *** join/#maemo trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623) |
| 13:11.56 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 13:12.14 | *** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net) |
| 13:18.11 | freemangordon | Pali, thanks |
| 13:19.07 | *** join/#maemo neal (~user@c-24-91-125-189.hsd1.ma.comcast.net) |
| 13:22.48 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 13:23.56 | Pali | freemangordon, is booting from sd card via u-boot working? |
| 13:30.02 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 13:30.37 | RST38h | Meanwhile: Portable Battery-Powered X-ray Machine Guarantees You'll Always Find the Best Kinder Surprise Toys |
| 13:32.35 | *** join/#maemo lxp1 (~lxp@62-47-168-101.adsl.highway.telekom.at) |
| 13:39.18 | Pali | ping NIN101 |
| 13:40.50 | DocScrutinizer | RST38h: awesome |
| 13:41.19 | *** join/#maemo dennis_ (~dennis@j138215.upc-j.chello.nl) |
| 13:41.45 | DocScrutinizer | RST38h: reminds me on the x-ray machines they had in shoe shops here, back in the 50s and into the 60s, though in the 60s they already were forbidden |
| 13:42.06 | *** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 13:42.43 | *** join/#maemo hurbu (~hurbanza@81-174-24-185.dynamic.ngi.it) |
| 13:43.36 | *** join/#maemo iDont (~iDont@j138215.upc-j.chello.nl) |
| 13:44.44 | DocScrutinizer | I found one of those when I was dunno maybe 4 years old, and of course immediately tested how it works - my mum got *really* upset |
| 13:46.59 | *** join/#maemo NIN101 (~NIN@p5DD289C1.dip0.t-ipconnect.de) |
| 13:47.31 | ErwinJunge | x-ray machines in shoeshops? wtf? |
| 13:47.59 | Termana | DocScrutinizer, that explains everything |
| 13:48.04 | Termana | lol j/k :p |
| 13:48.28 | DocScrutinizer | pedoskop : http://www.physikmuseum.at/index.php?aid=18 // http://www.spiegel.de/netzwelt/tech/0,1518,268071,00.html |
| 13:48.53 | DocScrutinizer | aims a MTHEL at Termana general direction |
| 13:50.02 | ErwinJunge | DocScrutinizer, but what's the point? |
| 13:52.25 | ErwinJunge | I have a problem adding a target to scratchbox (to use gcc 4.6.2 from freemangordon). When trying to use fakeroot, it complains about a missing library, running apt-get upgrade gives me dependency errors, and running apt-get -f install gives me this on libc6: package architecture (i386) does not match system () |
| 13:52.37 | *** join/#maemo johnsu01 (user@gateway/shell/gnu/x-lolmkfvverskgaev) |
| 13:52.46 | ErwinJunge | Obviously, the architecture is wrong (should be armel). Anyone know how to fix that? |
| 13:55.18 | ErwinJunge | sb-menu info on target: http://pastebin.com/sUESLT0C |
| 13:55.32 | ErwinJunge | That shows arm as architecture :( |
| 13:59.41 | ErwinJunge | Found the issue, SBOX_DPKG_INST_ARCH was not set. |
| 14:02.05 | DocScrutinizer | ErwinJunge: point of what? |
| 14:04.22 | *** join/#maemo eMHa (~mh@HSI-KBW-109-192-178-160.hsi6.kabel-badenwuerttemberg.de) |
| 14:06.41 | ErwinJunge | point of having an x-ray device in a shoestore |
| 14:12.14 | *** join/#maemo johnsu01 (user@fsf/staff/johnsu01) |
| 14:14.11 | *** join/#maemo SD69 (ae64f0d8@gateway/web/freenode/ip.174.100.240.216) |
| 14:14.21 | DocScrutinizer | well,isn't that obvious? x-ray baby feet with shoes on |
| 14:15.14 | DocScrutinizer | see if they fit |
| 14:15.26 | RST38h | fit where? |
| 14:15.41 | DocScrutinizer | *sigh* |
| 14:15.48 | RST38h | yep |
| 14:16.03 | DocScrutinizer | yep wut? |
| 14:16.23 | DocScrutinizer | go xray your kinder choclate eggs |
| 14:16.26 | RST38h | the feet already fit in those shoes, somehow |
| 14:16.46 | RST38h | Doc <-- obviously being playful |
| 14:16.46 | ErwinJunge | Interesting definition of obvious there ;) I guess the harmfullness of x-rays wasn't know back then? |
| 14:17.26 | DocScrutinizer | ErwinJunge: I guess you noticed the URLs I posted above? |
| 14:18.28 | RST38h | Doc: Lumias have been jailbroken. Sadly, not the 800s with NOKIA bootloader though |
| 14:18.29 | ErwinJunge | Yeah, but german isn't in my library of languages :) |
| 14:18.53 | ErwinJunge | Or in this case Austrian I guess (does that matter?) |
| 14:21.48 | DocScrutinizer | ErwinJunge: especially for you: http://en.wikipedia.org/wiki/Shoe-fitting_fluoroscope |
| 14:25.05 | ErwinJunge | Pedoscopes --> seriously? Sounds like something law enforcement would use to find sexual predators :) |
| 14:26.00 | *** join/#maemo hurbu (~hurbanza@81-174-24-19.dynamic.ngi.it) |
| 14:26.31 | DocScrutinizer | hands ErwinJunge a glass of radon water |
| 14:26.38 | ErwinJunge | Never knew these things existed. Thanks for the laughs :) |
| 14:28.14 | *** join/#maemo neal (~user@c-24-91-125-189.hsd1.ma.comcast.net) |
| 14:29.45 | ErwinJunge | Got to go, byebye all |
| 14:29.51 | DocScrutinizer | o/ |
| 14:30.00 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 14:31.39 | *** join/#maemo hardaker (~hardaker@mail.hardakers.net) |
| 14:37.05 | joga | damn...this funny small taiwanese phone I tested the solar thingy with is pretty remarkable in terms of power consumption...I charged it in direct sunlight for roughly two hours until it got a bit cloudy, and turning it on it showed 1 bar of battery...now it has a maintained a call for 36 minutes ._o |
| 14:40.39 | *** join/#maemo Zahra (~Zahra@unaffiliated/belendax) |
| 14:41.11 | joga | this one :) http://mobile.softpedia.com/phones/i-mobile/i-mobile-310.shtml |
| 14:41.49 | Pali | DocScrutinizer, can I vote for one extras-testing package version too times? |
| 14:42.10 | Pali | *two or more times |
| 14:42.50 | DocScrutinizer | hm? |
| 14:42.54 | Pali | or I found bug in maemo.org packages interface :D |
| 14:42.57 | DocScrutinizer | nope |
| 14:43.03 | Pali | see http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/kernel-power/2.6.28-10power50/ |
| 14:43.06 | Pali | I CAN |
| 14:43.09 | DocScrutinizer | o.O |
| 14:43.24 | DocScrutinizer | you're special :-P |
| 14:43.46 | DocScrutinizer | I aways thought only mohammad was special |
| 14:44.07 | DocScrutinizer | til it turned out he's my father |
| 14:44.13 | DocScrutinizer | ~mohammadag |
| 14:44.13 | infobot | methinks mohammadag is your father, or **special** |
| 14:44.29 | Pali | :) |
| 14:45.17 | DocScrutinizer | for the geeks: http://www.fingers-welt.de/gallerie/eigen/elektro/roentgen/roentgen.htm |
| 14:51.53 | joga | what's the typical power consumption of a very low-end phone such as the i-mobile 310 I pasted above, or something similar during a call? |
| 14:52.43 | joga | (assuming decent environment etc) |
| 14:54.09 | joga | I haven't really benchmarked actual call times myself I think |
| 14:57.23 | joga | I guess that's sort of a dumb question though...this device just seems to require a lot less than advertised, but I dunno |
| 14:59.35 | *** join/#maemo BCMM (~ben@unaffiliated/bcmm) |
| 15:00.14 | DocScrutinizer | joga: always something between 50mW and 1W, depending on TX Powerlevel the BTS requests for the phone's transmitter |
| 15:00.31 | *** join/#maemo kama (~kama@unaffiliated/kama) |
| 15:01.09 | joga | DocScrutinizer I'm just very impressed it's been maintaining the call for an hour now, I was expecting it to perform maybe 10 minutes with the ghetto setup I had and would have been content with that too :) |
| 15:01.35 | DocScrutinizer | that's the reason why you never can get the call times the manufacturer claims: you never get the lowest TX PWRLVL in eal life |
| 15:02.15 | joga | but in this case I'd expect to get more than they claim, I should try it sometime.. |
| 15:02.59 | DocScrutinizer | then an even more funny and more commonly ignored detail is: while you're just "listening" your phone has no useful data to transmit, so will stop transmitting all together for 95%..99% of the time |
| 15:03.29 | *** join/#maemo valdyn (~valdyn@valdyn.org) |
| 15:03.29 | joga | DocScrutinizer that's why I've been playing youtube videos and holding the other phone near my keyboard...both are in the same room now |
| 15:04.08 | joga | to sort of emulate an awkward conversation maybe :) |
| 15:04.26 | DocScrutinizer | good approach |
| 15:06.22 | joga | but this is pretty nice since I'll be going to some festival abroad for a few days next week and we'll be camping out, so at least I'm pretty confident I can use a phone if there's at least some sun :) |
| 15:07.51 | Pali | freemangordon, see http://lists.denx.de/pipermail/u-boot/2012-April/123333.html |
| 15:10.00 | joga | ok...now it finally hung up, lasted for 1 hour 7 minutes |
| 15:10.27 | joga | the other phone was probably transmitting more though, but that's pretty good anyway |
| 15:10.47 | *** join/#maemo jlebrech (~jlebrech@178.40.113.87.dyn.plus.net) |
| 15:12.57 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 15:15.14 | DocScrutinizer | btw my figure above been incorrect - poorly designed phones may burn up to 4..5W in bursts |
| 15:15.20 | *** join/#maemo spark666 (~spark666@92.86.186.16) |
| 15:15.21 | *** join/#maemo spark666 (~spark666@unaffiliated/spark666) |
| 15:15.33 | DocScrutinizer | 2W max TX power, *<50% efficiency |
| 15:31.19 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 15:31.36 | joga | DocScrutinizer since you probably know an answer (I'm less than an amateur with electronics)... right now I just have 3 panels in parallel and a voltage regulator before the usb port, but would it be possible to use a plain nokia battery (since I probably have a couple lying around) for the contraption instead of directly feeding it to the phone's battery? I'm not sure if they're the right kind of battery to use for such |
| 15:32.32 | joga | I was also thinking of a simple 6xaa case but can't find any junk with a big enough battery holder and should I make one myself it would probably suck anyway :) |
| 15:32.46 | DocScrutinizer | err, what? charge USB device from LiIon? doesn't work |
| 15:32.56 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 15:33.05 | joga | ok, that's what I basically wanted to hear |
| 15:33.08 | joga | :) |
| 15:33.15 | joga | I have some nimh but they're too tiny |
| 15:33.33 | DocScrutinizer | you need sth like 4V minimum to make it properly charge |
| 15:33.47 | joga | can you put those in series, if I have two |
| 15:34.01 | DocScrutinizer | LiIon has a voltage of nominal 3.7V which is too low |
| 15:34.27 | DocScrutinizer | USB doesn't "survivie" voltage >6V |
| 15:34.44 | DocScrutinizer | so 2 in series also is no option |
| 15:34.47 | joga | but my panels give about 7V currently |
| 15:34.58 | joga | (and it's 5.00V after the regulator) |
| 15:35.22 | DocScrutinizer | well a regulator can cope with whatever it's designed for |
| 15:35.39 | joga | I mean basically to charge the batteries first with solar and then feed that via regulator to phone or whatever |
| 15:35.43 | DocScrutinizer | for sure a 5V regulator can take 8V input |
| 15:36.11 | joga | it's just that the only decent battery I have around are some old nokia batteries I think |
| 15:36.18 | DocScrutinizer | you mustn't charge LiIon brute force! |
| 15:36.36 | joga | ok, I'll scratch the idea of using those for this :) |
| 15:36.56 | DocScrutinizer | you can do this with NiMH |
| 15:37.14 | DocScrutinizer | NOT with LiIon |
| 15:37.15 | joga | wish I had those as abundantly |
| 15:37.29 | joga | I was supposed to get a couple for this specific purpose but I've forgot |
| 15:38.14 | DocScrutinizer | 4 AA cells in series are *somewhat* safe to use for USB powering |
| 15:39.15 | DocScrutinizer | voltage range should be 4.4V...6.4V, something USB *usually* can cope with |
| 15:39.51 | *** join/#maemo danau (~danau@unaffiliated/eighteleven) |
| 15:39.53 | joga | how low can the voltage be that an n900 would charge? |
| 15:39.57 | DocScrutinizer | don't blame me when your USB emits blue magic smoke though |
| 15:40.19 | DocScrutinizer | as mentioned above, it needs ~4V |
| 15:40.34 | joga | ah, ok |
| 15:40.39 | DocScrutinizer | beter 4.5V |
| 15:41.12 | DocScrutinizer | but for all my experience it survives 7V easily |
| 15:41.33 | DocScrutinizer | so with 4 primary cells you're quite likely just fine |
| 15:42.31 | joga | at some point I should try and do this properly, ie. weave the panels into a backpack or whatever and put some adapters, battery and make it less embarrassing |
| 15:42.39 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 15:43.07 | DocScrutinizer | as 4* 1.5V(nominal) = 6V; 4* 1.6V(max)=6,4V; 4* 1.2V(real voltage)=4.8V |
| 15:43.28 | joga | DocScrutinizer thanks for all the info |
| 15:43.33 | DocScrutinizer | YW |
| 15:44.13 | joga | I'm pretty new to the electronics stuff but junk projects like these are fun to try, I also learn more albeit slowly :) |
| 15:46.05 | DocScrutinizer | I just probed a fresh alkaline cell: 1.67V |
| 15:46.52 | *** join/#maemo hurbu (~hurbanza@81-174-24-9.dynamic.ngi.it) |
| 15:49.04 | *** join/#maemo eMHa (~mh@HSI-KBW-109-192-178-160.hsi6.kabel-badenwuerttemberg.de) |
| 15:53.40 | *** part/#maemo danau (~danau@unaffiliated/eighteleven) |
| 15:55.39 | *** join/#maemo scoobertron (~tom@93.186.150.31) |
| 15:57.46 | *** join/#maemo kerio (~kerio@unaffiliated/kerio) |
| 16:00.05 | *** part/#maemo scoobertron (~tom@93.186.150.31) |
| 16:00.25 | Pali | freemangordon, that patch really fixing damaged framebuffer output |
| 16:00.47 | Pali | I will rebase patches, create new build and sent patch series to u-boot mailinglist |
| 16:29.16 | *** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com) |
| 16:33.52 | *** join/#maemo dhbiker (~dhbiker@APN-122-123-232-gprs.simobil.net) |
| 16:34.01 | *** join/#maemo valdyn (~valdyn@valdyn.org) |
| 16:38.55 | *** join/#maemo PeterWolf (~peter@118-160-195-33.dynamic.hinet.net) |
| 16:44.59 | *** join/#maemo Vanadis (~Vanadis@178-83-10-90.dynamic.hispeed.ch) |
| 16:48.37 | *** join/#maemo eMHa (~mh@HSI-KBW-078-042-037-221.hsi3.kabel-badenwuerttemberg.de) |
| 16:50.00 | *** join/#maemo GeorgeH (~George@c-69-141-105-145.hsd1.nj.comcast.net) |
| 16:50.01 | *** join/#maemo Jooles (~Jooles@02dbe00c.bb.sky.com) |
| 16:54.35 | *** join/#maemo Vanadis__ (~Vanadis@178-83-10-90.dynamic.hispeed.ch) |
| 16:56.33 | spark666 | its there a way to rename my n900 user whitout any risc? |
| 16:57.57 | *** join/#maemo s1gk1ll (~sigkill@bl15-195-27.dsl.telepac.pt) |
| 17:11.48 | NIN101 | my intuition says: no. |
| 17:12.23 | SpeedEvil | My intuition sings the LumberJack song. |
| 17:15.15 | freemangordon | DocScrutinizer, Pali, we have hald-addon-bme i386 compiled in SB and my IDA has hexrays :P |
| 17:15.32 | freemangordon | I am almost ready with REing |
| 17:15.51 | Pali | freemangordon, disassembler is not needed |
| 17:16.08 | Pali | you do not need to know how hald-addon-bme is communicating with BME |
| 17:16.21 | Pali | you only need to know hal interface for bme |
| 17:16.22 | freemangordon | it is, the one you in gitorious does not initialize in the same way |
| 17:16.24 | freemangordon | I know |
| 17:16.34 | Pali | and hal interface is visible via lshal :-) |
| 17:16.40 | freemangordon | but it handles dbus calls too |
| 17:16.52 | freemangordon | com.nokia.bme.request |
| 17:17.05 | freemangordon | status_info_req and timeleft_info_req |
| 17:17.07 | Pali | better look at libbmeipc |
| 17:17.35 | Pali | more closed apps are linked against libbmeipc |
| 17:17.47 | freemangordon | well, let mi finish that one :P |
| 17:17.51 | freemangordon | *me |
| 17:17.57 | Pali | ok :-) |
| 17:18.06 | freemangordon | anyway |
| 17:18.11 | freemangordon | is afk |
| 17:18.15 | *** join/#maemo sq-one (~sq-one@p54A1FDF7.dip.t-dialin.net) |
| 17:18.15 | *** join/#maemo em (~em@unaffiliated/emma) |
| 17:19.04 | RST38h | moos |
| 17:43.30 | *** join/#maemo zap_ (~zap@178.130.21.28) |
| 17:45.54 | Pali | freemangordon, I published new build of u-boot with that cfb flush patch |
| 17:46.26 | Pali | also now I send patch series (without bootmenu) to u-boot mailinglist |
| 17:46.57 | Pali | my bootmenu was rejected, becuase it must be rewrite to new menu code (common/menu.c) |
| 17:55.53 | *** join/#maemo em (~em@unaffiliated/emma) |
| 18:02.37 | *** join/#maemo neal (~user@c-24-91-125-189.hsd1.ma.comcast.net) |
| 18:09.04 | *** join/#maemo pcfe (~pcfe@91-158-7-105.elisa-laajakaista.fi) |
| 18:09.04 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 18:09.25 | *** join/#maemo pranka (~pranka@37.17.203.189) |
| 18:21.17 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 18:26.35 | *** join/#maemo em (~em@unaffiliated/emma) |
| 18:29.31 | *** part/#maemo Jooles (~Jooles@02dbe00c.bb.sky.com) |
| 18:30.30 | *** join/#maemo NIN101 (~NIN@p5DD289C1.dip0.t-ipconnect.de) |
| 18:30.58 | *** join/#maemo eMHa (~mh@HSI-KBW-078-042-037-221.hsi3.kabel-badenwuerttemberg.de) |
| 18:31.38 | *** join/#maemo em (~em@unaffiliated/emma) |
| 18:37.34 | *** join/#maemo hurbu (~hurbanza@81-174-24-122.dynamic.ngi.it) |
| 18:42.02 | zap | Hey, anybody updated advanced-power-monitor today? It doesn't work anymore for me. |
| 18:42.47 | zap | It kind of runs, but the status bard power applet shows a gray bar instead of charge level |
| 18:47.29 | *** join/#maemo em (~em@unaffiliated/emma) |
| 18:51.19 | zap | When running from command line it prints "[F] BQ27200 |
| 18:51.20 | zap | [F] BQ27200 Alternative". [F] means failed? |
| 18:57.25 | *** join/#maemo em (~em@unaffiliated/emma) |
| 18:57.49 | zap | "lshal | grep bq27200" gives nothing... what could be the cause? |
| 19:07.18 | *** join/#maemo sq-one (~sq-one@p54A1FDF7.dip.t-dialin.net) |
| 19:07.54 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 19:13.16 | *** join/#maemo prometoys (~prometoys@blfd-5d8211fa.pool.mediaWays.net) |
| 19:13.18 | *** join/#maemo realitygaps (~realityga@static.146.244.9.176.clients.your-server.de) |
| 19:13.18 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 19:14.08 | DocScrutinizer | LOL |
| 19:15.45 | DocScrutinizer | I CBA to check ftw this "monitor" does, but this msg sounds a lot like it's using the broken-badly bq27200.ko kernel module which got deprecated and hopefully completely removed from PowerKernel |
| 19:16.57 | zap | yep, it looks like it should use Nokia's BME |
| 19:17.13 | zap | but it also says "[L] Nokia's BME ... [U] Nokia's BME" |
| 19:17.22 | zap | as if it would load, then unload |
| 19:18.43 | *** join/#maemo em (~em@unaffiliated/emma) |
| 19:18.52 | DocScrutinizer | sure |
| 19:19.51 | zap | so which one is supposed to work? BME or bq27200? And yes, I have the power kernel |
| 19:20.02 | zap | but power manager worked until today |
| 19:20.54 | zap | hurray, just removed advanced-power-manager and all works now fine |
| 19:21.08 | zap | seems I have installed this thing some time just 4 lulz... |
| 19:21.32 | DocScrutinizer | look, somebody wrote a poor implementation for a bq27200.ko driver to expose the registers to /sys/. It did break bme as it exclusively opens and locks the chip on I2C, Then some f* fool decided to remove locking from I2C driver, exposing *whole* device to massive peril of hw breakage by random collisions on any I2C bus - but it somewhat made bq27200.ko cooperate with bme, as both didn't even try to avoid collisions |
| 19:22.06 | DocScrutinizer | effectively this fol pulled the pin of the hand grenade |
| 19:22.10 | DocScrutinizer | fool* |
| 19:22.14 | zap | :) and a third fool wrote advanced-power-manager using all this shit, got it :-D |
| 19:22.28 | *** join/#maemo em (~em@unaffiliated/emma) |
| 19:22.39 | DocScrutinizer | when I noticed this MESS, I convinced PK maintainer to immediately remove all that crap from PK |
| 19:23.12 | zap | I wonder how advanced-power-monitor worked until this morning |
| 19:23.30 | zap | are there alternative ways to know battery capacity? |
| 19:23.40 | *** join/#maemo valdyn (~valdyn@valdyn.org) |
| 19:23.45 | DocScrutinizer | probably it worked sitting on a ticking bomb, and this morning you updated kernel |
| 19:24.18 | zap | I updated it a while ago... but possible it was the first time I rebooted :) |
| 19:24.43 | zap | ok, the mystery is gone, all seems clear now |
| 19:24.46 | DocScrutinizer | http://maemo.cloud-7.de/maemo5/usr/local/sbin/ |
| 19:25.35 | *** join/#maemo Itschue (~Itschue@p54B4B7EF.dip.t-dialin.net) |
| 19:26.05 | DocScrutinizer | the bullshit "works" without the anti-locking patch as long as bme gets started first, then modprobe the crappy bq27200.ko |
| 19:26.06 | Itschue | hello someone here who use ovi maps on n900 ? |
| 19:26.47 | DocScrutinizer | with antilocking patch it ""works"" no matter what - until your device emits blue magic smoke |
| 19:27.28 | DocScrutinizer | Itschue: I used to, not using it since dunno, 6 months? |
| 19:28.57 | Itschue | i get ovi maps worked but there are some things that not worked ovi maps calculated the route the red points show the akzuial point but when i came of the route it doesnt recalculate the route |
| 19:30.57 | Itschue | dow you know of recalculating the route when you came(come) off it worked ? |
| 19:31.57 | DocScrutinizer | hmm, I think it never did |
| 19:32.15 | Itschue | its nice to see you docsrutinizer the last time you helped me was great if you can remember |
| 19:32.42 | DocScrutinizer | since OVI maps is using off-board routing, it won't as easily recalculate route when you're off |
| 19:33.01 | DocScrutinizer | I remember your nick, but that's it - sorry |
| 19:33.35 | Itschue | no sorry its ok its a very long time ago |
| 19:34.07 | Itschue | did i understand it right that ovi maps cant recalculate the route when i came off it? |
| 19:34.25 | DocScrutinizer | it can, if you got a data connection |
| 19:34.47 | DocScrutinizer | since it's causing traffic, I guess it won't do it without getting advised to do so |
| 19:35.17 | DocScrutinizer | I'm using marble, with monav on-board routing |
| 19:35.41 | DocScrutinizer | monav ?= Maemo Onboard NAViagtion |
| 19:36.13 | DocScrutinizer | Itschue: what'S been the topic last time? :-) |
| 19:38.09 | Itschue | i hab auto connect enabled and autodisconnect installed to cancel connection i think or im sure that ovi maps only says and show the first route direction |
| 19:38.58 | Itschue | topic last i get in big trouble with my device because it wont bott and there was no way to reflash and i must get it repairstore |
| 19:40.40 | Itschue | an i think ovi maps use very mouch power because 3 hours rpouting and battery was empty there where ca 5 internetconnectino of view minutes |
| 19:41.32 | *** join/#maemo cityLights (~cityLight@bzq-82-81-6-142.red.bezeqint.net) |
| 19:45.42 | Itschue | much to do docscrutinizer? |
| 19:47.34 | DocScrutinizer | well, not really - holiday :-D |
| 19:48.05 | DocScrutinizer | GPS eating quite a lot of power, as does screen backlight. 3h is ~ normal |
| 19:50.28 | Itschue | ok i think recalculating only worcs with permanent internet conn. that ther can be auto connect doesnt help because i activate it and ovi maps doesnt recalculate |
| 19:50.40 | *** join/#maemo ekze-nyan (~nyan@bakaekze.ru) |
| 19:51.19 | Itschue | marble and monav hmm wich version and which map or better do you know a good howto |
| 19:51.37 | Itschue | and you remember my big trobule? |
| 19:52.47 | DocScrutinizer | umm, install marble, install monav, setup stuff in marble's menus |
| 19:53.17 | DocScrutinizer | no, I'm sure OVI maps doesn't recalculate route as it would cause *lots* of traffic |
| 19:54.04 | DocScrutinizer | and OVI maps doesn't even find roads without internet support |
| 19:54.42 | DocScrutinizer | which is a bit strange, as it seems it knows about road names of arbitrary points on map |
| 19:55.14 | Itschue | and lots of traffic use lots of battery too hmm ios the laterst version of monav and marble ok? need marble omvoice server or espeak for voice commands? |
| 19:55.23 | DocScrutinizer | anyway, N900 OVI maps never was that brilliant so I don't miss it |
| 19:55.46 | Itschue | and which map for marble from where? |
| 19:55.47 | DocScrutinizer | I dunno |
| 19:56.05 | DocScrutinizer | afaik it's using OSM by default |
| 19:56.33 | NIN101 | yep |
| 19:57.07 | DocScrutinizer | http://maemo.org/packages/search/?org_maemo_packages_search[1][property]=name&org_maemo_packages_search[1][constraint]=LIKE&org_maemo_packages_search[1][value]=marble&org_maemo_packages_search[2][property]=title&org_maemo_packages_search[2][constraint]=LIKE&org_maemo_packages_search[2][value]=same |
| 19:58.34 | DocScrutinizer | >>Marble-data |
| 19:58.35 | DocScrutinizer | Data needed by marble at runtime |
| 19:58.37 | DocScrutinizer | <PROTECTED> |
| 19:58.56 | Itschue | what is taht for a link docsrcutinizer |
| 19:59.13 | DocScrutinizer | http://maemo.org/packages/view/marble-maps/ |
| 19:59.31 | DocScrutinizer | >>Additional maps for marble (earth and moon) |
| 19:59.33 | DocScrutinizer | <PROTECTED> |
| 19:59.34 | DocScrutinizer | <PROTECTED> |
| 20:00.27 | Itschue | *g* next time i drive at the moon *g* |
| 20:00.47 | DocScrutinizer | http://marble.garage.maemo.org/ |
| 20:04.07 | Itschue | which is a bit strange, as it seems it knows about road names of arbitrary points on map i dont understand this please germman? |
| 20:04.33 | Itschue | you said i dunno ???? i thit i dont know? |
| 20:05.21 | DocScrutinizer | yes |
| 20:05.40 | DocScrutinizer | http://talk.maemo.org/showthread.php?t=67316 |
| 20:06.28 | *** join/#maemo odin_ (~Odin@93-97-168-38.zone5.bethere.co.uk) |
| 20:06.37 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 20:06.51 | Itschue | that link is the ovi maps thread right? |
| 20:14.37 | Itschue | test |
| 20:17.49 | DocScrutinizer | >>It looks excellent. I'll definitely give it a try. Now we know where Nokia can stick their half-baked Ovi Maps<< X-P |
| 20:20.44 | Itschue | im use the how to in the link you send my n900 is next to mee and i will now install monav and marble and probably (i hope this is the right word) marble virtual globe |
| 20:22.24 | *** join/#maemo lxp (~lxp@62-47-168-101.adsl.highway.telekom.at) |
| 20:23.17 | Itschue | docsrutinizer did i need monav client? i didnt fond something in the howto or have tomatos on my eyes |
| 20:25.18 | DocScrutinizer | you want to install some monav thing - too long ago to recall whether it's been server, client, plugin, whatever |
| 20:25.49 | *** join/#maemo lxp (~lxp@62-47-168-101.adsl.highway.telekom.at) |
| 20:26.10 | DocScrutinizer | beware, there's an incompatible version of monav somewhere in extras-devel IIRC |
| 20:26.16 | DocScrutinizer | maybe fixed now |
| 20:27.27 | DocScrutinizer | some asshat updated extras-devel monav with version that broke API |
| 20:27.29 | Itschue | Make sure to install the correct version of monav-routing-daemon: Version 0.2.release-2 from the extras repository works with all versions of Marble. Version 0.3.release-1 from extras-devel works with Marble 1.1.1 and later. |
| 20:27.44 | DocScrutinizer | MHM |
| 20:27.47 | DocScrutinizer | thanks :-D |
| 20:28.37 | Itschue | i hope later vesion than 03-1 work correct when not i will see this in some minutes or later when im finnished |
| 20:29.08 | Itschue | i hope that al monav things also called somwhat with monav |
| 20:30.52 | Itschue | do you know something about navit and/or the other routing software? |
| 20:33.48 | *** join/#maemo em (~em@unaffiliated/emma) |
| 20:37.09 | *** join/#maemo Venusaur (~desu@wikipedia/Antonio-Lopez) |
| 20:38.23 | DocScrutinizer | well, latest marble version is 1.2 anyway |
| 20:38.29 | DocScrutinizer | so no issue realy |
| 20:39.01 | DocScrutinizer | (other sw) I used to use mappero |
| 20:39.12 | DocScrutinizer | I'm still undecided which one I like more |
| 20:40.10 | *** join/#maemo markinfo (~marek@dhcp13.dmg.tuwien.ac.at) |
| 20:40.16 | Itschue | hmm marble 1.3 has problems with monav 0.3-3 hmm |
| 20:40.38 | DocScrutinizer | dang |
| 20:41.23 | *** join/#maemo vdv (1000@e09R011.mensa-wohnheim.uni-bremen.de) |
| 20:41.35 | Itschue | hmm i must find a way to install other versions i thing i have a look at maemo.org/packages |
| 20:42.27 | DocScrutinizer | a pitty that devels tend to ignore the paramount importance of click-to-install convenient maintenance for apps |
| 20:43.01 | Itschue | that i dont understand |
| 20:43.10 | Itschue | can you please say it in german |
| 20:43.23 | DocScrutinizer | I.E. such type of breakage of a core function by such a silly thing is a killer issue for any app |
| 20:44.17 | DocScrutinizer | in simple english words: marble1.3 not working with monav after simple install: marble dead |
| 20:45.16 | DocScrutinizer | no user gives a flying F* about how many cute new features 1.3 brings to them, as long as it simply doesn't work OOTB |
| 20:45.33 | Itschue | and simple english for I.E. such type of breakage of a core function by such a silly thing is a killer issue for any app |
| 20:45.50 | DocScrutinizer | see above |
| 20:46.00 | DocScrutinizer | ~wtf i.e. |
| 20:46.11 | Itschue | so best way is use older version this version which is shown in the howto right? |
| 20:46.11 | DocScrutinizer | ~i.e. |
| 20:46.11 | infobot | i heard i.e. is there any more efficient way than just putting in a func call? |
| 20:46.31 | DocScrutinizer | dang, I.E. == In Expression |
| 20:46.42 | DocScrutinizer | aalso known as "particularly" |
| 20:47.40 | DocScrutinizer | ~forget i.e. |
| 20:47.40 | infobot | DocScrutinizer: i forgot i.e. |
| 20:47.58 | *** join/#maemo Timmy (~quassel@80.191.183.6) |
| 20:48.05 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 20:48.06 | Itschue | a pitty that devels tend to ignore the paramount importance of click-to-install convenient maintenance for apps I.E. such type of breakage of a core function by such a silly thing is a killer issue for any app please in german in query |
| 20:48.07 | DocScrutinizer | hates lusers abusing ~ attention-char of bot |
| 20:48.50 | DocScrutinizer | Itschue: please disable echo on your terminal ;-) |
| 20:50.54 | Itschue | sorry i dont know where i not often use mirc and its about 10 years ago when i used mirc ver often |
| 20:51.46 | DocScrutinizer | well, a joke. I guess you intentionally echoed my concatenated last 2 posts |
| 20:52.05 | DocScrutinizer | I miss the reason though why you did it |
| 20:52.18 | *** join/#maemo Timmy_ (~quassel@80.191.183.6) |
| 20:54.00 | Itschue | i want it in german look at query sorry for so much work with me |
| 20:58.16 | Itschue | back to the problems with monav 0.3-3 didnt work with marble 1.3 is there realy an error or only a settings thing that the programmer didnt changeded (i hope you can understand this) |
| 20:58.42 | DocScrutinizer | I understand but don't know |
| 20:59.28 | DocScrutinizer | I seem to remember I pinned the monav version back when, so it never updated to 0.3 |
| 21:00.18 | DocScrutinizer | then again I rarely ever been without internet connection during last ~12 months |
| 21:00.51 | DocScrutinizer | so proably I wouldn't even notice when marble used an online routing service rather than monav |
| 21:01.51 | DocScrutinizer | if the marble guys would care about their users, they had sorted the issue before even pushing anything to any repo, no matter if extras or extras-devel |
| 21:02.39 | DocScrutinizer | I mean how hard could it be to put a dependency to a particular version of monav in their marble .deb pkg? |
| 21:02.53 | Itschue | so to monav 0.3-3 and marble 1.3 it can be a realy incompatibility or only an "fake" error because some code things wouldnt changed by the programmer |
| 21:03.17 | DocScrutinizer | sorry, this I didn't get now |
| 21:04.14 | Itschue | but these are the only two options or did understand it fals? |
| 21:05.11 | Itschue | i think it couldnt be hard for a programmer to put in dependencys but i wont sy too mouch about this becaus i didnt programm |
| 21:06.42 | *** join/#maemo jrocha (~JRocha@156.0.60.213.dynamic.mundo-r.com) |
| 21:09.27 | Itschue | it is very curios on maemo.org/packages the ny monav routing daemon 0.3-1 in extras free stand missing dependencies and the same version in extras-testing ther isnt this message |
| 21:14.04 | DocScrutinizer | err, yes. >> libqt4-core (>= 4.7.0~git20100909-0maemo1+0m5)<< what a shite it's missing this on extras repo |
| 21:15.19 | Itschue | this message is an error or? |
| 21:17.12 | Itschue | hmm i find routing daemon 0.3-1 but not routing client in version 03-1 only 03-2 or 03-3 |
| 21:22.29 | DocScrutinizer | DAMN YOU RECALLER |
| 21:24.52 | DocScrutinizer | every now and then it doesn't stop recording at end of call, and then it floods the storage with some insanely huge file. OR it simply goes completely bonkers and doesn't stop popping up a notice "recaller: recording since 15:03:35" every 30s, and nothing will stop that |
| 21:25.24 | DocScrutinizer | damn shit |
| 21:26.18 | DocScrutinizer | and I bet not ever this boot will fix it :-S |
| 21:26.25 | DocScrutinizer | even* |
| 21:26.58 | DocScrutinizer | as it's probably a recurring event in alarmd |
| 21:28.47 | Itschue | for what you use/need recaller? |
| 21:28.58 | DocScrutinizer | it records my calls |
| 21:29.54 | Itschue | nad gives yu work or? |
| 21:30.07 | DocScrutinizer | I pretty much like the idea to listen to them when I'm old and senile, and I got no dairy or anything else to refresh my memories |
| 21:30.24 | Itschue | cool idea |
| 21:30.33 | DocScrutinizer | soory "nad gives yu work" doesn't parse |
| 21:32.00 | Itschue | that gives you work |
| 21:32.50 | DocScrutinizer | telegram style staements work the better, the more fluent and trained a speaker of the language you are |
| 21:34.13 | Itschue | and im not so good i know ill do my best i think i should be more often her to train my english |
| 21:34.19 | DocScrutinizer | very terse statements have no redundancy to correct any errors in them. make them even more terse and they start to lack important bits of info |
| 21:36.26 | DocScrutinizer | hmm, seems boot has 'fixed' the recurring notification at least. I hope the root cause got somewhat neutered by freeing up space on storage so recaller doesn'T enter pathological state when write() throws error |
| 21:38.25 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 21:39.06 | DocScrutinizer | idly ponders about his scrutinizer_daemon project from the shelf for green ideas that need some riping |
| 21:40.50 | *** join/#maemo retro|cz (~retro@106.142.broadband6.iol.cz) |
| 21:41.02 | DocScrutinizer | some monitor daemon that would kick in when any app is causing unusual state of system - may it be high CPU load, suddenly increased battery drain, whatever |
| 21:42.55 | kerio | DocScrutinizer: ulimit *all* the things? |
| 21:43.13 | kerio | it's easy to check that nothing is using too much cpu if nothing *can* use too much cpu |
| 21:43.44 | DocScrutinizer | showing the parameter that tripped the threshold, the process that's the suspected culprit, a rotary to adjust the threshold to a particular acceptable limit for this process, and "ignore", "ignore always", "kill this time" and "kill every time" buttons |
| 21:44.55 | DocScrutinizer | kerio: yep, something similar to ulimits, but per process and with a warning dialog (at least on first time a process trips a limit) |
| 21:46.26 | DocScrutinizer | faintly similar to cookie handling in browser: you can allow or reject cookies for any particukar URL, or just leave the rest of URLs to the general rules you've defined |
| 21:48.48 | kerio | a process is using too much cpu, let's use more cpu to display a dialog |
| 21:50.45 | DocScrutinizer | hahaha |
| 21:51.21 | DocScrutinizer | don't you think this was a rather silly comment? |
| 21:53.43 | DocScrutinizer | "battery is low, let's use some more battery to playback a warning signal" KTNXBYE |
| 21:54.26 | Itschue | hmmm |
| 21:54.38 | DocScrutinizer | oh wait, that's what maemo already does ;-P |
| 21:56.11 | Itschue | did i understand it right you speak about and app that reports app a use to much cpu there cann be an error in it app use very much ram space there can be an error |
| 21:56.37 | DocScrutinizer | yes |
| 21:56.46 | *** join/#maemo user_ (~user@95.214.187.137) |
| 21:59.04 | Itschue | that would be an geat ap because some days ago i had problems from minute to minute more processes are shown in htpo normlay they are under 200 and the go to over 600 and there where very very much processe called dbus-script |
| 22:01.37 | DocScrutinizer | mhm, I know that :-D |
| 22:01.48 | DocScrutinizer | had the same problem ;-) |
| 22:02.00 | Itschue | o cool im not allone |
| 22:02.13 | DocScrutinizer | you mustn't place bogus files in /etc/dbus-scripts |
| 22:02.27 | Itschue | i decide to flash my device because uninstal several apps didnt worked |
| 22:02.33 | DocScrutinizer | it makes dbus-scriptd go havok |
| 22:03.47 | Itschue | place bogus files ??? dbus-script go havok = it restarts and the error is away? |
| 22:04.20 | *** join/#maemo geaaru (~geaaru@host33-201-dynamic.50-79-r.retail.telecomitalia.it) |
| 22:04.34 | DocScrutinizer | exactly a typical case for my scrutinizer daemon, which whould detect the sudden increase on number of processes, should find out what's the parent process and SIGSTOP it and rise a requester what to do about the issue |
| 22:05.26 | DocScrutinizer | Itschue: in my case a placed a shell script in the /etc/dbus-scripts/ directory |
| 22:05.59 | DocScrutinizer | this was sufficient to make dbus-scripting daemon go mad and spawn almost 1000 processes |
| 22:06.46 | Itschue | and in my case its not easy to find out why i had so much dbus-scripts? |
| 22:06.53 | DocScrutinizer | actually it spawned new processes all the time, while some maemo think killed some of them when they hit limit of IIRC 1024 total processes on system |
| 22:07.53 | Itschue | what happen when the sytem reach 1024 processes? |
| 22:08.18 | DocScrutinizer | Itschue: for some reason your /usr/sbin/dbus-scripts --system process spawned new processes as well |
| 22:08.52 | DocScrutinizer | Itschue: usually things get nasty when process table is completely filled, as no new processes can get started |
| 22:09.25 | DocScrutinizer | caling "killall dbus-scripts" in shell is a new process - usually ;-D |
| 22:09.50 | DocScrutinizer | (not on busybox, which back when this happened it saved me) |
| 22:11.10 | Itschue | so "killall dbus-scripts" must be "started before 1024 processes are reached ? |
| 22:11.22 | DocScrutinizer | basically yes |
| 22:11.32 | DocScrutinizer | on a normal system it's like that |
| 22:11.56 | DocScrutinizer | on maemo you got busybox shell which doesn't start a new process for builtins like kill |
| 22:12.22 | Itschue | o god i hope my english isnt to bad |
| 22:12.32 | DocScrutinizer | starting a xterm to access shell anyway IS a new process |
| 22:13.10 | Itschue | when i see 1021 processes i must hurry up right |
| 22:13.24 | DocScrutinizer | hehe |
| 22:13.35 | DocScrutinizer | probably it's already too late then :-D |
| 22:14.08 | Itschue | i must be verry fast *g* |
| 22:14.11 | DocScrutinizer | on a desktop linux the max number of processes is way higher though, maybe 32k |
| 22:14.47 | DocScrutinizer | at least I assume it's like that |
| 22:15.02 | DocScrutinizer | actually I've never tested ;-) |
| 22:16.34 | Itschue | something to the query i think the main chat here isnt the right place for the translation in german and question if i understand it right or not ? |
| 22:17.11 | DocScrutinizer | I guess with dbus-scripting the problem is rather simple: if there's a file in /etc/dbus-scripts.d/ that has an error, it may cause the daemon process to fork an now subprocess |
| 22:17.16 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 22:17.42 | DocScrutinizer | usually we suggest to use google translate for that :-) |
| 22:19.40 | Itschue | i used it but wasnt sure yet |
| 22:20.14 | DocScrutinizer | though if anybody is using too poor or complicated english so you don't understand it, then this person might want to know about that fact and try to post simpler sentences |
| 22:20.18 | Itschue | i know google translator i use it too but sometimes it doenst 100% helps |
| 22:21.27 | DocScrutinizer | using proper punctuation and a spellchecker helps a lot |
| 22:21.45 | DocScrutinizer | (I know I'm not the best example for that :-D ) |
| 22:23.10 | Itschue | hmm where is a punctutation and spellchecker i dont know that google can do this |
| 22:23.53 | Itschue | on a scale from zero to ten, ten is the best where do you see my english? |
| 22:24.17 | *** join/#maemo Kilroo (~Kilroo@cpe-098-026-200-222.triad.res.rr.com) |
| 22:24.47 | Itschue | grrrrr downloads from marble maps faild said my n900 wtf is that |
| 22:25.28 | DocScrutinizer | it's not meant to be on google, spellchecker is helping me to spot typos on my IRC input line (if I care to watch for small red underlines). Punctuation is a matter of taking care ot to write on I usually start now sentences at least with a Capital Letter I also usually use a period. At end of semtence |
| 22:26.28 | DocScrutinizer | (scale) I'm no teacher, and we don't give grades here usually |
| 22:27.30 | Itschue | hmm please make an exception |
| 22:28.09 | DocScrutinizer | you're too shy to use proper pidgin |
| 22:29.07 | Itschue | to shy to use proper pidgin ? |
| 22:29.33 | Itschue | when yo didnt give a grade how good can you understand me ? |
| 22:30.05 | DocScrutinizer | your sentences are too complex for your english skills |
| 22:31.15 | DocScrutinizer | your very last pst is a good example |
| 22:31.30 | DocScrutinizer | it didn't transport exactly what I guess you meant |
| 22:34.17 | DocScrutinizer | "You do not give grade. OK. You can understand me?" is almost same in "pidgin" |
| 22:35.47 | DocScrutinizer | it's quite obvious that you tried to pack three notions/statements into one complex sentence, and that didn't exactly work |
| 22:37.03 | Itschue | i see two notions/statements |
| 22:37.26 | DocScrutinizer | the linking of both is a statement of its own |
| 22:38.24 | DocScrutinizer | and it's a quite hard to understand statement |
| 22:38.28 | Itschue | but when i ask you can understand me? i get as answer yes or no right? |
| 22:38.37 | DocScrutinizer | right |
| 22:39.14 | Itschue | but i still want to know how good you understand me |
| 22:39.49 | DocScrutinizer | I wouldn't know how to properly answe this question. In any language |
| 22:40.45 | DocScrutinizer | obviously I understand your last few posts good enough to have a conversation with you - at least that'S how it seems to me |
| 22:41.34 | Itschue | the "still" was to much |
| 22:42.20 | DocScrutinizer | yes |
| 22:43.25 | *** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net) |
| 22:43.28 | Itschue | " I wouldn't know how to properly answe this question. In any language" because the question was to bad ? |
| 22:43.57 | DocScrutinizer | anyway it seems your english is just fine for this channel (my own english skills are far from anything like "good") |
| 22:45.04 | Itschue | i think your english is good |
| 22:45.11 | DocScrutinizer | (woukdn't know) not because the question was bad, but because I a) lack the english expertise to rate your english, and b) I have no commonly accepted scale to use |
| 22:46.21 | DocScrutinizer | all I can say is a yes/no or good/bad qualification, and your english clearly rates for the "good" |
| 22:46.57 | DocScrutinizer | at least since last 15 or so minutes |
| 22:48.11 | Itschue | thank you for your patience with me |
| 22:48.19 | DocScrutinizer | yw |
| 22:48.27 | Itschue | yw ? |
| 22:48.33 | DocScrutinizer | you're welcome |
| 22:49.02 | Itschue | grrr i didnt get marble installed |
| 22:49.38 | DocScrutinizer | sorry, I'm out now, for saturday evening activities |
| 22:49.46 | Itschue | hmm i think youre english good and much better than mine (hope thats right spelling) |
| 22:50.05 | Itschue | no problem i thank you soooooo much |
| 22:50.53 | Itschue | you help me, and bear to me even |
| 22:51.40 | *** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net) |
| 22:55.10 | *** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net) |
| 23:02.18 | *** join/#maemo int_ua (~int_ua@159.146.157.214) |
| 23:21.31 | *** join/#maemo Itschue|ghost (~Itschue@p54B4B7EF.dip.t-dialin.net) |
| 23:22.20 | *** join/#maemo mortenvp (~mortenvp@port463.ds1-abc.adsl.cybercity.dk) |
| 23:22.51 | *** join/#maemo Sazpaimon_ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 23:23.08 | *** join/#maemo Sazpaimon_ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 23:23.25 | *** join/#maemo Sazpaimon_ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 23:23.42 | *** join/#maemo Sazpaimon_ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 23:23.59 | *** join/#maemo Sazpaimon_ (wat@c-68-32-58-174.hsd1.nj.comcast.net) |
| 23:37.27 | *** join/#maemo PeterWolf (~peter@118-169-32-220.dynamic.hinet.net) |