Live data from Hacker News

Some Android apps are using ultrasonic beacons to track users

bleepingcomputer.com

11–20 of 93 posts

Re: Some Android apps are using ultrasonic beacons to track users

#11
> Their results revealed Shopkick ultrasonic beacons at 4 of 35 stores in two European cities. The situation isn't that worrisome, as users have to open an app with the Shopkick SDK for the beacon to be picked up.

Wouldn't it be far easier to just transmit a wifi SSID that encodes this information?

Re: Some Android apps are using ultrasonic beacons to track users

#12
post #4
post #3

Is it really ultrasound? Microphones on phones may be able to pick this but what speakers are able to play even 20 kHz? And these apps should always listen, that will drain battery quickly, so these apps will be listed in top power-consuming apps and user will notice it.

18-19 kHz is usually high enough; smartphone speakers can play that fine from my experience. Yes, battery drain is an issue. Most apps use a background service that wakes up at a fixed interval. The longer the interval, the longer the broadcast has to be though, so it's basically a trial and error kind of thing.

Clock sync? Protocol usually is to check NTP and broadcast at prechosen times if you wanna keep the battery drain down.

Re: Some Android apps are using ultrasonic beacons to track users

#14
post #10

Sounds a little like one of Powa Technologies ideas before they went boom. Embed inaudible tones in tv content to sell you stuff. Never saw the appeal. But as we know the appetite for tracking is endless, foe some reason.

Facebook and Google's advertising revenues can give you some idea of the reason.

Re: Some Android apps are using ultrasonic beacons to track users

#16
Shouldn't be too hard, at least in principle, to enable a low-pass digital filter in the Android audio subsystem. There must already be one there for anti-aliasing when apps demand 16000 or 8000 samples/second capture. Just need to leave the 8KHz low-pass filter enabled for the 99% of us that never use the mike to capture music.

Re: Some Android apps are using ultrasonic beacons to track users

#17
post #4

Earlier quoted context omitted.

18-19 kHz is usually high enough; smartphone speakers can play that fine from my experience. Yes, battery drain is an issue. Most apps use a background service that wakes up at a fixed interval. The longer the interval, the longer the broadcast has to be though, so it's basically a trial and error kind of thing.

Another issue (besides the privacy issue) is that it may be annoying for pets. Dogs and cats can hear these sounds. Also the apps on the phone have access to the microphone (even though they probably do not need this permission for any other purpose), so these apps are all potential listening devices.

i'm so glad you said this... made my day

Re: Some Android apps are using ultrasonic beacons to track users

#18
post #5

This is why apps that shouldn't need the mic or speaker but still require it should not be installed. Permissions on an app should be checked carefully by a user, and users should be educated in this!

That model is backwards. If there is one thing iOS got right, it's the permission prompt. Nobody reads those lists and it's hard to know what the intent is without context in the app.

Having the app ask on first use makes much more sense. It's much less likely to get away with this. Even better, you can still use the app if you say no. It will just get dummy values back.

Re: Some Android apps are using ultrasonic beacons to track users

#19
> The only good news found in this research was that after searching TV streams from seven different countries, researchers failed to discover any ultrasonic beacons

Would that even work? I'm pretty sure modern digital TV audio compression totally removes sound that is vaguely close to 'ultrasound'. I guess maybe smart TV apps could add the signal though, but why would they when they already know what you are watching?

It reminds me of a website for one of those annoying 'Mosquito' anti-loitering devices. The sound was provided as an MP3, which was of course totally filtered out by the compression resulting in a totally empty file.

Post reply on HN