Bug did not expire due other bug tasks
No reply to comment #25 or other comments for over 3 years
Marking "Invalid" to close
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Confirm bug for 15.10
Even more, Bluetoth applet say 'no adapters found' even if connected to other
devises.
$sudo bccmd psset -s 0x 0x028c 0x0001
$hcitool dev
Devices:
hci0CC:52:AF:DE:E9:CB
$sudo /etc/init.d/bluetooth restart
[ ok ] Restarting bluetooth (via systemctl): bluetooth
tried
and it made it work on my ubuntu 14.04 LTS
sudo bccmd psset -s 0x 0x028c 0x0001
sudo hciconfig hci0 up
sudo /etc/init.d/bluetooth restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7815
This occurs in Ubuntu 13.10 amd64 on an HP Pavilion DM1Z (AMD APU E-350
unit) and the "bccmd psset -r -s implementation 0x028c 0x0001"
workaround does work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Confirm bug affects Ubuntu 13.04 (hardware: HP ProBook 4320s, Ralink
bluetooth ), so it must be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781556
Title:
bluetooth discovery fails: no devic
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
I can confirm that Linux Mint has normal wifi + bluetooth behaviour, how
does one go about extrapolating this onto Ubuntu?
** Also affects: bluez
Importance: Undecided
Status: New
** Project changed: bluez => linux
** Project changed: linux => blueman
--
You received this bug notific
Not sure on the progress on this but while toying around the other day under
Wubi on my HP G62-B18SA notebook I found that by default Bluez does not support
the wifi card entirely, however, Blueman does. The only issue I have found with
Blueman is that the wifi card tends to be enabled by defaul
I'm still not convinced that this should be covered by a udev rule in
bluez; seems to me like this will conflict with the killswitch states
for the device, which appear to me as more important to preserve in all
cases. (For instance, booting your computer in a plane shouldn't cause
the udev rule to
Updated the patch with v2:
- change to Makefile.in to add the udev rule as it seems not generated from
Makefile.am
- add 'udevadm trigger --action=add --subsystem-match=bluetooth' to
debian/bluez.postinst
** Patch added: "fix-ralink-rt5390-bluetooth-with-bccmd-v2.patch"
https://bugs.laun
Better to add 'udevadm trigger --action=add --subsystem-match=bluetooth'
to bluez.postinst, so the udev rule can take effect once the package has
been installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The attachment "fix-ralink-rt5390-bluetooth-with-bccmd.patch" of this
bug report has been identified as being a patch. The ubuntu-reviewers
team has been subscribed to the bug report so that they can review the
patch. In the event that this is in fact not a patch you can resolve
this situation by
Below is a fix to bluez
** Patch added: "fix-ralink-rt5390-bluetooth-with-bccmd.patch"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/781556/+attachment/2832774/+files/fix-ralink-rt5390-bluetooth-with-bccmd.patch
--
You received this bug notification because you are a member of Ubuntu
Simply performing bccmd in the bluetooth init script might not be a good
idea, as it's not applicable to other bluetooth modules. One reliable
way is to keep it in the udev rules. I used the rules below which is
working for me:
SUBSYSTEM=="bluetooth", SUBSYSTEMS="usb", ATTRS{idVendor}=="148f",
ATT
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781556
Title:
bluet
Hello everyone,
Using the following steps I fixed my bluetooth for now.
First I disabled wireless using fn+f12, and then I re-enabled it, again using
fn+f12.
This made the adapter show up in BlueZ as hci0, which is needed for running the
bccmd commands.
Then I issued the following command:
b
Did some further testing and finished my bash script to enable the
bluetooth radio when required. (I removed the modifications I made to
'/etc/init.d/bluetooth'). The script looks like this:
sudo bccmd psset -s 0x 0x028c 0x0001
sudo hciconfig hci0 up
sudo /etc/init.d/bluetooth restart
sleep 2
This single command is a good suggestion. I think I'll put in in a
script on my desktop to switch on the radio when needed instead of
switching it on by default using /etc/init.d/bluetooth. This will save
battery power.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Seems copy-pasting dropped the last 1 on the line, that should be
sudo bccmd psset -s 0x 0x028c 0x0001
sudo bccmd warmreset
Browsing through the bccmd source code: The first part is "put the value
0x0001 in ps key 0x028c and store it in store 0x". Store 0x is
the same as default, so
After issuing the following two commands:
sudo bccmd psset -s 0x 0x028c 0x000
sudo bccmd warmreset
I started seeing inquiry results and was able to successfully pair to
another device. I did not need to restart bluez.
--
You received this bug notification because you are a member of Ubuntu
Bluetooth discovery fails because with the Ralink chip the bluetooth
radio is off by default, it need's to be switched on after each boot.
This can be done with the command: sudo bccmd psset -s 0x 0x028c
0x0001
Afterwards restart bluetooth: sudo /etc/init.d/bluetooth restart
You can add this
Confirmed. Kubuntu 10.10. Bluez 4.6 and 4.85.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781556
Title:
bluetooth discovery fails: no devices found during scan
--
ubuntu-bugs mailing list
ubuntu
A workaround is described here:
http://ubuntuforums.org/showthread.php?t=1584388. Boot in Windows, turn
on bluetooth, turn off bluetooth/wifi in hardware with fn-12, and boot
in Linux. This is just a workaround; it's suboptimal having to install
Windows to get working bluetooth.
--
You received t
** Attachment added: "hcidump output during scan"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/781556/+attachment/2125478/+files/hci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781556
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781556
Title:
bluetooth discovery fails: no devices found during scan
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
26 matches
Mail list logo
