VCard parse multiline in 3.0

Due to differences in how VCard 2.1 and 3.0 handle multiline properties
there was a bug with peekLine not first checking for read in but
unprocessed lines.  The result was that getPotentialMultiline could
pick up on the next properties multiline field rather than the current
properties multiline fields.
           
Bug: 35946521
Test:  runtest -x frameworks/opt/vcard/
       (testV30ComplicatedCase_Parsing,testV30ComplicatedCase)

Change-Id: I4c9fa8840f2fe8acd2d9e12183dfebbe34be7fa0
3 files changed
tree: c1f4ba44ca19fe1c010aedf23ec101e525088e11
  1. java/
  2. tests/
  3. Android.mk
  4. build.gradle