IRC log for #maemo on 20120429

00:00.47*** join/#maemo DrGrov (~C.J@a91-153-77-41.elisa-laajakaista.fi)
00:12.41*** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141)
00:21.31*** join/#maemo topobot (~topobot@77.210.171.147)
00:21.46topobothi
00:22.20topobotis there any company producing  smartphones  with maemo?
00:22.37topobotor maemo is oldschool?
00:28.42villagerit isn't open enough that anyone other than nokia could do it
00:30.08villagermeego was supposed to fix that, but...
00:30.41*** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au)
00:48.39*** part/#maemo DrGrov (~C.J@a91-153-77-41.elisa-laajakaista.fi)
00:49.12SpeedEvil:/
00:49.18SpeedEvilAlas true
00:51.57*** join/#maemo sirdancealot2 (~sirdancea@98.82.broadband5.iol.cz)
01:05.20*** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz)
01:10.58*** join/#maemo uen| (~uen@p5DCB3292.dip.t-dialin.net)
01:40.42*** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz)
01:54.18*** join/#maemo Roomerlol (~Roomerlol@95-27-96-241.broadband.corbina.ru)
02:04.42*** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141)
02:17.21jpinx.
02:25.32*** join/#maemo Roomerlol (~Roomerlol@95-27-96-249.broadband.corbina.ru)
02:38.45*** join/#maemo radic_ (~radic@dslb-178-002-225-014.pools.arcor-ip.net)
02:43.00*** join/#maemo bergie (~bergie@216-75-224-178.static.wiline.com)
02:59.11*** join/#maemo pcfe (~pcfe@91-158-0-26.elisa-laajakaista.fi)
02:59.11*** join/#maemo pcfe (~pcfe@redhat/pcfe)
03:01.00*** join/#maemo dockane (~dockane@dsdf-4db51e1c.pool.mediaWays.net)
03:20.13*** join/#maemo Gh0sty (~ghosty@79.132.232.145)
03:20.27*** join/#maemo robbiethe1st (~robbiethe@71-221-216-73.spkn.qwest.net)
03:23.49*** join/#maemo valerius (~user@85.26.180.130)
03:25.20*** join/#maemo robbiethe1st (~robbiethe@71-221-216-73.spkn.qwest.net)
04:03.02*** join/#maemo PeterWolf (~peter@118-169-32-220.dynamic.hinet.net)
04:32.44*** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com)
04:35.47*** join/#maemo robink_ (~quassel@fatcat.creosotehill.org)
04:40.49*** join/#maemo robink (~quassel@unaffilated/robink)
04:46.14*** join/#maemo ArGGu^^ (~arggu@91-157-140-34.elisa-laajakaista.fi)
05:00.33*** join/#maemo e-yes (~e-yes@94.45.180.138)
05:00.35*** join/#maemo Zahra (~Zahra@unaffiliated/belendax)
05:17.20*** join/#maemo fscker (~adam@hypnos.fscker.com)
05:19.12*** join/#maemo fscker (~adam@hypnos.fscker.com)
05:20.29*** join/#maemo fscker (~adam@hypnos.fscker.com)
05:51.05*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
06:09.18*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
06:19.39*** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz)
06:27.34*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
06:39.40*** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141)
06:52.31*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
06:57.15*** join/#maemo Pali (~pali@unaffiliated/pali)
07:01.25*** join/#maemo sq-one (~sq-one@p54A1FD3B.dip.t-dialin.net)
07:04.16*** join/#maemo koo4 (~koo@98.82.broadband5.iol.cz)
07:13.54*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
07:14.36*** join/#maemo tank-man (1000@S010600121729c6a1.vc.shawcable.net)
07:15.35*** join/#maemo dhbiker (~dhbiker@APN-122-123-145-gprs.simobil.net)
07:18.37*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
07:23.33*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
07:29.37*** join/#maemo sasquatch (~username@p579581BC.dip.t-dialin.net)
07:30.33*** join/#maemo Itschue (~Itschue@p54B4CDD2.dip.t-dialin.net)
07:30.38*** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com)
07:33.15*** join/#maemo zap (~zap@178.130.21.28)
07:33.53*** join/#maemo udovdh (~udovdh@pindarots.xs4all.nl)
07:34.47Itschuegood morning
07:37.16*** join/#maemo MacDrunk (~marper@201.165.164.208)
07:38.40*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
07:43.44*** part/#maemo Gadgetoid (~phil@cpc6-nrwh10-2-0-cust61.4-4.cable.virginmedia.com)
07:54.33*** join/#maemo dhbiker (~dhbiker@APN-122-123-145-gprs.simobil.net)
07:55.27*** join/#maemo FACEFOX-DOT-COM (~gfdffdfd@pool-74-111-197-200.lsanca.fios.verizon.net)
07:56.52*** part/#maemo MacDrunk (~marper@201.165.164.208)
08:17.31*** join/#maemo dhbiker (~dhbiker@APN-122-120-196-gprs.simobil.net)
08:19.34*** join/#maemo kerio92 (~kerio@unaffiliated/kerio)
08:21.57*** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au)
08:27.00*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
08:32.18*** join/#maemo NIN101 (~NIN@p5DD28488.dip0.t-ipconnect.de)
08:33.54*** join/#maemo NIN102 (~NIN@p5DD28488.dip0.t-ipconnect.de)
08:35.52*** join/#maemo Free-MG (~test@p5DD7D374.dip.t-dialin.net)
08:43.50*** join/#maemo hurbu (~hurbanza@81-174-24-122.dynamic.ngi.it)
08:54.05*** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz)
08:59.56*** join/#maemo ced117 (~ced117@AStrasbourg-552-1-44-185.w90-26.abo.wanadoo.fr)
08:59.56*** join/#maemo ced117 (~ced117@opensuse/member/ced117)
09:06.27*** join/#maemo jrocha (~JRocha@156.0.60.213.dynamic.mundo-r.com)
09:07.31*** join/#maemo spark666 (~spark666@92.86.186.16)
09:07.31*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
09:13.14Itschuesomeone here ?
09:14.22spark666yes
09:15.30Itschuemy n900 cant acces to nokia repository
09:15.46Itschuecan you access nokia repository?
09:16.12spark666yes
09:16.23Itschueyou can access ?
09:16.33spark666your internet connection works for sure?
09:16.39spark666on phone i mean
09:16.58Itschueyes on phone i have acces to maemo.org repository
09:17.11Itschuecan surf to google and other inet sites
09:18.00Itschuean on pc can surf but cant acces to nokia repository
09:19.57Itschueits curious or?
09:20.14spark666yeah...
09:20.32spark666brb ill need to reboot my laptop
09:21.01Itschueok im back later have to go to bathromm for something
09:22.36spark666okey
09:26.08*** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net)
09:29.58*** join/#maemo spark666 (~spark666@92.86.186.16)
09:29.59*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
09:30.59*** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl)
09:38.09freemangordonPali, ping
09:38.17Palifreemangordon, pong
09:39.05freemangordonPali, hald-addon-bme is to the point that I have to get the real data, Where am I supposed go get that?
09:39.11freemangordonfrom
09:39.34freemangordonwhich sysfs entry is that?
09:39.48Pali/sys/class/power...
09:40.05Paliuse entry "uevent"
09:40.08freemangordonso, i should stop bme and insmod bqxxx module?
09:40.13Paliyes
09:40.20freemangordonuevent?
09:40.26Palialso for monitoring changes use inotify calls
09:40.41Palistandard linux uevent file
09:40.46freemangordon:D
09:40.55freemangordongood to hear.
09:41.11freemangordonsorry, do you have an example or I have to google
09:41.18Paliafter loading bq27x00_battery module, you will get /sys/class/power_supply/bq27200-*/
09:41.26freemangordonI know that
09:41.27Paliand here will be uevent file
09:41.33freemangordonknow that too
09:41.40Paliformat is PROPERTY=VALUE
09:41.44freemangordonbut have NFC what to do with it
09:41.48freemangordonaaah
09:41.50freemangordonok
09:41.58Paliuse inotify for monitoring if that file was changed
09:42.05Paliand when changed, read it
09:42.20freemangordonok
09:42.44*** join/#maemo iDont (~iDont@j138215.upc-j.chello.nl)
09:42.45Paliwhen you load bq2415x_charger module you will get entry /sys/class/power_supplt/bq2415x*/
09:43.09*** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ffdec300-4.dhcp.inet.fi)
09:43.12freemangordonPali, do I need it?
09:43.13Palibut I think for monitoring battery is only needed bq27200 chip
09:43.18freemangordonyeah
09:43.45Palibq24150 chip tell you when you really charging battery
09:44.03Palibut that can tell also bq27200
09:44.18freemangordonok, for now I will use 27200
09:48.38*** join/#maemo SmilybOrg (Smily@BSN-61-106-171.dial-up.dsl.siol.net)
10:05.30*** join/#maemo BCMM (~ben@unaffiliated/bcmm)
10:12.23*** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net)
10:14.21*** join/#maemo liar (~liar@clnet-p09-185.ikbnet.co.at)
10:19.16DocScrutinizerPali: inotify doesn't work on sysfs
10:19.35Paliand what is working?
10:19.52*** join/#maemo Itschue (~Itschue@p54B4CDD2.dip.t-dialin.net)
10:20.03freemangordong_file_monitor?
10:20.05DocScrutinizerkevents, if maemo powerkernel supports that
10:21.03Palifor example musb driver call sysfs_notify
10:21.14Paliand then hal is monitoring status of file
10:22.26DocScrutinizerPali: you loked into ke-recv
10:22.33DocScrutinizerlook again!
10:22.50Palike-recv receiving events from hal
10:22.58DocScrutinizerooh
10:23.06Paliit connect to hal via dbus
10:23.14Paliand listen for dbus signals
10:24.03Paliok, I looked into power_supply code and it call kobject_uevent KOBJ_CHANGE
10:24.13DocScrutinizerthat's kevents
10:24.31DocScrutinizeraka kobjects
10:25.45PaliI looked into hal year ago and I remember it monitor uevent file of power_supply
10:25.54PaliI download sources again
10:26.21DocScrutinizermaybe it's polling uevent
10:26.28DocScrutinizerwhich is a BAD thing
10:28.36DocScrutinizerI always thought ke-recv is KernelEvents-RECeiVe
10:28.56Paliwhen I patched kernel-power to call sysfs_notify when musb driver change mode to host HAL has correct state of usb host mode
10:29.34Paliwithout that patch HAL still show old informations, so hal do not polling for musb
10:29.47DocScrutinizersysfs-notify is using kevents afaik
10:30.30Palishit, now I looked into hal code for power_supply
10:30.34Paliand it doing polling
10:30.53DocScrutinizerI knew that
10:32.19DocScrutinizersysfs-notify / kevents wasn't available or very commonly used when maemo kernel version was developed
10:32.32PaliI wil try to look what is doing with musb
10:32.41DocScrutinizerkevents concept is relatively "new"
10:33.30*** join/#maemo diverse_izzue (~hunzikea@2606ds5-by.1.fullrate.dk)
10:33.52DocScrutinizeruse MXR, search for kobject_uevent
10:34.03*** join/#maemo udovdh (~udovdh@pindarots.xs4all.nl)
10:34.05DocScrutinizera pity you won't get a single hit
10:34.18DocScrutinizerwe at h-e-n frowned at that a lot
10:34.19freemangordonwhat about libudev?
10:34.35*** join/#maemo ced117_ (~ced117@AStrasbourg-552-1-85-155.w92-141.abo.wanadoo.fr)
10:34.54DocScrutinizerfreemangordon: udev is similar to kobjects, just a tiny bit different
10:35.13freemangordonbut could it be used?
10:35.21DocScrutinizerI don't think so
10:35.37DocScrutinizerit could be ABused
10:35.46freemangordonso, what am I supposed to use :)
10:36.02DocScrutinizerbut why would we wanna do that when there's nice shiny kobject_uevent concept
10:36.24DocScrutinizerfreemangordon: for now you need polling
10:36.28DocScrutinizer:-/
10:36.45DocScrutinizeruntil pali fixed the kernel side and implemented kobject_uevent
10:36.51DocScrutinizeraka sysfs-notify
10:37.04freemangordonso, you are sure i cannot use udev_monitor?
10:37.33DocScrutinizeryes. been there, tried that
10:37.47freemangordon:(
10:38.03*** join/#maemo zeq (~s_j_newbu@2a01:348:1e3:1:e6ec:10ff:fe9a:d418)
10:39.01DocScrutinizerudev-adm monitor -> nuttin
10:40.57DocScrutinizeractually all you both said has been said by me some 2 years ago, and IIRC it was moh who educated me about maemo not using kevents
10:42.24DocScrutinizerfor sure it was moh who tought me inotify doesn't work on sysfs
10:42.58Palihal using special maemo addon for musb
10:43.04Palisource code is in hald/linux/addons/addon-usb-cable.c
10:43.17freemangordondamn, so I have to poll. well, actually stock hald-addon-bme polls bme too :)
10:43.25Paliaddon open filedesc on sysfs entry
10:43.31Paliand call syscall poll
10:44.01Paliafter syscall exit read sysfs file
10:44.22freemangordonPali, where is that code?
10:44.54Palihttp://repository.maemo.org/pool/fremantle/free/h/hal/
10:45.17*** join/#maemo mortenvp (~mortenvp@port463.ds1-abc.adsl.cybercity.dk)
10:45.54Paliand if kernel (musb driver) do not call notify, poll syscall do not return
10:46.12*** join/#maemo dos1 (~dos@unaffiliated/dos1)
10:46.41freemangordonso, can we use that for bq
10:46.51Palifreemangordon, also code online here: http://mxr.maemo.org/fremantle/source/hal/hald/linux/addons/addon-usb-cable.c
10:47.04freemangordonok, i did apt-get source
10:47.36SpeedEvilidly wonders if you can swap emmc for a SD transparently.
10:47.40Palifreemangordon, no idea if it will work, in power_supply is kobject_event call
10:48.08freemangordonaah, ok, si i will have to poll it :(
10:48.13freemangordon*so
10:48.34*** join/#maemo diverse_izzue (~hunzikea@2606ds5-by.1.fullrate.dk)
10:48.48ShadowJKiirc poll()/select() works in sysfs, and wakes up when driver calls notify_all() or something like that
10:49.16ShadowJKoh you discovered already
10:49.22ShadowJKI was scrolled up a bit :)
10:49.55ShadowJKSpeedEvil: transparently, on the fly, online?
10:50.52ShadowJKI think you'd edit the script which mounts emmc, and disable the scripts that mount sd? :)
10:52.24SpeedEvilShadowJK: Well - no
10:52.36SpeedEvilShadowJK: offline - with hot-air and shizzle.
10:52.50ShadowJKoh, lol
10:56.50spark666its okey to give user a password?
10:57.12spark666like gpasswd user xxxxyyyxx
10:57.20*** join/#maemo ale152 (~quassel@host176-148-dynamic.7-87-r.retail.telecomitalia.it)
10:57.34DocScrutinizerShadowJK: Pali: freemangordon: aiui poll() and read() only wait for the function in kernel delivering new value for the sysfs node. However this is supposed to happen immediately after the read() *triggered* the function. So the poll()/read() doesn't wait for *new* state of e.g. VBUS, it simply *polls* the state each time addon-usb-cable.c main() gets called
10:57.37DocScrutinizerAIUI
10:57.50DocScrutinizerspark666: yes
10:57.56spark666couse when i try to ssh my n900 (not as root) it ask me the passw
10:58.06spark666but user doesnt have one by default afaik
10:58.13freemangordonsu user?
10:58.21freemangordonafter logged in as root
10:58.42spark666freemangordon: and what that makes?:P
10:58.50DocScrutinizerspark666: yes, that's how ssh works
10:59.13DocScrutinizerssh demands a password being set
10:59.14spark666DocScrutinizer: humm user its allready in sudoers
10:59.25spark666but its whit nopasswd
10:59.35DocScrutinizerunrelated
10:59.40spark666ok:P
11:00.05DocScrutinizerthough you might want to fix this nonsense as well
11:00.10DocScrutinizer~jrtools
11:00.11infobotfrom memory, jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
11:01.44spark666it works
11:01.45spark666:D
11:02.58freemangordonso, i should setup a timer and read the state of what?
11:03.15DocScrutinizerthat's the very polling HAL does
11:03.39spark666ohh and btw  its safe to switch to bash?
11:03.41DocScrutinizerwhich I toldya you'll have to use until Pali fixed sysfs-notify cals in kernel
11:03.41*** join/#maemo dos1 (~dos@unaffiliated/dos1)
11:03.57DocScrutinizerspark666: not exactly, for user
11:04.18spark666DocScrutinizer: then ill stich to ash,even that im not a big fan :P
11:04.50DocScrutinizerwell it's safe to switch to bash for login shells, unless you also replace busybox by proper unix tools, *and* make bash a valid shell in /etc/shells
11:05.04DocScrutinizeragain, see
11:05.07DocScrutinizer~jrtools
11:05.07infobotfrom memory, jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
11:05.33spark666im looking right now:P
11:06.07*** join/#maemo maybeWTF (~cl@p5B163533.dip.t-dialin.net)
11:07.07DocScrutinizerzhe crux is: boot resp X/hildon init scripts are using some busyboxisms, and when your system user is using bash and unix tools instead busybox during boot, it will bootloop
11:08.25DocScrutinizerroot however is dafe to completely replace messybox and switch to bash, I've been told
11:08.30DocScrutinizersafe*
11:10.06spark666hummm
11:10.34DocScrutinizerso if you are going to add /usr/bin/gnu etc to PATH in .bashrc, make DAMN SURE you remove this bullshit line >> . .bashrc<< from your .profile
11:11.17spark666i wont switch to bash better..more safw
11:11.20spark666safe*
11:11.40DocScrutinizeras this will make busybox also source .bashrc, which in turn causes PATH make usr/bin/gnu primary executable location, which in turn causes bootloop
11:12.15spark666i understand what you say
11:12.22DocScrutinizerspark666: I have the setup like I shown in ~jrtools, and first cmd I enter after login is >>bash<<
11:12.31DocScrutinizersafe bet
11:14.20*** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net)
11:19.06freemangordonDocScrutinizer, any idea how to force hal to load the addon?
11:19.14DocScrutinizernope
11:19.19DocScrutinizerHAL is EVIL
11:19.25DocScrutinizerI tend not to touch it
11:19.31DocScrutinizer:-)
11:20.23vdvfollowing dbus call has no effect my n900 dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternCommunicationIM"
11:20.27*** join/#maemo liar (~liar@clnet-p09-185.ikbnet.co.at)
11:20.32vdvwhat can be the reason for that?
11:20.34DocScrutinizeresp since I heard it's already dead, and what we see in maemo is a zombie
11:22.04DocScrutinizervdv: either you got a typo, or your etc/mce/mce.ini has no pattern of that name, or that pattern has lower prio than the one currently active, or it's not defined to be active for the state your device is in
11:22.34vdvhmm
11:22.49Palifreemangordon, forgot about kobject, notify, ...
11:23.00vdvdoubt, that it typo is, because copy-pasted from here http://wiki.maemo.org/Phone_control#LED
11:23.06DocScrutinizeriirc per default that pattern is defined as being active on locked screen only
11:23.20freemangordonPali, yeah, going to poll
11:24.25DocScrutinizervdv: lemme check - a minute please
11:24.49Palibq27200 kernel driver doing polling internally
11:24.59vdvthere's a line in mce.ini, PatternCommunicationIM=30;1;0;0000;0000;40007f00017f017f050001ff01ff0000
11:25.11DocScrutinizervdv: works great on my locked device here
11:25.30Paliso there cannot be proper implementation. you need to poll in kernel or poll in user space
11:25.37DocScrutinizeralso works on unlocked device3
11:25.52DocScrutinizerI c&p your post above
11:26.09freemangordonPali, can I poll this uevent file?
11:26.23vdvvery interesting..
11:26.31vdvsomething is wrong with my n900
11:26.35DocScrutinizerPali: I explained bq27200.ko is CRAP, just yesterday
11:26.35PaliI tried syscall select, but it not worked correctly
11:27.30DocScrutinizerPali: OTOH this chip has no infra to do proper event driven (IRQ-based) signalling
11:27.56*** join/#maemo dos1 (~dos@unaffiliated/dos1)
11:28.13vdvDocScrutinizer, PatternBatteryFull worked
11:28.15DocScrutinizervdv: check your settings-notificationlight
11:28.31Palibq driver read properties every 360s
11:28.39DocScrutinizerLOL
11:28.47vdvDocScrutinizer, device is connected via usb at the moment
11:28.49Paliso uevent file is updated every 360s
11:29.04Palibut if you read it, kernel driver update it immediately
11:29.06vdvmaybe that is the reason?
11:29.25Paliso select/poll syscalls is not good idea
11:29.47freemangordonno, i meant "read" every 5 secs or so
11:29.59Palifreemangordon, use some timer and every 10s read uevent file
11:30.04freemangordonyep
11:30.04DocScrutinizerfreemangordon: which is exactly the same
11:30.16freemangordonthe same as?
11:30.21Palino better solution
11:30.28DocScrutinizerindeed
11:30.34freemangordon:nod:
11:30.35Palibq chip has no signal...
11:30.42freemangordonwell, going to do it
11:30.54DocScrutinizeras fsckng HAL doesn'T signal hald-addon-bme/whatever when to *poll* the sysfs file
11:31.14DocScrutinizerand bq27200 doesn't tell kernel when values have changed
11:31.25vdvDocScrutinizer, settings-notificationlight is a file?
11:31.35DocScrutinizerSETTINGS
11:31.48vdvah, menu
11:31.57*** join/#maemo kama (~kama@unaffiliated/kama)
11:32.03vdvbut there's no notificationlight submenu
11:32.08DocScrutinizermeh
11:32.11DocScrutinizerthere is
11:32.18vdvah, right
11:32.20vdvsorry )
11:32.59vdvworks now
11:33.02vdvthanks
11:33.03DocScrutinizer:-P
11:33.07DocScrutinizeryw
11:33.29*** join/#maemo ced117 (~ced117@AStrasbourg-552-1-85-155.w92-141.abo.wanadoo.fr)
11:33.29*** join/#maemo ced117 (~ced117@opensuse/member/ced117)
11:33.35*** join/#maemo dos1 (~dos@unaffiliated/dos1)
11:35.01DocScrutinizerfreemangordon: however please ponder how to make the 10s sleep configurable
11:35.39freemangordonyeah, sure
11:35.48DocScrutinizerso you (at least on boottime, via parameter, $env, whatever) could set it to 1s for rapid reporting, or to 300s for better battery saving
11:35.48freemangordongconf or something
11:36.15DocScrutinizergconf is too way up?
11:36.27DocScrutinizerdunno when HAL gets instantiated
11:36.47DocScrutinizerif gconf is available at that time
11:37.22DocScrutinizerI gather hal has other settings to read during startup, just add something there
11:37.35freemangordonok, will find a way, lets first have the functionality in place
11:37.54DocScrutinizerif that's gconf - fine. If it's some /etc/* file, add it there
11:38.07freemangordonok, will remember it
11:38.11DocScrutinizer:-
11:38.12DocScrutinizer)
11:38.48*** join/#maemo hurrian (~hurrian@121.54.2.104)
11:39.45DocScrutinizerfreemangordon:   sysfs_path = getenv ("HAL_PROP_LINUX_SYSFS_PATH");  (/addon-usb-cable.c 271)
11:39.48*** join/#maemo markinfo (~marek@dhcp13.dmg.tuwien.ac.at)
11:40.25*** join/#maemo kerio (~kerio@unaffiliated/kerio)
11:41.01DocScrutinizer<PROTECTED>
11:41.06*** join/#maemo dos1 (~dos@unaffiliated/dos1)
11:41.23DocScrutinizeryw
11:42.01DocScrutinizererr
11:42.26DocScrutinizer<PROTECTED>
11:42.41DocScrutinizeranalog for other stuff
11:43.28DocScrutinizerwhile VBUS actually *has* IRQ so can get implemented event-driven/IRQ-based
11:43.42DocScrutinizerbq27200 hasn't
11:43.46DocScrutinizerso maybe
11:43.55DocScrutinizer<PROTECTED>
11:44.07DocScrutinizerI guess you got it :-)
11:45.17DocScrutinizerfor the chanlog:
11:45.23DocScrutinizerpoll_period = getenv ("HAL_PROP_BQ27200_POLL_PERIOD_SECONDS");
11:47.54*** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu)
11:49.49*** join/#maemo dhbiker (~dhbiker@APN-122-122-212-gprs.simobil.net)
11:50.36DocScrutinizeron a sidenote: this is exactly the crap sensorfw of meego did - for *all* sensors
11:51.50*** join/#maemo spark666 (~spark666@92.86.186.16)
11:51.51*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
11:52.04DocScrutinizerin any A(B(C(sysfs))) config, system C polls sysfs, B polls C, A polls B. Each on random periods, each causing wakeup of CPU.
11:52.51DocScrutinizerNot like a sane event driven setup where sysfs notifies C notifies B notifies A, *only* if there's actually something *new* to notify
11:54.56DocScrutinizerform above you might have guessed this is inevitable for some rare cases where idiotic peripherals like bq27200 have no IRQ to signal events (and even then B and C could wait for A starting a poll, and then hand it down to next lower layer, instead of each subsystem implementig its own timer based polling pace)
11:55.51DocScrutinizeron a general design rule you never want to do things like that anyway (unless there's absolutely no other way) - sensorfw does it *all the time* like that
11:56.49DocScrutinizerthat's why I always said meego has been designed by obtuse system architects and will never reach standby time of maemo
11:58.02DocScrutinizerwell, I have to admit I didn'T bother to proofread the complete sensorfw code, to check if they really use this sensor template everywhere
11:58.39DocScrutinizerand even less I checked whole meego if actually the architects had similar mindset when designing other subsystems than sensorfw
11:59.03*** join/#maemo dos11 (~dos@unaffiliated/dos1)
11:59.47DocScrutinizerbut the ignorance to even understand what I was telling them made me think whole system been designed with no clue about IRQ and event-driven design
12:00.26DocScrutinizerstandard answer: "we're using upstream"
12:01.20DocScrutinizerthat'S exactly what makes maemo different: Nokia didn't "use upstream" no matter what. Each system been carefully checked for optimal design, and completely rewritten if "upstream" was crap
12:01.52DocScrutinizeralmost each system, obviously :-D
12:01.57DocScrutinizernot HAL though
12:02.30ShadowJKthe right way is in between, fix upstream and use it
12:02.31DocScrutinizerHAL never been meant for this usecase
12:02.48ShadowJKinstead of rewriting from scratch, or using a broken upstream
12:02.56DocScrutinizerHAL basic design is incompatible with even driven concept
12:03.23DocScrutinizerHAL been invented for desktop PCs
12:03.39ShadowJKhal is dead now
12:03.52DocScrutinizerindeed, guess why ;-D
12:05.16DocScrutinizerevenT driven concept*
12:07.00*** join/#maemo WielkiTost (~dos@unaffiliated/dos1)
12:08.52*** join/#maemo dos1 (~dos@unaffiliated/dos1)
12:10.58villagerI don't think that's why HAL is dead... HAL does handle events, it can e.g. send dbus notifications when properties change (though the notification unfortunately does not say what *to*, it does say that it changed), and apps can listen, so there's obviously mechanisms for that
12:12.16DocScrutinizervillager: that's output side. input side - like hald-addon-foobar - seems unaware of any such event concept
12:12.51*** join/#maemo Sargun (~Sargun@atarack/Staff/Sargun)
12:13.30DocScrutinizervillager: but yes, you're right, it could get fixed without breaking basic HAL design
12:14.21DocScrutinizerand I agree pretty wholeheartedly about nonsensical lack of info regarding details of a change in HAL dbus msgs
12:14.30villagerDocScrutinizer: yeah, any lack of event seemed to me to be more like an implementation issue than a design issue
12:14.49*** join/#maemo dos1 (~dos@unaffiliated/dos1)
12:15.49villagerDocScrutinizer: from what I hear, HAL is dead mostly because it started to become a monolithic and unmaintainable beast (as well as a piece of crap)
12:16.02DocScrutinizerbitten me when I wrote that 4 liner gimmick for playswoosh when slider opened
12:19.34DocScrutinizervillager: http://talk.maemo.org/showpost.php?p=897443&postcount=14 , for nasty effects of HAL's dbus msgs missing state of element that changed
12:19.56DocScrutinizerI need to keep a local var to store old state, and compare that to sysfs
12:20.28DocScrutinizerI *could* also use HAL to query actual state
12:20.51DocScrutinizerbut, as mentioned above, I prefer to not touch HAL whenever avoidable
12:23.09DocScrutinizeridiot HAL sending a dbus msg "buttonpressed state has changed" - but it does NOT send HOW it changed
12:23.48*** join/#maemo LaoLang_cool (~LaoLang_c@221.226.175.141)
12:25.48*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
12:26.34freemangordonDocScrutinizer, care to write those HAL vars somewhere for further references
12:26.43freemangordonwiki, or wherever
12:26.48DocScrutinizerumm
12:27.02DocScrutinizerChanlog: http://mg.pov.lt/maemo-irclog
12:27.03*** join/#maemo dos1 (~dos@unaffiliated/dos1)
12:27.19freemangordonno, I was talking about some documentation :)
12:27.51DocScrutinizerI just looked up the MXR page Pali tossed, and found this one line 271
12:28.05DocScrutinizerwhat shall I document about that fact?
12:30.52Palifreemangordon, documentation is in file /usr/share/doc/hald-addon-bme/README.properties.gz
12:31.04Paliin deb package hald-addon-bme_0.0.17+0m5_armel.deb
12:31.04DocScrutinizerwiki page "souce line in HAL", content: "http://mxr.maemo.org/fremantle/source/hal/hald/linux/addons/addon-usb-cable.c:271" ?
12:31.16freemangordonPali, ok
12:31.41Palialso some info is on: https://gitorious.org/mer-toggles/hald-addon-bme/blobs/master/hald-addon-bme.c and https://gitorious.org/mer-toggles/hald-addon-smartq/blobs/master/hald-addon-smartq.c
12:36.25DocScrutinizerMEH https://gitorious.org/mer-toggles/hald-addon-smartq/blobs/master/hald-addon-smartq.c#line89
12:37.13freemangordonyeah, the same for bme in mer
12:37.24freemangordon1000ms poll interval
12:37.50DocScrutinizeryeah, https://gitorious.org/mer-toggles/hald-addon-bme/blobs/master/hald-addon-bme.c#line91
12:39.13DocScrutinizeranyway I'm MEHing on the missing getenv() line assigning _poll_interval a new value when we want sth different from " ~1000ms (default)"
12:39.50freemangordonwell, I don't want to comment on that sourec ;)
12:39.52DocScrutinizersince "(default)" suggests there has to be such line
12:39.53freemangordon*source
12:42.26DocScrutinizerbtw I guess getenv() returns empty string (or nullpointer) when env undef. You need a) catch that, and b) convert string to int in a segv safe way, for poll_int
12:42.43*** join/#maemo geaaru (~geaaru@host33-201-dynamic.50-79-r.retail.telecomitalia.it)
12:44.15freemangordonDocScrutinizer, do not forget I am a dveloper after all :P
12:44.22freemangordon*developer
12:44.26DocScrutinizer:-)
12:44.31DocScrutinizersorry, no offense
12:44.57DocScrutinizerjust correcting a omission I did
12:45.32*** join/#maemo spark666 (~spark666@92.86.186.16)
12:45.32*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
12:45.38*** join/#maemo rlinfati (~rlinfati@adsl-ull-9-142.42-151.net24.it)
12:45.50freemangordonI saw it, code alredy written
12:45.59DocScrutinizer:-D
12:46.48freemangordonaah, should be in seconds
12:50.45*** join/#maemo DocScrutinizer (~halley@openmoko/engineers/joerg)
13:00.40Palihacking HAM
13:00.59PaliI belive that current version in my git repo will be working now...
13:03.18DocScrutinizerPali: \o/
13:03.45Palineeds testing: https://gitorious.org/~pali/community-ssu/pali-hildon-application-manager
13:03.57DocScrutinizerI once looked into this unbearably obscure code that decides when to update, based on age of last update cache
13:04.58Palistupid scratchbox, it adding -mthumb
13:05.05vdvhow to know which hints does libnotify support?
13:05.16freemangordonPali, sorry for asking again the same stupid question, but what is supposed to be in uevent file?
13:05.21freemangordonfor bq
13:05.34DocScrutinizerPali: maybe you find a bug in that code, that makes HAM update after each single random user interaction
13:05.54freemangordonyeah, that bug is driving me nuts
13:06.01PaliPHYSDEVPATH=/class/i2c-adapter/i2c-2/2-0055
13:06.01PaliPHYSDEVBUS=i2c
13:06.01PaliPHYSDEVDRIVER=bq27x00-battery
13:06.01PaliPOWER_SUPPLY_NAME=bq27200-0
13:06.01PaliPOWER_SUPPLY_TYPE=Battery
13:06.01PaliPOWER_SUPPLY_STATUS=Discharging
13:06.04PaliPOWER_SUPPLY_PRESENT=1
13:06.06PaliPOWER_SUPPLY_VOLTAGE_NOW=3636000
13:06.08PaliPOWER_SUPPLY_CURRENT_NOW=436789
13:06.10PaliPOWER_SUPPLY_CAPACITY=48
13:06.13PaliPOWER_SUPPLY_TEMP=406
13:06.15PaliPOWER_SUPPLY_TIME_TO_EMPTY_NOW=4560
13:06.17PaliPOWER_SUPPLY_TIME_TO_EMPTY_AVG=4140
13:06.19PaliPOWER_SUPPLY_TECHNOLOGY=Li-ion
13:06.20DocScrutinizerPALI!!!!
13:06.21PaliPOWER_SUPPLY_CHARGE_FULL=1147398
13:06.23PaliPOWER_SUPPLY_CHARGE_NOW=551208
13:06.25*** mode/#maemo [+o DocScrutinizer] by ChanServ
13:06.26PaliPOWER_SUPPLY_CHARGE_FULL_DESIGN=2056320
13:06.27vdvPali, why don't you pastebin? :)
13:06.47Paliyes, I will do
13:06.56DocScrutinizeryay, one second from a kick
13:06.59*** mode/#maemo [-o DocScrutinizer] by ChanServ
13:07.08BCMMi don't think yelling at him will help when his IRC client is still finishing a paste
13:07.17DocScrutinizeryes
13:07.21DocScrutinizerthus the kick
13:09.16*** join/#maemo Zahra (~Zahra@unaffiliated/belendax)
13:10.02DocScrutinizerPOWER_SUPPLY_CHARGE_FULL_DESIGN=2056320  WTF??
13:11.16DocScrutinizera completely random selection of bq27200 values, some of which look even completely off resp in useless units
13:12.19PaliILMD register
13:12.48Palithat which is not configured correctly on n900
13:12.49DocScrutinizerraw
13:13.04DocScrutinizerhmm, possible
13:13.14DocScrutinizeranyway useless
13:13.24Paliyes, this value is useless
13:13.42DocScrutinizerwhile e.g. LMD is completely missing
13:13.45DocScrutinizeras is CI
13:14.37DocScrutinizeras is the highly useful set of values based on IDLE
13:15.42PaliLMD is POWER_SUPPLY_CHARGE_FULL
13:17.44*** join/#maemo jonne (~jonne@91.182.48.125)
13:17.46DocScrutinizers/IDLE/STANDBY/
13:17.47Paliif CI is invalid driver do not report any other values
13:20.03*** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net)
13:20.22DocScrutinizeras is cycle-count
13:21.00Palicycle-count is missing due 2.6.28
13:21.09Palibut is in upstream kernel
13:22.58ShadowJKcycle count and cycle count since learning is useful for guessing if caacity has been corrected
13:24.00DocScrutinizerbasically a driver shall export a comprehensive set of registers, "expanded" and corrected for proper units
13:25.18DocScrutinizerI suggest looking at output of http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2
13:26.46DocScrutinizereven that one missing the writable register access, for obvious reasons
13:27.11*** join/#maemo CodenameStrike-N (~Codenames@203.82.92.21)
13:27.53DocScrutinizerwe don't need the nifty calculator in bq27200, as we got a better one in CPU, but anyway you might want to write to the registers for doing other stuff - see bq27200 datasheet
13:29.21DocScrutinizerif you don't support all registers in expanded normalized form, you at very least should add a dump sysnode, to get a complete hex register dump
13:30.27*** join/#maemo lxp1 (~lxp@62-47-166-139.adsl.highway.telekom.at)
13:30.55DocScrutinizerso everybody is free to use his own userland tool like http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2 on that dump sysnode
13:32.26DocScrutinizerbq27200.ko is not only blocking bme access via I2C, but also i2cget tool. So bq27k-detail won't work when bq27200.ko got loaded, unless bq27200.ko exports a dump sysnode
13:32.38PaliDocScrutinizer, in kernel-power there is interface for that
13:33.22Paliuserspace library for LD_PRELOAD is here: https://code.launchpad.net/~pali/+junk/maemo_libbqioctl
13:35.50DocScrutinizererrrwut?
13:40.06PaliDocScrutinizer, do not remember? search in your history :-) http://mg.pov.lt/maemo-irclog/%23maemo.2011-09-30.log.html#t2011-09-30T13:55:01
13:41.04DocScrutinizerI know we pondered how to make bme work with bq27200.ko
13:41.57PaliI tested it with i2cget tool and worked
13:42.41DocScrutinizerbut AIUI: bq27200.ko is locking I2Cbus 2 chipaddr 0x55. This libbqioctl will intercept I2C calls to taht addr and redirect them to /sys/*/*/bq27200/<foobar>
13:44.30DocScrutinizerwhen bq27200.ko doesn't export cycle-count or STTE to sysfs, how is >libbqioctl i2cget -y 2 0x55 0x1c< going to work?
13:44.32Paliit redirect i2c ioctl calls to /dev/bq*
13:44.48Paliand /dev/bq* is character device created by bq kernel driver
13:45.04Paliand it handle any call
13:45.19Paliso make sure you do not ask for unknown register like BME :D
13:47.47DocScrutinizerso what you say is: >find /sys/devices/ -path '*/hdq/*' -name dump<  is now >find /dev  -name bq*<?
13:48.13*** join/#maemo Roomerlol (~Roomerlol@95-27-96-249.broadband.corbina.ru)
13:48.18*** join/#maemo jhb (~joerg@p4FEF5516.dip.t-dialin.net)
13:48.55*** join/#maemo FIQ (~FIQ@unaffiliated/fiq)
13:50.11DocScrutinizeras I'm not going to install a LD_PRELOAD lib for i2cget, to make a script like http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2 work
13:52.13*** join/#maemo NIN101 (~NIN@p5DD28488.dip0.t-ipconnect.de)
13:53.49DocScrutinizerif that'S what you say, I'd ask you to give me details so I can fix the script so it works on PK as well - *without* maemo_libbqioctl. And I'd ask you to test it on a system that already has bq27200.ko modprobed
13:54.52*** join/#maemo markinfo (~marek@dhcp13.dmg.tuwien.ac.at)
13:54.54*** join/#maemo trx (~ns-team@212.200.198.253)
13:56.18Paliyou need to build libbqioctl.so library
13:56.27DocScrutinizerWTF?
13:56.34Paliand then call i2cget like: LD_PRELOAD=./libbqioctl.so i2cget ....
13:56.42DocScrutinizerno way dude
13:57.22DocScrutinizerI want to do a pretty normal thing: read out a chip's complete register set. I'm not going to use a special library for that
13:57.53Palifirst check if bq module is loaded. if not use standard way
13:58.16DocScrutinizerif bq27200.ko doesn't alow access to all registers of bq27200 chip, it's buggy
13:58.17Paliif is loaded set export LD_PRELOAD=/path/to/libbqioctl.so
13:58.28Paliit allow access to all reigsters
13:58.44DocScrutinizerthat's BS
13:58.50DocScrutinizersorry
13:59.20DocScrutinizercat /dev/bq27200 is the supposedly right way
13:59.42DocScrutinizerif that's your direct access to chip registers now
14:00.20Palicat not working
14:00.25Paliit use ioctl
14:00.31Palilike /dev/i2c-*
14:00.33DocScrutinizerthen it's broken
14:00.46Paliwhat broken?
14:00.52Pali/dev/i2c-*?
14:01.05vdvanybody knows, whether sound utilities are accessable from qt? http://maemo.org/api_refs/5.0/5.0-final/hildon/hildon-Sound-Utilities.html
14:02.29DocScrutinizerlisten: a kernel driver is meant to allow *simple* *comprehensive* access to hardware
14:02.52DocScrutinizer*sigh*
14:03.01DocScrutinizertoldya bq27200.ko is crap
14:04.34Palitested, bq27200.sh working fine with library
14:04.43Palisudo sh -c "LD_PRELOAD=./libbqioctl.so ./bq27200.sh"
14:04.44DocScrutinizerif /dev/bq27200 is implementing a API ...
14:05.41DocScrutinizerDANG I don't give a flying shit about LD_PRELOADing a lib I ave to build and install on device, to do a *pretty* *normal* thing that worked before bq27200.ko messed up shit
14:06.59DocScrutinizerif /dev/bq27200 is implementing a API like /dev/I2C-2 then maybe we can symlink /dev/I2C-99 to /dev/I2C-2 and use i2cget -y 99 0x55...
14:09.28PaliI added this to top of file bq27200.sh: if [ -e /sys/class/power_supply/bq27200-0 ]; then export LD_PRELOAD=/home/user/libbqioctl.so; fi
14:09.51Paliit is not same api
14:10.08DocScrutinizerIOW a /dev/foobar device is udeless when there are no tools to access this device in a standard manner. LD_PRELOAD is *no* standard manner/tool
14:10.46Paliit is only for i2cget
14:10.58Palieasy way how to fix scripts using i2cget
14:11.03*** join/#maemo spark666 (~spark666@92.86.186.16)
14:11.03*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
14:11.17DocScrutinizerthis will never fly, nobody sane will accept a LD_PRELOAD to make a script work where you got the source of to fix it the rpoper way
14:11.34Paliat least see that code old (2011-08-02)
14:11.38*** join/#maemo em (~em@unaffiliated/emma)
14:11.57PaliI do not want to rewrite it now, no time for it
14:12.01Paliand is working
14:12.13DocScrutinizerif you define a new device in /dev, you as well need to provide the *proper* tools to access it. LD_PRELOAD=foobar i2cget is NO proper tool
14:12.42Paliin bzr is tool bqread.c
14:12.48Palifor that interface
14:12.51DocScrutinizerso I declare bq27200.kp buggy, same as it always been
14:13.31vdvfound, have to include <hildon-1/hildon/hildon-sound.h>
14:13.55DocScrutinizersince it's neither exporting all registers to sys, nor offers any standard alternative method to access those registers
14:16.03DocScrutinizerhonestly what's the common sense in inventing a /dev/bq27200 device that is neither accessable via standard >cat< nor compatible to /dev/I2C* ?
14:16.52DocScrutinizeris it compatible to *anything*
14:17.03DocScrutinizermaybe V4L2 interface?
14:17.06DocScrutinizer:-P
14:19.10*** join/#maemo acpi (~acpi@uber1.efence.co.uk)
14:20.44spark666DocScrutinizer: does it worth to give megoo a shot?
14:21.11DocScrutinizersuggested fix: export ALL registers to /sys/*/bq*/*
14:21.14spark666meego*
14:21.36DocScrutinizerspark666: I don't think so, but that's your beer
14:21.57spark666DocScrutinizer: i mean its more "linux" than maemo/
14:22.01spark666?
14:22.17DocScrutinizerit's less mature than maemo
14:22.33DocScrutinizermaemo is pretty much linux as much as it gets
14:22.56DocScrutinizerI mean, maemo is not android
14:23.01spark666yeah!
14:23.17spark666meego looks a bit like android from what i see :P
14:24.16spark666but does n950 run meego?or something else?
14:24.40DocScrutinizermaemo has some userland apps that rely on some /sys et al idiosyncrasies of this particular maemo kernel, which otherwise is a normal linux kernel also regarding those idiosyncrasies - at least 99.99%
14:25.12DocScrutinizerit's just you will break those APIs when you update to newer linux kernel versions
14:26.14DocScrutinizermeego otoh doesn't have those userland apps that require a special kernel land. Mostly because meego doesn't have *any* userland apps ;-P
14:26.30spark666hahahah :P
14:26.46spark666at least im happy that we have CSSU community
14:27.02spark666couse i see that nokia droped us :(
14:28.10DocScrutinizerwell, btw meego != meego
14:28.20spark666huh?
14:28.53DocScrutinizerthere's "true" meego, as in meego CE, and there's Harmattan "meego" which basically is Nokia's maemo rechristinaized
14:29.11spark666lol
14:29.11DocScrutinizerthe latter running on N9 and N950
14:29.30DocScrutinizermy comments above were about true meego
14:29.33spark666so the second meego its kinda maemo6?:P
14:29.38DocScrutinizeryes
14:29.58spark666so your opinion about the second its good,right?
14:30.10*** join/#maemo jpinx (~jpinx@trapper.beardy.se)
14:30.14DocScrutinizernot really
14:30.44DocScrutinizerit's again loaded with blob libs that are impossible to port to any other platform
14:30.55DocScrutinizerand it's almost more deadend than maemo5
14:31.03auenfmeego is more open than meego
14:31.04spark666lol
14:31.24spark666lets name them meego and meego 2 :P
14:31.40auenfmeego is more open than harmattan
14:31.48DocScrutinizernah, they are called meegoCE and HARM(attan)
14:31.58spark666:D
14:32.05auenfall maemos had quite a lot of closed source components
14:32.10auenfmeego would have fixed most of that
14:32.19DocScrutinizerHARM doesn't
14:32.31auenfharmattan is only meego by name
14:32.35spark666so meego CE its full opensource?
14:32.38DocScrutinizerindeed
14:32.48DocScrutinizerthough it's no proper maemo either
14:32.53spark666and its not made by nokia/
14:32.54spark666?
14:32.57DocScrutinizerat least in my book
14:33.16DocScrutinizerspark666: (meegoCE) yes
14:33.16auenfmeego was nokia & intel with a whole bunch of other minor input company
14:33.18auenfs
14:33.30DocScrutinizernow "continued" as nemo/mer
14:33.35spark666lol
14:33.55spark666i saw something about tizen to (even that i have no idea whats that) :P
14:34.05DocScrutinizersee #mer #nemomobile
14:34.29DocScrutinizertizen is intel's idea of meego's future
14:34.36DocScrutinizerAIUI
14:34.45spark666maemo its the best,and it would be even better if we hade all parts opensource,so ppl could develop more stuf for it
14:35.03DocScrutinizeryep
14:35.13auenfnokia wanted meego for arm
14:35.25auenfintel wanted to fight in the mobile arm war with x86
14:35.28DocScrutinizerthat's where CSSU and our arguments here about bq27200.ko come in
14:35.53spark666whats bq27200.ko is?
14:36.07DocScrutinizera kernel driver for the battery gauge chip
14:36.41spark666humm
14:36.52DocScrutinizerthat didn't exist in original maemo5 and that resulted in quite some troubles when we tried to augment the system at that end
14:37.42DocScrutinizeras this driver (again) conflicts with closed userland stuff, namely bme
14:38.00spark666that s**ks
14:38.01spark666:(
14:38.37DocScrutinizerwell, we found our way around that, we're just "fighting" for the best implementation still :-D
14:38.50spark666:>
14:38.57*** join/#maemo valerius (~user@85.26.180.130)
14:39.12*** join/#maemo Termana (Termana@199.127.226.8)
14:39.36spark666now im running the defaulf stuffs + cssu testing version
14:39.43DocScrutinizerbetter "fight" now, rather than moan later
14:39.55spark666its been more than a year since i had the last n900
14:39.56*** join/#maemo chadi (chadi@unaffiliated/chadi)
14:40.05spark666and i kinda forgot some stuffs
14:40.22spark666hahah nice words :D
14:40.40DocScrutinizeronce stuff is deployed, it's hard to change some details in some parts
14:41.11villagernoo, don't say "the last n900"
14:41.18DocScrutinizerso my part always is the bitching for the better
14:41.28spark666villager: the last that i had
14:41.35spark666now i buyed a new one :D:D:D
14:41.44DocScrutinizer*new*?
14:41.51spark666second hand :(
14:41.55DocScrutinizer:-/
14:42.08DocScrutinizerI'm looking for really new ones
14:42.11spark666the first that i had whas new more than 2 years ago
14:42.31spark666i payed 500 euros on that one
14:42.33villagerspark666: phew... will be a sad day when there's only one n900 left in the world
14:42.40spark666but now i dont have much money anymore :(
14:42.45DocScrutinizerI only have three devices, makes me kinda nervous ;-D
14:42.55spark666villager: we will fight for it :P
14:43.18spark666DocScrutinizer: wow :P your rich :P
14:43.27DocScrutinizernot at all :-)
14:43.32DocScrutinizerjust crazy
14:43.51spark666im crazy to
14:43.54spark666:P
14:44.44DocScrutinizerI'm less poor now than I've been half a year ago, but there's no more really unused new N900 available now :-/
14:45.00spark666im not a big fan of ubuntu,but if they will make ubuntu mobile version will be nice
14:45.04ThreeMsure there is
14:45.10ThreeMbut at a inhuman price
14:45.24DocScrutinizerwhere?
14:45.24ThreeMamazon what 599eur (in germany) for a new N900
14:45.27villagerhope they continue to sell replacement parts for a while, at least... I still haven't fixed my other n900, the one with the cracked lcd
14:45.34DocScrutinizero.O
14:45.37spark666in my country its still 500 euros in stores
14:45.56DocScrutinizervillager: spare parts getting rare as well
14:46.03ThreeMhttp://www.amazon.de/Nokia-Smartphone-Maemo-QWERTZ-Tastatur-black/dp/B002N2Z0MQ/ref=sr_1_1?ie=UTF8&qid=1335710754&sr=8-1
14:47.24DocScrutinizerhmmm
14:47.45*** join/#maemo cpt_nemo (cpt_nemo@rfc1459.de)
14:47.50DocScrutinizerwestcom, maybe this one isn't a sucker cheating his customers this time
15:02.35DocScrutinizerdid ebay nuke the "ask seller a question" function?
15:03.09ThreeMi hate ebay. some of the worst sites on the internet
15:03.16DocScrutinizersure
15:03.21DocScrutinizersame here
15:03.51ThreeMperiot im searching for functions... they are there but you have to serach for it
15:04.23DocScrutinizerI'd rather do bunjee jumping or play russian roulette, if that would get me a new N900
15:05.25ThreeMmy n900 is in pretty good condition
15:05.51ThreeMim lookging forward for the N9 but im still not sure to buy
15:06.29DocScrutinizeryou can have mine ;-) nah, not really
15:07.23DocScrutinizerit's a lend-out anyway, so I mustn't give it away
15:07.43ThreeMis the n) a good device?
15:07.49DocScrutinizerand actually last few weeks I started to look into hostmode for N9 again
15:07.55ThreeMa "like N900 good" device?
15:08.08DocScrutinizerdepends on what you expect
15:08.15DocScrutinizerHARM is no maemo anymore
15:08.40DocScrutinizerand the device never been an option for me, with crappy capacitive touchscreen and no hw-kbd
15:09.05ThreeMwhen this means i get no HAM... yea! ;)
15:09.07ThreeMhmm
15:09.27ThreeMdamn, im looking for a replacement for the N900 but still.... there is none
15:10.01DocScrutinizerthere definitely is none, otherwise I'd not ponder to buy new N900 for even astronomic price tags
15:10.09villagerimho, capacitive touchscreens should be outlawed
15:10.15DocScrutinizerindeed
15:11.10DocScrutinizermaybe one day Apple will do us the favour and claim they got all the patents on c-ts so nobody else may use it X-P
15:11.39ThreeM:)
15:11.45ThreeMi like them
15:11.52ThreeMon tablets
15:12.44DocScrutinizerso the sane 90% of industry (duh, did I write that?) could switch to really nice stuff, like Stantum http://www.youtube.com/watch?v=Bv3X5y-ajtc
15:13.04villagerI'm not going to buy any tablet or anything with a capacitive screen... I even hate the laptop's touchpad
15:14.39villagerI bought a n9 for the principle of it, but as a smartphone I use it as little as possible, the n900 has a much more comfortable resistive touchscreen
15:15.25ThreeMhmm what is more comfortable on a resistive ts?
15:16.11villagereverything, in my opinion... too bad the n900 doesn't have multitouch, but I think that's also possible on more advanced resistive screens
15:16.29DocScrutinizerit's WAAAAY more precide, and works with arbitrary objects you touch it
15:16.37DocScrutinizerprecise*
15:16.58DocScrutinizervillager: watch the youtube video!
15:17.13DocScrutinizeryou'll drool on your PC screen
15:17.16DocScrutinizer:-D
15:18.26DocScrutinizer(or n900 screen if you're watching it there :-D)
15:18.35villagerwith resistive, I can hit anything I want, also actually see what I'm hitting since my finger doesn't have to be in the way, I can use gloves or a stylus, and I don't get aches from hours of electric currents through my fingers
15:20.49DocScrutinizerc-ts has exactly one immanent advantage: it's more ruggedized by design. R-TS needs a somewhat flexible foil as cover, while C-TS can use even glass
15:21.53DocScrutinizeron absolutely every other discipline C-TS sucks competing to R-TS
15:22.53DocScrutinizerraindrops: R-TS check, C-TS BZZZZ
15:23.16DocScrutinizergloves, stylii: R-TS check, C-TS BZZZ
15:23.34*** join/#maemo BCMM (~ben@unaffiliated/bcmm)
15:23.40DocScrutinizeraccuracy: R-TS check, C-TS BZZZZZZZZ
15:24.21DocScrutinizermultitouch, R-TS check, C-TS check
15:26.52*** join/#maemo Macer (mace@scientiam.org)
15:27.05DocScrutinizereven sensibility and well defined activation: R-TS check (when done properly), C-TS BZZZZ (either acts on not-really-rouches since too sensible, or it decides to not really accept a touch at all)
15:28.41*** join/#maemo NIN101 (~NIN@p5DD28488.dip0.t-ipconnect.de)
15:28.54DocScrutinizeranother nice one of Stantum: http://www.youtube.com/watch?v=HnQHoCDxiRw&NR=1, 1:43 *awesome*
15:32.44freemangordonPali, ping
15:32.52Palifreemangordon, pong
15:33.17Palinow Integrating autodetection of charger to kernel-power for bq2415x_charger driver
15:33.21freemangordonPali, all hal entries are filled by someone when bq module is insmoded
15:33.48DocScrutinizerPali: you checked it against hostmode and general USB?
15:34.08PaliDocScrutinizer, I only export visible interface to bq module
15:34.22freemangordonso I am not sure what this is supposed to do (besides sending dbus signals)
15:34.31DocScrutinizerwell, that's enough to already break hostmode I guess
15:34.31freemangordoni mean hal-addon-bme
15:34.32Palilike dmesg messages: twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
15:35.27Palifreemangordon, what? someone is rewrting hal entries in hald-addnon-bme?
15:35.39freemangordonyep
15:35.52Palibut it is not possible
15:36.13Palidid you replaced original hald-addon-bme?
15:36.22freemangordonyep
15:36.26DocScrutinizerI toldya >cat /sys/devices/platform/musb_hdrc/vbus< invokes a function in kernel musb-hdrc that breaks USB data session
15:36.43freemangordonand the only thing I set so far is  battery.present
15:36.47PaliDocScrutinizer, I do not call ANY functions
15:37.08PaliI only store informations from dmesg
15:37.09DocScrutinizeractually not vbus
15:37.30DocScrutinizercat /sys/devices/platform/musb_hdrc/charge does
15:38.32DocScrutinizerwell, then you'll never learn about fastcharger, as the test in hw is only tiggered by reading this sysnode
15:38.59DocScrutinizerand that mustn't be done after you enabled hostmode
15:39.41DocScrutinizersighs and wishes some guys would talk to him a bit more
15:40.09PaliDocScrutinizer, when you enable hostmode bq2415x driver going to manual mode
15:40.13freemangordonApli, http://pastebin.com/GPXR1KJZ
15:40.19freemangordonPali ^^^
15:40.33Paliand then autodetection not working...
15:40.55DocScrutinizeruhuh
15:41.06DocScrutinizerand how do you detect "hostmode"?
15:41.42Palithat user enable hostmode via sysfs entry...
15:42.12DocScrutinizeryay, so I *really* wonder how you're going to solve those layering problems
15:42.29*** join/#maemo ced117[-] (~ced117@AStrasbourg-552-1-85-155.w92-141.abo.wanadoo.fr)
15:42.30*** join/#maemo ced117[-] (~ced117@opensuse/member/ced117)
15:42.53DocScrutinizeryou'll have to compile bq27200 as monolitic
15:43.00freemangordonerr, and what about hal addon?
15:43.24DocScrutinizerotherwise I fail to see how you hook into the syfs node of musb_hdrc to detect hostmode
15:44.02*** join/#maemo jluisn (~quassel@187.114.211.48)
15:47.43*** join/#maemo mase76 (~mase76@p5DD3BCBA.dip.t-dialin.net)
15:48.08DocScrutinizerPali: and honestly I fail to see how you'll make THAT kernel with bq24150 builtin to kernel compatible to stock rootfs that tries to start bme and will barf up when bme finds it can't conect to bq24150 anymore
15:49.00DocScrutinizeryou're definitely leaving maemo compatibility
15:49.46DocScrutinizeryou'll need userland patches to make KP work
15:50.03DocScrutinizeror rather, make userland work with KP
15:50.04Palino, bq* drivers will be always modules
15:50.09Palinot linked to kernel
15:50.29Paliall will be working...
15:50.37DocScrutinizerbut HOW?
15:50.39Paliwithout patching userspace
15:50.43Palihooks in board code
15:51.08Palifrom musb code is calling function in board code
15:51.28DocScrutinizerhmmm
15:51.35Paliand bq module register hook function from board code
15:51.55DocScrutinizersound story, though I never heard of it
15:52.01DocScrutinizermight actually work
15:55.58DocScrutinizerif that all pans out, it will be a nifty cute piece of software, and we'll dance on bme's grave :-D
15:58.30DocScrutinizeractually incredible - you can run on "stock" config (original BME and no bq27200.ko), you can load bq27200 and still get bme running on LD_PRELOAD maemo_libbqioctl, plus you can nuke bme completely and run system on bq27200.ko plus bq27150.ko
15:59.31DocScrutinizerI'd just really like to augment bq27200.ko to support *all* register the chip offers
15:59.40DocScrutinizerin /sys
16:00.26freemangordonand waht about battery calibration?
16:00.34freemangordonis it auto-calibrated?
16:00.42DocScrutinizerit never been
16:00.51DocScrutinizeryou need to run a learning cycle
16:01.02freemangordonso, how is that going to work?
16:01.27DocScrutinizeryou charge completely, then discharge completely
16:01.56DocScrutinizerwhen CI goes "0" your learning cycle got completed
16:03.04DocScrutinizerat least that's what bq27x00 does
16:03.28*** join/#maemo nsuffys (~NokiansFr@254.247.6.195.dynamic.adsl.abo.nordnet.fr)
16:03.49*** join/#maemo liar (~liar@clnet-p09-185.ikbnet.co.at)
16:03.49freemangordonthe question was - how (and where ) is that going to be integrated?
16:03.51DocScrutinizeralas it seems bq27200.ko tries to be overly smart and doesn't report anything when CI=1
16:04.29DocScrutinizerwhat? I don't want my device to randomly decide to completely deplete battery to complete a learning cycle
16:04.44DocScrutinizerit's user's very discretion to do that
16:05.11DocScrutinizerso probably no "integration"
16:05.27freemangordonbut without at least one calibration, bq module does not work properly
16:05.51DocScrutinizeryou're free to write a calibrator app that stops charging until CI=0
16:06.05freemangordonyeah
16:06.18DocScrutinizeryeah, that'S another point why bq27200.ko is broken
16:06.28DocScrutinizeralas it seems bq27200.ko tries to be overly smart and doesn't report anything when CI=1
16:06.39DocScrutinizer[/quote]
16:07.08freemangordonPali, back to my question, what is hald-addon-bme supposed to do besides sending dbus signals
16:07.37DocScrutinizerthis is not only unfortunate, it's utterly wrong, as CI=1 doesn't mean the values are bogus, it just means they are not *guaranteed* anymore
16:08.06freemangordonand one more thing, bme reports charge_level.current in unit bars, while bq module in mAh
16:08.42DocScrutinizerfor THAT you invent a nice function 100%->8bars :-D
16:08.56PaliDocScrutinizer, bq27200.ko do not report values if battery is not calibrated
16:09.04freemangordonbut that is already set in hal
16:09.11DocScrutinizerit's basically up to you and your taste what this function actually does
16:09.31DocScrutinizerPali: yes, and that's WRONG
16:09.37freemangordonDocScrutinizer, http://pastebin.com/GPXR1KJZ
16:09.46Paliand what should be correct?
16:10.01Palipaste is empty?
16:10.09DocScrutinizeralways report the values as seen in chip, only convert/normalize them
16:10.29freemangordonis not
16:11.06DocScrutinizerget a /sys/*/bq27200/CI_VALID that's either true or false, depending on CI
16:11.09Paliah, rekonq default kde borser is stupid...
16:11.35Palifreemangordon, that hal property is filled by HAL itself
16:11.44freemangordonyeah
16:11.56freemangordonwhat am I supposed to do?
16:12.04Paliignore it
16:12.13Palior copy values to BME udi
16:12.24freemangordonwhat?
16:12.37freemangordonyou mean to create a ned device?
16:12.41freemangordon*new
16:12.57Paliyou need to have hal device with BME name
16:13.13freemangordonhmm, let me check
16:13.18Paliand hald-addon-bme exports more properties
16:13.47freemangordonaah, ok, now i got it
16:13.52*** join/#maemo jluisn (~quassel@187.114.211.48)
16:14.31*** join/#maemo Tscheesy (~quassel@alfred.neversfelde.de)
16:17.03Palifreemangordon, I think it can be better to copy values from /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0 to hald-addon-bme
16:17.07DocScrutinizerPali: (and what should be correct?) see output of http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2. If all those values are showing up /sys/class/power_supply/bq27200-0 then the driver is somewhat complete, and it doesn't even need to bother about special treatment for CI=1
16:17.39freemangordonPali, does not kake sense, and I already made the parses :)
16:17.39DocScrutinizerit's raher HAL/whoever that may want to report about CI status
16:17.56Palifreemangordon, ok
16:18.19DocScrutinizers/report/care/
16:18.28*** join/#maemo GuySoft (~guysoft@109.226.48.6)
16:18.37Palibut power_supply interface does not support all those properties...
16:19.18DocScrutinizerwell, maybe that'S because bq27200 is not any kind of power-supply
16:19.39DocScrutinizerit's a battery GAUGE
16:21.29DocScrutinizerwhatever, there's no reason I'm aware of why you can't get a /sys/class/power_supply/bq27200-0/CI node
16:22.31DocScrutinizeras well as /sys/class/power_supply/bq27200-0/CYCL and  /sys/class/power_supply/bq27200-0/CYCT
16:22.42DocScrutinizerand a few others that are missing
16:23.34DocScrutinizerif HAL doesn't care about state of CI, what is most sensible thing to do? report capacity=0% always? or 100%?
16:24.04DocScrutinizeror simply report the probably still somewhat sane values from chip, even when CI=1
16:26.12PaliDocScrutinizer, ask that maintainers of battery-2.6.git tree
16:26.30DocScrutinizerno, I'm not going to do that
16:27.01DocScrutinizeras I'm not a meego guy that always answers "we're just using upstream"
16:28.20vdvanybody knows, how modest merges several subsequent notifications into one? it increases number of notifications instead of showing multiple popus http://imagebin.org/210268 ( i've marked with red number of notifications)
16:28.56vdvit's done here i think http://gitorious.org/community-ssu/modest/blobs/master/src/hildon2/modest-platform.c
16:29.03DocScrutinizerI made my point - get the missing registers/flags into  /sys/class/power_supply/bq27200-0/*, don't fake reported values based on (flase) assumtions what e.g. CI means
16:29.20vdvbut i can't find exact piece of code which does that
16:31.01DocScrutinizerIf I had to guess, I'd say modest cancels the old notification and sets up a new one instead
16:31.46*** join/#maemo dos1 (~dos@unaffiliated/dos1)
16:31.47vdvDocScrutinizer, most likely, but how to set that number?
16:31.58vdvi.e. for new notification it's always 1
16:32.12DocScrutinizererr, just concatenate it with your message string?
16:32.42DocScrutinizerooh, the notifier already has a dedicated integer parameter for that?
16:32.55vdvwhich one?
16:32.59vdvamount?
16:33.31DocScrutinizeror no parameter at all, while still showing a number that's *not* in notifier call's msg string?
16:34.21vdvyep
16:34.48vdvi.e. that number 2 in screenshot is not part of msg string
16:34.57DocScrutinizerI.E when you call the notification like notify("foobar") it actually displays "1 foobar" ?
16:35.06DocScrutinizermhm
16:35.10vdvyes
16:35.35DocScrutinizerso I guess it will increase that number for each subsequent call
16:35.36vdvand i can't find the way to set number of notifications
16:35.43villagervfv: line 1709 maybe?
16:36.29vdvvillager, 1709? modest_platform_remove_new_mail_notifications?
16:36.36*** join/#maemo liar (~liar@clnet-p09-185.ikbnet.co.at)
16:36.47villagervdv: yes looks to me like it cancels the old notifications
16:37.15vdvvillager, that is clear for me
16:37.38vdvi understand that modest cancels previous notification before displaying a new one
16:38.04vdvbut how it sets "number of notifications" for new notification?
16:38.25vdvvillager, look at screenshot
16:38.39vdvnumber marked with red
16:39.05vdvhow can i set that number for new notificaitons?
16:39.22vdvi can change title, icon, text
16:39.34vdvbut that number is always 1 for me
16:40.04villagervdv: is it line 1660?
16:40.13DocScrutinizernevertheless it seems to me there's no parameter for number of msgs to display in notifier
16:40.31DocScrutinizerg_object_get(G_OBJECT (notification), "id", &notif_id, NULL);  notifications_list = g_slist_prepend (notifications_list, GINT_TO_POINTER(notif_id));
16:40.39DocScrutinizeris probably doing the trick
16:41.14vdvvillager, i've tried that, but it has no effect
16:41.34vdvi.e. amount hint does something else
16:43.23vdvDocScrutinizer, that code just adds a notification to list, not?
16:43.45DocScrutinizer/* Set the number of new notifications */  notify_notification_set_hint_int32 (NOTIFY_NOTIFICATION (notification) "amount", g_list_length (URI_list));
16:43.58villagervdv: ok, what happens if you do open more than one hildon notification object?
16:44.18DocScrutinizer(1659)
16:44.48vdvDocScrutinizer, i also thought that it is exactly what i need
16:44.52vdvbut it's not
16:45.11DocScrutinizerI'd bet it is
16:45.13vdvvillager, i get two popus
16:45.33vdv*popups
16:45.49DocScrutinizervdv: probably only if you use a new  "id", &notif_id,
16:45.56villagervdv: according to the code, modest doesn't destroy the old popups, so maybe some of the parameters somehow convince hildon that it's from the same app
16:46.28DocScrutinizerid does that, in my world
16:46.56vdvDocScrutinizer, do you see also, whether new notification is created with old id?
16:47.26DocScrutinizernot yet, I only looked cursory at the code
16:47.27villagerDocScrutinizer: that code gets the id and stores it internally, it doesn't set it, I think
16:47.50vdvvillager, yes
16:48.01vdvvillager, with amout hint i do see that amount
16:48.04vdvbut
16:48.20DocScrutinizerI think if it doesn't reuse it, either for nuking the notification, or for sending an "update", it's a rather silly thing to store the id at all. no?
16:48.22vdvnot on the place which i've pointed on screenshot
16:48.45villagerDocScrutinizer: it nukes them from another function, but not sure when exactly
16:49.39villagerI don't use modest so not sure when it usually does that
16:49.43vdvvillager, i see the setted number of notifications in small popup which appears at the top near the clock
16:49.53DocScrutinizersimple approach: run modest under gdb, see what it actually does
16:50.23DocScrutinizerwhen increasing the number of msgs in notification
16:50.48*** join/#maemo mase_76 (~mase76@p5DD3A60E.dip.t-dialin.net)
16:51.13vdvok, thanks anyway for hints
16:52.49DocScrutinizeror, even simpler, use dbus-monitir
16:53.14DocScrutinizeras I gaher the notifications are handled via dbus interface by hildon-*
16:53.19DocScrutinizergather*
17:01.47*** join/#maemo dos1 (~dos@unaffiliated/dos1)
17:02.04DocScrutinizeranyway, Set the number of new notifications */  notify_notification_set_hint_int32 (NOTIFY_NOTIFICATION (notification) "amount", g_list_length (URI_list));  is just clear enough
17:04.29vdvyes, but it doesn't work, i've tried
17:08.08vdvDocScrutinizer, do you also understand comment on line 1644?
17:08.33vdvit says it sets the led pattern, but hint "time" is setted
17:08.42*** join/#maemo valerius (~user@95.153.189.107)
17:09.39DocScrutinizer1651
17:09.52vdvDocScrutinizer, is that normal, that i have two processes named modest in output of ps ax?
17:10.21vdvDocScrutinizer, yes, but comment is above another line
17:10.44vdvnot 1651, which actually sets led pattern
17:15.57villagerit's not that mysterious... programmers shuffle code around without remembering to update the comments all the time
17:17.53villagermany programmers seem to have developed comment-blindness
17:18.14vdvvillager, correct, that's why i'm not trusting to other comments too
17:21.27*** join/#maemo sq-one (~sq-one@p54A1FD3B.dip.t-dialin.net)
17:37.42*** join/#maemo valerius (~user@85.26.180.130)
17:44.55*** join/#maemo ferdna (~ferdna@cpe-67-10-220-35.elp.res.rr.com)
17:45.44Palipatched kernel with autocharger mode for bq2415x not working...
17:45.53Paliit boots to bootmenu
17:46.08Paliand after booting real /sbin/init black screen and reboot
17:46.24Paligiving up today
17:46.37Palipatch on top of kernel-power is here: http://atrey.karlin.mff.cuni.cz/~pali/bq2415x/0001-Added-bq2415x-driver.patch
17:47.32Pali(driver is really blacklisted)
17:53.36Paliin /dev/mtd2 is no error output (all dumps are for other kernel version strings)
17:56.07*** join/#maemo Itschue (~Itschue@p54B4CDD2.dip.t-dialin.net)
17:56.41Itschuehello
17:57.02freemangordonPali, what is POWER_SUPPLY_CAPACITY?
17:57.14Palicapacity in %
17:57.17Itschueafter flashing emmc and than flashing rootsfs device is booting
17:57.26freemangordonyou mean the charge in %?
17:57.40Paliyes
17:57.43Itschuei think all is ok but i will be 100%sure if all is really correct   how can i check this
17:57.46freemangordonok, thanks
17:59.14Itschueca someone please help me
18:02.17DocScrutinizervdv: the first uint32 you're passing to the call is 0 in this example: http://wiki.maemo.org/Phone_control#Make_an_.22Email_Style.22_notification_dialog
18:03.04DocScrutinizerthe point is it's NOT 0 on system's reply to the call, instead it holds a handle to the notification
18:03.43DocScrutinizerif you call same dbus call again, with this very ID / handle, it does NOT open a new notifier
18:03.59Itschuedocscutinizer is this for me?
18:04.06DocScrutinizeralas I was not able to set the amount value in dbus-send
18:04.20DocScrutinizerItschue: to vdv
18:04.36Itschueok did you read my question ?
18:04.55vdvDocScrutinizer, hmm
18:05.09vdvi've tried that before, as i was in python
18:05.23vdvdon't remember whether i worked or not
18:05.34vdvnow i'm on c++/qt
18:05.49DocScrutinizervdv: so I'd bet when you set BOTH the "amount" AND the "id" it shall just add the number of msgs
18:06.08vdvand seems c/c++ api doesn't allow to set id
18:07.19*** join/#maemo cityLights (~cityLight@bzq-82-81-7-28.red.bezeqint.net)
18:07.26DocScrutinizermeh, obviously there's a way to do it, and modest does
18:09.04DocScrutinizerItschue: test the device, use it, see if there are problems
18:09.15DocScrutinizerwhat do you expect to go awry?
18:10.12Itschueto go awry?
18:10.32DocScrutinizerwhy are you not 100% sure ?
18:10.48DocScrutinizerare you searching for problems?
18:11.06Itschuethe flasher doesnt say "device successfully flashed" after flashing emmc
18:11.15DocScrutinizerhmmm
18:11.23DocScrutinizerdoes it return?
18:11.42DocScrutinizerdoes it print an error message?
18:11.47Itschueno
18:11.55Itschueno error message
18:12.04DocScrutinizerthen I bet everything is fine
18:12.43DocScrutinizerjust check content of MyDocs, if there is something left over from before you flashed
18:12.43Itschuehmm but i have the same problem as before flashing
18:13.05DocScrutinizer*sigh*
18:13.20DocScrutinizerwill you ever tell us what that problem is?
18:15.25Itschueyes first mydocs looks fine there are no files from me
18:15.27DocScrutinizerI guess your original question wasn't " i will be 100%sure if all is really correct   how can i check this" anyway
18:16.14DocScrutinizerso why don't you simply state your problem, tell us you just flashed and that didn't help?
18:16.25Itschueproblem is i start application mannager and when he check for updates it takes very long time and he cant connect to all repos
18:16.40DocScrutinizerthat's normal
18:17.26DocScrutinizersometimes some of the repos are simply not online, or messed up. And HAM err Hildon App Manager is notorious for being *very* slow
18:17.44DocScrutinizeryou shouldn't keep extras-devel enabled by al means
18:18.03Itschuei had problems to connecting to the nokia repos
18:18.11*** join/#maemo flo_lap (~fuchs@sign-4db6b2bc.pool.mediaWays.net)
18:18.12*** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian)
18:18.18Paliaaaaaa, I forgot to run depmod - reason why kernel does not boot
18:18.26DocScrutinizerhaha
18:18.28Palistupid
18:18.33DocScrutinizer;-P
18:18.43Itschuei know tha ham is very slow
18:18.49DocScrutinizerprods Pali
18:18.50Itschuebut this problem i never had
18:19.12DocScrutinizerItschue: see my explanation above
18:19.31*** join/#maemo r00t|n900 (~r00t@82.113.121.181)
18:19.43DocScrutinizersometimes the repos are messed up, try again tomorrow, if problem persists, come back for getting help
18:19.55Itschuewhen i decativate extras devel ham connect to nokia repos?
18:20.09Itschueproblem persists since yesterday
18:20.10DocScrutinizerreposa are known for acting up occasionally, especially on weekends
18:20.54DocScrutinizerhave you changed anything yesterday?
18:21.30DocScrutinizerif not, then wait for problem to vanish tomorrow, just like it apeared yesterday
18:21.48Itschuei also did apt-get update in terminal. there its very slow to. on some repo links was an "ign"
18:22.02*** join/#maemo piggz (~piggz@host-92-18-186-45.as13285.net)
18:22.03*** join/#maemo e-yes (~e-yes@94.45.180.138)
18:22.14DocScrutinizeryes, see above
18:23.39DocScrutinizer"ign" probably means "ignored" -> problems with the repo. If you haven't changed anything in HAM catalog settings, it's a problem on internet side. Nothing you can do
18:24.30Itschuecan it be a problem with the router or the internet ip address
18:24.55DocScrutinizernope, as long as you can get any connection to internet from device
18:24.56Itschuebecause im by my aunt and not @home. @home i never had problems like this
18:25.15DocScrutinizercan you use browser?
18:25.42SpeedEvilI've not been using my n900 to share wifi. What's the recommended 3G-wifi bridge? I want to connect my cheap android tablet to it.
18:25.56Itschuecan start browse and browser loading inet site too
18:26.12DocScrutinizerSpeedEvil: mameo hotspot?
18:26.30DocScrutinizerItschue: repo defect, see above
18:26.42DocScrutinizerwait for Nokia fixing it
18:26.59*** join/#maemo ALoGeNo (~alogeno@unaffiliated/alogeno)
18:27.19SpeedEvilk
18:27.45DocScrutinizer(if it's related to your aunt's WLAN you probably can't fix it anyway, so better just wait for monday)
18:28.30Itschuetommorrow im at home problem is here by my aunt the mbile network isnt good
18:28.52DocScrutinizeryes, we all understood quite well
18:29.01Itschueor ist it an unfortunate coincidence
18:29.06DocScrutinizerthe advice won't change though
18:30.52*** join/#maemo uen (~uen@p5DCB3292.dip.t-dialin.net)
18:34.14Itschue:(
18:36.56DocScrutinizerwhat does HAM show when you select "catalogs" in menu?
18:37.56DocScrutinizersome of the repos are probably marked as having problems, you can check the details of the problem when you click on it
18:39.12*** join/#maemo spark666 (~spark666@92.86.186.16)
18:39.13*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
18:41.51Itschuemom docscrutnizer i must wait until i can see it on the n900
18:41.57*** join/#maemo sq-one (~sq-one@p54A1FD3B.dip.t-dialin.net)
18:43.30DocScrutinizeranyway since you reflashed and thus the settings for the repos are quite probably ok, there's basically nothing we can do for you
18:43.34*** join/#maemo Dynamit (~alexander@s203h74o2nst4.dyn.tyfon.se)
18:44.31DocScrutinizerno matter if Nokia's repo server or your auntie's WLAN is the culprit
18:44.38Itschueits curious now there isnt any error
18:45.15Itschuei think its my aunties wlan its an speedport router from german telekom :(
18:45.20Itschuei hate these routers
18:45.40Itschueat home i have a good linksys router
18:45.55DocScrutinizerso how can we help? send some punching ball to treat?
18:46.29*** join/#maemo kthomas_vh_ (~kthomas@c-107-3-244-159.hsd1.tn.comcast.net)
18:46.31Itschuenow there were no errors shon in ham
18:46.33DocScrutinizerI'm not inclined to discuss pros and cons of telekom branded speedport routers
18:46.43Itschueyesterday i had seen an error text in red
18:47.01DocScrutinizeryes, we all have seen this, dozens of times
18:47.09Itschueat the moment ham is checking updates
18:47.41Itschuei see it only along time ago because i typed the correct link
18:47.44DocScrutinizerI'm getting tired
18:48.37Itschuefrom my problem?
18:49.09DocScrutinizerhttp://talk.maemo.org/archive/index.php/t-74220.html
18:49.16DocScrutinizeryes
18:49.36Itschuewe stop it now
18:49.43Itschuei check it tomorrow at home
18:50.15Itschuean when i have the problem tomorrow at home than i have a big problem
18:50.26Itschuei think at home will be all fine
18:50.33*** join/#maemo kthomas (~kthomas@c-107-3-244-159.hsd1.tn.comcast.net)
18:54.56*** join/#maemo Soder (~Soder@53.96.227.87.static.vx.siw.siwnet.net)
18:59.09DocScrutinizerI thought you just found it works even where you are right now?
18:59.41DocScrutinizer[2012-04-29 20:47:09] <Itschue> at the moment ham is checking updates
18:59.59DocScrutinizerso why the heck should there any problems tomorrow?
19:00.08DocScrutinizershould there be*
19:00.45*** join/#maemo Itschue|2 (~Itschue@p54B4CDD2.dip.t-dialin.net)
19:00.53Itschue|2back
19:01.05DocScrutinizerrepo (or telekom DNS, or whatever) fixed itself, problem identified as transient non-issue
19:02.30DocScrutinizerPali: depmod helped?
19:02.41Paliyes
19:02.52Palipluged, unpluged detection working
19:02.56DocScrutinizerso it's "working"??? :-o
19:02.59Paliand battery is charging :-)
19:03.01DocScrutinizerWOW!
19:03.18DocScrutinizerhands Pali a lollipop
19:03.32Palinow I must thinging about wall charger and usb charger correct detection
19:04.05DocScrutinizerUSB host charger is absolutely nontrivial, and clearly a userland thing
19:04.25DocScrutinizerand probably so is fastcharger detection
19:04.49DocScrutinizersince you want to check for fastcharger only if ENUM fails
19:05.15freemangordonPali, congrats
19:05.26freemangordon:)
19:07.02DocScrutinizerjust wonders how to swap hald-addon-bme during running system
19:07.18DocScrutinizerto switch from bme to bq24150.ko
19:07.42DocScrutinizernot exactly trivial
19:08.26freemangordonif you find a way I will owe you a beer
19:08.49freemangordoni am restarting the device everytime a need to test a new version :)
19:09.04DocScrutinizerfreemangordon: maybe your hald-addon-bme replacement needs a fallback to original implementation on certain signals that bq24150.ko doesn't provide the needed info
19:11.08*** join/#maemo kerio92 (~kerio@unaffiliated/kerio)
19:11.08DocScrutinizerfreemangordon: well you could try initctl restart hal
19:11.11*** join/#maemo dos1 (~dos@unaffiliated/dos1)
19:11.20freemangordonhal restart does not help
19:11.33*** join/#maemo tuho (~t@a88-113-32-12.elisa-laajakaista.fi)
19:11.34DocScrutinizerbut I'm afraid hal is so central a conponent that this will make whole device reboot
19:11.39freemangordonwell, i am dount /etc/init.d/hal restart, but it should be the same
19:11.50freemangordon*doing
19:11.50DocScrutinizernope
19:12.02DocScrutinizermaybe not
19:12.05freemangordonsure? ok, let me try
19:13.26freemangordoninstant reboot :)
19:13.44DocScrutinizertoldya
19:14.09*** join/#maemo jluisn (~quassel@187.114.211.48)
19:14.31DocScrutinizeryou'll have to implement this fallback all across your code
19:14.48DocScrutinizerfoo(){
19:15.24DocScrutinizerif bq24150-works a;
19:15.38DocScrutinizerelse fallback-to-original;
19:15.57DocScrutinizer}
19:18.48*** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ffdec300-4.dhcp.inet.fi)
19:21.25*** part/#maemo SpacedOut (david@SubSpace.fries.net)
19:28.56Itschue|2docscrutinizer  "resolving host timed out"
19:29.18Macerkind of sucks no longer being able to fully use my n900
19:29.25Maceri'm using it like a damn nit lol
19:29.34Macerwhat a waste
19:32.18*** join/#maemo koo4 (~koo@98.82.broadband5.iol.cz)
19:32.39SpeedEvil:/
19:32.57*** join/#maemo valerius (~user@85.26.180.130)
19:40.51*** join/#maemo swc|666 (~goldbond@Aircrack-NG/Friend)
19:46.29vdvDocScrutinizer, found the reason
19:46.49vdvDocScrutinizer, title must be same
19:47.00vdvtitle of the notification
19:47.12vdvand same id also
19:48.36vdvand "amount" hint
19:50.12DocScrutinizervdv: toldya
19:50.50DocScrutinizeryou send exactly same message again, just with updated ID and amount
19:52.14vdvhmm.. just tested with different id's
19:52.18vdvand it also works
19:52.33vdvso, message title must be same
19:52.39vdvand amount must be set to one
19:52.53DocScrutinizererr, definitely not
19:53.03vdvjust tested
19:53.08vdvi print out id's
19:53.14DocScrutinizeramount is set as number of new msgs to add to the already signalled ones
19:53.20vdvfor two subsequent notifications
19:53.45vdvDocScrutinizer, yes, amount is a number to add
19:54.03DocScrutinizerif this doesn't work then there's a bug in this API and another one in modest
19:54.12vdvif there was one notification, and i create a new notification with "amount = 2", then i get three
19:54.23DocScrutinizeryep
19:54.42vdvso, it works as you said
19:54.48vdvjust id's must not be same
19:54.56DocScrutinizerstrange
19:55.05vdvi.e. they can be same or not
19:55.12vdvno effect on result
19:55.13DocScrutinizerI dunno what's that first integer in dbus msg
19:55.21DocScrutinizerI just see it's an integer
19:55.27vdvit's really id of the notification
19:55.36vdvand maybe it's used in some way
19:55.58vdvfor example, to reference later to the specific notification
19:56.05vdvhide it, or show it again
19:59.20DocScrutinizer>>> interface.Notify('Notification', 555, 'control_bluetooth_paired', 'Testing 123', 'Hello World', [], {}, 0)
19:59.21DocScrutinizer##method call sender=:1.310 -> dest=:1.28 serial=19 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=Notify
19:59.23DocScrutinizer<PROTECTED>
19:59.24DocScrutinizer<PROTECTED>
19:59.41DocScrutinizerreturns:
20:00.23DocScrutinizermethod return sender=:1.28 -> dest=:1.310 reply_serial=19
20:00.25DocScrutinizer<PROTECTED>
20:00.26DocScrutinizerdbus.UInt32(18L)....
20:00.54DocScrutinizernow I can send as many  interface.Notify('Notification', 18... as I want
20:01.03DocScrutinizerit won't open new requester
20:01.23DocScrutinizerso "18" is what I called handle or ID
20:03.02*** join/#maemo nox- (noident@p579010B4.dip.t-dialin.net)
20:03.05*** join/#maemo nox- (noident@freebsd/developer/nox)
20:05.39*** join/#maemo e-yes (~e-yes@94.45.180.138)
20:07.15*** join/#maemo lbt (~david@Maemo/community/contributor/lbt)
20:07.50*** join/#maemo teotwaki_ (~slau@Maemo/community/contributor/crashanddie)
20:07.51DocScrutinizervdv: http://paste.debian.net/166597/
20:10.05villagersure it's the id, but you don't need to set it to the id of the previous notification, keep in mind that modest doesn't do that either
20:13.36freemangordonPali, after battery change bq module is reporting total nonsense POWER_SUPPLY_CHARGE_NOW=0
20:14.27Palifreemangordon, try to cat /sys/class/..../bq2.../charge_now
20:15.00freemangordonstill 0
20:15.31freemangordonWTF?
20:15.43DocScrutinizervdv: see my pastebin, it's wxactly what happened there - when I don't set the id to the returned value, it opens a new notifier
20:16.47DocScrutinizerIt opens a new notifier for any integre it put there, except when that integer is a handle to an existing notifier
20:17.30DocScrutinizerooops, villager ^^^
20:18.38DocScrutinizerfreemangordon: CI=1
20:18.58DocScrutinizerI already elaborated on this being a bug in bq27200.ko
20:19.08freemangordonso? no charge?
20:19.11freemangordonmeh
20:19.52DocScrutinizerI actually elaborated about it in epic length
20:21.02DocScrutinizer[2012-04-29 18:23:33] <DocScrutinizer> if HAL doesn't care about state of CI, what is most sensible thing to do? report capacity=0% always? or 100%?  [2012-04-29 18:24:03] <DocScrutinizer> or simply report the probably still somewhat sane values from chip, even when CI=1
20:21.36*** join/#maemo valerius (~user@85.26.180.130)
20:21.56DocScrutinizero/
20:22.01DocScrutinizeroff for dinner
20:22.52*** join/#maemo trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623)
20:23.00*** join/#maemo Kilroo1 (~Kilroo@cpe-098-026-200-222.triad.res.rr.com)
20:24.21villagerDocScrutinizer: perhaps the way you're calling it, but that's almost certainly not the way vdv or modest is doing it... for example, the id would be set to 0 for new notifications, not some random number, and hints such as "amount" etc are set (not sure which hints vdv found were needed for this to work)
20:27.54vdvDocScrutinizer, villager: in order to combine several notification objects into one (with different or same id's) i had to 1) set "amount" hint and 2) set same title for both
20:28.34*** join/#maemo zeq (~s_j_newbu@2a01:348:1e3:1:e6ec:10ff:fe9a:d418)
20:28.50villagerand the "amount" hint is not set in that pastebin thing
20:30.03villagerI think you would replace [], {} with [], {"amount": 1} or something
20:32.30villagerthis is probably some dirty hack that nokia made anyway, not really clean design
20:33.42villagerideally it probably should have worked like Doc says, but...
20:34.44DocScrutinizer51but you're missing the point of what I said
20:35.04DocScrutinizer51damn roaming
20:35.29DocScrutinizer51villager: I'm not a fool, and I for sure wouldn't decide to instantiate a new dialog 'with any random number for ID'
20:35.34DocScrutinizer51I'm well aware that 0 is the only valid 'id' value to request a new dialog
20:35.36DocScrutinizer51but you're missing the point of what I said
20:35.40DocScrutinizer51damn roaming
20:37.16DocScrutinizer51and yes, probably we're supposed to set amount hint to a non-0 value
20:37.44*** join/#maemo vblazquez (~vic@35.41.15.37.dynamic.jazztel.es)
20:38.02vdvDocScrutinizer, and maybe also use "update" feature
20:38.15DocScrutinizer51just I was too lazy to find out about 'or something'
20:38.21vdvit's possible to update text and icon of execsting notification
20:38.46DocScrutinizer51sounds reasonable, yes
20:38.49villagerDocScrutinizer51: well, try that "amount" thing then
20:39.05DocScrutinizer51why?
20:39.17DocScrutinizer51I don't need the whole cruft
20:39.27DocScrutinizer51I just checked it for vdv
20:39.33vdv:)
20:39.58vdvvillager, and i've already get what i wanted, actually
20:40.01villagerDocScrutinizer51: as otherwise your pastebin shows you've missed the point?
20:40.04vdvgot
20:40.14villagerwell, doesn't matter, vdv is happy
20:40.16DocScrutinizer51pfff
20:40.34villagerI'm not really in the arguing mood
20:40.34vdvyep :)
20:40.45DocScrutinizer51me neither
20:41.02vdvthanks a lot
20:41.12DocScrutinizer51yw
20:41.35DocScrutinizer51was intriguing, I admit
20:42.14DocScrutinizer51so I just did it to make sure my advice wasn't utter BS
20:49.15*** join/#maemo mase76 (~mase76@p5DD3A60E.dip.t-dialin.net)
20:51.47*** join/#maemo valerius (~user@85.26.180.130)
20:53.58DocScrutinizer51villager: I even could figure a sane developer would check for other details of msg when and only when id=0, to allow some error tolerance
20:55.32DocScrutinizer51and of course such an API would handle id!=0 as 0 if no such id is actually in use
20:56.13DocScrutinizer51that's why my 'random id' worked like I wouldve used 0
21:01.30freemangordonDocScrutinizer, Pali, https://gitorious.org/hald-addon-bme/hald-addon-bme
21:01.40Palinice
21:01.53freemangordonnot complete of course
21:02.16DocScrutinizer51sorry, on n900
21:02.31freemangordonbut as a start should be enough
21:05.18freemangordonPali, is there anything to to to force bq module to report non-zero charge (besides calibration cycle)?
21:05.31Palipatch it
21:05.34freemangordons/to to to/to do to/
21:05.41freemangordonyeah, nice
21:06.17freemangordonBut it seems this is a readout from the chip, ain't?
21:07.44*** join/#maemo spark666 (~spark666@92.86.186.16)
21:07.44*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
21:08.07merlin1991hm silly question, how do I write a regex to check for a-z except for a few?
21:08.27DocScrutinizer51freemangordon: nope
21:08.49merlin1991is there a syntax for this caracter class minus xyz?
21:09.12DocScrutinizer51it's an atrificial intentional bug introduced by oversmart bq27200.ko
21:09.22DocScrutinizer51aiui
21:09.37DocScrutinizer51chip doesn't do that nonsense
21:11.01DocScrutinizer51merlin1991: either [^xyz]
21:11.15merlin1991well that allows anything but xyz
21:11.27merlin1991but I'd like todo a-z but not b e and o
21:11.49DocScrutinizer51or [A-Wa-w]
21:11.49merlin1991ofc I can type it out :D
21:12.25DocScrutinizer51yes, you'll have to
21:12.48DocScrutinizer51there's no set subtractor afaik
21:13.53merlin1991:/
21:14.33DocScrutinizer51[acdf-np-z]
21:15.23DocScrutinizer51i dunno of any nicer term
21:16.19*** join/#maemo GNUton-BNC (~gnuton@80-186-75-113.elisa-mobile.fi)
21:18.15*** join/#maemo spark666 (~spark666@92.86.186.16)
21:18.15*** join/#maemo spark666 (~spark666@unaffiliated/spark666)
21:19.18DocScrutinizer51maybe inverted logic: [^_-Zbeo*-]
21:21.48DocScrutinizer51I'm not sure sth like [^-k] would actually catch and forbid all from very beginning up to k
21:22.18DocScrutinizer51I rather guess that forbids just - and k
21:24.00DocScrutinizer51also I don't think there's any & analog to | in regex
21:27.02DocScrutinizer51kde had a nice regex wizard, I think in konqueror multi-rename or sth
21:27.35DocScrutinizer51merlin1991: ^
21:29.57*** join/#maemo Vib3 (~Vibe@gateway/tor-sasl/vib3)
21:59.22Palifreemangordon, DocScrutinizer, here bq2415x patch for kp50: http://atrey.karlin.mff.cuni.cz/~pali/bq2415x/0001-Added-bq2415x-driver.patch
21:59.36Paliwallcharger detection does not working correctly yet
22:00.05Palineed to call: cat /sys/devices/platform/musb_hdrc/charger
22:05.30DocScrutinizertoldya
22:06.05DocScrutinizerthe detection function in musb and hw is triggered only when you cat that sysnode
22:06.33DocScrutinizeranyway, nice work, worth even another lollipop :-D
22:07.42DocScrutinizer(cat sysnode) a thing usually done by ke-recv aiui
22:08.51DocScrutinizeror by bme itself, or knows-the-flying-spaghettimonszer-whom
22:08.58PaliDocScrutinizer, it will work, but I need to wait 1-2s
22:09.11Paliso some delay is needed
22:09.52DocScrutinizeryeah, the delay to allow ke-recv do its job
22:10.11Paligoing offline now, bye all
22:10.16DocScrutinizeror hal, or (see above)
22:10.25DocScrutinizerbye Pali
22:11.05vdvwhat does category mean for a notification in maemo? http://developer-next.gnome.org/libnotify/0.7/NotifyNotification.html#notify-notification-set-category
22:11.21DocScrutinizerprolly the icon used
22:11.40vdvif i set "email-message" category for new notification i get behaviour of modest automatically
22:12.08vdvbehavior = led pattern, sound, notification counter
22:12.10DocScrutinizerdang, don't ask me
22:12.12DocScrutinizer:-D
22:12.48DocScrutinizermaybe some sorta meta-macro
22:12.50vdvit's very interesting where is that defined
22:13.03DocScrutinizerGod knows
22:13.12vdv:)
22:13.33vdvand whether i'm allowed to use it
22:13.47DocScrutinizer"when I wrote that code, only God and me knew what I was doing - now only God knows"
22:14.34DocScrutinizero/
22:14.52vdvi've killed modest, thought, that category behaviour is defined by modest at runtime
22:15.30vdvDocScrutinizer, http://gitorious.org/community-ssu/modest/blobs/master/src/hildon2/modest-platform.c#line1630
22:16.21vdvit's all like a magic
22:17.18vdvmeaning of "category" is not documented
22:18.22*** join/#maemo robink_ (~quassel@fatcat.creosotehill.org)
22:22.27DocScrutinizer51vdv: that's defined somewhere in the abyss of hildon-notification-daemon or sth
22:24.44vdvit's interesting, whether it's standard, or added by modest
22:25.05vdvand if uninstalling modest will remove that category too
22:25.46*** join/#maemo Macor (macer@lasziv.reprehensible.net)
22:30.43*** join/#maemo teotwaki_ (~slau@Maemo/community/contributor/crashanddie)
22:38.52*** join/#maemo GuySoft (~guysoft@109.226.25.121)
22:40.04*** join/#maemo dimw1t (~atlas@71-13-79-30.static.aldl.mi.charter.com)
22:51.22*** join/#maemo Jooles (~Jooles@02dbe00c.bb.sky.com)
22:56.40*** join/#maemo sirdancealot (~sirdancea@98.82.broadband5.iol.cz)
22:57.16vdv/etc/hildon-desktop/notification-groups.conf
23:09.13*** join/#maemo Vanadis (~Vanadis@178-83-10-90.dynamic.hispeed.ch)
23:10.09*** join/#maemo valdyn (~valdyn@valdyn.org)
23:19.29topobotAre there any companies developing smartphones with maemo?
23:21.37GeneralAntillestopobot, no. Maemo's not being developed commercially any longer.
23:21.58topobotwhich is the last smartphone with maemo?
23:24.51SpeedEvilThe n900
23:25.05topobotoh
23:25.07SpeedEvilWell - arguably the n9
23:25.12topobotis it good the n900?
23:25.17SpeedEvilYes.
23:25.21SpeedEvilBut it's two years old.
23:25.21topobotor is it better iphone?
23:25.27SpeedEvilClosing on three.
23:25.54topobotis there any benefit in comparation with iphone or galaxy?
23:26.18SpeedEvilAt the moment - for 99.9% of users, no.
23:26.44topobotwhy?
23:26.58*** join/#maemo otep (~quassel@AP-203.167.31.157.sysads.com)
23:28.39SpeedEvilBecause nokia has switched for the mmomet entirely away from linux, and is trying to push their windows handsets.
23:29.31topobotand what anout that os based on maemo and intel?
23:30.17SpeedEvilIt fell apart.
23:30.19SpeedEvilMeego.
23:30.22SpeedEvilGone.
23:30.28topobotoh yes meego
23:30.33topobotgone? why?
23:31.26topobotif im developer and i want to develop a tool for smarphone, which is the best os should i use?
23:31.30SpeedEvilNokia became uninterested in the project.
23:32.00topoboti want to sell my app
23:32.13SpeedEvilIf you do not have a spare ten or twenty million to invest in attempting to get a new plaform on the market, android, ios, or blackberry.
23:32.25SpeedEvilYou may also consider windows phone, of course.
23:33.33topobotandroid or ios?
23:36.37topobothi?
23:37.40SpeedEvilyes.
23:37.42SpeedEvilone of them.
23:38.03SpeedEvilThe problem with either appstore is you are competing against tens of thousands of apps.
23:38.11SpeedEvilWindows may be somewhat better in that respect.
23:38.28topobotummm
23:40.21topobotmaemo is linux>
23:40.22topobot?
23:40.34topobotno android
23:40.43topobotis android linux?
23:41.28nox-their kernel is linux
23:41.44nox-(patched...)
23:42.26*** join/#maemo swc|666 (~goldbond@Aircrack-NG/Friend)
23:44.14SpeedEvilAndroid is based on a linux kernel.
23:44.29SpeedEvilYou might consider developing for N9.
23:44.45SpeedEvilWhich isn't - quite - a dead platform, though nokia are trying hard to kill it.
23:45.28*** join/#maemo PeterWolf (~peter@118-169-32-220.dynamic.hinet.net)
23:47.05topobotwhy nokia wants to kill n900?
23:48.38nox-elop wants to push win phone... :/
23:48.52nox-he killed n950 too
23:48.58topobotelop?
23:49.05nox-new nokia ceo
23:49.26topobotno business with linux based stuff?
23:56.08SpeedEvilThere are no new linux based phones, other than android, which is sort-of-arguable.

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