iBeacon AD filter too strict about android-ibeacon-service

[davidgyoung]

Thanks for this. I'm not sure I understand the details of what you are saying. The filter currently looks only for the sequence 4C 00 02 15. That was the change in the revision you mention. Are you saying some of these four bytes should not be part of the filter?

[slackhappy]

I'm saying that 4C could start at scanData[2] up to scanData[6]

my full advertisement started like:
scanData[0] == 0x1a
scanData[1] == 0xff
scanData[2] == 0x4c
scanData[3] == 0x00
scanData[4] == 0x02
scanData[5] == 0x15
//UUID
//Major
//Minor
//txPower

[davidgyoung]

Oh, I see. Yes, you are correct -- I was able to verify this with another iBeacon that starts at byte 2. I have pushed changes to master for this in 1e4f6af

[slackhappy]

Awesome! Thanks!