WirelessMoves

In Germany we have this great system in place since the liberalization of the telecoms industry in the 1990's called "Call-by-Call" that lets fixed line customers select a carrier to use for national and international calls by dialing an additional access code before the telephone number. In practice it has significantly spurred competition and has brought prices down. But there's also the danger that some black sheep change prices quickly, first getting customers with low prices and then increasing their price ten fold over night without informing them. But there are two cures now:

The first cure is that call-by-call carriers now have to play an announcement before each call to inform customers of the true cost. Problem fixed one might thing. Well not quite because my use of call-by-call is a bit different. I mostly use it for calling abroad from my mobile. Direct calls to international numbers are prohibitively expensive, somewhere between a Euro or two a minute. The same calls from my fixed line at home are in the order of 2 to 3 cents a minute. So the solution for me I have used over many years is to call one of my fixed line numbers at home which is permanently forwarded to one of the few international destinations I call frequently. Praise to home ISDN that gives one several phone numbers (5 in my case). The catch when combining unconditional call forwarding and call-by-call is that no announcement is made because it's not the caller that pays but the forwarder. So my problem was how do I get informed of price hikes?

In the past I manually had to look up prices and was sometimes surprised by the price hikes. Well, no more because now one of my Raspi's does the job for me. With the background I have gained when programming my water alarm system with email notification and the automatic download and backup of all pictures of this blog recently I could quickly put together a script and a Phyton program invoked by cron once a day to download the web page with the prices of my current call-by-call provider, parse it for the prices to the destination countries I'm interested in, extract the price, compare it against maximum values defined and send me an email with the prices and a general verdict in the subject line if everything is still o.k. And with the code for sending an email already there from my previous project and the knowledge I have gained previously of how to parse through strings in Python it took less than two hours to get it working.

Another cloud service at home, excellent! So why am I writing about this? Well, first of course because I'm proud to have done it and done it that quickly. But I also write about it because it shows what can be triggered once you have computing resources available at home running 24/7 that you can play around with and use your imagination and creativity.

And if you want to have a look at the code here we go: Download Call-By-Call-Pi-Code

During a recent basement search session I came across a couple of old newspaper pages I used for wrapping some stuff from December 2003, i.e. from about 10 years ago with advertising on them for mobile phones. I bought my first UMTS phone in December 2004 with hardly any network to use it with where I lived at the time. These advertisement pages predate my UMTS entry by a year and clearly show that UMTS was nowhere in sight then. GSM and GPRS phones being advertised on both pages, MMS and VGA (640×480 pixel) cameras were the highlights of the day. I also wanted to compare prices a bit but based on the information contained in the advertisement it's not really possible. Also no prices whatsoever were given for GPRS. And it was only 10 years ago…

About a year ago SSD prices had fallen to around €300 for a 500 GB drive and I couldn't resist any longer to replace my notebook hard drive for an SSD. The speed-up has been tremendous and I haven't regretted it since. Just for the fun of it I've been keeping a close look at how much data gets written to the SSD and even with a huge safty margin, the 5 GB of data that gets written to the SSD per day with my usage pattern I will not wear out my SSD for at least 30 years. Always ready to optimize, however, I noticed recently, that TRIMing was not activated for the drive.

As the Flash cells contained in an SSD drive can only be rewritten a couple of thousand times, SSDs have sophisticated algorithms to ensure write operations are distributed evenly over the complete drive. That requires that sometimes data of static files that never change is relocated to another part of the drive so those little used Flash cells can be used for something else. This is known as 'wear leveling'.

When a file is deleted, the blocks are marked as empty in the file system. Unfortunately, the SSD knows nothing of file systems as this is a higher layer concepts and SSDs only deal with blocks. That means that once a block is written to the SSD doesn't know whether it contains valid data or whether the block contains to a file that was deleted. In both cases the wear leveling algorithm has to copy the data somewhere else before the block can be reused for other data. This is obviously sub-optimal as a block that contains data of a previously deleted file doesn't have to be copied before it is overwritten.

This is where the TRIM command comes in. When a file is deleted, the file system first deletes the file and marks the blocks the file used as empty. That's standard procedure. But then, in addition, it sends a TRIM command to the SSD informing it that the block is empty. The SSD can then also mark the block as empty and doesn't have to bother copying the useless data it now contains when that block is due for wear leveling replacement.

By default, Linux has TRIM disabled but it's pretty simple to activate it by putting the "discard" option in /etc/fstab for the partition that resides on the SDD. Here's an example:

UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /  ext4    discard,errors=remount-ro 0       1

After a reboot TRIM should be activated. This post explains how to make sure it is active. And for more details on TRIM here's the Wikipedia entry!

 

Teltarif recently reported that one of the mobile network operators in Germany has pledged that they will blanket Germany with LTE by 2015 by using 10.000 LTE base stations. I wonder if that number is correct, however, as according to their Wikipedia entry they currently have 20.000 GSM base stations and 13.000 UMTS station to cover the nation. So either the wrong number of base stations has been reported, somebody is delusional or it's a marketing gag!? 2015 is not far away so we'll see soon.

