Cwa-app-android: Beacons are sent only sporadically on OnePlus 6, Android 10

Created on 20 Jun 2020  Â·  7Comments  Â·  Source: corona-warn-app/cwa-app-android

Because the app doesnt provide any feedback or stats about beacons sent/received, i used "BeaconScope" on an other device to check if the app works.

Describe the bug

In our household we have two main phones: an iphone and my android phone (OnePlus 6. Android 10). When i opened up "BeaconScope" on a third device to check if both phones advertise themselves correctly, i could only see the iPhone, sending out beacons with a 1 Hz rate.

After turning the androids bluetooth off and on again the phone appeared, i could see it with BeaconScope but only for 1 or 2 packets. Then it disappears while the iPhone still works fine. Every once in a while (30s up to 5 min interval) it appears again, sends out 2 or 3 packets and disappears again.

Even after turning energy-saving off for the app, it still does not work correctly.

Expected behaviour

I expect the app to send out beacons in a fixed interval, e.g. 1 Hz.

Technical details

First screenshot: both phones are discovered

Screenshot_20200620-101159

Second screenshot, 8 seconds later: only the iphone is still sending beacons

Screenshot_20200620-101206

Additional context

This issue kind of relates to https://github.com/corona-warn-app/cwa-wishlist/issues/5 because stats about beacons sent or received/stored in DB could show that somethings might be wrong here.


Internal Tracking ID: EXPOSUREAPP-1933

Add to FAQ bug community google mirrored-to-jira

Most helpful comment

That's interesting, perhaps there is some hardware issue with OnePlus 6 (I wonder if it differs much in terms of hardware from OnePlus 5T). Can just confirm that when placed far away from receiver in the second room, and with all applications closed the results from OnePlus 5T and Motorola seem to be consistent:

moto_vs_oneplus_2

All 7 comments

I gave it a quick smoke-test: two devices (OnePlus 5T with Android 10 and Motorola G2 with Android 6) next to each other and at the same very short distance to sensitive Bluetooth antenna (10 cm). Frequency is the same, but indeed OnePlus seems to be transmitting beacons with much weaker signal strength, corresponding to measured distance (if we translate it with proper equation) couple of times greater than for Motorola beacons. Maybe this is a factor why you don't see as frequent beacons from OnePlus device. But don't take my word for it - I'm also listening to music over Bluetooth on OnePlus so these are not laboratory conditions (although quite real-life).

oneplus_vs_moto

(the reason you see two beacons transmitted at the same time is that I just recorded it with 1-second time resolution)

Maybe this is a factor why you don't see as frequent beacons from OnePlus device

Although these results are interesting (weaker signal, but still frequent), in my test scenario the iPhone was placed 4 meters away (as seen in the screenshot), but the Oneplus was placed next to the test phone and i still cant receive frequent packets.

Note: With BeaconScope, the more packets it receives, the higher the accuracy. With 1 packet it measures sometimes 2m, sometimes 0,1m.

That's interesting, perhaps there is some hardware issue with OnePlus 6 (I wonder if it differs much in terms of hardware from OnePlus 5T). Can just confirm that when placed far away from receiver in the second room, and with all applications closed the results from OnePlus 5T and Motorola seem to be consistent:

moto_vs_oneplus_2

Update: this was fixed with the latest update, it shows the status correctly right now

I’d like to add to this that the app shows conflicting information on my Oneplus 6 also on Android 10, Oxygen OS v10.3.4
As you can see in this picture:
537C1CE6-5D83-4709-AABA-4D69E118C1D1
The top bar shows that I have tracing enabled, but the card below it says it is not. If I click on „einschalten“ this does not change. I have also set the app to „not optimized“ in battery settings.

Hey @florianwgnr,

Did the bug eventually disappear for you?

Regards,
CH


Corona-Warn-App Open Source Team

Hey @florianwgnr,

Did the bug eventually disappear for you?

I just checked it again and yes, beacons are now sent regularly. Thanks!

@florianwgnr Thanks for checking. One bug less to worry about :)


Corona-Warn-App Open Source Team

Was this page helpful?
0 / 5 - 0 ratings