[rilmodem] Set technology preference values to match recent RIL changes
Merge pull request #103 from tkenakka/techpref

[rilmodem] Set technology preference values to match recent RIL changes
Merge pull request #104 from jpoutiai/master

driver clean up fixes.
[rilmodem] Check the ratmode and force it to be as configured

After flashing default rat mode might be different than configured. If
so, it needs to be set.

Signed-off-by: Jussi Kangas <jussi.kangas@oss.tieto.com>
Merge pull request #105 from jkangas/master

Request for pulling ratmode forcing to main branch.

Reviewed by jpoutiai and me. Merging..
[gdbus] Fix crash when disconnecting from D-Bus

Upstream commit:

From b4b4b35d0beac7340aed6da979f043dd1424a631 Mon Sep 17 00:00:00 2001
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Mon, 9 Sep 2013 11:25:12 +0300
Subject: [PATCH 01/25] gdbus/watch: Fix crash when disconnecting from D-Bus

When disconnecting from D-Bus a message could be recieved with no sender:
Invalid read of size 1
   at 0x4A09EE1: strcmp (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
   by 0x3B03C386B8: g_str_equal (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x4065D6: message_filter (watch.c:529)
   by 0x3B0700F9E5: dbus_connection_dispatch (in /usr/lib64/libdbus-1.so.3.7.4)
   by 0x4052E7: message_dispatch (mainloop.c:76)
   by 0x3B03C48962: ??? (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x3B03C47E05: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x3B03C48157: ??? (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x3B03C48559: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x4038C5: client_proxy_removed (test-gdbus-client.c:902)
   by 0x3B03C6B566: ??? (in /usr/lib64/libglib-2.0.so.0.3600.3)
   by 0x3B03C6B6E5: ??? (in /usr/lib64/libglib-2.0.so.0.3600.3)
 Address 0x0 is not stack'd, malloc'd or (recently) free'd
Merge pull request #107 from marttipiirainen/dbus_crash_upstream_fix

[gdbus] Fix crash when disconnecting from D-Bus
[nettime] Prefer CLOCK_BOOTTIME over CLOCK_MONOTONIC

The CLOCK_MONOTONIC might get frozen during suspend.
CLOCK_BOOTTIME does not have this problem and should be used
when available.
[rilmodem] Queue DTMF requests in driver

Signed-off-by: Martti Piirainen <martti.piirainen@oss.tieto.com>
Merge pull request #108 from pgerdt/use-clock-boottime

[nettime] Prefer CLOCK_BOOTTIME over CLOCK_MONOTONIC
Merge pull request #109 from marttipiirainen/dtmf_queue

[rilmodem] Queue DTMF requests in driver
[smsutil] Allow partial conversion of UCS2 SMS

Signed-off-by: Martti Piirainen <martti.piirainen@oss.tieto.com>
Merge pull request #111 from marttipiirainen/sms_retry_conversion

[smsutil] Allow partial conversion of UCS2 SMS
[smsutil] Improve conversion of incoming UCS2 SMS to UTF-8

By this change characters found from incoming UCS2 SMS which are not part
of UTF-8 character set are passed to message manager API client as
Unicode escape characters (\uxxxx or \Uxxxxyyyy). The decoding codeset
has been changed from UCS-2BE to UTF-16BE as UTF-16 allows surrogates
(the use of two characters/four bytes to make one codepoint).

Signed-off-by: Petri Takalokastari <petri.takalokastari@oss.tieto.com>
Merge pull request #112 from ptakalok/master

[smsutil] Improve conversion of incoming UCS2 SMS to UTF-8
[rilmodem] do not check spdi if mcc and mnc are not valid

It is possible that network is received before current operator
is retrieved. In rare occasions this causes crash when tried
to compare mnc and mcc of current operator to spdi.

Signed-off-by: Jussi Kangas <jussi.kangas@oss.tieto.com>
Merge pull request #113 from jkangas/master

Request for pulling mcc and mnc presence check before spdi search to main branch
[rilmodem] numeric value can be null in response to RIL_REQUEST_OPERATOR

According to ril.h numeric value can be null in response to
RIL_REQUEST_OPERATOR. That means phone is unregistered and
current operator should return error

Signed-off-by: Jussi Kangas <jussi.kangas@oss.tieto.com>
Merge pull request #114 from jkangas/master

Request for pulling operator name numeric value check to main branch
Fix receiving USSD messages not part default GSM character set

RIL delivers USSD string already decoded in UTF-8 format. Hence there is
no need for extra encoding/decoding in rilmodem driver and ofono core.
This implementation will bypass the encoding/decoding mechanism by
using hexadecimal value 0xFF as data coding scheme (reserved SMS and CBS
data coding scheme value in 3GPP TS 23.038)

Signed-off-by: Petri Takalokastari <petri.takalokastari@oss.tieto.com>