Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Problem bluetooth on Nexus 6p

    Support
    2
    3
    96
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sagrotan last edited by

      Hallo,
      I have problems with bluetooth connection... First time I wanted to connect to another device the bluetooth switch turned automatically from on to off after a view seconds. After several reboots it stayed on. When I connect to another device they are pairing but then the file transport was unsuccessful. It seems the Nexus 6p was refusing the files. The other device gives the error "incorrect pin or passphrase wrong ".
      After a reboot the nexus has the first error (turning automatically from on to off). Logs:
      From file /home/phablet/.cache/upstart/indicator-bluetooth.log:
      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      ** (process:5982): CRITICAL **: rf_kill_switch_real_try_set_blocked: assertion 'tmp1 != tmp2' failed

      In system logs:
      From file /home/phablet/.cache/upstart/application-legacy-ubuntu-system-settings-.log:
      QObject::startTimer: Timers cannot be started from another thread
      Couldn't register agent at /com/canonical/SettingsBluetoothAgent/adapteragent
      Releasing device model ..
      file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml: QML Item: Cannot anchor to an item that isn't a parent or sibling.
      Failed to register our agent with BlueZ: "Already Exists"
      QObject::killTimer: Timers cannot

      Has someone any idea what went wrong?
      Sagrotan

      1 Reply Last reply Reply Quote 0
      • S
        sagrotan last edited by

        ... Strange, but after some days I have tryed again to start bluetooth and it was on?! Now also bluez has started.
        Is it possible the app "bluetooth file transfer" is not available for the nexus 6p? It is not listed in the OpenStore. Is there another way to send / get files via bluetooth?

        Flohack 1 Reply Last reply Reply Quote 0
        • Flohack
          Flohack @sagrotan last edited by

          @sagrotan the App might be 32bit-only. I am afraid there is no other way to transfer files, sorry. And Bluetooth in general isn´t great on UT, thats not a direct fault of the device 😉

          1 Reply Last reply Reply Quote 0
          • First post
            Last post