Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No beacons sent on Asus Nexus 7 (2013) / Android 6.0.1
See original GitHub issueI was curious about the data that is sent over the air, so I extended my test-app for receiving ble-data in order to be able to se the beacons sent by this app. With the app I can see beacons sent out by some device (currently only one of my neighbors has the app installed) I then installed the app to my old tablet (Asus Nexux 7 (2013), Android 6.0.1). Installation succeeded without any errors.
Expected behaviour
But I can not see any beacons sent by this device.
I then hooked the tablet to my development machine to have a look at the logs and fond the following:
06-19 17:51:15.561 2835-2835/? I/ExposureNotification: BleDatabaseWriter.writeBleSighting, id=2EF48754ABD44A88144A5B555E640095 [CONTEXT service_id=236 ]
06-19 17:51:15.614 2835-2835/? I/ExposureNotification: Scan device 5C:F3:3D:7E:67:93, type=1, id=2EF48754ABD44A88144A5B555E640095, raw_rssi=-83, calibrated_rssi=-89, meta=5C57DF85 [CONTEXT service_id=236 ]
06-19 17:51:15.614 2835-2835/? I/ExposureNotification: Reschedule interval too short, timeMsSinceLastSchedule=9701 [CONTEXT service_id=236 ]
06-19 17:51:15.614 2835-2835/? I/ExposureNotification: BleDatabaseWriter.writeBleSighting, id=2EF48754ABD44A88144A5B555E640095 [CONTEXT service_id=236 ]
06-19 17:51:15.626 2835-2835/? I/ExposureNotification: Scan device 5C:F3:3D:7E:67:93, type=1, id=2EF48754ABD44A88144A5B555E640095, raw_rssi=-83, calibrated_rssi=-89, meta=5C57DF85 [CONTEXT service_id=236 ]
06-19 17:51:15.627 2835-2835/? I/ExposureNotification: Reschedule interval too short, timeMsSinceLastSchedule=9705 [CONTEXT service_id=236 ]
06-19 17:51:15.627 2835-2835/? I/ExposureNotification: BleDatabaseWriter.writeBleSighting, id=2EF48754ABD44A88144A5B555E640095 [CONTEXT service_id=236 ]
06-19 17:51:15.631 2835-2835/? I/ExposureNotification: Scan device 5C:F3:3D:7E:67:93, type=1, id=2EF48754ABD44A88144A5B555E640095, raw_rssi=-83, calibrated_rssi=-89, meta=5C57DF85 [CONTEXT service_id=236 ]
06-19 17:51:15.631 2835-2835/? I/ExposureNotification: Reschedule interval too short, timeMsSinceLastSchedule=9701 [CONTEXT service_id=236 ]
06-19 17:51:15.631 2835-2835/? I/ExposureNotification: BleDatabaseWriter.writeBleSighting, id=2EF48754ABD44A88144A5B555E640095 [CONTEXT service_id=236 ]
Not sure if it helps …
Technical details
- Mobile device: Asus Nexus 7 (2013)
- Android version: 6.0.1
(Installing on a Pixel3a also succeeded without errors and there I can see the generated beacons.)
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In the case that the device does not support required modes, it should generate an error-message, preferably by Google, but if they don’t do it, it could be done through the app.
@cschweers: Well, I might behave differently if I think that I informed all my contacts about my infection when the device was not capable of doing so. I disagree with the “social” argument. The fact that the app does not all the things that it promises to do IMHO must not be hidden to the user - 100% transparency. Although this affects only a very small portion of the user base (infected users that use those old devices) - sending useless data to the server does not make sense to me. So the corresponding option to send infection informatio has to be disabled in that cases.