From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WLrI9-00009K-9C for bitcoin-development@lists.sourceforge.net; Fri, 07 Mar 2014 09:42:09 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of zweng.at designates 80.67.31.38 as permitted sender) client-ip=80.67.31.38; envelope-from=johannes@zweng.at; helo=smtprelay04.ispgateway.de; Received: from smtprelay04.ispgateway.de ([80.67.31.38]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WLrI7-0007HV-69 for bitcoin-development@lists.sourceforge.net; Fri, 07 Mar 2014 09:42:09 +0000 Received: from [209.85.216.180] (helo=mail-qc0-f180.google.com) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.68) (envelope-from ) id 1WLr3E-0003jv-VW for bitcoin-development@lists.sourceforge.net; Fri, 07 Mar 2014 10:26:45 +0100 Received: by mail-qc0-f180.google.com with SMTP id x3so4328809qcv.39 for ; Fri, 07 Mar 2014 01:26:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=+Z7Ws/vf4OoNLqTUdrsbOBQY6JyQHCTW05L3+gtoSw8=; b=aVVv3R0Vf77IRqpDTht5ehVl6Fcr3UqjYgBcweRnYzWr2DVRhhU0gkjs182VoBnMFG zVS0/JY59neh1QGh2Es3/J2HtP3LxThW+wNStQVMVSvcipHWmfM7J3pJmxLW9pbCBCaa Jdh4Zd3Q2bfCBg8JAVmAkngUMRTto79v+4rqfdeQk1gFiRyfTpmHvfzQZ7F/uu+TkQ/y 6+Kn8AFLJ3nWnOkfiyBkqHOt0+hjMMdHz7SHiuNbS9N0KhhThX0ePRSAlI8u2fABUlDX DS1h1/x1Z85ZyWRyCsGZ2YtpvYmGM2d6eWBhtlCZfyl/3FBKLJyDtzOm84loG7SwADTH PAVA== X-Received: by 10.140.108.2 with SMTP id i2mr9993042qgf.80.1394184404052; Fri, 07 Mar 2014 01:26:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.66.97 with HTTP; Fri, 7 Mar 2014 01:26:03 -0800 (PST) In-Reply-To: References: From: Johannes Zweng Date: Fri, 7 Mar 2014 10:26:03 +0100 Message-ID: To: Andreas Schildbach Content-Type: multipart/alternative; boundary=001a113ab74a27cc5904f400da3e X-Df-Sender: am9oYW5uZXNAendlbmcuYXQ= X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.67.31.38 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WLrI7-0007HV-69 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Instant / contactless payments X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: johannes@zweng.at List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 09:42:09 -0000 --001a113ab74a27cc5904f400da3e Content-Type: text/plain; charset=ISO-8859-1 2014-03-06 12:26 GMT+01:00 Andreas Schildbach : > In current phone implementations, the screen must be on already for NFC > to be active. Also it must be unlocked, although I certainly hope future > OSes will allow payment apps on the lock screen, just like they allow > music players. Just a small input to this point: On Android 4.4 the new host card emulation (HCE) feature (aka: the phone emulates a ISO-DEP Smartcard and processes ISO7816-4 APDU commands like a Smartcard would do) only works when the display is on, but even when the screen is locked (can be changed with "android:requireDeviceUnlock" in Manifest). See here for detailled specification: http://developer.android.com/guide/topics/connectivity/nfc/hce.html Using the HCE API on Android 4.4 also has the beauty that any app that registers itself for HCE and sets its category to CATEGORY_PAYMENT in the Manifest automatically shows up in Adroid's system settings under "Tap & Pay" (where a user would expect payment applications). --001a113ab74a27cc5904f400da3e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= 2014-03-06 12:26 GMT+01:00 Andreas Schildbach <andreas@schildbach.de>:
=A0
In current phone implementations, the screen= must be on already for NFC
to be active. Also it must be unlocked, although I certainly hope future OSes will allow payment apps on the lock screen, just like they allow
music players.

Just a small input to this p= oint:

Using the HCE API on Android 4.4 also has the beauty th= at any app that registers itself for HCE and sets its category to CATEGORY_= PAYMENT in the Manifest automatically shows up in Adroid's system setti= ngs under "Tap & Pay" (where a user would expect payment appl= ications).


--001a113ab74a27cc5904f400da3e--