Re: [Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I understand the logic of the of doing this and don't disagree. However, as this is an entry level device and I believe the only true 64bit O/S advertised for this device, the fact that it does not not work out of the box may impact on the perception of potential new Ubuntu users? Reading Tony's post the Mate website does not say it will work on the PI400 where as the Ubuntu site does. I think the main issue is that people think it is the same board as the Pi4 and it is not. Just my opinion. On Thu, 2020-11-12 at 11:11 +, Sebastien Bacher wrote: > Sorry but I'm reverting that upload for now until the patches are > properly upstreamed. We have been bitten too often by unforwarded > changes that create issues or create maintainance burden over the > years > and we currently don't have the team capacity to deal with extra > cost. > If foundations would like to step up and take over bluez though > that's a > discussion we could have... > > ** Changed in: bluez (Ubuntu Hirsute) >Status: Fix Released => Triaged > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks guys for all the work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Test case works perfectly on the Pi400. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400
Is this the same as: #1903286? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: New Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903286] Re: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
I can confirm all of the above. Also looking at the Pi OS the in which the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the soft block has no effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607490] [NEW] OTA 12 some aplications fail after upgrade
Public bug reported: Following upgrades to OTA 12 the location failed to work on the BQ 4.5 and the Finger print option was missing from the setting menu on the Pro 5. A further reboot of both fixed the problems. I therefore assume that the upgrade process is not initialising some programs correctly? ** Affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1607490 Title: OTA 12 some aplications fail after upgrade Status in ubuntu-touch-session package in Ubuntu: New Bug description: Following upgrades to OTA 12 the location failed to work on the BQ 4.5 and the Finger print option was missing from the setting menu on the Pro 5. A further reboot of both fixed the problems. I therefore assume that the upgrade process is not initialising some programs correctly? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1607490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5
Ok after Marks comment I tried again but without any luck. However I also have a Pro 5 and the finger print function did not work (was not in the menu). I rebooted and it appeared so In did the same with the E4.5 and the new location icon started to change colour and within a few minutes it was all working correctly. It therefore looks like the upgrade process does not initialise all of the programs correctly but a reboot seems to cure this. I will file a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1588994 Title: Location not working since OTA-11 on BQ 4.5 Status in location-service package in Ubuntu: Confirmed Bug description: Since installing OTA-11 Google maps reports 'Google maps could not determine your precise location' and Here maps says 'Can't find your location'. Location detection is ON. 'Using GPS, anonymised Wi-Fi and mobile network info' is selected in Location settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5
Confirm Tony's post above BQ 4.5 location still not working. On my pro 5 as soon as the phone is unlocked the new location icon is coloured in and location is possible. The BQ does not colour in at all and nearby says please enable location service even when scope pulled down to refresh. (Both on OTA 12) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1588994 Title: Location not working since OTA-11 on BQ 4.5 Status in location-service package in Ubuntu: Confirmed Bug description: Since installing OTA-11 Google maps reports 'Google maps could not determine your precise location' and Here maps says 'Can't find your location'. Location detection is ON. 'Using GPS, anonymised Wi-Fi and mobile network info' is selected in Location settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
