OK, it seems like the case reported in the past by few users but we haven't found the cause. There is something different in their setup that makes this not working. It must be related to DBus and someone withis issue needs to run "dbus-monitor --system" in a shell to see the exact message and help us understand the cause. By the way, what's the language set to your device?