| 00:16.58 | *** join/#maemo-ssu raccoon_ (user@ghs/raccoon) |
| 01:45.23 | *** join/#maemo-ssu raccoon_ (user@zizek.nori.jp) |
| 01:45.37 | *** join/#maemo-ssu raccoon_ (user@ghs/raccoon) |
| 01:48.23 | *** join/#maemo-ssu raccoon_ (user@zizek.nori.jp) |
| 02:21.36 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-125-59.net.upcbroadband.cz) |
| 02:28.32 | DocScrutinizer05 | great work, alas on a completely fsckdup item. I never got the rationale to not offer the much easier timezones and instead force people to pick closest town to their own position which will get pretty annoying when you're not familiar witg geography of the country you're just in |
| 02:29.04 | DocScrutinizer05 | that's of course not ade's fault but a general unix7linux idiocy |
| 03:57.16 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 05:02.15 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
| 05:44.19 | *** join/#maemo-ssu FlameReaper (~assassin@115.132.100.68) |
| 07:10.37 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-88-64.residential.rdsnet.ro) |
| 07:28.59 | *** join/#maemo-ssu FlameReaper (~assassin@115.132.100.68) |
| 07:49.59 | *** join/#maemo-ssu FlameReaper (~assassin@115.132.100.68) |
| 08:01.27 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
| 08:24.25 | sixwheeledbeast | I would suggest that people may know the closest large town/city but not the timezone they are in. It therefore makes sense to use approximate location over timezone. Also I would assume that GPS could locate your position and change timezones as required. |
| 09:12.04 | *** join/#maemo-ssu NIN101 (~core@n900.quitesimple.org) |
| 09:15.33 | *** join/#maemo-ssu jonwil (~jonwil@1.121.109.114) |
| 09:18.07 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 09:37.34 | *** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 09:49.20 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 09:57.05 | *** join/#maemo-ssu _ade_ (~arno@5ED6BB86.cm-7-7c.dynamic.ziggo.nl) |
| 09:57.45 | _ade_ | freemangordon: would you see it as an issue to also modifify the (flat file) database in libcityinfo0-0 if we want to update the timezones? |
| 09:58.02 | _ade_ | freemangordon: and how do you get from the glibc bz2 file to the actual deb file? |
| 09:58.17 | _ade_ | freemangordon: the timezone files are generated during the build of the deb file it looks |
| 09:58.52 | freemangordon | _ade_: (re deb) - dpkg-buildpackage should do the job, iirc you need to have the kernel sources installed |
| 09:58.59 | freemangordon | merlin1991: ping, see ^^^ |
| 09:59.32 | freemangordon | _ade_: what kind of database is that? |
| 09:59.40 | _ade_ | just an ascii file |
| 09:59.57 | freemangordon | do we have the sources? |
| 10:00.14 | freemangordon | (debian packaging, etc) |
| 10:00.14 | *** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn) |
| 10:00.43 | _ade_ | An ASCII file is no issue :) libcityinfo itself is closed iirc |
| 10:01.13 | freemangordon | hmm, where is that db? /usr/share/clock/wdb ? |
| 10:01.17 | _ade_ | yep |
| 10:01.38 | freemangordon | hmm, 8164 Mar 31 2010 /usr/lib/libcityinfo0.so.0.0.0 |
| 10:01.49 | freemangordon | I guess I'll have to RE that |
| 10:01.54 | freemangordon | it shouldn't be that hard |
| 10:02.06 | _ade_ | not really needed for this |
| 10:02.18 | freemangordon | I know, but while we're on it |
| 10:02.53 | *** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn) |
| 10:03.03 | freemangordon | yep, 9k x86 binary, I need 1-2 days |
| 10:03.31 | _ade_ | If would rather see a RE for custom ringtones :) |
| 10:03.41 | freemangordon | _ade_: hehe |
| 10:04.00 | freemangordon | I know, but libhildonblabla lib is a huge one |
| 10:04.12 | freemangordon | not impossible though |
| 10:04.32 | freemangordon | but there are really higher priority issues IMO |
| 10:04.50 | freemangordon | _ade_: why don;t you fire up IDA and RE it? |
| 10:05.00 | freemangordon | I'll help you with whatever needed |
| 10:05.39 | _ade_ | I thought it wasn't, but back then you gave priority over the certificate stuff. |
| 10:06.22 | freemangordon | I still think certificate stuff had higher priority :) |
| 10:06.47 | _ade_ | I am afraid you are one of the few how is capable of the RE stuff sadly |
| 10:07.10 | freemangordon | _ade_: ever tried it? it is not a rocket science |
| 10:07.26 | freemangordon | not that it is easy, but not impossible |
| 10:07.46 | freemangordon | and hexrays is doing GREAT job to make it easier |
| 10:08.12 | _ade_ | How do you want to continue with the tz stuff? I can try to create a deb for now. |
| 10:08.25 | freemangordon | that one will be great |
| 10:08.41 | freemangordon | you mean debian source, right? |
| 10:09.20 | _ade_ | Yes, but to see if it is correct, I would like to create a deb |
| 10:09.54 | freemangordon | _ade_: sure, but I'll need the source package, so I will put REed libcityinfo there |
| 10:10.18 | _ade_ | Oh, you mean libcityinfo? |
| 10:10.22 | freemangordon | yep |
| 10:10.31 | freemangordon | what else? |
| 10:10.48 | freemangordon | libc6? |
| 10:11.12 | _ade_ | I was talking glibc, as the tz files are in there |
| 10:11.51 | freemangordon | _ade_: oh, yeah, sorry :). so, I will need a .patch changing whatever needed in libc6 source code. |
| 10:12.29 | freemangordon | _ade_: I gtg in 5 minutes, will pester merlin1991 as he was the last to build glibc, just a couple of days ago |
| 10:12.36 | _ade_ | And an can only tell that to change if I can create a correct deb |
| 10:12.43 | _ade_ | okay, later.. |
| 10:13.03 | freemangordon | _ade_: iirc you only need the kernal sources installd |
| 10:13.09 | _ade_ | thanks |
| 10:13.14 | freemangordon | or rather - kernel headers |
| 10:13.24 | freemangordon | bye for now, bbl |
| 10:18.29 | *** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn) |
| 10:18.47 | _ade_ | ping sixwheeledbeast |
| 10:19.24 | sixwheeledbeast | _ade_: pong |
| 10:20.00 | _ade_ | have you been using/testing EasyList lately? |
| 10:20.44 | sixwheeledbeast | I have it installed with a list but I can't say I have used it in anger. |
| 10:20.51 | sixwheeledbeast | why? |
| 10:22.50 | _ade_ | sixwheeldbeast: I rewrote the sync part, I was wondering if someone was interested in that. You will need to have a webservices running on a pc/server for that so you can sync both ways |
| 10:24.47 | sixwheeledbeast | I'll have a look, doesn't it use william's server somehow? |
| 10:25.41 | _ade_ | no, not anymore. That was too limited for me (only a special synclist etc). |
| 10:26.42 | _ade_ | Well, maybe I will post an update om TMO some time in the future about that |
| 10:27.51 | sixwheeledbeast | cool, that put me off using it TBH. I use Qalender for my notes now, but I will certainly test this application for you. Have you requested to be a maintainer of the package? |
| 10:28.57 | _ade_ | sixwheeledbeast: no. But he gave up maintaining it a long time ago. So I could ask him. |
| 10:31.00 | sixwheeledbeast | If no response from him use the package interface to request to be maintainer and techstaff can approve. This goes for all packages to wish to fix ;) |
| 10:32.44 | _ade_ | sixwheeledbeast: this one will do :) |
| 10:33.57 | sixwheeledbeast | :P |
| 10:41.07 | sixwheeledbeast | TBH you may as well push your latest version to -devel. you can do that without being a maintainer IIRC. All the versions in extras, testing and devel are the same so it will not make any difference. |
| 10:41.27 | sixwheeledbeast | http://maemo.org/packages/view/easylist/ |
| 10:41.41 | sixwheeledbeast | last update was Nov 2011 as you say. |
| 10:43.38 | _ade_ | sixwheeledbeast: yes, you can always push a version to extras-devel, regardless ownership. Willem has explicitly stated he is no longer maintaining it (same goes for the N9 version) |
| 10:45.39 | sixwheeledbeast | Ok well if you wish, request to be a maintainer and it will get sorted. I can see you have contributed patches in the current versions. |
| 10:53.34 | *** join/#maemo-ssu hbib (~wurmel@pD9E3CA13.dip0.t-ipconnect.de) |
| 10:55.41 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-125-59.net.upcbroadband.cz) |
| 11:27.50 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 12:04.41 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 13:37.10 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 13:45.58 | *** join/#maemo-ssu NIN102 (~core@n900.quitesimple.org) |
| 14:08.55 | *** join/#maemo-ssu arcean (~arcean@aafs104.neoplus.adsl.tpnet.pl) |
| 14:09.03 | freemangordon | arcean: ping |
| 14:20.41 | DocScrutinizer05 | sixwheeledbeast: ((may know the closest large town/city)) no, I often don't. Particularly I dunno which of several chinese or whatever towns is closest to my own town/village that I often can't even spell the name |
| 14:21.09 | DocScrutinizer05 | GPS would be the most reasonable way to implement that |
| 14:21.45 | sixwheeledbeast | You wouldn't have to speel you have a list :) |
| 14:21.46 | DocScrutinizer05 | I can't see particular rationale why I have to select Germany/Berlin when I'm ~1000km away, in Munich |
| 14:21.53 | sixwheeledbeast | s/speel/spell/ |
| 14:22.58 | DocScrutinizer05 | sorry, I think this approach is based on assumtions about knowledge in users that is not generally granted |
| 14:24.44 | DocScrutinizer05 | the most sane approach though would be to enter the time as read from a local clock and the UI filters out all settings/towns that would not result in this time to be your device system time |
| 14:25.43 | DocScrutinizer05 | this way I easily "know" about my local TZ |
| 14:26.52 | sixwheeledbeast | Well I live 200miles away from our capital city but I know what it is. Timezones are closely linked to capital city's for most places |
| 14:26.58 | DocScrutinizer05 | even when I got NFC about the name of the village i'm in, least about near big towns |
| 14:27.23 | DocScrutinizer05 | sixwheeledbeast: heck, you're talking about YOUR capital |
| 14:27.44 | DocScrutinizer05 | e.g. in australia I wouldn't even know what IS the capital |
| 14:28.26 | DocScrutinizer05 | this whole city approach is fubar by design |
| 14:28.37 | sixwheeledbeast | Surely you know the capital city of the country you travel too. |
| 14:28.49 | DocScrutinizer05 | aha, why do you think so? |
| 14:29.10 | sixwheeledbeast | FWIW Australia is Canberra |
| 14:29.19 | DocScrutinizer05 | do you think in china it makes any difference for TZ when I know it's called Beijing |
| 14:29.35 | DocScrutinizer05 | same for australia |
| 14:30.22 | DocScrutinizer05 | when capital was always the only relevant choice for TZ setting, then you can reduce that to country without even naming the capital |
| 14:30.35 | sixwheeledbeast | Well you normally fly into an airport in a big city with it's name on it |
| 14:30.59 | DocScrutinizer05 | yeah, and more often than not this airport is not in TZ list |
| 14:31.27 | DocScrutinizer05 | airports rarely are *in* big cities |
| 14:32.21 | DocScrutinizer05 | and even when they are named according to next big city maybe 100km away, that big city also rarely ever shows up in TZ list |
| 14:32.22 | sixwheeledbeast | Well "associated" to big cities, there's no room in the city for a runway |
| 14:33.05 | DocScrutinizer05 | the concept is fubar, unless you use the 2enter local current time" approach |
| 14:33.23 | DocScrutinizer05 | I can find a clock almost everywhere |
| 14:33.41 | DocScrutinizer05 | and usually it's correct time it shows |
| 14:34.37 | DocScrutinizer05 | so when I enter the time of novosibirsk it probably will filter out moscow from the towns to select from |
| 14:35.38 | DocScrutinizer05 | no need to know about capital, nor about next big city that is more relevant for TZ than that capital |
| 14:36.05 | DocScrutinizer05 | odds are that only one russion town with correct TZ stays after filtering |
| 14:36.13 | DocScrutinizer05 | Russian* |
| 14:36.56 | DocScrutinizer05 | and if there are two, then odds are it doesn't matter which of them I pick, since they are same TZ, incl DST and all, anyway |
| 14:37.41 | sixwheeledbeast | Look at the US, if you fly over there an input the state you are located at you will get the correct timezone. |
| 14:38.19 | DocScrutinizer05 | I more than once found myself trying "let's try this one. Meh, 1h+ off. OK this one then. Meh, 1h-. Maybe this..." |
| 14:39.16 | DocScrutinizer05 | sixwheeledbeast: I don't want to hear about a selected usecase where it works |
| 14:39.32 | DocScrutinizer05 | I say the approach is braindamaged by design |
| 14:39.46 | DocScrutinizer05 | even when it sometimes "works" |
| 14:40.13 | sixwheeledbeast | Australia is the same too, I don't have an issue with it TBH |
| 14:41.15 | DocScrutinizer05 | I'm not interested in (learning about) next city listed in TZ list, when I already have suffient easily acquired data (local time) that perfectly determines the TZ I need to set in my device |
| 14:42.29 | DocScrutinizer05 | it's a approach for a worlclock, but not for setting your TZ |
| 14:43.19 | FIQ | hi |
| 14:43.38 | DocScrutinizer05 | I know Rster lives in Sydney, so I try to find Sydney (or a town close to it, annoying enough) in my KDE clock applet to know gis local time |
| 14:43.40 | FIQ | since latest CSSU update, I've had issues with the battery indicator |
| 14:44.07 | sixwheeledbeast | Well there kinda linked |
| 14:44.16 | DocScrutinizer05 | for setting TZ of my mobile phone I prefer to enter the local time of that bush airport I landed and that's all i need to do |
| 14:44.19 | FIQ | it's "good enough", but it's having trouble noticing low battery correctly |
| 14:44.19 | sixwheeledbeast | FIQ: CSSU-T update? |
| 14:44.27 | FIQ | thumb |
| 14:44.36 | FIQ | sec |
| 14:44.51 | FIQ | Tmaemo9.1 |
| 14:45.02 | FIQ | from 8.3 |
| 14:45.35 | FIQ | it started showing %, but this data is no use since it's just a number representation of the battery icon and not exact |
| 14:45.51 | FIQ | but that's not the issue (other than that this is redundant) |
| 14:46.15 | FIQ | the issue is that it goes to sudden "Battery dead, charge battery!" warning from green |
| 14:46.36 | FIQ | and occasionally the icon goes *backwards* from red back to lowest green |
| 14:47.13 | DocScrutinizer05 | hehe |
| 14:47.16 | FIQ | I've seen the latter only once before this CSSU update, but this update has given the indicator more issues |
| 14:47.58 | sixwheeledbeast | Kinetic charging :P |
| 14:48.03 | DocScrutinizer05 | i finally have to edit the meanwhile incorrect phrase "CSSU is recommended for every user" |
| 14:48.57 | FIQ | Perhaps these issues are caused by me never charging on device? and thus it is having trouble calibrating the displaying? |
| 14:49.23 | FIQ | At least there was such need for the non-core (non CSSU) version of "more detailed info" |
| 14:49.38 | FIQ | that you had to use device for charging for it to work correctly |
| 14:51.05 | sixwheeledbeast | the battery indicator has never been truly accurate, I have experienced this "backwards" on all flavours |
| 14:51.11 | FIQ | oh and DocScrutinizer05, fyi before you draw any conclusions - there's nothing wrong with the batteries I carry right now, no damage, no weird issues (apart from since last CSSU), no sparks, or any similar issues |
| 14:51.38 | FIQ | sixwheeledbeast: mkay, well I never did until now strangely |
| 14:52.46 | FIQ | (apart from once, as said, several months ago) |
| 14:57.38 | DocScrutinizer05 | FIQ: I'm sure your battery is not the culprit |
| 14:58.31 | FIQ | also |
| 14:58.34 | FIQ | [15:48:03] <DocScrutinizer05> i finally have to edit the meanwhile incorrect phrase "CSSU is recommended for every user" |
| 14:58.48 | FIQ | keep in mind, I do use the T branch :p |
| 14:59.03 | FIQ | pretty sure CSSU-stable is intended to be... well, stable |
| 14:59.07 | FIQ | and recommended |
| 14:59.08 | FIQ | no? |
| 14:59.28 | FIQ | while testing which I use is expected to have issues |
| 14:59.53 | FIQ | which needs to be taken care of before even considering moving these to stable |
| 14:59.57 | DocScrutinizer05 | battery applet is hard to het right, seen a lot of tuning over the last decade (yes the concepts origin even in pre-symbian times) and recent "improvements" done to it always planned to overcome one annoyince and missed about the linked other 5 annoyances the fix would introduce |
| 15:02.21 | DocScrutinizer05 | the problem is different users have different expectations regarding battery meter |
| 15:03.27 | DocScrutinizer05 | what you blame as a bug (phantom charging going from red to green) is correct representation of what actually happens for other users |
| 15:04.11 | DocScrutinizer05 | it's a question to *define* what that meter actually *means*, to start with |
| 15:05.42 | DocScrutinizer05 | is it voltage? remaining energy (Watt-hours)? remaining ampere-hours? remaining operation time at average power consumption? on current consumption? on max consumption? |
| 15:06.02 | DocScrutinizer05 | is it average of last 5 min? of last 30s? |
| 15:06.37 | DocScrutinizer05 | is it relative to a new battery, or to the status of this particular battery? |
| 15:06.55 | DocScrutinizer05 | is it linear or logarithmic? |
| 15:07.05 | DocScrutinizer05 | or even with an offset? |
| 15:07.31 | DocScrutinizer05 | to give an additional hour of operation time when meter reaches ZERO |
| 15:08.17 | DocScrutinizer05 | shall it make assumptions of (future) usage? |
| 15:08.58 | DocScrutinizer05 | based on what? current cell coverage/signal, or worst case signal? |
| 15:09.10 | DocScrutinizer05 | 2G or 3G |
| 15:09.22 | DocScrutinizer05 | how much data traffic? |
| 15:09.44 | FIQ | if you're going to list every single expectation, you'll be here for a year ;) |
| 15:09.45 | DocScrutinizer05 | ask 100 users and you get 350 notions |
| 15:09.58 | DocScrutinizer05 | yep, exactly |
| 15:11.40 | sixwheeledbeast | :nod: to all of the above. |
| 15:12.15 | DocScrutinizer05 | best approach was a pretty comprehensive rich battery diagnostics page, listing all relevant parameters like e.g. bq2k-detail2 does, and make user pick the value she wants to get displayed in applet gauge bar |
| 15:13.43 | DocScrutinizer05 | even allow to enter simple mathematical equations in a shell or C syntax to calculate what to display on apllet |
| 15:14.09 | DocScrutinizer05 | my dream OS |
| 15:14.36 | DocScrutinizer05 | alas common take on such thing is "waaay too complex for average joe" |
| 15:23.28 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 15:49.37 | *** join/#maemo-ssu arcean_ (~arcean@aafs104.neoplus.adsl.tpnet.pl) |
| 16:45.56 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 16:58.35 | *** join/#maemo-ssu arcean__ (~arcean@aaem138.neoplus.adsl.tpnet.pl) |
| 17:46.06 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 17:46.11 | *** join/#maemo-ssu hbib1 (~wurmel@pD9E3D19C.dip0.t-ipconnect.de) |
| 17:48.50 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 18:00.55 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 18:05.52 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 18:08.00 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 18:41.29 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 19:27.13 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 19:52.20 | *** join/#maemo-ssu amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 20:08.29 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 20:23.14 | *** join/#maemo-ssu arcean__ (~arcean@aafs12.neoplus.adsl.tpnet.pl) |
| 20:35.58 | *** join/#maemo-ssu _rd (~rd@p57B486F0.dip0.t-ipconnect.de) |
| 20:41.34 | *** join/#maemo-ssu int_ua (~int_ua@37.73.220.99) |
| 20:50.21 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-88-64.residential.rdsnet.ro) |
| 22:25.57 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 22:26.19 | *** join/#maemo-ssu aap (~drew@cpe-71-64-199-26.cinci.res.rr.com) |
| 22:53.51 | *** join/#maemo-ssu ravelo (~ravelo@85-127-59-167.dynamic.xdsl-line.inode.at) |
| 23:01.31 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
| 23:57.51 | *** join/#maemo-ssu dafox (~dafox@ip3e8380c8.speed.planet.nl) |