Using WireMessage instead of FakeWireMessage.

Using WireMessage instead of FakeWireMessage.

This CL breaks the compatibility with BLE devices expecting FakeWireMessages.

This CL also fixes a bug when reconnecting to a given device. It no
 longer removes the |adapter_| after the right device is found.

BUG=513675
Committed: https://crrev.com/7ae8d9c314c283e9d2d8b72e106d6625a009e7bc
Cr-Commit-Position: refs/heads/master@{#341872}

[sacomoto, 2015-07-22 11:33:20]

sacomoto@chromium.org changed reviewers:
+ msarda@chromium.org, tengs@chromium.org

[sacomoto, 2015-07-22 11:33:39]

PTAL.

[msarda, 2015-07-22 12:38:45]

Please add a bug for this change as it breaks the protocol between Chrome and
the other BLE device.

LGTM.

[Tim Song, 2015-07-23 21:23:10]

lgtm

[sacomoto, 2015-07-24 13:58:45]

I filled a bug associated to this CL.

I'm holding this CL until we are ready to go (i.e. CL ready to be submitted) on
the remote BLE side.

On 2015/07/23 21:23:10, Tim Song wrote:
> lgtm

[sacomoto, 2015-08-05 08:13:15]

The CQ bit was checked by sacomoto@chromium.org

[sacomoto, 2015-08-05 08:13:16]

The patchset sent to the CQ was uploaded after l-g-t-m from tengs@chromium.org,
msarda@chromium.org
Link to the patchset: https://codereview.chromium.org/1251843002/#ps80001
(title: "Fixing notification issue")

[commit-bot: I haz the power, 2015-08-05 08:13:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1251843002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1251843002/80001

[commit-bot: I haz the power, 2015-08-05 09:05:18]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2015-08-05 09:07:12]

Patchset 5 (id:??) landed as
https://crrev.com/7ae8d9c314c283e9d2d8b72e106d6625a009e7bc
Cr-Commit-Position: refs/heads/master@{#341872}