| *** DocScrutinizer05 has quit IRC | 00:00 | |
| *** DocScrutinizer05 has joined #maemo | 00:00 | |
| *** pdz has quit IRC | 00:04 | |
| sixwheeledbeast | M4rtinK: :) | 00:04 |
|---|---|---|
| *** shentey has quit IRC | 00:05 | |
| sixwheeledbeast | re tracklogs I cannot reproduce the reported issue of not stopping a tracklog. However I did notice the stop button displays the banner "saving" even if the tracklog is off. | 00:05 |
| M4rtinK | sixwheeledbeast: BTW, any feedback on the track logging fix ? :) | 00:05 |
| M4rtinK | yeah, it should do that | 00:06 |
| M4rtinK | for about 3 seconds | 00:06 |
| M4rtinK | because if you leave it running for a couple of hours | 00:06 |
| M4rtinK | there will be a multi-MB CSV file that needs to be converted to GPX | 00:06 |
| *** rm_work is now known as rm_work|away | 00:07 | |
| *** pdz has joined #maemo | 00:07 | |
| M4rtinK | so while usually it is quite redundant, sometimes it is indeed "saving" for some time :) | 00:07 |
| sixwheeledbeast | Well I tried to use the tracklog for the first time this weekend out on the motorbike. However the device became unresponsive by the time I got to the petrol station 5 minutes away. | 00:07 |
| M4rtinK | weird | 00:08 |
| sixwheeledbeast | Not tried again since. | 00:08 |
| M4rtinK | I've use | 00:08 |
| sixwheeledbeast | Black screen with backlight on only modRana was open. I did get a SMS in that time so maybe that caused some weirdness?. | 00:09 |
| M4rtinK | d modRana a bit on a field trip this Friday and it worked fine | 00:09 |
| sixwheeledbeast | I plan to track my route up Snowdon in a few weeks. | 00:10 |
| sixwheeledbeast | So when I walk or ride I am testing it out. | 00:10 |
| M4rtinK | lets hope we can track it down before then :) | 00:10 |
| M4rtinK | I think there are 3 most probable possible causes: | 00:11 |
| M4rtinK | 1) memory leek - it is possible modRana is adding to some data structure somewhere and not removing from it | 00:11 |
| M4rtinK | 2) modRana triggering some race or other bug in Cairo/GTK/X | 00:12 |
| *** flynx_ has joined #maemo | 00:12 | |
| M4rtinK | (could b related to the SMS - might trigger a notification, which shows an overlay, etc.) | 00:13 |
| M4rtinK | 3) that SGX driver bug resurfacing for some reason | 00:13 |
| M4rtinK | so I think that black screen could be either the N900 swapping like hell and being unresponsive or X/GPU driver crashing | 00:14 |
| sixwheeledbeast | M4rtinK: seemed like the SGX bug symptoms however I was away from a device I could SSH with. | 00:15 |
| M4rtinK | I'm thinking some sort of script that logs top or free memory could be useful to track it down | 00:16 |
| sixwheeledbeast | M4rtinK: could swap on uSD be a constant? Maybe reports are from people with uSD swaps? | 00:16 |
| M4rtinK | as for potential countermeasures I'm thinking about introducing performance tuning settings | 00:17 |
| M4rtinK | for the tile cache size, download thread counts, etc. | 00:17 |
| M4rtinK | in hope that setting them to lower values it could be possible the work around the issue :) | 00:17 |
| M4rtinK | sixwheeledbeast: for the record I'm using the stock partitioning on my N900 | 00:18 |
| M4rtinK | only bigger change is CSSU + Thumb + 900 MHz overclock (since like ever) | 00:18 |
| M4rtinK | so yeah, I guess it could be influenced by it | 00:19 |
| M4rtinK | like say io errors crashing the kernel :) | 00:19 |
| M4rtinK | actually I wonder what happens if you kill the block device under an active swap :) | 00:20 |
| sixwheeledbeast | :nod: well it is popular to use uSD swaps now. no overclocking here. | 00:20 |
| M4rtinK | well, could improve the eMMC lifetime I guess | 00:20 |
| M4rtinK | I wonder about throughput though | 00:21 |
| *** wotan147 has quit IRC | 00:21 | |
| M4rtinK | uSD bandwidth generally sucks | 00:21 |
| sixwheeledbeast | eMMC lifetime and workaround for swap defragmentation | 00:21 |
| M4rtinK | oh, interesting :) | 00:22 |
| sixwheeledbeast | ~flopswap | 00:22 |
| infobot | well, flopswap is http://wiki.maemo.org/Flopswap | 00:22 |
| sixwheeledbeast | ;) | 00:22 |
| M4rtinK | BTW, what about compressed swap ? :) | 00:22 |
| M4rtinK | using something like LZOo/LZ4/snappy could work | 00:23 |
| M4rtinK | might also help with the limited bandwidth | 00:25 |
| sixwheeledbeast | I dont believe there are any benefits, you have to uncompress it. | 00:25 |
| M4rtinK | sure, bu the benefit is that only compressed data will go over the presumably slow uSD bus | 00:28 |
| M4rtinK | all the compression would happen in RAM and LZO & co are _FAST_ | 00:28 |
| M4rtinK | but who knows, it might still be too much for the CPU of the N900 to provide any benefit | 00:30 |
| M4rtinK | on the other hand we have had some good experience with zRAM (previously called compcache) | 00:30 |
| M4rtinK | N9 is using it's predecessor and it is in mainline kernel since 3.10 | 00:31 |
| M4rtinK | it is basically a fixed size compressed block device residing in RAM you can use to setup swap | 00:32 |
| *** wotan147 has joined #maemo | 00:32 | |
| M4rtinK | and it indeed seem to work quite nicely | 00:32 |
| M4rtinK | we have enabled it on one of our virtualisation servers and the claim of the zRAM people that using it basically duplicates possible RAM usage before the real swap is hit seems to hold :) | 00:34 |
| M4rtinK | oh, looks like it is in kernel power already: http://talk.maemo.org/showthread.php?t=76112 :) | 00:35 |
| *** florian has quit IRC | 00:40 | |
| sixwheeledbeast | Well I believe Swappolube should be able to tune the I/O | 00:40 |
| M4rtinK | BTW, provided the swap on uSD can be disabled | 00:44 |
| M4rtinK | it might be good to try if you get more/less modRana freezes if it is ON or OFF | 00:44 |
| *** wotan147 has quit IRC | 00:49 | |
| *** xes has joined #maemo | 00:55 | |
| *** fanf has joined #maemo | 00:58 | |
| fanf | 'lo ? | 00:59 |
| *** fanf has left #maemo | 01:00 | |
| *** fanf has joined #maemo | 01:02 | |
| *** fanf has left #maemo | 01:03 | |
| *** rm_work|away is now known as rm_work | 01:06 | |
| *** xes_ has joined #maemo | 01:08 | |
| *** xes has quit IRC | 01:10 | |
| sixwheeledbeast | well yes it can be disabled, I'll check that out. | 01:12 |
| *** xes_ is now known as xes | 01:13 | |
| ShadowJK | The current day deent uSDs have better iops performance than 2008-2009 era emmc | 01:21 |
| ShadowJK | Though of course, you can also buy worse performing cards. | 01:21 |
| M4rtinK | new modRana is out! :D http://talk.maemo.org/showpost.php?p=1434142&postcount=1619 | 01:23 |
| *** N-Mi has quit IRC | 01:38 | |
| *** jooles has joined #maemo | 01:47 | |
| jooles | Hey all. Does anyone have a copy of the latest rx-48 firmware image? All the sites that had it seem to have gone down and my N810 won't boot anymore :C | 01:48 |
| ShadowJK | did you take out battery for 5 minutes? | 01:48 |
| jooles | not for 5 minutes | 01:48 |
| jooles | even so, it's in a mess and could do with being re-flashed | 01:49 |
| ShadowJK | rx-48, is that wimax model? | 01:50 |
| jooles | I succumbed to temptation like I always do, some months back, and tried to build a new kernel for it which never ends well | 01:50 |
| jooles | it is | 01:50 |
| DocScrutinizer05 | err | 01:50 |
| DocScrutinizer05 | ~tabletsdev | 01:50 |
| infobot | extra, extra, read all about it, tabletsdev is http://tablets-dev.nokia.com/ http://wiki.maemo.org/Tabletsdev , http://tabletsdev.maemo.org (all defunct, thanks Nokia) or the nice site http://www.fladnag.net/downloads/telephone/n900/tools/, or http://www.mmnt.net/db/0/0/93.81.63.203/repositories/skeiron.org/skeiron.org/tablets-dev/maemo_dev_env_downloads | 01:50 |
| jooles | in order, down, 404 and has no images | 01:51 |
| DocScrutinizer05 | ~combined | 01:51 |
| infobot | extra, extra, read all about it, combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, or http://galif.eu/nokia/ | 01:51 |
| DocScrutinizer05 | ~emmc | 01:51 |
| infobot | emmc is, like, magnet:?xt=urn:btih:402fb5cc8a48ecbc18a77c9cf70d869a775bcf53&dn=RX-51%5F2009SE%5F10.2010.13-2.VANILLA%5FPR%5FEMMC%5FMR0%5FARM.bin or https://dl.dropboxusercontent.com/u/4105928/RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.torrent, or http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/5/--FID--A0A22YHFSICNA/--LID--FiRe1275051276916/AE98ED9D_RX-51_2009SE_10.2010.13-2.CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin | 01:51 |
| DocScrutinizer05 | ~flasher | 01:52 |
| infobot | somebody said flasher was at http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz (also .exe!), or http://www.chakra-project.org/ccr/packages.php?ID=5027 or generally http://www.google.com/search?q=maemo_flasher-3.5_2.5.2.2.tar.gz. HARMattan(N9): https://aur.archlinux.org/packages/fl/flasher-harmattan/flasher-harmattan.tar.gz, or -- list of filenames/md5sums: http://pastebin.com/sYKdNJSH, or http://galif.eu/nokia/ | 01:52 |
| jooles | DocScrutinizer05, Care to read what I wrote or not? I get that these questions get annoying but once all the sites went down I had no choice but to come and ask. I'm not an idiot but clearly you can't tell that RX-48 != RX-51 | 01:53 |
| DocScrutinizer05 | thanks for your kind way to tell me that you didn't notice http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz | 01:54 |
| jooles | right, the flasher I could find | 01:54 |
| jooles | I'm looking for the firmware image | 01:54 |
| DocScrutinizer05 | *sigh* | 01:54 |
| jooles | As I also said earlier. Also spamming links at me is kinda rude | 01:54 |
| *** N-Mi has joined #maemo | 01:55 | |
| DocScrutinizer05 | meh | 01:55 |
| DocScrutinizer05 | good luck | 01:55 |
| jooles | Well thanks anyway. Sorry everyone for causing so much spam. | 01:57 |
| *** jooles has left #maemo | 01:58 | |
| DocScrutinizer05 | friendly guy | 01:58 |
| bencoh | what the ... hmm. | 02:02 |
| *** M4rtinK has quit IRC | 02:03 | |
| nox- | no n8xx firmware anymore? | 02:06 |
| *** odin_ has joined #maemo | 02:10 | |
| *** antranigv has joined #maemo | 02:15 | |
| antranigv | Hay, I have N900, I changed the /bin/sh to /bin/bash in /etc/passwd file... I wanted to use Bash as default... so now I can't boot the device :( it's stuck at loading :( any help ?? | 02:17 |
| nox- | ~rescueos | 02:20 |
| infobot | [rescueos] http://n900.quitesimple.org/rescueOS/ | 02:20 |
| antranigv | P.S. MicroUSB not working :( ... I can fix it after I go back home (still outside of my country) | 02:22 |
| nox- | ow | 02:23 |
| * nox- leaves you to DocScrutinizer05 maybe he has a better idea | 02:23 | |
| antranigv | Let's hope and wait :)) | 02:24 |
| DocScrutinizer05 | there's no idea how to fix such sort of broken rootfs | 02:25 |
| antranigv | DocScrutinizer05: is flashing a good idea ? I can get the USB port fix | 02:25 |
| DocScrutinizer05 | when you can fix the USB, then get rescueos and revert the passwd edit | 02:26 |
| antranigv | DocScrutinizer05 , nox- thanks ! | 02:27 |
| DocScrutinizer05 | nox-: how would I publish a torrent? | 02:27 |
| DocScrutinizer05 | noob here | 02:28 |
| xes | http://www.btkitty.com/DcjJAQAgCAOwmcBSyjh47T-C5hnUNWOxIzmdvZc84MZ0QfilCJzxAA~S8ssyi1PLEotBgA.torrent.html | 02:30 |
| nox- | DocScrutinizer05, i havent tried that yet either... | 02:33 |
| nox- | oh xes found it it seems :) | 02:35 |
| xes | anyway md5 must be checked | 02:37 |
| nox- | *nod* | 02:38 |
| bencoh | broken usb + broken fs abroad ? sounds terrible :/ | 02:39 |
| *** dima5` has joined #maemo | 02:39 | |
| nox- | indeed | 02:40 |
| DocScrutinizer05 | xes: I found this, and it doesn't work for me. but that's maybe because I'm behind a NAT anyway. And actually I asked how to *publish* a torrent/magnet | 02:42 |
| nox- | downloading a torrent more or less needs portfowards yeah | 02:43 |
| nox- | (if you're behind nat) | 02:43 |
| *** arcean_ has quit IRC | 02:52 | |
| DocScrutinizer05 | yeah, I know. I have to admit I simply don't understand that crap (not port forwarding since that's easy - but that torrent client) | 02:56 |
| DocScrutinizer05 | it seems to miss any server it can coordinate with | 02:57 |
| DocScrutinizer05 | neither sends nor receives a single byte | 02:57 |
| DocScrutinizer05 | search is more or less broken too | 02:58 |
| *** bef0rd has joined #maemo | 02:59 | |
| *** bef0rd has joined #maemo | 02:59 | |
| dos1 | there is no "server it can coordinate with" aside of trackers, but that's per torrent file (but DHT can be used instead anyway) | 03:02 |
| *** goldkatze has quit IRC | 03:02 | |
| dos1 | generally you just create a .torrent file with a hash and some open tracker specified, then point your local client to it in a way so it treats your file as already downloaded, and then send .torrent file to someone else (or to some public index) | 03:03 |
| dos1 | (or magnet link can be used instead of .torrent file) | 03:05 |
| DocScrutinizer05 | no connection to any trackers here | 03:06 |
| dos1 | http://www.mepis.org/docs/en/index.php?title=Creating_a_torrent | 03:06 |
| *** RiD has quit IRC | 03:06 | |
| *** RiD has joined #maemo | 03:07 | |
| dos1 | trackers are per-file, so if you don't have any torrents down/uploading then that's expected :P | 03:07 |
| DocScrutinizer05 | HAHAHA!!! >>You must add at least one tracker: type or paste in the URL: http://linuxtracker.org:2710/announce and click the add button.<< | 03:07 |
| DocScrutinizer05 | suuure, I know this by heart, and thus the shitty ktorrent doesn't even suggest it | 03:08 |
| DocScrutinizer05 | and the magnet seems to linger there like it does nothing at all | 03:09 |
| dos1 | dunno what you want to seed - if it's not some 100% legal linux iso, then something like http://openbittorrent.com/ will probably be a better choice :P | 03:09 |
| DocScrutinizer05 | probably best choice is to forget about that torrent shit | 03:09 |
| nox- | torrents are faster for some people | 03:10 |
| DocScrutinizer05 | meh, I don't care | 03:10 |
| nox- | :) | 03:10 |
| TheOnlyJoey|desk | i normally download torrent with the speed of my internet connection, 50mbit as we speak | 03:11 |
| DocScrutinizer05 | it's not like it gives me headache to NOT share some of the stuff I have here | 03:11 |
| dos1 | it all depends | 03:11 |
| DocScrutinizer05 | this ktorrent client however for sure gives me headache | 03:11 |
| TheOnlyJoey|desk | DocScrutinizer05, try Transmission, has served me well for years :) | 03:11 |
| dos1 | ktorrent is a pretty good client imo - you would probably have similar problems with any client | 03:12 |
| dos1 | unless it has some "friendly" trackers etc. so it autoprefills this stuff for you ;) | 03:13 |
| DocScrutinizer05 | ok, so much for wasted time with torrents | 03:13 |
| dos1 | anyway, that mepis wiki page has it described pretty well | 03:15 |
| *** xes has quit IRC | 03:15 | |
| *** janemba has quit IRC | 03:18 | |
| nox- | magnet:?xt=urn:btih:49f11696a576b26adc8254216728484b268554e3&dn=firmwares | 03:18 |
| nox- | doesnt seem to work at least in rtorrent | 03:18 |
| *** janemba has joined #maemo | 03:19 | |
| nox- | (from xes' link) | 03:19 |
| *** antranigv has quit IRC | 03:20 | |
| DocScrutinizer05 | exactly | 03:23 |
| *** eMHa_ has joined #maemo | 03:24 | |
| DocScrutinizer05 | and http://openbittorrent.com/ reports "Error: invalid data from tracker" | 03:24 |
| nox- | theres a thunder:// link too which seems to belong to https://en.wikipedia.org/wiki/Thunder_Download | 03:32 |
| nox- | "Although not widely reported, Xunlei client has been discovered spreading the malware Win32/KanKan to thousands of Chinese Windows PCs and Android devices.[5] In 2013 the company admitted its employees bundled malware into Xunlei client.[6]" | 03:32 |
| nox- | uh | 03:32 |
| hurrian_ | such a surprise | 03:32 |
| jon_y | isn't xunlei also one of those exploiting torrent clients? | 03:35 |
| jon_y | uh, selfish client | 03:35 |
| * nox- wouldnt know | 03:35 | |
| jon_y | last I read, it was banned from private trackers | 03:36 |
| nox- | well if it spreads malware who wants to use it anyway... | 03:36 |
| *** jonwil has joined #maemo | 03:37 | |
| jon_y | lusers want to, for faster speeeeed | 03:37 |
| nox- | any idea whats wrong with that magnet link? or is it just the tracker being down? | 03:39 |
| jon_y | I think its just the tracker since you got the torrent already | 03:40 |
| nox- | there doesnt even seem to be a .torrent to download | 03:44 |
| hurrian_ | man, and people wonder why nobody outside of china wants to use that crap | 03:44 |
| *** dima5` has left #maemo | 03:46 | |
| *** robbiethe1st has joined #maemo | 03:49 | |
| *** flynx_ has quit IRC | 03:50 | |
| *** Humpelstilzchen has quit IRC | 04:10 | |
| *** Kabouik has quit IRC | 04:11 | |
| *** Humpelstilzchen has joined #maemo | 04:15 | |
| *** bef0rd has quit IRC | 04:20 | |
| *** janemba has quit IRC | 04:27 | |
| *** janemba has joined #maemo | 04:27 | |
| *** erlehmann has joined #maemo | 04:29 | |
| *** RiD has quit IRC | 04:39 | |
| *** RiD has joined #maemo | 04:39 | |
| DocScrutinizer05 | I gave up on torrent, that's silly. When you need sth, just ask me | 04:48 |
| DocScrutinizer05 | I got an amazingly huge backup folder here | 04:48 |
| *** janemba has quit IRC | 05:04 | |
| *** nox- has quit IRC | 05:04 | |
| *** janemba has joined #maemo | 05:05 | |
| *** maybeWTF has quit IRC | 05:34 | |
| *** maybeWTF has joined #maemo | 05:39 | |
| *** lxp1 has joined #maemo | 06:01 | |
| *** lxp has quit IRC | 06:04 | |
| *** dima5` has joined #maemo | 06:05 | |
| *** janemba has quit IRC | 06:11 | |
| *** janemba has joined #maemo | 06:12 | |
| *** RiD has quit IRC | 06:26 | |
| *** janemba has quit IRC | 06:38 | |
| *** janemba has joined #maemo | 06:40 | |
| *** Psi has quit IRC | 06:58 | |
| *** Psi has joined #maemo | 07:09 | |
| *** LauRoman has joined #maemo | 07:11 | |
| *** robbiethe1st has quit IRC | 07:25 | |
| *** dhbiker has joined #maemo | 07:52 | |
| *** erlehmann has quit IRC | 07:59 | |
| *** maybeHere has joined #maemo | 08:09 | |
| *** maybeArgh has joined #maemo | 08:09 | |
| *** maybeHere has quit IRC | 08:10 | |
| *** jormungandr has joined #maemo | 08:25 | |
| *** jonwil has quit IRC | 08:52 | |
| *** kolp has joined #maemo | 08:54 | |
| *** fuz_ has quit IRC | 08:57 | |
| *** fuz_ has joined #maemo | 09:02 | |
| *** DocScrutinizer05 has quit IRC | 09:14 | |
| *** DocScrutinizer05 has joined #maemo | 09:14 | |
| *** Gadgetoid has quit IRC | 09:16 | |
| *** Gadgetoid has joined #maemo | 09:17 | |
| *** mavhc has quit IRC | 09:22 | |
| *** mavhc has joined #maemo | 09:22 | |
| *** mavhc has quit IRC | 09:29 | |
| *** mavhc has joined #maemo | 09:32 | |
| *** Pilke has joined #maemo | 09:56 | |
| *** AD-N770 has joined #maemo | 09:59 | |
| *** tanty_off is now known as tanty | 10:00 | |
| *** norayr has joined #maemo | 10:02 | |
| *** LaoLang_cool has joined #maemo | 10:22 | |
| *** dhbiker has quit IRC | 10:42 | |
| *** rcg has joined #maemo | 10:43 | |
| *** protem has quit IRC | 10:48 | |
| *** goldkatze has joined #maemo | 10:48 | |
| *** janemba has quit IRC | 10:56 | |
| *** janemba has joined #maemo | 10:57 | |
| *** APic has quit IRC | 10:57 | |
| *** shamus has quit IRC | 10:59 | |
| *** shamus has joined #maemo | 10:59 | |
| *** geaaru has joined #maemo | 11:07 | |
| *** dhbiker has joined #maemo | 11:14 | |
| *** norayr has quit IRC | 11:16 | |
| *** LaoLang_cool has quit IRC | 11:24 | |
| *** tanty has quit IRC | 11:25 | |
| *** Kup has joined #maemo | 11:29 | |
| *** Pilke has quit IRC | 11:32 | |
| *** goldkatze has quit IRC | 11:44 | |
| *** tanty_off has joined #maemo | 11:48 | |
| *** tanty_off is now known as tanty | 11:48 | |
| *** geaaru has quit IRC | 11:53 | |
| *** dima5` has quit IRC | 11:55 | |
| *** robink has quit IRC | 11:58 | |
| *** robink has joined #maemo | 12:05 | |
| *** geaaru has joined #maemo | 12:06 | |
| *** Kabouik has joined #maemo | 12:13 | |
| *** Aspi has joined #maemo | 12:21 | |
| Aspi | there are lots of entries of phones world wide promoting "UNLOCKED". what is this "unlocked" really, can a vendor lock a device, especially a N900 that will be flashed? | 12:23 |
| kerio | Aspi: rapuyama don't care, rapuyama don't give a fuck | 12:25 |
| kerio | you can flash as hard as you want, the n900 will stay oplocked/simlocked | 12:25 |
| Aspi | so it's done in some ROM? | 12:26 |
| hurrian_ | there are locked N900s? | 12:29 |
| *** mkaindl has joined #maemo | 12:30 | |
| Aspi | that's what I don't know. I dunno if "unlocked" is Chinese marketing scam. | 12:31 |
| hurrian_ | the Hong Kong refurbished N900s are unlocked, but are probably reballed with cigarette lighters | 12:31 |
| *** eMHa_ has quit IRC | 12:33 | |
| Aspi | so, I have the dilemma that if I buy second hand, previous owner might in turn have bought a HK :) | 12:33 |
| hurrian_ | do you already have a N900? | 12:34 |
| Aspi | no | 12:34 |
| hurrian_ | reusing HK N900s isn't too bad if you just want spare parts | 12:34 |
| hurrian_ | welp, that's pretty risky then | 12:34 |
| fizzie | There's an "Enter code to remove operator lock" option in the title-bar-menu of the "Settings" application, which kind of sounds like they sold operator-locked N900s somewhere. Unless it's there just in case. | 12:34 |
| *** ALo has quit IRC | 12:35 | |
| Aspi | ah, okay. I'm just gonna ask seller if I buy. | 12:35 |
| Aspi | are y'all excited about the Neo900? or will you live with the N900 to your death? :) | 12:36 |
| *** DocScrutinizer05 is now known as DocScrutinizer06 | 12:36 | |
| hurrian_ | my N900 was swiped, and all the N900s on the local equivalent of eBay are dead/sold as-is. | 12:37 |
| *** DocScrutinizer06 is now known as DocScrutinizer05 | 12:37 | |
| *** ALo has joined #maemo | 12:37 | |
| Aspi | ditto, so I look international | 12:37 |
| hurrian_ | unfortunately, I won't be happy with just an OMAP3730, having been totally spoiled by how powerful octa-core balls out Android phones are. | 12:38 |
| Aspi | I might take a chance on a HK refurb if I can't get something else, as they are not extremely expensive, and I might get lucky and get a reasonably working item (?) | 12:38 |
| hurrian_ | I'll probably just run NeoFremantle on my N9, when it materializes. | 12:39 |
| dos1 | [02:24:25] <DocScrutinizer05> and http://openbittorrent.com/ reports "Error: invalid data from tracker" | 12:40 |
| dos1 | this url is for the browser, tracker url is on the page :) | 12:41 |
| *** eMHa_ has joined #maemo | 12:58 | |
| *** arcean has joined #maemo | 12:58 | |
| *** LauRoman has quit IRC | 12:59 | |
| *** DocScrutinizer05 is now known as DocScrutinizer06 | 13:08 | |
| *** DocScrutinizer06 is now known as DocScrutinizer05 | 13:08 | |
| Aspi | kerio: after reading the logs about rapuyama O_o maybe I'll need a second thinkthrough about N900 | 13:08 |
| *** Aspi has left #maemo | 13:10 | |
| DocScrutinizer05 | hurrian_: good luck! I doubt anybody will backport the N9-BB5 cmt stack to fremantle | 13:16 |
| DocScrutinizer05 | other than that, you're right that N9 has basically exactly same SoC and Storage/Memory chip like Neo900 | 13:18 |
| hurrian_ | isn't the BB5 comm rather similar? | 13:18 |
| *** janemba has quit IRC | 13:21 | |
| *** janemba has joined #maemo | 13:22 | |
| DocScrutinizer05 | I don't think so. N9 BB5 is responsible for handling aegis certs/tokens and actually this is what forbids downgrading of HARM "firmware" | 13:22 |
| hurrian_ | that's something interesting to test, unlzo'ing PR1.2 and running it on N9. | 13:24 |
| hurrian_ | as far as I've read in the kernel hooks for aegis, I haven't seen any calls to BB5, but it might be in userland | 13:24 |
| hurrian_ | besides, if BB5 doesn't get it's aegis fix, what's it gonna do, shut down the device? Nemo clearly works without it* (ofono as the RIL instead of Nokia's stuff, but hey, it works) | 13:26 |
| *** dhbiker has quit IRC | 13:30 | |
| *** norayr has joined #maemo | 13:31 | |
| *** goldkatze has joined #maemo | 13:46 | |
| *** janemba has quit IRC | 13:46 | |
| *** janemba has joined #maemo | 13:47 | |
| *** janemba has quit IRC | 13:51 | |
| *** janemba has joined #maemo | 13:52 | |
| *** merlin1991 has quit IRC | 14:03 | |
| *** janemba has quit IRC | 14:06 | |
| *** merlin1991 has joined #maemo | 14:06 | |
| *** janemba has joined #maemo | 14:07 | |
| *** b1101 has quit IRC | 14:10 | |
| *** dhbiker has joined #maemo | 14:13 | |
| *** jas4711 has quit IRC | 14:14 | |
| *** Kup has left #maemo | 14:36 | |
| *** janemba has quit IRC | 14:44 | |
| *** janemba has joined #maemo | 14:44 | |
| *** janemba has quit IRC | 15:03 | |
| *** janemba has joined #maemo | 15:04 | |
| *** Ninja has quit IRC | 15:13 | |
| *** Wulfe has joined #maemo | 15:13 | |
| *** Wulfe has joined #maemo | 15:13 | |
| *** erlehmann has joined #maemo | 15:25 | |
| *** janemba has quit IRC | 15:33 | |
| *** janemba has joined #maemo | 15:34 | |
| *** b1101 has joined #maemo | 16:00 | |
| *** b1101 has joined #maemo | 16:00 | |
| *** flynx_ has joined #maemo | 16:04 | |
| *** janemba has quit IRC | 16:26 | |
| *** janemba has joined #maemo | 16:27 | |
| *** janemba has quit IRC | 16:37 | |
| *** jas4711 has joined #maemo | 16:37 | |
| *** janemba has joined #maemo | 16:38 | |
| *** SAiF1 has joined #maemo | 16:41 | |
| *** RiD has joined #maemo | 16:43 | |
| *** RedM has joined #maemo | 16:56 | |
| *** RedW has quit IRC | 16:56 | |
| *** jas4711 has quit IRC | 16:58 | |
| *** DrCode has quit IRC | 17:02 | |
| *** DrCode has joined #maemo | 17:03 | |
| *** konelix__ has joined #maemo | 17:32 | |
| *** konelix__ has quit IRC | 17:34 | |
| *** konelix__ has joined #maemo | 17:34 | |
| *** bluelupo has joined #maemo | 18:01 | |
| *** bluelupo_ has joined #maemo | 18:07 | |
| *** bluelupo_ has quit IRC | 18:15 | |
| *** bluelupo_ has joined #maemo | 18:22 | |
| *** bluelupo has quit IRC | 18:22 | |
| *** SAiF has joined #maemo | 18:24 | |
| *** SAiF1 has quit IRC | 18:26 | |
| *** bluelupo has joined #maemo | 18:49 | |
| *** ced117 has joined #maemo | 18:51 | |
| *** kerio has quit IRC | 18:54 | |
| *** kerio has joined #maemo | 18:54 | |
| *** rcg has quit IRC | 18:56 | |
| bencoh | hm, looking at scim_panel_gtk code ... no wonder scim eats battery ... | 19:00 |
| bencoh | _check_exit_timeout = gtk_timeout_add (500, check_exit_timeout_cb, NULL); | 19:00 |
| bencoh | couldnt get uglier | 19:01 |
| bencoh | (checks every 500ms whether it should exit or not) | 19:03 |
| *** N-Mi has quit IRC | 19:04 | |
| *** N-Mi has joined #maemo | 19:07 | |
| *** LjL has quit IRC | 19:08 | |
| *** AD-N770 has quit IRC | 19:11 | |
| *** heroux has quit IRC | 19:11 | |
| *** heroux has joined #maemo | 19:11 | |
| *** tanty is now known as tanty_off | 19:13 | |
| *** tanty_off is now known as tanty | 19:14 | |
| *** LjL has joined #maemo | 19:15 | |
| *** Kabouik has quit IRC | 19:41 | |
| *** kraft has quit IRC | 19:43 | |
| *** fuz_ has quit IRC | 19:44 | |
| *** fuz_ has joined #maemo | 19:49 | |
| *** Kabouik has joined #maemo | 19:57 | |
| *** tanty is now known as tanty_off | 19:58 | |
| *** LauRoman has joined #maemo | 20:00 | |
| *** ced117 has quit IRC | 20:12 | |
| *** Katajakasa has quit IRC | 20:15 | |
| *** infobot has quit IRC | 20:15 | |
| *** infobot has joined #maemo | 20:17 | |
| infobot | DocScrutinizer: infobot joined! | 20:17 |
| *** ChanServ sets mode: +v infobot | 20:17 | |
| *** RzR is now known as rZr | 20:31 | |
| DocScrutinizer05 | bencoh: every 500ms is almost OKish | 20:47 |
| DocScrutinizer05 | also aiui it passes a callback to some gtk_timeout_add () function, which - depending on the way this function works - could cancel the previous callback registered. When it does, then this is an absolutely correct way to implement a 500ms timeout | 20:50 |
| DocScrutinizer05 | however when it doesn't cancel the previous check_exit_timeout_cb registration then that's terribly broken indeed | 20:51 |
| DocScrutinizer05 | I guess the real problem happens somewhere else, prolly in some busy loop that polls for input | 20:53 |
| *** mbs1337 has joined #maemo | 21:01 | |
| *** mbs1337 has quit IRC | 21:03 | |
| *** mbs1337 has joined #maemo | 21:04 | |
| *** mbs1337 has quit IRC | 21:05 | |
| bencoh | DocScrutinizer05: well according to powertop it does fix the issue | 21:05 |
| DocScrutinizer05 | what does fix which issue? | 21:06 |
| bencoh | removing this timer let the cpu go to c4 | 21:07 |
| bencoh | lets* | 21:07 |
| kerio | isn't it c0 | 21:07 |
| kerio | no wait, it goes the other way right | 21:07 |
| bencoh | yeah the other way | 21:07 |
| DocScrutinizer05 | well, randomly removing timers for sure fixes some timer-caused issues eventually, but it prolly will introduce some severe other breakage | 21:08 |
| bencoh | it doesnt break a functionality as such (and newer versions of scim have this line commented as well) .... but it wont die on sigterm anymore | 21:10 |
| bencoh | sigs are processed in another thread which updates a global var (ugly) | 21:11 |
| DocScrutinizer05 | I cannot tell for sure what's the root problem from a single line of code (in this case), but I can *guess* that the code registers 100 timer callbacks per second and never cancels a single one of them. And when push comes to pull it will register a new timer callback event when the callback function of a previous timer event gets called | 21:11 |
| bencoh | this line gets executed once and the _cb doesnt seem to register a timer .... but meh :) | 21:14 |
| DocScrutinizer05 | the line >> _check_exit_timeout = gtk_timeout_add (500, check_exit_timeout_cb, NULL); << doesn't look like it could cancel a previously registered timer, since for that it would need the _check_exit_timeout handle to that previous instance as a parameter handed to the function | 21:14 |
| *** sLumPia has joined #maemo | 21:15 | |
| *** geaaru has quit IRC | 21:16 | |
| bencoh | http://scim-for-maemo.googlecode.com/svn-history/r162/trunk/scim-1.4.7-maemo/extras/panel/scim_panel_gtk.cpp :) | 21:16 |
| *** jas4711 has joined #maemo | 21:16 | |
| DocScrutinizer05 | >> gtk_timeout_add has been deprecated since version 2.4 and should not be used in newly-written code. Use g_timeout_add() instead.<< | 21:19 |
| bencoh | it's a 5yo code ;) | 21:19 |
| bencoh | but yeah, looks like others patched it to use g_timeout_add() as well | 21:19 |
| DocScrutinizer05 | http://www.gtk.org/tutorial1.2/gtk_tut-17.html#ss17.1 mhm | 21:20 |
| DocScrutinizer05 | >>...can create a timeout function that will be called every "interval" milliseconds.<< | 21:20 |
| bencoh | hmm actually they also removed this callback as well | 21:21 |
| DocScrutinizer05 | so it's a recurring timer | 21:21 |
| bencoh | yeah it is | 21:21 |
| DocScrutinizer05 | that's pretty odd | 21:21 |
| bencoh | (that's actually what I was implying, sorry) | 21:21 |
| *** florian has joined #maemo | 21:21 | |
| bencoh | it's an ugly recurring timer to check "should I die now ?" | 21:22 |
| DocScrutinizer05 | The return value is an integer "tag" which may be used to stop the timeout by calling: | 21:22 |
| DocScrutinizer05 | void gtk_timeout_remove( gint tag ); | 21:22 |
| DocScrutinizer05 | braindamaged code | 21:22 |
| bencoh | yup | 21:22 |
| DocScrutinizer05 | HAHA >>You may also stop the timeout function by returning zero or FALSE from your callback function.<< | 21:22 |
| bencoh | I might try to update scim to 1.4.14 (part of it has been rewritten and it should behave better) | 21:23 |
| bencoh | but I cant even build 1.4.7 in sb | 21:23 |
| bencoh | I half-baked the tool from binary lib | 21:23 |
| bencoh | I wonder how it got built at first | 21:24 |
| *** at1as has joined #maemo | 21:24 | |
| DocScrutinizer05 | I'd not be surprised to find gtk do a busy loop for every instance of timer event registered via gtk_timeout_add() | 21:24 |
| *** mkaindl has left #maemo | 21:25 | |
| *** jas4711 has quit IRC | 21:26 | |
| DocScrutinizer05 | I honestly wonder why this code needs such nonsense instead of doing it right in signalhandler(int sig) | 21:34 |
| bencoh | they eventually had it write | 21:37 |
| bencoh | the author was probably on heavy drug .... or just sleep deprived ;) | 21:37 |
| bencoh | s/write/right/ : https://bugzilla.redhat.com/show_bug.cgi?id=444150 | 21:38 |
| bencoh | funny thing is we got a borked version for maemo, and people started writing a kludgy menu applet "switcher" instead of patching/looking for a patch | 21:39 |
| bencoh | (this bug ticket predates n900) | 21:39 |
| DocScrutinizer05 | if (!_panel_agent->run ()) | 21:39 |
| DocScrutinizer05 | std::cerr << "Failed to run Panel.\n"; | 21:39 |
| DocScrutinizer05 | G_LOCK (_global_resource_lock); | 21:39 |
| DocScrutinizer05 | _should_exit = true; | 21:39 |
| DocScrutinizer05 | WTF? | 21:39 |
| bencoh | exactly | 21:39 |
| bencoh | told you it was ugly | 21:40 |
| DocScrutinizer05 | this whole code has more cruft and commented-out lines of code than actually meaningful ones | 21:40 |
| DocScrutinizer05 | and this coude looks to me pretty similar to a chinese PCB | 21:41 |
| DocScrutinizer05 | code* | 21:41 |
| bencoh | :)) | 21:42 |
| bencoh | considering scim is mostly used for cjk input .... it probably is | 21:42 |
| bencoh | (or japanese code, maybe) | 21:42 |
| DocScrutinizer05 | apply random changes until it starts to work. then cut out components until it stops working. Revert last component removal. Produce | 21:42 |
| bencoh | hm no, definitely chinese, from the names | 21:43 |
| *** sLumPia has quit IRC | 21:44 | |
| DocScrutinizer05 | God, I hate such uninspired code | 21:47 |
| DocScrutinizer05 | reading it feels like drinking sour milk | 21:47 |
| *** sq-one has joined #maemo | 21:48 | |
| DocScrutinizer05 | and thinking of that code maybe running on my machine gives me a feeling like in a restaurant where I know they cook with rotten milk | 21:48 |
| DocScrutinizer05 | ugh, meeting today | 21:49 |
| *** ciroip has quit IRC | 21:53 | |
| *** ciroip has joined #maemo | 21:55 | |
| bencoh | I'm pretty sure half (most ?) of desktop software looks or looked like that at some point | 21:58 |
| bencoh | and maemo prolly isnt an exception | 21:58 |
| *** b1101 has quit IRC | 22:01 | |
| DocScrutinizer05 | I'm quite sude most of KDE looks similar, yes | 22:03 |
| DocScrutinizer05 | sure* | 22:03 |
| DocScrutinizer05 | most (core) maemo code I've seen isn't all that bad | 22:04 |
| bencoh | look at hildon-desktop then :> | 22:04 |
| DocScrutinizer05 | some stuff (hildon for example) could use some more love for parameter checking etc | 22:05 |
| bencoh | or just the fact that you cant have desktop widgets without waking cpu | 22:05 |
| DocScrutinizer05 | err wut? | 22:05 |
| bencoh | (I mean, waking cpu more than is needed) | 22:05 |
| bencoh | I spotted a few loops/condition inversion in hildon-home | 22:06 |
| bencoh | (or hildon-desktop, I dont remember where this part of the code sits) | 22:06 |
| bencoh | basically it loops through widgets and checks whether display is *inside* the loop for each widget | 22:07 |
| bencoh | and I suspect there is more | 22:07 |
| *** totalizator has quit IRC | 22:08 | |
| DocScrutinizer05 | you mean hildon executing all widget code frequently to do display updates as long as desktop is visible? well, that's not exactly nice but sort of tolerable | 22:08 |
| DocScrutinizer05 | the fact that a single segfaulting or freezing widget makes whole desktop go south is more severe | 22:09 |
| bencoh | depending on the widget it can get pretty heavy | 22:09 |
| bencoh | true, that's quite bad as well, but this is more of a design thing | 22:10 |
| DocScrutinizer05 | display update for all widgets is as well | 22:10 |
| bencoh | on a different level/of a different nature | 22:11 |
| DocScrutinizer05 | since the widgets are executed in hildon context, as simple function calls, there's no reasonable way for them to announce they don't need to update their display | 22:11 |
| DocScrutinizer05 | a widget simply returning as fast as possuble when nothing to do is the most lightweight way to handle this in this architecture | 22:12 |
| *** totalizator has joined #maemo | 22:13 | |
| DocScrutinizer05 | and anyway since the homescreen and thus the widgets are visible, there's a certain system load anyway, and particularly a certain energy consumption by backlight and mere display data bus. So a 10 wakeups per second for CPU don't really hurt | 22:13 |
| bencoh | anyway ... now to build http://tomoe.sourceforge.jp against scim in sb | 22:13 |
| bencoh | DocScrutinizer05: actually I was talking of display status check | 22:14 |
| bencoh | s/of/about/ | 22:14 |
| infobot | bencoh meant: DocScrutinizer05: actually I was talking about display status check | 22:14 |
| DocScrutinizer05 | display status check? | 22:14 |
| bencoh | "is display on" "is desktop visible" "is device unlocked" | 22:14 |
| bencoh | that kind of things | 22:14 |
| DocScrutinizer05 | that's supposed to get done in hildon | 22:14 |
| DocScrutinizer05 | makes absolutely no sense to do it in every widget | 22:15 |
| bencoh | that's done in hildon but in reverse order/in a peculiar way | 22:15 |
| bencoh | lemme find the source | 22:15 |
| DocScrutinizer05 | when display of homescreen isn't visible, not a single widget is visible, so why should hildon run any wiget code in that sitation? | 22:16 |
| DocScrutinizer05 | as soon as display status changes from invisible to visible, all widgets need to update their display content, and then every 50ms or whatever | 22:17 |
| DocScrutinizer05 | as soon as status changes from visible to not visible (aka background, or locked), hildon should stop executing +any* widget code | 22:18 |
| bencoh | hd_comp_mgr_update_applets_on_current_desktop_property | 22:18 |
| DocScrutinizer05 | every widget in turn is supposed to check early if there's actually sth to update and return when e.g. last (seconds) digit of the clock didn't change | 22:19 |
| bencoh | it goes through widgets twice and make Xlib calls whether display is on or not | 22:19 |
| *** erlehmann has quit IRC | 22:19 | |
| bencoh | which roughly means going through X11 crazy codepath | 22:19 |
| DocScrutinizer05 | I never checked that hildon code. I'm talking from mere best practice which I'd expect to see in hildon | 22:20 |
| bencoh | well ... I'd definitely love to see more best practice everywhere :) | 22:21 |
| DocScrutinizer05 | and I'm pretty sure hildon does NOT do what you say it does, when screen is locked. Otherwise my battery wouldn't stay a 5h even | 22:21 |
| bencoh | I didnt say it would really update widgets when locked, but it would do some X calls | 22:22 |
| *** qwazix_ has quit IRC | 22:22 | |
| DocScrutinizer05 | X calls are as worse as display updates | 22:22 |
| jaska | i guess i need to look up the dual bl-5j hack, my mugen is getting shorter | 22:23 |
| bencoh | DocScrutinizer05: well some widgets (hello qwb !) can do much worse ... but yeah, X calls arent free, that's my point ;) | 22:26 |
| DocScrutinizer05 | my point is that I honestly doubt they happen while screen locked | 22:29 |
| DocScrutinizer05 | if they actually do, then that's prolly a bug | 22:30 |
| bencoh | I think it does at least for XDeleteProperty | 22:30 |
| bencoh | though I didnt rebuild hildon/mb to trace that | 22:30 |
| bencoh | but then again, powertop has different output with and without widgets (be it one simple widget) | 22:31 |
| DocScrutinizer05 | that's bad | 22:32 |
| DocScrutinizer05 | at least when you talk about locked screen | 22:32 |
| bencoh | yup | 22:32 |
| DocScrutinizer05 | actually with a locked screen hildon itself shouldn't run anymore | 22:33 |
| DocScrutinizer05 | unless some idiotic widget scheduled a timer | 22:33 |
| *** konelix__ has quit IRC | 22:34 | |
| DocScrutinizer05 | you know, one of the kind that sends a signal to wake up the process on expiry | 22:34 |
| *** ult has joined #maemo | 22:35 | |
| DocScrutinizer05 | "the process" is hildon here, and of course it needs to run *all* widgets so the idiotic one has a chance to service the timer expiry | 22:35 |
| bencoh | I think I tested with DCE widget at that time | 22:36 |
| bencoh | (which behaved better than qwb, but still) | 22:36 |
| DocScrutinizer05 | whatever that is | 22:36 |
| bencoh | desktop cmd exec | 22:36 |
| *** xes has joined #maemo | 22:36 | |
| bencoh | and I checked the source as well | 22:36 |
| DocScrutinizer05 | umm well | 22:37 |
| *** ult has left #maemo | 22:37 | |
| bencoh | I stopped using widgets at that point | 22:38 |
| DocScrutinizer05 | I dunno what QBW does, but it prolly shouldn't run any timers. it has nothing that needs a timed execution | 22:38 |
| bencoh | qwb has timed functionality (as well as dce) | 22:38 |
| *** dhbiker has quit IRC | 22:38 | |
| *** bluelupo has quit IRC | 22:38 | |
| bencoh | but qwb is heavier in everything | 22:38 |
| DocScrutinizer05 | ~qbw | 22:39 |
| DocScrutinizer05 | ~qwb | 22:39 |
| *** ult has joined #maemo | 22:40 | |
| DocScrutinizer05 | it's probably an absolutely idiotic idea to implement something like a daemon that get executed 10 times per second in a widget | 22:41 |
| DocScrutinizer05 | I can't think of any such function that would need that | 22:41 |
| bencoh | it is, but ... looks like some people found it neat | 22:41 |
| bencoh | I dont understand either :) | 22:41 |
| *** at1as has quit IRC | 22:44 | |
| *** javispedro has joined #maemo | 22:46 | |
| *** goldkatze has quit IRC | 22:52 | |
| DocScrutinizer05 | I mean, sure I could integrate the fan control of my PC into xeyes.... BUT... | 22:53 |
| DocScrutinizer05 | shouldn't a widget do *only* stuff that's actually visible on display? And particularly shouldn't it STOP doing this as soon as the display isn't visible? | 22:54 |
| DocScrutinizer05 | a maemo widget isn't just an arbitrary X-app with a funny shaped window | 22:56 |
| kerio | DocScrutinizer05: X has a way to figure out whether or not you're drawn | 23:01 |
| DocScrutinizer05 | kerio: so what? | 23:03 |
| DocScrutinizer05 | you're aware that all widgets run as "hildon" ? | 23:03 |
| kerio | so even if it was an arbitrary X program, it doesn't really have an excuse to waste cpu | 23:03 |
| bencoh | :) | 23:04 |
| DocScrutinizer05 | kerio: that's completely off the point we discussed, which is timer ALARM | 23:05 |
| kerio | "shouldn't a widget do *only* stuff that's actually visible on display? And particularly shouldn't it STOP doing this as soon as the display isn't visible?" | 23:05 |
| kerio | i expect every fucking program to do that, not only widgets | 23:05 |
| DocScrutinizer05 | aha | 23:05 |
| DocScrutinizer05 | kerio: that's completely off the point we discussed, which been daemons | 23:05 |
| DocScrutinizer05 | and those for sure don't give an F that they are not visible usually | 23:06 |
| DocScrutinizer05 | lemme put it simple: you MUST NOT make an X program out of crond | 23:08 |
| *** xes_ has joined #maemo | 23:12 | |
| *** jas4711 has joined #maemo | 23:14 | |
| *** xes has quit IRC | 23:14 | |
| *** xes_ is now known as xes | 23:17 | |
| *** DrCode has quit IRC | 23:21 | |
| *** DrCode has joined #maemo | 23:22 | |
| *** alexript has joined #maemo | 23:24 | |
| *** alexript has quit IRC | 23:26 | |
| *** sq-one has quit IRC | 23:26 | |
| *** YnG has joined #maemo | 23:38 | |
| *** YnG has quit IRC | 23:40 | |
| *** louisdk has joined #maemo | 23:49 | |
| *** florian has quit IRC | 23:51 | |
| *** at1as has joined #maemo | 23:52 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!