bluetooth lowenergy - Android L - Difference in BLE Scan Result in LG Nexus 4 and Samsung S4 -


we developing app uses ble functionality. app working fine on devices till of them got android l update. 1 of these devices being lg google nexus 4. device stopped working ever since updated android l. below issues identified:

  1. device scanning slow. returns device after 5-10 seconds when scan every 1 second , use new android l api (startscan proper filter , scan mode set low latency).

  2. even if scan device after delay, there difference in scan result packet returned. on samsung devices (even android l update), proper advertisement packet while same device gives different advertisement packet on nexus 4.

below scan result both devices. both of them 62 bytes see difference in bytes.

we use manufacturing data our business logic because of bytes missing (or replaced other bytes), don't information required on lg nexus 4.

--lg nexus 4 (android 5.1.0) {0x02,0x01,0x06,0x1a,0xff,0x4c,0x00,0x02,0x15,0xf7,0x82,0x6d,0xa6,0x4f,0xa2,0x4e,0x98,0x80,0x24,0xbc,0x5b,0x71,0xe0,0x89,0x3e,0x00,0x00,0x00,0x00,0xa6,0x08,0x09,0x42,0x4c,0x45,0x20,0x52,0x44,0x52,0x02,0xa6,0x00,0x11,0x06,0xfe,0xe2,0x45,0x7f,0x5a,0xb5,0xfd,0x8c,0xf2,0x4a,0x0e,0x3f,0xf4,0xa7,0x25,0x66,0x00,0x00}

--samsung s4 (android 5.0.2) {0x02,0x01,0x06,0x11,0x06,0xfe,0xe2,0x45,0x7f,0x5a,0xb5,0xfd,0x8c,0xf2,0x4a,0x0e,0x3f,0xf4,0xa7,0x25,0x66,0x09,0xff,0xff,0xff,0x2f,0xff,0x11,0xe2,0x02,0x39,0x08,0x09,0x42,0x4c,0x45,0x20,0x52,0x44,0x52,0x02,0xa6,0x00,0x11,0x06,0xfe,0xe2,0x45,0x7f,0x5a,0xb5,0xfd,0x8c,0xf2,0x4a,0x0e,0x3f,0xf4,0xa7,0x25,0x66,0x00}

anyone knows how solve problem?


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -