**** BEGIN LOGGING AT Sat Jan 12 02:59:59 2013 Jan 12 17:30:40 My UI finally got the ability to show the neighbour cells information: http://paulfertser.info/files/fso-el-screenshots/monitor.png :) Jan 12 17:41:24 Hm, i guess "time alignment is useless", "time advance" is a bit interesting but is available only for the serving cell. Jan 12 18:09:22 GNUtoo-x60: hi :) i can't resist to boast a bit http://paulfertser.info/files/fso-el-screenshots/monitor.png :) Jan 12 18:09:56 wow, it runs stock fso right? Jan 12 18:10:01 no osmocombb involved? Jan 12 18:12:50 GNUtoo-x60: yes, that's just calypso's EM21/EM23, supported by FSO since ages Jan 12 18:13:59 ok Jan 12 18:14:17 how much RAM does the calypso have on the openmoko? Jan 12 18:14:23 like internal RAM Jan 12 18:14:31 and what's EM21/EM23? Jan 12 18:16:05 GNUtoo-x60: those are undocumented stock calypso firmware commands to get serving cell info and neighbour cells info Jan 12 18:16:15 GNUtoo-x60: unfortunately, i have no idea about the RAM Jan 12 18:16:15 ah ok Jan 12 18:16:52 basically I'd like to make use of some more RAM on the openmoko's calypso to have in nuttx nsh and layer1 at the same time Jan 12 18:17:08 dos1: hi, please, i want to talk about opimd :) Jan 12 18:17:25 GNUtoo-x60: i know :) You're doing so much on so many fronts. Jan 12 18:18:24 ah you're aware that I got layer1 + sercomm standalone but that sercomm is too slow when used with layer1? Jan 12 18:20:04 GNUtoo-x60: no, i didn't know you finally tried that on FR. Jan 12 18:20:18 PaulFertser, on c155 for now Jan 12 18:20:21 But you wanted to have a full stack on calypso since long time ago Jan 12 18:20:27 yes Jan 12 18:21:06 btw you should tell openBmap people about EM21/EM23 Jan 12 18:21:34 GNUtoo-x60: they're using that, probably existance of those commands was what started the openbmap project. Jan 12 18:22:34 ok nice Jan 12 18:22:48 basically it scans every cell Jan 12 18:22:55 including the one of other operators? Jan 12 18:23:29 does it get the MNC+MCC of the cells? Jan 12 18:23:33 GNUtoo-x60: no, only the same operator Jan 12 18:23:44 ah ok Jan 12 18:23:58 that's why openBmap people were interested in osmocombb Jan 12 18:24:12 (because I told them aoout it) Jan 12 18:24:14 GNUtoo-x60: no, i'm afraid not http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.Monitor.html;hb=HEAD Jan 12 18:24:41 altougth someone should code a gpx backend to the mapping cell osmocombb app Jan 12 18:24:49 because I don't have google earth Jan 12 18:26:08 it's great to have the ARFCN tough Jan 12 18:26:57 GNUtoo-x60: i know it tells the frequency and that allows me to distinguish between 1800 and 900 cells but i have no clue how is that any useful. Jan 12 18:28:09 maybe with openBTS? Jan 12 18:28:15 I don't have an USRP tough Jan 12 18:28:34 or for sniffing? Jan 12 18:28:49 so you hope on the same freq with a script? Jan 12 18:29:07 :) Jan 12 18:29:09 Probably Jan 12 18:31:23 PaulFertser: hello Jan 12 18:33:13 dos1: hi :) Jan 12 18:33:29 dos1: i have a strange issue using opimd to resolve phonenumber to contacts Jan 12 18:33:42 dos1: that might be related to normalisation and collation Jan 12 18:34:05 TAsn: ping Jan 12 18:34:22 he did major refactoring of opimd, maybe he'll be interested too Jan 12 18:34:42 dos1: basically, some numbers resolve and some do not (consistently). Those numbers are both fully normalised beforehand, both in the database itself and in the query. Jan 12 18:36:31 hmmm it reminds me that I should update the srcrev of osmocombb Jan 12 18:36:44 in meta-smartphone/meta-osmocombb Jan 12 18:38:12 PaulFertser: do you have python-phoneutils installed? Jan 12 18:38:56 dos1: sure Jan 12 18:39:01 dos1: btw, how are you doing lately? Jan 12 18:39:06 and configured properly? Jan 12 18:39:39 lot of studying, exam session in progress :x Jan 12 18:40:01 dos1: what is the most interesting in what you study? Jan 12 18:40:16 dos1: i guess so, i can't figure yet how area code comes into play though. Jan 12 18:42:07 dos1: it should work regardless, as both my query and the database have a fully normalised number. Jan 12 18:42:49 this semester is a bit boring, the most interesting stuff now i guess is optimisation of heuristics and related things Jan 12 18:43:23 and hmm... opimd just creates a handler for sqlite to compare two phone numbers Jan 12 18:43:42 dos1: yes, and i wonder if that breaks some sqlite assumptions about the collation Jan 12 18:43:43 and it just normalises both numbers before comparing, nothing more Jan 12 18:43:48 I know Jan 12 18:44:17 are you using field name known to opimd? Jan 12 18:44:24 with "phonenumber" type? Jan 12 18:44:24 $phonenumber Jan 12 18:44:31 ok Jan 12 18:44:36 And field "Phone" Jan 12 18:44:40 strange Jan 12 18:45:03 maybe check in python interpreter Jan 12 18:45:11 how phoneutils normalises your phone numbers Jan 12 18:45:25 dos1: seem to work good, tried that already. Jan 12 18:45:38 so looks like some kind of sqlite voodoo Jan 12 18:46:02 I can't use sqlite3 cli to check because it needs collation Jan 12 18:46:53 Here're the collation rules http://www.sqlite.org/c3ref/create_collation.html I wonder if they might be accidentially violated Jan 12 18:47:10 But i can't see how Jan 12 18:49:12 I think they shouldn't be violated irregardless of phoneutils configuration. Jan 12 18:49:24 I mean can't be violated, at least i can't see any possibility for that. Jan 12 18:49:38 i can't either Jan 12 18:53:39 I do not remember when that started to happen Jan 12 18:53:50 I'm now trying to upgrade libphoneutils Jan 12 18:55:55 I think i added some number to the database... Jan 12 18:57:13 Or upgraded something Jan 12 19:06:11 dos1: lol, disabled phoneutils (by moving out the libraries) and now it finds the contact Jan 12 19:06:29 Probably installing it was what broke my setup :) Jan 12 19:06:50 it fallbacks to Jan 12 19:06:51 def normalize_number(a): Jan 12 19:06:52 return a Jan 12 19:07:17 dos1: i know :))) Jan 12 19:07:32 dos1: hm Jan 12 19:07:33 if that wouldn't work then it would be completely insane :D Jan 12 19:07:51 dos1: is it possible that if the database was created with one collation it can't be used with another? Jan 12 19:08:21 dunno... Jan 12 19:08:33 dos1: i wouldn't be surprised! Jan 12 19:08:39 but that might be good point, maybe some indexes are wrong Jan 12 19:08:42 yeah Jan 12 19:09:22 But how to prevent the nastiness? It wasn't that easy to understand... And it's easy to mess accidentally. Jan 12 19:09:56 (by using wrong phoneutils settings for some time) Jan 12 19:12:21 dos1: there should be a "migration" script probably that would allow to dump all the contacts and import again. Jan 12 19:17:15 dos1: anyway, was glad to talk again, thanks for bearing with me :) Jan 12 21:18:30 ha JaMa is not there Jan 13 00:20:23 morphis: how come you didn't tag libfso-glib 2012.07.27.2? Jan 13 01:44:59 * pabs3 looks at specs.git and goes ick! **** ENDING LOGGING AT Sun Jan 13 02:59:58 2013