Coder's Log

Soon after I mentioned the need for an oFono -backend in Geoclue in my blog , Sri kindly helped me get in touch with oFono developers. What started as a nice friendly discussion soon was turned into a not so nice discussion. I won't get into details and blames but here is what I found out about the project:  oFono developers claim that its is still a maintained project while rest of the world think its a dead project, even people who love the project. Last release being in 2012 and loads of missing essential features (see rest of the points below) and link to mailing-list broken (even though I pointed it out 3 weeks ago and its been broken for much longer) on the homepage all points to the fact that its essentially a dead project. No proper D-Bus introspection nor any client libraries. This already makes it extremely difficult to work with oFono but wait there is more hurdles on the way. No online cross-references documentation: The documentation link on the home-page l

I just flew back from Berlin where I spent the last week, mainly to participate in the GNOME Developer Experience hackfest . As you can see from blog posts from other awesome gnomies , the hackfest was a pretty big success. I focused on the use of virtual machines (as thats right up my alley) for making application development as easy as possible. I talked to Christian , who has been working on an IDE for GNOME about his idea of a simulator VM which allows the developer to quickly test their app in a pristine environment. We discussed if and how Boxes can be involved. After some discussion we decided that we probably don't want to use Boxes but rather create another binary that re-uses the existing virtualization infrastructure: libvirt, qemu, spice (and maybe libosinfo) etc. Another way to make GNOME development easy through VM would be what we already have on a very crude level: Distribution of ready-made VMs with all the development environment setup. Continuous alre

I just rolled out Geoclue 2.1.1 ! Since my last post with Geoclue update, there has been lots of changes. You can find a list of all the changes here but here are the highlights: Modem geolocation: If you got a 3GPP modem, geoclue will now be able to use that to locate you (with neighborhood-level accuracy) using opencellid.org . Additionally if your modem has GPS capability, geoclue can use that as well and as you know GPS is the most reliable geolocation source. One issue with GPS currently is that it takes a while before it can get a lock on and reason for that is that we currently have no support for A-GPS . I'll be talking with Aleksander Morgado during the weekend about how we can add that support but if I've understood correctly, it will need more work in ModemManager than geoclue now that it has all these other sources. Geoclue locating me using 3GPP source WiFi geolocation: In my last relevant blog post, I mentioned that we'll be implementing this