Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Deprecating Android 2.1 Support

Received: by 10.68.235.4 with SMTP id ui4mr17989671pbc.3.1332737039091;
        Sun, 25 Mar 2012 21:43:59 -0700 (PDT)
X-BeenThere: serval-project-developers@googlegroups.com
Received: by 10.68.226.102 with SMTP id rr6ls10078978pbc.8.gmail; Sun, 25 Mar
 2012 21:43:58 -0700 (PDT)
Received: by 10.68.232.169 with SMTP id tp9mr17995184pbc.6.1332737038714;
        Sun, 25 Mar 2012 21:43:58 -0700 (PDT)
Received: by 10.68.232.169 with SMTP id tp9mr17995182pbc.6.1332737038703;
        Sun, 25 Mar 2012 21:43:58 -0700 (PDT)
Return-Path: <paul.gardner.step...@gmail.com>
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49])
        by gmr-mx.google.com with ESMTPS id e6si15292843pbt.1.2012.03.25.21.43.55
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 25 Mar 2012 21:43:55 -0700 (PDT)
Received-SPF: pass (google.com: domain of paul.gardner.step...@gmail.com designates 209.85.160.49 as permitted sender) client-ip=209.85.160.49;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of paul.gardner.step...@gmail.com designates 209.85.160.49 as permitted sender) smtp.mail=paul.gardner.step...@gmail.com; dkim=pass header...@gmail.com
Received: by pbcun4 with SMTP id un4so6207125pbc.36
        for <serval-project-developers@googlegroups.com>; Sun, 25 Mar 2012 21:43:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        bh=gwQ84rjGIAx00OsIiDZqL1IByK3o5ZuKZkVt5pXOKJc=;
        b=nkipfKPMwxeV29zY67DoJXMWf2Du8OkHe1sU/oJGmPtjzZLHRR95Qsakc5HOpOkXAR
         L28LSemIQoIjL6kOVV+/szgjZchKNVhwGn+PlJWQL6DkH3AFPnOQWcsfVMQ3tgCkWJpl
         UXv/Xdc6Lt0lpRF/YrH9YFln06O5XVCw6R6OkIfykH/MHGj+HxRXK9EfGOpU2W8T4BFw
         LDQCvIjCF5H8vXN2g64deyvJrHuqDoq2UHuwybvGWR7R6eXAu3v2VB78YsTCrGgIbzgr
         d+houx6kFRfQa6TP1ZSt5O6NosfBkJBTJS8iH1EzLzyAydO3D3QTptR77Vq1ZPcU5BXC
         iA6A==
MIME-Version: 1.0
Received: by 10.68.197.194 with SMTP id iw2mr49768906pbc.26.1332737035623;
 Sun, 25 Mar 2012 21:43:55 -0700 (PDT)
Sender: paul.gardner.step...@gmail.com
Received: by 10.68.138.136 with HTTP; Sun, 25 Mar 2012 21:43:55 -0700 (PDT)
Date: Mon, 26 Mar 2012 15:13:55 +1030
Message-ID: <CA+_T8-D+6fAZBzysvNqfUFp=ZCJ+EARP+g2Dx5x53oPZE2v...@mail.gmail.com>
Subject: Deprecating Android 2.1 Support
From: Paul Gardner-Stephen <p...@servalproject.org>
To: serval-project-developers@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

We are currently thinking about deprecating support for Android 2.1 in
our next release, as it solves a few problems for us.

Google statistics suggest that only about 7.5% of devices today are on
Android 2.1 or older, and we expect that this figure will be even
lower by the time we hit official public release around September
2012.

Does anyone see any problems with this?  We can't think of any, but
want to make sure we are not committing some heinous error in doing
so.

Thanks,
Paul.