Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iPhone 15 - lack of reports #219

Open
davesenior9 opened this issue Oct 28, 2023 · 10 comments
Open

iPhone 15 - lack of reports #219

davesenior9 opened this issue Oct 28, 2023 · 10 comments
Labels
question Further information is requested

Comments

@davesenior9
Copy link

I've recently upgraded to an iPhone 15 and I am noticing a distinct lack of reports, generated by that device.

My old phone (iPhone 8), would routinely upload reports, and I would subsequently see a location report of my home.

Since getting the iPhone 15, I have got ZERO reports from my OpenHayStack devices. I haven't changed the beacon device, if I leave it in my bag and go to work, I'll get reports as per usual from the wider Apple Offline Finding network.

Does anyone have any insight's on how the iPhone 15 might be doing this? Or has anyone seen similar behavior?

@davesenior9 davesenior9 added the question Further information is requested label Oct 28, 2023
@shiprec
Copy link

shiprec commented Dec 6, 2023

@davesenior9 Where you able to get this resolved?

@davesenior9
Copy link
Author

Unfortunately no. I tried changing the status field to 'imitate' other Apple Devices, such as Airpods an actual Airtag etc, didn't see any change in result.

@shiprec
Copy link

shiprec commented Dec 19, 2023

Not sure if you saw this:
biemster/FindMy#40

@biemster
Copy link

@davesenior9 what exactly did you do to the status field?

@davesenior9
Copy link
Author

when capturing 'offline finding' data, you will see some variance in the status byte field that directly correlates to the type of device that is beaconing that data.

Example; most of the haystack stuff has it set to 0x00, however, a real AirTag status byte is 0x10 (I think this changes to 0x11 when it has a lower battery? unconfirmed). AirPods will transmit a status byte of 0x33 or 0x39.

So, in my troubleshooting, I just tried manipulating the status byte with these values to see if anything worked.

@Systm21
Copy link

Systm21 commented Dec 29, 2023

@davesenior9 the guys at biemster/FindMy#40 already fiddled around with Status Bytes and Hint Bytes, but without any success.
If you have logs from apple devices and maybe the adv data, it can help, finding a solution.

@isibizi
Copy link

isibizi commented Mar 22, 2024

iOS 17.4.1 has fixed this issue

@davesenior9
Copy link
Author

So the Off-line Finding network is working as it was with IOS 16?

@isibizi
Copy link

isibizi commented Mar 22, 2024

Yes, is definitely fixed. I have an 15 pro max with 17.4.1

@davesenior9
Copy link
Author

That's huge news. I'll give it a look/try this morning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants