**** BEGIN LOGGING AT Fri Oct 03 02:59:57 2008 Oct 03 04:01:47 Okay, getting UTC time should be much faster now. Oct 03 04:01:55 From the GPS Oct 03 04:02:25 yay! Oct 03 04:02:40 now we just need to set the time from it *hint hint* ;) Oct 03 04:03:18 It's more or less instantaneous Oct 03 04:03:26 mickey|tw: :-) Oct 03 04:03:40 mickey|tw: You know what your tasks are for today :-) Oct 03 04:04:54 *cough* right Oct 03 04:38:12 freesmartphone.org: 03mickey 07framework * r0e81df51f0e5 10/framework/resource.py: Oct 03 04:38:12 freesmartphone.org: resource handling: if ousaged is not present at runtime, start with Oct 03 04:38:12 freesmartphone.org: the resource enabled, otherwise we have no chance to turn it on. Oct 03 04:38:12 freesmartphone.org: 03mickey 07framework * r6e9c755c6e88 10/framework/subsystems/ogsmd/ (6 files in 3 dirs): (log message trimmed) Oct 03 04:38:14 freesmartphone.org: ogsmd: classes derived from AbstractModemChannel now need the parent Oct 03 04:38:16 freesmartphone.org: 'modem' to be supplied in init (as keyword argument). Oct 03 04:38:18 freesmartphone.org: ogsmd: implement org.freesmartphone.GSM.Device methods: Oct 03 04:38:20 freesmartphone.org: * GetSimBuffersSms() -> (b) Oct 03 04:38:22 freesmartphone.org: * SetSimBuffersSms(b) -> () Oct 03 04:38:24 freesmartphone.org: Note: This is only working for TI Calypso atm., please catch up in the Oct 03 06:21:37 morning Oct 03 06:42:29 morning Oct 03 06:50:23 freesmartphone.org: 03jluebbe 07zhone * rccd603cb6407 10/src/zhone: fix typo, thanks to flyser Oct 03 07:02:21 mickey|tw, python-pyrex-native geht jetzt nicht mehr Oct 03 07:06:50 bummer Oct 03 07:07:04 guess we need to revert/fix it Oct 03 07:42:19 morning Oct 03 07:42:26 sorry Oct 03 08:18:05 hi everyone Oct 03 08:18:19 is there an easy way to restore freerunner NAND flash to factory defaults? Oct 03 08:18:30 copy NOR to NAND or something ... Oct 03 08:18:38 boot NOR and reflash Oct 03 08:18:48 si-m1: I did this Oct 03 08:18:58 it didn't work? Oct 03 08:19:03 should be loads of images up Oct 03 08:19:05 but since the env is sep., reflashing u-boot is not enough Oct 03 08:19:17 I also lost my openmoko splash screen :) Oct 03 08:19:54 I tried the following: Oct 03 08:19:58 nand erase u-boot_env Oct 03 08:20:02 nand erase u-boot Oct 03 08:20:06 dynpart Oct 03 08:20:10 dynenv set u-boot_env Oct 03 08:20:15 wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in Oct 03 08:20:23 uboot-envedit -s 262144 -D GTA02 -f environment.in -o env.new Oct 03 08:20:27 dfu-util -a u-boot_env -R -D env.new Oct 03 08:20:34 and of course flashing the latest u-boot image Oct 03 08:20:44 it actually works, but with sideffects Oct 03 08:21:00 1. no splash screen any more, I always see the last pic before power off Oct 03 08:21:32 2. booting from SD is only possible if I boot to flash first and then a hard power off (power button) Oct 03 08:21:52 so my NAND is bricked :) Oct 03 08:27:35 anyone? Oct 03 09:25:27 Hey Oct 03 10:22:55 http://lwn.net/Articles/299483/ Oct 03 10:46:54 freesmartphone.org: 03jluebbe 07framework * re2ea88b39a2d 10/framework/subsystems/ogpsd/ubx.py: ogpsd.ubx: add simple debug interface Oct 03 10:50:01 reet: did you flash the splash picture as well? Oct 03 10:55:21 Weiss: nope Oct 03 10:55:36 Weiss: how can I do that? Oct 03 10:56:57 dfu-util Oct 03 11:00:09 reet: yep, it's dead easy: http://lists.openmoko.org/nabble.html#nabble-td837466 Oct 03 11:01:37 tried that Oct 03 11:02:27 it's seems nand erase also erased some basic init code Oct 03 11:02:37 or my environment is not ok Oct 03 11:03:04 splash is not shown, booting from SD only works when booting from flash first and then hard power off Oct 03 11:03:44 is there some other parition to flash which inits the device? Oct 03 11:03:54 or maybe I just need a factory default environment ... Oct 03 11:04:12 I used the one from http://svn.openmoko.org/trunk/src/host/devirginator/environment.in ... Oct 03 11:06:45 reet Oct 03 11:06:55 flash is a separate partition Oct 03 11:07:37 alphaone, atm the screen is not turned on if an incoming call appears unless I touch the screen. Should the brightness be handled by frameworkd? Oct 03 11:08:12 quickdev: we have no rule for that in the rules yet Oct 03 11:08:16 could easily add one Oct 03 11:08:21 atm. zhone is doing that Oct 03 11:08:30 (by setting the State to BUSY on incoming call) Oct 03 11:08:48 ah, ok Oct 03 11:09:12 reet: how does your mtdparts variable look like? Oct 03 11:09:16 mickey|tw, any news on the NW DETACH thing? Just testing some things where it does not happen.. Oct 03 11:10:28 philhug: flash is a separate partition? what do you mean by that? Oct 03 11:10:40 quickdev: you mean recamping? Oct 03 11:11:09 reet: sorry, I meant 'splash' Oct 03 11:11:10 mickey|tw, releasing and registering the network Oct 03 11:11:13 quickdev: i'm afraid we have to live with that. i don't see any substantial movement in TI to fix that, considering that the Calypso is EOL Oct 03 11:11:18 :( Oct 03 11:11:27 EOL? Oct 03 11:11:47 philhug: Is there a "factory default" u-boot_env somewhere? Oct 03 11:11:58 mickey|tw, isn't that chipset used in other mobile phones? Oct 03 11:12:18 quickdev: likely Oct 03 11:12:23 philhug: let me check ... Oct 03 11:12:26 mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040) Oct 03 11:12:36 mickey|tw, would be interesting if it works there without problems Oct 03 11:12:38 quickdev: but chances are these vendors have the full source code and forked the firmware to fix it Oct 03 11:12:44 reet: looks good Oct 03 11:13:07 mickey|tw, isn't that possible for openmoko with a NDA? Oct 03 11:13:14 and binary firmware release Oct 03 11:13:28 no Oct 03 11:13:39 what's the problem? Oct 03 11:13:42 openmoko has not the full source code and will never get it Oct 03 11:14:32 Kensan__: you have to execute dynpart in u-boot, edit it with envedit (apply environment.in) and upload again.. Oct 03 11:14:44 philhug: ah ic. Oct 03 11:15:00 but where is the factory default environment.in? Oct 03 11:15:07 mickey|tw, sorry if I don't understand, but why aren't they able to get it? Oct 03 11:15:22 reet: the one in svn, I assume Oct 03 11:15:49 quickdev: bunch of reasons. Openmoko too unimportant, GSM stack is crown jewels, etc. Oct 03 11:16:00 I used http://svn.openmoko.org/trunk/src/host/devirginator/environment.in Oct 03 11:16:07 but obviously it is not quite working Oct 03 11:16:09 mickey|tw, ah, ok, thanks for clarifying Oct 03 11:16:14 should be ok Oct 03 11:16:19 mmh Oct 03 11:16:32 reet: what command did you use? Oct 03 11:16:38 the steps I did are ok too? Oct 03 11:16:49 reet: can you paste them again? Oct 03 11:16:49 nand erase u-boot_env Oct 03 11:16:52 mickey|tw, what about warranty issues? Haven't they signed a contract that things have to work? Oct 03 11:16:55 nand erase u-boot Oct 03 11:16:59 dynpart Oct 03 11:17:03 dynenv set u-boot_env Oct 03 11:17:07 wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in Oct 03 11:17:11 uboot-envedit -s 262144 -D GTA02 -f environment.in -o env.new Oct 03 11:17:15 dfu-util -a u-boot_env -R -D env.new Oct 03 11:17:21 ok, one step missing Oct 03 11:17:22 and flash u-boot image Oct 03 11:17:24 quickdev: no. to add up on that, the relationship between TI and FIC is not the best one Oct 03 11:17:32 quickdev: and Om "inherited" that... Oct 03 11:17:37 philhug: which one? :) Oct 03 11:18:09 reet: before wget, still in u-boot, do a saveenv, then "dfu-util -a u-boot_env -R -U env.old" Oct 03 11:18:13 freesmartphone.org: 03jluebbe 07framework * re727b4a7144b 10/framework/subsystems/ogpsd/ubx.py: ogpsd.ubx: use the correct dbus signature Oct 03 11:18:47 reet: and then supply "-i env.old" to envedit Oct 03 11:18:56 reet: otherwise it'll loose dynamic partitioning Oct 03 11:19:02 philhug: oh ic Oct 03 11:19:19 philhug: I think I tried something like that but get DFU error -110 or something Oct 03 11:19:27 philhug: I'll retry that later Oct 03 11:19:29 philhug: thanks Oct 03 11:19:34 ok Oct 03 11:20:43 reet: if it doesn't work, copy the mtdparts variable from your device into your environment.in Oct 03 11:22:35 guys, anyone use wikipedia on the fr? Any hints/links/advice on where to get, how to install, etc... Oct 03 11:25:04 face: http://wiki.openmoko.org/wiki/Mokopedia Oct 03 11:25:15 philhug: ok thanks Oct 03 11:25:49 mickey|tw: are there no other companies using the same chip ? Oct 03 11:26:24 FilipLinux4: well there are but as mickey said: they have full access to the source and probably fixed it in their fork. Oct 03 11:27:15 Kensan_: thanks Oct 03 11:28:06 I have to check my legal notes, but if I'm not mistaken, it is legal in my country (and most other european countries) to reverse engineer if the the supplier does not can or want to give everything needed to get the device working Oct 03 12:14:20 FilipLinux4: well reverse engineering the gsm chip would be a major undertaking which would need some specialized equipment afaik Oct 03 12:17:13 i think there could be potential for "consequences" if someone published too many details, even if they were obtained legally Oct 03 12:17:49 Weiss, what are you talking about? TI chipset? Oct 03 12:18:29 quickdev: yep: < FilipLinux4> I have to check my legal notes, but if I'm not mistaken, it is legal in my country (and most other european countries) to reverse engineer if the the supplier does not can or want to give everything needed to get the device working < Kensan__> FilipLinux4: well reverse engineering the gsm chip would be a major undertaking which would need some specialized equipment afaik Oct 03 12:18:41 NDA of Doom, etc Oct 03 12:19:16 you don't sign an nda when you buy a phone over the counter. Oct 03 12:19:23 Weiss: well the NDA concerns you if you have signed it. Oct 03 12:19:52 so if you're smart enough (and I doubt anyone is) to reverse engineer from a finished phone with absolutely no access to any proprietary information, then I'm sure there are countries where that is legal Oct 03 12:19:54 Weiss: if you work with "legally optained" information then you should be save. Oct 03 12:20:16 of course, but surely the GSM networks would get SERIOUSLY upset? Oct 03 12:20:43 Weiss: sure they would, but it wouldn't be law which would allow them to stop you, it would be might or power. Oct 03 12:20:46 Weiss: of course, but that does not mean they can sue you into oblivion Oct 03 12:21:29 my understanding is that the GSM NDA of Doom is there because the GSM network is about as stable as a bowl of blancmange, and needs impressively tight restrictions to keep it alive Oct 03 12:21:38 yup Oct 03 12:22:08 so if people started playing with things, i'd expect trouble (even if legally those people are safe) Oct 03 12:22:32 rwhitby: I have a question: in mokomakefile you source the setup-env. Raster does the same in his illume build scripts but the variables (OMDIR in particular) do not seem to be set. the variable OMDIR is used in his local.conf so it does not work out. Oct 03 12:22:47 Weiss: absolutely, but it would not be because they violated an NDA. Oct 03 12:22:59 rwhitby: would you happen to know why bitbake disregards the OMDIR variable set in setup-env? Oct 03 12:23:31 Kensan_: you need to make sure the setup-env is sourced, and that the variables are still set when bitbake is called. Oct 03 12:23:37 Weiss: yes, but the point is, that if you have not signed the NDA then you are not bound to it or any such think. Oct 03 12:24:10 true, i suppose (the problems would not be to do with the NDA) Oct 03 12:24:21 you'll still get screwed over by the government, but the charges will be conspiracy to commit terrorism, rather than violating an NDA. Oct 03 12:24:37 rwhitby: this is the script I am talking about http://trac.enlightenment.org/e/browser/trunk/TMP/oe/oe-build-illume.sh Oct 03 12:25:07 Kensan_: that should work Oct 03 12:25:29 rwhitby: with this setup-env: http://trac.enlightenment.org/e/browser/trunk/TMP/oe/setup-env Oct 03 12:26:14 rwhitby: hm yes, that's why I am so confused: it doesn't. If I use these scripts I have to define OMDIR in local.conf seperately or it won't work. Rather confusing to me. Oct 03 12:26:39 yes, weird. Oct 03 12:27:28 rwhitby: because mokomakefile works flawlessly on the same machine, so it's not an issue with my setup/gear. Oct 03 12:27:53 rwhitby: not entirely sure what i'd be more afraid of.. :) - i can imaging heavy-handed legal proceedings which get targeted at OM just because "they seem to be responsible" (even though they're not) Oct 03 12:28:01 rwhitby: I don't know enough about bitbake and when/where local.conf is read. Oct 03 12:28:43 Weiss: sure - there would have to be a scapegoat Oct 03 12:28:59 rwhitby: fact is, that OMDIR is not set when local.conf gets processed... Oct 03 12:29:43 Kensan_: that could be your problem. In all my setup-env scripts, the values are fully expanded before exporting Oct 03 12:30:08 (mine use TOPDIR, and they unset TOPDIR at the end of setup-env to make sure it is not required in the expanded values Oct 03 12:31:10 rwhitby: hm... ok. Oct 03 12:32:01 rwhitby: so this line "export OMDIR=`readlink -f $PWD`" could actually be the culprit. I will rewrite the script and try that. Oct 03 12:33:01 rwhitby: thanks for the help. Oct 03 12:33:29 Kensan_: ah, that's why my makefiles have topdir.con Oct 03 12:33:32 topdir.conf Oct 03 12:33:39 so that local.conf can include it and have TOPDIR set Oct 03 12:34:29 rwhitby: ah so your local.conf includes topdir.conf. didn't see that. Oct 03 12:54:40 Ainulindale: shr-image needs to have tangogps-fso removed, since it no longer exists in OE Oct 03 13:03:00 freesmartphone.org: 03charlie 07framework * r5dbb2358e42b 10/ (9 files in 2 dirs): oeventsd: Added the 'while' rule (rule that can be undo) Oct 03 13:16:04 philhug: ./dfu-util -a u-boot_env -R -U env.old Oct 03 13:16:15 philhug: dfu_upload error -110 :-( Oct 03 13:16:29 philhug: cannot save u-boot env after saveenv and nand erase etc. Oct 03 14:00:24 reet: are you in NOR u-boot? Oct 03 14:03:04 reet: does "dfu-util -l" return the list of partitions? Oct 03 14:03:58 philhug: yep, NOR u-boot Oct 03 14:04:32 I think you have to go to NAND u-boot to change environment Oct 03 14:04:40 oh ok Oct 03 14:05:01 the upload fails, the kernel (on the host) reports Oct 03 14:05:03 usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110 Oct 03 14:05:18 what does dfu-util -l return? Oct 03 14:05:21 Linux 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Oct 03 14:05:35 mickey|tw, http://docs.openmoko.org/trac/ticket/1024 - the author says that this bug didn't happen with the version used some months ago, did you check that? Oct 03 14:05:36 mom Oct 03 14:05:53 dfu-util -l when in NOR? Oct 03 14:06:03 in NAND Oct 03 14:06:05 I cannot go to NAND right now :) Oct 03 14:06:15 I tried to do copy from NOR to NAND Oct 03 14:06:41 ok Oct 03 14:06:43 Found Runtime: [0x1d50:0x5119] devnum=29, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade" Oct 03 14:06:47 when in NOR Oct 03 14:06:59 but you can flash u-boot? Oct 03 14:07:02 maybe the 2.6.18 kernel does not support upload? Oct 03 14:07:03 yep Oct 03 14:07:06 but not upload Oct 03 14:07:15 that should be enough to go to NAND Oct 03 14:07:39 yep, but I cannot download the newly created NAND after nand erase ... saveenv Oct 03 14:07:39 you'll just get an empty boot menu Oct 03 14:07:53 yep Oct 03 14:08:05 you don't need to do nand erase again Oct 03 14:08:06 I try to get env.old from another worksation Oct 03 14:08:10 bad idea ;) Oct 03 14:08:20 are you in NAND? Oct 03 14:08:36 I need to restore it first :) Oct 03 14:08:49 ok Oct 03 14:08:54 just load u-boot Oct 03 14:08:59 u-boot-env should be empty Oct 03 14:09:31 so nand erase is not necessary? Oct 03 14:09:46 just dynpart, dynenv set u-boot_env, saveenv Oct 03 14:09:48 you can nand erase u-boot_env to be sure Oct 03 14:09:49 and flash u-boot Oct 03 14:09:51 ? Oct 03 14:10:05 to get a "clean" nand.... Oct 03 14:10:07 to start with Oct 03 14:10:10 dynpart/dynenv must be called in NAND Oct 03 14:10:34 nand erase the environment, that's enough Oct 03 14:10:41 ok Oct 03 14:14:08 ok, I'm in NAND now .. Oct 03 14:14:18 Found Runtime: [0x1d50:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="UNDEFINED" Oct 03 14:14:25 ./dfu-util -l Oct 03 14:14:31 now call 'dynpart' Oct 03 14:14:36 that's ok because it's not yet paritioned Oct 03 14:14:54 done Oct 03 14:14:57 and also "dynenv set u-boot_env" Oct 03 14:14:58 now Oct 03 14:15:00 saveenv Oct 03 14:15:02 and reset Oct 03 14:15:12 done Oct 03 14:15:18 go back to NAD Oct 03 14:15:19 NAND Oct 03 14:15:22 reset? Oct 03 14:15:27 and you should see the alt-names in dfu-util Oct 03 14:15:28 yes Oct 03 14:15:36 ok done Oct 03 14:15:37 did you save your environment? Oct 03 14:16:29 did it work? Oct 03 14:18:51 Found Runtime: [0x1d50:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="UNDEFINED" Oct 03 14:19:04 printenv? Oct 03 14:19:10 does it show mtdparts? Oct 03 14:19:43 yes Oct 03 14:20:20 strange Oct 03 14:20:27 but can you upload env? Oct 03 14:21:13 that should work, it worked before Oct 03 14:21:28 -U didn't work last time Oct 03 14:21:29 ah upload, let me try.. Oct 03 14:22:25 dfu_upload error -110 Oct 03 14:23:22 let me again print my "factory defaults for NAND" howto, maybe something is still wrong: Oct 03 14:23:25 "dynenv set u-boot_env" and saveenv returned no error? Oct 03 14:23:30 when in NOR: Oct 03 14:23:34 nand erase u-boot_env Oct 03 14:23:41 dfu-util -a u-boot -R -D gta02v5_and_up-u-boot.bin Oct 03 14:23:47 boot NAND: Oct 03 14:23:51 dynpart Oct 03 14:23:55 dynenv set u-boot_env Oct 03 14:24:00 saveenv Oct 03 14:24:01 reset Oct 03 14:24:12 dfu-util -a u-boot_env -R -U env.old Oct 03 14:24:16 (this does not work for me) Oct 03 14:24:25 I'll try ;) Oct 03 14:24:34 ... then merge the other environment.in Oct 03 14:24:41 and maybe flash splash screen Oct 03 14:26:38 cleared env, now in NAND with empty menu Oct 03 14:27:40 ok Oct 03 14:28:26 philhug: I missed one of your questions: < philhug> "dynenv set u-boot_env" and saveenv returned no error? Oct 03 14:28:30 philhug: nope, no errors Oct 03 14:28:55 dynenv set u-boot_env is actually restoring default env? Oct 03 14:29:17 no Oct 03 14:29:28 it tells u-boot where to look/save environment Oct 03 14:29:39 ok, and u-boot brings default env Oct 03 14:30:02 which is not stored in u-boot-env partition? Oct 03 14:30:21 ound Runtime: [0x1d50:0x5119] devnum=54, cfg=0, intf=0, alt=2, name="u-boot_env" Oct 03 14:30:21 C Oct 03 14:30:28 strange Oct 03 14:30:38 do you see any errors in kernel log? Oct 03 14:30:47 just when "uploading" Oct 03 14:30:50 but not before Oct 03 14:30:53 what's your kernel? Oct 03 14:31:04 2.6.26 Oct 03 14:31:15 ok, maybe my kernel is too old Oct 03 14:31:16 maybe it's an usb connectivity problem Oct 03 14:31:20 yep Oct 03 14:31:28 can you try without -R Oct 03 14:31:28 I'll retry later with an actual kernel Oct 03 14:31:46 and check in dmesg if your device is detected correctly Oct 03 14:31:53 ok Oct 03 14:31:59 I'll do that and keep you posted Oct 03 14:32:03 gotta go now Oct 03 14:32:17 I think it's a kernel problem with 2.6.18 being too old Oct 03 14:32:32 or maybe my nand erase bricked NAND ;-( Oct 03 14:33:19 did you only use 'nand erase partition'? Oct 03 14:33:29 or did you mess with bad block table? Oct 03 14:33:56 nand erase showed me some bad block messages Oct 03 14:34:01 ah Oct 03 14:34:07 I used nand erase as well one time Oct 03 14:34:22 then maybe you also need to recreate badblock table Oct 03 14:34:40 how? Oct 03 14:35:02 there's a command called 'nand createbbt'. BUT ATTENTION! Oct 03 14:35:15 I think it marks all blocks that don't have a specific value Oct 03 14:35:23 so read documentation first Oct 03 14:35:27 ok Oct 03 14:35:32 I'd try without it first Oct 03 14:35:43 command right after dynpart? Oct 03 14:35:45 looks like it's just some usb problem Oct 03 14:35:48 no Oct 03 14:36:02 before saveenv? Oct 03 14:36:46 no, really at the beginning. but as I said. don't try it now... Oct 03 14:36:47 :) Oct 03 14:37:08 I wont :) Oct 03 14:37:52 which u-boot did you try? Oct 03 14:38:09 ok, nand createbbt after nand erase u-boot_env when booting NAND Oct 03 14:38:14 after reading the docs :) Oct 03 14:38:49 don't you have to do 'nand erase' to erase the whole NAND? Oct 03 14:39:36 I think so, but it shouldn't be necessery Oct 03 14:39:44 as you warned ... Oct 03 14:42:14 ok thanks philhug Oct 03 14:42:34 I'll further debug this issue Oct 03 14:43:43 ok, have fun ;) Oct 03 14:43:54 thx! :) Oct 03 14:54:59 mickey|tw, here? Oct 03 15:11:55 AndreasD, have you had a look at the NW DETACH bug, the release & reconnect to network bug? Oct 03 16:18:45 quickdev: sorry no :-( I've been too busy Oct 03 16:21:03 ehm... Oct 03 16:21:09 news from shr? :D Oct 03 16:29:08 anyone know which package provides optparse python module? Oct 03 16:58:29 Hire: no news Oct 03 16:58:33 Hire: is not good news :-( Oct 03 16:58:48 :\ Oct 03 16:58:56 Hire: How are your gtk coding skillz? Oct 03 16:59:05 none :/ Oct 03 16:59:36 I can only test, find bug and do small coding Oct 03 17:00:03 We got stuck on some gtk issues, and it has almost completely stalled since then Oct 03 17:00:31 wurp2|working, talking about shr apps? dialer and gtk things? Oct 03 17:00:39 i don't have experience with it Oct 03 17:00:48 however you can talk about it on ML Oct 03 17:01:00 and/or gtk's ml Oct 03 17:01:33 I quickdev: yep Oct 03 17:01:38 er Oct 03 17:01:42 s/I // Oct 03 17:02:54 The only real reason to go with dialer3/contacts3 (as opposed to zhone) is to get the call history and quickdialing from your 2007.2 contact list Oct 03 17:03:20 Does anyone know if FSO MS3's contact manager includes a way to store contacts other than in the SIM? Oct 03 17:06:14 wurp2|working: i was literally just typing a very similar question.. Oct 03 17:09:42 * Weiss does GTK, if that's any help Oct 03 17:19:54 Weiss: Have time to devote to shr? Oct 03 17:19:55 :-) Oct 03 17:20:02 All the back end work is essentially done Oct 03 17:20:40 possibly.. what are the particular GTK issues? Oct 03 17:21:04 and how big are they? Oct 03 17:34:45 I just committed a version of my efl user interface Oct 03 17:34:58 which is an alternative to gtk Oct 03 17:36:56 I could provide packages if someone is interested in Oct 03 17:37:59 quickdev: any screenshots of what is looks like? =] Oct 03 17:38:53 freesmartphone.org: 03wessel 07fso-gpsd * r5475d4769d8c 10/ (ChangeLog Makefile.am): Removed -Wall flag from AM_CFLAGS Oct 03 17:38:53 freesmartphone.org: 03wessel 07fso-gpsd * r361be3c1c06f 10/ (ChangeLog fso-gpsd.c): Improved ANSI C99 standard compliance Oct 03 17:39:13 sicu, it looks very minimal, but there are theme files which can easily be manipulated. I'm using Edje Oct 03 17:39:40 quickdev: cool =] Oct 03 17:40:14 would be fine if someone could test an alpha Oct 03 17:42:21 quickdev: sounds interesting, might be able to give it a testrun =] but will have to wait until after work ... few hrs Oct 03 17:45:03 Hi Oct 03 17:49:51 I plan to compile a bootloader background image in the kernel itself (Gimp can save_as .c files with RLE decoding macro). This would not require to add append the image to kernel file or initrd file. Is that OK ? People could change this image by changing om/packages/linux*/files/bootloader-bg.patch Oct 03 17:50:27 write_erase, in order to save boot time? Oct 03 17:52:03 There are imho 3 thing to do with FR : 1/ Add some nice background from the power off 2/ Add a progress bar in kernel & userland 3/ Optimise driver init/device detection. Oct 03 17:52:12 I'm working on 1 & 2 at the moment. Oct 03 17:53:33 1 & 2 can optimize 3, by avoiding console writing on framebuffer, which is damned slow Oct 03 17:54:12 a worthful goal, keep on ;) Oct 03 17:55:09 but 3 requires to understand how kernel detects & initialize hardware, clean up userland (who realy need portmap for example) Oct 03 18:06:07 Ainulindale, here? Oct 03 18:13:55 sicu, probably I'll make some packages tomorrow Oct 03 18:14:30 quickdev: great, will check back in tomorrow then =] Oct 03 18:16:11 Hey alphaone Oct 03 18:16:38 hey quickdev Oct 03 18:17:16 Weiss: Sorry, work got busy Oct 03 18:17:16 alphaone, is your neo releasing and reregistering the network every minute? Or have you luck? :) Oct 03 18:17:22 And now it's lunchtime Oct 03 18:17:43 quickdev: It seems to be pretty stable here in .tw Oct 03 18:17:46 quickdev: But, does your UI fix any of the reasons we couldn't just use zhone? Oct 03 18:18:09 quickdev: You got a UI now? Oct 03 18:18:13 wurp2|working, probably not yet, what are the reasons? Oct 03 18:18:31 alphaone, yes, but it's pretty much alpha so far Oct 03 18:18:46 quickdev: Cool Oct 03 18:19:24 alphaone, btw., your patch works great Oct 03 18:19:43 quickdev: Which one? what for? Oct 03 18:19:45 :-) Oct 03 18:20:06 alphaone, sim auth (puk, pin), incoming call, and a very basic dialer Oct 03 18:20:20 based on libframeword-glib and ophonekitd Oct 03 18:20:29 quickdev: cool stuff Oct 03 18:20:47 Do you have recipies? Oct 03 18:20:52 or an image to try? Oct 03 18:22:10 alphaone, I could upload some packages - compiling from svn does not work right now because Ainu has to commit some patches Oct 03 18:23:22 quickdev: I'd like to try it if it's not too much work for you Oct 03 18:23:33 alphaone, give me your mail :) Oct 03 18:23:44