Half a year ago two things came together that reconciled me with cloud computing: A Raspberry Pi, an inexpensive Linux computer than I can run 24/7 at home as it requires very little power and Owncloud, a piece of open source software that lets me, as its name says, run my own cloud services at home. Not trusting web companies to keep my private data safe even before the recent PRISM revelations I could not export my private data to web based companies. So until then, even though it would have been convenient, I didn't synchronize my calendars and address books on different devices and also did not use cloud storage for exchanging files between different devices and to make them available to others. Obviously when I got things working for the first time I was overjoyed. But how has the setup fared in the past 6 months as routine has set in?

Contacts

In short, it has performed beyond my expectations. Address book synchronization between my Android based mobile devices and Owncloud works like a charm. The only glitch I found so far is that when I rename a contact via the Web interface the change is not propagated to my mobiles. If I do the same on a mobile device, however, the change is properly synchronized. Changes in all other fields are synchronized just fine both ways. Since names of contacts usually change very little that's something that can easily be lived with.

Another thing, due to the limited speed of the Raspi is that it takes a while for the pictures of my contacts to show up in the web interface, even for those contacts that I don't have any pictures and thus get a neutral logo. This has the effect that when I just want to quickly go to my contacts on the PC and then change something it takes a bit for the dialog box that pops-up with the contact's information to become editable. This is not a bug but rather a bit of a usability issue and again not something that stands in the way of an otherwise great usability experience.

Calendar

Calendar synchronization has become even more important to me than address book synchronization across Thunderbird/Lightning on the PC and Android based devices. The Owncloud calendar can be used in Thunderbird with or without a local copy. Over time I noticed that when keeping a local copy, Thunderbird refuses at some point to let me delete some entries while I can delete others just fine. I haven't found a pattern in the behavior but it's not a problem in practice as the online mode that just caches information in Thunderbird for times when a connection to the server is not available works without a flaw. The only downside of online mode is that for adding, removing or changing an entry, Thunderbird needs to have a connection to the Owncloud server. Again, only a problem when I'm not connected, which is pretty much only when I'm on a plane. And even then, I can modify the calendar on my mobile device and changes are synchronized back to Owncloud and Thunderbird as soon as connectivity is reestablished.

File Sharing

I use Owncloud's file storage for sharing files between different devices of my own and also to share files that are too big to be included in emails. Individual files or complete directories can be shared with others without the need for an Owncloud account for the person on my server by generating a link that can simply be clicked. Again, this works great in practice.

A feature requests for the future would be for Owncloud show pictures in externally shared directories with the same gallery option as it does when I view them myself or if I share them with another Owncloud user on my sever. Also, when sharing only a single file the download button should be more in the center of the web browser rather than on the top right for users to find it more easily. Nobody's complained to me about it but I find the layout a bit odd. And finally, I'd like to see an option for external sharing that does not only give me a URL that can be used in my home network but in addition a URL that can be used externally. Today I copy/paste the URL to an email and then replace the beginning of the link with my externally visible URL and a different TCP port number. Not a problem for me but normal users struggle a bit with this.

Summary

Yes, I know, there are a lot of other applications for Owncloud but those three are the ones I use on a daily basis. I can't say this often enough, the combination of a Raspi and Owncloud has been a real game changer for me as I now enjoy the benefits of cloud services without the need for putting my private data out of my zone of trust.

Everyday is groundhog day (in case you know the movie) and every year at around the same time, very detailed network tests of German computer magazines give an interesting insight and comparison of the capabilities of mobile networks in practice.

The latest report is from 'Chip' and the top speed they've measured in an LTE network is almost 80 Mbit/s. While this is an exception rather than the norm, other values are equally stunning. Here's a link to the magazines report in German and here in English, thanks to Google translate. Enjoy!

If you are aware of similar reports about networks in other countries, please leave a comment, I'd be quite interested.

While many users have fast DSL lines at home when it comes to the downlink, uplink speeds are typically still very limited. While many might argue that unless you run servers at home (which I do, e.g. Owncloud, Selfoss, Prosody…) this is hardly noticeable I have to disagree now that I have seen how a Skype video call looks like when both sides of the connection have an uplink that allows them to transmit at faster than 1 Mbit/s. The video resolution, quality and frame refresh rate are as stunning as the bandwidth taken once Skype notices what the network can provide. Quite a number of my video calls these days now stream at an uplink/downlink aggregate of 5 Mbit/s. In othr words such video calls consume 2.25 GB of data per hour. Compare that full two hour movies in SD quality I download from my online video recorder that have a mere 1.5 GB per file.

Every now and then I have to sigh when using Android and wished they would have at least implemented telephony features half as intelligent as Symbian did in its days. But gone is gone and I have to make the best out of it. Activation of call forwarding is one such thing I kept sighing about because changing settings requires to go down several menu levels and waiting a couple of seconds for the device to read the current status from the HLR. But now I've found an interesting fix for that: USSD codes.

Yes, this 1990's technology to use special command codes in a dial string to interact with the HLR in the network in a standardized way speeds up a 2013 Android device. And here's how it works: As it's usually the same numbers I want to forward my calls to when my device is not reachable one can extend the entry of a person in the contacts by the phone number embedded in the USSD code to perform the desired call forwarding activation / deactivation procedure. The figure on the left shows how this is done for 'call forwarding when not reachable'.

The string starting with the '*' activates call forwarding when not reachable to this number and the entry with '#' at the beginning deactivates it again. Not shown in the image is the '#' sign that follows the phone number. Using the code is then as simple as selecting the entry in the address book and to 'dial' it. There's even feedback that the action has been performed.