**** BEGIN LOGGING AT Wed Jun 20 02:59:59 2012 Jun 20 07:50:46 heyho Jun 20 12:59:47 DocScrutinizer: http://enotty.pipebreaker.pl/2012/06/20/af-dbus-is-coming/ Jun 20 13:16:44 radekp: hey! So, what am i to do? My ext3 rootfs occassionally remounts read-only with your kernel... What should i use? :( Jun 20 13:16:55 (remounts after resume) Jun 20 13:22:17 PaulFertser: hi, gta02 or 04? Jun 20 13:24:45 radekp: gta02 Jun 20 13:26:06 PaulFertser: hmm no idea sorry :( i am using the same kernel for very long time now Jun 20 13:26:26 radekp: with rootfs on ext3 on uSD? Jun 20 13:26:50 PaulFertser: for me uSD and Freerunner never worked good Jun 20 13:28:11 radekp: with 2.6.29 it worked without any issues for me. And now i'm screwed :/ Jun 20 13:28:14 :( Jun 20 13:28:39 PaulFertser: i was thinking about going back to 2.6.29 for qtmoko & freerunner Jun 20 13:28:49 radekp: impossible, udev needs newer kernel. Jun 20 13:29:13 I would stay with my trusty old 2.6.29 if not for that requirement. Jun 20 13:29:18 Also, it makes no sense. Jun 20 13:29:28 hmm that's bad then... btw qtmoko on FR works without udev Jun 20 13:29:28 Bugs are to be fixed, i do not want to be stuck forever with that old version. Jun 20 13:29:40 i devtmpfs is enough Jun 20 13:30:12 I want stock debian to run there. Jun 20 13:30:26 well i have no idea about kernel development - i am doing userspace Jun 20 13:30:31 :((( Jun 20 13:31:07 i did just tons of testing and few patches backporting, but otherwise i have no idea about kernel and electronics in general... Jun 20 13:32:04 PaulFertser: buy GTA04 :) Jun 20 13:32:51 it has absolutely rocking SD card support - i am running from SD and doing crazy things and it works perfectly Jun 20 13:33:28 on Freerunner it usually took me like 2 days to corrupt SD card... Jun 20 13:33:32 radekp: i'm not sure FSO works reliable on it. Jun 20 13:33:42 radekp: i have gta04, but i have no spare uSD. Jun 20 13:33:49 And i want my gta02 to run no worse than before. Jun 20 13:34:46 Before i start experimenting. FSO is in flux nowadays. And its gta04 support seems to be not there yet. Jun 20 13:35:03 There's nothing that should really harm uSD on gta02. It worked fine for me for years. Jun 20 13:36:41 i agree - i also hate when things break... Jun 20 13:37:38 but this time i even have no idea - i never used SD card for main os - i always used NAND Jun 20 13:37:59 and used FAT for data - this worked good Jun 20 13:46:20 I've used SD since 2008 daily Jun 20 13:58:36 maybe i had bad luck on SD cards Jun 20 14:10:59 My luck with cards was ok until i upgraded : Jun 20 14:11:02 :/ Jun 20 14:15:33 pabs3: ?? Jun 20 14:16:04 DocScrutinizer51: it seems parts of dbus are moving into the kernel Jun 20 14:16:17 bwahahaha Jun 20 14:16:46 why not into systemd? ;-P Jun 20 14:17:18 thanks anyway, will look at it after work Jun 20 14:26:24 freesmartphone.org: 03morphis 07morphis/hfp * rb7f315779de3 10cornucopia/fsogsmd/src/lib/at/atcommands.vala: fsogsmd: lib: at: implement AT+CMER command Jun 20 14:26:25 freesmartphone.org: 03morphis 07morphis/hfp * rc039a500559a 10cornucopia/fsogsmd/ (src/lib/at/atcommands.vala tests/testatcommand.vala): fsogsmd: lib: at: implement test functionality for AT+CHLD command Jun 20 14:26:25 freesmartphone.org: 03morphis 07morphis/hfp * r818f10610ac8 10cornucopia/fsogsmd/src/ (7 files in 2 dirs): fsogsmd: modem_hfp_hf: implement service level connection establishment procedure Jun 20 14:26:26 freesmartphone.org: 03morphis 07morphis/hfp * rb5a496fc67e3 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/ (Makefile.am modem.vala unsolicited.vala): fsogsmd: modem_hfp_hf: implement handler for unsolicited response messages Jun 20 14:26:27 freesmartphone.org: 03morphis 07morphis/hfp * rf2d30c473f80 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/ (channel.vala modem.vala slc.vala): fsogsmd: modem_hfp_hf: move SLC handling to modem class and keep our channel unresponsible Jun 20 14:26:27 freesmartphone.org: 03morphis 07morphis/hfp * r514ccd56a143 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/modem.vala: fsogsmd: modem_hfp_hf: don't use any SMS, phonebook or call handler yet Jun 20 14:26:28 freesmartphone.org: 03morphis 07morphis/hfp * rea6809af51b4 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/modem.vala: fsogsmd: modem_hfp_hf: register a unsolicited response since we're not a "real" AT channel Jun 20 14:26:30 freesmartphone.org: 03morphis 07morphis/hfp * r451fad6893b5 10cornucopia/fsogsmd/ (8 files in 4 dirs): fsogsmd: modem_hfp_hf: implement own handler class for the indicators Jun 20 14:26:30 freesmartphone.org: 03morphis 07morphis/hfp * r856fe6b403a8 10cornucopia/fsogsmd/src/lib/bluetooth.vala: fsogsmd: lib: bluetooth: add org.bluez error domain Jun 20 14:26:30 freesmartphone.org: 03morphis 07morphis/hfp * rc429fbbb96b8 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/modem.vala: fsogsmd: modem_hfp_hf: throw errors from the org.bluez error domain and nothing else Jun 20 14:26:30 freesmartphone.org: 03morphis 07morphis/hfp * r609477d5b405 10cornucopia/fsogsmd/src/ (4 files in 2 dirs): fsogsmd: modem_hfp_hf: move indicator type definitions to core library as they are pretty std. 27.007 Jun 20 14:26:33 freesmartphone.org: 03morphis 07morphis/hfp * r904056b859cc 10cornucopia/fsogsmd/src/plugins/modem_hfp_hf/ (indicators.vala modem.vala unsolicited.vala): fsogsmd: modem_hfp_hf: update indicator status handling Jun 20 14:26:50 heyho Jun 20 16:59:03 jake42: ping Jun 20 17:12:45 morphis: pong Jun 20 17:12:55 freesmartphone.org: 03morphis 07cornucopia * r56d1798ab8d0 10/fsogsmd/ (12 files in 11 dirs): Jun 20 17:12:55 freesmartphone.org: fsogsmd: don't use /tmp for data that needs to be persistent as default anymore, fixes #693 Jun 20 17:12:55 freesmartphone.org: /tmp is mounted on most distributions as tmpfs so data is not persistent on reboot. Jun 20 17:12:55 freesmartphone.org: /var/tmp is safe to be used for data that should stay persistent accross a reboot. Jun 20 17:14:20 jake42: one moment Jun 20 17:14:40 morphis: sure :) Jun 20 17:18:37 freesmartphone.org: 03morphis 07cornucopia * r9ff692bb28e5 10/fsogsmd/ (12 files in 11 dirs): Jun 20 17:18:37 freesmartphone.org: fsogsmd: don't use /tmp for data that needs to be persistent as default anymore, fixes #693 Jun 20 17:18:37 freesmartphone.org: /tmp is mounted on most distributions as tmpfs so data is not persistent on reboot. Jun 20 17:18:37 freesmartphone.org: /var/tmp is safe to be used for data that should stay persistent accross a reboot. Jun 20 17:18:37 freesmartphone.org: See http://0pointer.de/blog/projects/tmp.html for more details on the /tmp story. Jun 20 17:26:23 yeah, closing trac tickets per git commit is really nice: http://trac.freesmartphone.org/ticket/693#comment:2 Jun 20 17:26:57 jake42: about the bug you reported for FSO, #689 Jun 20 17:27:10 you can reproduce the described problem? Jun 20 17:31:34 morphis: in a newer version? Jun 20 17:31:42 in general Jun 20 17:32:52 morphis: it happens everytime when receiving a sms Jun 20 17:33:04 ok Jun 20 17:33:10 which version of FSO you have on your device? Jun 20 17:35:17 jake42: if it's latest shr-core can you please try to set sms_storage_dir = /var/tmp/fsogsmd/sms/ in fsogsmd.conf? Jun 20 17:35:43 morphis: yep also in latest Jun 20 17:35:46 i'll try Jun 20 17:35:59 jake42: can you give me to complete package version of fsogsmd? Jun 20 17:39:13 morphis: I'm using latest core and some old (040). Jun 20 17:39:23 I see it in both Jun 20 17:40:49 one moment for the exact versions Jun 20 17:42:16 ok Jun 20 17:44:20 oldone: fsogsmd - 1:0.10.0+gitr33+76a784884647eba46abf4c850d45222e555cdec5-r0.0 Jun 20 17:46:12 jake42: you see that the SMS receives twice and the failed +CNMA too? Jun 20 18:15:22 freesmartphone.org: 03morphis 07cornucopia * r5940e2bbdf1d 10/ (28 files in 28 dirs): Bump required vala version to 0.16.0 Jun 20 18:15:23 freesmartphone.org: 03morphis 07cornucopia * r55b1b4501ce1 10/fsotdld/src/plugins/source_ntp/plugin.vala: fsotdld: source_ntp: use owned variable instead of unowned due to binding updates in 0.16 Jun 20 18:27:38 freesmartphone.org: 03morphis 07cornucopia * r407ace07977b 10/RELEASE-TODO: Update RELEASE-TODO list, fixes #690 Jun 20 18:32:53 DocScrutinizer51: hi :) I might have asked about this before, but i can't remember the answer: what are the ferrite beads on the laptops' wallchargers for? Jun 20 18:43:27 PaulFertser: to avoid skin waves from psu in PC move to mains, or vice versa Jun 20 18:45:02 basically a RF thing Jun 20 18:47:06 DocScrutinizer51: that's an obvious answer :) But what is the measureable effect? Also, the bead is between the laptop and the real powerful impulse PSU, not between the PSU and the mains. Jun 20 18:49:12 morphis: recent one: fsogsmd - 2:0.11.3.r1.0 Jun 20 18:51:23 ok Jun 20 18:59:22 jake42: you see that the SMS receives twice and the failed +CNMA too? Jun 20 19:05:00 the real PSU is probably meant to have internal shielding & beads. the PC however shall not use the cable as an antenna Jun 20 19:05:10 PaulFertser: Jun 20 19:06:12 or even complete mains network Jun 20 19:06:49 morphis: with the config change I still have the failed +CNMA Jun 20 19:07:06 on latest shr Jun 20 19:07:47 DocScrutinizer06: that's strange because i see so many devices that integrate an impulse PSU inside but only laptops have that extra bead. Jun 20 19:08:31 quite rarely Jun 20 19:08:49 jake42: but SMS message are not displayed again after reboot? Jun 20 19:09:06 none of my laptop psu bricks has any Jun 20 19:09:22 morphis: they are display again Jun 20 19:09:26 indeed Jun 20 19:09:33 ok Jun 20 19:09:38 ooh, actually the unoiversal one has Jun 20 19:09:47 morphis: but not in the old version Jun 20 19:10:07 jake42: can you try to send a new SMS to the device and tell me if it gets displayed again too Jun 20 19:10:13 jake42: really? Jun 20 19:10:15 though they should not even be in the sim storage Jun 20 19:11:12 morphis: sure, I would just need to reboot and see if I get the last one displayed too? Jun 20 19:11:14 #pausorry, I dunno why some manufs do that Jun 20 19:11:20 jake42: yes Jun 20 19:11:22 dafaq Jun 20 19:11:26 PaulFertser: ^^^ Jun 20 19:11:59 DocScrutinizer05: ok, thanks a lot for the clarifications! Jun 20 19:12:50 you might recall we has similar beads on gta02 psu Jun 20 19:13:24 nobody knows why they were there, I'd bet Jun 20 19:13:34 And even the majority of "good" plain usb cables have that. Jun 20 19:13:43 nah Jun 20 19:13:52 some extremely expensive ones Jun 20 19:14:08 The one that came with gta02 had :) Jun 20 19:14:11 freesmartphone.org: 03morphis 07specs * rd08536cde197 10/html/index.html: Include org.freesmartphone.GSM.VoiceMail API page in our index, fixes #697 Jun 20 19:14:17 some extremely expensive onesard to find any such critter nowadays Jun 20 19:14:27 tzzzz Jun 20 19:14:34 wtf is going on? Jun 20 19:14:46 hard to find any such critter nowadays Jun 20 19:14:55 DocScrutinizer05: i guess some folks who do emi compatibility testing can probably explain the reason, but meh. :) Thanks again! :) Jun 20 19:15:14 yw Jun 20 19:16:29 N900 reduces FM-TX power when on charger, to not exceed the regulatory limit (on some 1.5 nano(!)Watt) Jun 20 19:17:03 due to USB cable acting as antenna Jun 20 19:17:24 same rationale might apply for WLAN, BT Jun 20 19:18:43 morphis: none of the messages are dislayed after booting now Jun 20 19:18:55 and for sure for those crappy laptops that don't shield their 100W@1.1V CPU regulators Jun 20 19:19:02 jake42: ok Jun 20 19:19:09 but log still shows failing +CNMA? Jun 20 19:20:21 I mean, no kidding! figure the core voltage and max transient power consumption of an intel CPU Jun 20 19:20:37 then calculate the current! Jun 20 19:20:47 :-O Jun 20 19:22:18 jake42: can you delete the messages from your SIM card and then send+received a new message and verify that the failing +CNMA is still there? Jun 20 19:23:01 morphis: failing +CNMA only happens when a message comes from the network not when rebooting Jun 20 19:23:25 ok Jun 20 19:23:40 but can you verify that still the case when there are no messages on the SIM card? Jun 20 19:24:12 morphis: now I just got a message by chance and it didn't display the second one beause of: Jun 20 19:24:26 2012-06-20T21:22:58.509901Z [WARN] FsoGsmAtSmsHandler <262012146010423>: Ignoring already seen SMS Jun 20 19:25:01 morphis: I'll delete the messages and veryfy Jun 20 19:25:07 s/veryfy/verify Jun 20 19:25:26 jake42: if a message is already on SIM, in storage and acknowledge it should not get displayed again Jun 20 19:26:00 if it's on SIM, in storage and not acknowledged it should get displayed only once Jun 20 19:26:18 yes Jun 20 19:26:57 though it should be on SIM, in storage in the first place if I get it right Jun 20 19:27:55 s/should/shouldn't/ Jun 20 19:27:55 jake42 meant: though it shouldn't be on SIM, in storage in the first place if I get it right Jun 20 19:30:54 or should it? Jun 20 19:34:45 morphis: still seeing +CNMA failing on receiving message with SIM storage empty Jun 20 19:39:59 I still fail to get the point of storing SMs to SIM Jun 20 19:40:13 DocScrutinizer05: they should be stored Jun 20 19:40:26 says who? Jun 20 19:41:15 the intend is to not store them, though (probably) the software fails at doing so Jun 20 19:41:31 as it can't ack incoming messages Jun 20 19:41:35 the sw as in...? Jun 20 19:41:45 and the modem then stores them on SIM Jun 20 19:41:53 that depends Jun 20 19:41:55 thats what I'm understanding Jun 20 19:42:03 sw as in fsogsmd Jun 20 19:42:19 iirc you can set up modem to store on SIM or deliver instantly Jun 20 19:42:26 yes Jun 20 19:42:32 and it's set to diliver instantly Jun 20 19:42:38 which it does Jun 20 19:42:54 I store SMSes to SIM so that I can get delivery information Jun 20 19:43:03 well, and for unknown reasons fsogsmd fails Jun 20 19:43:04 (outgoing SMSes) Jun 20 19:43:15 though fsogsmd can't ack (+CNMA fails) Jun 20 19:45:31 lindi-: I'd guess you should receive SMS-delivery-notifications for SMS sent directly without storing them, as well Jun 20 19:53:03 morphis: now I got a message which was only stored in SIM and not delivered directly Jun 20 19:53:29 maybe thats related to sending a message shortly before that Jun 20 20:01:58 DocScrutinizer05: but how would it identify which SMS was delivered? Jun 20 20:02:12 DocScrutinizer05: now it returns index to the SIM storage Jun 20 20:02:59 cu Jun 20 20:34:01 lindi-: the raw data SMS ack that's sent by carrier for sure has no index into SIM storage Jun 20 20:34:13 iirc it has a generic index Jun 20 20:37:25 SHR: 03Martin.Jansa 07shr-chroot * r00b0ec164d18 10/ (360 files in 31 dirs): system upgrade Jun 20 20:37:26 which - surprise surprise - is the one you've set into index/ID field of original SMs you send Jun 20 20:39:22 DocScrutinizer05: yes but I'm using AT Jun 20 20:40:01 DocScrutinizer05: I don't know any other way with FR Jun 20 20:44:39 unrelated Jun 20 20:45:18 I'd think most SMS are sent via AT protocol Jun 20 20:46:17 sssince there's no dedicated SMs channel Jun 20 21:16:45 DocScrutinizer05: do you know how to get the delivery information with AT on FR without storing SMS on SIM? Jun 20 21:23:52 SHR: 03shr-devel 07buildhistory * r8acae0be5b98 10/packages/armv4t-oe-linux-gnueabi/ (14 files in 14 dirs): packages: Build 201206202259 of shr 20120620 for machine om-gta02 on opmbuild Jun 20 21:26:05 SHR: 03Martin.Jansa 07meta-smartphone * r26924b85fed2 10/meta-fso/recipes-freesmartphone/ (14 files in 3 dirs): meta-fso: bump PR for stuff depending on vala Jun 20 21:34:01 lindi-: I know I once read about it Jun 20 21:34:31 st like PDU mode Jun 20 21:51:28 lindi-: from 1st cursory read, this seems to be the link for you: http://www.developershome.com/sms/operatingMode.asp Jun 20 21:53:31 lindi-: >>Although it is easier to use AT commands in SMS text mode, it supports fewer features of SMS messaging than SMS PDU mode. This is because you do not have complete control over the header values and message body in SMS text mode. Some tasks, although can be done in text mode, require the programmer to have knowledge about PDU mode and TPDU. For example, to request a status report from SMSC in SMS text mode, you have Jun 20 21:53:33 to set bit 5 of the first octet of the SMS-SUBMIT TPDU to 1 by the AT command +CSMP (command name in text: Set Text Mode Parameters)<< Jun 20 21:56:21 if i remember well extended charset also required pdu mode Jun 20 21:57:38 http://www.developershome.com/sms/cpmsCommand.asp Jun 20 21:57:51 GNUtoo-hplaptop: yep Jun 20 22:00:09 SR. It refers to the status report message storage area. It is used to store status reports. Jun 20 22:00:19 TA. It refers to the terminal adaptor message storage area. Jun 20 22:02:49 http://www.developershome.com/sms/sendSmsByAtCommands.asp Jun 20 22:05:27 >>Note: To keep things simple in the above examples, we assume that the same message storage area is used by the AT commands +CMSS, +CMGW, +CMGD and for receiving SMS messages. But this may not be true in real situations. To learn how to set the message storage areas to be used by different SMS operations, please refer to the earlier section "Preferred Message Storage (AT+CPMS)" of this SMS tutorial.<< Jun 20 22:14:44 DocScrutinizer05: but I am using PDU mode already, isn't everyone? Jun 20 22:16:41 http://www.developershome.com/sms/cmgrCommand.asp Jun 20 22:18:36 DocScrutinizer05: ah so message storage area is something that is not in sim? Jun 20 22:19:00 there are several message storage areas Jun 20 22:19:20 TA is "outside modem" Jun 20 22:19:37 there's also "modem storage" and "SIM" Jun 20 22:19:42 ah so the modem is not going to write it to some flash Jun 20 22:19:54 depends Jun 20 22:20:05 not all modems work same way regarding that Jun 20 22:20:16 some do not offer this, some do not offer that Jun 20 22:21:00 ok but you don't know about FR? Jun 20 22:21:14 nope Jun 20 22:21:29 ok, I guess that explains why people use it like this, they don't know any other way Jun 20 22:21:57 but I'm quite sure it offers the most simple method, which is 'don't store at all., simply pass thru to TA" Jun 20 22:22:19 it probably also offers "store to SIM" Jun 20 22:22:31 it might not offer "store to modem" Jun 20 22:22:55 NB: >>SR. It refers to the status report message storage area. It is used to store status reports.<< Jun 20 22:23:24 it's quize a bit complicated Jun 20 22:23:32 but manageable Jun 20 22:25:22 sorry for spamming... >> Jun 20 22:25:23 The First Sub-field: First Octet of the TPDU Jun 20 22:25:25 The first sub-field is the first octet of the TPDU. It tells us several things: Jun 20 22:25:26 the type of the TPDU Jun 20 22:25:28 whether the SMSC has messages that are waiting to be sent to us Jun 20 22:25:29 whether a reply path exists Jun 20 22:25:31 whether a user data header exists in the TPDU Jun 20 22:25:32 whether a status report is requested by the sender of the SMS message<< Jun 20 22:26:08 it's all about first octet, and you control 1st octet in PDU Jun 20 22:26:19 in text mode it's limited control only Jun 20 22:26:43 http://www.developershome.com/sms/cmgrCommand3.asp Jun 20 22:34:56 http://www.google.de/search?q=sms+status+report+pdu+format Jun 20 22:36:37 http://www.diafaan.com/sms-tutorials/gsm-modem-tutorial/online-sms-status-report-pdu-decoder/ ! *top* Jun 20 22:37:26 "Reference" is the "index" I mentioned Jun 20 22:39:04 lindi-, for freerunner it supports pdu I think Jun 20 22:39:39 ah you were talking about storage methods Jun 20 22:39:42 like for phonebook Jun 20 22:39:46 like SM ME etc... Jun 20 22:42:11 you send a simple SMs, you set "request status report" bit in first octet. SMSC sends a status report PDU to you, which has a tag "i'm a status report". You already have set modem in a way that says "storage area for status reports is TA". modems sends status report PDU like in http://www.diafaan.com/sms-tutorials/gsm-modem-tutorial/online-sms-status-report-pdu-decoder/ directly to TA Jun 20 22:43:03 SHR: 03shr-devel 07buildhistory * r055b6ba57a0e 10/packages/armv4t-oe-linux-gnueabi/ (246 files in 246 dirs): packages: Build 201206202345 of shr 20120620 for machine om-gta02 on opmbuild Jun 20 22:43:19 you find matching SMS for this status report by "Reference" Jun 20 22:44:30 I admit it's a bit fuzzy and terse instruction, but it should suffice to make you scan for the right info bits Jun 20 22:45:23 yeah if I had time :) Jun 20 22:45:51 and yes, *maybe* some parts of all that aren't completely supported by calypso. Though I doubt it has limitations here Jun 20 22:53:13 or by the calypso firmware that can be replaced by osmocombb.... Jun 20 22:53:34 altough we need it to be standalone such as running on top of nuttx Jun 20 22:53:40 else no power management is possible Jun 20 23:42:46 SHR: 03shr-devel 07buildhistory * r3e78e68c736b 10/packages/armv7a-vfp-neon-oe-linux-gnueabi/ (260 files in 260 dirs): packages: Build 201206210045 of shr 20120620 for machine nokia900 on opmbuild Jun 21 00:20:56 SHR: 03shr-devel 07buildhistory * r6a326fcfbba0 10/images/crespo/eglibc/chroot-image/ (build-id image-info.txt installed-package-sizes.txt): images: Build 201206210204 of shr 20120621 for machine crespo on opmbuild Jun 21 00:44:38 SHR: 03shr-devel 07buildhistory * r364fd8f05520 10/packages/armv7a-vfp-neon-oe-linux-gnueabi/ (21 files in 21 dirs): packages: Build 201206210222 of shr 20120621 for machine palmpre on opmbuild **** ENDING LOGGING AT Thu Jun 21 02:59:58 2012