Bluetooth to work on crouton #55
Comments
|
It should work already if you install and then set up your bluetooth audio device in the resulting blueman applet. |
|
Does this support the arm chromebook? |
|
Probably. |
|
Thanks for your help with my other question, re: deleting the chroot that didn't install completely. I have it working now on my C7, and just installed blueman and pulseaudio. When i start Blueman it isays, "Connection to BlueZ failed. Bluez daemon is not running, blueman-manager cannot continue. This probably means there were no bluetooth adapters detected or bluetooth daemon was not started. I am trying to use the built in bluetooth adapter in the C7. Would this only work with a USB bluetooth dongle adapter? |
|
Did you start blueman via the command |
|
wow, you are really quick with the help. How would I quit it? I know these questions are perhaps annoying, but I am learning from almost no background here. Is there a good place to learn basic commands to use in this terminal? |
|
LinuxCommand.org seems to have a pretty good tutorial to get you started; the rest just comes with experience and a lot of searching. |
Prevents accidental wiping when switching between normal and dev modes. installer, host-bin: Automatically mount crouton partition. mkpart.sh: Warn if ChrUbuntu is installed. Increase logout timeout. Thanks @DennisLfromGA for testing mkpart.sh: Check if chroots are mounted before waiting 10 seconds. Also readlink /var/run/crouton (on most recent Chromium OS we use /run/crouton) We are crouton Authors... ...crunchy and yummy! mkpart.sh: Use partx instead of partprobe. partprobe was removed from upstream (crbug.com/377052) mkpart.sh: Do not run if a Chromium OS update is pending Fixes dnschneid#55. mkpart.sh: Autoreboot after 30 seconds. mkpart.sh: s/read/read -r/ mkpart.sh: Allow automation of answers. mkpart.sh: Not being able to call clear is not a fatal error. mkpart.sh: Pipe output to /dev/kmsg Especially in autotest context, it can be useful to have access to logs in /dev/pstore. test/test-mkpart.sh: non-autotest mkpart test This should be rewritten as a server-side test in autotest. This test is simpler: it locks the machines, runs the partition tests, then unlocks them. Revert "mkpart.sh: Pipe output to /dev/kmsg" This reverts commit 856896a. This causes install to hang waiting for loggout. Probably beacuse tee is still running. For now we can do without.
Prevents accidental wiping when switching between normal and dev modes. installer, host-bin: Automatically mount crouton partition. mkpart.sh: Warn if ChrUbuntu is installed. Increase logout timeout. Thanks @DennisLfromGA for testing mkpart.sh: Check if chroots are mounted before waiting 10 seconds. Also readlink /var/run/crouton (on most recent Chromium OS we use /run/crouton) We are crouton Authors... ...crunchy and yummy! mkpart.sh: Use partx instead of partprobe. partprobe was removed from upstream (crbug.com/377052) mkpart.sh: Do not run if a Chromium OS update is pending Fixes dnschneid#55. mkpart.sh: Autoreboot after 30 seconds. mkpart.sh: s/read/read -r/ mkpart.sh: Allow automation of answers. mkpart.sh: Not being able to call clear is not a fatal error. mkpart.sh: Pipe output to /dev/kmsg Especially in autotest context, it can be useful to have access to logs in /dev/pstore. test/test-mkpart.sh: non-autotest mkpart test This should be rewritten as a server-side test in autotest. This test is simpler: it locks the machines, runs the partition tests, then unlocks them. Revert "mkpart.sh: Pipe output to /dev/kmsg" This reverts commit 856896a. This causes install to hang waiting for loggout. Probably beacuse tee is still running. For now we can do without. Conflicts: installer/main.sh
|
I am having trouble with this, even with bluetooth in chrome os on. My little sticker says CB3-131, and I have a Acer Chromebook 11. Here is the error, Trusty Xubuntu https://imgur.com/gallery/wCBhx |
Would it be possible to get bluetooth support on crouton for audio devices?
The text was updated successfully, but these errors were encountered: