biemster
strict use of status byte since 17.5.1?
The documents show the first 6 bits of byte 2 of the advertising string being reserved, only the last 2 can be used "freely" (e.g. for battery state):
I've been using byte 2 of the advertisement fully for my own purpose which never happened to be a problem. My phone has updated to 17.5.1 last night and today I see differences for faketags close to it. Exactly since updating iOS the status byte keeps being set to zero.
Interestingly the confidence byte also has dramatically changed exactly at the time of update: it shows values 4-5 times higher than before. Without tags or phone being moved a bit. Has anyone else noticed this?
@humpataa I wonder if this is also causing the issue for tags to not get updates. I posted the issue here: https://github.com/biemster/FindMy/issues/55
Also looks like there is another conversation that might be relevant: https://github.com/seemoo-lab/openhaystack/pull/250
@humpataa were you able to figure out how to get around the issue you mentioned: "I've been using byte 2 of the advertisement fully for my own purpose which never happened to be a problem"
I believe that beta updates of iOS (currently running 17.6.1) have fixed the problem. But I am using the status byte now according to the specification as shown above. Looking good.
@humpataa have you been able to test the new IOS18? If so, have you noticed how it handles the status byte? Thank you for any insights. 🙏
The documents show the first 6 bits of byte 2 of the advertising string being reserved, only the last 2 can be used "freely" (e.g. for battery state):
@humpataa do you have a link to that document?
@humpataa do you have a link to that document?
unfortunately not, you'll need a developer account to get access to it