These seem to be part of a kernel interface to user-space which, according to Linux licence, is generally held to be a copyright boundary. So your claim there likely is baseless.
There is perhaps a more fundamental problem, in that Google have built their Java userspace bluetooth stack on top of BlueZ. They have insulated their userspace by plugging a DBus proxy/agent in between their software and BlueZ code. However, while this may reduce the technical API dependence of most of their code, the functional fact remains that their Bluetooth stack appears to be dependent on GPL software (outside of that accessed via the Linux userspace API).
My experience of legal advice at another large corporate, in a similarish situation, is that sticking IPC between your code and GPL code does not, of itself, do anything to affect whether or not your code derives from the GPL code.
However, if the BlueZ copyright holders are cool with it, then there's no problem - regardless of what anyone else thinks.