GitLab

This allows you to switch from FW 109.11 (ICS-MR1) and FW 109.7 (ICS-MR0).

This EEPROM location is used in ICS-MR1 for a new feature (Hybrid polling),
but the value used in MR1 causes polling to be disabled in MR0. EEPROM values
are stored on the NFC controller and will survive regular flashing. So the
result is that if you switch from MR1 to MR0 then polling will fail.

This fix is low risk, it just explicitly writes the value already stored in
this EEPROM location.

Bug: 5519093
Change-Id: I33d97134c68c03358f22b7773deea73c66166a98

Change-Id: I146e1c83692dc78f647ac01b8470d82c6047996c

Set to 255 ms, increase number of retries to 64.
Add dump() interface to native library

Change-Id: Ib3a32f70453f7f8b79ff89394410f56b4b9dd7a2

Bug: 5480404
Change-Id: I52add3c89fc535bfc37bc8c12ed0f8f905cbe304

Change-Id: I25ff3a0808477797e2916838719f995b2e4368e5

Instead of launching NFC into existing tasks, always launch
into a clean task that is owned and controlled by the NFC process.

Bug: 5122560
Change-Id: Iea6022bb754bcc46e7ab3adb1b9ccc7fe20797e3

The LLCP stack is still using globals without
holding the concurrency lock. When turning the
screen off we were previously disabling the
NFCEE routing before disconnecting the active
target. The routing code would grab the lock
and then touch the globals, which the LLCP
was using illegally, causing a crash when the
LLCP triggered callbacks are delivered.

This change reorders the shutdown at screen
off to disconnect the remote target before
issuing the change to the NFCEE routing in
an attempt to stop the ongoing LLCP
transactions, thereby avoiding the crash.
Since the callbacks are asynchronous the
race is still there, but it's hit more like
10% of the time instead of 100% of the time.

Bug: 5366024
Change-Id: I31230166c1c5bf116195db350ac6605feb90e87f

Bug: 5318512
Change-Id: Iae150be1210bf25c1fc58b41ec24dc301547cf7f

This just crops the status bar and the navbar from the screenshot we take.
This makes the animation look right in all cases, except for when we are full screen:
in that scenario we're cropping away too much.

Also removed the clone view (was no longer used) and cleaned FireflyRenderer
a bit.

Bug: 5318512
Change-Id: I37189a576f19937c2cae4ec368f26ac0725a1b62

Bug: 5430205
Change-Id: I2b6581cb54f49693744bd8739856877dec19f933

Merge "NFC screenshot animation adjustments: - eliminate discontinuous jump when starting failure animation (mScaleUpAnimator) - simplify success animation: fade live app in at scale=1, rather than scaling it back up - minor timing and motion curve tweaks"

Change-Id: I031d83074f38592019912c34a06ddc5c74afd53a

- eliminate discontinuous jump when starting failure animation (mScaleUpAnimator)
- simplify success animation: fade live app in at scale=1, rather than scaling it back up
- minor timing and motion curve tweaks

Change-Id: I1fd5989a6e58e493087653d3a865f774cfc2b32d

Change-Id: I833c466e867b1c1c787654b0b3a42ebca27b7c14

Change-Id: I0cd23cb557e59d7f7736495749e8dc090d771b22

Bug: 5389201
Change-Id: I8ddb60ebe63bcc01e0695868286ad4c7da4afa69

* commit '732f77cf':
  Import revised translations.  DO NOT MERGE.

Change-Id: I9b18d646d7d731f8f227685ccfa4f21276ca8009

This addresses the responsiveness issue identified in b/5140941

Change-Id: I8fad061be2e3f1006e4e2910db84c0a3360e2a0a

* commit '416d5ff3':
  Import revised translations.  DO NOT MERGE

Change-Id: I8cde4e2ddd9df24fae0d19c4d1a865560526a5a4

* commit 'c625b19e':
  Import revised translations. DO NOT MERGE

Change-Id: Iabb046baae875db5b4d26409fb591b54484626a8

Bug: 5300713
Change-Id: I93f0d75d159b3456e6fa8fc376d10493f25e3233

* commit '01400378':
  Import revised translations.  DO NOT MERGE

Change-Id: Iaa6189fc48d663042d7fc0747320d14ef57b09d9

Change-Id: Iadf9d337e0645aaf3d3aafaee0ab710c76d04257

Bug: 4381131

Change-Id: I336adcc3ec4072088074fceabac80e93f992a254

Pull out all the code the track success/failure for the hint.

Doing this as a standalone commit so we can easily revert if we want it back.

Bug: 5350022
Change-Id: Ieb70af10ebaabdf82421c128d72ed1fc374130d2

Bug: 5350022
Change-Id: I803facfd2f50329771ad6eb6e608b91a94e9a6bb

mStartTime was not initialized, which would cause a very large
positive value in mTimeRemaining, because it was only an int
and it wrapped. This caused the scale to be all wrong.

Fixed both issues.

Bug: 5350022
Change-Id: I49c987fb905c90998f5b9083b9c7590225b751c7

Bug: 5296866
Change-Id: I90ccb7127b61aa2242fdb5252cdacccc049d5081

Patch to perform a download at NfcService boot time

This patch permit, when NFC is off, to perform a download if the PN544
is not up to date

Change-Id: Iaa01e218ccd1e4cb18ef77d58c18348823135b1e