**** BEGIN LOGGING AT Sun Apr 17 02:59:58 2011 Apr 17 09:16:40 hi ! Apr 17 09:41:55 heyho Apr 17 10:17:32 JaMa: about meta-shr, what do you think about separating the recipes-freesmartphone into a own layer? Apr 17 10:18:00 JaMa: or should it merged into meta-oe anyway? Apr 17 10:46:28 mickeyl: ping Apr 17 10:46:44 mickeyl: you should take a look at this: http://cgit.freedesktop.org/telepathy/telepathy-qt4/ Apr 17 10:53:22 mickeyl: it seems to be the one we need to generate bindings for FSO and QT Apr 17 10:53:44 as telepathy seems to have pretty std. xml spec files Apr 17 10:54:30 just some own annotations like we have for FSO too Apr 17 11:05:59 morphis: it would be nice to have it in meta-oe later, but don't know if it will be allowed Apr 17 11:06:21 ok Apr 17 11:06:50 otherwise it would be good to split meta-shr into meta-shr and meta-fso to be able to use fso in other targets than only shr Apr 17 11:07:56 as my plan for the future of FSO is to make it more open and faster ready for using for other targets Apr 17 11:09:15 and for that it would be nice to have a subset in a meta-fso which is used in SHR and all other targets Apr 17 11:09:46 agreed, problem is where is the line.. Apr 17 11:09:56 currently we have many 3rdparty apps in meta-shr Apr 17 11:10:06 like intone? Apr 17 11:10:08 which can be used on any device without any problems Apr 17 11:10:11 yes Apr 17 11:10:23 ok, they should stay in SHR Apr 17 11:10:25 so those should go to meta-oe too imho Apr 17 11:10:31 or in meta-oe Apr 17 11:10:44 but if they are in meta-oe they need meta-fso Apr 17 11:10:54 and then you can even include meta-fso in meta-oe Apr 17 11:10:56 as someone using Angstrom should be able to build and use it Apr 17 11:11:19 yes.. in the end I can imagine everything except distro config in meta-oe :) Apr 17 11:11:42 and meta-shr only with distro config and .bbappends for distro overrides Apr 17 11:11:46 then we have the big fat OE repository again, right? Apr 17 11:11:54 right Apr 17 11:12:01 but with separate oe-core Apr 17 11:12:04 is that the aim of meta-oe? Apr 17 11:12:43 the aim as I understand it is to provide similar functionality then oe.dev has now on top of oe-core Apr 17 11:12:46 I understand it more the way that it is oe-core + additional parts which might be usefull for most distributions but not everything from OE Apr 17 11:12:50 ok Apr 17 11:13:05 nobody said if similar functionality is based on oe-core/meta-oe + 3-5 layers on top of it Apr 17 11:13:09 or just oe-core/meta-oe Apr 17 11:13:42 who decides what goes into meta-oe? Apr 17 11:13:47 the community? Apr 17 11:13:50 yes but as we just said fso and intone might be usefull for most distributions Apr 17 11:13:51 or the board? Apr 17 11:14:15 I think common sense Apr 17 11:14:21 ok Apr 17 11:14:30 even in policy draft there is no strict clause what can go in Apr 17 11:14:45 and meta-oe will be released as 1.0 in June too? Apr 17 11:15:00 everytime I asked koen as pull master to pull something it went in without discussion Apr 17 11:15:22 morphis: that's plan, but everybody expects few months slip I think Apr 17 11:16:05 http://lists.linuxtogo.org/pipermail/tsc/2011-March/000209.html says 2011.07 release.. Apr 17 11:16:33 so we will have a meta-oe/recipes-freesmartphone Apr 17 11:16:47 and then distro specific layers on top of meta-oe Apr 17 11:16:52 sounds ok for me Apr 17 11:17:14 as I want to provide a simple distro providing the core features of FSO Apr 17 11:17:34 and only FSO not anything else Apr 17 11:18:33 JaMa: so it would be the best way to do that with setting up a layer on top of meta-shr and later switch down to meta-oe when fso stuff and other things are merged Apr 17 11:18:55 damn it Apr 17 11:23:51 morphis_: right Apr 17 11:24:06 honestly I don't like layers at all :) Apr 17 11:25:10 JaMa: :) Apr 17 11:25:13 GarthPS: heyho Apr 17 11:25:19 GarthPS: your device is working again? Apr 17 11:26:22 JaMa: simple distro or board layers are usefill imho as it reduces the bullshit we have in OE theses for multiple machines Apr 17 11:26:34 s/it red/they red/ Apr 17 11:26:34 morphis_ meant: JaMa: simple distro or board layers are usefill imho as they reduces the bullshit we have in OE theses for multiple machines Apr 17 11:28:46 morphis_: but then you had to watch all those layers to see what bullshit they need in case you will have to add similar machine with same bullshit to new bsp layer Apr 17 11:29:17 hm Apr 17 11:33:49 imagine aa_1.0.bb in oe-core or meta-oe Apr 17 11:34:42 then first distribution finds that something extra in EXTRA_OECONF makes it better for them but not for ie distributions building only console images, so they put it ie to meta-angstrom layer Apr 17 11:35:17 then I'll find it too (reinvent the wheel) and add it to meta-shr layer Apr 17 11:35:38 and someone else notices that aa-1.1 is out and upgrades oe-core recipe to aa_1.1.bb Apr 17 11:35:50 I see the problem Apr 17 11:35:55 meta-shr and meta-angstrom, aa_1.0.bbappend will fail to apply Apr 17 11:36:07 aa_1.1 is built and installed on user devices Apr 17 11:36:08 so we should rather make meta-oe more modular but still the main source for everything Apr 17 11:36:23 someone notices and renames aa_1.0.bbappend to aa_1.1.bbappend Apr 17 11:36:38 but need also PR bump now, because wrong aa-1.1 is already on user devices Apr 17 11:36:53 maintenance hell .. Apr 17 11:36:58 but if you do PR bump in bbappend then you have to bump it everytime upstream (oe-core) bumps it Apr 17 11:37:24 or you create something like LAYER_PR and keep PKGPR=PR.LAYER_PR.DISTRO_PR Apr 17 11:37:33 btw. I get the following error with bitbake since today: http://pastie.org/1803429 Apr 17 11:37:49 sounds all too complicated too me Apr 17 11:38:00 fix /dev/shm permissions I guess Apr 17 11:38:05 hm ok Apr 17 11:38:45 morphis_: every layer adds to this complexity another level.. so oe-core/meta-oe is complicated enough already :) Apr 17 11:39:16 for most contributors oe.dev itself was already too complicated to contribute :/ Apr 17 11:40:05 and this .bbappend is currently workarounded by those shr branches in -contrib repos Apr 17 11:40:28 if I merge upstream to shr branch and forget to update .bbappend files then it's my fault Apr 17 11:41:31 but if we use upstream repos directly then I need to update .bbappend files imediately after upstream changes them, before first builder does "make update" Apr 17 11:41:52 which is bad idea as I plan 4 weeks holidays :) Apr 17 11:42:16 oh Apr 17 11:43:39 so there are no changes to shr-core for the next four weeks, good to know Apr 17 11:44:19 24.6.-15.7 Apr 17 11:44:29 but I'll be moving to new flat before Apr 17 11:44:49 and there is no internet connection now :/ Apr 17 11:45:06 so I'll be online only from work for few days Apr 17 11:45:12 ok, so we maybe should write down a roadmap for the new meta-oe/meta-shr workflow Apr 17 11:45:28 s/workflow/conversion/ Apr 17 11:45:29 morphis_ meant: ok, so we maybe should write down a roadmap for the new meta-oe/meta-shr conversion Apr 17 11:45:38 and for the workflow howto work with it Apr 17 11:47:36 I'm waiting for next tsc meeting, if they summarize ELC meeting in minutes.. because there were many important topics on agenda Apr 17 12:17:03 morphis_: hi ! yeah thx! like I big boy I did it on my own remade the lvm layout and then the doctor worked. Apr 17 12:17:58 morphis_: the good thing is that I will be able to do a video of the install process and test byt the same wya the automatic install target Apr 17 12:18:57 on a fresh device Apr 17 12:24:27 morphis_: pong Apr 17 12:25:46 yes, telepathy did something on their own, i wonder how that relates to the tool that comes with qt4 Apr 17 12:26:14 (which i have made to work by now) Apr 17 12:28:28 still it's extremely more wordy Apr 17 12:28:32 which i don't like Apr 17 12:28:36 i like brief and concise code Apr 17 12:28:59 so i will try continue to find a way to use my vala dbus code with qml Apr 17 12:29:07 s/try// Apr 17 12:29:08 mickeyl meant: so i will continue to find a way to use my vala dbus code with qml Apr 17 12:44:23 morphis_: did you have a chance to check the touchscreen-on-qte issue? Apr 17 12:47:37 hi GNUtoo|oeee Apr 17 12:47:54 hi Apr 17 12:48:07 * GNUtoo|oeee is fighting bad autorev rev in oe Apr 17 12:48:29 any news? Apr 17 12:48:52 my hdd is in fsck mode(else I have problems like fosdem's with inexpected shutdown) Apr 17 12:48:53 diving into qml, and trying to get a rokr2 running w/ fso Apr 17 12:48:58 ok Apr 17 12:49:02 any news on ISI Apr 17 12:49:08 not here Apr 17 12:49:13 ok Apr 17 12:49:28 ici non plus Apr 17 12:49:54 morphis_, hi Apr 17 12:49:55 *nod* Apr 17 12:50:09 maybe mrmoku has news Apr 17 12:50:16 yeah Apr 17 12:50:33 also, unaccelerated framebuffer is very slow on the n900. i was somewhat disappointed Apr 17 12:50:39 ? Apr 17 12:50:40 not fluid at all Apr 17 12:50:44 ah? Apr 17 12:50:49 omapfb is not good? Apr 17 12:50:54 i would have expected more given the power Apr 17 12:50:56 at least it has XV Apr 17 12:51:48 maybe with a better defconfig we could get more of it? Apr 17 12:52:59 ya, perhaps Apr 17 12:55:01 because somewhere in make ARCH=arm xconfig there was stuff about framebuffer accelerations that were left unchecked Apr 17 12:55:13 not sure if they do something for us Apr 17 12:55:29 at least we have XV Apr 17 12:55:33 XV is so great Apr 17 12:55:38 on big screens Apr 17 12:55:59 (I know it because on the bug 2.x there is a VGA/HDMI adapter) Apr 17 12:56:09 and it really makes a difference there Apr 17 12:56:59 aha fsck finished Apr 17 13:01:19 morphis_, ping me when you have some time Apr 17 13:04:30 GNUtoo: pong Apr 17 13:04:43 mickeyl: no, I am currently compiling from scratch and will afterwards Apr 17 13:04:46 morphis_, I'll PM you Apr 17 13:04:57 morphis_: ok, thanx Apr 17 13:06:45 GNUtoo: ok Apr 17 13:07:06 mickeyl: a way to intgerate vala code with QML sounds nice Apr 17 13:08:04 yeah Apr 17 13:10:47 mrmoku: Are you around? Apr 17 13:11:21 mickeyl: we can still use simple C API of our generated GLib Binding ... Apr 17 13:11:49 or even drop out a C++ GLib Binding Apr 17 13:12:03 or make a QML C bindin Apr 17 13:13:16 yes, the C ABI is the only gateway. my idea is that we have a helper that creates the glue code so we can call bidirectional. Apr 17 13:13:42 and we need to check whether the glib mainloop is properly working Apr 17 13:15:25 as when I searched around it's supported by Qt Apr 17 13:18:38 mickeyl: can you outline me shortly what are the problems with the ISI thing currently are (GNUtoo asked me if I can h?elp out) Apr 17 13:20:08 bottom line is we can't get it to reliable camp the network Apr 17 13:20:20 as whenever we try to move it to 'online' mode, the phonet link goes down Apr 17 13:20:28 ok Apr 17 13:20:36 you tried to run plain ofono on the device? Apr 17 13:20:41 yes, it works. Apr 17 13:20:56 without any additional binary blocks? Apr 17 13:21:00 yes Apr 17 13:21:25 ok Apr 17 13:21:51 ok, then it should be less complicated than with the Palm Pre :) Apr 17 13:22:20 in theory yes Apr 17 13:23:24 ok Apr 17 13:25:42 Anyone up to speed with phoneuid errors? Apr 17 13:26:02 morphis_, basically now we have a kernel that does proper power management Apr 17 13:26:21 so we only lack modem(phone calls, "GPRS", and maybe GPS) Apr 17 13:26:39 My messages app keeps crashing (on FR). It _looks_ like it gets a message with a strange variant type from the SIM. Apr 17 13:26:59 GNUtoo: So, it's almost complete then! Apr 17 13:27:14 ChristW_, not at all, modem is the big blocker Apr 17 13:27:25 I'll try to unlock it with money Apr 17 13:27:30 I hope it works Apr 17 13:27:56 GNUtoo: That was meant to be sarcastic... Apr 17 13:28:15 Got to go,, will check back later... Apr 17 13:39:07 mickeyl: what about moving freesmartphone.org, should we move it to the amethyst? Apr 17 13:39:49 ya, i don't see any other option atm. Apr 17 13:39:53 ok Apr 17 13:40:22 with creating a virtual machine there? Apr 17 13:40:42 yeah Apr 17 13:40:58 there is already software installed for this? Apr 17 13:41:17 or how is the structure of the amethyst? (maybe we should discuss this in detail) Apr 17 13:41:22 (and in private) Apr 17 13:41:56 i don't think there is any virtualization installed yet Apr 17 13:43:02 ok Apr 17 13:43:17 are you online with jabber? Apr 17 13:43:35 amethyst we can use however we want, the physical machine is mine, however the connectivity is being paid by Harald Welte, and he is the client of the computing centre, so it's always a hassle, if something goes wrong Apr 17 13:44:10 hm Apr 17 13:47:14 hmm, does anyone have a t9 kernel driver or something like that? Apr 17 13:47:29 or a keypad tty driver Apr 17 13:50:15 hmm, nm, the keypad is not mapped anyways Apr 17 13:59:03 1970-01-01T00:22:50.469482Z [ERROR] fsodeviced : Could not call ifconfig wlan0 up! Apr 17 13:59:03 1970-01-01T00:22:50.483795Z [ERROR] fsodeviced : Could not call iwconfig wlan0 power! Apr 17 13:59:09 what could be the cause? Apr 17 13:59:14 I'll look at the code Apr 17 13:59:19 maybe /sbin/ Apr 17 14:04:13 hmm, i didn't write that Apr 17 14:04:16 dos1 did Apr 17 14:04:33 GNUtoo: what device is that btw? Apr 17 14:04:42 it looks odd, he's not parsing the result, but still calling exec Apr 17 14:04:45 my wifi on FR broke today too and I haven't changed kernel :) Apr 17 14:05:50 lindi-, n900, under SHR Apr 17 14:05:54 ok Apr 17 14:05:59 probably unrelated then Apr 17 14:06:03 I'll try to fix Apr 17 14:06:11 works fine on om-gta02 Apr 17 14:44:09 mrmoku, hi Apr 17 14:44:11 mrmoku, http://scap.linuxtogo.org/ Apr 17 14:44:33 *I disabled SHM in xorg.conf like that: Apr 17 14:44:45 Section "Extensions" Apr 17 14:44:45 Option "MIT-SHM" "no" Apr 17 14:44:45 EndSection Apr 17 14:44:51 *I modified that file: Apr 17 14:45:02 /usr/share/mokomaze/config.json Apr 17 14:45:10 *I launched like that: Apr 17 14:45:22 mokomaze -i keyboard Apr 17 14:48:26 I also forgott to mention that I disabled the vibrator Apr 17 15:24:06 GNUtoo: you will take care about the funding website? Apr 17 15:24:27 what should I do? Apr 17 15:28:45 we need a wiki page or a website where we descibre the motivation behind this funding Apr 17 15:28:57 whats the result and so on Apr 17 15:29:13 so we can motivate people to give something Apr 17 15:29:23 ok Apr 17 15:29:27 imho a FSO wiki page should be enough Apr 17 15:29:31 ok Apr 17 15:29:34 then I can do that Apr 17 15:30:33 ok Apr 17 15:56:17 [fsodevice.kernel_idle] makes fsodevieced segfault on n900 Apr 17 15:56:22 in fsodeviced.conf Apr 17 16:03:58 mickeyl, can I push that: http://www.pastie.org/private/mutpdmsl1kybejglerzrfa Apr 17 16:06:08 GNUtoo: yes. the code is still suboptimal, but that might improve it a bit Apr 17 16:06:28 what should I do to fix the subobtimal code? Apr 17 16:06:39 (it improves a lot: it makes it work) Apr 17 16:06:54 the best way would be to stop calling binaries Apr 17 16:07:04 how? Apr 17 16:07:11 you've got some replacement in some libs? Apr 17 16:07:12 use networking code instead Apr 17 16:07:17 ok good idea Apr 17 16:07:18 no, not for everything Apr 17 16:07:25 for ifconfig ? Apr 17 16:07:32 iwconfig is not needed anymore Apr 17 16:07:32 yes, should be in libfsosystem Apr 17 16:07:45 or so the plan is, for bisectability: Apr 17 16:07:49 1)push /sbin Apr 17 16:07:53 2)rework it Apr 17 16:07:53 ? Apr 17 16:07:57 yes, sounds good Apr 17 16:08:01 ok thanks Apr 17 16:08:01 * mickeyl -> dinner Apr 17 16:11:56 Guten Apetit! Apr 17 16:12:15 (too late I guess ;-) ) Apr 17 16:17:52 freesmartphone.org: 03GNUtoo 07cornucopia * rb526bcc33eeb 10/fsodeviced/src/plugins/powercontrol_ifconfig/plugin.vala: Apr 17 16:17:52 freesmartphone.org: fsodeviced: powercontrol_ifconfig: make it bring up the network interface Apr 17 16:17:52 freesmartphone.org: Without that fix we have: Apr 17 16:17:52 freesmartphone.org: [ERROR] fsodeviced : Could not call ifconfig wlan0 up! Apr 17 16:17:52 freesmartphone.org: [ERROR] fsodeviced : Could not call iwconfig wlan0 power! Apr 17 16:17:53 freesmartphone.org: Signed-off-by: Denis 'GNUtoo' Carikli Apr 17 16:30:02 * GNUtoo got an idea Apr 17 16:30:20 did someone tried registering without lowlevel_nokia900? Apr 17 16:59:26 mickeyl, are you back Apr 17 16:59:28 mrmoku, ping Apr 17 16:59:39 * GNUtoo needs help Apr 17 17:01:22 what'sup? Apr 17 17:02:46 mickeyl, I got an idea to try for the modem Apr 17 17:03:00 could it be the nokia900_poweron plugin's fault? Apr 17 17:03:04 could we try without it? Apr 17 17:03:13 unlikely, but worth a try Apr 17 17:03:16 in a previous not messed state Apr 17 17:03:18 sure, just power it on manually Apr 17 17:03:25 like when it really tried to register Apr 17 17:03:27 yes but how? Apr 17 17:03:34 there's some shell script Apr 17 17:03:38 ok Apr 17 17:03:40 dunno where i got it from Apr 17 17:03:45 but it features --enable and --disable Apr 17 17:03:45 pastebin it Apr 17 17:03:50 it's actually a binary Apr 17 17:03:53 ok I think I already get it Apr 17 17:03:56 so i can't paste it Apr 17 17:04:03 https://elektranox.org/n900/libisi/power.html Apr 17 17:04:09 I've modified that Apr 17 17:04:14 but still I can't pass level1 Apr 17 17:04:17 ya, that could be it Apr 17 17:04:34 /GISI/Netlink/Bringup: ** (./testping:528): DEBUG: testping.vala:74: netlink status for modem 0x19823a0 (phonet0) now PN_LINK_DOWN Apr 17 17:05:48 yo, same old crap Apr 17 17:06:27 ok Apr 17 17:06:34 if you're adventurous you could try with the old libisi stuff, would be interesting to see whether this makes a difference. Apr 17 17:06:40 ok Apr 17 17:06:51 you mean what exactly? Apr 17 17:06:58 get it up with libisi? Apr 17 17:07:00 yes Apr 17 17:07:05 making anything work :D Apr 17 17:07:52 but the way it's written, it shouldn't work at all... it simultaneously calls listproviders _and_ register and everytime i do that i got a 'busy' error Apr 17 17:08:15 but apparantly sre doesn't work on it anymore or did you hear something? Apr 17 17:08:21 ok Apr 17 17:08:31 no Apr 17 17:08:35 I didn't eared from sre Apr 17 17:10:16 still down Apr 17 17:10:18 I miss something Apr 17 17:11:09 phonet? Apr 17 17:11:24 you need to do the phonet dance before bringing the modem up Apr 17 17:13:39 yes Apr 17 17:13:43 I did it Apr 17 17:14:05 phonet -a 0x6C -i phonet0 Apr 17 17:14:05 pnroute add 0x00 phonet0 Apr 17 17:14:05 ip link set dev phonet0 up Apr 17 17:18:42 ok now I got it Apr 17 17:18:45 thanks to that: Apr 17 17:18:49 http://www.mail-archive.com/ofono@ofono.org/msg03770.html Apr 17 17:18:54 manually using shell Apr 17 17:18:58 I'll try real tests now Apr 17 17:22:18 so sre's binary is wrong? Apr 17 17:27:12 maybe Apr 17 17:27:25 but maybe you have a modified binary Apr 17 17:27:30 sre's thing was for 2.6.28 Apr 17 17:27:35 mrmoku, found something better Apr 17 17:27:38 but I can't find it Apr 17 17:42:35 hey Apr 17 17:42:56 GNUtoo: do you know where's the source code for shr connection manager ? Apr 17 17:43:05 no idea Apr 17 17:43:16 maybe on shr's source code repo? Apr 17 17:43:26 but I've no idea on what you're talking about Apr 17 17:43:58 the program that has connect to gprs button Apr 17 17:45:02 1970-01-01T00:02:43.010130Z [CRITICAL] fsogsmd : GLib : file mediators.c: line 1557: uncaught error: (null) (free_smartphone_gsm_error-quark, 2) Apr 17 17:45:06 GRRRRR Apr 17 17:45:16 ah I know it's from dbus Apr 17 17:45:21 but that's all I know Apr 17 17:45:26 try mdbus -s for SHR thing Apr 17 17:45:37 but if you only want to get your button recognized it's easier Apr 17 17:45:43 look in fsodeviced.conf in that case Apr 17 17:45:55 GNUtoo: and particularly I am talking about its lack to show the correct error on non-registered status Apr 17 17:46:17 ah ok Apr 17 17:46:25 no idea, the shr repo should be at: Apr 17 17:46:34 http://git.shr-project.org/git/ Apr 17 17:46:44 GNUtoo: mickey added a mechanism to give dbus error when an application tries to connect to gprs while gsmd is not connected to network Apr 17 17:46:56 ok Apr 17 17:46:58 I know Apr 17 17:47:05 GNUtoo: it seems like the shr connection settings program does not recognize this error. Apr 17 17:47:08 but I didn't know how it worked Apr 17 17:47:10 ok Apr 17 17:47:17 GNUtoo: instead the connect button will just 'freeze' Apr 17 17:47:21 leaving the user with no clue. Apr 17 17:47:39 ah ok Apr 17 17:47:42 try mdbus -s Apr 17 17:47:52 to know the program name Apr 17 17:47:59 and then clone the respective program Apr 17 17:48:06 *git clone Apr 17 17:49:19 maybe somebody on the chan can help out there ? Apr 17 17:49:59 me too Apr 17 17:50:14 I'm getting quite desesperated not succeding to reproduce the clean state Apr 17 17:50:23 1970-01-01T00:07:33.017608Z [DEBUG] fsogsmd : GLib : gisicomm.vala:900: query status done, error = 224 Apr 17 17:50:28 clean state of what ? Apr 17 17:50:34 modem for n900 Apr 17 17:50:43 I want to try a theory Apr 17 17:50:45 and can't Apr 17 17:50:51 mrmoku, please appear Apr 17 17:50:54 what exactly does clean state mean in modem context ? Apr 17 17:50:56 * GNUtoo summon mrmoku Apr 17 17:51:01 nothing Apr 17 17:51:18 just something that isn't too much recent and that doesn't segfault or quark Apr 17 17:51:32 or quit Apr 17 17:51:35 or something like that Apr 17 17:51:39 something to try Apr 17 17:51:43 shr-wizard.git Apr 17 17:51:45 The SHR fist time wizard Apr 17 17:52:03 this program has large timeouts Apr 17 17:52:19 on my htcleo it takes ages to finish Apr 17 17:52:38 maybe it waits for network registration (which takes long on the device. known problem) Apr 17 17:52:53 GNUtoo: how long does it take for htcdream to register to network in shr ? Apr 17 17:53:09 long Apr 17 17:53:15 interesting ! Apr 17 17:53:33 I suspected it might be related to newer qualcomm modems only Apr 17 17:53:37 ok Apr 17 17:53:49 because I can't remember to see the problem with kaiser and kovsky Apr 17 17:54:55 anyway I can't tell, I always skip the first time wizard Apr 17 17:55:07 at what poing is Cotulla? Apr 17 17:55:18 university learning stress Apr 17 17:55:21 :( Apr 17 17:55:46 GNUtoo: do you think we can improve qualcomm network registration time ? Apr 17 17:55:56 GNUtoo: imho it's usability blocker Apr 17 17:56:59 tada http://git.shr-project.org/git/?p=shr-settings.git;a=blob;f=shr_settings_modules/shr_gprs.py;hb=HEAD Apr 17 17:57:40 __author__ = "hiciu, dos, Toaster`" Apr 17 17:57:53 ~seen Toaster Apr 17 17:57:57 toaster <~Toaster@piratenpartei/jupi/Toaster> was last seen on IRC in channel #webos-internals, 434d 20h 29m 56s ago, saying: 'and, sorry, my english is quite bad, i know :\ what exactly do you mean reality9110?'. Apr 17 17:58:11 :'-( Apr 17 17:59:25 to find out any potential delays, try on the AT layer, then on fsogsmd layer Apr 17 17:59:35 if it's already long on the AT layer, you can stop looking Apr 17 18:00:48 mickeyl: to seek potential delay on AT layer you mean connect to the network by sending the according AT command to the modem manually with fsogsmd ? Apr 17 18:01:35 shr_settings_modules/shr_gprs.py:212 " # This needs expansion, error reason etc..." Apr 17 18:01:43 :) Apr 17 18:01:46 dcordes: without fsogsmd Apr 17 18:01:54 first layer is AT, doesn't get more barebones Apr 17 18:02:03 sorry.. s/with/without/ Apr 17 18:02:05 if it is snappy there, move on to the 2nd layer, and invoke dbus commands Apr 17 18:02:18 if it is still snapy there, move on to the 3rd, etc. Apr 17 18:02:25 ok Apr 17 18:03:29 * dcordes needs to install minicom Apr 17 18:03:48 nah Apr 17 18:03:49